911 353 02a0350

Operating Manual
SRA series 3 SVR 3.5.0 OMN
911-353/02A0350
Copyright (C) Siemens Information and Communication Networks S.p.A. 2002 Microwave Networks
Issued by Product Documentation Department S.S. 11 Padana Superiore, km 158 I-20060 Cassina de Pecchi MI Technical modifications possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.
SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002
STATUS OF MANUAL
STATUS OF MANUAL Current: Previous: Issue 1, May 2002
R-1
STATUS OF MANUAL
LA
PA
R-2 SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002
INDEX
INDEX
STATUS OF MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R.1 INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.1 LIST OF ILLUSTRATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.5 LIST OF TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.11
FOREWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1
1.1 1.2 1.3 1.4 Subject and purpose of the manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Testing and warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Manuals related to SRA series 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3
EQUIPMENT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

2.1 2.1.1 2.1.2 2.2 2.2.1 2.2.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Local Craft Terminal (LCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 LCT connection to the equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 User classes and security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 User classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 NE Access Control Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3
SAFETY RULES AND PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

3.1 3.2 3.3 3.4 First aid for electric shocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Artificial respiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Treatment of burns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Safety labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3
INSTALLATION OF SOFTWARE PLUG-IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1

4.1 4.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1
DOWNLOAD OF CONTROLLER UNIT SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . 5.1

5.1 5.2 5.3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Download via FTP (for IDU unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Download via FTP (for ODU NPL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7
I-1
INDEX
GUIDE TO USE OF SRA SERIES 3 MANAGEMENT PROGRAM. . . . . . . . . . . . . . . 6.1

6.1 6.2 6.2.1 6.2.2 6.2.3 6.2.3.1 6.2.4 6.2.4.1 6.2.4.1.1 6.2.4.1.2 6.2.4.2 6.2.4.2.1 6.2.4.2.2 6.2.4.3 6.2.4.4 6.2.4.4.1 6.2.4.4.2 6.2.4.4.3 6.2.4.4.4 6.2.5 6.2.6 6.2.7 6.3 6.4 6.5 6.5.1 6.5.1.1 6.5.1.2 6.5.1.3 6.5.1.4 6.5.1.5 6.5.1.6 6.5.1.6.1 6.5.1.6.2 6.5.1.6.3 6.5.1.6.4 6.5.1.6.5 6.5.1.7 6.5.2 6.5.2.1 6.5.2.2 6.5.2.3 6.5.2.4 6.5.3 6.5.3.1 6.5.3.2 6.5.4 6.5.5 6.5.5.1 6.5.5.2 6.5.5.3 6.5.5.3.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 Software functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 Equipment control and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 EEPROMs management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3 Key policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3 Configurations stored in the key EEPROM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5 1+1 equipment description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 Master / Slave definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 Master/Slave swap operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 Illegal situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 E2PROM and key management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8 Key/ MB E2PROMs copy directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8 E2PROMs updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8 IDU1 / IDU2 definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9 Matching between two IDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9 Hardware matching requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10 Software matching requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10 System type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10 Changing the system type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10 Use licence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.11 Connection status of the unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.12 Loading of SRA Series 3 plug-in software (configuration file) . . . . . . . . . . . . . . . . . . . . . . . . 6.13 Structure of the operative menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.15 Status and Config menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switches Config (only for (1+1) System Types) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J0 Link ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCN Setting menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RPS (only 1+1 system types) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RST Trib Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RST Radio Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BER-RSPI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IDU Status & Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ODU Status and Configuration window (for ODU NPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATPC function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ext EOW Status & Config window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Download menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FTP Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Banks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edit NE menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copy command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.26 6.29 6.29 6.32 6.36 6.40 6.45 6.52 6.53 6.57 6.60 6.63 6.66 6.68 6.69 6.70 6.75 6.84 6.85 6.85 6.86 6.86 6.87 6.87 6.87 6.89 6.91 6.91
I-2
INDEX
6.5.5.3.2 Paste command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.93 6.6 6.6.1 6.6.1.1 6.6.1.2 6.6.2 6.6.2.1 6.6.2.2 6.6.2.3 6.6.3 6.6.4 6.6.4.1 6.6.4.2 6.6.4.3 6.6.4.4 6.6.4.5 6.6.5 6.7 6.7.1 6.7.1.1 6.7.1.2 6.7.1.3 6.7.1.4 6.7.1.5 6.7.1.6 6.7.2 6.7.3 6.8 6.8.1 6.8.2 6.8.2.1 6.8.2.2 6.8.2.3 6.8.3 6.8.3.1 6.8.3.2 6.8.3.3 6.8.4 6.8.5 6.9 6.10 6.11 Alarms menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.97 Functional menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.97 STM-1 Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.98 AUX and Control Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.100 Physical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.102 IDU Maintenance Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.103 ODU Maintenance Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.104 System Maintenance Physical Alarms window (only (1+1) S.T.) . . . . . . . . . . . . . . . . . . . . . 6.106 Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.107 Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.108 Critical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.108 Minor Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.109 Major Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.111 Warning Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.112 Test window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.113 TCN menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.113 Measurements menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.115 Performance menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.115 Quality and unavailability parameters (RST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.116 RPS menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.118 RST Trib Side menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.119 RST Radio Side menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.120 RSPI menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.121 BER RSPI menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.123 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.125 RF RX Power REC menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.126 Inventory menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.127 Hw/Sw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.127 User menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.128 IDU unit inventory data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.128 ODU unit inventory data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.129 External EOW unit inventory data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.130 Factory Data menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.130 IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.131 Hardware Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.131 EOW external unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.132 PID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.132 Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.133 SECURITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.133 History menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.134 Alarm list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.134
ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1
7.1 7.2 7.3 7.4 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 Summary alarm signallings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 Alarm signalling leds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.12 Alarms classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.13
I-3
INDEX
LIST OF ACRONYMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1

A.1 Lists of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1
I-4
LIST OF ILLUSTRATIONS
Fig. 2.1 Fig. 3.1 Fig. 3.2 Fig. 3.3 Fig. 3.4 Fig. 3.5 Fig. 3.6 Fig. 4.1 Fig. 4.2 Fig. 5.1 Fig. 5.2 Fig. 5.3 Fig. 5.4 Fig. 5.5 Fig. 5.6 Fig. 5.7 Fig. 5.8 Fig. 5.9 Fig. 5.10 Fig. 5.11 Fig. 5.12 Fig. 5.13 Fig. 5.14 Fig. 6.1 Fig. 6.2 Fig. 6.3 Fig. 6.4 Fig. 6.5 Fig. 6.6 Fig. 6.7 Fig. 6.8 Fig. 6.9 Fig. 6.10 Fig. 6.11 Fig. 6.12 Fig. 6.13 Fig. 6.14 Fig. 6.15 Fig. 6.16 Fig. 6.17 Fig. 6.18 Fig. 6.19 Fig. 6.20 Fig. 6.21 Fig. 6.22 Fig. 6.23 Fig. 6.24 Fig. 6.25 Fig. 6.26 Fig. 6.27 IDU optical unit front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Artificial respiration procedure (1/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Artificial respiration procedure (2/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Artificial respiration procedure (3/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Artificial respiration procedure (4/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Elasticized band and coiled cord . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Installation of plug-in software (1/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Installation of plug-in software (2/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Download procedure via FTP (1/9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Download procedure via FTP (2/9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 Download procedure via FTP (3/9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 Download procedure via FTP (4/9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Download procedure via FTP (5/9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Download procedure via FTP (6/9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5 Download procedure via FTP (7/9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5 Download procedure via FTP (8/9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6 Download procedure via FTP (9/9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6 Procedura di download per ODU NPL (1/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7 Procedura di download per ODU NPL (2/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7 Procedura di download per ODU NPL (3/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8 Procedura di download per ODU NPL (4/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8 Procedura di download per ODU NPL (5/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8 Example of map with SRA series 3 equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13 Operative menu of SRA series 3 equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.15 Status and Config menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.26 Equipment menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.29 System Status window (1+0 system type) - example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.30 System Status window (1+1 system types) - example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.30 System Configuration window (1+1 system type with electrical IDU) . . . . . . . . . . . . . . . . . . . . . . . 6.32 System Configuration window (1+1 system type with optical IDU). . . . . . . . . . . . . . . . . . . . . . . . . 6.33 System Configuration window (1+0 system type with electrical IDU) . . . . . . . . . . . . . . . . . . . . . . . 6.33 Window for the configuration of the System type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.33 IDU type configuration (example: IDU1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.34 ODU type configuration (example: ODU1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.34 External EOW configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.34 Window for B1 Threshold for SD Alarm (Trib Side) selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.35 Window for B1 Threshold for SD Alarm (Radio Side) selection . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.35 ALS procedure enabling/disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.35 Window for Way-Side Channel Mode enabling/disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36 Window for User Ch Mode configuration (F1 Byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36 Enabling/disabling of E1 byte management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36 Switches Status & Config window ((1+1) Hetero Freq DTI w/o MST)) . . . . . . . . . . . . . . . . . . . . . . 6.37 Switches Status & Config window ((1+1) Hetero Freq STI w/o MST)) . . . . . . . . . . . . . . . . . . . . . . 6.37 Switches Status & Config window ((1+1) Hot Stby DTI w/o MST)) . . . . . . . . . . . . . . . . . . . . . . . . 6.37 Switches Status & Config window ((1+1) Hot Stby STI w/o MST)). . . . . . . . . . . . . . . . . . . . . . . . . 6.38 Switch Mode selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38 MS-AIS Insertion Trib Side configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.39 MS-AIS Trib Side Management configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.40 MS-RDI Trib Side Management configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.40
I-5
Fig. 6.28 Fig. 6.29 Fig. 6.30 Fig. 6.31 Fig. 6.32 Fig. 6.33 Fig. 6.34 Fig. 6.35 Fig. 6.36 Fig. 6.37 Fig. 6.38 Fig. 6.39 Fig. 6.40 Fig. 6.41 Fig. 6.42 Fig. 6.43 Fig. 6.44 Fig. 6.45 Fig. 6.46 Fig. 6.47 Fig. 6.48 Fig. 6.49 Fig. 6.50 Fig. 6.51 Fig. 6.52 Fig. 6.53 Fig. 6.54 Fig. 6.55 Fig. 6.56 Fig. 6.57 Fig. 6.58 Fig. 6.59 Fig. 6.60 Fig. 6.61 Fig. 6.62 Fig. 6.63 Fig. 6.64 Fig. 6.65 Fig. 6.66 Fig. 6.67 Fig. 6.68 Fig. 6.69 Fig. 6.70 Fig. 6.71 Fig. 6.72 Fig. 6.73 Fig. 6.74 Fig. 6.75 Fig. 6.76 Fig. 6.77 Fig. 6.78 Fig. 6.79 Fig. 6.80 Fig. 6.81 Fig. 6.82
HBER Management configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link Identification window (1+0 system type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link Identification window (1+1 system types). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window for the J0 Management Tributary Side selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window for the J0 Expected Tributary Side insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window for the J0 Inserted Tributary Side insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window for the AIS Insertion enabling/disabling (Tributary Side) . . . . . . . . . . . . . . . . . . . . . . . . . Window for the TIM Activation Interval insertion (Tributary Side) . . . . . . . . . . . . . . . . . . . . . . . . . Window for the TIM Disactivation Interval insertion (Tributary Side) . . . . . . . . . . . . . . . . . . . . . . . Window for the J0 Management Radio Side selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window for the J0 Expected Radio Side insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window for the J0 Inserted Radio Side insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window for the AIS Insertion enabling/disabling (Radio Side) . . . . . . . . . . . . . . . . . . . . . . . . . . . Window for the TIM Activation Interval insertion (Radio Side). . . . . . . . . . . . . . . . . . . . . . . . . . . . Window for the TIM Disactivation Interval insertion (Radio Side) . . . . . . . . . . . . . . . . . . . . . . . . . Performance Monitoring Config window (1+1 system types). . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Monitoring Config window (1+0 system type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX Field Threshold (TLTS1) insertion window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RX Field Threshold (RLTS1) insertion window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurazione di RX Field Threshold (RLTS2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RPS 15 performance monitoring configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RPS Day performance monitoring configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling/disabling of Suspect Running Window RPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RST Trib 15 performance monitoring configuration (example: IDU1) . . . . . . . . . . . . . . . . . . . . . . RST Trib Day performance monitoring configuration (example: IDU1) . . . . . . . . . . . . . . . . . . . . . RST Radio 15 performance monitoring configuration (example: IDU1) . . . . . . . . . . . . . . . . . . . . RST Radio Day performance monitoring configuration (example: IDU1) . . . . . . . . . . . . . . . . . . . RSPI 15 performance monitoring configuration (example: IDU1) . . . . . . . . . . . . . . . . . . . . . . . . . RSPI Day performance enabling/disabling (example: IDU1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Suspect Running Window RST Trib (IDU1) configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Suspect Running Window RST Radio (IDU1) configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Suspect Running Window RSPI (IDU1) configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCN Setting > IDU1 menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCN Setting RPS window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for 15 Trib Switch Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the de-activation value for 15 Trib Switch Alarm . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for Day Trib Switch Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for 15 Dem Switch Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the de-activation value for 15 Dem Switch Alarm . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for Day Dem Switch Alarm . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for 15 Stby Switch Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the de-activation value for 15 Stby Switch Alarm . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for Day Stby Switch Alarm . . . . . . . . . . . . . . . . . . . . . . . . . TCN Setting RST Trib window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for 15 SES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the de-activation value for 15 SES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for Day SES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for 15 BBE Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the de-activation value for 15 BBE Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for Day BBE Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for 15 ES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the de-activation value for 15 ES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for Day ES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCN Setting RST Radio window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the activation value for 15 SES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.40 6.41 6.41 6.41 6.42 6.42 6.43 6.43 6.43 6.44 6.44 6.44 6.45 6.45 6.45 6.46 6.46 6.47 6.47 6.47 6.48 6.48 6.48 6.49 6.49 6.49 6.50 6.50 6.50 6.51 6.51 6.51 6.52 6.53 6.54 6.54 6.54 6.55 6.55 6.55 6.55 6.56 6.56 6.57 6.57 6.57 6.58 6.58 6.58 6.59 6.59 6.59 6.59 6.60 6.60
I-6
Configuration of the de-activation value for 15 SES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.60 Configuration of the activation value for Day SES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.61 Configuration of the activation value for 15 BBE Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.61 Configuration of the de-activation value for 15 BBE Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.61 Configuration of the activation value for Day BBE Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.62 Configuration of the activation value for 15 ES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.62 Configuration of the de-activation value for 15 ES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.62 Configuration of the activation value for Day ES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.62 TCN Setting RSPI window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.63 Configuration of the activation value for 15 RLTS1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.63 Configuration of the de-activation value for 15 RLTS1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.63 Configuration of the activation value for Day RLTS1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.64 Configuration of the activation value for 15 TLTS1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.64 Configuration of the de-activation value for 15 TLTS1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.64 Configuration of the activation value for Day TLTS1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.65 Configuration of the activation value for 15 RLTS2 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.65 Configuration of the de-activation value for 15 RLTS2 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.65 Configuration of the activation value for Day RLTS2 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.65 TCN Setting BER-RSPI window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.66 Configuration of the activation value for 15 SES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.66 Configuration of the de-activation value for 15 SES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.66 Configuration of the activation value for Day SES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.67 Configuration of the activation value for 15 ES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.67 Configuration of the de-activation value for 15 ES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.67 Configuration of the activation value for Day ES Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.67 External Setting window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.68 Window for the insertion of Alarm 1 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.68 Polarity Alarm 1 configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.68 Window for the insertion of Description Remote Control 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.69 Unit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.69 IDU1 Status & Configuration window (optical IDU, ODU SRA) . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.70 IDU2 Status & Configuration window (optical IDU, ODU NPL) for LCT . . . . . . . . . . . . . . . . . . . . . 6.70 Local Loop-Back enabling/disabling window (Tributary Side) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.71 Laser Forcing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.71 Laser Restart configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.72 Local Loop-Back enabling/disabling window (Radio Side) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.72 Modulator Mode configuration window (electrical IDU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.73 IF TX Level configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.73 ATPC Management configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.74 ATPC Mode configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.74 ODU Status & Configuration window (ODU Power-up: Running). . . . . . . . . . . . . . . . . . . . . . . . . . 6.75 ODU Status & Configuration window (ODU Power-up: Completed). . . . . . . . . . . . . . . . . . . . . . . . 6.75 Configuration of Freq Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.76 Freq Plan Fail alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.76 Freq Plan Activation enabling/disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.77 Configuration of TX Freq Ch#1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.77 Configuration of First Channel ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.78 Configuration of Last Channel ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.78 Configuration of RF Channel ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.78 Configuration of TX Freq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.78 Configuration of RX Freq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.79 Configuration of ATPC Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.80 Configuration of ATPC Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.80 Configuration of TX Power Pmin Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.80 Configuration of ATPC Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.81
I-7
Configuration of ATPC Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.81 Configuration of Squelch Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.81 Configuration of Comp IF Cable Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.82 Start of cable compensation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.82 Positive end of the cable compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.83 Negative end of the cable compensation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.83 Ext EOW Status & Config window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.85 Phone Number configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.85 Software Download menu (for ODU SRA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.85 Software Download menu (for ODU NPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.85 IDU Software Banks window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.86 ODU1 Software Banks window (ODU NPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.86 Network menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.87 NE Parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.88 NE Parameters window (write mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.88 Window for IP address value insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.88 Window for Net Mask value insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.88 Routing Table window (with not modifiable fields) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.89 Routing Table window (with modifiable fileds) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.89 Window for the selection of the interface type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.90 Window for the insertion of the Destination Network routing entry . . . . . . . . . . . . . . . . . . . . . . . . 6.90 Window for the insertion of Gateway routing entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.90 Example of Routing Entry window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.90 Edit NE menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.91 Copy NE procedure (1/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.91 Copy NE procedure (2/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.92 Copy NE procedure (3/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.92 Copy NE procedure (4/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.92 Copy NE procedure (5/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.93 Paste NE procedure (1/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.93 Paste NE procedure (2/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.93 Paste NE procedure (3/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.94 Paste NE procedure (4/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.94 Alarms menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.97 Functional menu (1+1 system types). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.97 Channel 1 menu (1+1 system types) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.98 Functional menu (1+0 system type). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.98 STM-1 Payload Functional Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.98 AUX and Control Channel Functional Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.101 Equipment User Physical Alarms window (1+0 system type) . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.102 Equipment User Physical Alarms window (1+1 system types) . . . . . . . . . . . . . . . . . . . . . . . . . . 6.102 IDU 1 Maintenance Physical Alarms window ((1+1) system type) . . . . . . . . . . . . . . . . . . . . . . . 6.103 ODU Maintenance Physical Alarms window (ODU SRA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.104 ODU Maintenance Physical Alarms window (ODU NPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.105 System Maintenance Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.106 Station Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.107 Severity Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.108 Critical Alarms window ((1+0) system type, ODU NPL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.108 Critical Alarms window ((1+1) HSBY STI system type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.109 Critical Alarms window ((1+0) ODU SRA system types) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.109 Minor Alarms window ((1+1) system type). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.109 Minor Alarms window ((1+0) system type). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.110 Major Alarms ((1+1) DTI system types with optical IDU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.111 Severity Alarms window - MAJOR (system type 1+1 STI, electrical IDU) . . . . . . . . . . . . . . . . . . 6.111 Warning Alarms window ((1+1) system types) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.112
I-8
Fig. 6.193 Fig. 6.194 Fig. 6.195 Fig. 6.196 Fig. 6.197 Fig. 6.198 Fig. 6.199 Fig. 6.200 Fig. 6.201 Fig. 6.202 Fig. 6.203 Fig. 6.204 Fig. 6.205 Fig. 6.206 Fig. 6.207 Fig. 6.208 Fig. 6.209 Fig. 6.210 Fig. 6.211 Fig. 6.212 Fig. 6.213 Fig. 6.214 Fig. 6.215 Fig. 6.216 Fig. 6.217 Fig. 6.218 Fig. 6.219 Fig. 6.220 Fig. 6.221 Fig. 6.222 Fig. 6.223 Fig. 6.224 Fig. 6.225 Fig. 6.226 Fig. 6.227 Fig. 6.228 Fig. 6.229 Fig. 6.230 Fig. 6.231 Fig. 6.232 Fig. 6.233
Warning Alarms window ((1+0) system type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.112 TEST window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.113 TCN menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.113 IDU 1 TCN Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.113 IDU 2 TCN Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.114 Measurements menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.115 Performance menu - IDU1 (S.T. 1+1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.115 Performance menu - IDU2 (S.T. 1+1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.115 RPS menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.118 RPS Performance Monitoring - Quarter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.118 RPS Performance Monitoring - Day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.118 RST Trib Side menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.119 Performance Monitoring (RST Trib Side) window - Quarter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.119 Performance Monitoring (RST Trib Side) window - Day. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.119 RST Radio Side menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.120 Performance Monitoring (RST Radio Side) window - Quarter . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.120 Performance Monitoring (RST Radio Side) window - Day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.121 RSPI menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.121 Performance Monitoring (RSPI) window - Quarter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.122 Performance Monitoring (RSPI) window - Day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.122 BER-RSPI menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.123 Performance Monitoring (BER-RSPI) window - Quarter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.123 Performance Monitoring (BER-RSPI) window - Day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.124 Event Presence Summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.124 Unit Measures window (ODU SRA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.125 Unit Measures window (ODU NPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.125 RF RX Power REC menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.126 Inventory menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.127 Hardware & Software Inventory window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.127 User menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.128 User Inventory window (1+1 system type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.128 FIELD EDITING window for IDU User Inventory (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.129 ODU User Inventory window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.129 Finestra FIELD EDITING per User Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.129 EOW User Inventory window (1+0 system type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.130 FIELD EDITING window for EOW User Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.130 Factory Data menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.130 Factory Data window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.131 Key Factory Data window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.131 External EOW Factory Data window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.132 ODU PID window (S.T. (1+1)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.132
I-9
LA
PA
I-10 SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002
LIST OF TABLES
LIST OF TABLES
Tab. 1.1 Tab. 2.1 Tab. 6.1 Tab. 6.2 Tab. 6.3 Tab. 6.4 Tab. 6.5 Tab. 6.6 Tab. 6.7 Tab. 6.8 Tab. 6.9 Tab. 6.10 Tab. 6.11 Tab. 6.12 Tab. 6.13 Tab. 6.14 Tab. 6.15 Tab. 6.16 Tab. 6.17 Tab. 7.1 Tab. 7.2 Tab. 7.3 Tab. 7.4 Tab. 7.5 Tab. 7.6 Tab. 7.7 Features of SVR 3.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 User classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 Configurations stored in the hardware key EEPROM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5 Structure of the SRA series 3 operative menu (1+0 system type, ODU SRA) . . . . . . . . . . . . . . . . 6.16 Structure of the SRA series 3 operative menu (1+0 system type 1+0, ODU NPL). . . . . . . . . . . . . 6.18 Structure of the SRA series 3 operative menu (1+1 system type, ODU SRA) . . . . . . . . . . . . . . . . 6.20 Structure of the SRA series 3 operative menu (1+1 system type, ODU NPL) . . . . . . . . . . . . . . . . 6.22 Default system configuration (ODU SRA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.26 Default system configuration (ODU NPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.28 RSPI parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.46 Default values for TCN parameters: 15 min ON/OFF (Single Mode) . . . . . . . . . . . . . . . . . . . . . . . 6.53 Default values for TCN parameters: 24h ON (Cyclic Mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.53 Access to the Loop-Back parameters (tributary side). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.71 Laser operative rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.72 Access to the Loop-Back parameters (radio side) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.72 ATPC setting rules (ODU SRA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.74 ATPC management rules (ODU NPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.79 ATPC threshold values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.84 Configurations copied by Copy NE function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.95 Alarm signallings description and severity ((1+0) w/o MST system type) . . . . . . . . . . . . . . . . . . . . 7.2 Alarm signallings description and severity ((1+1) Hetero Freq STI w/o MST system types) . . . . . . 7.4 Alarm signallings description and severity ((1+1) Hetero Freq DTI w/o MST system types) . . . . . . 7.6 Alarm signallings description and severity ((1+1) Hot Stby DTI w/o MST system types) . . . . . . . . . 7.8 Alarm signallings description and severity ((1+1) Hot Stby STI w/o MST system types) . . . . . . . . 7.10 LEDs indications on IDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.12 Signalling of manual operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.13
I-11
LIST OF TABLES
LA
PA
I-12 SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002
1 - FOREWORD
1 FOREWORD
1.1 Subject and purpose of the manual
This OMN manual provides the necessary instructions for the management, via PC, of the SRA series 3 radio equipment (SVR 3.5.0). The main features of the System Version Release 3.5.0 are listed in the following table (Tab. 1.1). Tab. 1.1 System configuration: Features of SVR 3.5.0 1+0 w/o MST 1+1 Hot Stand-by w/o MST 1+1 Hetero frequency w/o MST 1+1 Hot Stand-by w/o MST Double Tributary Interface 1+1 Hetero frequency w/o MST Double Tributary Interface Tributary throughput: 155.520 Mbit/s Digital service channels: 2.048 Mbit/s (G.703) 64 Kbit/s (V.11 or G.703) Voice channels 1x64 kbit/s channel for E1: Omnibus call inside a SRA Series 3 subnetwork Selective call inside a SDH subnetwork EOW external unit (64 Mbit/s) STM-1 electrical (ITU-T G.703) STM-1 optical (ITU-T G.957 S-1.1) 15 GHz: 14.5 - 15.35 18 GHz: 17.7 - 19.7 23 GHz: 21.2 - 23.6 26 GHz: 24.5 - 26.5 18 GHz 23 GHz 26 GHz 38 GHz 28 Mhz, 56 Mhz 32 TCM 128 QAM SRA NPL Radio side: trib RSOH level Trib side: trib physical interface level RX radio side RX tributary side TX radio side
Equipment traffic capacity:
Base-band interfaces: Operating frequency bands (ODU SRA)
Operating frequency bands (ODU NPL)
Channels spacing Modulation type ODU type Available loop-backs: 1+1 non hitless protection
1-1
1 - FOREWORD
Tab. 1.1 ATPC
Features of SVR 3.5.0 (Cont.) 2 ATPC levels (Pnom, Pnom-8) Range 8 dBm Linearized for ODU NPL TX and RX frequency Transmission power (ATPC) Link identification code Alarm parameters Remote controls Local loop-back (from LCT) User channel (byte F1) User channel (byte E1) ALS (Automatic Laser Shutdown) Laser restart Received power ODU transmitted power RF RX power BER on radio side Performance Events Report of inventory data Diagnostics Input of station alarms (max. 4) System alarms restitution (max.8) Remote station alarms restitution (max.2) Signalling of alarm threshold crossing InDoor Unit OutDoor Unit External EOW Unit LCT/Net Viewer and Net Builder RIP Disabling Option by Q interface IP address Static routing tables Net-mask F interface Q interface S23 of SOH (64 kbit/s) DCC of SOH (192 kbit/s) Selection of the active memory bank Software download from local PC or via FTP
Configuration of the operative parameters:
Measures:
Recordings:
Alarms management:
Units:
User interface: RIP features Configuration of TCP/IP connection:
Management interfaces
Management of Controller unit: Security User and factory data storage Hardware backup key ODU heater unit (optional)
1-2
1 - FOREWORD
1.2 Testing and warranty

Refer to the contract clauses for the information about the subject matter.
1.3 Responsibility
Refer to the contract clauses for the information about the subject matter. Besides it is necessary to observe that: The manufacturer declines all responsibilities deriving from the incorrect or wrong use of the equipment, from the utilization of unauthorized parts and circuit, component and system software violations. The responsibility for the application of safety rules and use prescriptions is entrusted to the technical personnel responsible for the various activities, which has to make sure that the authorized personnel is qualified to perform the requested activity and has the required knowledge.
1.4 Manuals related to SRA series 3

For the SRA series 3 equipment, the following manuals are available: Installation and Test Manual (ITMN) It contains the necessary informations for the equipment installation, the commissioning and the maintenance. Operating Manual (OMN) It contains the necessary informations for the equipment configuration and control by means of PC. LCT (OMN) It contains the necessary informations for the configuration and control, by means of a service PC, of a SRA series 3 link and of the relative equipments. Net Viewer (OMN) It contains the necessary informations for the configuration and control, by means of a network PC, of a SRA series 3 network and of each network equipments.
All the manuals are available in English; they can be also provided in other languages, depending on the contract clauses.
1-3
1 - FOREWORD
LA
PA
1-4 SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002
2 - EQUIPMENT MANAGEMENT
2 EQUIPMENT MANAGEMENT
2.1 Introduction
This manual describes the graphic user interface to manage the SRA series 3 equipment. The same graphic interface is specified for the LCT and the telecommunication network management. The configuration of a NE can be managed either locally by the Local Terminal or remotely by the EM. The user interface of the EM is aware of the constrains related to the System Type and doesnt allow any illegal configuration. The NE Controller is aware of these constrains too and checks the configurations imposed either by the Local Terminal or by the EM. In order to avoid problems due to these duplicated checks, the remote configuration of a NE shall be managed by the following steps: the EM shall write the right System Type value for the NE in the NE Controller; the NE Controller shall use this information to set the NE expected configuration to a default configuration containing all the mandatory units and to program the actual slave units to perform the functionalities implied by the System Type; the EM can then modify the configuration of the optional units and, if necessary, the type of the mandatory units.
The EM doesnt allow to remove a mandatory unit without a previous change in the System Type.
2.1.1
Local Craft Terminal (LCT)

The LCT is a local personal computer which the operator uses to dialogue with the SRA series 3 equipment. By means of LCT it is possible to modify and configure up to three SRA series 3 at the same time. The modification of the IP address for a specific SRA series 3 equipment is allowed only on the NE directly connected to the PC/LCT. It is used for the following activities: lining up, in order to start in service and check the equipment before its connection to the network; operation and maintenance, to allows the local access to the operator for the monitoring of the system and, at the same time, to modify the system configuration, if necessary. If the connection between the network manager and the SRA series 3 equipment is not possible (for hardware or software troubles), however LCT allows the system management.
2-1
2.1.2
LCT connection to the equipment

The connection between system and the local PC takes place by means of a RS-232 V.24/V.28 interface. Its physical access is located on the main board in the IDU unit and allows a local access to the system. For the connection between LCT and SRA series 3 equipment, a D-9 female connector is used to implement the RS-232 interface. Q interface is used only by NetViewer program.
Fig. 2.1
IDU optical unit front panel
By means of the local terminal, it is possible to set and modify the following parameters: NE address; the system type, stored in the EEPROM key; the type of the equipped units; the Modulator Mode; the loopbacks.
2-2
2.2 User classes and security

2.2.1 User classes
The user classes features are the following ones: Tab. 2.1 User classes Class Name Anonymous Admin User Read Write User Read Only User Class Rights Transparent Read&Write + (2) rights Password modification + (3) rights Normal read and write operations Read only operations
The Anonymous user class is not present when NetViewer is used to manage the equipment. The user login class restricts the operations allowed to the user, as is hereafter specified: read only users can only read, but not change any system configuration; in addition to the previous class rights, read write users can also write the read/write the configuration parameters, but they cannot modify the password of any user class; in addition to the previous class rights, administrator users can also modify the passwords for the administrator, normal and readonly user class.
Before starting the operations with the NE, either the Local Terminal Operator or the EM Application shall log onto the NE, giving to the NE controller the user login class and the password for that class. Transmission of the protocol passwords shall be cryptographed. The Local Terminal operator must enter the user login class at which he wants to operate and the relevant password. Therefore the identity of the local operator is unknown in the NE: the NE controller knows only the login class of the operator.
2.2.2
NE Access Control Management

Basically the NE concurrent access control is achieved by allowing no more than one user with user login class 1, 2 or 3 to be logged onto the NE at the same time. In this way only one user at a time can modify the NE configuration. If an user attempts to log onto the NE with user login class 1, 2 or 3 while another user with writing rights is already logged, the log on is still accepted, but the rights of the new user are restricted to those of user login class 4. The NE controller shall emit an event whenever an user with user login class 1, 2 or 3 does login or logout onto the NE. In order to change the user login class, an user must first disconnect and then reconnect during the login with the new user class.
2-3
LA
PA
3 - SAFETY RULES AND PRECAUTIONS
3 SAFETY RULES AND PRECAUTIONS

3.1 First aid for electric shocks
Do not touch the patient with bare hands until the circuit has been opened. Open the circuit by switching the line switches off. If that is not possible, protect yourself with dry material and free the patient from the conductor.
3.2 Artificial respiration

It is important to start mouth to mouth resuscitation at once and seek doctor help immediately. The mouth to mouth method to apply is described here below. Mouth to mouth resuscitation method 1. Lay the patient supine with his arms parallel with the body. If the patient is laying on a inclined plane, make sure that his stomach is slightly lower than his chest. Open the patients mouth and check that there are no extraneous bodies in his mouth (dentures, chewing-gum, etc.). Kneel beside the patient level with his head. Put a hand under the patients head and one under his neck (Fig. 3.1). Lift the patients head and let it recline backwards as far as possible.
2.
Fig. 3.1
Artificial respiration procedure (1/4)
3.
Shift the hand from the patients neck to his chin: place your thumb between his chin and his mouth, the index along his jawbone, and keep the other fingers closed together (Fig. 3.2). While performing these operations take a good supply of oxygen by taking deep breaths with your mouth open.
Fig. 3.2
4.
With your thumb between patients chin and mouth keep his lips together and blow into his nasal cavities (Fig. 3.3).
3-1
Fig. 3.3
5.
While performing these operations, observe if the patients chest rises (Fig. 3.4). If not, it is possible that his nose is blocked: in that case, open the patients mouth as much as possible by pressing on his chin with your hand, place your lips around his mouth and blow into his oral cavity. Observe if patients chest heaves. This second method can be used instead of the first even when the patients nose is not obstructed, provided his nose is kept closed by pressing the nostrils together by using the hand you were holding his head with. The patients head must be kept sloping backwards as much as possible.
Fig. 3.4
6.
Start with ten rapid expirations, hence continue at a rate of twelve/fifteen expirations per minute. Go on like this until the patient has regained consciousness, or until a doctor has ascertained his death.
3.3 Treatment of burns

This treatment should be used after the patient has regained consciousness. It can also be employed while the artificial respiration is being applied (in this case, there should be at least two persons present). Do not attempt to remove his clothing from the burnt parts. Apply dry gauze on the burns. Do not apply ointments or other oily substances.
3-2
3.4 Safety labels

When the assemblies and the units are provided with the following labels: Fig. 3.5 Label
It is MANDATORY to observe the precautionary measures stated. The LASER label warns that the power transmitted by the LASER might be dangerous to the eyes. An antistatic protection is supplied for reducing the risk of damage to electrostatic sensitive devices. It consists of the following items: Fig. 3.6 Elasticized band and coiled cord
the elasticized band is to be worn around the wrist; the coiled cord is to be connected to the elasticized band and to the corresponding socket on the rack.
3-3
LA
PA
4 - INSTALLATION OF SOFTWARE PLUG-IN
4 INSTALLATION OF SOFTWARE PLUG-IN

4.1 Overview
The application program for the control and management of SRA series 3 equipment is a plug-in of the program for the management of SRA series 3 network/link. The Net Viewer/LCT program is able to acknow and, then, manage only the radio equipments, whose plug-in has been previously installed. To install the plug-in software, the Net Viewer/LCT program must be already installed; otherwise, first it is necessary to install the Net Viewer/LCT program and, only after, install the plug-in software. The installation of plug-in software determines: the possibility for Net Viewer/LCT program to manage SRA series 3 radio equipment; the addition of the help, relative to SRA series 3 management application, to the Help menu of Net Viewer/LCT program.
For more informations about the Net Viewer and LCT programs, refer to the related OMN Manual.
4.2 Installation procedure

If the Net Viewer/LCT program was already running, it is necessary to exit. Start the installation of SRA series 3 plug-in software (file setup.exe). The program is of auto-start type (that is, it starts by itself at CD-ROM inserting). The Welcome window opens on the screen (Fig. 4.1). Click on Next button to start the installation. At the end of installation, the Setup Complete window (Fig. 4.2) opens. Click on Finish button to close and exit. Restart the program to load the plug-in.
4-1
4 - INSTALLATION OF SOFTWARE PLUG-IN
Fig. 4.1
Installation of plug-in software (1/2)
Fig. 4.2
Installation of plug-in software (2/2)
4-2
5 - DOWNLOAD OF CONTROLLER UNIT SOFTWARE
5 DOWNLOAD OF CONTROLLER UNIT

SOFTWARE
5.1 Overview
The Controller unit is a microprocessor unit provided with a management program, which resides on flash memories. There are two flash memories; called Bank 1 and Bank 2: one is active, the other is in stand-by state. This assures the redundancy of the management software and acts when the active bank fails. The Controller unit is provided with the managemernt program already installed. It is possible to update or re-load the content of the memory bank (EEPROM) by means of FTP (applicative of the TCP/IP protocol stack), using a service PC connected to SRA series 3 network/limk and by means of the command from equipment menu in Net Viewer / LCT program. The download via FTP doesnt cause any interruption in the operation of Controller unit, which is always on-line. The downloading procedure is the same for 1+0 and 1+1 equipment types. As regards IDU unit, in case of (1+1) equipment type, the software download is executed on the master IDU, which automatically will transfer this software to the slave IDU. As regards ODU NPL, in case of (1+1) equipment type, the software download must be executed twice, one for ODU Master and one for ODU Slave (order doesnt matter). The software download maintains the pre-existent configurations. If the new software adds new configurations, these assume their default value only if this is compatible with the configurations already present on the equipment; otherwise, the new configurations will assume a value coherent with the pre-existent configurations. The software download can be executed both locally and remotely: Locally: Remotely: from LCT (F interface) from LCT via modem (F interface) from Net Viewer (Q interface)
Download operations are faster if executed by interface Q (LAN EThernet). During a software download made via F interface (both locally and remotely), each time the user commands a switch of the flash bank, he must disactivate the dial-up connection and, then, restore it (besides to run the TNMP connection again).
5-1
Using the FTP default, the download, even if correctly completed, ends displaying an error message: Cannot get remote directory listing. To avoid this, select the Dont use extra Flag check box in the FTP preferences in List View submenu.
5.2 Download via FTP (for IDU unit)

To be able to execute the software download, the PC with the file to be transferred must be switched on and connected to SRA series 3 network/link. Start the application for the equipment management on the service PC. Activate the connection to the interested SRA series 3 equipment using the Admin User class. Select Status and Config -> Software Download -> IDUs -> Software banks in the operative menu. Check that the memory bank on which the download is going to be executed is the stand-by one; otherwise, command the switching between the two memory banks. Start the FTP Client program, selecting Status and Config -> Software Download -> IDUs -> FTP Transfer in the operative menu. Insert the IP address of SRA series 3 equipment on which the download has to be executed in the Hostname field of the Connect window (Fig. 5.1), and then click OK.
Fig. 5.1
Download procedure via FTP (1/9)
Set the following parameters in the Connection Information window (Fig. 5.2): Username: adminuser; Password: sysmanager; Startup Directory: \.
5-2
and click on OK to activate the connection to the Controller unit. Fig. 5.2 Download procedure via FTP (2/9)
Select, under Local, the unit and the directory where the file with the new software for the Controller unit is stored: the system.bin file must appear in the Files box (Fig. 5.3). Select the file system.bin and set Binary as transfer modality in the Transfer box, in the upper part of the FTP window, and command the download operation acting on the Copy button (Fig. 5.3). After the download start, the information about the status of progressing of the operation appears in the status bar (bottom of the window).
Fig. 5.3
At the end of operation, the file system.bin is shown in the Files box under Remote (Fig. 5.4).
5-3
Fig. 5.4
Save the profile set for the download with the SRA 3 FTP name, selecting Save As in File menu (Fig. 5.5).
Fig. 5.5
In case of successive downloads, also on different SRA series 3 equipments, it is not necessary to set the connection parameters again (except for the IP address), because it is sufficient to recall the SRA series 3 FTP profile in the initial window Connect of the FTP Client program (Fig. 5.1). Exit from the FTP Client program.
5-4
Select Status and Config -> Software Download -> IDU -> Software banks in the operative menu. The IDU Software Banks (Fig. 5.6) opens.
Fig. 5.6
Select the Copy to Flash command to copy the content of the RAM in the inactive Flash memory. The string Copy in progress with the indication of the percentage of the operation in progress is displayed (Fig. 5.7).
Fig. 5.7
At the end of the copy, the indication of the checksum of the stand-by bank is changed. Now on the stand-by bank, there is the new software for the Controller unit (Fig. 5.8). Select the Switch to Stand-by Bank to switch between the two memory banks. The active bank will become the stand-by Bank and viceversa (Fig. 5.9). Then the active bank will contain the updated version of the control software. Select Banks Alignment to align to content of the two memory banks.
After the Switch Bank operation, the TNMP connection goes down. The map closes and a new work session must be opened by a new login.
5-5
Fig. 5.8
Fig. 5.9
5-6
5.3 Download via FTP (for ODU NPL)

The procedure of software download to ODU NPL is generally the same as for the IDU unit (par. 5.2), but with the following differences: the procedure is activated by the Status and Config -> Software Download -> ODU1 (or ODU2) -> Software banks menu item. the name of the related file is odu_npl.hex.
In case of equipment in (1+1) configuration, the software download must be executed twice, one for ODU Master and one for ODU Slave (order doesnt matter, but not at the same time). The sequence of windows for the procedure of software download, in case of ODU NPL, is the following: Fig. 5.10 Procedura di download per ODU NPL (1/5)
Fig. 5.11
Procedura di download per ODU NPL (2/5)
5-7
Fig. 5.12
Fig. 5.13
Fig. 5.14
5-8
6 - GUIDE TO USE OF SRA SERIES 3 MANAGEMENT PROGRAM
6 GUIDE TO USE OF SRA SERIES 3

MANAGEMENT PROGRAM
6.1 Overview
This document describes the user interface and the commands for the configuration and control of the operative status of the SRA series 3 radio equipment. SRA series 3 is a series of STM-1 wireless systems for point-to-point applications, using an high frequency indoor-outdoor architecture, designed to transfer ther SDH/SONET signals. SRA Series 3 radio equipment is built up by: one or two indoor shelves (IDU, indoor unit), providing the base band; one or two outdoor equipment (ODU, outdoor unit), containing RF devices, connected with the IDU through an IF (Intermediate Frequency) cable; an external EOW SRA L (that can be equipped on all the system types); one heater sub-unit on the outdoor equipment (optional).
The IDU deals with all the digital interfaces and performs a first frequency conversion to/from IF signals which are transmitted to the ODU. IDU unit houses an internal EOW card, which supports the broadcast connection function towards all the other stations. The call is activated by a simple buzzer. The ODU performs signal amplification and frequency up/down conversion to/from the millimeter-wave frequency. An external EOW unit allows to execute a selective call (dial-up) towards each network element: this unit is the same used in SRA L systems. The configuration of the indoor shelf and the ways controller card programs the slave cards are different according to the selected system type and configuration. In addition, system provisioning and management are available using local connection via standard RS 232 connection or via 10 Base 2 Ethernet connection. To configure and control the SRA series 3 equipment by means of PC, the Net Viewer/LCT program must be used. The Net Viewer/LCT program, available in Windows NT environment, allows the supervision of networks/links formed by equipments of different type. The specific application program for SRA series 3 equipment is a plug-in, which adds to Net Viewer/LCT program the functionality to manage this type of radio equipment. For the modalities of use of the Net Viewer/LCT program, refer to the related OMN Manual.
6-1
6.2 Software functions

6.2.1 Equipment control and configuration
The application program for SRA series 3 management supports the following functions: system configuration: (1+0) w/o MST, unprotected system; (1+1) Hot Stand-By Single Tributary Interface (STI) w/o MST; (1+1) Hetero Frequency Single Tributary Interface (STI) w/o MST; (1+1) Hot Stand-By Double Tributary Interface (DTI) w/o MST; (1+1) Hetero Frequency Double Tributary Interface (DTI) w/o MST; traffic capacity: STM-1 electrical, STM-1 optical operative functions: equipment configuration and outfitting configuration of the IDU parameters configuration of ODU parameters (for ODU NPL) management of test loops control of equipment configuration and status control of the status of TX and RX sections control of ODU status control of external EOW unit status protection functions ALS functionality (automatic shutdown of the laser source) management of the equipment diagnostics channels management based on TCP/IP protocol management of hardware and software inventory data of the units report of inventory data of the units configuration of the parameters for the connection to SRA series 3 network/link selection/change of the active memory bank storing the unit software for the Controller unit download of Controller unit software measuring and recording of RF RX values of ODU unit measuring and recording and analysis of the reception and transmission system performances measuring and recording of events related to the equipment operation backup of the equipment configuration data by means of the hardware key RIP disabling option by Q-interface BER threshold crossing notification.
The communication services present on the SRA series 3 equipment are protected in case of fading, modem failure or failure of the RX/TX system.
6-2
6.2.2
EEPROMs management
The IDU unit is provided with two different system EEPROMs, to store all the NE configurations: an internal EEPROM an external EEPROM (KEY)
These two EEPROMs usually have the same information stored, but there are some particular cases in which a data mismatch between them shall be managed. These particular cases are: IDU first installation the KEY is blank and shall be overwritten by the internal EEPROM for an easier and faster configuration of different NEs, the copy&paste NE command (implemented in the manager) will be used; consequently, a LCT will be necessary for this operation. IDU replacement the IDU is new and shall assume all the configurations of the replaced IDU; consequently, the KEY shall overwrite the internal EEPROM the IDU replacement operation shall be possible without the support of the LCT. This feature will be supported by inserting the key in the new IDU not feeded yet. Consequently: all the NE configurations are stored into the key the key is a part of its own NE and cannot be used to configure other NEs: if an operator inserts a key already used in another NE, he will change all the network parameters and, consequently, the NE will be not anymore reachable by the Manager. Key fault the key must be replaced; consequently, the new key (blank) will be overwritten from the internal EEPROM.
1. 2.
6.2.3
Key policy
At IDU start-up or when a key is inserted in the system (that is, the key presence is detected), the agent (i.e. CPU) checks the following: 1. 2. if data in the key are valid (if not a key fault is declared) if the data in the key and in the internal EEPROM are identical. If not, two actions are possible: if the key was inserted when IDU was off, then the key data overwrite the IDU data; if the key was inserted when IDU was on, then the key data are overwritten by IDU data.
a) b)
In the above point 2, a mismatch is declared to user by the red led fast blinking. This condition lasts for 20 seconds. After this timeout has expired, the consequent overwriting action is taken without any user confirmation. In case a), payload could be affected by the new data that are running in the IDU and that could have change some important set-up. In case b), payload is not affected by data transferring.
6-3
If the user extracts the key, a warning message appears to inform him of the action. If the hardware key is missing for more than 20 seconds, the connection, both on Q interface and F interface, is lost (LCT/NetViewer).
6-4
6.2.3.1
Tab. 6.1 DATA TYPE
Configurations stored in the key EEPROM

Configurations stored in the hardware key EEPROM FUNCTION NOTES
SYSTEM
System Type ODU1 equipping ODU2 equipping IDU1 equipping IDU2 equipping Station Alarm 1 Description Station Alarm 2 Description Station Alarm 3 Description Station Alarm 4 Description Remote Control 1 Description Remote Control 2 Description NE_IP_ADDRESS NET_MASK ROUTING TABLE 1st ENTRY: INTERFACE ROUTING TABLE 1st ENTRY: DEST NETWORK ROUTING TABLE 1st ENTRY: GATEWAY ROUTING TABLE 2nd ENTRY: INTERFACE ROUTING TABLE 2nd ENTRY: DEST NETWORK ROUTING TABLE 2nd ENTRY: GATEWAY ROUTING TABLE 3rd ENTRY: INTERFACE ROUTING TABLE 3rd ENTRY: DEST NETWORK ROUTING TABLE 3rd ENTRY: GATEWAY ATPC Management IDU 1 DEFAULT Power IDU 1 En/Dis RPS PM Notifing ATPC Management IDU 2 DEFAULT Power IDU 2 Enable MS-AIS insertion_trib side MS-AIS trib enable MS-RDI trib enable HBER enable RPS EN TP 15 RPS EN TP day EOW EXT equipping ALS EN/DIS
DTI system only DTI system only DTI system only
6-5
Tab. 6.1 DATA TYPE
Configurations stored in the hardware key EEPROM FUNCTION NOTES trib side
IDU
ODU NPL
B1 Threshold WS En/Dis F1 INSERT J0 Management TX AIS INS ON TIM TX TIM Activation Interval TIM Disactivation Interval B1 Threshold RX J0 Management RX TIM Activation Interval TIM Disactivation Interval AIS INS ON TIM RX IF OUTPUT LEVEL RST TRIB EN TP 15 RST TRIB EN TP day RST RADIO EN TP 15 RST RADIO EN TP day RSPI EN TP 15 RSPI EN TP day RLTS1 Threshold Setting TLTS1 Threshold Setting RLTS2 Threshold Setting E1 management en/dis LASER FORCING RIP Disable/Enable TCN Threshold On/Off ATPC Management IDU 1 DEFAULT Power IDU 1 ATPC Management IDU 2 DEFAULT Power IDU 2 FREQ_MODE Freq ch #1 first ch ID last ch ID RF_CHN ID ATPC_Control Pmin Setting ATPC_RANGE COMP CABLE MODE
trib side trib side trib side trib side radio side radio side radio side radio side radio side
The value of the transmitted power is mantained only if it is coherent with the constrains related to ATPC range.
6-6
6.2.4
6.2.4.1
1+1 equipment description

Master / Slave definitions
The system in protection mode has two IDUs: Master and Slave. The Master IDU is the IDU with the key inserted. The IDU without the key is always in Slave mode. The IDU with the key is responsible to establish a negotiation with the other IDU. The negotiation will be established in two cases: after SW reset was performed; if a communication loss between the IDUs occurred, after communication with the mate IDU is re-established.
If the IDUs succeed to communicate with each other, the two IDUs try to reach an agreement of their state (who is the Master and who is the Slave). In this case, the IDU with the key will become a Master only after agreement has been achieved. If there is no communication between the IDUs, the IDU with the key will become Master, even without agreement. The design avoids any situation where both IDUs decide to become Master IDUs. In any case of disagreement between the IDUs, Master IDU leaves the Master state (the IDU will do a SW reset and move to Idle state). When the key is plugged out of a working Master IDU, this IDU shall move to a different state called 'Last Master'. In this state, the IDU continues its full Master operation (there is no change in agent operation, except, TNMP session disconnection over Q and F interface occurring after a Timeout of 20 seconds). In Last Master State, the MSTR LED should blink to indicate that this IDU 'used to be' the Master IDU. If a key is re-inserted to an IDU, this IDU returns to 'regular' Master state. If no key is inserted and timeout expires, the NE looses TNMP connection over Q and F int but the agent is kept alive (all the recording data i.e. history, the monitoring, ecc... are saved). The purpose of this timeout is to allow the replacement of a faulty key without TNMP system interruption. If a key is inserted to a Slave IDU, it should notify the Last Master of its new state. This message will cause a dis-agreement detected by the Master IDU (which will prevent the situations of two Master IDUs).
6.2.4.1.1 Master/Slave swap operation

This operation is needed in order to replace a Master IDU. When a technician moves the key from the Master IDU to the Slave IDU, both IDUs should swap their Master/ Slave functionality. The IDU with the key notifies the Master of its new state, performs a SW reset and re-starts with the key inserted, as a Master. In this case, the IDU from which the key had been extracted (must be in Last Master state now) detects a disagreement and consequently performs SW reset, and restarts without a key, as a Slave. A Master / Slave swap had been completed.
6.2.4.1.2 Illegal situations

The following illegal situations can occur in the system: Both IDUs have a key: they negotiate and detect a disagreement. Both move to Idle mode (the agent will not work).
6-7
If during an IDUs Power-on there is No key in both IDUs: both will become Slave IDUs (the system goes in IDLE STATE and it will not work). No cable is connected between the IDUs: the IDU with the key becomes a Master. This is as if a single IDU (with a key) works in as in 1+0 configuration (maintaining 1+1 system type).
6.2.4.2
E2PROM and key management

A 1+1 protected system contains 3 configuration E2PROMs: Master IDU MainBoard E2PROM; Slave IDU MainBoard E2PROM and the key E2PROM.
The key contains the configuration for the entire system. It contains the system configuration TVs and the IDU configuration TVs, which are used for both IDUs. That is, the master CPU reads the configuration for both master and slave IDUs.
6.2.4.2.1 Key/ MB E2PROMs copy directions

During the system power-up (or if the key exists during software reset), the configuration in the key E2PROM is copied to the IDU MB E2PROM (oinly if they are not identical). In order to force the system to have the configuration of a new key, the system must be powered-up with this key in. If a key is inserted to an IDU in Last Master state, the configuration in the MB E2PROM will be copied to the key E2PROM (only if they are not identical). When replacing a faulty key, the key is plugged out, and a new key (might have unknown configuration) is inserted to the Last Master IDU. When a technician moves the key from Master to Slave IDU (to generate a Master / Slave swap), the system configuration should not be changed. That is, when a key is inserted to a Slave IDU during run time, the key E2PROM will not be changed (even if not identical to the Slave's MB E2PROM). After plugging the key, this IDU automatically performs a SW reset (with the key in), and the configuration in the key E2PROM will be copied to the IDU MB E2PROM (if they are not identical).
6.2.4.2.2 E2PROMs updating

Upon receiving any new configuration from the Manager, the Master CPU updates its own E2PROM and the key, and also updates the Slave IDU with the new data. The Slave CPU will update its own E2PROM. That keeps MB E2PROMs in both IDUs identical. Generally, the Master IDU is responsible that the Slave's configuration will be always updated. The Master will update the Slave with its own E2PROM data in two cases: after SW reset was performed; if a communication loss between the IDUs occurred, after communication with the mate IDU is re-established.
6-8
6.2.4.3
IDU1 / IDU2 definition

The IDUs in a 1+1 configuration are logically numbered as IDU1 and IDU2. The manager addresses each IDU by its logical number (note: the manger always sends its requests to the Master CPU, which runs the Agent). For example, assuming that the Master IDU is IDU1 and the Slave IDU is IDU2, if the manager wants to get status from IDU2, it sends its request to the Master IDU. The Master IDU (which is IDU1 in this example) addresses the Slave IDU in order to achieve the required information. There is no correlation between IDU1/ IDU2 and Master/Slave (Master IDU can be IDU1 or IDU2). The Master and Slave can swap (by moving the key), but the IDU numbers must remain the same. The manager reads from the equipment whether Master IDU is IDU1 or IDU2. Once the numbers have been assigned to each IDU in the first installation of the system, those numbers should not be changed, even when one of the IDUs is replaced. If an IDU is replaced, the system shall automatically give the new installed IDU the same logical IDU number as the former one. The IDU number (1 or 2) of each IDU is written in its MB E2PROM. After system power-up (or after SW reset was performed, or after communication is re-connected), the Master IDU is responsible to negotiate with the Slave IDU and determine the IDU numbers. The algorithm is the following : the Master IDU reads its own IDU number from the MB E2PROM and gives the Slave IDU the other IDU number. Consequently these situations can occur: Two new IDUs first installed in field. In a new IDU, the default number in the E2PROM is '1'. The Master IDU reads the value '1' from its own E2PROM. In that case, the Master will remain IDU1 and the Slave will become IDU2. After system is running, the power turns-off for one of the IDUs or both. When the power turns-on, each IDU remains with its own number (written in the E2PROM). The Master reads its own number and gives the Slave the other number, which it already has. Slave IDU replacement in field. When a new Slave IDU (with an unknown number written in its E2PROM) is installed, the Master starts negotiating with it. The Master IDU number remains the same, and the new Slave IDU will have the opposite number. When a Master IDU replacement is needed or in case of a communication problem between the two IDUs during system installation or IDU replacement. Extract the hardware key from the Master IDU (IDU1) and insert it in the Slave IDU (IDU2). Once the new IDU has been installed according the procedure, IDU1 is the Slave and IDU2 is the Master. Then, extract the hardware key from the Master IDU (IDU2) and insert it in the Slave IDU (IDU1). The system resets and begins the negotiating as described before.
6.2.4.4
Matching between two IDUs

Master/ Slave negotiation shall include all the information of the hardware and software profile of both IDUs.
6-9
6.2.4.4.1 Hardware matching requirements

The hardware profile contains information of all the hardware boards (HW type and SW Interface version for each board). The Master requests the hardware profile from the Slave and compares its own hardware profile with the Slave's one. Both IDUs must have the same hardware profile data; otherwise, the system will not start working (an appropriate alarm, 'HW mismatch', will be issued). In particular, both IDUs must have the same IDU type and ODU type.
6.2.4.4.2 Software matching requirements

The software profile contains information of the SW Release and SW Version of the CPU and FPGAs code (for both active and inactive flash banks). The Master requests the software profile from the Slave, and compare its own software profile with the Slave's software profile. In any case, running two IDUs (in a 1+1 configuration) with different SW versions is not allowed.
6.2.4.4.3 System type

The 'system type' (1+0, or one of several 1+1 configurations) is determined by the manager, and can be changed during system operation. Five possible system type configurations exist: (1+0) w/o MST, unprotected system; (1+1) Hot Stand-By Single Tributary Interface (STI) w/o MST; (1+1) Hetero Frequency Single Tributary Interface (STI) w/o MST; (1+1) Hot Stand-By Double Tributary Interface (DTI) w/o MST; (1+1) Hetero Frequency Double Tributary Interface (DTI) w/o MST.
6.2.4.4.4 Changing the system type

When the manager requests for system type change, the Master IDU writes the new system type value in the MB E2PROM and in the key E2PROM. The Master will automatically perform a SW reset, and start running with the new system type configuration.
6.2.5
Use licence
The licence to use of the application program given to the user is not related only to the software version, but also to the system configurations and the traffic capacities forseen in the provision. The program functions relative to the system configuration and to the traffic capacities not provided from the provision are disabled. In case of expansion, a new licence must be required to be able to manage a new system configuration and/or a not implemented traffic capacity.
6-10
6.2.6
Security
The Security function allows the access only to the authorized users; each user is characterized by a user class and by a password. A security mechanism is present both at server level and at NE level; the two security level are independent and work on parallel planes. For both the security levels, three different user classes are provided: Read Only: read-only access. The user can only read the alarms and the configurations set in the system; ha cannot modify any configuration. Read Write: access to the functions both in writing and in reading, except for the Admin user class. An user belonging to Admin user class can modify: all the slave/board configurations; all the commands; the inventory data (User Inventory Data); the fields for J0 management; the external alarms; the status and IDU configuration parameters; the ATCP fields. Admin: access to all the functions in reading and writing.
At any Security level (Server or NE), the disabled Security condition is equal to gain, for this level, Admin privileges; the only restriction is that passwords cannot be changed (class Anonymous). No Security mechanism is provided for the access to the commands of Net Viewer Server program menu, because this can be controlled by the Lock Workstation function of Windows NT, whose window the user can access to by command: Control + Alt + Delete. When the Security is enabled, using LCT, the following types of connection to NE can be executed: only 1 Admin user and 4 ReadOnly users; only 1 ReadWrite User and 4 ReadOnly users;
5 ReadOnly users. When the Security is disabled, only one user at time is allowed.
6-11
6.2.7
Connection status of the unit

The application program for the management displays the connection status with the Controller unit for each slave unit. DISCONNECTED CONNECTED ON LINE MISMATCH.
In DISCONNECTED status, the slave unit is considered extracted (the same message is returned even if the unit is inserted in the equipment, but it cannot correctly communicate with the Controller unit). The CONNECTED status identifies the beginning phase of the connection and control by Controller unit. In ON LINE status, the slave unit is present and communicates correctly with the Controller unit; furthermore, the firmware version is consistent with that of the Controller unit. In MISMATCH status, the slave unit is present and the communication with the Controller unit is active, but it doesnt correspond to the current equipment configuration or the firmware version is not congruent with that of the Controller unit. The signalling of the connection statuses is automatically updated by Controller unit, while the equipping setting of the units is executed via software by the operator. Therefore, some errors are possible, due to the mismatch between the equipping status, set by the operator, and the physic one of the equipment.
6-12
6.3 Loading of SRA Series 3 plug-in software (configuration file)

In Net Viewer and LCT programs, the plug-in of SRA series 3 equipment must be loaded (activation of the access to the equipment) to activate the related functions of control and configuration. The map constitutes the graphic interface for the access to the radio equipments of Net Viewer/LCT program. For the map construction, the user must select the TNMP EXT protocol. At the map opening, the Net Viewer/LCT program tries to connect to all the enabled equipments; for each equipment, the connection phase takes place in the following way: if a communication error is detected (example: not-existent equipment), an icon is displayed showing that the equipment is disconnected (not voluntary disabling status); if the connection is successful, the program tries to identify the type of radio equipment: if the identification is successful, a predefind icon is displayed, showing the type of radio equipment (Fig. 6.1); furthermore, the equipment menu is added; if the identification is not successful, (for example, the plug-in of that type of radio equipment is not installed), an icon is displayed, showing that this type of equipment is not supported.
Fig. 6.1
Example of map with SRA series 3 equipment
6-13
IP ADDRESS SETTING: The equipment (NE) cant maintain two IP address active. Then, the user must known beforehand the IP adrdress of NE. Consider that: during the first installation, the IDU has the default local IP address (192.168.255.3) and then the user can access the NE, set the network IP address and build the map containing IP address itself; during the replacement operations, the IP address is stored in the Key. So it is automatically saved, without need of PC; the current IP address can be known by dial-up menu or by proper DOS commands (during the dial-up: PC IP address = NE IP address + 1). This DOS command is: WinNT: ipconfig /all
The two NEs connected by means of the R channel must belong to different IP networks.
6-14
6.4 Structure of the operative menu

The access to the operative menu is possible by the menu bar of Net Viewer/LCT program or by clicking with the right button of the mouse on the equipment icon. Each equipment operative menu is characterized by the name (IP address or numeric acronym) and it contains: a predefined part, with the enabling and connecting commands, which depends on the SVR of Net Viewer/LCT program and not on the equipment (NE) type. a dynamic part, with the operative menu of control and configuration, available only if the communication towards the equipment is active (configuration file loaded).
For the description of the commands in the predefined part of the equipment menu, refer to the OMN Manual of the Net Viewer/LCT program. The SRA series 3 operative menu has the following options (Fig. 6.2). Status and Config: allows to configure the SRA series 3 equipment and to control its operating status. Alarms: allows to check the alarms status on the equipment and, then, to identify the cause of a possible fault. Measurements: allows to execute the measurement of the RF RX Power and to analyse the equipment performances. Inventory: allows to access the inventory data (stored in EEPROM) of the equipment units, to read them or to write possible notes (for example, installation date, type of fault, ecc.) and to record them. Security: allows to enable/disable the equipment Security and to configure the password for the different user classes. History Report: allows to record the most significant events, regarding the equipment operation. Alarm List: allows to display the list of the alarms currently active on the equipment.
Fig. 6.2
Operative menu of SRA series 3 equipment
The operative menu is formed by a series of menus in cascade. The following table (Tab. , Tab. 6.3, Tab. 6.4, Tab. 6.5) shows the complete structure of the operative menu: for each menu the associated user class is displayed.
6-15
Tab. 6.2 Main menu Status and Config>
Structure of the SRA series 3 operative menu (1+0 system type, ODU SRA) Submenus Equipment> System Status System Config J0 Link ID PM Config External TCN Setting> Restriction on User class
RST Trib Side RST Radio Side RSPI BER RSPI
Unit> Software Download>
IDU External EOW FTP Transfer Software Banks
Date and Time Network> NE Parameters Routing Table Edit NE> Copy Paste Alarms> Functional> STM-1 Payload AUX and Control Channels
Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user
Physical Station Severity TCN
6-16
Tab. 6.2 Main menu Measurements >
Structure of the SRA series 3 operative menu (1+0 system type, ODU SRA) Submenus Performance> IDU> RST Trib Side> B1 Quarter B1 Day B1 Record B1 Quarter B1 Day B1 Record Quarter Day Quarter Day Restriction on User class
RST Radio Side>
RSPI> BER RSPI> Summary Unit RF RX Power REC HW/Sw User> Factory Data>
Inventory>
IDU External EOW IDU Key External EOW
Report Security History Report Alarm List
6-17
Structure of the SRA series 3 operative menu (1+0 system type 1+0, ODU NPL) Submenus Equipment> System Status System Config J0 Link ID PM Config External TCN Setting> RST Trib Side RST Radio Side RSPI BER RSPI Unit> IDU ODU External EOW Software Download> IDU> FTP Transfer Software Banks ODU> FTP Transfer Software Banks Date and Time Network> NE Parameters Routing Table Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Edit NE> Copy Paste Active only for Admin user Active only for Admin user Restriction on User class
Alarms>
Functional>
STM-1 Payload AUX and Control Channels
Physical Station Severity TCN
6-18
Tab. 6.3 Main menu Measurements >
Structure of the SRA series 3 operative menu (1+0 system type 1+0, ODU NPL) Submenus Performance> IDU> RST Trib Side> B1 Quarter B1 Day B1 Record RST Radio Side> B1 Quarter B1 Day B1 Record RSPI> BER RSPI> Summary Unit RF RX Power REC Quarter Day Quarter Day Restriction on User class
Inventory>
HW/Sw User> IDU ODU External EOW Factory Data> IDU Key External EOW PID Report
Security History Report Alarm List
6-19
Structure of the SRA series 3 operative menu (1+1 system type, ODU SRA) Submenus Restriction on User class
Equipment >
System Status System Config Switches Config J0 Link ID PM Config TCN Setting>
IDU1>
IDU2>
RPS RST Trib Side RST Radio Side RSPI BER RSPI RST Trib Side RST Radio Side RSPI BER RSPI
External IDU 1 IDU 2 External EOW Software Download > FTP Transfer Unit > Software Banks Date and Time Network > NE Parameters Routing Table Edit NE > Copy Paste
Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user
6-20
Tab. 6.4 Main menu Alarms>
Structure of the SRA series 3 operative menu (1+1 system type, ODU SRA) Submenus Restriction on User class STM-1 Payload AUX and Control Channels STM-1 Payload AUX and Control Channels
Functional >
Channel 1 >
Channel 2 >
Physical Station Severity TCN> Measurements > Performance>
IDU1 IDU2 IDU1>
RPS > RST Trib Side >
RST Radio Side > RSPI > BER RSPI > Summary RST Trib Side >
Quarter Day B1 Quarter B1 Day B1 Record B1 Quarter B1 Day B1 Record Quarter Day Quarter Day B1 Quarter B1 Day B1 Record Quarter Day Quarter Day
IDU2>
RSPI> BER RSPI> Unit RF RX Power REC > Inventory > HW/Sw User > Factory Data >
ODU 1 ODU 2 IDU External EOW IDU Key External EOW
Report Security History Report Alarm List
6-21
Tab. 6.5
Structure of the SRA series 3 operative menu (1+1 system type, ODU NPL) Restriction on User class
Main menu Status and Config> Equipment >
Submenus System Status System Config Switches Config J0 Link ID PM Config TCN Setting> IDU1> RPS RST Trib Side RST Radio Side RSPI BER RSPI IDU2> RST Trib Side RST Radio Side RSPI BER RSPI External Unit > IDU 1 IDU 2 ODU1 ODU2 External EOW
6-22
Tab. 6.5
Structure of the SRA series 3 operative menu (1+1 system type, ODU NPL) Restriction on User class FTP Transfer Software Banks ODU1> FTP Transfer Software Banks ODU2> FTP Transfer Software Banks Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user Active only for Admin user NE Parameters Routing Table Edit NE > Copy Paste STM-1 Payload AUX and Control Channels Channel 2 > STM-1 Payload AUX and Control Channels Active only for Admin user Active only for Admin user Active only for Admin user
Main menu Software Download > IDUs>
Submenus
Date and Time Network >
Alarms>
Functional >
Channel 1 >
Physical Station Severity TCN> IDU1 IDU2
6-23
Tab. 6.5
Structure of the SRA series 3 operative menu (1+1 system type, ODU NPL) Restriction on User class RPS > RST Trib Side > Quarter Day B1 Quarter B1 Day B1 Record RST Radio Side > B1 Quarter B1 Day B1 Record RSPI > BER RSPI > Summary IDU2> RST Trib Side> B1 Quarter B1 Day B1 Record RSPI> BER RSPI> Quarter Day Quarter Day Quarter Day Quarter Day
Main menu Measurements > Performance> IDU1>
Submenus
Unit RF RX Power REC > Inventory > HW/Sw User > IDU ODU External EOW Factory Data > IDU Key External EOW PID Report Security History Report Alarm List ODU 1 ODU 2
6-24
In each dialog box or selection window described in this manual, there are two types of push buttons available to the user, with different meaning: OK button, use this button to apply the implemented changes or selections and closes the window. Cancel button, use this button to close the window without applying any change.
6-25
6.5 Status and Config menu

Status and Config menu allows to access to the commands and to the menus for checking the equipment operational status and for configuring the operational parameters of the network element (software, date and time, network parameters, ecc.). Fig. 6.3 Status and Config menu
Status and Config menu (Fig. 6.3) has the following options: Equipment: it manages the equipment status and configuration; Unit: it manages the unit status and configuration; Software Download: it manages the management of equipment software; Date and Time: it manages the setting of date and time of the system; Network: it manages the configuration of the network parameters of the network element.
In case of hardware fault, all the configuration menus related to the faulted hardware will be writable, to allow the user to correct the values (stored in EEPROM), which will be used by the equipment at the end of the replacing operations for the faulted components. Tab. 6.6 Parameter ATPC Management IDU 1 ATPC Management IDU 2 ATPC Mode IDU1 ATPC Mode IDU2 Default Power IDU1 Default Power IDU 2 HBER Enable J0 Management AIS Insertion for TIM Tim Activation Interval TIM Disactivation Interval J0 Management AIS Insertion for TIM Tim Activation Interval TIM Disactivation Interval B1 Threshold for SD Alarm Default system configuration (ODU SRA) Related Area TX Power TX Power TX Power TX Power TX Power TX Power TX Power Link Identification (TX side) Link Identification (TX side) Link Identification (TX side) Link Identification (TX side) Link Identification (RX side) Link Identification (RX side) Link Identification (RX side) Link Identification (RX side) SDH Channel (Trib side) Default value Enabled Enabled Automatic Automatic Nominal Power-8 Nominal Power-8 Disabled Disabled Disabled 10 1 Disabled Disabled 10 1 10E-5 Type Configuration Configuration Command Command Configuration Configuration Configuration Configuration Configuration Configuration Configuration Configuration Configuration Configuration Configuration Configuration
6-26
Tab. 6.6 Parameter Way-Side Ch Mode User Ch Mode
Default system configuration (ODU SRA) Related Area AUX Channel AUX Channel SDH Channel (Radio side) SDH Channel (Radio side) SDH Channel (Radio side) PM RSPI PM RSPI PM RSPI Radio side Tributary side Tributary side Tributary side Performance Monitoring Performance Monitoring Performance Monitoring Performance Monitoring Performance Monitoring Performance Monitoring Performance Monitoring Performance Monitoring Performance Monitoring Monitoraggio performance EOW external unit EOW external unit EOW external unit EOW external unit EOW external unit Optical interface Optical interface Optical interface Routing table Default value Disabled Disabled 10E-5 Normal -17dBm -75 dBm 10 dBm -75 dBm Disabled Disabled Disabled Disabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Disabled see Tab. 6.9 25 Enabled Enabled 1=1+1 Disabled ON Enabled Auto Enabled SRA 198.168.255.3 0.0.0.0 32TCM Type Configuration Configuration Configuration Command Configuration Configuration Configuration Configuration Command Command Configuration Configuration Command Command Command Command Command Command Command Command Command Command Configuration Configuration Configuration Configuration Configuration Configuration Configuration Command Configuration Configuration Configuration Configuration Configuration
B1 Threshold for SD Alarm Modulator Mode IF TX Level RX Field Threshold (RLTS1) TX Field Threshold (TLTS1) RX Field Threshold (RLTS2) Radio Local Loopback Trib Local Loopback MS-AIS trib enable MS-RDI trib enable RST TRIB EN TP 15 (*) RST TRIB EN TP day (*) RST RADIO EN TP 15 (*) RST RADIO EN TP day (*) RSPI EN TP 15 (*) RSPI EN TP day (*) RPS EN TP 15 (*) RPS EN TP day (*) Suspect Window setting TVs TCN thr. On/off EOW_ID LINE1_DIS LINE2_DIS LINE CONFIG E1 management en/dis LASER FORCING A.L.S LASER RESTART Rip disable/enable ODU1/2_type NE_IP_ADDRESS NET_MASK IDU Type
The parameters of type Configuration, which are disabled, are enabled in writing, to allow a correct operation of the system as soon as the configuration is enabled (es: IO Management).
6-27
(*): When disabled, the counters are still active, but no event is generated.
Tab. 6.7 Parameter
Default system configuration (ODU NPL) Related Area Transmission power Transmission power Transmission power Transmission power Transmission power Transmission power RF Frequency RF Frequency RF Frequency Transmission power RF Frequency Transmission power Transmission power RF Frequency RF Frequency RF Frequency Default value Enabled Enabled Automatic Automatic Pmin Pmin 0 0 0 10 dBm Freq Plan Enabled 0 dB 0 0 0 Not Valid Enabled Frequenza RF Disable Normal AUTO Type Configuration Configuration Command Command Configuration Configuration Configuration Configuration Configuration Configuration Configuration Configuration Configuration Configuration Configuration Command Command Configuration Configuration Configuration Configuration
ATPC Management IDU 1 ATPC Management IDU 2 ATPC Mode IDU1 ATPC Mode IDU2 Default Power IDU1 Default Power IDU 2 RF_CHN RF_TX_FREQ RF_RX_FREQ Pmin Setting FREQ_MODE ATPC_Control ATPC_RANGE Freq ch #1 first ch ID last ch ID FREQ_PLAN_NOTVALID SW_SQUELCH FREQ_PLAN_ACT TEST_SIGNAL COMP CABLE MODE
6-28
6.5.1
Equipment menu
Equipment menu (Fig. 6.4) allows to access to the following functions, to configure the equipment and to check the system status.
Fig. 6.4
Equipment menu
The following paragraphs describe the windows opened by the single menu entries and the related commands/configurations. Switches Config item is not present in this menu in case of (1+0) system type.
6.5.1.1
System Status
Selecting System Status item in Equipment menu (Fig. 6.4), the System Status window opens (Fig. 6.5, Fig. 6.6), where the operational status of the equipment and of all the constituting units is displayed, with the signalling of possible alarms present on the equipment itself. First of all, the current System Type and IDU type are displayed. In the left part of the window, the operational status of the main hardware components is shown: Indoor Unit (IDU for 1+0 S.T. or IDU1/IDU2 for 1+1 S.T.); Outdoor Unit (ODU for 1+0 S.T. or ODU1/ODU2 for 1+1 S.T.); Hardware backup key (Key); External EOW unit (EOW Ext).
Furtherrmore, for (1+1) system type equipments, the indication of Master/Slave is displayed for each IDU/ODU present in the system. In the right part of the window, the alarm signallings are reported, divided according to their severity (Severity box). Thanks to these alarm signallings, the user can detect a functional failure in the system, even if, from the hardware point of view, the IDU, ODU and the backup key are properly working. For 1+1 system type equipments, there is also the indication of the channel used for the Payload Flow in the following sections: Trib Section; Radio RX Section; Radio TX Section.
6-29
Fig. 6.5
System Status window (1+0 system type) - example
Fig. 6.6
System Status window (1+1 system types) - example
In System Status window (Fig. 6.5, Fig. 6.6), for each equipped unit, the status of the communication with the Controller unit is displayed. There can be the following cases: Disconnected (DIS), if the unit is not physically present, or it is OFF, or the Unit SW Self Test, relative to the check on the software functionality and on the EEPROM functionality, has given a negative result; Connected (CON): if the unit is ON. This is the communication status related to the initial checks; Mismatch (MIS): if the unit is different from the expected one, for the required configuration, or its firmware version cannot support the required operational modality (it depends on the firmware SVR of the Controller unit). In this condition, the alarm reports or the modification of the configuration are not enabled; On Line (OnL): the unit is correctly communicating with the Controller unit. The indication related to the communication status with the Controller unit is updated at time intervals in order of some seconds.
System indications System Type The system configuration. It can be: (1+0) w/o MST; (1+1) Hot Stand-By STI w/o MST; (1+1) Hetero Frequency STI w/o MST; (1+1) Hot Stand-By DTI w/o MST;
6-30
(1+1) Hetero Frequency DTI w/o MST.
IDU Type, The indication can be 32 TCM or 128 QAM. Summarized severity signalling (Severity) In this document, the severity has been given according with CCITT X.733, listed from the most severe to least severe: Critical: a service affecting condition has occurred and an immediate corrective action is required. Major: a service affecting condition has developed and an urgent corrective action is required. Minor: a non-service affecting fault condition has occurred and a corrective action should be taken in order to prevent a more serious fault. Warning: a potential or impeding affective service fault has been detected, before any significant effect has been felt. Action should be taken to further diagnose (if necessary) and the problem must be corrected in order to prevent it from becoming a more serious affecting fault. Test: indicates the existence of a special working condition for test or maintenance purpose. Traffic indication (only for (1+1) system types) (Payload Flow), the channel used for the information flow is indicated: Trib Section: Channel #; Radio RX Section: Channel #; Radio TX Section: Channel #;
System Backup Key The possible indications are: EOW external unit indications
green (normal) and
red (fault).
EOW unit connection indication The possible indications are: DIS, CON, onL, MIS. Unit status green (normal) and The possible indications are: indication is displayed only if the external EOW is On Line. red (fault). The
ODU indications ODU connection indication The possible indications are: DIS, CON, onL, MIS. ODU Type, The displayed indication can be SRA or NPL. Role of the unit in the system Possible roles are: Master or Slave (only for S.T. (1+1)). Unit status The possible indications are: green (normal) and indication is displayed only if the ODU is On Line. Heater It describes the operational status of ODU heater (optional). green (normal) and The possible indications are: indication is displayed only if the ODU heater is installed. red (fault). The
red (fault). The
6-31
IDU indications Unit type Possible values are: electrical (El) or optical (Opt). Role of the unit in the system Possible roles are: Master or Slave (only for S.T. (1+1)). IDU connection indication The possible indications are: DIS, CON, onL, MIS. Unit status The possible indications are: green (normal) and indication is displayed only if the IDU is On Line. red (fault). The
The unit fault is given by the logic sum of the alarm roots related to the unit itself, such to cause an out-of-order condition.
6.5.1.2
System Configuration
Selecting System Config command in Equipment menu (Fig. 6.4), the System Configuration window (Fig. 6.7, Fig. 6.9) opens, where the user can identify three areas. In the first area (above), the equipment System Type, the IDU (IDU1/IDU2) type (Electrical/Optical), the ODU (ODU1/ODU2) type (SRA/NPL), the possible equipping of the external EOW unit (Ext EOW).
are reported. The second area (below on the left) is related to the configuration of the characteristics of SDH Channel (B1 error threshold on radio and tributary side) and to the enabling status of the ALS procedure. This one only for optical IDU unit. The third area (below on the right) is related to the configuration of the AUX Channel (Way-Side Ch Mode, User Ch Mode (F1 Byte) and E1 Byte Management). Fig. 6.7 System Configuration window (1+1 system type with electrical IDU)
6-32
Fig. 6.8
System Configuration window (1+1 system type with optical IDU)
Fig. 6.9
System Configuration window (1+0 system type with electrical IDU)
System Type configuration The user can configure the equipment in one of the following five system type: (1+0) w/o MST; (1+1) Hetero Freq STI w/o MST; (1+1) Hot Stby STI w/o MST; (1+1) Hetero Freq DTI w/o MST; (1+1) Hot Stby DTI w/o MST.
Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window for the choice of the desired system type (Fig. 6.10) opens. Fig. 6.10 Window for the configuration of the System type
6-33
IDU type configuration The user can choose the IDU type: Electrical or Optical. This choice is available for all the system types. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window for the choice of the desired IDU type (Fig. 6.11) opens. Fig. 6.11 IDU type configuration (example: IDU1)
ODU type configuration The user can choose the ODU type: SRA or NPL. This choice is available for all the system types. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window for the choice of the desired ODU type (Fig. 6.12) opens. Fig. 6.12 ODU type configuration (example: ODU1)
External EOW unit configuration The user can choose to equip (Equipped) or not (Unequipped) the external EOW in the system. This unit allows to execute a selective call (dial-up) to another equipment in the network. The two EOW channels (external and internal) are separated and independent one from another, that is: the EOW signals (broadcast or selective) are never mixed together; the contemporary use of the two EOW channels is never allowed. The switch on the IDU front panel determines the EOW channel interested by the communication.
Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window for equipping/unequipping the external EOW unit (Fig. 6.13) opens. Fig. 6.13 External EOW configuration
6-34
SDH Channel parameters configuration B1 Threshold for SD Alarm (Trib Side) The user can configure the B1 threshold on the signal in input to tributary from tributary side, besides which the related alarm of degraded signal is activated. The range of selectable values is 10-5 - 10-9 (default: 10-5). Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window for the choice of the desired threshold (Fig. 6.14) opens.
Fig. 6.14
Window for B1 Threshold for SD Alarm (Trib Side) selection
B1 Threshold for SD Alarm (Radio Side) The user can configure the B1 threshold value on the signal in input to demodulator on radio side, besides which the related alarm of degraded signal is activated. The range of the allowed values is 10-5 - 10-9 (default: 10-5). Clicking twice on the insertion field with the left button of the mouse, the FIELD EDITING window for the selection of the desired threshold value opens (Fig. 6.15).
Fig. 6.15
Window for B1 Threshold for SD Alarm (Radio Side) selection
ALS Procedure (for optical IDU) The user can enable (Enabled) or disable (Disabled) the ALS procedure for the automatic laser shutdown, acting on this parameter. Clicking twice on the insertion field with the left button of the mouse, the FIELD EDITING window for the parameter configuration (Fig. 6.16) opens. By default, this value is Disabled.
Fig. 6.16
ALS procedure enabling/disabling
AUX Channel parameters Way-Side Channel Mode The user can enable or disable the WST channel (which provides a 2.048 Mbit/s
6-35
transmission payload), acting on this field. Clicking twice with the left button of the mouse on the insertion field, the related FIELD EDITING window (Fig. 6.17) opens. The possible values are Enabled and Disabled. By default, the parameter value is Disabled. Fig. 6.17 Window for Way-Side Channel Mode enabling/disabling
User Ch Mode (F1 Byte) This field is used to set the F1 interface. Clicking twice with the left button of the mouse on the insertion field, the related FIELD EDITING window (Fig. 6.18) opens. The possible values are: Disable (default value); G.703 Insert; V.11 Insert.
Fig. 6.18
Window for User Ch Mode configuration (F1 Byte)
E1 Byte Management The user can enable (Enabled) or disable (Disabled) the operation of the E1 byte user channel, acting on this field. Clicking twice with the left button of the mouse on the insertion field, the related FIELD EDITING window (Fig. 6.19) opens. By default, the parameter value is Disabled.
Fig. 6.19
Enabling/disabling of E1 byte management
6.5.1.3
Switches Config (only for (1+1) System Types)

Selecting Switches Config in Equipment menu (Fig. 6.4), the Switches Status & Configuration window (Fig. 6.20, Fig. 6.21, Fig. 6.22, Fig. 6.23) opens, where the status of the switches is displayed and the user can configure the parameters related to
6-36
switching operation. Here below the Switches Status & Configuration windows for the four different (1+1) system types are displayed. Fig. 6.20 Switches Status & Config window ((1+1) Hetero Freq DTI w/o MST))
Fig. 6.21
Switches Status & Config window ((1+1) Hetero Freq STI w/o MST))
Fig. 6.22
Switches Status & Config window ((1+1) Hot Stby DTI w/o MST))
6-37
Fig. 6.23
Switches Status & Config window ((1+1) Hot Stby STI w/o MST))
System Type indication The upper part of the window shows the system type actually configured on the equipment. It can be one of the four (1+1) system types present in the release of the equipment. This parameter is read only. Switches Setting parameters configuration Switch Mode The user can select the switching mode for the equipment acting on this field. Clicking twice with the left button of the mouse on the insertion field, the related FIELD EDITING window (Fig. 6.24) opens. The possible values are Auto and Manual. By default, this parameter value is Auto. In Auto mode, all the switches forcing configurations are ignored and the switches will move in accordance with their own switching criteria. In Manual mode, all the switching criteria are ignored and the switches will move in accordance with their own switches forcing configuration. The switch mode involves the switches all together.
Fig. 6.24
Switch Mode selection
During the normal working, all the switches move in the unrevertive mode (both for HW faults and for propagation alarms). The case of HSBY unbalanced systems (one antenna) is properly managed by replacement operations. Trib Selection (only for DTI system type) The user can set which of the two tributaries must be on line, acting on the related check box (Trib 1 on Line or Trib 2 on Line).
6-38
Dem Selection The user can set which of the two demodulator must be on line, acting on the related check box (Dem 1 on Line or Dem 2 on Line). ODU TX Selection (only for Hot Stand-by system type) The user can set which of the two ODU unit must be on line, acting on the related check box (ODU 1 on Line or ODU 2 on Line).
Switches Status box In this box, the switching status of the different component in the system is displayed. The parameters are read only and display information about: the tributary actually on line (Trib 1 on Line or Trib 2 on Line), only for DTI systems; the demodulator actually on line (Dem 1 on Line or Dem 2 on Line), only for Hot Stand-by systems; the ODU actually on line (ODU 1 on Line or ODU 2 on Line), only for Hot Stand-by systems.
Hot-Stby Switches Alarm Mismatch box (only for Hot Stand-by system types) ODU Switch Mismatch This alarm occurs in case of a mismatch between the command sent by the IDU and the switch status restituted by the ODU. green (normal) and red (fault). The possible indications are:
Switching Criteria Configuration box The user can enable/disable the desired switching criteria acting on the related field. MS-AIS Insertion Trib Side (only for DTI system type with electrical IDU) The value of this parameter is fixed to Disabled. Clicking twice with the left button of the mouse on the insertion field, the related FIELD EDITING window (Fig. 6.25) opens.
Fig. 6.25
MS-AIS Insertion Trib Side configuration
MS-AIS Trib Side Management (only for DTI system type) By acting on this field, the user can enable (Enabled) or disable (Disabled, default value) the management of the MS-AIS on the tributary side. Clicking twice with the left button of the mouse on the insertion field, the related FIELD EDITING window (Fig. 6.26) opens.
6-39
Fig. 6.26
MS-AIS Trib Side Management configuration
MS-RDI Trib Side Management (only for DTI system type) By acting on this field, the user can enable (Enabled) or disable (Disabled, default value) the management of the MS-RDI on the tributary side. Clicking twice with the left button of the mouse on the insertion field, the related FIELD EDITING window (Fig. 6.27) opens.
Fig. 6.27
MS-RDI Trib Side Management configuration
HBER Management By acting on this field, the user can enable (Enabled) or disable (Disabled, default value) the HBER management. Clicking twice with the left button of the mouse on the insertion field, the related FIELD EDITING window (Fig. 6.28) opens.
Fig. 6.28
HBER Management configuration
6.5.1.4
J0 Link ID
Selecting J0 Link ID in Equipment menu (Fig. 6.4), the Link Identification window (Fig. 6.29) opens, where the user can configure the parameters related to the link, both on the tributary side and on the radio side. The user can set, separately, the values of J0 Expected and J0 Inserted, typing a string of, at most, 15 characters for each of the two parameters. All the writing/reading parameters of J0 are collected in the Link Identification window.
6-40
Fig. 6.29
Link Identification window (1+0 system type)
Fig. 6.30
Link Identification window (1+1 system types)
Tributary Side parameters J0 Management This parameter can assume two values: Disabled (default) Enabled By means of this parameter, the user can enable (Enabled) or disable (Disabled) the management function of byte J0 on the tributary side. Clicking twice on this field, the FIELD EDITING window (Fig. 6.31) for the selection of the parameter value opens.
Fig. 6.31
Window for the J0 Management Tributary Side selection
6-41
J0 Expected In this field, the user can write the expected value (at most 15 characters) of byte J0 on the tributary side. To access the FIELD EDITING window (Fig. 6.32), click twice on the value field.
Fig. 6.32
Window for the J0 Expected Tributary Side insertion
J0 Inserted In this field, the user can write the inserted value (at most 15 character) of byte J0 on the tributary side. To access the FIELD EDITING window (Fig. 6.33), click twice on the value field.
Fig. 6.33
Window for the J0 Inserted Tributary Side insertion
J0 dropped (1+0 system type) This is a read-only field, which shows the value of byte J0 dropped from the frame on the tributary side. J0 dropped IDU1 (1+1 system types) This is a read-only field, which shows the value of byte J0 dropped from the frame on the tributary side. J0 dropped IDU2 (1+1 system types) This is a read-only field, which shows the value of byte J0 dropped from the frame on the tributary side. AIS insertion for TIM By acting on this field, the user can enable (Enabled) or disable (Disabled, default value) the alarm signalling insertion for the TIM (Trail Identifier Mismatch) alarm on the tributary side. This alarm occurs in the following cases: when no alignment on TTI can be done; when CRC calculated is different from CRC Dropped; when J0 Dropped is not equivalent to J0 Expected. To access the FIELD EDITING window (Fig. 6.34), click twice on the value field.
6-42
Fig. 6.34
Window for the AIS Insertion enabling/disabling (Tributary Side)
TIM Activation Interval In this field, the user can write the threshold value for the activation of TIM alarm on tributary side (number of the requested errored samples before TIM alarm is issued). The range of the allowed values is: 1-100 (default = 10). To access the FIELD EDITING window (Fig. 6.35), click twice on the value field.
Fig. 6.35
Window for the TIM Activation Interval insertion (Tributary Side)
TIM Disactivation Interval In this field, the user can write the threshold value for the disactivation of TIM alarm on tributary side (number of the requested right samples before TIM alarm is removed). The range of the allowed values is: 1-100 (default = 1). To access the FIELD EDITING window (Fig. 6.36), click twice on the value field.
Fig. 6.36
Window for the TIM Disactivation Interval insertion (Tributary Side)
Radio Side parameters J0 Management This parameter can assume two values: Disabled (default) Enabled By means of this parameter, the user can enable (Enabled) or disable (Disabled) the management function of byte J0 on the radio side. Clicking twice on this field, the FIELD EDITING window (Fig. 6.37) for the selection of the parameter value opens.
6-43
Fig. 6.37
Window for the J0 Management Radio Side selection
J0 Expected In this field, the user can write the expected value (at most 15 characters) of byte J0 on the radio side. To access the FIELD EDITING window (Fig. 6.38), click twice on the value field.
Fig. 6.38
Window for the J0 Expected Radio Side insertion
J0 Inserted In this field, the user can write the inserted value (at most 15 characters) of byte J0 on the radio side. To access the FIELD EDITING window (Fig. 6.39), click twice on the value field.
Fig. 6.39
Window for the J0 Inserted Radio Side insertion
J0 dropped This is a read-only field, which shows the value of byte J0 dropped from the frame on the radio side. AIS Insertion for TIM By acting on this field, the user can enable (Enabled) or disable (Disabled, default value) the alarm signalling insertion for the TIM (Trail Identifier Mismatch) alarm on the radio side. This alarm occurs in the following cases: when no alignment on TTI can be done; when CRC calculated is different from CRC Dropped; when J0 Dropped is not equivalent to J0 Expected. To access the FIELD EDITING window (Fig. 6.40), click twice on the value field.
6-44
Fig. 6.40
Window for the AIS Insertion enabling/disabling (Radio Side)
TIM Activation Interval In this field, the user can write the threshold value for the activation of TIM alarm on radio side (number of the requested errored samples before TIM alarm is issued). The range of the allowed values is: 1-100 (default value = 10). To access the FIELD EDITING window (Fig. 6.41), click twice on the value field.
Fig. 6.41
Window for the TIM Activation Interval insertion (Radio Side)
TIM Disactivation Interval In this field, the user can write the threshold value for the disactivation of TIM alarm on radio side (number of the requested right samples before TIM alarm is removed). The range of the allowed values is: 1-100 (default value = 1). To access the FIELD EDITING window (Fig. 6.42), click twice on the value field.
Fig. 6.42
Window for the TIM Disactivation Interval insertion (Radio Side)
6.5.1.5
PM Configuration
Selecting PM Config in Equipment menu (Fig. 6.4), the Performance Monitoring Config window (Fig. 6.43, Fig. 6.44) opens, where the user can configure the parameters related performance measurement for IDU and ODU units. Here below the windows in case of (1+0) and (1+1) system types are reported. The RSPI counters have the same strategy as the RST PM counters: ES - a one second period in which the estimated BER measure is less than a threshold (1E-10), or at least one defect occurred. SES - a one second period in which the estimated BER measure is less than a threshold (1E-6), or at least one defect occurred.
6-45
Tab. 6.8
RSPI parameters Parameter RLTS TLTS Default value RLTS1 = -75 dBm RLST2 = -65 dBm +10 dBm Range -66/-80 dBm (only RLTS1) +10/+17 dBm
Fig. 6.43
Performance Monitoring Config window (1+1 system types)
Fig. 6.44
Performance Monitoring Config window (1+0 system type)
When a IDU unit is in MISMATCH status, the MISMATCH red indication is displayed in the related windows and the configuration of the parameters for that IDU is not allowed. PM RSPI parameters configuration TX Field Threshold (TLTS1) The TLTS event is defined as a one second period during which the detected TL value is greater than a predefined threshold (in dB). Clicking twice on this field, the FIELD EDITING window (Fig. 6.45) for the insertion of the value opens. The user can set the threshold value (range between +10 dBm and +17 dBm, default value = +10 dBm).
6-46
Fig. 6.45
TX Field Threshold (TLTS1) insertion window
In (1+1) system type equipments, this configuration can be made both for IDU1 and for IDU2. RX Field Threshold (RLTS1) The RLTS event is defined as a one second period during which the detected RL value is below a predefined threshold (in dB). Clicking twice on this field, the FIELD EDITING window (Fig. 6.46) for the insertion of the value opens. The user can set the threshold value (range between -66 dBm and -80 dBm, default value = -75 dBm).
Fig. 6.46
RX Field Threshold (RLTS1) insertion window
In (1+1) system type equipments, this configuration can be made both for IDU1 and for IDU2. RX Field Threshold (RLTS2) The RLTS event is defined as a one second period during which the detected RL value is below a predefined threshold (in dB). Clicking twice on this field, the FIELD EDITING window (Fig. 6.47) for the insertion of the value opens. The threshold value can be defined by the user.
Fig. 6.47
Configurazione di RX Field Threshold (RLTS2)
In (1+1) system type equipments, this configuration can be made both for IDU1 and for IDU2.
6-47
PM en/dis TP parameters configuration RPS 15 By means of this parameter, the user can enable (Enabled) or disable (Disabled) the event associated to RPS 15 performance monitoring (data presence / summarisation). Clicking twice on this field, the FIELD EDITING window (Fig. 6.48) for the selection of the parameter value opens.
Fig. 6.48
RPS 15 performance monitoring configuration
RPS Day By means of this parameter, the user can enable (Enabled) or disable (Disabled) the event associated to RPS Day performance monitoring (data presence / summarisation). Clicking twice on this field, the FIELD EDITING window (Fig. 6.49) for the selection of the parameter value opens.
Fig. 6.49
RPS Day performance monitoring configuration
Suspect Running Window RPS Setting this parameter to Enabled (par. 6.50), the related time interval is considered suspect and the related PM measuring is not taken in consideration for the global PM statistics. The enabling/disabling regards only the current time period: at the beginning of the next time period this parameter is reset to Disabled.
Fig. 6.50
Enabling/disabling of Suspect Running Window RPS
6-48
IDU parameters configuration The configuration windows has the same appearance for the IDU1 and IDU 2 units. RST Trib 15 By means of this parameter, the user can enable (Enabled) or disable (Disabled) the RST Trib 15 performance monitoring on IDU. Clicking twice on this field, the FIELD EDITING window (Fig. 6.51) for the selection of the parameter value opens.
Fig. 6.51
RST Trib 15 performance monitoring configuration (example: IDU1)
RST Trib Day By means of this parameter, the user can enable (Enabled) or disable (Disabled) the RST Trib Day performance monitoring on IDU. Clicking twice on this field, the FIELD EDITING window (Fig. 6.52) for the selection of the parameter value opens.
Fig. 6.52
RST Trib Day performance monitoring configuration (example: IDU1)
RST Radio 15 By means of this parameter, the user can enable (Enabled) or disable (Disabled) the RST Radio 15 performance monitoring on IDU. Clicking twice on this field, the FIELD EDITING window (Fig. 6.53) for the selection of the parameter value opens.
Fig. 6.53
RST Radio 15 performance monitoring configuration (example: IDU1)
6-49
RST Radio Day By means of this parameter, the user can enable (Enabled) or disable (Disabled) the RST Radio Day performance monitoring on IDU. Clicking twice on this field, the FIELD EDITING window (Fig. 6.54) for the selection of the parameter value opens.
Fig. 6.54
RST Radio Day performance monitoring configuration (example: IDU1)
RSPI 15 By means of this parameter, the user can enable (Enabled) or disable (Disabled) the RSPI 15 performance monitoring on IDU. Clicking twice on this field, the FIELD EDITING window (Fig. 6.55) for the selection of the parameter value opens.
Fig. 6.55
RSPI 15 performance monitoring configuration (example: IDU1)
RSPI Day By means of this parameter, the user can enable (Enabled) or disable (Disabled) the RSPI Day performance monitoring on IDU. Clicking twice on this field, the FIELD EDITING window (Fig. 6.56) for the selection of the parameter value opens.
Fig. 6.56
RSPI Day performance enabling/disabling (example: IDU1)
Suspect Running Window RST Trib Setting this parameter to Enabled (Fig. 6.57), the related time interval is considered suspect and the related PM measuring is not taken in consideration for the global PM statistics. The enabling/disabling regards only the current time period: at the beginning of the next time period this parameter is reset to Disabled.
6-50
Fig. 6.57
Suspect Running Window RST Trib (IDU1) configuration
Suspect Running Window RST Radio Setting this parameter to Enabled (Fig. 6.58), the related time interval is considered suspect and the related PM measuring is not taken in consideration for the global PM statistics. The enabling/disabling regards only the current time period: at the beginning of the next time period this parameter is reset to Disabled.
Fig. 6.58
Suspect Running Window RST Radio (IDU1) configuration
Suspect Running Window RSPI Setting this parameter to Enabled (Fig. 6.59), the related time interval is considered suspect and the related PM measuring is not taken in consideration for the global PM statistics. The enabling/disabling regards only the current time period: at the beginning of the next time period this parameter is reset to Disabled.
Fig. 6.59
Suspect Running Window RSPI (IDU1) configuration
6-51
6.5.1.6
TCN Setting menu

The TCN (Threshold Crossing Notification) function allows to activate an alarm when any performance counter crosses a specified threshold (Threshold ON). The mechanism for the de-activation of this alarm depends on which interval (15 or 24h) has been considered: in any case, the counter value is reset at the end of the considered interval. TCN 15, if the counter crosses the Threshold ON in the interval under control, the alarm is activated and it remains active until the end of the first successive period, during which the Threshold OFF is not crossed. TCN 24h, if the counter crosses the Threshold ON in the interval under control, the alarm is activated and it is automatically reset at the end of the interval under control. If the counter is active yet, the alarm is activated again in the following interval only when the Threshold ON is crossed again.
The TCN 15 alarms are set as Single Mode, that is they use two thresholds: ON and OFF. The TCN 24h alarms are set as Cyclic Mode, that is they use only the Threshold ON. The relation between the TCN thresholds is Thr ON > Thr OFF. The IDU software doesnt provide this limitation. TCN Setting menu allows the access to the windows for the configuration of the error thresholds, behing which the alarm notification is activated. The configurable thresholds are related to different parameters in case of IDU 1 (Fig. 6.60) or IDU 2 (Fig. 6.60). Fig. 6.60 TCN Setting > IDU1 menu
In case of IDU2, RPS menu item is not present.
6-52
Tab. 6.9
Default values for TCN parameters: 15 min ON/OFF (Single Mode) RST RSPI BBE 3000 20 RLTS1 900 2 RLTS2 900 2 TLTS1 900 2 20 2 BER-RSPI BER-SES BER-ES 300 20 2 0 RPS SWITCH
Counter Th. ON Th. OFF
SES 2 0
ES 30 2
Tab. 6.10
Default values for TCN parameters: 24h ON (Cyclic Mode) RST RSPI BBE 1800 RLTS1 900 RLTS2 900 TLTS1 900 20 BER-RSPI BER-SES BER-ES 300 2 RPS SWITCH
Counter Th. ON
SES 2
ES 30
The range of configurable values for the TCN counters changes in the following way: the 15 minutes records are configurable between 0 and 900, except BEE (range within 0 and 216-1) and RPS (range within 0 and 5); the 24 hours records are configurable between 0 and 216-1 (65535). These numbers define the record capacity, even if the number of the possible event is, in theory, greater (the record goes in overflow). RPS range is within 0 and 5.
The following parameters describe the windows opened by each single menu item and the related commands/configurations.
6.5.1.6.1 RPS (only 1+1 system types)

Selecting RPS in TCN Setting > IDU1 menu (Fig. 6.60), the TCN Setting RPS window (Fig. 6.61) opens, where the user can set the activation and de-activation thresholds of the Trib Switch Alarm and Dem Switch Alarm. Fig. 6.61 TCN Setting RPS window
6-53
Trib Switch Alarm configuration Threshold ON for 15 Trib Switch Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. TheThe default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.62) opens for choice of the parameter value.
Fig. 6.62
Configuration of the activation value for 15 Trib Switch Alarm
Threshold OFF for 15 Trib Switch Alarm In this field the user can set the value of the de-activation threshold. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.63) opens for choice of the parameter value.
Fig. 6.63
Configuration of the de-activation value for 15 Trib Switch Alarm
Threshold ON for Day Trib Switch Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.64) opens for choice of the parameter value.
Fig. 6.64
Configuration of the activation value for Day Trib Switch Alarm
Dem Switch Alarm configuration Threshold ON for 15 Dem Switch Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.66) opens for choice of the parameter value.
6-54
Fig. 6.65
Configuration of the activation value for 15 Dem Switch Alarm
Threshold OFF for 15 Dem Switch Alarm In this field the user can set the value of the de-activation threshold. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.66) opens for choice of the parameter value.
Fig. 6.66
Configuration of the de-activation value for 15 Dem Switch Alarm
Threshold ON for Day Dem Switch Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.67) opens for choice of the parameter value.
Fig. 6.67
Configuration of the activation value for Day Dem Switch Alarm
Stby Switch Alarm configuration Threshold ON for 15 Stby Dem Switch Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.68) opens for choice of the parameter value.
Fig. 6.68
Configuration of the activation value for 15 Stby Switch Alarm
6-55
Threshold OFF for 15 Stby Switch Alarm In this field the user can set the value of the de-activation threshold. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.69) opens for choice of the parameter value.
Fig. 6.69
Configuration of the de-activation value for 15 Stby Switch Alarm
Threshold ON for Day Stby Switch Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.70) opens for choice of the parameter value.
Fig. 6.70
Configuration of the activation value for Day Stby Switch Alarm
6-56
6.5.1.6.2 RST Trib Side

Selecting RST Trib Side in TCN Setting > IDU1 menu (Fig. 6.60) or in TCN Setting > IDU2 menu, the TCN Setting RST Trib window (Fig. 6.71) opens, where the user can set the activation and de-activation thresholds of the SES, ES and BBE alarms for the tributary side. Fig. 6.71 TCN Setting RST Trib window
SES Alarm configuration Threshold ON for 15 SES Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.72) opens for choice of the parameter value.
Fig. 6.72
Configuration of the activation value for 15 SES Alarm
Threshold OFF for 15 SES Alarm In this field the user can set the value of the de-activation threshold. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.73) opens for choice of the parameter value.
Fig. 6.73
Configuration of the de-activation value for 15 SES Alarm
6-57
Threshold ON for Day SES Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.74) opens for choice of the parameter value.
Fig. 6.74
Configuration of the activation value for Day SES Alarm
BBE Alarm configuration Threshold ON for 15 BBE Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.75) opens for choice of the parameter value.
Fig. 6.75
Configuration of the activation value for 15 BBE Alarm
Threshold OFF for 15 BBE Alarm In this field the user can set the value of the de-activation threshold. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.76) opens for choice of the parameter value.
Fig. 6.76
Configuration of the de-activation value for 15 BBE Alarm
Threshold ON for Day BBE Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.77) opens for choice of the parameter value.
6-58
Fig. 6.77
Configuration of the activation value for Day BBE Alarm
ES Alarm configuration Threshold ON for 15 ES Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.78) opens for choice of the parameter value.
Fig. 6.78
Configuration of the activation value for 15 ES Alarm
Threshold OFF for 15 ES Alarm In this field the user can set the value of the de-activation threshold. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.79) opens for choice of the parameter value.
Fig. 6.79
Configuration of the de-activation value for 15 ES Alarm
Threshold ON for Day ES Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.80) opens for choice of the parameter value.
Fig. 6.80
Configuration of the activation value for Day ES Alarm
6-59
6.5.1.6.3 RST Radio Side

Selecting RST Radio Side in TCN Setting > IDU1 menu (Fig. 6.60), the TCN Setting RST Radio window (Fig. 6.81) opens, where the user can set the activation and de-activation thresholds for the SES, ES and BBE alarms for the radio side. Fig. 6.81 TCN Setting RST Radio window
Fig. 6.82
Fig. 6.83
Threshold ON for Day SES Alarm In this field the user can set the value of the error threshold that, if crossed,
6-60
activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.84) opens for choice of the parameter value. Fig. 6.84 Configuration of the activation value for Day SES Alarm
BBE Alarm configuration Threshold ON for 15 BBE Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.85) opens for choice of the parameter value.
Fig. 6.85
Configuration of the activation value for 15 BBE Alarm
Threshold OFF for 15 BBE Alarm In this field the user can set the value of the de-activation threshold. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.86) opens for choice of the parameter value.
Fig. 6.86
Configuration of the de-activation value for 15 BBE Alarm
Threshold ON for Day BBE Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.87) opens for choice of the parameter value.
6-61
Fig. 6.87
Configuration of the activation value for Day BBE Alarm
Fig. 6.88
Fig. 6.89
Fig. 6.90
6-62
6.5.1.6.4 RSPI
Selecting RSPI in TCN Setting > IDU1 menu (Fig. 6.60) or in TCN Setting > IDU2 menu (Fig. 6.60), the TCN Setting RSPI window (Fig. 6.91) opens, where the user can set the activation and de-activation thresholds for RLTS1 Alarm, RLTS2 Alarm and TLTS1 Alarm. Fig. 6.91 TCN Setting RSPI window
RLTS1 Alarm configuration Threshold ON for 15 RLTS1 Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.92) opens for choice of the parameter value.
Fig. 6.92
Configuration of the activation value for 15 RLTS1 Alarm
Threshold OFF for 15 RLTS1 Alarm In this field the user can set the value of the de-activation threshold. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.93) opens for choice of the parameter value.
Fig. 6.93
Configuration of the de-activation value for 15 RLTS1 Alarm
Threshold ON for Day RLTS1 Alarm In this field the user can set the value of the error threshold that, if crossed,
6-63
activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.94) opens for choice of the parameter value. Fig. 6.94 Configuration of the activation value for Day RLTS1 Alarm
TLTS1 Alarm configuration Threshold ON for 15 TLTS1 Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.95) opens for choice of the parameter value.
Fig. 6.95
Configuration of the activation value for 15 TLTS1 Alarm
Threshold OFF for 15 TLTS1 Alarm In this field the user can set the value of the de-activation threshold. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.96) opens for choice of the parameter value.
Fig. 6.96
Configuration of the de-activation value for 15 TLTS1 Alarm
Threshold ON for Day TLTS1 Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.97) opens for choice of the parameter value.
6-64
Fig. 6.97
Configuration of the activation value for Day TLTS1 Alarm
RLTS2 Alarm configuration Threshold ON for 15 RLTS2 Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.98) opens for choice of the parameter value.
Fig. 6.98
Configuration of the activation value for 15 RLTS2 Alarm
Threshold OFF for 15 RLTS2 Alarm In this field the user can set the value of the de-activation threshold. The default parameters are specified in Tab. 6.9. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.99) opens for choice of the parameter value.
Fig. 6.99
Configuration of the de-activation value for 15 RLTS2 Alarm
Threshold ON for Day RLTS2 Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.100) opens for choice of the parameter value.
Fig. 6.100
Configuration of the activation value for Day RLTS2 Alarm
6-65
6.5.1.6.5 BER-RSPI
Selecting BER-RSPI in TCN Setting > IDU1 menu (Fig. 6.60) or in TCN Setting > IDU2 menu (Fig. 6.60), the TCN Setting BER-RSPI window (Fig. 6.101) opens, where the user can set the activation and de-activation thresholds of SES and ES alarms. Fig. 6.101 TCN Setting BER-RSPI window
Fig. 6.102
Fig. 6.103
Threshold ON for Day SES Alarm In this field the user can set the value of the error threshold that, if crossed, activates the notification to the management system. The default parameters are specified in Tab. 6.10. Clicking twice with the left button of the mouse on the insertion field, the FIELD EDITING window (Fig. 6.104) opens for choice of the parameter value.
6-66
Fig. 6.104
Configuration of the activation value for Day SES Alarm
Fig. 6.105
Fig. 6.106
Fig. 6.107
6-67
6.5.1.7
External
Selecting External in Equipment menu (Fig. 6.4), the External Setting window (Fig. 6.108) opens, where the user can configure the Station Alarms and the Remote Controls.
Fig. 6.108
External Setting window
There are four configurable station alarms and two remote controls. It is possible to assign a name to each station alarm, clicking twice on the relative field. The FIELD EDITING window for the insertion of the desired string (max. 16 characters) opens (Fig. 6.109). Fig. 6.109 Window for the insertion of Alarm 1 description
For each one of the available station alarms, the user can configure the Polarity parameter, for the setting of the electric level corresponding to the alarm logic condition. Clicking twice on this field, the FIELD EDITING window (Fig. 6.110) for the selection of the parameter configuration opens. Two alarm logics are configurable: Fig. 6.110 Gnd=Alarm (default); Floating=Alarm.
Polarity Alarm 1 configuration
In the Remote Control area of the External Setting window, the user can write a string
6-68
(max. 16 characters) of description for the remote control (Description Remote Control) (Fig. 6.111), clicking twice on the related texfield, and enable/disable the command, acting on the Command check boxes (possible values are On and off) (Fig. 6.108). Fig. 6.111 Window for the insertion of Description Remote Control 1
6.5.2
Unit menu
Unit menu (Fig. 6.112) allows to access to the following functions, to configure the operative parameters of the IDU, ODU or EOW units. If the unit is not on line, the correspondent menu item is greyed out.
Fig. 6.112
Unit menu
The menu items related to ODU or ODU1/ODU2 are present in Unit menu only if ODU NPL units are equipped.
6-69
6.5.2.1
IDU Status & Configuration window

Selecting IDU1 or IDU2 in Unit menu (Fig. 6.112) (or IDU for 1+0 system type equipment), the IDU Status & Configuration window (Fig. 6.113, Fig. 6.114) opens, where the user can configure the IDU unit operating parameters.
Fig. 6.113
IDU1 Status & Configuration window (optical IDU, ODU SRA)
For the (1+1) Single Tributary Interface system types, both Hot-Stby and Hetero Frequency, the Local Loop-Back parameter only on tributary side in the IDU2 Status & Configuration window (Fig. 6.114) is read only and fixed on Disabled value. For the (1+1) Double Tributary Interface system types, both Hot-Stby and Hetero Frequency, the Local Loop-Back parameters on tributary and radio sides in the IDU2 Status & Configuration window are user configurable. Fig. 6.114 IDU2 Status & Configuration window (optical IDU, ODU NPL) for LCT
SDH Channel parameters configuration (Tributary side) Local Loop-Back The tributary local loop-back is executed at the physical tributary interface level. The user can enable or disable the local loop-back function. This is automatically implemented on the local equipment and is related to the signal on radio side. The local loop-back should be executed as nearest as possible to the SDH tributary interface. The possible values are Enabled and Disabled (default value).
The local loop-backs are configurable by the user only from LCT, not from the supervision system.
6-70
Tab. 6.11
Access to the Loop-Back parameters (tributary side) Trib STI DTI Master Slave Master Slave NetViewer R/O R/O R/O R/O LCT R/W R/O R/W R/W
Fig. 6.115
Local Loop-Back enabling/disabling window (Tributary Side)
Laser Forcing The user can force the switching on and the switching off of the laser beam used for the transmission on optical fiber. Possible values are: On (default) and Off. Selecting Off, the laser status doesnt change until an operator manual command.
Fig. 6.116
Laser Forcing configuration
Laser Restart The user can select the desired modality for the laser restart among the following ones: Auto (default) , Manual and Manual for Test.
The switching from Automatic to Manual is possible only if the laser is state off, otherwise a message error is returned to the user. The relus for the automatic laser restart: Automatic: the laser operation is automatically restored, after the execution of the ALS procedure, when the cause that issued it has been removed; Manual: the laser operation restarts as a consequence of a user manual command. Then the procedure returns to the Automatic mode and the service is restored only when the cause that issued ALS has been removed; Manual for Test: it is used to test the equipment. After this operation, the modality returns to Automatic.
6-71
Fig. 6.117
Laser Restart configuration
Laser Status It is a read only parameter, which indicates the laser operation status. It can be: On or Off.
Tab. 6.12
Laser operative rules ALS Enabled Enabled Disabled Disabled Laser Forcing Normal (ON) OFF Normal (ON) OFF Laser Status as defined by ALS OFF ON OFF
SDH Channel parameters configuration (Radio side) Local Loop-Back The radio local loop-back is executed at the tributary RSOH interface level. The user can enable or disable the local loop-back function. This is implemented on the local equipment and is related to the signal on radio side. The local loop-back should be executed as nearest as possible to the SDH tributary interface. The possible values are Enabled and Disabled (default value).
Tab. 6.13
Access to the Loop-Back parameters (radio side) Trib STI DTI Master Slave Master Slave NetViewer R/O R/O R/O R/O LCT R/W R/W R/W R/W
Fig. 6.118
Local Loop-Back enabling/disabling window (Radio Side)
Modulator Mode By means of this button, the user can select the Modulator operating modality.
6-72
The related FIELD EDITING window (Fig. 6.119) opens, where there are three possible options: Normal (default); Carrier Only; Mute. The configuration of the Modulatore Mode parameter is possible only by means of the LCT. This field is read only for NetViewer. Fig. 6.119 Modulator Mode configuration window (electrical IDU)
IF TX Level It allows to select the transmission level (in dBm) on IF cable. Clicking twice on the insertion field, the FIELD EDITING window for the IF TX level configuration opens (Fig. 6.120). The selectable values are: -17 dBm (default) and +5 dBm for IDU32 -17 dBm (default) and +3 dBm for IDU128.
Fig. 6.120
IF TX Level configuration window
TX Power parameters (ODU SRA only) This section is present in IDU Status & Configuration window (Fig. 6.113) only for ODU SRA. Otherwise, in case of ODU NPL, these parameters are managed by ODU Status & Configuration window (Fig. 6.123). The setting of TX Power in the ATPC box and in the Local Default Power box are mutually exclusive: that is, the Pdef is active only when the ATPC Management is disabled ATPC Management It allows to enable or disable the ATPC parameter management. The user must click twice on the value field with the left button of the mouse to open the selection window (Fig. 6.121). In this window, the user can select: Disabled, to disable the automatic management of the transmission power;
6-73
Enabled (default), to enable the automatic management of the transmission power.
Fig. 6.121
ATPC Management configuration window
ATPC Mode This field allows the user to set the local transmitter power. The user must click twice with the left button of the mouse to open the selection window (Fig. 6.122). There are three options: Automatic (default value); Nominal Power; Nominal Power -8dB.
Fig. 6.122
ATPC Mode configuration window
The following table (Tab. 6.14) lists the rules which determine the transmission power. These rules allow to the user to decide if activating or not the indication of manual operation when the transmission power is forced to a predefined value. Tab. 6.14 ATPC setting rules (ODU SRA) ATPC management Disabled Enabled Enabled Enabled auto Pnom Pnom-8 dB ATPC mode Resulting TX power Pdef (*) according to ATPC algorithm Pnom Pnom-8 dB Manual operation OFF OFF ON ON
(*): Pdef = Pnom, Pnom-8 dB Local Default Power In this area, the user can select, by means of the check boxes, one of the two settings: Nominal Power Nominal Power-8 dB (default value)
The two check boxes are mutually exclusive.
6-74
6.5.2.2
ODU Status and Configuration window (for ODU NPL)

Selecting ODU1 or ODU2 in Unit menu (Fig. 6.112) (or ODU for the (1+0) system type), the ODU Status and Configuration window (Fig. 6.124) opens, where the user can configure the ODU operative parameters. At the bottom of the window, there is the string: ODU Power-up Procedure: Completed (or Running, when ODU is powered-up)).
Fig. 6.123
ODU Status & Configuration window (ODU Power-up: Running)
Fig. 6.124
ODU Status & Configuration window (ODU Power-up: Completed)
RF Frequency Setting parameters Freq Mode It allows to choose the frequency modality to be used. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.125) opens. The two possible choices are: Freq Plan and Continuous.
6-75
Fig. 6.125
Configuration of Freq Mode
In Freq Plan, it is necessary: 1. 2. 3. 4. to enable Freq Plan Activation (Enabled); to set the parameters of the frequency plan: Freq Ch. #1, First Channel ID e Last Channel ID; to disable Freq Plan Activation (Disabled); to modify the RF Channel ID.
ODU automatically checks that the set value is between First Channel ID and Last Channel ID and, if the parameter is correct, it updates the transmission and reception frequencies to match the frequency plan. If Frequency Plan mode has been chosen, but the Freq Plan parameters in ODU are not stored or not corrected, the FREQ_PLAN_FAIL alarm is activated (a red string in Freq. Plan setting field). This alarm is cancelled when the Freq Plan parameters are correctly set. Fig. 6.126 Freq Plan Fail alarm
In Frequency Plan modality, the parameters setting is effective (that is the transmission and reception RF frequencies are really changed) if and only if the value of the RF Channel ID parameter is modified. If ODU NPL at 18 GHz is used, it is not possible to use the Frequency Plan modality for the setting of the RF frequency.
6-76
If the modification of RF Channel ID is not necessary for the setting of these parameters, RF Channel ID shall be modified and then reset to the previous value (if RF Channel ID was already 1 and must be set to 1, before it must be changed to 2 and then reset to 1). This because the transmission and reception RF frequencies change only after a change of: TX Freq or RX Freq, in Continuos Mode; RF Channel ID, in Freq Plan
Freq Plan Activation It allows to enable (Enabled) or disable (Disabled) the activation of the frequency plan. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.127) opens.
Fig. 6.127
Freq Plan Activation enabling/disabling
Channel Spacing (kHz) This parameter defines te separation, within the frequency plan, between the central frequencies of two adjacent RF channels with the same polarisation and the on the same transmission direction. The possible values returned by the equipment are: 28000 kHz or 56000 kHz (default).
TX Freq Plan Mode parameters TX Freq Ch#1 It allows to set the radio frequency (kHz) corresponding to the first channel that can be used for the signal transmission. The default value is 0 kHz. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.128) opens for the insertion of the parameter value.
Fig. 6.128
Configuration of TX Freq Ch#1
First Channel ID It allows to define the number of the first channel that can be used for the signal transmission. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.129) opens for the insertion of the parameter value.
6-77
Fig. 6.129
Configuration of First Channel ID
Last Channel ID It allows to define the number of the last channel that can be used for the signal transmission. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.130) opens for the insertion of the parameter value.
Fig. 6.130
Configuration of Last Channel ID
RF Channel ID It allows to set the number of the radio frequency channel currently in use. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.131) opens for the insertion of the parameter value.
Fig. 6.131
Configuration of RF Channel ID
TX Freq It allows to set the radio frequency (kHz) used for the transmission. The default value is 0 kHz. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.132) opens for the insertion of the parameter value.
Fig. 6.132
Configuration of TX Freq
RX Freq It allows to set the radio frequency (kHz) used for the reception. The default value is 0 kHz. Clicking twice with the left button of the mouse on the selection field, the
6-78
FIELD EDITING window (Fig. 6.133) opens for the insertion of the parameter value. Fig. 6.133 Configuration of RX Freq
TX Power parameters For the setting of the parameters related to ATPC, consider the following table table: Tab. 6.15 ATPC management rules (ODU NPL) ATPC Management Enabled Disabled ATPC Mode Pmin Pmax Auto Default Power It doesnt matter Pmin Pmax Transmitted Power Pmin Setting (manual forcing) Pmin Setting+R (manual forcing) Pmin Setting +automatic level Pmin Setting Pmin Setting +R
when R is the gratest ATPC range that can be added to Pmin Setting. When ATPC Management is Enabled, IDU sends a proper ATPC command with the information related to this increment, according to the ATPC Mode value, which can be: Auto Pmax Pmin
When ATPC Management is Disabled, IDU sends a proper ATPC command with the information related to this increment, according to the Default Power value, which can be: Pmax Pmin
Anyway, the ATPC Control is active into ODU.
ATPC Management It allows to enable (Enabled) or disable (Disabled) the management of the transmission power. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.134) opens.
6-79
Fig. 6.134
Configuration of ATPC Management
ATPC Mode It allows to choose the value of the transmission power among the Pmax, Pmin and Automatic values. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.135) opens. This depends on the current radio link and it is calculated and stored into IDU during installation.
Fig. 6.135
Configuration of ATPC Mode
Pmin Setting It allows to set the value of the transmission minimum power. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.136) opens for the insertion of the parameter value.
Pmin and ATPC Range values are set in such a way to respect the hardware range of the transmission power values for ODU. The control on these values is executed by ODU that refuses the settings if they are not correct. The limitations that must be respected are: Pmin_setting + ATPC_Range Pmax Pmin_setting Pmin where Pmax e Pmin are reported in Fig. 6.218. Fig. 6.136 Configuration of TX Power Pmin Setting
ATPC Control It is always set to Enabled.
6-80
Fig. 6.137
Configuration of ATPC Control
ATPC Range It allows to choose the range of the ATPC values. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.138) opens for the insertion of the parameter value. The range of allowed values is between 0 and 15 dB.
Fig. 6.138
Configuration of ATPC Range
Local Default Power parameter The user can choose, by means of the check box, if set the value to Pmin or Pmax. Commands Squelch Activation It allows to activate (ON) or de-activate (off) the software procedure for the ODU squelch (in transmission). Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.139) opens for the insertion of the parameter value.
Fig. 6.139
Configuration of Squelch Activation
Comp IF Cable Mode It allows to choose one of the possible management strategies: Auto (default) or Manual. Clicking twice with the left button of the mouse on the selection field, the FIELD EDITING window (Fig. 6.140) opens for the insertion of the parameter value. After an ODU replacement, the procedure for the cable compensation must be activated to calculate the correct attenuation value (the default value stored in ODU unit is 31 dB), depending on the lenght of the IF cable and of the IF TX power level.
6-81
In Auto mode, the cable compensation is automatically activated when one of the following conditions takes place: the ODU is switched on; the IF TX power level is modified In Manual mode, the cable compensation is activated acting on the corresponding activation command. Set the cable compensation modality to Manual after the installaion of ODU NPL. The default value is Auto. Fig. 6.140 Configuration of Comp IF Cable Mode
Start Compensation Cable It allows to manually force the procedure for the cable compensation. It is visible and can be activated only by LCT.
During the cable compensation procedure, the red indication Comp Cable Running appers (Fig. 6.141). Fig. 6.141 Start of cable compensation procedure
If the compensation procedure ends successfully, the red indication End Comp Cable appears for some seconds (Fig. 6.142).
6-82
Fig. 6.142
Positive end of the cable compensation
Otherwise, the Cable Comp Out of Range indication appears (Fig. 6.143). Fig. 6.143 Negative end of the cable compensation
6-83
6.5.2.3
ATPC function
SRA 3 radio equipment supports the ATPC functionalities both in HSBY and in FD systems. Since both the ATPC and the Ptx manual forcing are channel features and not system ones, the IDUs ID# in both the NEs shall be aligned to proper run the ATPC algorythm. This means that: 1. 2. in FD systems the local idu1 shall be connected with the far-end IDU1; the local IDU2 shall be connected with the far-end IDU2. in HSBY unbalanced systems the local IDU1 shall have the same coupling loss with the antenna of the far-end IDU1; the local IDU2 shall have the same coupling loss with the antenna of the far-end IDU2. no special requirements in HSBY balanced systems.
3.
If this requirement is not matched, the ATPC functionalities are lost. As in the 1+0 systems all the processing is done by the Tx CPU: from the far-end terminal only the Prx measure is sent (acknowledged 8 times) via both byte S22 and byte S32. HSBY Systems In HSBY systems, the local TX level depends on the remote RX power corresponding to the odu RX section selected (switch B closed). In the local NE, this RX measure will affect the TX level corresponding to the odu TX section selected (switch HSBY closed), no matter which dem was on-line in the remote (dem1 or dem 2): the algorythm manages all the possible combinations. FD Systems In FD systems the radio links are completely separate and independent: the radio link #1 RX level cannot affect the radio link #2 TX level and viceversa. The threshold values for ATPC parameters in case of IDU 32 TCM and IDU 128 QAM are reported in the following table (Tab. 6.16). Tab. 6.16 ATPC threshold values IDU 32 TCM ODU SRA (ATPC a step) THRESHOLD ON THRESHOLD OFF -65 dBm -50 dBm ODU NPL (ATPC lineare) -60 dBm IDU 128 QAM ODU SRA (ATPC a step) -57 dBm -45 dBm ODU NPL (ATPC lineare) -50 dBm
6-84
6.5.2.4
Ext EOW Status & Config window

Selecting External EOW in Unit menu (Fig. 6.112), the Ext EOW Status & Config window (Fig. 6.144) opens, where the user can configure the Phone Number parameter for the call using the external EOW unit present in the system.
Fig. 6.144
Ext EOW Status & Config window
Clicking twice on the insertion field, the related FIELD EDITING window (Fig. 6.145) opens, where the user can type the Phone Number desired value. Fig. 6.145 Phone Number configuration
6.5.3
Software Download menu

Software Download menu lists two commands which are used to manage the software present on SRA series 3 radio equipment: FTP Transfer, for the software download via FTP; Software Bank, for the switching between the active memory bank and the stand-by one.
Fig. 6.146
Software Download menu (for ODU SRA)
If ODUs NPL are configured on the equipment, the software download operations are manageable also on these ones. Fig. 6.147 Software Download menu (for ODU NPL)
6-85
6.5.3.1
FTP Transfer
The FTP Transfer command in Software Download > IDUs (or Software Download > ODU1 or Software Download > ODU2) menu (Fig. 6.146) is used to execute the download of the Controller unit software (Cap. 5).
6.5.3.2
Software Banks
Selecting Software Banks in Software Download > IDUs menu (Fig. 6.146), the IDU Software Banks window opens (Fig. 6.148). This window is used by the user during the procedure od download for the Controller unit software for IDU unit (Cap. 5).
Fig. 6.148
IDU Software Banks window
Selecting Software Banks in Software Download > ODU1 (or ODU2) menu (Fig. 6.141), the ODU Status and Configuration window (Fig. 6.144) opens to help the user in the download procedure of the Controller unit (Cap. 5) for ODU NPL unit. Fig. 6.149 ODU1 Software Banks window (ODU NPL)
In the upper part of this window, the Software Code and the Software Release for the software versions present on the IDU active and stand-by banks ad the related Checksum values are displayed. In the following part of the window, there are three push-buttons:
6-86
Copy to Stand-by Bank This command copies the content of the memory bank in the inactive Flash memory. The string Copy in progress with the indication of the percentage of the operation in progress is displayed. Switch to Stand-by Bank This command executes the switching to the stand-by memory bank. Banks Alignment This command copies the content of the active memory bank to the other memory bank. The string Copy in progress with the indication of the percentage of the operation in progrss is displayed.
In case of read only users, the Software Banks window is composed only by the upper part of the window shown in case of RW users. Furthermore, the checksum indication is not reported.
6.5.4
Date and Time

The configuration of the equipment date and time is an external application of Net Viewer/LCT program, that starts selecting the Date and Time command in the Status and Config menu (Fig. 6.3). The date and the time assume a particular importance in the execution and analysis of the measurements and recordings on the equipment (description of the quality and unavailability parameters). For the description of the procedures to configure the equipment date and time, refer to the OMN Manual of Net Viewer/LCT program.
6.5.5
Network menu
Network menu (Fig. 6.150) contains the commands which allows to manage the NE address and the routing table.
Fig. 6.150
Network menu
6.5.5.1
NE Parameters
Selecting NE Parameters in the Network menu (Fig. 6.150), the NE Parameters window (Fig. 6.151) opens, where the operator can configure the IP address and the Net Mask for the selected NE. The window presents a message which recommends the user to pay attention in this operation, because a wrong configuration of NE parameters can make the NE unreachable.
6-87
Fig. 6.151
NE Parameters window
To modify the values present in this window, click on Modify button: the fields switch to read/write mode and the button itself change name becoming OK. Fig. 6.152 NE Parameters window (write mode)
Clicking twice on IP Address field, the window for the insertion of IP address value (Fig. 6.153) opens, where the user can define the IP address. Fig. 6.153 Window for IP address value insertion
Clicking twice on Net Mask field, the window for the insertion of Net Mask value (Fig. 6.154) opens, where the user can define the Net Mask. Fig. 6.154 Window for Net Mask value insertion
6-88
6.5.5.2
Routing Table
Selecting Routing Table in the Network menu (Fig. 6.150), the Routing Table window (Fig. 6.156) opens, where the user can configure the three routing entry. The window presents a message which recommends the user to pay attention in this operation, because a wrong configuration of NE parameters can make the NE unreachable.
Fig. 6.155
Routing Table window (with not modifiable fields)
To modify the values present in this window, click on Modify button: the fields switch to read/write mode and the button itself change name becoming OK. Fig. 6.156 Routing Table window (with modifiable fileds)
Clicking twice on each Interface field, the window for the selection of the interface type (Fig. 6.157) opens. The user has three possible choices: Unconfigured; F-Interface; Q-Interface.
6-89
Fig. 6.157
Window for the selection of the interface type
Clicking twice on each Destination Network field, the window for the insertion of the destination network routing entry (Fig. 6.158) opens. Fig. 6.158 Window for the insertion of the Destination Network routing entry
Clicking twice on each Gateway field, the window for the insertion of the gateway routing entry (Fig. 6.159) opens. Fig. 6.159 Window for the insertion of Gateway routing entry
Clicking twice on the RIP by Q i/f field, the window for enabling/disabling the RIP opens. Select the desired value (Enabled or Disabled) and close with OK button to store the setting. After completing all the desired settings for the first Routing Entry, the Routing Table window appears as follows (Fig. 6.160). Fig. 6.160 Example of Routing Entry window
6-90
6.5.5.3
Edit NE menu
This menu allows the user to manage the network element configuration by means of the simple Copy and Paste command.
Fig. 6.161
Edit NE menu
The function for the loading/storing of the NE configuration file is available only for some radio equipments. Edit NE menu has the following commands: Copy: storing of the equipment configuration parameters in a file. Paste: configuring the equipment by means of the parameters present in the NE configuration file.
6.5.5.3.1 Copy command

Selecting Copy in the Edit NE menu (Fig. 6.161), the following window (Fig. 6.162) opens, where the user can define the file on which store the NE configuration to be pasted later. Fig. 6.162 Copy NE procedure (1/5)
To make this, the user must select the Browse button: the Destination File window (Fig. 6.163) opens, allowing the user to choose the file name and the directory where store the information.
6-91
Fig. 6.163
Copy NE procedure (2/5)
When the user press OK button, the copy procedure starts: the indication of the operation in progress appears in the lower part of the window (percentage) together with generic information about the procedure listed in the box above (Fig. 6.164, Fig. 6.165). If the user wants to stop the procedure before its end, he can select the Stop button. Fig. 6.164 Copy NE procedure (3/5)
Fig. 6.165
At the end of the procedure, the user can close the window (Fig. 6.166) by means of Close button and return to the main window to paste the configuration.
6-92
Fig. 6.166
6.5.5.3.2 Paste command

Selecting Paste in the Edit NE menu (Fig. 6.161), the following window (Fig. 6.167) opens, where the user can define the file to use for pasting the NE configuration. Fig. 6.167 Paste NE procedure (1/4)
To make this, the user must select the Browse button: the Source File window (Fig. 6.168) opens, allowing the user to choose the file name and the directory where the source file is stored. Fig. 6.168 Paste NE procedure (2/4)
At OK selection, the pasting operation starts, with the relevant indications in the PASTE NE CONFIGURATION window (Fig. 6.169, Fig. 6.170).
6-93
Fig. 6.169
Paste NE procedure (3/4)
Fig. 6.170
Paste NE procedure (4/4)
At the end of this procedure, all the configuration parameters stored in the file are pasted to the current NE. In the following table (Tab. 6.17) the configurations copied by the Copy NE function are reported, with their default values and range of interest.
6-94
Tab. 6.17 Data Type
Configurations copied by Copy NE function Function Values/Range Notes
System Type ODU 1 equipping ODU 2 equipping IDU 1 equipping IDU 2 equipping ATPC Management IDU 1 ATPC Mode IDU 1 DEFAULT Power IDU 1 ATPC Management IDU 2 ATPC Mode IDU 2 System DEFAULT Power IDU 2 Enable MS-AIS insertion trib_side MS-AIS trib enable MS-RDI trib enable HBER enable RPS EN TP 15 RPS EN TP day EOW EXT equipping ALS EN/DIS Q i/f RIP Disabling COMP_CABLE_MODE Enable/Disable Enable/Disable Auto/Manual Enabled/Disabled Automatic / Pnom / Pnom-8 dB Pnom / Pnom-8 dB Enabled/Disabled Automatic / Pnom / Pnom-8 dB Pnom / Pnom-8 dB Enable/Disable Enable/Disable Enable/Disable Enable/Disable Enable/Disable Enable/Disable Only DTI Only DTI Only DTI
6-95
Tab. 6.17 Data Type
Configurations copied by Copy NE function Function Values/Range 10E-5...10E-9 Enabled/Disabled Disabled / G.703 / V.11 Enabled/Disabled Enabled/Disabled 1...100 1...100 10E-5...10E-9 Enabled/Disabled 1...100 1...100 Enabled/Disabled Enable/Disable Enable/Disable Enable/Disable Enable/Disable Enable/Disable Enable/Disable Enable/Disable ON/Off Enabled See Tab. 6.9 and Tab. 6.10 Enable/Disable Optical IDU Tributary side Tributary side Tributary side Tributary side Radio side Radio side Radio side Radio side Radio side Notes Tributary side
B1 Threshold TX WS En/Dis F1 INSERT J0 Management TX AIS INS ON TIM TX TIM Activation Interval TIM Disactivation Interval B1 Threshold RX J0 Management RX TIM Activation Interval TIM Disctivation Interval IDU AIS INS ON TIM TX RST TRIB EN TP 15 RST TRIB EN TP day RST RADIO EN TP 15 RST RADIO EN TP day RSPI EN TP 15 RSPI EN TP day E1 management en/dis RLTS2 Threshold LASER FORCING RIP Disable/Enable TCN Threshold On/Off ALS ODU FREQ_MODE
The use of the NE configuration files, stored on PC or on a central archive, has two functions: to make available some backup copies of the equipment configuration, to allow a fast reset of the equipment in case of loss of the configuration; to make available different basic configuration, so facilitating and reducing the operations related to the configuration of the connected equipment.
For a more complete description of the commands and of the procedure to operate on the equipment configuration files, refer to the NetViewer/LCT OMN Manual.
6-96
6.6 Alarms menu

Alarms menu (Fig. 6.171) allows to check the status of the equipment alarms and, then, to determine the cause of a possible malfunction. Any interface alarm between boards (TX or RX interface fail) can be detected only in the RX section, but it could be due to other side. Then, since the source cannot be known, it is necessary to alarm both the faults of involved boards. Alarms menu offers the following options: Functional: alarms related to the SDH signal; Physical: alarms related to hardware malfunctions on the equipment; Station: alarms related to station components external to the equipment; Severity: list of alarms, divided according the severity class; TCN: it allows to access the windows for the configuration of the threshold crossing notification values.
Fig. 6.171
Alarms menu
In the alarm windows, the outbreak of a malfunction is signalled by the accension of the related alarm signalling with the preset colour (generally red) and by the displaying of the ! symbol (before the alarm acronym).
6.6.1
Functional menu
Selecting Functional in Alarms menu (Fig. 6.171), the following options are available (Fig. 6.174): STM-1 Payload; AUX and Control Channels.
In case of (1+0) system type equipments, this choice can be made for each of the two channel present in the system (Fig. 6.173). Fig. 6.172 Functional menu (1+1 system types)
6-97
Fig. 6.173
Channel 1 menu (1+1 system types)
Fig. 6.174
Functional menu (1+0 system type)
6.6.1.1
STM-1 Payload
Selecting the STM-1 Payload command in Functional menu (Fig. 6.174) or in Channel 1 / Channel 2 menu (Fig. 6.173) , the STM-1 Payload Functional Alarms window (Fig. 6.175) opens. In this window, the alarm signallings present on the tributary side (Trib Side), on radio side (Radio Side) and the operational status (Op Status) of the SPI, RST and RSPI sections are reported. The two boxes on the left represent the IDU unit, while the two on the right represent the ODU unit. The position of the alarm signallings in the window allows to assign each alarm to the interested logic section of the equipment. The possible indications, relative to the light signallings of the alarm statuses and green (normal) and red (fault). the operational statuses, are:
Fig. 6.175
STM-1 Payload Functional Alarms window
6-98
Status indications (tributary and radio side) SPI it is the operational status of the SDH physical interface; RST it is the operational status of the Regenerator Section Termination; RSPI it is the operational status of the Radio Synchronous Physical Interface.
Alarm indications on tributary side LOS Trib, this is an alarm relative to the board of tributary interface and indicates the Loss Of Signal on tributary side. This alarm can be issued by a loss of the clock signal or by payload missing. LOF Trib, this is an alarm relative to the main board and indicates the Loss Of SDH Frame on tributary side. B1 SD Trib, this is an alarm relative to the main board and indicates that the set threshold of signal degrade related to byte B1 on tributary side has been exceeded. Range for threshold setting: 10-5 - 10-9 (default: 10-5). TIM Trib, this is an alarm relative to the main board and indicates a mismatch between the expected J0 byte and the received J0 byte (dropped) on tributary side. The user can configure the indoor unit acting on the J0 Expected TX and the J0 Inserted TX for the tributary side. The received value is restituted by J0 Dropped TX measure. MS-RDI, this is an alarm relative to the board of tributary interface and indicates a remote malfunctioning on the Multiplex Section. MS-AIS, this is an alarm relative to the board of tributary interface and indicates that an AIS signal is present on the Multiplex Section. AIS Inserted, this is an alarm relative to the board of tributary interface and indicates that an AIS signal has been inserted by the equipment on tributary side.
Alarm indications on radio side AIS Inserted this is an alarm relative to the main board and indicates that an MS-AIS signal has been inserted by the equipment on radio side. LOF Radio this is an alarm relative to the main board and indicates the Loss Of SDH Frame on radio side. B1 SD Radio this is an alarm relative to the main board and indicates that the set threshold of
6-99
signal degrade related to byte B1 on radio side has been exceeded. Range for threshold setting: 10-5 - 10-9 (default: 10-5). TIM Radio this is an alarm relative to the main board and indicates a mismatch between the expected J0 byte and the received J0 byte (dropped) on radio side. The user can configure the indoor unit acting on the J0 Expected RX and the J0 Inserted RX for the tributary side. The received value is restituted by J0 Dropped RX measure. LOF RFCOH this is an alarm relative to the radio interface board and indicates the loss of the radio frame in input. H-BER this is an alarm relative to the modem board and indicates that a BER equal to 10-6 is present on the signal incoming from radio side. EW this is an alarm relative to the modem board and indicates that a BER equal to 10-9 is present on the signal incoming from radio side. RF LOS this is an alarm relative to the equipped ODU unit. It indicates that ODU has received no RF signal.
If the operational status (Op Status) of a functional unit is faulted (red led on), the alarm signallings related to that functional unit can be meaningless, that is the green leds dont rule out the presence of alarms on SDH signal: a more careful check on the interested unit is required.
6.6.1.2
AUX and Control Channels

Selecting AUX and Control Channels in Functional menu (Fig. 6.172) or in Channel 1 / Channel 2 menu (Fig. 6.173), the AUX and Control Channel Functional Alarms window (Fig. 6.176) opens. In this window, the operational statuses (Op Status) of SPI, RST and RSPI sections of the IDU unit (Trib Side) and ODU unit (Radio Side) are reported, together with the alarm signallings of the User and Way-Side channels of RST section of IDU. The position of the alarm signallings in the window allows to assign each alarm to the interested logic section of the equipment. The possible indications, relative to the light signallings of the alarm statuses and the operational statuses, are: green (normal) and red (fault).
6-100
Fig. 6.176
AUX and Control Channel Functional Alarms window
The AUX Functional alarms for the Slave IDU (1 or 2) are not active.
Status indications (tributary and radio side) SPI it is the operational status of the SDH physical interface; RST it is the operational status of the Regenerator Section Termination; RSPI it is the operational status of the Radio Synchronous Physical Interface. EOW Int Channel (E1 Byte), it is the operational status of the EOW internal channel; EOW Ext Channel (E1 Byte), it is the operational status of the EOW external unit; User Channel (F1 Byte), it is the operational status of the F1user channel; Way Side Channel, it is the operational status of the Way-Side channel.
Alarm indications on User Channel (byte F1) LOS this alarm is issued by the loss of signal on F1 byte auxiliary channel.
Alarm indications on Way-Side Channel LOS this alarm is issued by the loss of signal on the WS auxiliary channel. AIS Inserted User Side this is an alarm relative to the main board and indicates that an AIS signal has been inserted by the equipment on User channel in the frame in output on radio side. AIS Inserted Radio Side this is an alarm relative to the main board and indicates that an AIS signal has been
6-101
inserted by the equipment on Way-Side channel in the frame in output on radio side. If the operational status (Op Status) of a functional unit is faulted (red led on), the alarm signallings related to that functional unit are meaningless, that is the green leds dont rule out the presence of alarms: a more careful check on the interested unit is required.
6.6.2
Physical
Selecting Physical in Alarms menu (Fig. 6.171), the Equipment User Physical Alarms window (Fig. 6.177) opens, where the operational statuses of IDU(s), ODU(s), external EOW, backup hardware key and optical Heater are reported, together with the connection status between the two units. In case of hardware fault, all the physical alarms related to the involved hardware will be made inactive. The possible indications, relative to the light signallings of the alarm statuses and green (normal) and red (fault). the operational statuses, are:
Fig. 6.177
Equipment User Physical Alarms window (1+0 system type)
Fig. 6.178
Equipment User Physical Alarms window (1+1 system types)
In case a fault in the operational status is signalled on one or on both the units, it is possible, by means of button More, to access to the window related to the alarms present on the sigle units (Fig. 6.179, Fig. 6.180).
6-102
6.6.2.1
IDU Maintenance Physical Alarms window

Selecting the More button in the box related to IDU (or IDU1 or IDU2) unit in Equipment User Physical Alarms window (Fig. 6.178), the IDU Maintenance Physical Alarms window (Fig. 6.179) opens.
Fig. 6.179
IDU 1 Maintenance Physical Alarms window ((1+1) system type)
The alarm signalling are divided according to the physical units inside the IDU. General alarm signallings CPU Alarm this alarm signals the presence of a communication problem occurred between the CPU and at least of the units inside the IDU. green (normal) and red (fault). The possible indications are: Power Supply this alarm signals the presence of a fault in IDU power supply. The possible indications are: green (normal) and red (fault). Laser Transmit (for optical IDU) this alarm signals the failure of the STM-1 transmission by the tributary optical interface, due to a unit fault. green (normal) and red (fault). The possible indications are:
Alarm signallings on Payload Boards SDH Trib Board this alarm signals the presence of a fault on the SDH physical interface board. green (normal) and red (fault). The possible indications are: Main Board this alarm signals the presence of a fault on IDU main board. The possible indications are: green (normal) and red (fault). Modem Board this alarm signals the presence of a fault on IDU modem board. green (normal) and red (fault). The possible indications are: IF Board this alarm signals the presence of a fault on IF board. green (normal) and The possible indications are:
red (fault).
6-103
Alarm signallings on AUX Boards Way Side Ch Board this alarm signals the presence of a fault on the Way Side board. green (normal) and red (fault). The possible indications are: User Ch Board this alarm signals the presence of a fault on the User board. The possible indications are: green (normal) and red (fault). Internal EOW this alarm signals the presence of a fault on the internal EOW communication green (normal) and red (fault). channel. The possible indications are:
Alarm signallings on IDU-ODU interface IDU-ODU i/f this alarm signals the presence of a fault on the interface between the two units. The possible indications are: green (normal) and red (fault).
Cable alarms (only for 1+1 system types) Data Exp Cable Fault this alarm signals the presence of one of the two following conditions: IDU cannot communicate with its mate IDU; the hardware reports loss of clock signal from the other IDU. The possible indications are: green (normal) and red (fault).
6.6.2.2
ODU Maintenance Physical Alarms window

Selecting More button in the box related to ODU unit in Equipment User Physical Alarms window (Fig. 6.178), the ODU Maintenance Physical Alarms window (Fig. 6.180) opens.
Fig. 6.180
ODU Maintenance Physical Alarms window (ODU SRA)
The alarm signallings are divided according to the physical units present in ODU unit.
6-104
ODU SRA alarm signallings Power Supply this alarm signals the presence of a fault in the power supply of the ODU unit. green (normal) and red (fault). The possible indications are: Synthetizer this alarm signals the presence of a fault in the ODU synthetizer. The possible indications are: green (normal) and red (fault). TX Amplifier this alarm signals a fault of the transmitter amplifier in the external cabinet (the output power of the transmitter has an incorrect value). green (normal) and red (fault). The possible indications are: TX Oscillator this alarm signals the presence of a fault in the transmission local oscillator. green (normal) and red (fault). The possible indications are: RX Oscillator this alarm signals the presence of a fault in the reception local oscillator. green (normal) and red (fault). The possible indications are: Hot-Stby Switch (only for (1+1) Hot Standby system types) this alarm signals the presence of a fault in the switching operation. The possible indications are: green (normal) and red (fault).
Fig. 6.181
ODU Maintenance Physical Alarms window (ODU NPL)
ODU NPL alarm signallings Power Supply This alarm signals the presence of a fault in ODU unit power supply. The possible green (normal) and red (fault). indications are: TX Section This alarm signals the presence of a fault in ODU transmission section. The possible indications are: green (normal) and red (fault). RX Section This alarm signals the presence of a fault in ODU reception section. The possible green (normal) and rred (fault). indications are: TX HSBY This alarm signals the presence of a fault in ODU switching operation. The possible green (normal) and red (fault). indications are:
6-105
Alarm signallings on IDU-ODU interface IDU-ODU i/f this alarm signals the presence of a fault on the interface between the two units. green (normal) and red (fault). The possible indications are:
6.6.2.3
System Maintenance Physical Alarms window (only (1+1) S.T.)

Selecting More button in the lower right corner of the Equipment User Physical Alarms window (Fig. 6.177), the System Maintenance Physical Alarms window (Fig. 6.182) opens.
Fig. 6.182
System Maintenance Physical Alarms window
This window list the alarms signalling related to the whole system: Data Exp Cable Fault, this alarm signals a fault to the data cable connecting the two IDUs. The switches are frozen in the current status. green (normal) and red (fault). The possible indications are: Data Exp Cable Missing, this alarm signals the data cable connecting the two IDUs is missing or is not correctly connected. The system passes to the (1+0) master configuration and it is forced in this condition until the cable is re-inserted. green (normal) and red (fault). The possible indications are: IDU Software Mismatch, this alarm signals a mismatch between the software values of the two IDUs. The possible indications are: green (normal) and red (fault). IDU Hardware Mismatch, this alarm signals a mismatch between the hardware values of the two IDUs. green (normal) and red (fault). The possible indications are: System Switches Frozen, this alarm signals that the status of the switches in the system has been frozen. green (normal) and red (fault). The possible indications are: System Frozen in 1+0 Master Config, this alarm signals that the system is forced to operate in 1+0 configuration. The possible indications are: green (normal) and red (fault). IDU1 Main Battery, this alarm signals a problem to the IDU1 Main Battery. This alarm is meaningful
6-106
only for (1+1) system type configurations. The possible indications are: green (normal) and
red (fault).
IDU2 Main Battery, this alarm signals a problem to the IDU2 Main Battery. This alarm is meaningful only for (1+1) system type configurations. green (normal) and red (fault). The possible indications are: ODU Switch Mismatch, This alarm occurs in case of a mismatch between the command sent by the IDU and the switch status restituted by the ODU. It is meaningful only for (1+1) Hot-Stby system type configurations. green (normal) and red (fault). The possible indications are: I2C Bus Fail, this alarm signals the disconnection of the I2CBUS interface. The possible indications are: green (normal) and red (fault). External EOW Presence, this alarm signals the presence or the absence of the external EOW unit. The green (normal) and red (fault). possible indications are:
6.6.3
Station
Selecting Station in Alarms menu (Fig. 6.171), the Station Alarms window (Fig. 6.183) opens, where the station alarm signalling (max 4) are reported. Each alarm can be defined by the user in the External Setting window (Fig. 6.108). The possible indications are: green (normal) and red (fault).
Fig. 6.183
Station Alarms window
Generally the Station Alarms signal problems related to the station where the network element is located (for example: fire, open door, ecc...).
6-107
6.6.4
Severity
Selecting Severity in Alarms menu (Fig. 6.171), the window Severity Alarms window (Fig. 6.184), where the alarms are divided according to the severity class which they green (normal) and red (fault). belong to. The possible indications are:
Fig. 6.184
Severity Alarms window
Each alarm class is provided with a light signalling, which indicates the activation of one or more alarms related to it. Cliking on More buttons, a different window for each severity class opens. For the description of each alarm listed in the previous windows, refer to the paragraphs before in this chapter (the alarms are divided according to the logic group they belong to and not according to severity).
6.6.4.1
Fig. 6.185
Critical Alarms window

Critical Alarms window ((1+0) system type, ODU NPL)
In the two following windows reporting the list of the Critical alarms (Fig. 6.186, Fig. 6.187), the ODU Switch Mismatch signalling is not present in case of (1+1) Hetero Frequencies system types.
6-108
Fig. 6.186
Critical Alarms window ((1+1) HSBY STI system type)
Fig. 6.187
Critical Alarms window ((1+0) ODU SRA system types)
6.6.4.2
Minor Alarms window

In the following window reporting the list of the Minor alarms (Fig. 6.188), the part related to IDU2 is not present in case of (1+0) system type configuration and the IDU-ODU i/f alarm signalling is not present in case of (1+1) Hot-Stby system type configurations.
Fig. 6.188
Minor Alarms window ((1+1) system type)
6-109
Fig. 6.189
Minor Alarms window ((1+0) system type)
6-110
6.6.4.3
Major Alarms window

In the two following windows reporting the list of the Major alarms (Fig. 6.190, Fig. 6.191), the Hot-Stby Switch alarm signallings are not present in case of (1+1) Hetero Frequencies system type configurations.
Fig. 6.190
Major Alarms ((1+1) DTI system types with optical IDU)
Fig. 6.191
Severity Alarms window - MAJOR (system type 1+1 STI, electrical IDU)
6-111
6.6.4.4
Warning Alarms window

In the two following windows reporting the list of the Warning alarms (Fig. 6.192, Fig. 6.193), the B1 Signal Degraded Trib/Radio Side alarm signallings related to IDU2 are not present in case of (1+1) STI system type configurations.
Fig. 6.192
Warning Alarms window ((1+1) system types)
Fig. 6.193
Warning Alarms window ((1+0) system type)
6-112
6.6.4.5
Fig. 6.194
Test window
TEST window
6.6.5
TCN menu
Selecting TCN > IDU1 o TCN > IDU2 in Alarms menu (par. 6.6), the user can display the TCN status for the different counters on each section (RST Radio, RST Trib, RSPI, BER-RSPI, RPS) related to IDU1 (Fig. 6.196) or to IDU2 (Fig. 6.197).
Fig. 6.195
TCN menu
The signallings are referred to two different intervals: 15 minutes or 24 hours. In case of alarm notification, the correspondent light signalling switches from green (no alarm) to red (alarm). Fig. 6.196 IDU 1 TCN Alarms window
6-113
Fig. 6.197
IDU 2 TCN Alarms window
6-114
6.7 Measurements menu

Measurements menu (Fig. 6.198) allows to monitor the equipment performances and to record the trend of the transmission power as function of time. It has the following items: Fig. 6.198 Measurements menu
6.7.1
Performance menu
Performance menu allows the following choices to the user:
Fig. 6.199
Performance menu - IDU1 (S.T. 1+1)
Fig. 6.200
Performance menu - IDU2 (S.T. 1+1)
In Performance menu (Fig. 6.199), the user can select the interested type of performance monitoring with the correspondant timescale (performance on quarter or on day). The Performance Monitoring window related to quarters (Fig. 6.203) shows the results of measurements of the current quarter and of the previous sixteen quarters. It is managed by the following rules: the day is composed by 6 blocks, each of these of 4 hours: (0:00 - 4:00), (4:00 8:00), (8:00 - 12:00), (12:00 - 16:00), (16:00 - 20:00), (20:00 - 24:00); the measurement related to the current period is the lower part of the window. Starting from the top, the already counted quarters of the 4 hours current block are listed: these replace, row by row, the quarters of the previous 4 hours block.
The performance function allows to display on PC: the quality parameters calculated according to the following recommendations: ITU-T G.829 (draft) for the incoming B1 bytes (tributary side for Tributary unit and line side for Demodulator unit) the unavailability parameters of the radio link estimated according to the ITU-T G.827 recommendation.
6-115
The performance monitoring is executed only on point-to-point links. The approach is monodirectional, because the two direction of the connection are considered as separated. In fact, the counting of the quality parameters relative to the A->B direction of a A - B connection is executed for all the periods during which the connection in this direction is available, without considering the availability, or not, in the B->A direction.
6.7.1.1
Quality and unavailability parameters (RST)

In each Quarter or Day window, the data provided for the user (Performance Monitoring window - Quarter, Performance Monitoring on B1 Byte - Day window) are the following ones: UAS (Number of Seconds of Unavailability): it provides the unavailability seconds of connection into a specified observation period. SES (Number of Severely Errored Seconds): it provides the seconds, for which one of the following conditions is present: percentage of errored blocks equal to or higher than 30% presence of at least one particular event called defect (the defect classification for the single units is reported in the following paragraphs). ES (Number of Errored Seconds): it provides the seconds where the presence of at least one errored block occurs. BBE (Number of Background Block Errors): it provides the number of errored blocks into a not SES second. OI (Number of Outage Intensity): it provides the number of unavailability events into a specific observation period.
The counting of the quality parameters (SES, ES, BBE) is displayed on video and of the unavailability ones (UAS, OI) for the current quarter of hour/24 hours and for the preceeding 16 quarters of hour/4 days. It is then provided the number of seconds counted by the slave into each of the nominal quarters of hour/24 hours; this operation allows a correct evaluation of performances seen not as an absolute measure, but as a measure relevant to a period with a well known duration. The defects (LOS, LOF, AIS alarms) considered in the SES evaluation are valid after 1 reading where the alarm is active, that is, if they have a minimum duration of 20 ms. The time measuring unit is the second. The measure of the quarter of an hour has an allowance of 1 second. The measure of the 24 hours has an allowance of about 10 seconds. The 24 hours start and finish at 0:00. It is necessary to take into account that a drift of the measures can be present, caused by the allowance of the quartzs equipped into the several units. The internal time reference is provided by the Controller unit. The equipment Controller unit can be synchronized to the local PC, to which it is connected, at customers request. If the connection with supervision system is active, the equipment synchronization can be executed by means of supervision network. If the connection to PC is absent at the starting up time, the Controller unit sets its time to 0:00 of 1/1/1990. In the case of equipment connected to supervision system, the tollerance on the 24 hours measure depends on the frequency and on the precision of the synchronization between the supervision system and the Controller unit. The maximum frequency used
6-116
by supervision system to synchronize the equipment is 4 days (in normal functioning condition). Roots of suspect windows : RST trib: ref clock change RST radio: ref clock change RSPI: ref clock change ; FSK lof; additional RSPI : none slave PM: CPUs comm. loss
PM vs HW faults Master IDU: RST PM (Trib side and Radio side) / RSPI additional PM: No special treatment needed to deal with HW faults. There is no case of 'suspect window' due to HW faults. RSPI PM: HW faults in the Rx chain should not affect RLTS counter (RLTS is related to the RL measured at the antenna port). HW faults in the Tx chain should affect RLTS counter: when the ODU is not transmitting, do not count TLTS. A 'suspect window' will be due to FSK LOF alarm. Slave IDU: For all PM measures (RST, RSPI standard/ additional), suspect window will be due to CPU COMM. alarm (communication loss between CPUs). RPS: all the switching counters (Trib, Dem, ODU) are managed the PSAC will count for every actual switch in both directions (non revertive switching) there is no case of 'suspect window' due to HW faults (the CPU COMM alarm does not cause 'suspect window' in this case, since a proper communication between the CPUs is one of the conditions for the actual switch).
The second in which a defect has happened must be considered as a SES second. On the following are listed the defects: Line side: LOF RX, TIM RX, DEM FAIL. Tributary Side: LOS TX, LOF TX, TIM TX.
6-117
6.7.1.2
RPS menu
Selecting RPS in Performance menu (Fig. 6.199), a menu (Fig. 6.201) opens with the following options: Quarter; Day.
Fig. 6.201
RPS menu
Selecting Quarter, the RPS Performance Monitoring - Quarter window (Fig. 6.202) referred to quarters, for displaying the RPS performances (according to the quality and unavailability parameters) opens. Fig. 6.202 RPS Performance Monitoring - Quarter
Selecting Day, the RPS Performance Monitoring - Day window (Fig. 6.203) referred to the 24 hours, for displaying the performances (according to the quality and unavailability parameters), opens. Fig. 6.203 RPS Performance Monitoring - Day
6-118
6.7.1.3
RST Trib Side menu

Selecting RST Trib Side in Performance menu (Fig. 6.199), a menu (Fig. 6.204) opens with the following options: B1 Quarter; B1 Day; B1 Record.
Fig. 6.204
RST Trib Side menu
Selecting Quarter, the Performance Monitoring (RST Trib Side) window (Fig. 6.205) referred to quarters, for displaying the performances (according to the quality and unavailability parameters) of the RST section, on tributary side. Fig. 6.205 Performance Monitoring (RST Trib Side) window - Quarter
Selecting Day, the Performance Monitoring (RST Trib Side) window (Fig. 6.206) referred to the 24 hours, for displaying the performances (according to the quality and unavailability parameters) of the RST section, on tributary side. Fig. 6.206 Performance Monitoring (RST Trib Side) window - Day
Selecting Record in RST Trib Side menu (Fig. 6.204), an external application of Net Viewer/LCT program is started, allowing to record the performances for possible following processings.
6-119
The Excel program is necessary to display, in table format, the performances recorded on file. For the description of the recording procedures and the windows involved in the procedures themselves, refer to the OMN Manual of the Net Viewer/LCT program.
6.7.1.4
RST Radio Side menu

Selecting RST Radio Side in Performance menu (Fig. 6.199), a menu (Fig. 6.207) opens with the following choices: B1 Quarter; B1 Day; B1 Record.
Fig. 6.207
RST Radio Side menu
Selecting Quarter, the Performance Monitoring (RST Radio Side) window (Fig. 6.208) referred to quarters, for displaying the performances (according to the quality and unavailability parameters) of the RST section, on radio side. Fig. 6.208 Performance Monitoring (RST Radio Side) window - Quarter
Selecting Day, the Performance Monitoring (RST Radio Side) window (Fig. 6.209) referred to the 24 hours, for displaying the performances (according to the quality and unavailability parameters) of the RST section, on tributary side.
6-120
Fig. 6.209
Performance Monitoring (RST Radio Side) window - Day
Selecting Record in RST Radio Side menu (Fig. 6.207), an external application of Net Viewer/LCT program is started, allowing to record the performances for possible following processings. The Excel program is necessary to display, in table format, the performances recorded on file. For the description of the recording procedures and the windows involved in the procedures themselves, refer to the OMN Manual of the Net Viewer/LCT program.
6.7.1.5
RSPI menu
Selecting RSPI in Performance menu (Fig. 6.199), a menu (Fig. 6.210) opens allowing one of the following choices: Quarter; Day.
The RSPI counters have the same strategy as the RST PM counters: ES - a one second period in which the estimated BER measure is less than a threshold (1E-10), or at least one defect occurred. SES - a one second period in which the estimated BER measure is less than a threshold (1E-6), or at least one defect occurred.
Fig. 6.210
RSPI menu
Selecting Quarter, the Performance Monitoring (RSPI) window (Fig. 6.211) referred to quarters opens, displaying the performances (according to the quality and unavailability parameters).
6-121
Fig. 6.211
Performance Monitoring (RSPI) window - Quarter
Selecting Day, the Performance Monitoring (RSPI) window (Fig. 6.212), referred to the 24 hours, opens for displaying the performances (according to the quality and unavailability parameters) of the RSPI. Fig. 6.212 Performance Monitoring (RSPI) window - Day
In both cases, the following measures are present: RLTS1: it indicates the number of seconds during which the received power is less than the presetted (by user) value RLTS1; RLTS2: it indicates the number of seconds during which the received power is less than the value RLTS2 (not settable); TLTS1: it indicates the number of seconds during which the transmitted power is greater than the presetted (by user) value TLTS1; Suspect: it indiscates if the interval is supect or not; Number of seconds: it is the total number of seconds of the measure.
On reception side, there are two thresholds: RLTS1 and RLTS2. If also the more restrictive threshold (RLTS1) is exceeded, however the counters of the other threshold (RLTS2) continue to count. The ranges of values for these parameters are the following: range for RLTS1: -66 dBm / -80 dBm;
6-122
range for TLTS1: +10 dBm / +17 dBm.
As regards TLTS1, there are only two allowed values for the transmitted power. So, setting a value between +10 dBm and +17 dBm creates the same result.
6.7.1.6
BER RSPI menu

Selecting BER RSPI in Performance menu (Fig. 6.199), a menu (Fig. 6.213) opens allowing one of the following choices: Quarter; Day.
Fig. 6.213
BER-RSPI menu
Selecting Quarter, the Performance Monitoring (BER-RSPI) window (Fig. 6.214) referred to quarters, for displaying the performances (according to the quality and unavailability parameters). Fig. 6.214 Performance Monitoring (BER-RSPI) window - Quarter
Selecting Day, the Performance Monitoring (BER-RSPI) window (Fig. 6.215) referred to the 24 hours, for displaying the performances (according to the quality and unavailability parameters).
6-123
Fig. 6.215
Performance Monitoring (BER-RSPI) window - Day
Selecting Summary in the Performance menu, the Event Presence Summary window (par. 6.216) opens, with the collection of the performance data recorded during the last 5 days and 16 quarters (of the current day), for IDU1 and IDU2 units. Fig. 6.216 Event Presence Summary window
The disabled TPs dont concur in activating any data presence.
6-124
6.7.2
Unit
Selecting Unit in Measurement menu (Fig. 6.198), the Unit Measures window (Fig. 6.217) opens. This read-only window is divided in two parts: the first is related to IDU unit and the second to ODU unit. In case of (1+0) system types, the area of the window related to IDU2 and to ODU2 is not present.
Fig. 6.217
Unit Measures window (ODU SRA)
Parameter displayed in IDU section: Radio Side BER: error rate on radio side.
The RSPI counters have the same strategy as the RST PM counters: ES - a one second period in which the estimated BER measure is less than a threshold (1E-10), or at least one defect occurred. SES - a one second period in which the estimated BER measure is less than a threshold (1E-6), or at least one defect occurred.
Parameters displayed in ODU section (SRA): Fig. 6.218 RX Power: value of the power in reception (dBm); TX Power: Pnom or Pnom-8 (dBm).
Unit Measures window (ODU NPL)
Parameter displayed in ODU (NPL) section: ODU Type: the type of ODU NPL present in the system (32 or 128 states);
6-125
RX Power: value of the reception power (in dBm); TX Power: value of the transmission power (in dBm); RX Power min: minimum value (in dBm) of the power received from when the equipment has been switched on; RX Power min: maximum value (in dBm) of the power received from when the equipment has been switched on; Pmin: it defines the minimum level which the transmission power can set to (in dBm); Pmax: it defines the maximum level which the transmission power can set to (in dBm); TX Frequency min: minimum value of the transmission RF frequency, referred to the carrier (in GHz); TX Frequency max: maximum value of the transmission RF frequency, referred to the carrier (in GHz); RF Band: it displays the band of the radio frequency signal (in GHz); Shift: it display the gap between the radio frequency in transmission and the one in reception (in KHz).
6.7.3
Fig. 6.219
RF RX Power REC menu

RF RX Power REC menu
Selecting ODU 1 or ODU 2 in RF RX Power REC menu of Measurement menu, the RF RX Power window opens. In case of (1+0) system types, the RF RX Power Rec command directly opens the RF RX Power window. RF RX Power command run an external application of Net Viewer/LCT program, which allows to execute the measure of RF RX power for the system. The measured data are stored in text file xxxxx.odu. Pressing Show during the data recording, together with the saving of the data to the text file, Excel program opens, displaying a graph with the data of file xxxxx.odu. The graph is not automatically saved/created: if Cancel is pressed during the recording, only the text file is saved. Then, if the user wants to save the graph, he must do this operation before exiting Excel. For the description of the measurement procedure, refer to the OMN Manual of Net Viewer/LCT program.
6-126
6.8 Inventory menu

Inventory menu (Fig. 6.220) allows to access to the inventory data (stored in EEPROM) of the equipment unit, to read them or to write possible notes (ex.: commissioning data, type of malfunction, ecc.) and to record them. It shows the following options. Fig. 6.220 Inventory menu
PID menu item is present only in case of ODU NPL.
6.8.1
Hw/Sw
Selecting Hw/Sw in Inventory menu (Fig. 6.220), the Hardware & Software Inventory window (Fig. 6.221) opens, displaying the software and hardware inventory data of the units present in the system.
Fig. 6.221
Hardware & Software Inventory window
Unit parameters (Unit) Hardware Code: hardware code of IDU (IDU1 and IDU2 for 1+1 system types) unit, of ODU (ODU1 and ODU2 for 1+1 system types), of the Key and of the external EOW unit (EOW Ext); Software Code: software code of IDU (IDU1 and IDU2 for 1+1 system types) unit, of ODU (ODU1 and ODU2 for 1+1 system types), of the Key and of the external EOW unit (EOW Ext); Software Release: software release code of IDU (IDU1 and IDU2 for 1+1 system types) unit of ODU (ODU1 and ODU2 for 1+1 system types), and of the Key.
6-127
Net Viewer/LCT parameters Software Code: software code of engine program (Engine) and of plug-in program (Plug-in); Software Release: software release of engine program (Engine) and of plug-in program (Plug-in).
6.8.2
User menu
Selecting User in the Inventory menu (Fig. 6.220), the following options are possible:
Fig. 6.222
User menu
The user can write the inventory data regarding the IDU unit, the ODU NPL unit or the external EOW unit.
6.8.2.1
IDU unit inventory data

It is possible to insert, for the IDU unit of the equipment, some informations and annotations, which are written in the EEPROM and, then, can be read in any moment. To write the unit data, you must act in the following way: Select IDU in User menu (Fig. 6.222): the IDU User Inventory window (Fig. 6.223) opens; Clicking twice on the data field; the insertion window (Fig. 6.224) opens; Insert, by keyboard, the data in the insertion field and click on OK to confirm the written data.
Fig. 6.223
User Inventory window (1+1 system type)
6-128
Fig. 6.224
FIELD EDITING window for IDU User Inventory (example)
6.8.2.2
ODU unit inventory data

It is possible to insert, for the ODU unit of the equipment, some informations and annotations, which are written in the EEPROM and, then, can be read in any moment. To write the unit data, you must act in the following way: Select ODU in User menu (Fig. 6.222): the ODU User Inventory window (Fig. 6.225) opens; Clicking twice on the data field; the insertion window (Fig. 6.226) opens; Insert, by keyboard, the data in the insertion field and click on OK to confirm the written data.
Fig. 6.225
ODU User Inventory window
Fig. 6.226
Finestra FIELD EDITING per User Inventory
6-129
6.8.2.3
External EOW unit inventory data

It is possible to insert, for the external EOW unit, some informations and annotations, which are written in the EEPROM and, then, can be read in any moment. To write the unit data, you must act in the following way: Select External EOW in User menu (Fig. 6.222): the EOW User Inventory window (Fig. 6.227) opens; Clicking twice on the data field; the insertion window (Fig. 6.228) opens; Insert, by keyboard, the data in the insertion field and click on OK to confirm the written data.
Fig. 6.227
EOW User Inventory window (1+0 system type)
Fig. 6.228
FIELD EDITING window for EOW User Inventory
6.8.3
Factory Data menu

Selecting Factory Data in Inventory menu (Fig. 6.220), the following options are available (Fig. 6.229):
Fig. 6.229
Factory Data menu
The user can choose to read the inventory data of IDU unit, of the hardware key or of the external EOW unit. SRA ODU has not the Factory Data.
6-130
6.8.3.1
IDU
The following data can be acquired and displayed for the IDU unit of the equipment: Hardware Code, extension and issue Serial Number; MAC Address; Manufacturer; Manufacturing Site; Manufacturing Business Unit; Date of Commissioning (year and month).
To read the IDU factory data, select Factory Data in Inventory menu (Fig. 6.220) and, then, select IDU. The IDU Factory Data window opens (Fig. 6.230). Fig. 6.230 Factory Data window
6.8.3.2
Hardware Key
The following data can be displayed for the equipment hardware key: Hardware Code, extension and issue Serial Number; Manufacturer.
To read the factory data of the hardware key, select Factory Data in Inventory menu and, then, select Key. The Key Factory Data window (Fig. 6.231) opens. Fig. 6.231 Key Factory Data window
6-131
6.8.3.3
EOW external unit

The following data can be acquired and displayed for the EOW external unit: Hardware Code, extension and issue Serial Number; Manufacturer; Manufacturing Site; Manufacturing Business Unit; Date of Commissioning (year and month).
To read the factory data of the external EOW unit, select Factory Data in Inventory menu (Fig. 6.220) and, then, select External EOW. The External EOW Factory Data window opens (Fig. 6.232). Fig. 6.232 External EOW Factory Data window
6.8.4
PID
To read the factory data of the ODU NPL unit, select PID in Inventory menu (Fig. 6.220): the ODUs PID window (Fig. 6.233) opens.
Fig. 6.233
ODU PID window (S.T. (1+1))
The following data can be get and displayed for the ODU unit: Hardware Code; Serial Number; Manufacturer;
6-132
Manufacturing Site; Manufacturing Business Unit; Date of Commissioning; Equipment; Unit; Date of Commissioning; Location of Last Modification; Date of Last Modification; Location of Last Repair; Date of last Repair.
6.8.5
Report
Selecting Report in Inventory menu (Fig. 6.220), the Inventory Data window opens for the recording on file of the system inventory data. Report command runs an external application of the Net Viewer/LCT program, which allows to execute the report of the unit inventory data on a single file. It is possible open the report file and to display the inventory data using any text editor. For the description of the reporting procedure, refer to the OMN Manual of Net Viewer/LCT program.
6.9 SECURITY
Security command in the main menu allows to configure the security access to the equipment. Select Security in the operative menu. In the Security window the user can: verify the current user class and and the Security enabling status; change the Security enabling status and the access password for the different user class.
If the Security is enabled, when the equipment is switched on, the login phase takes place: a window opens, where the user must insert his user class and relative password. By default, the Security is disabled. Enabling/Disabling Security It is possible to enable (Enabled) or disablee (Disabled) the Security. Password change It is possible to change the access password for each user class. To access to the CHANGE PASSWORD window, click on the user class field, whose password is intended to be modified.
6-133
Actual User Class The possible displayings are: Read Write User Read Only User Admin User.
6.10 History menu

History menu is a functionality of the Net Viewer/LCT program, which allows to execute the recording of the events (alarms, status changes, ecc.) related to the equipment operation. It is possible to use any text editor to open a recording file and to dipslay the recorded events. For the description of the commands in History menu, refer to the OMN Manual of Net Viewer/LCT program.
6.11 Alarm list

Alarms List command starts an external application of the Net Viewer/LCT program, that allows to display every type of alarm and/or fault currently present on the equipment. For the description of the Alarm List window, refer to the OMN Manual of Net Viewer/LCT program.
6-134
7 - ALARMS
7 ALARMS
7.1 Overview
The SRA series 3 equipment is provided with an alarm system, with different signalling modalities (via software, LED, returns to connector), which allow a fast identification of the faulted module or function to the operator. This document describes all the available alarms for the equipment, subdividing them both for functions and for the different signalling modalities.
7.2 Summary alarm signallings

The status of the single summary alarm signallings, described here below, is reported in the following table (Tab. 7.1). The possible alarm severities, reported in the table, are: Critical (CR): a service affecting condition has occurred and an immediate corrective action is required. Major (MA): a service affecting condition has developed and it is possible to postpone the corrective action. Minor (MI): a non-service affecting fault condition has occurred and it is possible to postpone the corrective action. Warning (WA): a potential or impeding affective service fault has been detected, before any significant effect has been felt. No special action is required over the equipment. Test (TE): indicates the existence of a special working condition for test or maintenance purpose.
These note are valid in the following tables: (1): for ODU SRA (2): for ODU NPL
7-1
7 - ALARMS
Tab. 7.1 Events on
Alarm signallings description and severity ((1+0) w/o MST system type) Alarm Description Fault on IDU CPU Fault on SDH board, tributary side Fault on main board Fault on modem board Fault on IF board Fault on IDU-ODU interface Loss Of Frame RFCOH Loss Of Frame on tributary side Trail Identifier Mismatch - trib side Loss Of Frame on radio side Trail Identifier Mismatch - radio side Loss Of Signal on tributary side Laser fault High BER condition Fault in IDU power supply Fault on WS channel board Fault on User channel board Loss Of Signal on User Channel Loss Of Signal on Wayside Channel B1 Signal Degrade Trib Side B1 Signal Degrade Radio Side Early Warning condition Indication of active loop-back on tributary side Indication of active loop-back on radio side Indication of the modulator operation mode Indication of the transmission power modality Indication of active laser restart Fault in ODU power supply Fault in TX Amplifier Fault in Synthetizer Fault in TX Oscillator Fault in RX Oscillator Loss Of Signal RF Fault on IDU-ODU interface Fault of transmission section * * * * * * *
(1)
CR * * * * * *(1) * * * * * * * *
MA
MI
WA
TE
CPU Alarm SDH Trib Board Main Board Modem Board IF Board IDU-ODU i/f LOF RFCOH LOF Trib TIM Trib LOF Radio TIM Radio LOS Trib Laser Transmit H-BER IDU Power Supply Way Side Ch Board User Ch Board LOS User Ch LOS WS Ch B1 SD Trib Side B1 SD Radio Side Early Warning SDH Local Loop-Back Trib Side SDH Local Loop-Back Radio Side Modulator Mode TX Power Mode Laser Restart Power Supply TX Amplifier Synthetizer ODU TX Oscillator RX Oscillator RF LOS IDU-ODU i/f TX Section (2)
*(2)
* * * * * * * * * * * * *
*(2)
7-2
7 - ALARMS
Tab. 7.1 Events on
Alarm signallings description and severity ((1+0) w/o MST system type) Alarm Description Fault of reception section Cable compensation value out of allowed range Cable compensation activated Fault in frequency plan operation Indication of frequency plan activation Fault on Backup Key Communication bus fault Error in trasfer procedure Error in alignment procedure External EOW unit not present Summary of all the TCN alarms * * * * * * CR * * * * * MA MI WA TE
RX Section (2) Cable Out of Range (2) Comp Cable Running (2) Freq Plan Fail
(2)
Freq Plan Activation Key I2C Bus System Backup Key I2C Bus Fail Transfer to Stand-by Bank System Alignment Banks Procedure EOW EXT Absent Summary TCN
7-3
7 - ALARMS
Tab. 7.2
Alarm signallings description and severity ((1+1) Hetero Freq STI w/o MST system types) Alarm Description Fault on IDU CPU Fault on SDH board, tributary side Fault on main board Fault on modem board Fault on IF board Fault on IDU-ODU interface Loss Of Frame RFCOH Loss Of Frame on tributary side Trail Identifier Mismatch - trib side Loss Of Frame on radio side Trail Identifier Mismatch - radio side Loss Of Signal on tributary side Laser fault High BER condition Fault in IDU power supply Fault on WS channel board Fault on User channel board Loss Of Signal on User Channel Loss Of Signal on Wayside Channel Fault to EOW internal channel B1 Signal Degrade Trib Side B1 Signal Degrade Radio Side Early Warning condition Indication of active loop-back on tributary side Indication of active loop-back on radio side Indication of the modulator operation mode Indication of the transmission power modality Indication of active laser restart Fault to connection cable between IDU1 and ODU1 Fault to connection cable between IDU2 and ODU2 * * * * * * * * * * * * * * * * * * * * * * * * CR MA * * * * * * * MI WA TE
Events on
CPU Alarm SDH Trib Board Main Board Modem Board IF Board IDU-ODU i/f LOF RFCOH LOF Trib TIM Trib LOF Radio TIM Radio LOS Trib Laser Transmit H-BER Power Supply Way Side Ch Board IDU1 / IDU2 User Ch Board LOS User Ch LOS WS Ch EOW Int B1 SD Trib Side B1 SD Radio Side Early Warning SDH Local Loop-Back Trib Side SDH Local Loop-Back Radio Side Modulator Mode TX Power Mode Laser Restart IDU1-ODU1 i/f (2) IDU2-ODU2 i/f (2)
7-4
7 - ALARMS
Tab. 7.2
Alarm signallings description and severity ((1+1) Hetero Freq STI w/o MST system types) Alarm Description Fault in ODU power supply Fault in TX Amplifier Fault in Synthetizer Fault in TX Oscillator Fault in RX Oscillator Loss Of Signal RF Fault on IDU-ODU interface Fault of transmission section Fault of reception section Cable compensation value out of allowed range Cable compensation activated Fault in frequency plan operation Indication of frequency plan activation Fault on Backup Key Fault to EOW external unit Communication bus fault Fault on cable connecting the IDUs Cable connecting IDUs missing Mismatch between the software of the two IDUs Mismatch between the hardware of the two IDUs The system is forced to work in 1+0 configuration Fault on IDU1 main battery Fault on IDU2 main battery Error in trasfer procedure Error in alignment procedure External EOW unit not present Switches status frozen Loss of Signal on both beams Summary of all TCN alarms Indication of the switching modality * * * * * * * * * * * * * * * * *
(2) (2)
Events on
CR
MA * * * * * * * * * *
MI
WA
TE
Power Supply TX Amplifier Synthetizer TX Oscillator RX Oscillator RF LOS ODU1 / ODU2 IDU-ODU i/f TX Section RX Section
Cable Out of Range (2) Comp Cable Running (2) Freq Plan Fail
(2)
* * *
Freq Plan Activation Key External EOW I2C Bus System Backup Key EOW Ext I2C Bus Fail Data Exp Cable Fault Data Exp Cable Missing IDUs Software Mismatch IDUs Hardware Mismatch System Forced in 1+0 Master Config IDU1 Main Battery System IDU2 Main Battery Transfer to Stand-by Bank Alignment Banks Procedure EOW EXT Absent System Switches Frozen Both RF LOS Summary TCN Switch Mode
7-5
7 - ALARMS
Tab. 7.3
Alarm signallings description and severity ((1+1) Hetero Freq DTI w/o MST system types) Alarm Description Fault on IDU CPU Fault on SDH board, tributary side Fault on main board Fault on modem board Fault on IF board Fault on IDU-ODU interface Loss Of Frame RFCOH Loss Of Frame on tributary side Trail Identifier Mismatch - trib side Loss Of Frame on radio side Trail Identifier Mismatch - radio side Loss Of Signal on tributary side Laser fault High BER condition Remote Defect Indication on multiplex section Alarm Indication Signal on multiplex section Fault in IDU power supply Fault on WS channel board Fault on User channel board Loss Of Signal on User Channel Loss Of Signal on Wayside Channel B1 Signal Degrade Trib Side Fault to EOW internal channel B1 Signal Degrade Radio Side Early Warning condition Indication of active loop-back on tributary side Indication of active loop-back on radio side Indication of the modulator operation mode Indication of the transmission power modality Indication of active laser restart Fault to connection cable between IDU1 and ODU1 Fault to connection cable between IDU2 and ODU2 * (2) * (2) * (1) * (1) * * * * * * * * * * * * * * * * * * * * * CR MA * * * * * * * * * * MI WA TE
Events on
CPU Alarm SDH Trib Board Main Board Modem Board IF Board IDU-ODU i/f LOF RFCOH LOF Trib TIM Trib LOF Radio TIM Radio LOS Trib Laser Transmit H-BER MS-RDI IDU1 / IDU2 MS-AIS Power Supply Way Side Ch Board User Ch Board LOS User Ch LOS WS Ch B1 SD Trib Side EOW Int B1 SD Radio Side Early Warning SDH Local Loop-Back Trib Side SDH Local Loop-Back Radio Side Modulator Mode TX Power Mode Laser Restart IDU1-ODU1 i/f IDU2-ODU2 i/f
7-6
7 - ALARMS
Tab. 7.3
Alarm signallings description and severity ((1+1) Hetero Freq DTI w/o MST system types) Alarm Description Fault in ODU power supply Fault in TX Amplifier Fault in Synthetizer Fault in TX Oscillator Fault in RX Oscillator Loss Of Signal RF Fault on IDU-ODU interface Fault of transmission section Fault of reception section Cable compensation value out of allowed range Cable compensation activated Fault in frequency plan operation Indication of frequency plan activation Fault on Backup Key Fault on external EOW External EOW unit not present Fault on I2C communication bus Fault on cable connecting the IDUs Cable connecting IDUs missing Mismatch between the software of the two IDUs Mismatch between the hardware of the two IDUs The system switches cannot change their configuration The system is forced to work in 1+0 configuration Fault on IDU1 main battery Fault on IDU2 main battery Error in trasfer procedure Error in alignment procedure External EOW unit not present Loss of Signal on both beams Summary of all TCN alarms Indication of the switching modality * * * * * * * * * * * * * * * * * *
(2) (2)
Events on
CR
MA * * * * * * * * * *
MI
WA
TE
Power Supply TX Amplifier Synthetizer TX Oscillator RX Oscillator RF LOS ODU1 / ODU2 IDU-ODU i/f TX Section RX Section
(2)
* * *
Freq Plan Activation Key External EOW Bus I2C System Backup Key EOW Ext EOW EXT Absent I2C Bus Fail Data Exp Cable Fault Data Exp Cable Missing IDUs Software Mismatch IDUs Hardware Mismatch System Switches Frozen System Forced in 1+0 Master Config IDU1 Main Battery IDU2 Main Battery Transfer to Stand-by Bank Alignment Banks Procedure EOW EXT Absent Both RF LOS Summary TCN Switch Mode
System
7-7
7 - ALARMS
Tab. 7.4
Alarm signallings description and severity ((1+1) Hot Stby DTI w/o MST system types) Alarm Description Fault on IDU CPU Fault on SDH board, tributary side Fault on main board Fault on modem board Fault on IF board Fault on IDU-ODU interface Loss Of Frame RFCOH Loss Of Frame on tributary side Trail Identifier Mismatch - trib side Loss Of Frame on radio side Trail Identifier Mismatch - radio side Loss Of Signal on tributary side High BER condition Remote Defect Indication on Multiplex Section Alarm Indication Signalling on Multiplex Section Fault in IDU power supply Fault on WS channel board Fault on User channel board Loss Of Signal on User Channel Loss Of Signal on Wayside Channel Laser fault B1 Signal Degrade Trib Side Fault to EOW internal channel B1 Signal Degrade Radio Side Early Warning condition Indication of active loop-back on tributary side Indication of active loop-back on radio side Indication of the modulator operation mode Indication of the transmission power modality Indication of active laser restart Fault to connection cable between IDU1 and ODU1 * * * * * * * * * * * * * * * * * * * * * * CR MA * * * * * * * * * MI WA TE
Events on
CPU Alarm SDH Trib Board Main Board Modem Board IF Board IDU-ODU i/f LOF RFCOH LOF Trib TIM Trib LOF Radio TIM Radio LOS Trib H-BER MS RDI MS AIS Power Supply IDU1 / IDU2 Way Side Ch Board User Ch Board LOS User Ch LOS WS Ch Laser Transmit B1 SD Trib Side EOW Int B1 SD Radio Side EW SDH Local Loop-Back Trib Side SDH Local Loop-Back Radio Side Modulator Mode TX Power Mode Laser Restart IDU1-ODU1 i/f (2)
7-8
7 - ALARMS
Tab. 7.4
Alarm signallings description and severity ((1+1) Hot Stby DTI w/o MST system types) Alarm Description Fault to connection cable between IDU2 and ODU2 Fault in ODU power supply Fault in TX Amplifier Fault in Synthetizer Fault in TX Oscillator Fault in RX Oscillator Loss Of Signal RF
(1)
Events on
CR
MA
MI *
WA
TE
IDU2-ODU2 i/f (2) Power Supply TX Amplifier Synthetizer TX Oscillator RX Oscillator RF LOS IDU-ODU i/f ODU1 / ODU2 TX Section RX Section Hot-Stby Switch
(2) (2)
* * * * * * * * * * * * * * * * * * * * * * * * * * *
Fault on IDU-ODU interface Fault in switching procedure Fault of transmission section Fault of reception section Cable compensation value out of allowed range Cable compensation activated Fault in frequency plan operation Indication of frequency plan activation Fault on Backup Key Fault on cable connecting the IDUs Cable connecting IDUs missing Mismatch between the software of the two IDUs Mismatch between the hardware of the two IDUs The system switches cannot change their configuration The system is forced to work in 1+0 configuration Fault on IDU1 main battery Fault on IDU2 main battery Mismatch during ODU switching Fault to EOW external unit External EOW unit not present Communication bus fault
(2)
Freq Plan Activation Key System Backup Key Data Exp Cable Fault Data Exp Cable Missing IDUs Software Mismatch IDUs Hardware Mismatch System System Switches Frozen System Forced in 1+0 Master Config IDU1 Main Battery IDU2 Main Battery ODU Switch Mismatch External EOW I2C Bus EOW Ext APU EOW EXT I2C Bus Fail
7-9
7 - ALARMS
Tab. 7.5
Alarm signallings description and severity ((1+1) Hot Stby STI w/o MST system types) Alarm Description Fault on IDU CPU Fault on SDH board, tributary side Fault on main board Fault on modem board Fault on IF board Fault on IDU-ODU interface Loss Of Frame RFCOH Loss Of Frame on tributary side Trail Identifier Mismatch - trib side Loss Of Frame on radio side Trail Identifier Mismatch - radio side Loss Of Signal on tributary side High BER condition Fault in IDU power supply Fault on WS channel board Fault on User channel board Loss Of Signal on User Channel Loss Of Signal on Wayside Channel Fault of EOW internal channel B1 Signal Degrade Trib Side B1 Signal Degrade Radio Side Early Warning condition Laser fault Indication of active loop-back on tributary side Indication of active loop-back on radio side Indication of the modulator operation mode Indication of the transmission power modality Indication of active laser restart Fault to connection cable between IDU1 and ODU1 Fault to connection cable between IDU2 and ODU2 * * * * * * * * * * * * * * * * * * * * * * * * CR MA * * * * * * * MI WA TE
Events on
CPU Alarm SDH Trib Board Main Board Modem Board IF Board IDU-ODU i/f LOF RFCOH LOF Trib TIM Trib LOF Radio TIM Radio LOS Trib H-BER Power Supply Way Side Ch Board User Ch Board IDU1 / IDU2 LOS User Ch LOS WS Ch EOW Int B1 SD Trib Side B1 SD Radio Side Early Warning Laser Transmit SDH Local Loop-Back Trib Side SDH Local Loop-Back Radio Side Modulator Mode TX Power Mode Laser Restart IDU1-ODU1 i/f (2) IDU2-ODU2 i/f (2)
7-10
7 - ALARMS
Tab. 7.5
Alarm signallings description and severity ((1+1) Hot Stby STI w/o MST system types) Alarm Description Fault in ODU power supply Fault in TX Amplifier Fault in Synthetizer Fault in TX Oscillator Fault in RX Oscillator Loss Of Signal RF Fault on IDU-ODU interface Fault in switching procedure Fault of transmission section Fault of reception section Cable compensation value out of allowed range Cable compensation activated Fault in frequency plan operation Indication of frequency plan activation Fault on Backup Key Fault on cable connecting the IDUs Cable connecting IDUs missing Mismatch between the software of the two IDUs Mismatch between the hardware of the two IDUs The system switches cannot change their configuration The system is forced to work in 1+0 configuration Error in trasfer procedure Error in alignment procedure Fault on IDU1 main battery Fault on IDU2 main battery Mismatch during ODU switching Loss of Signal on both beams Summary of all TCN alarms Indication of the switching modality Fault to EOW external unit External EOW unit not present Communication bus fault * * * * * * * * * * * * * * * * * * * * * * * CR MA * * * * * * * * MI WA TE
Events on
Power Supply TX Amplifier Synthetizer TX Oscillator RX Oscillator RF LOS IDU-ODU i/f ODU1 / ODU2 Hot-Stby Switch TX Section RX Section
(2) (2)
(2)
Freq Plan Activation Key System Backup Key Data Exp Cable Fault Data Exp Cable Missing IDUs Software Mismatch IDUs Hardware Mismatch System Switches Frozen System Forced in 1+0 Master Config Transfer to Stand-by Bank Alignment Banks Procedure IDU1 Main Battery IDU2 Main Battery ODU Switch Mismatch Both RF LOS Summary TCN Switch Mode External EOW I2C Bus EOW Ext EOW EXT Absent I2C Bus Fail
System
7-11
7 - ALARMS
7.3 Alarm signalling leds

All the LEDs for the alarm signallings, present on the frontal panel of the IDU unit, are reported in the following table (Tab. 7.6) with a brief description of their behaviour. Tab. 7.6 NAME ODU FAULT IDU FAULT IDU1/PWR ON IDU2/PWR ON CPU FAULT RF LOS TRIB LOS TRIB R_RX R_TX KEY FAULT / KEY MISSING LEDs indications on IDU LED Red Red Green Green Red Red Red Yellow Yellow Yellow Red LABEL ODU IDU ON-1 ON-2 CPU LOS TRIB LOS TRIB R_RX R_TX KEY DESCRIPTION If ON, it indicates an ODU fault If ON, it indicates an IDU fault Identifies IDU1 Identifies IDU2 Lit for restitution fault root If On, it indicates a RF loss of signal If ON, it indicates a loss of signal on tributary side Trib active Radio TX active Radio RX active It signals a fault relative to the key. LED OFF: the key is inserted and is working properly. LED ON: the key is not inserted. LED blinks slowly: key fault. LED blinks quickly: either the key or the internal EEPROM is about to be overwritten (the blink indication lasts 20 seconds and after that the E2PROM will be overwritten). ON: IDU MASTER BLINKING: key extracted / MSTR hystorical (*) ODU: IDU SLAVE / 1+0 10BASE2 RX SIGNAL 10BASE2 TX SIGNAL 10BASE2 COLLISIONS Green Green Yellow RX TX CL Ethernet 10 BASE2 indications
MASTER (OFF IN 1+0 SYSTEM TYPE)
Yellow
MSTR
7-12
7 - ALARMS
7.4 Alarms classification

In the following tables, the alarms are associated at the physical part of the equipment from which they are likely generated. Moreover, they are marked as Physical (P) or as Functional (F): Tab. 7.7 Physical alarms: they are related to an hardware failure; Functional alarms: they are related to SDH signal.
Signalling of manual operation Unit Allarme LOS Trib LOF Trib B1 SD Trib TIM Trib AIS Inserted AIS Inserted LOF Radio B1 SD Radio TIM Radio LOF RFCOH H-BER EW IDU RF LOS CPU Alarm Power Supply Laser Transmit SDH Trib Board Main Board Modem Board IF Board WaySide Ch Board User Ch Board EOW Int IDU Main Battery System Backup Key Lato Tributary Tributary Tributary Tributary Tributary Radio Radio Radio Radio Radio Radio Radio Radio Scheda Main Main Main Payload boards Payload boards Payload boards Payload boards AUX boards AUX boards AUX boards AUX boards Classe Functional Functional Functional Functional Functional Functional Functional Functional Functional Functional Functional Functional Functional Physical Physical Physical Physical Physical Physical Physical Physical Physical Physical Physical Physical
7-13
7 - ALARMS
Tab. 7.7
Signalling of manual operation Unit Allarme Power Supply TX Section Synthetizer TX Amplifier ODU TX Oscillator RX Oscillator IDU-ODU i/f Hot-Stby Switch ODU Switch Mismatch IDUs Cable EOW esterna Data Exp Cable Fault Data Exp Cable Missing External EOW Presence Lato Scheda Classe Physical Physical Physical Physical Physical Physical Physical Physical Physical Physical Physical Physical
7-14
A - LIST OF ACRONYMS AND ABBREVIATIONS
A LIST OF ACRONYMS AND

ABBREVIATIONS
A.1 Lists of abbreviations
AIS Alarm Indication Signal ALS Automatic Laser Shutdown ALM Alarm ATPC Automatic Transmission Power Control AUX Auxiliary BBE Background Block Errors BER Bit Error Rate CH Channel CON Connected CPU Central Processing Unit CRC Cyclic Redundancy Check Dem Demodulator DIS Disconnected DTI Double Tributary Interface EEPROM Electrically Erasable Programmable Read Only Memory EM Element Manager
A-1
EOW Engineering Order-Wire ES Errored Seconds EW Early Warning FERF Far End Receive Failure FSK Frequency Shift Keying FTP File Trasfer Protocol Gnd Ground HBER High Bit Error Ratio HEX Hexadecimal HF Hetero Frequency HSBY Hot Stand-by HW Hardware I/O Input/Output ID Identifier IDU InDoor Unit i/f Interface IF Intermediate Frequency IN Input IP Internet Protocol LCT Local Craft Terminal LED Light Emission Diode
A-2
LOF Loss Of Frame LOP Loss Of Pointer LOS Loss Of Signal MIB Management Information Base MIS Mismatch MOD Modulator MS Multiplex Section MSOH Multiplex Section OverHead MST Multiplex Section Termination NE Network Element ODU OutDoor Unit OI Outage Intensity OMN Operating Manual OnL On line OUT Output PC Personal Computer PID Product Identification Data PM Performance Monitoring PWR Power RAM Random Access Memory RDI Remote Defect Indication
A-3
RF Radio Frequency RFCOH Radio Frequency Customer OverHead RIP Routing Information Protocol RL Received Level RLTS Received Level Threshold Second RPS Radio Protection Switching RSOH Regenerator Section OverHead RSPI Regenerator Section Physical Interface RST Regenerator Section Termination RX Reception R/O Read Only R/W Read Write SD Signal Degrade SDH Synchronous Digital Hierarchy SES Severely Errored Seconds SPI SDH Physical Interface SRA Synchronous Radio Access S.T. System Type Stby Stand-by STI Single Tributary Interface STM Synchronous Transfer Module
A-4
SVR Software Version Release SW Software TCM Trellis Code Modulation TCN Threshold Crossing Notification TCP Transmission Control Protocol TF Transmission Frequency TIM Trail Identifier Mismatch TL Transmitted Level TLTS Transmitted Level Threshold Second TMN Telecommunications Management Network TNMP Telecommunications Network Management Point TP Termination Point TRIB Tributary TX Transmission UAS UnAvailability Seconds WS Way-Side
A-5
LA
PA
A-6 SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002
PRINTED in ITALY
SRA series 3
SVR 3.5.0
Operating Manual (OMN)
911-353/02A0350
SRA series 3 SVR 3.5.0
D.45
D.55
SRA series 3
SVR 3.5.0 Operating Manual (OMN)

911-353/02A0350
SRA series 3 SVR 3.5.0 Operating Manual (OMN)

911-353/02A0350
D.25
911-353/02A0350
D.30
SRA series 3 SVR 3.5.0
SRA series 3 SVR 3.5.0 Operating Manual (OMN) 911-353/02A0350
D.20

911-353/02A0350

911 353 02a0350

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

911 353 02a0350

Enviado por

Direitos autorais:

Formatos disponíveis

Operating Manual

SRA series 3 SVR 3.5.0 OMN

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

STATUS OF MANUAL Current: Previous: Issue 1, May 2002

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

EQUIPMENT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

SAFETY RULES AND PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

INSTALLATION OF SOFTWARE PLUG-IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1

DOWNLOAD OF CONTROLLER UNIT SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . 5.1

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

GUIDE TO USE OF SRA SERIES 3 MANAGEMENT PROGRAM. . . . . . . . . . . . . . . 6.1

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

LIST OF ACRONYMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

Equipment traffic capacity:

Base-band interfaces: Operating frequency bands (ODU SRA)

Operating frequency bands (ODU NPL)

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

Tab. 1.1 ATPC

Configuration of the operative parameters:

User interface: RIP features Configuration of TCP/IP connection:

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

1.2 Testing and warranty

1.4 Manuals related to SRA series 3

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

Local Craft Terminal (LCT)

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

LCT connection to the equipment

IDU optical unit front panel

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

2.2 User classes and security

NE Access Control Management

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

3 - SAFETY RULES AND PRECAUTIONS

3 SAFETY RULES AND PRECAUTIONS

3.2 Artificial respiration

Artificial respiration procedure (1/4)

Artificial respiration procedure (2/4)

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

3 - SAFETY RULES AND PRECAUTIONS

Artificial respiration procedure (3/4)

Artificial respiration procedure (4/4)

3.3 Treatment of burns

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

3 - SAFETY RULES AND PRECAUTIONS

3.4 Safety labels

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

3 - SAFETY RULES AND PRECAUTIONS

4 - INSTALLATION OF SOFTWARE PLUG-IN

4 INSTALLATION OF SOFTWARE PLUG-IN

4.2 Installation procedure

SRA series 3 - OMN 911-353/02A0350 - Issue 1, May 2002

4 - INSTALLATION OF SOFTWARE PLUG-IN

Installation of plug-in software (1/2)

Installation of plug-in software (2/2)