Siemens Sra4 Svr4.6 Omn - Operating Manual

Operating Manual
SRA 4
SVR 4.6
OMN
911-381/02A0460
Issue 1, March 2006
FOR INTERNAL USE ONLY FOR INTERNAL USE ONLY
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Copyright (C) Siemens S.p.A. 2006
V.le Piero e Alberto Pirelli, 10
I-20126 Milano
Issued by Customer Documentation Department
S.S. 11 Padana Superiore, km 158
I-20060 Cassina de Pecchi MI
DISCLAIMER
Siemens may have patents, patent applications, trademarks, copyrights, or other intellectual property rights relevant to the subject matters
present in this document.
If not explicitly defined by a license agreement written by Siemens, the ownership of this document does not give any use license for the
above mentioned patents, trademarks, copyrights, or other intellectual properties.
For your convenience, Siemens may make this document available.
The entire risk deriving from the use, or the results of the use, of this document are at users charge.
The information contained in this document is subjected to changes without notice.
Technical specifications and features are binding only insofar as they are specifically and expressly agreed previously in a written contract.
Siemens gives no assurance relevant to the accuracy of the results or of the output deriving from such information.
In case of utilization of the information transferred by means of this document, we advise You to verify if the export licenses, required by the
laws, have been granted or if there are not any other impediments arising from the laws in course in Italy, Germany or relevant to the export.
STATUS OF MANUAL
R-1
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
This OMN manual describes the procedures for the installation and the use of the
software plug-in for the management of SRA4 SVR 4.6. equipment.
With respect to the Issue 1, December 2005, the alarm tables in Chapter 6 and 7 have
been updated.
STATUS OF MANUAL
Current: Issue 1, March 2006
Previous: Issue 1, Dicember 2005
STATUS OF MANUAL
R-2
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
B
L
A
N
K

P
A
G
E
INDEX
I-1
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
INDEX
STATUS OF MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R.1
INDEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.1
LIST OF ILLUSTRATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.5
LIST OF TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.11
1 GENERAL INFORMATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1
1.1 Subject and Purpose of the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1
1.2 Functionalities of the Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2
1.3 Testing and Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4
1.4 Responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4
1.5 Conditions of the Provision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5
1.6 Related Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5
1.7 Lists of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5
2 EQUIPMENT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1
2.1.1 Local Craft Terminal (LCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1
2.2 User Classes and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2
2.2.1 User Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2
2.2.2 Management of the access to the network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3
3 INSTALLATION OF PLUG-IN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1
3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1
3.2 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1
3.3 Uninstallation of Plug-In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3
4 COMMISSIONING VIA LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1
5 DOWNLOAD OF CONTROLLER UNIT SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . 5.1
5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1
5.2 Download via FTP of IDU software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2
5.3 Download via FTP of ODU software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6
INDEX
I-2
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6 OPERATING GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1
6.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1
6.2 Architecture of the System with Double IDU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1
6.3 Software Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2
6.3.1 Plug-in Functionalities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2
6.3.2 Hardware hardware key Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3
6.3.2.1 Controller operating modalities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4
6.3.2.2 Main/Expansion Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5
6.3.2.2.1 IDU numbering in 2 IDU units based System Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5
6.3.2.2.2 Main/Expansion negotiation at controller start up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5
6.3.2.2.3 Loss and recovery of communication between main and expansion controllers . . . . . . . . . . . 6.5
6.3.2.2.4 Check of the HW and SW versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5
6.3.3 License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6
6.3.4 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7
6.4 Uploading of profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8
6.5 Push-buttons Key in Plug-in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9
6.6 Structure of the Operating Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9
6.7 Configuration and Status of the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10
6.7.1 Equipment Status & Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.11
6.7.1.1 System Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.17
6.7.1.1.1 Management of J0 byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.22
6.7.1.1.2 Config Type Setting window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.26
6.7.1.2 External Interface Setting window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.28
6.7.1.2.1 BB-Modem Payload window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.30
6.7.1.2.2 Q Interface Parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.32
6.7.1.2.3 Output Commands Settings window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.33
6.7.1.2.4 Input Station Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.34
6.7.1.2.5 AUX Channel BB-Modem window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36
6.7.1.3 Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38
6.7.1.3.1 Protection in (1+1) and 2x(1+1) System Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.39
6.7.1.3.2 Protection in (N+1) System Types (starting from SVR 4.4) . . . . . . . . . . . . . . . . . . . . . . . . . . 6.42
6.7.1.4 Co-Channel operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.45
6.7.1.5 Testing window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.48
6.7.1.5.1 Testing Mode & Loop-Backs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.49
6.7.1.5.2 Recording of the Long Period Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.51
6.7.1.5.3 Timed Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.54
6.7.1.6 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.60
6.7.1.7 Feature Control window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.61
6.7.1.8 Copy Config command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.62
6.7.1.9 Paste Config command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.63
6.7.1.10 BB-Modem Config window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.63
6.7.1.11 ATPC function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.65
6.7.1.11.1ATPC for ODU Narrowband. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.66
6.7.1.11.2ATPC for ODU Wideband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.67
6.7.1.11.3Setting of the transmission power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.68
6.7.1.12 Configuration of ODU unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.69
6.7.1.12.1Configuration of Wideband ODU unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.69
6.7.1.12.2Configuration of Narrowband ODU unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.79
6.7.2 Software Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.82
6.7.2.1 IDU Software Banks window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.82
6.7.2.2 ODU Software Banks window (only for ODU Wideband) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.84
6.7.2.3 FTP Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.86
INDEX
I-3
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.2.4 SW Reset window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.87
6.7.3 Management of the network parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.87
6.7.3.1 Access to the dynamic routing table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.88
6.7.3.2 IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.89
6.7.3.3 Interface network parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.91
6.7.3.4 Static Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.95
6.7.4 Configuration of the error notification thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.97
6.7.5 Setting of date and time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.99
6.8 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.100
6.8.1 Physical and functional alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.100
6.8.1.1 TX Way Payload Functional Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.103
6.8.1.1.1 RST Tx STM-1 (BB-Modem) window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.104
6.8.1.2 RX Way Payload Functional Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.104
6.8.1.2.1 RST Rx STM-1 (BB-Modem) window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.106
6.8.1.3 IDU Other Functional Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.106
6.8.1.4 A.U. IDU User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.108
6.8.1.5 Controller IDU User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.108
6.8.1.6 Mem Key User Physical Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.109
6.8.1.6.1 Mem Key Maint Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.109
6.8.1.7 FAN IDU User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.110
6.8.1.8 BB-Modem User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.110
6.8.1.9 i/f User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.111
6.8.1.10 System User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.112
6.8.1.11 ODU User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.113
6.8.1.11.1Physical Maintenance Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.114
6.8.1.12 i/f CPU User Physical Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.115
6.8.1.13 i/f Exp Cable User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.115
6.8.1.13.1i/f Exp Cable Maint Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.116
6.8.2 Alarm Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.116
6.8.3 Station alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.117
6.9 Management of Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.118
6.9.1 Unit Measurements window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.118
6.9.2 Measurement of RX and TX ODU power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.119
6.10 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.120
6.10.1 RST Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.121
6.10.2 Unavailability Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.121
6.10.3 RSPI parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.122
6.10.4 RPS Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.123
6.10.5 Suspect Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.124
6.10.6 Performance menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.125
6.10.7 Performance - PM Setting window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.126
6.10.8 Performance Monitoring View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.129
6.10.8.1 RST Performance View: BB-Modem - Trib Side STM-1 (Quarter) window. . . . . . . . . . . . . . 6.130
6.10.8.2 RST Performance View: BB-Modem - Trib Side STM-1 (Day) window. . . . . . . . . . . . . . . . . 6.130
6.10.8.3 RST Performance View: RX Chain - Radio Side STM-1 (Quarter) window . . . . . . . . . . . . . 6.131
6.10.8.4 RST Performance View: RX Chain - Radio Side STM-1 (Day) window . . . . . . . . . . . . . . . . 6.132
6.10.8.5 RPS Performance View: RX Chain (Quarter) window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.132
6.10.8.6 RPS Performance View: RX Chain (Day) window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.133
6.10.8.7 RSPI Performance View: ODU Tx Side (Quarter) window . . . . . . . . . . . . . . . . . . . . . . . . . . 6.134
6.10.8.8 RSPI Performance View: ODU Rx Side (Quarter) window . . . . . . . . . . . . . . . . . . . . . . . . . . 6.134
6.10.8.9 RSPI Performance View: ODU (Day) window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.135
6.11 Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.136
6.11.1 PID window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.138
INDEX
I-4
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.11.2 Management of the user inventory data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.138
6.11.3 Equipment Software window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.139
6.11.4 About window (NetViewer/LCT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.139
6.11.5 Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.140
6.12 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.142
6.13 NE Severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.144
6.13.1 Critical. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.145
6.13.2 Major. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.149
6.13.3 Minor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.153
6.13.4 Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.154
7 ALARM MANAGEMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1
7.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1
7.2 Summary Alarm Signalings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1
7.3 Alarm Signaling via Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1
A LICENSE UPGRADE PROCEDURE FOR SRA4 EQUIPMENT. . . . . . . . . . . . . . . . . A.1
A.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1
A.2 Upgrading Procedure Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2
I-5
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
LIST OF ILLUSTRATIONS
Fig. 2.1 IDU unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2
Fig. 3.1 Installation of plug-in (1/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2
Fig. 3.2 Installation of plug-in (2/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2
Fig. 5.1 Download procedure of IDU software via FTP (1/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2
Fig. 5.6 IDU Software Banks window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5
Fig. 5.7 Download procedure of ODU software via FTP (1/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6
Fig. 5.12 ODU Software Banks window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.9
Fig. 6.1 Example of map with SRA4 equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8
Fig. 6.2 Operating menu of SRA 4 equipment plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10
Fig. 6.3 Status and Config Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.11
Fig. 6.4 Equipment Status & Configuration window (e.g.: 2x(1+1) FD DTI System Type) . . . . . . . . . . . . . 6.12
Fig. 6.5 System Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.17
Fig. 6.6 Configuration of System Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.18
Fig. 6.7 Configuration of modulation and capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.19
Fig. 6.8 Configuration of Radio Channel Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20
Fig. 6.9 Configuration of Alarm unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20
Fig. 6.10 Configuration of Controller unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20
Fig. 6.11 Configuration of FAN unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20
Fig. 6.12 Configuration of BB-Modem unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.21
Fig. 6.13 Configuration of ODU unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.21
Fig. 6.14 Link ID (J0) BB-Modem1 window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.23
Fig. 6.15 Configuration of TIM alarm activation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.23
Fig. 6.16 Configuration of TIM alarm deactivation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.23
Fig. 6.17 Window for the J0 Management Tributary Side (TX) selection . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.24
Fig. 6.18 Window for enabling/disabling AIS Insertion for TIM (Tributary Side) . . . . . . . . . . . . . . . . . . . . . . 6.24
Fig. 6.19 Window for the insertion of J0 Inserted Tributary Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.24
Fig. 6.20 Window for the J0 Expected Tributary Side insertion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.25
Fig. 6.21 Window for the J0 Management Radio Side (Rx) selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.25
Fig. 6.22 Window for the AIS Insertion for TIM (Rx) enabling/disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.25
Fig. 6.23 Window for the J0 Inserted Radio Side insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.26
Fig. 6.24 Window for the J0 Expected Radio Side insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.26
Fig. 6.25 Config Type Setting window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.27
Fig. 6.26 Configuration of Config Type Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.27
Fig. 6.27 External Interface Setting window (System Type: 2x(1+1) FD DTI) . . . . . . . . . . . . . . . . . . . . . . . . 6.28
Fig. 6.28 Configuration of Automatic Laser Shut Down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.29
Fig. 6.29 Configuration of Masking STM-1 #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.30
Fig. 6.30 BB-Modem Payload window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.30
Fig. 6.31 Configuration of Laser Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.31
Fig. 6.32 Configuration of the Laser Forcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.31
Fig. 6.33 Q Interface Parameters window (write modality) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.32
Fig. 6.34 Configuration of Bit-Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.33
Fig. 6.35 Configuration of Electrical i/f Duplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.33
I-6
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.36 Output Command Settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.33
Fig. 6.37 Output Command description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.34
Fig. 6.38 Enabling of Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.34
Fig. 6.39 Station Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.34
Fig. 6.40 Name/descripiton configuration window for station alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.35
Fig. 6.41 Configuration of Polarity Alarm 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.35
Fig. 6.42 AUX Channel BB-Modem window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36
Fig. 6.43 Configuration of Service Channel Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36
Fig. 6.44 Configuration of Enable 64 kb/s V11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36
Fig. 6.45 Configuration of Enable 64 kb/s G703. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.37
Fig. 6.46 Configuration of Way Side (WS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.37
Fig. 6.47 AUX Channel IDU #1 BB-Modem 1 window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.37
Fig. 6.48 Configuration of F1 byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38
Fig. 6.49 Configuration of Way Side (WS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38
Fig. 6.50 Protection Status & Configuration window (System Type 2x(1+1) FD DTI) . . . . . . . . . . . . . . . . . 6.39
Fig. 6.51 Configuration of Switching Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.40
Fig. 6.52 Configuration of Switch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.40
Fig. 6.53 Configuration of Trib Forcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.41
Fig. 6.54 Configuration of ODU Forcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.41
Fig. 6.55 Configuration of Dem Forcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.41
Fig. 6.56 Protection Status & Configuration window ((3+1) System Types) . . . . . . . . . . . . . . . . . . . . . . . . . 6.42
Fig. 6.57 Configuration of Switching Criteria Enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.43
Fig. 6.58 Configuration of Remote Tx Prioritary Ch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.43
Fig. 6.59 Configuration of Switch Priority Ch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.44
Fig. 6.60 Configuration of Switch Criteria Forcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.44
Fig. 6.61 Co-Channel window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.46
Fig. 6.62 Configuration of synchronization modality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.47
Fig. 6.63 Synch Forcing window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.47
Fig. 6.64 Configuration of Synch Forcing (CC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.47
Fig. 6.65 Configuration of Polarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.48
Fig. 6.66 Testing window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.48
Fig. 6.67 Testing Mode & Loop-Backs window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.49
Fig. 6.68 Configuration of Loop-Back Trib Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.50
Fig. 6.69 Configuration of Loop-Back Trib Side INT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.50
Fig. 6.70 Configuration of Loop-Back Radio Side EXT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.50
Fig. 6.71 Configuration of Modulator Mode BB-Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.51
Fig. 6.72 Testing - Long PM Recording window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.51
Fig. 6.73 Long period PM recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.52
Fig. 6.74 Configuration of Recording Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.52
Fig. 6.75 Configuration of recording start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.52
Fig. 6.76 Enabling/disabling of the recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.53
Fig. 6.77 Configuration of Timed Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.55
Fig. 6.78 Single Timed Switching window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.56
Fig. 6.79 Configuration of Switch Starting Position (example: ODU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.57
Fig. 6.80 Example of Single Timed Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.57
Fig. 6.81 Periodic Timed Switching window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.58
Fig. 6.82 Example of Periodic switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.59
Fig. 6.83 Maintenance window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.60
Fig. 6.84 Feature Control window (write modality) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.61
Fig. 6.85 Configuration of License Key #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.61
Fig. 6.86 BB-Modem Config window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.63
Fig. 6.87 Configuration of Cable Length. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.64
Fig. 6.88 Configuration of IF Output Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.64
Fig. 6.89 Configuration of TX Mod Spectrum Inversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.65
Fig. 6.90 Configuration of XPIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.65
I-7
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.91 ODU Config window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.66
Fig. 6.92 Hysteresis cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.66
Fig. 6.93 Linear ATPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.68
Fig. 6.94 ODU Config window (Freq Mode = Continuous) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.69
Fig. 6.95 ODU Config window (Freq Mode = Continuous) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.70
Fig. 6.96 ODU Config window (Freq Plan Activation = On) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.70
Fig. 6.97 Configuration of Freq Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.71
Fig. 6.98 Frequency plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.71
Fig. 6.99 Enabling/disabling of Freq Plan Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.72
Fig. 6.100 Configuration of Channel Spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.73
Fig. 6.101 Configuration of TX Freq Ch#1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.73
Fig. 6.102 Configuration of First Channel ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.73
Fig. 6.103 Configuration of Last Channel ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.74
Fig. 6.104 Configuration of RF Channel ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.74
Fig. 6.105 Configuration of TX Freq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.74
Fig. 6.106 Configuration of RX Freq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.74
Fig. 6.107 Configuration of Pmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.75
Fig. 6.108 Configuration of ATPC Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.75
Fig. 6.109 Configuration of ATPC Threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.75
Fig. 6.110 Configuration of ATPC Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.76
Fig. 6.111 Configuration of Squelch SW Activation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.76
Fig. 6.112 Configuration of Comp IF Cable Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.77
Fig. 6.113 Configuration of the cable compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.77
Fig. 6.114 Warning for temporary loss of the payload in transmission (Tx AGC) . . . . . . . . . . . . . . . . . . . . . . 6.78
Fig. 6.115 Configuration of Tx AGC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.78
Fig. 6.116 Warning for temporary loss of the payload in reception (IF Power RX) . . . . . . . . . . . . . . . . . . . . . 6.78
Fig. 6.117 Configuration of IF Power (Rx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.78
Fig. 6.118 Configuration of IF Attenuation (Tx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.79
Fig. 6.119 ODU Config window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.79
Fig. 6.120 Configuration of ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.80
Fig. 6.121 Configuration of TX Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.80
Fig. 6.122 Configuration of ATPC Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.80
Fig. 6.123 Configuration of ATPC Threshold 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.81
Fig. 6.124 Configuration of Nominal Power Level Setting Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.81
Fig. 6.125 Configuration of Nominal Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.81
Fig. 6.126 Software menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.82
Fig. 6.127 IDU Software Banks window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.83
Fig. 6.128 IDU Software Banks window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.83
Fig. 6.129 ODU Software Banks window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.85
Fig. 6.130 Warning for payload loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.85
Fig. 6.131 Warning for not compatible SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.86
Fig. 6.132 Software Reset window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.87
Fig. 6.133 Network menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.87
Fig. 6.134 Directory tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.88
Fig. 6.135 Structure of table.txt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.88
Fig. 6.136 Example of routing table seen by FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.89
Fig. 6.137 IP Address window (write modality) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.90
Fig. 6.138 Configuration of IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.91
Fig. 6.139 Configuration of Net Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.91
Fig. 6.140 NE Parameters window (with ETH MTU = default value) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.92
Fig. 6.141 Configuration of ETH MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.93
Fig. 6.142 NE Parameters window with ETH MTU field set to Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.93
Fig. 6.143 Window for the insertion of an arbitrary value of ETH MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.93
Fig. 6.144 Enabling/disabling of the Telnet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.94
Fig. 6.145 Configuration of RIPv1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.94
I-8
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.146 Static Routing Table window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.96
Fig. 6.147 Configuration of Destination Network Routing Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.96
Fig. 6.148 Configuration of Subnet Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.97
Fig. 6.149 Configuration of Gateway Routing Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.97
Fig. 6.150 Configuration of Metric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.97
Fig. 6.151 TCN - Threshold Settings window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.98
Fig. 6.152 Configuration of B1 Threshold for SD alarm (tributary side) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.98
Fig. 6.153 Configuration of B1 Threshold for SD alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.98
Fig. 6.154 Date & Time window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.99
Fig. 6.155 Alarms menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.100
Fig. 6.156 Physical and Functional Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.101
Fig. 6.157 TX Way Payload Functional Alarms window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.103
Fig. 6.158 RST Tx STM-1 (BB-Modem) window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.104
Fig. 6.159 RX Way Payload Functional Alarms window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.105
Fig. 6.160 RST Rx STM-1 (BB-Modem) window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.106
Fig. 6.161 IDU Other Functional Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.107
Fig. 6.162 A.U. IDU User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.108
Fig. 6.163 Controller IDU User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.108
Fig. 6.164 Mem Key User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.109
Fig. 6.165 Mem Key Maint Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.109
Fig. 6.166 FAN IDU User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.110
Fig. 6.167 BB-Modem User Physical Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.111
Fig. 6.168 User Physical Alarms - IDU-ODU i/f window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.111
Fig. 6.169 System User Physical Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.112
Fig. 6.170 ODU User Physical Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.113
Fig. 6.171 ODU Maint Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.114
Fig. 6.172 ODU Maint Physical Alarms window - Wideband ODU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.114
Fig. 6.173 i/f CPU User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.115
Fig. 6.174 i/f Exp Cable User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.116
Fig. 6.175 i/f Exp Cable Maint Physical Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.116
Fig. 6.176 TCN - Alarm Threshold window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.117
Fig. 6.177 Station Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.117
Fig. 6.178 Measurements menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.118
Fig. 6.179 Unit Measurements window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.118
Fig. 6.180 Measurement - Record menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.120
Fig. 6.181 Performance menu (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.125
Fig. 6.182 Performance PM Setting window - Common Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.126
Fig. 6.183 Performance PM Setting window - Independent Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.127
Fig. 6.184 Configuration of RSPI Thresholds Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.128
Fig. 6.185 Configuration of RLT ODU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.128
Fig. 6.186 Configuration of TLT ODU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.128
Fig. 6.187 Performance Monitoring View window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.129
Fig. 6.188 RST Performance View: BB-Modem Trib Side (Quarter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.130
Fig. 6.189 RST Performance View: BB-Modem Trib Side (Day) window. . . . . . . . . . . . . . . . . . . . . . . . . . . 6.131
Fig. 6.190 RST Performance View: RX Chain - Radio Side STM-1 (Quarter) window. . . . . . . . . . . . . . . . . 6.131
Fig. 6.191 RST Performance View: RX Chain - Radio Side STM-1 (Day) window . . . . . . . . . . . . . . . . . . . 6.132
Fig. 6.192 RPS Performance View: RX Chain (Quarter) window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.133
Fig. 6.193 RPS Performance View: RX Chain (Day) window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.133
Fig. 6.194 RSPI Performance View: ODU - Tx Side (Quarter) window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.134
Fig. 6.195 RSPI Performance View: ODU - Rx Side (Quarter) window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.135
Fig. 6.196 RSPI Performance View: ODU (Day) window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.136
Fig. 6.197 Inventory window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.137
Fig. 6.198 PID window (e.g.: Controller) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.138
Fig. 6.199 USER window (e.g.: Controller) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.138
Fig. 6.200 User Inventory window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.139
I-9
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.201 Equipment Software window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.139
Fig. 6.202 About NetViewer window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.140
Fig. 6.203 About LCT window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.140
Fig. 6.204 Security window (Admin user class) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.142
Fig. 6.205 Window to enable the Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.142
Fig. 6.206 Field Editing for the insertion of the new password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.143
I-10
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
B
L
A
N
K

P
A
G
E
LIST OF TABLES
I-11
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
LIST OF TABLES
Tab. 6.1 Description of the push-buttons in the plug-in window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9
Tab. 6.2 Laser operating rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.31
Tab. 6.3 Independent switches depending on System Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.54
Tab. 6.4 ATPC management (ODU Narrowband) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.66
Tab. 7.1 Functional Alarms: description and severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2
Tab. 7.2 Physical Alarms: description and severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4
Tab. A.1 License Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1
LIST OF TABLES
I-12
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
B
L
A
N
K

P
A
G
E
1 - GENERAL INFORMATION
1-1
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
1 GENERAL INFORMATION
1.1 Subject and Purpose of the Manual
SRA4 is a STM-1 and 2xSTM-1 radio communication equipment for point-to-point
applications, using an high frequency indoor-outdoor architecture, designed to transfer
the SDH/SONET signals. SRA4 radio equipment is managed using the extended TNMP
protocol; the network protocol is TCP/IP.
SRA4 radio equipment is built up by:
one or two indoor shelves (IDU, indoor unit), providing the base band;
from one to four outdoor equipment (ODU, outdoor unit), containing RF devices.
ODU units are connected with the IDU by means of an IF cable;
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.
The ODU performs signal amplification and frequency up/down conversion to/from the
millimeter-wave frequency.
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 (F interface) or via 10 Base T Ethernet connection (Q interface).
This OMN manual provides the necessary instructions for the management, via PC, of
the SRA4 digital radio equipment with SVR 4.6. The management via software of the
equipment with SVR 4.6 can be executed as by NetViewer 7.0 (management system of
radio networks) as by LCT 6.1 (management system of the local terminal and/or of the
radio link).
For a detailed description of the units present in the system, refer to the UMN
manual of SRA4 equipment.
For the using modes of NetViewer/LCT, refer to the relevant operating guide.
Without a written authorization, it is forbidden to forward to third parties the
contents of the subject Manual.
The Customer can require a copy of the subject manual pointing out its code
(present on the cover rear-page).
1-2
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
1.2 Functionalities of the Equipment
The equipment SVR 4.6 supports the following functionalities:
Managed System Types:
1+0 w/o MST
1+1 Hot Stand-by w/o MST Single Tributary Interface
1+1 Hetero frequency w/o MST Single Tributary Interface
1+1 Hot Stand-by w/o MST Double Tributary Interface
1+1 Hetero frequency w/o MST Double Tributary Interface
2x(1+1) Frequency Diversity w/o MST Single Tributary Interface
2x(1+1) Frequency Diversity w/o MST Double Tributary Interface
2x(1+1) Hot Stand-by w/o MST Single Tributary Interface
2x(1+1) Hot Stand-by w/o MST Double Tributary Interface
2+0 w/o MST (with independent configuration of the two basebands)
2+1 w/o MST
3+1 w/o MST
Equipment traffic capacity
Tributary capacity: STM-1 or 2xSTM-1
Digital service channels: 2.048 Mbit/s (G.703) Way-Side
Auxiliary Data Channels: 64 Kbit/s V.11 or 64 Kbit/s G.703
Base-band interface:
STM-1 electrical ITU-T G.703
STM-1 optical ITU-T G.957 S-1.1
Modulation type
32 TCM + Reed-Solomon Concatenated Coding
128 TCM + Reed-Solomon Concatenated Coding
Pattern type:
AP (Alternate Polarization)
CC (Co-Channel)
ODU type
Narrowband
Wideband
Available loop-back types
Radio side up to tributary section
Tributary side up to tributary physical interface
Tributary side up to the modem interface
1+1 protection
RX radio side
TX tributary side
TX radio side
Control of the transmission power
ODU Narrowband. 2 ATPC levels (Pnom, Pnom-8). Range: 8 dBm
ODU Wideband. Linearized for ODU Wideband
Possibility of independent configuration of the BB-Modem units in the (2+0) System
Type without MST
1-3
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Configuration of the operating parameters
Transmission and reception frequency
Transmission power (ATPC)
Alarm parameters
Remote controls
Local loop-back (from LCT)
User channels (byte F1/ byte S(2,3))
ALS (Automatic Laser Shutdown)
Laser restart
Configuration of the co-channel operation
Management of J0 byte
Configuration of the error thresholds (TCN)
Measures
ODU transmitted power
RF RX power
Recordings
Performance Monitoring (independent counters for each measurement point)
Events
Report of inventory data
Alarms management
Diagnostics
Input of station alarms (max. 4)
System alarms restitution (max. 8)
Signalling of alarm threshold crossing
Software download
Local/remote download of the equipment software
Switching of the Controller banks
Copy of the active banks of the Controller
Alignment of the unit software
License management
Management of the hardware key
Management of the inventory data
hardware data (unit PID data, user data)
software data
Support of the TNMP protocol (base and extended) as management application
protocol
Management system
Local supervision of NEs and of the radio link via LCT
Remote supervision of the NEs of the radio network via NetViewer
Networking functions
RIPv1 protocol for the transport of the routing information
Propagation of static routing table
Notification of the dynamic routing table
Border Gateway
Ingress Summarization
Configuration of TCP/IP connection
IP address
1-4
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Static routing tables
Net-mask
configurable Ethernet MTU (Maximum Transfer Unit)
Management interfaces
F interface (RS-232) for the serial connection to LCT
Q interface (10/100 Base T) for the connection to LAN network
E interface (10 Base T) for the connection between the two IDUs in a system
with double IDU
Use of SOH bytes
Byte S23 as auxiliary channel
Byte S22 as ATPC channel
Byte S32 as management channel (R)
Management of Controller unit
Selection of the active memory bank
Software download from local PC or via remote
Equipment commissioning (with recording of the relevant performance) and
periodic tests
Local History Log (storing of the last events occurred on the equipment)
Switch of the synchronism source of the STM-1s for MS-AIS alarm (in case of
2xSTM-1 capacity)
Replacement of the alarm unit without traffic loss (only for the proper hardware
version of the 2xSTM-1 unit).
1.3 Testing and Warranty
Refer to the contract clauses for the information about testing and warranty.
1.4 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-5
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
1.5 Conditions of the Provision
The SRA4 plug-in is provided on CD-ROM and is included, together with the LCT
program, into the equipment provision.
The equipment CD-ROM includes:
the LCT program for the management of the radio link and/or of the local radio
equipment
the SRA4 plug-in.
The SRA4 plug-in can be included on demand into the CD-ROM of NetViewer.
1.6 Related Manuals
For the SRA4 equipment, the following manuals are available:
User Manual (UMN)
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 6.1 (OMN)
It contains the necessary informations for the configuration and control, by means
of a service PC, of SRA4 link and of the relative equipments.
NetViewer (OMN)
It contains the necessary informations for the configuration and control, by means
of a network PC, of SRA4 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.7 Lists of Abbreviations
AGC
Automatic Gain Control
AIS
Alarm Indication Signal
ALS
Automatic Laser Shutdown
The plug-ins available on the CD-ROM of NetViewer depend on the provision
conditions of NetViewer.
By default, the plug-ins for Cisco router and generic SNMP device are always
available.
All the other plug-ins are provided only on demand.
1-6
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
ALM
Alarm
AP
Alternate Pattern
ATM
Asynchronous Transport Mode
ATPC
Automatic Transmission Power Control
AUX
Auxiliary
BB
Base Band
BBE
Background Block Errors
BER
Bit Error Rate
CC
Co-Channel
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
ES
Errored Seconds
ETSI
European Telecommunications Standard Institute
EW
Early Warning
1-7
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
FD
Frequency Diversity
FERF
Far End Receive Failure
FPGA
Field Programmable Gate Array
FSK
Frequency Shift Keying
FSRC
Failed Switch Request Count
FSRD
Failed Switch Request Duration
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
1-8
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
LED
Light Emission Diode
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
PS
Power Supply
PSAC
Protection Switch Actual Count
1-9
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
PSAD
Protection Switch Actual Duration
PWR
Power
RAM
Random Access Memory
RDI
Remote Defect Indication
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
SCS
Switching Control Signal
SD
Signal Degrade
SDH
Synchronous Digital Hierarchy
SES
Severely Errored Seconds
SOH
Section OverHead
1-10
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
SONET
Synchronous Optical Network
SPI
SDH Physical Interface
SRA
Synchronous Radio Access
S.T.
System Type
Stby
Stand-by
STI
Single Tributary Interface
STM
Synchronous Transfer Module
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
1-11
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
UAS
UnAvailability Seconds
UHF
Ultra High Frequency
WS
Way-Side
XPIC
Cross Polarity Interference Canceller
1-12
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
B
L
A
N
K

P
A
G
E
2 - EQUIPMENT MANAGEMENT
2-1
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
2 EQUIPMENT MANAGEMENT
2.1 Introduction
This manual describes the graphic user interface to manage the SRA4 equipment. The
same graphic interface is specified for the LCT and the telecommunication network
management.
The configuration of a Network element (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 according the following procedure:
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.
EM doesnt allow to remove a mandatory unit without a previous change in the System
Type.
2.1.1 Local Craft Terminal (LCT)
LCT is a local personal computer which the operator uses to dialogue with the SRA4
equipment. By means of LCT it is possible to modify and configure up to three SRA4 at
the same time.
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 SRA4 equipment is not possible (for
hardware or software troubles), however LCT allows the system management.
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 SRA4
equipment, a D-9 female connector is used to implement the RS-232 interface.
2-2
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
To realize the connection via RS-232 to the SRA4 equipment, it is necessary to run from
PC a direct connection with 38400 bps bit rate.
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.
Fig. 2.1 IDU unit
2.2 User Classes and Security
2.2.1 User Classes
The user classes foreseen to access the system are the following ones:
Anonymous (Security disabled)
Admin User (administrator)
Read Write User (read/write user)
Read Only User (read only user)
The user login class restricts the operations allowed to the user, as specified here below:
read only users can only read, but not change, any system configuration;
Q interface is used only by NetViewer management program.
The Anonymous user class is present only for the access via LCT.
Alarm unit hardware key FAN unit BB-Modem#1 unit
Controller unit BB-Modem#2 unit
2-3
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
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 must login to the NE, giving to the NE controller the user login class and the
password for that class. Transmission of the protocol passwords is encrypted.
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 Management of the access to the network element
The concurrent access to the network element is achieved by allowing no more than one
user with user login class Anonymous, Admin User, ReadWrite User can login to 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 Anonymous, Admin User,
ReadWrite User 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 Read
Only.
The NE controller will record an event whenever an user with user login class
Anonymous, Admin User, ReadWrite User 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-4
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
B
L
A
N
K

P
A
G
E
3 - INSTALLATION OF PLUG-IN
3-1
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
3 INSTALLATION OF PLUG-IN
3.1 Overview
The application program for the control and management of SRA4 equipment is a
plug-in of the program for the management of SRA4 network/link.
The NetViewer/LCT program is able to acknowledge and, then, manage only the radio
equipments, whose plug-in has been previously installed.
To install the plug-in software, the NetViewer/LCT program must be already installed;
otherwise, first it is necessary to install the NetViewer/LCT program and, only after,
install the plug-in software.
The installation of plug-in software determines:
the possibility for NetViewer/LCT program to manage SRA4 radio equipment;
the addition of the help, relative to SRA4 management application, to the Help
menu of NetViewer/LCT program.
3.2 Installation Procedure
The plug-in can be installed during the setup of NetViewer/LCT or added/replaced later;
in this case, the procedure for the installation of the plug-in software related to SRA4
equipment is the following one:
Start the installation of the SRA4 plug-in (file ..\Disk1\setup.exe). If a plug-in
version is already installed, the system requires a confirmation to continue with the
installation and, then, continue and replace the already installed version.
The Welcome window opens on the screen (Fig. 3.1).
Click on Next button to start the installation.
At the end of installation, the Setup Complete window (Fig. 3.2) opens. Click on
Finish button to close and exit.
For more informations about the NetViewer and LCT programs, refer to the related
operating guide.
If NetViewer/LCT is already running, it is necessary to exit from it.
After the installation of the plug-in, it is necessary to restart NetViewer/LCT, if
already running, to apply the changes.
3-2
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 3.1 Installation of plug-in (1/2)
Fig. 3.2 Installation of plug-in (2/2)
3-3
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
3.3 Uninstallation of Plug-In
For the uninstallation of the plug-in, no special procedure is required; then follow the
typical uninstallation modality of a Microsoft Windows application (Add/Remove
Programs in Control Panel).
3-4
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
B
L
A
N
K

P
A
G
E
4 - COMMISSIONING VIA LCT
4-1
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
4 COMMISSIONING VIA LCT
This Chapter lists all the configuration and activation operations which must be executed
via LCT for the commissioning of the equipment.
The sequence of the operations is decribed by means of a step-by-step procedure; for
each operation, the heading of the table (upper cell on the right of the title) shows the
paragraph of the operating guide which you have to refer to in order to get more details.
Before starting the commissioning procedure, execute the following preliminary
operations:
Connect the LCT to the F interface of the equipment.
Check that the hardware key is inserted before switching on the equipment.
The IDU is provided with a hardware key, where the configuration of the equipment is
stored to allow an easy and fast replacement of the Controller.
The hardware key has the following characteristics:
it is the key for the backup of the equipment configuration; each modification of a
configuration parameter is stored in the non volatile memory of the Controller and
immediately also in the non volatile memory of the hardware key (EEPROM)
it is identified by:
serial number, which is univocal
the equipment type
it is strictly associated, after the switching on, to the equipment controller (the
Controller stores the serial number of the hardware key)
it contains the licence; the hardware key provided with the equipment contains the
licence ordered by the Customer.
Also a maintenance key is available (Repair Key), to be used only in case of fault to the
hardware key provided with the equipment. In the Repair Key there is stored only its own
serial number.
INTERFACE FOR THE
CONNECTION TO LCT
HARDWARE KEY
4-2
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Diagnostics of the hardware key
For the diagnostics of the hardware key, the following diagnostic signalings via software
are available:
Key Missing or Key Mismatch
This signaling is displayed in one of the two cases:
the hardware key is disconnected. The controller detects, by means of a
dedicated sensor, the availability of the memeory key. If the detection fails,
the hardware key is disconnected
the inserted key is not valid or it belongs to a different equipment.
Key Fault
The hardware key is fault or it is not accessible: the configurations stored in the non
volatile memory of the controller are used.
Statuses of the Controller
The Controller of the equipment can assume one of the following operating statuses:
No Setting Mode
the external and internal interfaces are enabled; only reading operations are
allowed. All the configuration settings are refused.
Halt mode
the controller does not execute any action. It refuses also the connection to LCT.
To exit from this status, it is only possible to reset the controller or switch off the
equipment (the correct hardware key must be inserted).
Start-up of Controller
The Controller executes the same actions made after a software reset, a bank switching
or a switching of the IDU unit. As soon as the embedded software exits from the boot
phase, it controls the hardware key.
if the hardware key is disconnected, the system enters in the status of Halt Mode
if the hardware key is faulted, the system enters in the No Setting status. The
configurations stored in the non volatile memory of the controller are used.
in the inserted hardware key is different from that of the SRA 4 equipment, the
controller loads the settings from the key, all the existing licences are lost.
if a repair key is detected, after the start-up of the controller, the system starts with
the default configuration and licence.
In the following flow diagram, the management of the hardware key is displayed.
Run-time operation of Controller
During the normal run-time operation, the status of the system can be:
Normal Mode: the hardware key is On Line without alarms
No Setting Mode: this status is reached as consequence of: disconnection of
hardware key, insertion of a hardware key different from the expected one, or a
faulted hardware key.
If a repair key is acknowledge, the configurations and the licences present in the non
volatile memory of the controller will be loaded on the repair key.
4-3
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Replacing of the hardware key
The hardware key must be always connected to the IDU during the normal operation of
the equipment and never extracted unless in case of replacement of the alarm unit (card
fail of the alarm unit) or need to replace the key itself (hardware key fail).
If the replacement of the hardware key is required, the maintenance must be executed
without executing the software reset or the switching of the radio unit.
In case of faulted hardware key during the operation, the Key Fault alarm raises and
the controller enters in No Setting Mode modality.
The repair key must be connected to replace the damaged one.
When the controller detects the repair key, all the radio configurations and the licences
are copied into the new hardware key and the controller exits from the Setting Mode
modality to operate in normal modality. The serial number is copied to the non volatile
memory of the controller and the new hardware key is a perfect copy of the old one.
The Repair key must be inserted with equipment switched on. If it is inserted with
equipment switched off, at the switching on all the configurations are reset to
their default value.
IDU Run-time
hardware key not
congruent (Key
Missing or Key
Mismatch)
hardware key
faulted
(Key Fault)
hardware key
disconnected
(Key Missing or
Key Mismatch)
No Setting Mode
4-4
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 1 Login to NE par. 6.4
Create, using NetBuilder, a map for the connection to the local NE, setting the IP address 192.168.255.3 for the
NE; this is the predefined local IP address for each equipment. It is also possible to use one of the local
connection map already provided with LCT (e.g.: Localne.map).
Run LCT and load the map for the connection to the local NE (by default: LocalNE.map).
Verify that the connection to the equipment is execute successfully; this causes the loading of the equipment
profile, with the displaying of the SRA4 icon.
Open the NE (double ckick on the equipment icon or Open command of the equipment pop-up menu),
executing the login with the Admin user class, and check that the operating menu is loaded for the control and
configuration of the equipment.
4-5
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 2 Configuration of System Type par. 6.7.1.1
Open the Status and Config Equipment.
Click on System button. The System Configuration window opens.
Double click on System Type field. The editing window opens.
Select the wished System Type. Possible values are:
(1+0) without MST, unprotected system
(1+1) Hot Stand-By Single Tributary Interface (STI) without MST
(1+1) Frequency Diversity Single Tributary Interface (STI) without MST
(1+1) Hot Stand-By Double Tributary Interface (DTI) without MST
(1+1) Frequency Diversity Double Tributary Interface (DTI) without MST
2x(1+1) Frequency Diversity Single Tributary Interface (STI) without MST
2x(1+1) Frequency Diversity Double Tributary Interface (DTI) without MST
2x(1+1) Hot Stand-By Double Tributary Interface (DTI) without MST
2x(1+1) Hot Stand-By Single Double Tributary Interface (STI) without MST
(2+0) without MST, unprotected system
(2+1) without MST, protected system
(3+1) without MST, protected system
Confirm pressing OK button.
4-6
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 3 Configuration of the modulation and the capacity par. 6.7.1.1
Open the Status and Config Equipment window.
Double click on System Config field. The editing window opens.
Select the wished modulation and capacity for the system. Possible values are:
STM-1 32 Alternate Polarization
STM-1 32 Co-Channel
STM-1 64 Co-Channel
STM-1 128 Co-Channel
2xSTM-1 128 Alternate Polarization
2xSTM-1 128 Co-Channel
Confirm pressing OK button.
The availability of a given modulation/capacity combination depends on the licence installed on the system.
4-7
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 4 Configuration of the system units par. 6.7.1.1
4-8
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Configure the IDU and ODU units present in the system.
For each IDU unit: double click on BB-Modem field. The editing window opens. Possible values are:
Electrical 2xSTM-1
Optical 2xSTM-1
Select the wished IDU type and confirm with OK.
For each ODU unit: double click on ODU. The editing window opens. Possible values are:
Wideband
Narrowband
Select the wished ODU type and confirm with OK.
For all the systems with double IDU, also the Controller, FAN and Alarms units must be equipped.
For each one of them, double click on the corresponding field: the configuration window opens.
Select Equipped and confirm with OK.
Once they have been equipped and switched on/supplied, be sure that they are on-line.
Step 4 Configuration of the system units par. 6.7.1.1
4-9
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 5 Configuration of ID link par. 6.7.1.1.1
This configuration step is optional: it is not necessary for the correct operation of the system.
Click on the Channel button related to the channel whose link must be configured (in the systems with single
IDU, the button is called Link ID (J0)): the corresponding Link ID (J0) window opens.
For the tributary and radio side, after having enabled the management of byte J0 (J0 Management field), set
the configuration parameters of the link:
J0 Inserted on radio side and on tributary side
J0 Expected on radio side and on tributary side
Double click on the configuration field: the window for the assignment of the value opens.
Once inserted the values, confirm with OK.
NOTE: For DTI systems, it is suggested to configure the J0 inserted for the Radio Side to the same value for
both the STM-1s.
4-10
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 6 Configuration of the external interface par. 6.7.1.2
Q interface
Click on Ext Interfaces button. The External Interface Setting window opens.
Click on Q Interface button. The Q Interface Parameters window opens.
It is necesary to set the following parameters.
Bit Rate: value of bit-rate for Q interface. It can be:
Not Working
10 Mbit/s
100 Mbit/s
Electrical i/f Duplexing: operating modality of Q interface (10/100 BaseT). It can be:
Not working
Full duplex
Half duplex
For the setting: doublre click on the parameter field. In the window that opens, select the wished parameters
and confirm pressing OK.
4-11
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Auxiliary channels
Click on AUX Channel button. One of the following window opens according to the system type configured on
the equipment.
For each one of the auxiliary channels present in the windows, the default value is Disable.
Enable the auxiliary channels you want to use.
To do this: double click on the field corresponding to the channel to enable. The editing window opens.
Select Enabled (or the F1 byte insert) and confirm with OK.
For system types (1+0), (1+1), (2+0) and 2x(1+1)
For system types (N+1)
4-12
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Output commands
Opent the Status and Config Equipment window.
Click on Output Commands button. The following window opens.
For each one of the external commands, iti s possible to assign a name and enable (On) or not (Off) the
command itself.
To insert the name: double click on Name field, in the window that opens insert the wished name and confirm
with OK.
To enable the command: double click on Command field, in the window that opens select On and confirm with
OK.
4-13
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Station Alarms
Click on Station Alm button. The following window opens.
For each one of the four alarms in input, it is possible to assign a name and decide the electrical level
corresponding to the alarm condition.
To insert the name: double click on Alarm Name field, in the window that opens insert the wished name and
confirm with OK.
To enable the command: double click on Polarity field, in the window that opens select the wished polarity
(Gnd or Floating) for the alarm and confirm with OK.
4-14
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 7 Configuration of the Co-Channel operation par. 6.7.1.4
The Co-Channel operation can be configured and managed only in (2+0) System Type.
Click on Co-Channel button. The Co-Channel window opens.
Double click on the Synch for CC Pair #n field: a window opens to define if the synchronization source is
selected by the operator or, in automatic way, by the system. In this way, the Synch Forcing push-button is
displayed in the window. Select the wished value and confirm with OK.
Click on Synch Forcing button: the window that opens allow defining the Master unit or the Slave unit as
synchronization source. This operation causes a temporary loss of payload and of the control channels. Double
click on Synch Forcing field. In the window that opens, select the wished value and confirm with OK.
Double click on Polarization field: a window opens where it is possible to define the polarization of the
co-channel pair. Possible values are V (vertical) or H (horizontal). Select the wished value and confirm with OK.
4-15
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 8 Configuration of protection par. 6.7.1.3
The configuration of the protection for the SRA4 equipment is different depending on the set System Type.
System Type (1+1) and 2x(1+1) (par. 6.7.1.3.1)
Click on Protection button. The Protection Status & Configuration window opens.
4-16
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
The protection parameters configurable by operators are the following ones.
Protection Mode
Behaviour of the equipment when a radio channel has switched and the cause of the switching is ended. The
possible switching modalities are:
Unrevertive
Revertive 1
Revertive 2
Select the wished value for the parameter and confirm with OK.
Switch Mode
The operator can choose if the switching must occur in automatic or manual mode. Possible values are Auto
and Manual. Select the wished value for the parameter and confirm with OK.
Trib Forcing (only system type (1+1) Double Tributary Interface)
It forces the use of the tributaries in input to BB-Modem 1, to BB-Modem 2 or leaves the choice to the system.
I possibili valori sono:
Trib 1
Trib 2
None
ODU Forcing (only system type (1+1) Hot Stand-by)
It forces the use of the radio interface 1, of the radio interface 2 or leaves the choice to the system.
ODU 1
ODU 2
None
DEM Forcing
It forces the use in reception of radio channel 1, of radio channel 2 or leaves the choice to the system.
Dem 1
Dem 2
None
4-17
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
System Type (N+1) (par. 6.7.1.3.2)
Click on Protection button. The Protection Status & Configuration window opens.
4-18
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
The protection parameters configurable by the operator are the following.
Switch Criteria Enabling
It defines the enabling criteria of the switching. Possible values are:
None
Minor alm disabled
Major alm disabled
Remote Tx Prioritary Channel
It defines the channel to be protected in transmission to the remote end. Possible values are:
Channel 1 on Remote Tx
Last Protected Channel on Remote
Switch Criteria Forcing
It simulates on a given channel the existence of an alarm of the severity indicated to artificially change the
decisions of the logic for the protection switching. Possible values are:
normal
Minor alarm
Major alarm
Critical alarm
Channel in Service
Protected
4-19
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 9 Configuration of BB-Modem unit par. 6.7.1.10
Click on Configure button related to the BB-Modem unit to configure. The BB-Modem Config window opens.
The configurable parameters are the following.
Cable Lenght
Select the lenght of the IF cable. It can assume two values: Short or Long.
IF Output Level
Only in case of Narrowband ODU, it defines the output level on IF cable. Possible values are: +5dBm and
-10dBm.
TX Mod Inverted Spectrum
Only in case of Narrowband ODU, it defines if invert (Inverted) or not (Not Inverted) the transmission spectrum
of the modem.
4-20
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
XPIC
This configuration is optional: it is not necessary for the correct operation of the system.
Only for co-channel system. It allows cancelling the residual of the hortogonal channel. Possible values are:
ON (activation of the canceller)
Forced OFF (canceller disabled)
Step 9 Configuration of BB-Modem unit par. 6.7.1.10
4-21
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 10 Configuration of the Wideband ODU unit par. 6.7.1.12.1
Open the Status and Config Equipment window. Click on Configure button related to the ODU you want
to configure. The ODU Config window opens.
The first parameter to set is Freq Mode: it indicates the type of RF frequency modality used by ODU: two
modalities are allowed: Continuous or Freq Plan. Double click on the configuration field: the related editing
window opens. Select one of the two modalities and confirm with OK. Depending on the chosen modalities, the
configurable fields in the window are different.
Frequency modality: Continuous
The parameters to set are the following:
Channel Spacing [kHz]
TX Freq [kHz]
RX Freq [kHz]
Double click on the selection field. Set the wished value and confirm with OK.
For the detailed description of the parameters, refer to par. 6.5.1.11.1.
Warning: in the Hot Stand-by and Co-Channel systems, the value of the TX Freq parameters for the two ODUs
present in the system must be the same.
4-22
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Frequency modality: Freq Plan
Execute the following sequence of operations:
1- set Frequency Plan Activation to On
2- set Freq Ch#1
3- set First Channel ID
4- set Last channel ID
5- set Frequency Plan Activation to Off.
6- set RF Channel ID, which points out the frequency used to transmit.
If the parameters are not congruent, an error message is returned and the inserted parameters are refused. It is
necessary to repeat the sequence of operations inserting the correct set of parameters.
For the detailed description of the parameters, refer to par. 6.5.1.11.1.
Warning: in Hot Stand-by and Co-Channel systems, the values of the TX Freq parameters for the ODUs
present in the systems must be the same.
4-23
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Setting of the transmitted power parameters
If the ATPC modality is disabled (ATPC Management = Disable), set the value of the power you wish to
transmit (Ptx field)
If the ATPC modality is enabled (ATPC Management = Enable), it is necessary to set the following
parameters:
Pmin
ATPC Range
ATPC Threshold
For the detailed description of the parameters, refer to par. 6.5.1.11.1..
Setting of the parameters relevant to the length of IF cable
In the Commands area, the Comp IF Cable Mode parameter is, by default, Auto. At switching on of the ODU,
the procedure for the compensation of the IDU-ODU cable starts (Compensation Cable Running indication).
At the end of the procedure, the End Compensation Cable indication appears. Once ended the procedure of
cable compensation, set the Comp IF Cable Mode parameter to Manual.
If, at the end of the procedure, the Compensation Cable Out of Range indication appears, it is necessary to
check that the IDU - ODU connection cable is properly installed and has no excessigve length. Then repeat the
procedure of cable compensation, activating it manually:
set the Compensation Cable Mode field to Manual
set the Start Compensation Cable to ON and wait for the completion of the procedure (End Compensation
Cable message).
If the procedure does not end correctly (Compensation Cable Out of Range), the Squelch SW Activation is ON
and the ODU does not transmit.
4-24
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 11 Configuration of the network parameters par. 6.7.3
IP Address (par. 6.7.3.2)
Open the Status and Config Network IP Address window.
Click on Modify button to pass to read/write modality.
Set the IP address of the equipment and the related Net-Mask, which must be assigned by the network
administrator on the basis of the planning of the supervision network. Confirm with OK button.
4-25
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Static Routing Table (par. 6.7.3.4)
Open the Status and Config Network Static Roting Table window.
Click on Modify button to pass to read/write modality.
The displayed window becomes the following one.
Set the entries of the static routing table according to what foreseen by the planning of the supervision network.
Confirm with OK. It is possible to set up to 16 entries.
For each entry, it is necessary to set the following parameters:
Destination Address: it is the destination IP address; it can be both the address of an host and the address
of a different network/subnetwork
SubNet-Mask: it is the SubNet-Mask associated to the destination IP address
Gateway: it is the IP address of the gateway used to reach the destination of the routing entries
Metric: it is the number of hops which separates the equipment from the destination indicated in the routing
entry.
NOTE: in order to delete an entry, it is sufficient to set the relevant Gateway field to 0.0.0.0.
4-26
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
NE Parameters (par. 6.7.3.3)
Open the Status and Config Network NE Parameters window.
The operator can configure the ETH MTU parameter for the Ethernet interface. Double click on the relevant
field: the Field Editing window opens. If the operator does not choose one of the default values and selects
Other, another Field Editing field appears, where it is possible to insert the wished value.
The operator can enable the use of the Telnet port. Double click on the relevant field: the Field Editing window
opens. Select Enabled or Disabled and confirm with OK.
For each network interface present in the system, the operator can enable the foloowing parameters:
RIPv1: it allows managing the information for the updating of the routing table.
To configure it, double click on the RIPv1 field corresponding to the interested interface: the selection
window opens. Select the wished value and confirm with OK.
Static Route Propagation: it allows enabling/disabling, clicking on the Enable check-box, the propagation
of all the static routing information through the interested interface. Select the wished value and press OK.
Border Gateway: it allows enabling/disabling, clicking on the Enable check-box, the Border Gateway
functionality on the interested functionality. Select the wished value and confirm with OK.
Ingress Summarization: it allows enabling/disabling, clicking on the Enable check-box, the Ingress
Summarization on the interested interface. Select the wished value and confirm with OK.
4-27
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 12 Configuration of TCN par. 6.7.4
Open the Status and Config TCN Setting window.
It is possible to configure, for the BB-Modem units, on radio side and tributary side, the BER value that, if
exceeded, generates the corresponding alarm.
For each configuration parameter: double click on the corresponding field. The editing window opens to select
the BER value. The possible values are the following:
10E-5
10E-6
10E-7
10E-8
10E-9
Once chosen the wished BER value, confirm with OK.
4-28
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Step 13 Configuration of the RSPI parameters par. 6.10.7
Open the Performance PM Setting window.
Define if the RSPI thresholds (RLT and TLT) to set are the same for all the ODU units installed in the system
(Common) or if they change ODU by ODU (Independent).
Double click on the RSPI Threshold Setting insertion field: the editing window opens. Choose the type of
setting and confirm with OK.
If the choice has been Independent, the operator shall configure the interested threshold for each ODU of the
system.
If the choice has been Common, a single configuration field will be displayed, valid for all the ODUs of the
system.
In both cases, double click to open the editing window and confirmation clicking on OK.
5 - DOWNLOAD OF CONTROLLER UNIT SOFTWARE
5-1
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
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 4
network/link and by means of the command from equipment menu in NetViewer / LCT
program.
The software download maintains the existing configurations. If the new software adds
new configurations, these assume their default value only if the software is compatible
with the configurations already present on the equipment.
Otherwise, the new configurations will assume a value coherent with the already
existent configurations.
The software download can be executed both locally and remotely:
Local SW download: from LCT (F interface)
Local SW download: from LCT via modem (F interface)
from NetViewer (Q interface)
Download operations are faster if executed by interface Q (LAN Ethernet).
The download via FTP doesnt cause any interruption in the operation of
Controller unit, which is always on-line.
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 (besides to run the
TNMP connection again) disactivate the dial-up connection and, then, restore it.
5-2
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
5.2 Download via FTP of IDU software
The download procedure is the following:
Select the zionare FTP Transfer in Software menu. The Connect To Server
window opens.
Fig. 5.1 Download procedure of IDU software via FTP (1/5)
Login to the server inserting the following parameters:
User Name: Admin
Password: sysmanager
The FTP Client opens, showing the tree of the directories of the PC on the left side
and the tree of the equipment directories on the right side.
To execute the software download, the PC with the file to be transferred must be
switched on and connected to SRA4 network.
5-3
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Open the directory of the PC where the file 7133.pec is contained. Select the file
and drag it to the corresponding IDU directory on the equipment.
A window opens requiring to confirm the operation. Confirm pressing Yes.
5-4
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
The download window opens, showing the progress bar of the running operation.
This window automatically closes at the ened of download.
At the end of the operation, the new software version is present on the stand-by
bank.
5-5
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
If yoy wish to run this bank, open the IDU Software Banks window (Fig. 5.7) and
press the Switch Banks push-button. The IDU disconnects and restarts.
Fig. 5.6 IDU Software Banks window
If the new downloaded software contains a different version of FPGA, the LED on the
controller becomes red and the Software Mismatch notification appears. At this point,
the user can align the FPGA version with that contained in the new software (pressing
the FPGA Version Alignment button).
The switch operation of the banks does not cause traffic loss.
This operation causes traffic loss.
5-6
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
5.3 Download via FTP of ODU software
The download procedure is the following:
Select the zionare FTP Transfer in Software menu. The Connect To Server
window opens.
Fig. 5.7 Download procedure of ODU software via FTP (1/5)
Login to the server inserting the following parameters:
User Name: Admin
Password: sysmanager
The FTP Client opens, showing the tree of the directories of the PC on the left side
and the tree of the equipment directories on the right side.
To execute the software download, the PC with the file to be transferred must be
switched on and connected to SRA4 network.
5-7
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Open the directory of the PC where the file 7533.hex is contained. Select the file
and drag it to the corresponding ODU directory on the equipment.
A window opens requiring to confirm the operation. Confirm pressing Yes.
5-8
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
The download window opens, showing the progress bar of the running operation.
This window automatically closes at the ened of download.
5-9
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
At the end of the operation, the new software version is present on the stand-by
bank.
If yoy wish to run this bank, open the ODU Software Banks window (Fig. 5.12) and
press the Switch Banks push-button. The ODU disconnects and restarts.
Fig. 5.12 ODU Software Banks window
The switch operation of the banks does not cause traffic loss.
During the FTP download FTP of the ODU file (7533.hex), it is necessary to keep
closed this window
5-10
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
B
L
A
N
K

P
A
G
E
6 - OPERATING GUIDE
6-1
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6 OPERATING GUIDE
6.1 Overview
The configuration and the control of the SRA4 equipment through PC are possible only
using the NetViewer/LCT program and if the relevant plug-in is installed.
NetViewer allows the supervision of networks and radio equipment, while LCT allows
managing the equipment of a radio link and/or the local equipment.
6.2 Architecture of the System with Double IDU
Some system configuration need two IDUs (and related ODUs) to support the required
functionalities. The two IDUs need to be connected via E-link (the two controllers are
linked together so that the radio unit can be seen as a single Network Element) and via
Expansion Port. This second cable allows traffic and hardware managed alarms and
commands to be exchanged between the two IDU units.
The two IDU units are identifiable from the fact that IDU #1 unit (also called main) has
the configuration hardware key inserted, whereas the IDU #2 unit (also called
expansion) does not.
Double IDU architectures are required for (N+1) System Types and for (1+1) protected
System Types.
The four BB Modem Units can be numbered in the following way:
IDU #1 - BB Modem #1
Both the IDUs are equipped with a controller card, but only one of the two shall be the
Network Element controller (the other controller card can be seen as an expansion of
the main controller)
Main controller will:
The equipment SVR 4.6 is managed starting from LCT 6.1 and from NetViewer 7.0.
As regards the usage of the modalities of use of the NetViewer/LCT program, refer
to the related operating guide.
SRA4 supports, as management application protocol, the extended TNMP
protocol.
6 - OPERATING GUIDE
6-2
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
manage the complete NE, collecting alarms and configuring also the expansion
IDU (and related ODUs) via expansion controller;
save all configurations of the NE
manage communication channels with LCT, NetViewer and other TCP/IP routers;
support the software downloading on itself and all other cards/units.
Expansion controller will:
act as an intermediary among the main controller and the slaves of the expansion
rack (IDU and ODUs);
run procedures related to the safety of the IDU (e.g. Automatic Laser Shut-down);
support Radio Protection Switching functionalities in N+1 System Types.
6.3 Software Functions
The main characteristics of the management via software of the equipment are the
following:
Plug-in Functionalities
Hardware hardware key Management
License
Security
6.3.1 Plug-in Functionalities
The application program for SRA 4 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
(2+0) w/o MST, protected system
2x(1+1) Frequency Diversity Single Tributary Interface (STI) w/o MST
(starting from SVR 4.5)
2x(1+1) Frequency Diversity Double Tributary Interface (DTI) w/o MST
(starting from SVR 4.5)
(2+1) w/o MST, protected system (starting from SVR 4.4)
(3+1) w/o MST, protected system (starting from SVR 4.4)
2x(1+1) Hot Stand-By Single Tributary Interface (STI) w/o MST (starting from
SVR 4.6)
2x(1+1) Hot Stand-By Double Tributary Interface (DTI) w/o MST (starting from
SVR 4.6)
traffic capacity:
STM-1 electrical
STM-1 optical
2xSTM-1 electrical
6 - OPERATING GUIDE
6-3
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
2xSTM-1 optical
pattern:
AP (Alternate Polarization)
CC (Co-Channel, starting from SVR 4.4)
operating functions:
equipment configuration and outfitting
configuration of IDU parameters
configuration of ODU parameters
loopback management for tests on the equipment
control of equipment configuration and status
control of the status of transmission (TX) and reception (RX) sections
control of ODU unit status
protection functions
ALS functionality (automatic shutdown of the laser source)
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 the network
selection/change of the active memory bank storing the unit software for the
Controller unit
download of Controller unit software and of the ODU software
measuring and recording of RF RX power values of ODU unit
measuring and recording of events related to the equipment operation
backup of the equipment configuration data by means of the hardware key
BER threshold crossing notification
Enabling/disabling of RIP protocol
management of J0 byte on tributary and radio side
management of co-channel operation
configuration of alarm threshold (TCN)
measuring and reading of the performances of the transceiver system
alarm management
license management
networking functions
management of the equipment Security
implementation of the Account Log functionality
commissioning of the equipment and recording of the relevant performance.
6.3.2 Hardware hardware key Management
The IDU unit equipped with the hardware key is defined as main IDU (or IDU 1), while
the other will be the expansion IDU (o IDU 2). Once configured, they have not to be
switched.
During normal operation, all configurations are saved in main controller non volatile
memory and copied into the Configuration hardware key. No configuration is saved in
expansion controller.
Here below, the following topics are described:
The switching between main and expansion IDU seriously affects the payload
traffic and auxiliary channels.
6 - OPERATING GUIDE
6-4
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Controller operating modalities
Main/Expansion Configuration Management
6.3.2.1 Controller operating modalities
The Controller card will support the following working modes (beyond the normal one):
Frozen: all the software controlled switch configurations and positions are frozen,
while it is possible to change any other configuration. Hardware controlled switches
continue to work if previously configured in automatic way.
No setting: all incoming configurations are refused, while hardware and software
driven switches continue to properly work if already configured in automatic way
Stand-by: mode entered as a consequence of an FPGA mismatch (the mismatch
may arise only after a new software version activation while the system was on).
Software driven switches are frozen and configuration/command changes (FPGA
related) are refused for the whole system; also configuration changes relevant to
ODU are refused. Alarms will be managed. Payload and auxiliary channels will
continue to properly work because the FPGA card was already correctly
configured. In protected configurations, hitless switch protecting the received radio
signal will keep on working, if automatic configuration was previously chosen.
Microprocessor communication channel between IDU and Wideband ODU will
keep on working. Also R channel will keep on working.
Mismatch x,y: when a BB-modem unit different from that physically equipped on
the equipment is configured, a mismatch condition is detected. It is necessary the
intervention of the operator to properly configure the BB-Modem type.
Waiting for IDU 1: controller has not detected a Configuration hardware key
connected to the alarm unit at start up, so it waits for a communication on E-link.
No communication with LCT is possible while in this state and no interaction with
the other boards of the IDU is performed. The three severity LEDs mounted on the
controller card, will blink ciclically, giving an optical indication of the anomalous
situation.
Suspended: serial interface is activated to support a possible connection with
LCT. This mode is only intended to allow the LCT connection in order to view
alarms or perform a software download. The controller does not perform any action
on the Radio Unit:
all the software controlled switch configurations and positions are frozen.
Hardware controlled switches continue to work if previously configured in
automatic way
all incoming configurations and commands are refused.
The three severity LEDs mounted on the controller card, will blink simultaneously,
giving an optical indication of the anomalous situation.
Waiting for SW download: serial interface is activated to support a possible
connection with a PC with FTP client. This mode is only intended to allow a
software download of the main IDU. The three severity LEDs mounted on the
controller card, will blink simultaneously, giving an optical indication of the
anomalous situation.
6 - OPERATING GUIDE
6-5
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.3.2.2 Main/Expansion Configuration Management
6.3.2.2.1 IDU numbering in 2 IDU units based System Types
In the systems which foresee two IDU units, these are called IDU1 and IDU2. The IDU1
is always the Main one, the IDU 2 is always the expansion one. At system start up, the
IDU with the hardware key inserted in the alarm unit is automatically configured as Main,
while the other one is configured as Expansion.
6.3.2.2.2 Main/Expansion negotiation at controller start up
At system start-up or after a software reset, controller checks the hardware key
presence in the alarm units slot of the IDU it is inserted in:
if the Controller detects a hardware key (its not important if it is valid or not), it
configures itself as main controller and, in case of System Types based on the
operation with two IDU units, tries to set up a communication with the other IDU
unit via E-link channel;
if the Controller does not detect the presence of the hardware key, it waits for a
communication started from the other IDU.
If a communication is established and just one of the two IDUs is connected to a
hardware key, everything will go on without any problem.
If an hardware key is inserted in both the IDU units, they are forced to Suspended
modality (the operator must intervene to remove the hardware key wrongly connected
with to the expansion IDU and must reset the controllers, otherwise the software
embedded into the controller does not start).
In the system with single IDU, only the IDU1 is foreseen, but the controller will select a
behaviour as IDU 2, if the hardware key is not inserted at the controller start-up.
If no hardware key is inserted, the system does not work.
6.3.2.2.3 Loss and recovery of communication between main and expansion
controllers
In case of communication loss between the two controllers, main controller will refuse
any configuration affecting IDU 2 and ODUs connected to it, while expansion controller
will keep on working as an isolated entity (it cannot be reached via LCT/EMS), assuring
safety conditions. In the meanwhile main controller has to periodically try to start the
communication and expansion controller has to wait for a communication started from
the main one.
As soon as communication is recovered, main controller has to perform all hardware
and software checks, relevant to IDU 2 only and ODUs connected to it, foreseen in case
of first connection.
6.3.2.2.4 Check of the HW and SW versions
After the starting checks related to the hardware key, the controller verifies the hardware
and software compatibility of the different components:
in the (1+1) systems, both the ODUs must be of the same type (Wideband or
Narrowband).
6 - OPERATING GUIDE
6-6
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
in the Co-Channel systems, the ODUs must be of Wideband type.
in the (N+1) and 2x(1+1) systems, both the IDUs must have the same software
version.
If the hardware or software compatibility is not assured, the related Mismatch indications
are issued.
In case of controller card replacement and during a new software version activation,
BB-modem cards keep on running. A misalignment in BB FPGA versions may arise.
If the controller detects a different version between the currently working FPGA version
and the one stored in its software, it activates a specific alarm (FPGA mismatch) and
Stand-by mode will be entered. User will be allowed at any time to select (via LCT/EMS)
one of the following actions:
load the FPGA versions contained in the software package in the BB-modem
boards;
download a new software.
If the user does not perform any of the two actions, the FPGA version contained in the
embedded software package will be loaded next time the BB-modem card is switched
on (card extraction/insertion or IDU power off / power on).
6.3.3 License
The possibility to configure the modulation and the capacity of the NE is subjected to
licence. To enable the wished configuration, it is necessary to have the proper licence.
The parameters subjected to licence are the following:
Modulation (32 TCM, 64 TCM or 128 TCM)
Capacity (1xSTM1 or 2xSTM1)
Pattern (AP or CC)
The Payload, System Type and Channel Spacing parameters are under license. All the
information related to system configurations and the available licenses are stored in the
If a Wideband ODU is configured, but connected to a Narrowband ODU (or vice
versa), there is not mismatch indication, but the indication of ODU disconnection.
Conditions of software mismatch can issue also after a controller replacement. In
this case, the operator must intervene.
Loading a new FPGA version while a BB-modem board is running will result in
traffic loss for that BB-modem board.
The 64 TCM modulation is available starting from equipment SVR 4.6.
6 - OPERATING GUIDE
6-7
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
hardware key. A copy of the hardware key is available in the not volatile memory of the
Controller unit, to assure a back-up in any possible condition.
The factory license is loaded on each hardware key delivered with the equipment.
The default license, inserted in the embedded software, is the following:
Modulation: 32 levels
Capacity: STM-1
Pattern: AP
The following functions are under license in the following way:
Modulation: High Density
Capacity: 2xSTM-1
Pattern: AP/CC
6.3.4 Security
The plug-in allows enabling/disabling the equipment Security, that is the possibility to
access to the equipment only for authorized users; each user is characterized by a user
class and by a password. The user class defines the access privileges to the equipment.
The configuration of the Security (enabling status and password) is stored into the
equipment memory.
The system foresees three different user classes:
Read Only: access to the functions in reading only mode
Read Write: access to the functions as in reading as in writing mode, with the
exception of the functions reserved to the Admin user class
Admin: access to the all the functions as in reading as in writing mode.
It is possible to set/change, through the operating menu, the configuration of the
Security only if the login is executed with the Admin user class.
The functions reserved for the Admin user class are the following ones:
configuration of the equipment IP address
all the configurations of the cards
all the commands
the inventory data
the external alarms
the ATPC values
configuration of the NE date and time
configuration of the Security
In case of disabled equipment Security, in NetViewer/LCT also the Anonymous
user class is available, which does not require password and has the same
privileges of the Admin class, except for the Security configuration function.
Only one user at a time can access the equipment using writing privileges (Admin
or Read Write user class).
6 - OPERATING GUIDE
6-8
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
copy/paste operation of the NE configuration file.
6.4 Uploading of profile
In NetViewer/LCT, to activate the Element Manager functions, it is necessary to upload
the equipment profile and then to access to the equipment (Open command of the
pop-up menu of the NE icon in the map).
The map (Fig. 6.1) represents the graphical interface of NetViewer/LCT for the access
to the radio equipment.
At the map opening, NetViewer/LCT tries to connect itself with all the equipment recalled
into the map itself; for each equipment the connection phase is executed in the following
way:
if it is detected a communication error, the system displays a generic NE icon with
grey background color (unvoluntary disabling status)
if the connection is successfully executed, the program executes the login and the
uploading of the equipment profile and it displays the icon that identifies the
equipment type.
Fig. 6.1 Example of map with SRA4 equipment
In case of connection towards an equipment of which it has not been installed the
relevant plug-in, the system displays the unknown equipment icon; the
equipment is not supported.
In NetViewer, the background color of the equipment name points out the
summarized status of the equipment itself, that coincides with the alarm with the
highest severity. Such a function is not supported by LCT.
6 - OPERATING GUIDE
6-9
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.5 Push-buttons Key in Plug-in Windows
In the user interface windows displayed by the equipment plug-in, there are some
push-buttons for the window management, whose functionality is described here below.
6.6 Structure of the Operating Menu
The operating menu of SRA4 is a tree menu whose root is the name/IP address of the
NE. The NE operating menu can be accesses selecting the NE in the map. The NE
operating menu is available only if the NE is open (Open command from GUI) and has
the following options (par. 6.2).
Status and Config: allows configuring the SRA 4 equipment and controlling its
operating status (par. 6.7).
Alarms: allows checking the alarms status on the equipment and, then, identifying
the cause of a possible fault (par. 6.8).
Measurements: allows measuring the RF RX Power and analysing the measures
related to IDU and ODU units present in the system (par. 6.9).
Performance: allows recording and displaying the system performances
(par. 6.10).
Inventory: allows accessing the inventory data (stored in EEPROM) of the
equipment units, reading them or writing possible notes (for example, installation
date, type of fault, ecc.) and recording them (par. 6.11).
Security: allows enabling/disabling the equipment Security and to configure the
password for the different user classes to the equipment (par. 6.12).
The equipment operative menu implements also the following NE applications of
NetViewer/LCT:
Commissioning Report: it allows setting and executing the Commissioning
recording of the equipment
Tab. 6.1 Description of the push-buttons in the plug-in window
Push-button Function
It iconizes the window in the low left corner of the GUI working area
It closes the window
It closes the window applying the possible executed changes or configurations
It closes the window without applying the possible executed changes or
configurations
It switches the field of the window from ReadOnly to ReadWrite modality
6 - OPERATING GUIDE
6-10
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Local History Log: it allows displaying the last alarms stored on the equipment
History: functionality that provides a report with all the events occurred on the
equipment
Alarm List: functionality that provides the list of all the alarms currently active on
the equipment
Performance Report: functionality that provides a report of the performance
(subdivided by type) of the NE, stored into the Database of NetViewer
Fig. 6.2 Operating menu of SRA 4 equipment plug-in
6.7 Configuration and Status of the System
The operator can display the operative status of the equipment and configure the system
parameters by means of the Status and Config menu.
The Performance Report application is available only in NetViewer starting from
release V8.0.
The applications of NE, Commissioning Report and Local History Log, are
implemented starting from SVR 4.5 of SRA 4.
The NE applications have different characteristics and operating modalities
depending if they are executed by NetViewer or by LCT.
For the description of the NE applications, refer to the operating guide of
NetViewer/LCT.
The Local History Log application of NE is available only on LCT.
6 - OPERATING GUIDE
6-11
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.3 Status and Config Menu
Status and Config menu has the following options:
Equipment: equipment status and configuration (par. 6.7.1);
Software: management of the equipment software (par. 6.7.2);
Network: configuration of the network parameters for the network element
(par. 6.7.3);
TCN Settings: configuration of the alarm thresholds (par. 6.7.4);
Date and Time: configuration of the date and time of the system (par. 6.7.5).
6.7.1 Equipment Status & Configuration
Selecting Equipment in Status and Config menu (Fig. 6.3), the Equipment Status &
Configuration window opens. It displays the operative status of the system and the
possible alarms present on the different units and allows configuring the main operating
parameters of the equipment.
All the commands in Software and Network menus and the Date and Time
command can be activated only by users belonging to Administrator class.
6 - OPERATING GUIDE
6-12
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.4 Equipment Status & Configuration window (e.g.: 2x(1+1) FD DTI System Type)
Status indications
Connection status of the unit
The application program for the management displays the connection status with
the Controller unit (on the IDU unit) for each slave unit present in the system. The
connection status of the slave units can be:
DISCONNECTED status (DIS), 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).
CONNECTED status (CON), identifies the beginning phase of the connection
and control by Controller unit.
The functional layout of the equipment displayed in the Equipment Status &
Configuration window depends on the System Type.
The push-buttons available in the Equipment Status & Configuration window
depends on the System Type configured on the equipment and on the present
licences.
The Protection push-button is present only for 2x(1+1), (1+1) and (N+1) System
Types.
The Co-Channel push-button is available only for (2+0) and 2x(1+1) System
Types.
The Copy Config and Paste Config push-buttons are activve only in case of login
with administrator privileges (Admin user class). With disabled Security, the
push-buttons are active also in case of login with Anonymous user class.
In case of login with read-only privileges (Read Only user class), the setting fields
of the configuration windows are all read only.
6 - OPERATING GUIDE
6-13
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
ON LINE status (OnL), the slave unit is present and physically equipped in
the IDU unit and communicates correctly with the Controller unit; furthermore,
the firmware version matches with that of the Controller unit.
MISMATCH status (MIS), the slave unit is present and physically equipped in
the IDU unit and the communication with the Controller unit is active, but it
does not match to the current equipment configuration or the firmware version
is not congruent with that of the Controller unit.
The signalling of the connection statuses of the slave units with the Controller is
automatically updated by Controller unit itself, 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.
License Fee Status
It is a read only field that shows the status of the license present in the system. It
can assume the values:
STM-1 Normal Density, Alternate Polarization
STM-1 Normal Density, Co-Channel (starting from SVR 4.4)
STM-1 High Density, Alternate Polarization
STM-1 High Density, Co-Channel (starting from SVR 4.4)
2xSTM-1 High Density, Alternate Polarization
2xSTM-1 High Density, Co-Channel (starting from SVR 4.4)
System Type
it shows the current System Type of the equipment. It can be configured in the
System Configuration window (par. 6.7.1.1).
System Config
it shows the type of modulation. It can be configured in the System Configuration
window (par. 6.7.1.1).
Alarm signaling
No setting mode
the switching strategy of the system operates correctly (only in automatic mode),
but all the setting operations of the commands/configurations are refused.
System Frozen (Switches)
the system switches are frozen while all the other commands and configurations
can be set. The payload continues to pass over the same path without
interruptions. If a switching alarm occurs in this state, the switching does not take
place and the payload is lost (but in this case, there are two contemporary faults).
Configuration not congruent with HW
it indicates that the set configuration is not congruent with the equipped hardware
and, then, the correct operation of the system is not allowed.
Mis
in case of mismatch between the setting of BB type (electrical or optical) and the
type of BB physically inserted in the slot, the Mismatch indication for BB and two
wordings are displayed:
in black, the type of HW set via SW
in red, the type of HW physically equipped
To correct the mismatch condition, it is necessary to equip via software the BB type
really used (System Configuration window)
6 - OPERATING GUIDE
6-14
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Manual operation on Equipment
it indicates that on the equipment a manual forcing has been set. The possible
causes of this alarm are described in the following table:
Parameter
Value that activates
the indication
NOTES
SWITCH MODE Manual In 1+1 and N+1
TX mod spectrum inversion Different from Auto Only with Narrowband ODUs
LASER FORCING Off Only for optical BB-modem
LASER RESTART Different from Auto Only for optical BB-modem
Loop Back (for STM1#1 or
STM1#2)
Different from Disable
BB Loop Back INT Different from Disable
Loop Back EXT Different from Disable
Modulator mode Different from Normal
Compensation cable
Procedure
Running Only with Wideband ODUs
XPIC forced Off Only for co-channel systems
6 - OPERATING GUIDE
6-15
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
IDU
This section displays the current status of the sub-units composing the IDU unit:
Alarms
the connection status and the alarm status of the alarm unit are reported. The
possible indications are: green (normal) and red (fault).
Controller
the connection status and the alarm status of the Controller unit are reported. The
possible indications are: green (normal) and red (fault).
Mem Key (only IDU#1)
the alarm status of the backup hardware key is reported. The possible indications
are: green (normal) and red (fault).
FAN
the connection status and the alarm status of the fan unit are reported. The
possible indications are: green (normal) and red (fault). The wording in
the lower part of the box shows the fan operating status (Fan On: fan is operating;
Fan Off: fan is not operating)
BB-Modem
besides the used tributary (optical or electrical) and the maximum system capacity
(2xSTM-1), the connection status and the alarm status of the baseband - modem
1 unit are reported. The possible indications are: green (normal) and red
(fault). The Configure button opens the BB-Modem Config window
(par. 6.7.1.10) to configure the parameters of the modem 1 unit.
ODU section
This section shows the type of ODU installed in the system (Wideband or Narrowband)
and the alarm status of the unit itself. The possible indications are: green (normal)
and red (fault). The Configure button opens the ODU Config window for the
configuration of the operating parameters of the ODU Wideband unit (par. 6.7.1.12.1) or
the ODU Narrowband unit (par. 6.7.1.12.2).
For 2x(1+1) (starting from SVR 4.5), (2+0), (2+1) and (3+1) System Types, also the
indications related to the second IDU present in the system are displayed.
The Configure button is active only if the unit is on line (OnL indication).
The number of ODU units present in the system changes depending on the
System Type.
The Configure button is active only if the unit is on line (OnL indication).
6 - OPERATING GUIDE
6-16
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Severity Alarms box
This box displays the LEDs corresponding to the four possible alarm severities of the
system:
Critical: a service affecting condition has occurred and an immediate corrective
action is required.
Major: a service affecting condition has developed and it is possible to delay the
corrective action.
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.
Push-buttons
The following push-buttons are present in the left part of the window.
System
opens the System Configuration window (par. 6.7.1.1)
Ext Interface
opens the External Interface Setting window (par. 6.7.1.2)
Protection (only for System Type (1+1))
opens the Protection window (par. 6.7.1.3)
Co-Channel (only for (1+1) FD and (2+0), starting from SVR 4.4)
opens the Co-Channel window (par. 6.7.1.4)
Testing
opens the Testing window (par. 6.7.1.5)
Maintenance (starting from SVR 4.5)
opens the Maintenance window (par. 6.7.1.6)
License Upgrade
opens the Feature Control window (par. 6.7.1.7)
Copy Config
starts the Copy procedure of the equipment configuration (par. 6.7.1.8)
Paste Config
starts the Paste procedure of the equipment configuration (par. 6.7.1.9)
When an alarm occurs in the system, the LED with the related severity lits on
video (red) and an exclamation mark is put before the name of the alarm.
6 - OPERATING GUIDE
6-17
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.1.1 System Configuration window
Pressing the System push-button in the Equipment Status & Configuration window
(Fig. 6.4), the System Configuration window opens, for the configuration of the main
system parameters. For each unit displayed in the window, the current connection
status is reported.
Fig. 6.5 System Configuration window
System Type 2x(1+1) DTI
System Type (2+0)
6 - OPERATING GUIDE
6-18
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
License Fee Status indication
It is a read only field, which displays the status of the license present in the system.
Possible values are:
STM-1 Normal Density, Alternate Polarization
STM-1 Normal Density, Co-Channel (starting from SVR 4.4)
STM-1 High Density, Alternate Polarization
STM-1 High Density, Co-Channel (starting from SVR 4.4)
2xSTM-1 High Density, Alternate Polarization
2xSTM-1 High Density, Co-Channel (starting from SVR 4.4)
Configuration of System Type
The user can configure the equipment with the following System Types:
(1+0)
(1+1) Hot Stand-By STI
(1+1) Frequency Diversity STI
(1+1) Hot Stand-By DTI
(1+1) Frequency Diversity DTI
2x(1+1) Frequency Diversity STI
2x(1+1) Frequency Diversity DTI
2x(1+1) Hot Stand-By STI
2x(1+1) Hot Stand-By DTI
(2+0)
(2+1)
(3+1)
Clicking twice with the left button of the mouse on the insertion field, the Field Editing
window opens for the choice of the desired value.
Fig. 6.6 Configuration of System Type
The (2+1) and (3+1) System Types are implemented starting from SVR 4.4.
The 2x(1+1) Frequency Diversity STI and 2x(1+1) Frequency Diversity DTI System
Types are implemented starting from SVR 4.5.
The 2x(1+1) Hot Stand-By STI and 2x(1+1) Hot Stand-By DTI System Types are
implemented starting from SVR 4.6.
6 - OPERATING GUIDE
6-19
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Configuration of modulation and capacity
The user can choose one of the following values:
STM-1 32 Co-Channel (starting from SVR 4.4)
STM-1 64 Alternate Polarization (starting from SVR 4.6)
2xSTM-1 128 Co-Channel (starting from SVR 4.4)
Fig. 6.7 Configuration of modulation and capacity
Configuration of Radio Channels destination (only System Type (2+0))
In this System Type, the two radio streams are completely independent. They can be
routed in two different directions or in the same direction. This setting is useful to
correctly manage the supervision channels. The operator has the following options:
Same destination
a single remote radio exists, in correspondence of the two independent radio
channels;
Different destinations
two different remote radios exist in correspondence of the two independent radio
channels.
The availability of the slave configurations depends on the license present in the
system and on the System Type.
6 - OPERATING GUIDE
6-20
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.8 Configuration of Radio Channel Destination
Configuration of Alarm unit
The Alarm unit is always equipped. Clicking twice with the left button of the mouse on
the insertion field, the Field Editing window opens.
Fig. 6.9 Configuration of Alarm unit
Configuration of Controller unit (Master and Slave & RS Controller)
The Controller unit provides the communication and control function of the system: it is
always equipped. Clicking twice with the left button of the mouse on the insertion field
of the Controller Slave &RS Controller (System Types with two IDUs), the Field Editing
window opens: only the Payload Controller value is present.
Fig. 6.10 Configuration of Controller unit
Configuration of FAN unit
FAN unit is always equipped: the fans are useful to avoid an excessive heating of the
critical components inside the IDU unit. Clicking twice with the left button of the mouse
on the insertion field, the Field Editing window opens.
Fig. 6.11 Configuration of FAN unit
6 - OPERATING GUIDE
6-21
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Configuration of BB-Modem unit
The operator can choose the type of the type of BB-Modem unit to install (optical or
electrical tributary). This choice is available for all the System Types. Possible values
are:
Optical 2xSTM-1
Electrical 2xSTM-1
Fig. 6.12 Configuration of BB-Modem unit
Configuration of ODU unit
The operator can choose the type of ODU unit to install. This choice is available for all
the System Types. Possible values are:
Wideband
Narrowband
Fig. 6.13 Configuration of ODU unit
The number of BB-Modem units present in the system depends on the System
Type configured on the equipment.
If an IDU unit is in MISMATCH status, the Mis red indication is displayed in the
related windows and the configuration of the parameters for that IDU is not
allowed.
The number of ODU units present in the system depends on the System Type
configured on the equipment.
6 - OPERATING GUIDE
6-22
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Management of J0 byte (starting from SVR 4.4)
Pressing the Link ID (J0) push-button for the System Type with single IDI, or the
Channel push-button in the Link ID (J0) box for the System Type with two IDUs, in the
System Configuration window (Fig. 6.5), the Link ID (J0) window related to the
selected BB-Modem unit opens (par. 6.7.1.1.1).
Modify BB-Modem Config/Modify System Config push-button (only System Type
(2+0))
Pressing the Modify BB-Modem Config push-button for the System Type (2+0), the
Config Type Setting window (par. 6.7.1.1.2) opens, where it is possible to configure the
two BB-Modem units in common or independent way.
6.7.1.1.1 Management of J0 byte
The byte J0 belongs to the Regenerator section of SDH frame: it is used to verify that
the transmitting station is the expected one. This byte is written by each transmitting
station and it is extracted from the frame by the receiving station.
For each interface (tributary side and radio side for each BB card), it is possible:
to enable/disable the management of the J0 byte (which influences both the STM-1
signals);
to define the value of expected J0 (independent for each STM-1 signal);
to define the value of J0 to be transmitted (independent for each STM-1 signal);
to enable/disable the AIS insertion for TIM (Trace Identifier Mismatch) alarm (which
influences both the STM-1 signals);
to define the TIM activation interval (which influences both the STM-1 signals);
to define the TIM deactivation interval (which influences both the STM-1 signals).
The operator can configure the parameters for the management of the byte J0 both on
the tributary side and on the radio side in the Link ID (J0) window.
The values of J0 Expected and J0 Inserted can be set, typing a string (maximum length
of 15 characters) for each one of the two parameters. Here below, the Link ID (J0)
window for the System Type (2+0) is displayed.
If the ODU connected to the IDU is not of the type selected via software, the
Mismatch wording does not appear, but the ODU remains Disconnected until the
operator does not provide to select the correct slave type.
If the current configuration is Type Setting=Common, the push-button in the
System Configuration window has name Modify System Config.
If the current configuration is Type Setting=Independent, the push-button in the
System Configuration window has name Modify BB-Modem Config.
The management of the byte J0 is available starting from SVR 4.4.
6 - OPERATING GUIDE
6-23
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.14 Link ID (J0) BB-Modem1 window
Management of TIM alarm
Number of Wrong J0 for TIM Activation
the operator can set the number of wrong samples of the byte J0 which must be
received before issuing the TIM alarm on the tributary side. The allowed range of
values is: 1-100 (default = 10). Double click on the related field to open the
following Field Editing window.
Fig. 6.15 Configuration of TIM alarm activation
Number of Wrong J0 for TIM Deactivation
the operator can set the number of right samples of byte J0 which must be received
before clearing the TIM alarm on the tributary side. The allowed range of values is:
1-100 (default = 10). Double click on the related field to open the following Field
Editing window.
Fig. 6.16 Configuration of TIM alarm deactivation
The window layout and the present parameters depends on the System Type
6 - OPERATING GUIDE
6-24
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
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 for the selection of the parameter value opens.
Fig. 6.17 Window for the J0 Management Tributary Side (TX) selection
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.
To access the following Field Editing window, click twice on the value field.
Fig. 6.18 Window for enabling/disabling AIS Insertion for TIM (Tributary Side)
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 following Field Editing window, click twice on
the value field.
Fig. 6.19 Window for the insertion of J0 Inserted Tributary Side
In DTI systems, it is suggested to set J0 Inserted Radio Side equal for all the
STM-1s.
6 - OPERATING GUIDE
6-25
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
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 following Field Editing window, click twice
on the value field.
Fig. 6.20 Window for the J0 Expected Tributary Side insertion
J0 Dropped
This is a read-only field, which shows the value of byte J0 dropped from the frame
on the tributary side.
Configuration of 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 following Field Editing window for the selection of the parameter value opens.
Fig. 6.21 Window for the J0 Management Radio Side (Rx) selection
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.
To access the following Field Editing window, click twice on the value field.
Fig. 6.22 Window for the AIS Insertion for TIM (Rx) enabling/disabling
6 - OPERATING GUIDE
6-26
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
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 following Field Editing window, click twice on the
value field.
Fig. 6.23 Window for the J0 Inserted Radio Side insertion
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 following Field Editing window, click twice on
the value field.
Fig. 6.24 Window for the J0 Expected 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.
6.7.1.1.2 Config Type Setting window
In the System Type (2+0), starting from SVR 4.5, each one of the two BB-Modem units
can be configured with values independent with respect to the other, in relation to the
system capacity (STM-1 or 2xSTM-1) and to the modulation format (32TCM, 64 TCM or
128TCM).
Clicking on the Modify System Config push-button of the System Configuration
window (Fig. 6.5), the Config Type Setting window opens.
In the 2xSTM-1 System Types, on the radio side, the same value of J0 must be
inserted for the two streams STM-1 #1 and STM-1 #2.
6 - OPERATING GUIDE
6-27
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.25 Config Type Setting window
Clicking twice with the left button of the mouse on the Config Type Setting field, the
Field Editing window opens for the selection of the wished configuration (Common =
same parameters for the two BB-Modem units, Independent = independent
parameters).
Fig. 6.26 Configuration of Config Type Setting
For the configuration of the System Config parameter, refer to System Configuration
window paragraph.
When the equipment is configured to operate in co-channel modality, the
Controller of the Network Element verifies that the two BB-Modem cards are
configured with the same values of the above mentioned parameters before
accepting the configuration.
In any moment, it is possible to modify the parameters both of the Common
modality and of the Independent modality.
The active configuration, currently used by the equipment, is pointed out by the
"Active Setting" wording. If the user wishes to change the modality from Common
to Indipendent or vice versa, in order to avoid the traffic loss, it is necessary to
verify the correct configuration to set and, if necessary, to change it before
executing the Common/Independent switch.
If it was necessary to change from System Type (2+0) to System Type (1+0), it is
necessary to set the Common modality to avoid the traffic loss.
6 - OPERATING GUIDE
6-28
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.1.2 External Interface Setting window
Pressing the Ext Interface button in the Equipment Status & Configuration window
(Fig. 6.4), the External Interface Setting window opens, where the user can configure:
the operation of the laser (par. 6.7.1.2.1)
the Q interface (par. 6.7.1.2.2)
the output commands (par. 6.7.1.2.3)
the input station alarms (par. 6.7.1.2.4)
the auxiliary channels (par. 6.7.1.2.5)
Fig. 6.27 External Interface Setting window (System Type: 2x(1+1) FD DTI)
System Config indication
This field displays the current system configuration. It can be:
STM-1 64 Alternate Polarization (starting from SVR 4.6)
2xSTM-1 128 Co-Channel (starting from SVR 4.4)
The system configuration can be modified in the System Configuration window
(Fig. 6.5).
The window layout and the displayed parameters depend on the SVR and on the
System Type configured on the equipment.
6 - OPERATING GUIDE
6-29
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Q Interface button
It opens the Q Interface Parameters window (Fig. 6.33) for the configuration of the
parameters of Q interface.
Output Commands button
It opens the Output Commands Setting window (Fig. 6.36) for the configuration of the
external parameters.
Station Alm button
It opens the Station Alarms window (Fig. 6.39) for the configuration of the station
alarms.
SDH Channel section (only 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 opens for the parameter
configuration. Possible values are Enabled and Disabled. By default, value of the
parameter is Enabled.
Fig. 6.28 Configuration of Automatic Laser Shut Down
Slave Interface Configuration section
When the system capacity is 2xSTM-1, the operator can disable the second STM-1
tributary. This option allows setting the 2xSTM-1 capacity even if only one of the two
STM-1 signals must be transmitted; the operator will enable the second STM-1 port
when a second tributary signal must be transmitted. The disabling of the STM-1 #2
tributary port causes:
the masking of all the alarms related to the second tributary signal;
the disabling of the measurement of the quality and unavailability parameters of the
involved tributary signal (both on the radio and tributary side);
the switching off of the laser interface (if present);
Clicking twice with the left button of the mouse on the insertion field, the following Field
Editing window opens. Possible values are Enabled and Disabled. By default, the
parameter value is Disabled.
The availability of the slave configurations depends on the license present in the
system and on the System Type.
6 - OPERATING GUIDE
6-30
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.29 Configuration of Masking STM-1 #2
Laser Management button
It opens the corresponding BB-Modem Payload window (Fig. 6.30), for the
management of the laser.
AUX Channel button
It opens the corresponding AUX Channel BB-Modem window (par. 6.7.1.2.5), for the
enabling/disabling of the auxiliary channels present in the system.
6.7.1.2.1 BB-Modem Payload window
Pressing the Laser Management push-button (present only for BB-modem with optical
interface) in the External Interface Setting window (Fig. 6.27), the BB-Modem
Payload window opens, where the operator can configure the laser operation.
Fig. 6.30 BB-Modem Payload window
Parameters configuration
Laser Restart
If the laser is on and a loss of the reception signal occurs for a period longer than
500ms, the status becomes off and the user can select the wished modality for
the restart of the laser beam among the following ones: Auto (default), Manual and
Manual for Test (Recc. ITU-T G.664).
Auto modality: after a delay about of 100s, the laser is activated for a period
of 2 0.25s. If the signal is received by the remote terminal and the cause that
has determined the switching off has been removed, the system passes to the
normal operating status with Laser Restart: Auto modality;
The BB-Modem Payload window is present starting from SVR 4.4. In the previous
SVR, the Laser Restart, Laser Forcing field and the Laser Status indication are
inserted in the External Interface Setting window.
The switching from automatic to manual status is possible only if the laser is
state off, otherwise a message error is returned to the user.
6 - OPERATING GUIDE
6-31
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Manual modality: the laser is activated for a period of 2 0.25s. If the signal
is received by the remote terminal and the cause that has determined the
switching off has been removed, the system passes to the normal operating
status with Laser Restart: Auto modality;
Manual for Test: the laser is activated for a period of 90 10s. If the signal is
received by the remote terminal and the cause that has determined the
switching off has been removed, the system passes to the normal operating
status with Laser Restart: Auto modality.
If the cause that has determined the switching off of the laser has not been
removed, the Laser Restart parameter come backs anyway to Auto modality.
Clicking twice on the insertion field with the left button of the mouse, the Field Editing
window opens.
Fig. 6.31 Configuration of Laser Restart
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. If
the selected value is off, the laser status is off until a manual operation of the user
occurs. Selecting Off, the laser status doesnt change until an operator manual
command. Clicking twice on the insertion field with the left button of the mouse, the
Field Editing window opens.
Fig. 6.32 Configuration of the Laser Forcing
Tab. 6.2 Laser operating rules
ALS Laser Forcing Laser Status
Enabled ON as defined by ALS
Enabled OFF OFF
Disabled ON ON
Disabled OFF OFF
6 - OPERATING GUIDE
6-32
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Signalings
Laser Status (only optical IDU)
It is a read only parameter, which shows the laser operation status. It can assume
the values: On (laser switched on) or Off (laser switched off).
6.7.1.2.2 Q Interface Parameters window
Pressing the Q Interface button in the External Interface Setting window (Fig. 6.27),
the Q Interface Parameters window opens, for the configuration of the parameters
related to the Q communication interface (10/100BaseT). This is used for the transport
of the TMN information of the SRA 4 radio network towards a supervision center.
The window opens in read only modality (grayed fields). To modify the values reported
in the window, press the Modify button: the configuration fields switch to write modality.
Fig. 6.33 Q Interface Parameters window (write modality)
Indication of Bit Rate status
This field shows the current value of the bit-rate for Q interface. It can be:
Not Working
10 Mbit/s
100 Mbit/s
Indication of Electrical i/f Duplexing status
The operator can set the operating modality of the Q electrical interface (10/100 BaseT).
The values that can be selected are:
Autosensing
Half duplex
Full duplex
Configuration of Bit Rate
The operator can set the values of the interface bit-rate. Possible values are:
Autosensing
10 Mbit/s
100 Mbit/s
window opens.
6 - OPERATING GUIDE
6-33
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.34 Configuration of Bit-Rate
Configuration of Electrical i/f Duplexing
The operator can set the operating modality of the Q interface (10/100 BaseT). Possible
values are:
Half duplex,
only one terminal at a time can talk and the other one listens;
Full duplex,
the two terminals can talk contemporarily;
Autosensing,
Q interface automatically adapts to work in the modality of the remote terminal,
which can be Half duplex or Full duplex.
window opens.
Fig. 6.35 Configuration of Electrical i/f Duplexing
6.7.1.2.3 Output Commands Settings window
Selecting Output Commands in the External Interface Setting window (Fig. 6.27), the
Output Commands Setting window opens, where the user can configure up to 4 output
commands.
Fig. 6.36 Output Command Settings window
6 - OPERATING GUIDE
6-34
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
It is possible to assign a name to each output command, clicking twice on the related
description field: the Field Editing window opens for the insertion of the desired string
(max. 16 characters).
Fig. 6.37 Output Command description
The operator can activate or deactivate each one of the four output commands by
means of the Command box. Clicking twice on this field, the Field Editing window
opens. The values configurable by the user are:
Off,
to disable the command;
On,
to enable the command.
Fig. 6.38 Enabling of Command
6.7.1.2.4 Input Station Alarms window
Pressing the Station Alm button in the External Interface Setting window (Fig. 6.27),
the Input Station Alarms window opens.
Fig. 6.39 Station Alarms window
By default, the alarm carried on the input lines of the station alarms are identified by a
generic label. For each input line of the station alarms, from NetViewer it is possible:
If the hardware hardware key is not inserted in the IDU or a mismatch occurs in
the configuration, the hardware key Not Inserted or Mismatch alarm signaling
is displayed in the lower part of the window.
6 - OPERATING GUIDE
6-35
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
set the label (Station Alarm) with which the carried alarm will be displayed in the
plug-in windows and in the Alarm List
insert a description (Alarm Name) to identify the function associated to the carried
alarm (right entry-box).
The configuration procedure is the following one:
click twice on the in the entry-box of an alarm line; the configuration window opens
insert the label/description to associate to the carried alarm on the selected line
confirm the setting clicking on OK.
Fig. 6.40 Name/descripiton configuration window for station alarms
Name configuration
Description configuration
For each one of the available station alarms, the user can configure the Polarity
parameter, to set the electric level corresponding to the alarm logic condition. Clicking
twice on this field, the Field Editing window opens for the selection of the parameter
configuration.
Two alarm logics can be configured:
Ground = alarm (Gnd=Alarm) (default condition);
Floating = alarm (Floating=Alarm).
Fig. 6.41 Configuration of Polarity Alarm 1
This configuration is not available from LCT.
6 - OPERATING GUIDE
6-36
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.1.2.5 AUX Channel BB-Modem window
*** (1+0), (1+1), (2+0) and 2x(1+1) System Type ***
Pressing the AUX Channel button in the External Interface Setting window (Fig. 6.27),
the corresponding AUX Channel BB-Modem window opens, where the user can map
and enable/disable the operation of the auxiliary channels related to the selected
BB-Modem unit.
Fig. 6.42 AUX Channel BB-Modem window
Service Channel Mapping (starting from SVR 4.6)
The operator can select the type of interface (V.11 or G.703) of the auxiliary signal at 64
kbit/s to map into the F1 byte for each System Type. The other 64 kbit/s signal will be
automatically mapped into S23 byte (except for (N:1) systems). Clicking twice with the
left button of the mouse on the insertion field, the Field Editing window opens.
Fig. 6.43 Configuration of Service Channel Mapping
64 kb/s channel (V11 interface)
The user can enable (Enabled) or disable (Disabled) this auxiliary channel. Clicking
twice on the insertion field with the left button of the mouse, the Field Editing window
opens.
Fig. 6.44 Configuration of Enable 64 kb/s V11
6 - OPERATING GUIDE
6-37
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
64 kb/s channel (G703 interface)
The user can enable (Enabled) or disable (Disabled) this auxiliary channel. Clicking
twice on the insertion field with the left button of the mouse, the Field Editing window
opens.
Fig. 6.45 Configuration of Enable 64 kb/s G703
WS channel (2Mbit/s channel, G703 interface)
The operator can enable (Enabled) or disable (Disabled) the auxiliary Way Side
channel. Clicking twice on the insertion field with the left button of the mouse, the Field
Editing window opens.
Fig. 6.46 Configuration of Way Side (WS)
*** (N+1) System Types ***
Pressing the AUX Channel button in the External Interface Setting window (Fig. 6.27),
the corresponding AUX Channel BB-Modem window opens, where the operator can
enabled or disable the operation of the auxiliary channels related to the selected BB
Modem unit.
Fig. 6.47 AUX Channel IDU #1 BB-Modem 1 window (example)
Byte F1 insert
The operator can configure the operation of byte F1 according to one of the following
values:
Disable
64 Kbit/s G.703 Insert
64 Kbit/s V.11 Insert
6 - OPERATING GUIDE
6-38
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Clicking twice with the left button of the mouse on the insertion field, the following Field
Fig. 6.48 Configuration of F1 byte
Configuration of Way-side
The operator can enable the WaySide auxiliary channel (Enabled) or disable it
(Disabled). Clicking twice with the left button of the mouse on the insertion field, the
following Field Editing window opens.
Fig. 6.49 Configuration of Way Side (WS)
6.7.1.3 Protection
The protection scheme which can be used on the SRA 4 equipment are:
(1+1) Hot Stand-by, for the protection against hardware failures of the reception
and transmission failures (RF and IF sections)
(1+1) Frequency Diversity, to add a protection also against the unbalancings in the
propagation of the radio signal as fading and multipath interferences (the hitless
switching is required in the reception section)
2x(1+1) Frequency Diversity, it is a protection scheme identical to (1+1) Frequency
Diversity, but with two (1+1) independent systems within the same Network
Element
2x(1+1) Hot Stand-by, it is a protection scheme identical to (1+1) Hot Stand-by, but
with two (1+1) independent systems within the same Network Element
(2+1) and (3+1) Frequency Diversity, with hitless switching in the reception section
(1+1) Double Tributary Interface, for the protection against the failures of the
tributary line and the base band unit.
The equipment with System Type (1+1) STI do not provide tributary protection.
6 - OPERATING GUIDE
6-39
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
The type of protection is then different for (1+1) or 2x(1+1) systems (par. 6.7.1.3.1) and
(N+1) systems (par. 6.7.1.3.2).
6.7.1.3.1 Protection in (1+1) and 2x(1+1) System Types
Pressing the Protection button in the Equipment Status & Configuration window
(Fig. 6.4), in case of System Type (1+1) and 2x(1+1) (this starting from SVR 4.5), the
Protection window opens, where the user can configure the protection modality for the
equipment.
Fig. 6.50 Protection Status & Configuration window (System Type 2x(1+1) FD DTI)
System Type indication
It displays the System Type of the equipment (par. 6.7.1.1).
Protection Mode (only for Switch Dem)
The operator can configure the behaviour of the equipment when a radio channel
switched and the cause of the switching is terminated. Possible switching modalities
are:
Unrevertive
the system does not operate on a default channel. When the protection is required,
it switches and continues to operate on the switched channel even when the cause
of the switching is terminated.
In all the Hot Standby System Types, the ODU unit which goes on-line at start-up
is not fixed but must be configured by the operator. This because the switch is of
unrevertive type and none of the two ODUs is prioritary.
The window layout and the present parameters depend on the System Type
6 - OPERATING GUIDE
6-40
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Revertive 1
the system operates, by default, on the radio channel 1 (associated to BB-Modem
1 and ODU 1). When the protection is required, the system switches to radio
channel 2 (associated to BB-Modem 2 and ODU 2). When the request of protection
is terminated, the system returns to operate on radio channel 1.
Revertive 2
the system operates, by default, on the radio channel 2 (associated to BB-Modem
2 and ODU 2). When the protection is required, the system switches to radio
channel 1 (associated to BB-Modem 1 and ODU 1). When the request of protection
is terminated, the system returns to operate on radio channel 2.
window opens for selection of the desired value.
Fig. 6.51 Configuration of Switching Type
Switches Forcing section
Switch Mode
The operator can choose if the switching must occur in automatic or manual
modality. Clicking twice with the left button of the mouse on the insertion field, the
Field Editing window opens for the selection of the desired value.
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 all the switches at the same time.
Fig. 6.52 Configuration of Switch Mode
Trib Forcing
This field exists only for (1+1) Freq Diversity DTI and (1+1) Hot-Stby DTI System
Types. For DTI System Type, in TX (from tributary interface to radio interface), the
user can choose to force the use of the tributaries in input to BB-Modem 1 (Trib
The modality of the HSBY and Tributary switches is always Unrevertive (no
channel is privileged).
6 - OPERATING GUIDE
6-41
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
forcing=Trib 1), or to BB-Modem 2 (Trib forcing=Trib 2), or not to force any tributary
and let the system automatically select one of the two tributaries in input (Trib
forcing=None). Default value is None. Clicking twice on the insertion field with the
left button of the mouse, the Field Editing window opens for selection of the
desired value.
Fig. 6.53 Configuration of Trib Forcing
ODU Forcing
This field exists only for (1+1) Hot-Stby STI and (1+1) Hot-Stby DTI System Types.
For Hot-Stby System Types, in TX, only one radio interface transmit (while the
other one in stand-by). The user can choose to force the use of the radio interface
1 (ODU forcing=ODU 1), or the radio interface 2 (ODU forcing=ODU 2), or to let
the systen automatically selects one of the two (ODU forcing= None). Default value
is None. Clicking twice on the insertion field with the left button of the mouse, the
Field Editing window opens for selection of the desired value.
Fig. 6.54 Configuration of ODU Forcing
Dem Forcing
The field exists in all the System Types (1+1) System Types. In RX, only the radio
channel 1 or the radio channel 2 can be used. The user can choose to force the
use of the radio channel 1 (Dem forcing=Dem 1), or of the radio channel 2 (Dem
forcing=Dem 2), or to let the system automatically selects one of the two (Dem
forcing= None). Default value is None. Clicking twice on the insertion field with the
left button of the mouse, the Field Editing window opens for selection of the
desired value.
Fig. 6.55 Configuration of Dem Forcing
6 - OPERATING GUIDE
6-42
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Switches Status section
The window is divided in two parts:
Trib --> Radio (it displays the status of the switches of the TX chain)
Radio --> Trib (it displays the status of the switches of the RX chain)
It displays, for the protected systems, which tributary (only for DTI) and which ODU (only
for Hot-Stby systems) are currently used for the transmission, and which radio channel
is currently used for the reception.
6.7.1.3.2 Protection in (N+1) System Types (starting from SVR 4.4)
Pressing the Protection button in the Equipment Status & Configuration window
(Fig. 6.4), in case of (N+1) System Type, the following Protection opens, where the
user can configure the protection modality for the for the local equipment and display the
display the status of the remote radio unit.
Fig. 6.56 Protection Status & Configuration window ((3+1) System Types)
System Type (read-only)
It displays the System Type of the equipment (par. 6.7.1.1).
Switching Criteria Enabling
By means of this field, the user can define which is the switching enabling criterion.
Possible values are:
None,
normal condition (all the criteria enabled);
The window layout and the displayed parameters depend on the System Type
6 - OPERATING GUIDE
6-43
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Minor alm disabled,
Minor criterion disabled (the switching will occur only for alarms of Major and
Critical type);
Major alm disabled,
Minor and Major criteria disabled (the switching will occur only for alarms of Critical
type).
Fig. 6.57 Configuration of Switching Criteria Enabling
Remote Tx Prioritary Ch
This field allows selecting the channel to protect in transmission in the remote end.
Channel 1 on Remote Tx: enabling of parallel channel in transmission of the
channel 1 in the remote end
Last Protected Channel on Remote Tx: enabling of parallel channel in
transmission of the last protected channel.
Clicking twice with the left button of the mouse on the selection filed, the following Field
Editing window opens for the selection of the parameter value.
Fig. 6.58 Configuration of Remote Tx Prioritary Ch
Local Radio Unit parameters
Switch Priority Ch
It allows assigning to each working channel a priority value (at the same
conditions). Possible values are:
Low (low priority)
Medium (medium priority)
High (high priority)
Clicking twice with the left button of the mouse on the selection filed, the following Field
6 - OPERATING GUIDE
6-44
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.59 Configuration of Switch Priority Ch
This setting allows simulating on a given channel (working or stand-by) the
presence of an alarm of the indicated severity or the absence of alarms, in such a
way to change the decision of the protection switching logic. For each working
channel, the following selections are possible:
normal: no forcing active;
Minor Alarm: forcing of a Minor alarm on the channel;
Major Alarm: forcing of a Major alarm on the channel;
Critical Alarm: forcing of a Critical alarm on the channel;
Channel in Service: forcing of the channel to service;
Protected: forcing of the channel to protection
Clicking twice with the left button of the mouse on the selection filed, the following
Field Editing window opens for the selection of the parameter value.
Fig. 6.60 Configuration of Switch Criteria Forcing
Switch Alarm
It displays the status of the channel switching criteria:
normal: normal condition;
Minor: switching criterion of Minor type active (Fast BER Low alarm active);
Major: switching criterion of Major type active (Fast BER High alarm active);
Critical: switching criterion of Critical type active (HBER and/or Dem Alm
alarm active).
Switch refused by remote Eqp
It is the alarm of refused switching. This alarm is activated by the switching logic
when the switching procedure is not ended.
Input Ch
It displays the presence or absence of the following signals in input to the base
bands of the service channels: LOS STM1, OOF STM1, LOF STM1, MSAIS STM1,
TIM STM1.
Local Ch on St-by Tx
It is the indication of the channel that transits on the stand-by in the local
transmission section.
6 - OPERATING GUIDE
6-45
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Local Ch on St-by Rx
It is the indication of the channel that transits on the stand-by in the local reception
section.
Remote Radio Unit parameters (read-only)
It displays a possible forcing executed in the remote end (see Switch Criteria
Forcing)
normal: no forcing active;
Minor Alarm: forcing of a Minor alarm on the channel;
Major Alarm: forcing of a Major alarm on the channel;
Critical Alarm: forcing of a Critical alarm on the channel;
Channel in Service: forcing of the channel to service;
Protected: forcing of the channel to protection;
Standby in Service: forcing in service of the standby channel
Switch Alarm
It displays the status of the switching criteria of the remote channel:
normal: normal condition;
Minor: switching criterion of Minor type active (Fast BER Low alarm active);
Major: switching criterion of Major type active (Fast BER High alarm active);
Critical: switching criterion of Critical type active (HBER and/or Dem Alm
alarm active).
Remote Ch on St-by Tx
It is the indication of the channel that transits on the stand-by in the transmission
section of the remote end.
Remote Ch on St-by Rx
It is the indication of the channel that transits on the stand-by in the reception
section of the remote end.
Alarm signalings
Remote SCS1 Alarm Off/On and Remote SCS2 Alarm Off/On
They are status indications of the SCS 1 and SCS 2 channels (channels mapped
on the S23 bytes of the base bands of channels 1 and 2 of the remote end).
6.7.1.4 Co-Channel operation
The SRA 4 radio equipment, starting from SVR 4.4, allows setting the co-channel
operation for the system, only for System Types (2+0) or 2x(1+1). This functionality is
supported only by Co-channel Wideband ODU. It is possible to configure each
BB-Modem unit to operate with a given polarization at RF frequency: one of the two
ODUs will be configured as master sync (synchronization source), while the other ODU
will be configured as slave sync (the synchronization source is taken by the other
ODU).
In case of co-channel configuration, the transmission frequencies of the two
ODUs must be the same (F_TX_ODU1=F_TX_ODU2; F_RX_ODU1=F_RX_ODU2).
6 - OPERATING GUIDE
6-46
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
The operator must configure one of the two BB-Modem units with a given polarization:
the other unit will automatically configured with the orthogonal polarization.
A configuration change from alternate polarization to co-channel polarization (in the
System Types which support this functionality) is refused if:
at least one of the two ODUs is a Narrowband ODU;
at least one of the two ODUs does not support the co-channel operation.
It is possible to select the IF/RF synchronization between the ODUs among:
ODU 1 (connected to the upper BB-modem card) master, ODU 2 slave;
ODU 2 (connected to the lower BB-modem card) master, ODU 1 slave;
Pressing the Co-Channel button in the Equipment Status & Configuration window,
the following Co-Channel window opens, for the configuration of the operating
parameters.
Fig. 6.61 Co-Channel window
Synchronization section
The present displayings are:
CC Pair
indicates the considered IDU-ODU pair
Synch Status
indicates the synchronization status of the CC pair. The displayed values are
Master Free Running for the master and Slave Locked for the unit slave.
Starting from SVR 4.5, the operator can configure if the switch for the synchronization
must operate in automatic or manual modality. To do this, double click on the Synch for
CC Pair #n field: the following Field Editing opens, where it is possible to choose
between the two settings (Auto and Manual).
The equipments with (1+1) FD System Type and enabled co-channel functionality
do not protect against the selective fading.
6 - OPERATING GUIDE
6-47
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.62 Configuration of synchronization modality
If the operator selects Auto, the operation is automatic.
If the operator selects Manual, the operation is defined by the operator: in this case, the
window displays the Synch Forcing push-button. Clicking on the Synch Forcing
push-button, the Synchronization window opens, allowing configuring how to force the
synchronization window.
Fig. 6.63 Synch Forcing window
Double click with the left button of the mouse on the Synch Forcing IDU #n
BB-Modem/ODU#n field: the following Field Editing window opens for the
configuration of the parameter.
Fig. 6.64 Configuration of Synch Forcing (CC)
Polarization section
For each one of the two CC pairs, this section displays the status of the current
polarization: V (vertical) or H (horizontal). The operator can set a new value of
polarization to the BB-Modem/ODU1 pair: the other CC pair will automatically assume
the orthogonal polarization value.
To do this, click twice on the Polarization field: the following Field Editing window
The phrase written in the window remember to the operator that, as consequence
of this operation, both the payloads and the control channels will be temporarily
lost.
The setting of the Master or Slave value for this parameter does not activate the
displaying of Manual Operation on the Equipment (allowed equipment
configuration).
6 - OPERATING GUIDE
6-48
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
opens for the configuration of the parameter.
Fig. 6.65 Configuration of Polarization
6.7.1.5 Testing window
Pressing the Testing push-buttons in the Equipment Status & Configuration
(Fig. 6.4) window, the Testing window opens. The window contains the push-buttons:
Loop Backs,
opens the Testing Mode & Loop-Backs window (par. 6.7.1.5.1);
Long PM Recording,
opens the Long PM Recording window (par. 6.7.1.5.2);
Timed Switching,
this functionality is available only in protected System Type and allows forcing the
position of the switches for a given time period (selected by the user)
(par. 6.7.1.5.3).
Fig. 6.66 Testing window
The Long PM Recording and Timed Switching functionalities are present starting
from SVR 4.5.
6 - OPERATING GUIDE
6-49
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.1.5.1 Testing Mode & Loop-Backs window
Pressing the Loop Backs button in the Testing window (Fig. 6.66), the Testing Mode
and Loop-Backs window opens, where the operator can configure the loopback on the
equipment at different levels, to verify the correct operation of the equipment itself. For
each BB-Modem card, the window displays the current connection status with the
Controller.
Fig. 6.67 Testing Mode & Loop-Backs window
Configuration of Loop-back Trib Side
The tributary local loop-back is executed at the physical input/output interface level. The
user can enable or disable the local loop-back function. The possible values for this
parameter are: Enabled (loop-back enabled) and Disabled (loop-back disabled, default
value).
If Modulator Mode is not Normal, the remote NE becomes unreachable.
Only one loop-back at a time can be executed for each BB-Modem unit.
The window layout and the parameters present in the window depend on the
System Type configured on the equipment.
6 - OPERATING GUIDE
6-50
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.68 Configuration of Loop-Back Trib Side
Configuration of Loop-Back Trib Side INT
The internal tributary loopback is executed at BB unit level (the signal closed in loop
before the modem section). Clicking twice with the left button of the mouse on the
selection field, the Field Editing window opens to enable (Enabled) or disable
(Disabled) the loopback.
Fig. 6.69 Configuration of Loop-Back Trib Side INT
Configuration of Loop-Back Radio Side
The local loop-back on radio side is executed up to the level of RSOH tributary interface.
Possible values are Enabled and Disabled (default value).
Clicking twice with the left button of the mouse on the selection field, the Field Editing
Fig. 6.70 Configuration of Loop-Back Radio Side EXT
Modulator Mode
Clicking on this button, the user can select the operating modality of the modulator. The
related Field Editing window opens, where three options are available:
Normal (default);
Carrier Only;
Mute.
6 - OPERATING GUIDE
6-51
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.71 Configuration of Modulator Mode BB-Modem
6.7.1.5.2 Recording of the Long Period Performance
Starting from SVR 4.5, there is a command that allows enabling/disabling the recording
of the long period performances (by default, this recording is disabled).
Click on the Long PM Recording push-button of the Testing window (Fig. 6.66) to
access to the window that manages this function.
Fig. 6.72 Testing - Long PM Recording window
To define the time window for the recording, it is necessary to configure:
Recording Type,
defines the the relevant position of the time window: From Start Time o Continuous
Mode:
Start Time,
defines the start instant of the recording of the performance data (meaningful
only if the previous parameter is set to From Start Time). This parameter is
expressed as Day/Month/Year/Hour:Minute, with steps of 15 minutes. If the
network management system re-synchronize the radio unit, the Start Time
value does not change. The system records 192 consecutive complete
intervals of 15 minutes in the volatile memory starting from Start Time.
In NetViewer, the recording of the long period performance application, is
supported since the V8.0 release.
It is possible to change the Start Time value only if the long period performance
recoding function is disabled. Values of day and time before the current date and
time of NE are not accepted.
6 - OPERATING GUIDE
6-52
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Continuous Mode
the storing is continuous and cyclic: after the first 192 complete periods of 15
minutes have been recorded, the 193-th will replace the first in the volatile
memory: then, the last 192 quarters will be recorded.
The following figure gives an example of the operation of the two different modalities.
Fig. 6.73 Long period PM recording
Clicking twice on the Recording Type field, the following Field Editing window opens
for the configuration of the recording modality.
Fig. 6.74 Configuration of Recording Type
To configure the date and time corresponding to the start of the performance recoding,
the operator must click on the Modify push-button: the following window opens.
Fig. 6.75 Configuration of recording start
The Modify push-button is not available if the recording modality is configured as
Continuous Mode.
6 - OPERATING GUIDE
6-53
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
The NE Controller resets the content of the long period performance records:
at start-up;
after a manual reset command;
in correspondence of Start Time (start of the data recording)
The window displays a counter that shows how many 15 minutes intervals have been
already recorded (Expired Quarters field).
If the Long PM Recording Start setting is From Start Time, the NE writes a file as soon
as it ends to record the last 15 minutes interval.
If Long PM Recording Start is set to Continuous Mode, the file of the recordings is
created on-fly when the FTP request is made.
The operator, after the configuration of all the recording parameters, can enable it
clicking twice on the Long Period PM Recording field: the following Field Editing
window opens.
Fig. 6.76 Enabling/disabling of the recording
The Get PM Recorded File push-button opens the PMCommReport window for the
recording of the long period performance file.
Before setting this date, it is suggested to have previously set the correct date
and time on the equipment.
If the FTP request is made before that the last of the 192 periods of 15 minutes has
been recorded, the resulting file will contain also some meaningless values,
which will be not displayed.
For the description of the long period performance period recording procedure
and of the content of the PMCommReport window, refer to the operating guide of
LCT/NetViewer.
6 - OPERATING GUIDE
6-54
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.1.5.3 Timed Switching
The use of the Timed Switching functionality allows forcing the position of the
equipment switches for a given period of time, which can be selected by the operator.
The following forced manual switching options are available:
Demodulator forcing: in (1+1) protected System Types, it allows forwarding the
received IF signals to the BB unit to be processed.
Hot Stand-By forcing: in HSBY System Types, it allows selecting the active
transmitter.
Tributary forcing: in DTI System Types, it allows forwarding the STM-1 tributary
signals to both the modulators.
RPS forcing: in (N+1) System Types, it allows executing a simple switching
sequence (which service channel will occupy the protection channel).
The number and the type of the switch depends on the equipment System Type
(Tab. 6.3).
The operator can select the type of behaviour of the switches for the whole radio unit
acting on the Timed Switching field. Clicking twice on this field, the following Field
This function is available only in protected System Types, starting from SVR 4.5.
Tab. 6.3 Independent switches depending on System Type
System Type Demodulator Hot Stand-by Tributary RPS
(1+0) - - - -
(2+0) - - - -
(1+1) HSBY STI 1 1 - -
(1+1) HSBY DTI 1 1 1 -
(1+1 FD STI 1 - - -
(1+1) FD DTI 1 - 1 -
(2+1) - - - 1
(3+1) - - - 1
2X(1+1) FD STI 2 - - -
2X(1+1) FD DTI 2 - 2 -
2X(1+1) HSBY STI 2 2 - -
2X(1+1) HSBY DTI 2 2 1 -
In the previous table, 2 means 1 for each (1+1) block.
6 - OPERATING GUIDE
6-55
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.77 Configuration of Timed Switching
The possible values are:
Disabled (default value): no forcing. In this case, the Timed Switching
push-button in the Testing window is inactive.
Single Sequence: independent switching sequences are foreseen for each
switch;
Periodic: it allows the stand-by transmitter being forced active.
If the operator selects Single Sequence or Periodic, the Timed Switching push-button
opens the corresponding Timed Switching window.
Single Timed Switching
When single sequence switch is operating, the forcing of the commissioning switch
has the priority on the manual forcing of the switch. If a manual forcing of a switch is set
during a single sequence switch, this will be applied only to the end of the single
sequence switch procedure. The NE Controller, before frocing the configured switches,
saves their current configuration and position. SRA4 restores the configuration of the
hitless switches saved at the end of the forcing sequence.
The Periodic option is present only for Hot Stand-by System Types.
Single Sequence Switch is coupled to the collection of the long period
performances. The switching must be avoid at the end of a quarter period, in order
not to influence the PM data associated to a quarter only. For this purpose, the
Start Switch Date & Time parameter is increased, automatically, of 10 seconds.
6 - OPERATING GUIDE
6-56
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.78 Single Timed Switching window
When the operator selects the single sequence modality, it is necessary to set the
following configuration for each supported switch (Demodulator, HSBY and Tributary):
Enabled:
check-box that allows enabling (checked) or disabling (unchecked) the switch
function.
Current Switch Status:
points out the current switch status.
Start Switch Date & Time:
points out the date and time of the start of the switching. The format is
Day/Month/Year-Hour:Minutes and the default value is 01/01/1990-00:00. The
Modify push-button opens a window that allows modifying the value of this field.
First Forcing Period:
points out the first forcing period. The format is Hour:Minute, the default value is
00:00 and the allowed intervals are: 0-48 (hour) and 0-59 (minute). The Modify
push-button opens a window that allows modifying the value of this field.
Second Forcing Period:
points out the second forcing period. The format is Hour:Minute, the default value
is 00:00 and the allowed intervals are: 0-48 (hour) and 0-59 (minute). The Modify
push-button opens a window that allows modifying the value of this field.
Third Forcing Period:
only for (3+1) System Type. It points out the third forcing period. The format is
If also the IDU2 unit is equipped in the system, the Single Timed Switching
IDU#1 window displays, in the lower right corner, the IDU#2 push-button,
which allows opening the same window referred to the second IDU unit.
Once enabled the switch, all the corresponding parameterscannot be modified
anymore (greyed fileds).
6 - OPERATING GUIDE
6-57
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Hour:Minute, the default value is 00:00 and the allowed intervals are: 0-48 (hour)
and 0-59 (minute). The Modify push-button opens a window that allows modifying
the value of this field.
Switch Starting Position:
points out the forced position of the switch in the first period. During the second
period, the switch is forced in the opposite position. The operator can select the
starting position of the switch clicking twice on the relevant field: the Field Editing
window opens for the selection of the wished value.
Fig. 6.79 Configuration of Switch Starting Position (example: ODU)
Test Status:
points out the test status (scheduled for a future date, running, ended or disabled).
The switch behaviour is displayed in the following figure.
Fig. 6.80 Example of Single Timed Switch
A way not to force a switch during the commissioning, besides to disable it,
consists in setting its forcing periods to 00:00. It is also possible to force the
switch in only one position setting one of the two forcing period to 00:00.
6 - OPERATING GUIDE
6-58
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Periodic Timed Switching
The Periodic operation modality is available only in Hot Stand-By System Types, for a
maximum of 3 minutes and 59 seconds. This configuration allows the stand-by
transmitter being periodically switched on for a brief period of time, to check the whole
transmission chain.
Fig. 6.81 Periodic Timed Switching window
The following parameters must be set for each Hot Stand-By switch:
Enabled,
it is a check box used to enable/disable the forced management of the switch (by
default, iti s disabled).
First Switch Date & Time,
it points out the date and time of the first switch. The format is
Day/Month/Year-Hour:Minutes and the default value is 01/01/1990-00:00. The
Modify push-button opens a window that allows modifying the value of this field.
Repetition Period,
it points out the period after which the switch is repeated. It is expressed in days
and the allowed interval is 0-400. The Modify push-button opens a window that
allows modifying the value of this field.
This procedure causes the payload loss, then it must not be often repeated.
The section of the window referred to the IDU#2 is displayed only in the 2x(1+1)
Hot Stand-by System Types.
Before setting this date, it is suggested to have previously set the correct date
and time on the equipment.
6 - OPERATING GUIDE
6-59
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Forcing period on protection chain,
it points out the period during which the stand-by transmitter is activated instead of
the working one. Its format is min/sec and the allowed intervals are respectively 0-3
and 0-59. The Modify push-button opens a window that allows modifying the value
of this field.
Next Scheduled Test,
it points out the date and time of the next forcing period.
The NE Controller compares the current date and time of the equipment with the Next
Scheduled Test value. When the two values coincide, the NE Controller forces the
switches on the protection chain for a period corresponding to the Forcing period value,
if no active alarms are present on the protection chain.
The behaviour of the switch is displayed in the following figure.
Fig. 6.82 Example of Periodic switch
The working ODU is that active just before the periodical forced switching sequence.
When a fault is already present on the protection chain, the periodic switch must not be
executed and the Last Test Failed is issued. This alarm is cleared as soon as a switch
is successfully made during a scheduled switching procedure or disabling and
re-enabling the procedure itself.
If an alarm is detected on the protection chain during a switching, a Stand-by ODU
failed during periodic test alarm is issued. This alarm is cleared as soon as a switch is
successfully made during a scheduled switching procedure or disabling and re-enabling
the procedure itself.
When a periodic switch is operating, it has the priority on the manual forcing of the
switch. If a manual forced switch is set while a periodic switch is operating, the setting
will be applied only after that the periodic switching procedure is ended. If a sequence
must be activated while a manual switch is active, this one is temporary stopped.
6 - OPERATING GUIDE
6-60
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.1.6 Maintenance
Pressing the Maintenance push-button in the Equipment Status & Configuration
window (Fig. 6.4), the Maintenance window opens, where the operator can execute the
procedure for the replacing of the alarm unit without traffic loss.
Fig. 6.83 Maintenance window
The window points out if the procedure is supported or not. If yes, the procedure to
execute for the replacing of the alarm unit is the following:
1. Press the Start push-button and verify that Switch Status changes from Open to
Closed.
2. Extract the hardware key from the alarm unit
3. Extract the front panel from the unit
4. Insert the new alarm unit
5. Install the front panel
6. Insert the hardware key.
The Maintenance functionality is present starting from SVR 4.5.
All the steps must be completed within 3 minutes. Otherwise, the IDU unit, after 3
minutes, switches off.
In order that this functionality is supported, it is necessary that at least a
BB-modem unit is of the HW version that supports this procedure and that this
BB-modem unit is supplied (Vpow connector connected to power supply). Other
wise, the Start push-button will remain inactive and the extraction of the alarm
unit will cause the switching off of the whole IDU and of the ODUs.
6 - OPERATING GUIDE
6-61
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.1.7 Feature Control window
Pressing the License Upgrading button in the Equipment Status & Configuration
window (Fig. 6.4), the Feature Control window opens, where the operator can check
and possible modify the status of the licenses present on the equipment.
The window opens in read only modality. Pressing the Modify button, the operator can
pass to the write modality and modify the value of the four fields composing the License
Key field. Modify button change its name to Upgrade.
Fig. 6.84 Feature Control window (write modality)
Clicking twice with the left button of the mouse on the selection field, the Field Editing
window opens for the choice of the value necessary to the activation of the license.
Fig. 6.85 Configuration of License Key #1
The correct value of the License Key is generated using the proper kit for license
upgrading.
6 - OPERATING GUIDE
6-62
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.1.8 Copy Config command
The use of the configuration files of the network element, stored on PC or in a central
archive, has two functions:
make some backup copies of the equipment configuration available to allow a fast
restore of the equipment itself in case of loss of configuration;
make some different basic configurations available, in such a way to make easy
and to reduce the operations related to the configuration of the connected
equipment.
Pressing the Copy Config button of the Equipment Status & Configuration window
(Fig. 6.4), an external application to copy the equipment configuration data starts.
The configurations copied by the Copy Config functions are the following one:
System
Start SRA4 Equipment Configuration Profile
Propagation enabling of Static Routing Table on interface
Selection of Comp IF Cable Mode
Enabling of Automatic Laser Shut Down
Selection of Switch Trib Forcing
Selection of IDU #1 Switch Trib Forcing
Selection of IDU #2 Switch Trib Forcing
Selection of Switch Dem Forcing
Selection of IDU #1 Switch Dem Forcing
Selection of IDU #2 Switch Dem Forcing
Selection of Switch ODU Forcing
Selection of IDU #1 Switch ODU Forcing
Selection of IDU #2 Switch ODU Forcing
Enabling of Border Gateway functionality on interface
Selection of Radio Channel Destination
Enabling of RIP on interface
Configuration of RIP on Q interface
Enabling of ingress summarization on interface
Setting of System Configuration
Selection of Dem Protection Mode
Selection of IDU #1 Dem Protection Mode
Selection of IDU #2 Dem Protection Mode
Selection for CC pair #1
Selection of Polarization for IDU #1
Enabling of Masking of STM1 #2
Enabling of IDU #1 Masking of STM1 #2
Enabling of IDU #2 Masking of STM1 #2
ODU Narrowband
ATPC parameters and Tx Power
ODU Wideband
Frequency Mode
ATPC parameters and Tx Power
6 - OPERATING GUIDE
6-63
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
BB-Modem
Configuration of Number of Wrong J0
Enabling of AIS insertion for TIM
Enabling of 64 Kb/s V11 Channel Mode
Enabling of 64 Kb/s G703 Channel Mode
Enabling of Way-Side Channel Mode
Selection of B1 Threshold for SD Alarm
Enabling of J0 Management
Selection of Cable Length
Selection of IF Output Level
Enabling of STM-1 #1 Optical Interface Laser Forcing
Enabling of Masking of STM1 #2
Enabling of STM-1 #2 Optical Interface Laser Forcing
6.7.1.9 Paste Config command
Pressing the Paste Config button of the Equipment Status & Configuration window
(Fig. 6.4), an external application to paste the equipment configuration data starts.
6.7.1.10 BB-Modem Config window
Pressing the Configure button in the BB-Modem section of the Equipment Status &
Configuration window (Fig. 6.4), the BB-Modem Config window opens, for the
configuration of the parameters related to Modem section.
Fig. 6.86 BB-Modem Config window
For a complete description of the commands and the procedures to operate on
the equipment by the configuration files, refer to the operating guide of
NetViewer/LCT.
For a complete description of the commands and the procedures to operate on
the equipment by the configuration files, refer to the operating guide of
NetViewer/LCT.
6 - OPERATING GUIDE
6-64
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Cable Length
The operator can choose the length of the IF cable between one of the two values: Short
and Long. Clicking twice on the insertion field with the left button of the mouse, the Field
Editing window opens for selection of the desired value.
Fig. 6.87 Configuration of Cable Length
IF Output Level
In case of Narrowband ODU, the operator can choose the output level on the IF cable
between one of the two values: +5dBm and -10dBm.
In case of Wideband ODU, this parameter cannot be set and it is fixed to the value of
+5dBm.
Fig. 6.88 Configuration of IF Output Level
Tx Mod Inverted Spectrum (only if BB-Modem is connected to ODU Narrowband)
This parameter inverts the transmission spectrum of the modem and it must be properly
set for the Narrowband ODUs, in accordance to what reported in the hardware manual.
In case of wrong configuration of the parameter, the traffic is interrupted.
The operator can choose one of the two values: Inverted and Not Inverted.
For the proper setting of the Cable Length and IF Output Level fields, refer to UMN
manual.
6 - OPERATING GUIDE
6-65
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.89 Configuration of TX Mod Spectrum Inversion
XPIC Status
It indicates the status of XPIC canceller: ON or OFF
XPIC (starting from SVR 4.4)
This parameter is meaningful only for co-channel systems. It allows canceling the
residual of the orthogonal. The operator can choose between one of the two values: ON
(canceller running, manual oepration) and Forced OFF (canceller disabled).
Clicking twice with the left button of the mouse on the selection field, the following Field
Fig. 6.90 Configuration of XPIC
6.7.1.11 ATPC function
SRA 4 equipment supports the ATPC function both in HSBY systems and in FD
systems.
All the processings are executed by the FPGA present on the BB-Modem. The ATPC
information is exchanged between the far ends via byte S(2,2).
In all the System Types, the radio links are completely separated and independent: the
RX level of link #1 cannot influence the TX level of link #2 and viceversa.
The ATPC function has a different implementation in systems with Narrowband ODU
(par. 6.7.1.11.1) and with Wideband ODU (par. 6.7.1.11.2).
6 - OPERATING GUIDE
6-66
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.1.11.1 ATPC for ODU Narrowband
The parameters for the management of the ATPC function are reported in Tab. 6.4 and
can be configured in the ODU Configuration window (Fig. 6.91).
Fig. 6.91 ODU Config window
HW management
ATPC algorithm is based on the following hysteresis (based on RX field).
Fig. 6.92 Hysteresis cycle
Tab. 6.4 ATPC management (ODU Narrowband)
Parameters configurable by the user
ATPC
management
ATPC mode TX Power Transmitted power
Enabled
Pmin (Pnom-8dB)
No matter
Pmin (Pnom-8dB)
Pmax (Pnom) Pmax (Pnom)
Auto
According to the algorithm of
ATPC for ODU Narrowband
Disabled No matter
Pmin (Pnom-8dB) Pmin (Pnom-8dB)
Pmax (Pnom) Pmax (Pnom)
6 - OPERATING GUIDE
6-67
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
The value of the RX field is transmitted by ODU to the IDU. When the value of the RX
field decreases under a predefined threshold (ATPC_Threshold 1), IDU inserts in the
radio frame the request of Pmax and when the value of the RX field exceeds a
predefined threshold (ATPC_Threshold 2), IDU inserts in the radio frame the request of
Pmin. The remote station extracts from the received frame this information and, after a
proper processing of the IDU, extracts the ATPC command to be transmitted to the TX
section of ODU. To transmit the ATPC information to the remote terminal, the byte S22
is used.
6.7.1.11.2 ATPC for ODU Wideband
ATPC (Automatic Transmit Control Power) executes an automatic control of the
transmitted local power level to assure a minimum level of power received by the remote
terminal, even if a fading event disturbs the radio channel. This automatic control is
applied in linear mode in a predefined dynamic power range (see following figure).
The interval within which Prx can be maintained constant is defined by two parameters:
P
RX_TH
,
Prx level at which ATPC activates: it is the minimum level of Prx to assure in ATPC
modality
ATPC range,
dynamic power range within which Ptx can be changed from Pmin to Pmax
If Prx decreases (1) and reaches the P
RX_TH
threshold, Ptx starts to increase (2) to
maintain constant the Prx level.
Ptx can increase up to a maximum level: so, if the channel fading becomes greater, it
cannot be compensated and Prx starts to decrease (3).
Once the fading decreases, the system behaves following the same strategy, but in the
opposite direction.
6 - OPERATING GUIDE
6-68
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.93 Linear ATPC
6.7.1.11.3 Setting of the transmission power
ATPC functionality is managed by SW using the following parameters:
Pmin: it is the minimum power level you wish to transmit
ATPC Range: it is the maximum increase of power you wish to obtain. The
maximum power that can be transmitted is then equal to Pmin+ATPC_Range
ATPC Management: it enables or disables the ATPC functionality
ATPC Mode: inside the ATPC algorithm, it allows determining the Ptx value in
automatic mode or setting the value at two ends (maximum and minimum power).
This parameter is meaningful in case of Enabled ATPC Management
TX_power: if the ATPC algorithm is disabled (ATPC Management = Disabled), this
parameter allows setting Ptx to the minimum and maximum power
ATPC Threshold: threshold for the intervention of ATPC algorithm
When ATPC MANAGEMENT is set to enabled, the local transmitter is set according to
the extracted byte S22. IDU sends an ATPC command with the information of the
necessary increase/decrease.
When ATPC MANAGEMENT is set to disabled, IDU sends an ATPC command with the
information of the necessary increase. The S22 byte is ignored.
6 - OPERATING GUIDE
6-69
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.94 ODU Config window (Freq Mode = Continuous)
6.7.1.12 Configuration of ODU unit
The operator can configure the operating parameters of the ODU units present in the
system. The parameters to set change if ODU of Wideband type (par. 6.7.1.12.1) or
ODU of Narrowband type (par. 6.7.1.12.2) are present in the system.
6.7.1.12.1 Configuration of Wideband ODU unit
Pressing the Configure button of the ODU section in the Equipment Status &
Configuration window (Fig. 6.4), the ODU Config window opens, where the user can
configure the ODU operating parameters.
As regards the range of the operating frequencies of the Narrowband and
Wideband ODUs, refer to the UMN manual of SRA4.
In case of (1+1) HSBY System Type and Wideband ODU, the configuration related
to the RF frequency for the two ODUs must be manually set to the same value.
6 - OPERATING GUIDE
6-70
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.95 ODU Config window (Freq Mode = Continuous)
Fig. 6.96 ODU Config window (Freq Plan Activation = On)
License Free Status indication
This field displays the type of license present in the system.
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 opens. The
two possible choices are: Freq Plan or Continuous.
6 - OPERATING GUIDE
6-71
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.97 Configuration of Freq Mode
The Frequency Plan modality allows determining the transmission frequency and
specifying the number of the channel where transmit instead of determining directly the
value of the frequency transmission.
To use this modality, it is necessary to define the frequency plan intended to be used
(see figure below).
In particular, it is necessary to specify the identifier (numeric) of the first and last channel
intended to be used (3 and 7 in figure), the frequency transmission of the first channel
and the spacing among the different channels.
Fig. 6.98 Frequency plan
To execute these settings, it is necessary to proceed as follows:
1. enable the Freq Plan Activation On;
2. set the parameters of the frequency plan: Freq Ch. #1, First Channel ID and Last
Channel ID;
3. disable the Freq Plan Activation Off;
Once described the frequency plan, in order to transmit on a given channel, it is
sufficient to write the identifier of the chosen channel into the RF Channel ID field.
ODU automatically checks that the set value is between First Channel ID and Last
It is recommended not to use the Freq Plan modality in case of channellings with
frequencies multiple of 250 KHz.
6 - OPERATING GUIDE
6-72
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Channel ID and, if the parameter is correct, it updates the transmission and reception
frequencies to match the frequency plan.
In Frequency Plan modality, the setting of parameters 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.
Tx Frequency min
It is the minimum transmission frequency that can be set on the ODU with the set
value of Channel Spacing.
Tx Frequency max
It is the maximum frequency transmission supported by the ODU with the set value
of Channel Spacing.
RF Band
It is the frequency range of the ODU (e.g.: 18GHz, 11GHz, 38GHz).
Shift
It is the difference between the value of the transmission and reception frequencies
of the ODU.
Freq Plan Activation
It allows to enable (On) or disable (Off) the modification of the parameters of the
frequency plan. Clicking twice with the left button of the mouse on the selection
field, the Field Editing window opens.
Fig. 6.99 Enabling/disabling of Freq Plan Activation
Channel Spacing (kHz)
This parameter defines the separation, within the frequency plan, between the
central frequencies of two adjacent RF channels having the same polarization and
on the same transmission direction. Clicking twice with the left button of the mouse
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.
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 Continuous Mode;
RF Channel ID, in Freq Plan.
6 - OPERATING GUIDE
6-73
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
on the selection field, the Field Editing window opens for the insertion of the
parameter value.
Fig. 6.100 Configuration of Channel Spacing
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 opens
for the insertion of the parameter value.
Fig. 6.101 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 opens for the insertion of the parameter value.
Fig. 6.102 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,
In modality Freq Mode = Freq Plan, the Channel Spacing parameter is displayed
in TX Freq Plan Mode box.
6 - OPERATING GUIDE
6-74
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.103 Configuration of Last Channel ID
RF Channel ID
It allows to set the number of the radio frequency channel currently in use. This
setting is possible only in Frequency Plan modality. Clicking twice with the left
button of the mouse on the selection field, the Field Editing window opens for the
insertion of the parameter value.
Fig. 6.104 Configuration of RF Channel ID
In Continuous modality:
the RF Channel ID parameter is set to zero by IDU and the frequency plan is not
considered by ODU. The TX or RX frequencies are directly modified, and they become
effective after that ODU has verified that these are within the range of hardware
frequencies.
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,
Fig. 6.105 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
Field Editing window opens for the insertion of the parameter value.
Fig. 6.106 Configuration of RX Freq
6 - OPERATING GUIDE
6-75
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
TX Power parameters
Pmin [dBm]
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 opens
for the insertion of the parameter value. This depends on the current radio link and
is calculated and inserted in the IDU unit during the installation.
Fig. 6.107 Configuration of Pmin
ATPC Range [dBm]
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 opens for the
insertion of the parameter value. The range of allowed values is between 0 and 15
dB.
Fig. 6.108 Configuration of ATPC Range
ATPC Threshold [dBm]
It allows selecting the threshold for ATPC parameter. Clicking twice with the left
button of the mouse on the selection field, the Field Editing window opens for the
insertion of the parameter value.
Fig. 6.109 Configuration of ATPC Threshold
ATPC Management
It allows to enable or disable the ATPC parameter automatic management.
Clicking twice with the left button of the mouse on the insertion field, the Field
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 + ATPC_Range less or equal to TX Power max
Pmin TX Power min
6 - OPERATING GUIDE
6-76
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.110 Configuration of ATPC Management
Current TX Power
It displays the current value of the ODU transmission power (in dBm).
Commands
Squelch SW Activation
It allows stopping the transmission of the TX RF signal. It is used during the
installation for the safety of the installators. Possible values are:
Off, the system transmits (normal operation)
On, the transmission is interrupted.
Clicking twice with the left button of the mouse on the selection field, the Field
Fig. 6.111 Configuration of Squelch SW Activation
Comp IF Cable Mode
It allows selecting one of the two possible management strategies: Auto (default)
or Manual. Clicking twice with the left button of the mouse on the selection field,
the Field Editing window opens for the insertion of the parameter.
After an ODU replacement, the procedure for cable compensation must be
activated to calculate the correct value of the attenuation (default value stored in
ODU is 31 dB), depending on the length of IF cable and on the IF TX power level.
In Auto mode, the cable compensation is automatically activated when one of
these two conditions occurs:
ODU is switched on
the IF TX power level is changed
In Manual mode, the cable compensation is activated acting on the related
activation command.
After the installation procedures and during the normal operation of the system,
set the value of IF Compensation Cable Mode to Manual.
6 - OPERATING GUIDE
6-77
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.112 Configuration of Comp IF Cable Mode
Start Compensation IF Cable
It allows to manually force the procedure for the cable compensation. It is visible
and can be activated only by LCT. Clicking twice with the left button of the mouse
on the selection field, the Field Editing window opens for the selection of the
value.
Fig. 6.113 Configuration of the cable compensation
During the cable compensation procedure, the red indication Comp Cable Running
appears. If the compensation procedure ends successfully, the red indication End
Comp Cable appears for some seconds. If the compensation procedure ends
unsuccessfully, the Cable Comp Out of Range indication appears.
The ODU Config window displays also the wording ODU Power-up procedure:
Completed (at the end of the ODU initialisation) or ODU Power-up Procedure:
Running (during the initialisation of ODU).
Tx AGC (only Co-Channel Wideband ODU, starting from SVR 4.4)
The operator can choose between one of the two values: ON (transmitter in
Automatic Gain Control, normal operation) and OFF (transmitter in Manual Gain
Control). In MGC, additional 15dB (from pmin to Pmin -15 dB), which can be
selected by means of the configuration of the TX Power parameter in the IF
Parameters section.
Pressing the TX AGC button, the TX AGC window opens warning the operator
about the loss of transmission payload deriving from the modification of the
parameter.
La condizione di Tx AGC Off deve essere usata solo durante la fase di
installazione. Durante il normale funzionamento, il parametro Tx AGC deve essere
impostato a On.
The Tx AGC push-button is displayed in the window when the ATPC Management
parameter is set to Disabled.
6 - OPERATING GUIDE
6-78
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.114 Warning for temporary loss of the payload in transmission (Tx AGC)
Clicking twice with the left button of the mouse on the insertion field, the following
Field Editing window opens.
Fig. 6.115 Configuration of Tx AGC
TX_AGC On
When the transmitter is set to TX_AGC Off modality, the Tx Power box switches to
read-only modality and the Tx Power configuration appears in the IF Parameters
section.
IF Parameters (starting from SVR 4.4)
IF Power RX (only ODU Wideband AP/CC)
This button opens a window that allows setting the value of the IF 140 MHz power
from ODU to IDU, selecting between the value -16 dBm and -10 dBm. Clicking on
the IF Power (Rx) button, first the Rx IF Power window opens, warning the
operator that the modification of the parameter causes a temporary loss of the
payload in reception.
Fig. 6.116 Warning for temporary loss of the payload in reception (IF Power RX)
Clicking twice with the left button of the mouse on the IF Power (Rx) insertion field,
the following Field Editing window opens for the selection of the value.
Fig. 6.117 Configuration of IF Power (Rx)
6 - OPERATING GUIDE
6-79
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
IF RX Filter Bandwidth
This field displays the value of the bandwidth of the IF filter in reception. It can
assume two values (automatically set by the controller depending on the selected
bandwidth of the signal): 56 MHz and 28 MHz.
IF Attenuation (Tx)
This parameter is visible and configurable in case of AGC set to Off. The
configuration allows the operator setting the power of the transmitter from a
maximum of Pmin to a minimum of Pmin -15 dB, at step of 1 dB. It is a parameter
used only during the installation.
Fig. 6.118 Configuration of IF Attenuation (Tx)
6.7.1.12.2 Configuration of Narrowband ODU unit
Pressing the Configure button of the ODU section in the Equipment Status &
Configuration window (Fig. 6.4), the ODU Status & Configuration window opens,
where the operator can configure the ODU operative parameters.
Fig. 6.119 ODU Config window
Indications
Current TX Power
it display the current transmission power (dBm) of ODU unit
Current RX Power
it display the current reception power (dBm) of ODU unit
ATPC
Acting on this field, the operator can activate (On) or deactivate (Off) the operation of
the ATPC function for the automatic control of the ODU transmission power. Clicking
6 - OPERATING GUIDE
6-80
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
twice with the left button of the mouse on the selection field, the Field Editing window
opens for the selection of the value.
Fig. 6.120 Configuration of ATPC
TX Power
Acting on this field, the operator can set the value of the transmission power in case of
ATPC: Off. Possible values are: Nominal Power and Nominal Power - 8dB. Clicking
twice with the left button of the mouse on the selection field, the Field Editing window
opens for the selection of the value.
Fig. 6.121 Configuration of TX Power
ATPC Mode
Acting on this field, the operator can decide if the ATPC algorithm sets the P
TX
automatically or if the P
TX
is fixed to Pmin or Pmax value also with enabled ATPC
functionality. Clicking twice with the left button of the mouse on the selection field, the
Field Editing window opens for the selection of the parameter value.
Fig. 6.122 Configuration of ATPC Mode
ATPC Threshold 1 and 2 (in dBm)
It allows selecting the threshold for ATPC parameter. Clicking twice with the left button
of the mouse on the selection field, the Field Editing window for the insertion of the
parameter value.
6 - OPERATING GUIDE
6-81
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.123 Configuration of ATPC Threshold 1
Nominal Power Level Setting Mode (starting from SVR 4.4)
Acting on this field, the operator can set if:
assigning the same value of the transmission power to all the ODU units present
in the system (Common option)
specifying the value of the transmission power for each ODU of the system in
independently way (Independent option)
Clicking twice with the left button of the mouse on the selection field, the following Field
Editing window opens for the selection of the wished option.
Fig. 6.124 Configuration of Nominal Power Level Setting Mode
Nominal Power (dBm) (starting from SVR 4.4)
In this field, the operator must set the value of the nominal transmission power: this
value is used for the calculation of the RSPI performances. The value in dBm to set
changes according to the range of the ODUs (e.g.: for Narrowband ODU 18GHz, the
value is 18dBm). Clicking twice with the left button of the mouse on the selection field,
the following Field Editing window opens for the selection of the wished option.
Fig. 6.125 Configuration of Nominal Power
The default value of the parameter is 0 dBm and it is reset at each change of the
System Type.
6 - OPERATING GUIDE
6-82
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.2 Software Management
All the operations regarding the software of the units that compose the system can be
executed via Software menu. The menu items are:
Software Bank IDU (1 or 2), to download the software of the Controller unit for the
selected IDU unit
Software Bank ODU (Stby, 1, 2 or 3) to download the software of the Controller
unit for the selected ODU unit
FTP Transfer, to download the software via FTP
SW Reset, to reset the software from Manager
Fig. 6.126 Software menu
6.7.2.1 IDU Software Banks window
Selecting Software Bank IDU in the Software menu (Fig. 6.126), the IDU Software
Banks window opens, allowing to manage the memory banks of the IDU unit and to
verify the embedded software and/or firmeware running on the equipment unit.
The commands relevant to the memory banks and the unit softwares are available only
in case of login with administrator privileges (Admin user class); in case of login without
administrator privileges, the IDU Software Banks window (Fig. 6.127) is displayed
without the command push-buttons, as only read-only operations are possible.
The items related to software banks of the ODU units are present in menu only if
ODU Wideband are equipped in the system, as the ODU Narrowband units have
no software on board.
The item related to ODU 2 is present in menu only in case of System Type (1+1)
or (2+0).
The FTP Transfer and Controller Reset options are inactive in case of login
without administrator privileges.
With disabled Security, the FTP Transfer and Controller Reset options are
active also in case of login with Anonymous and Read Write user class.
6 - OPERATING GUIDE
6-83
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
The upper part of the IDU Software Banks window displays, in table format, the
operating status of the two memory banks of the IDU, with the indication of the following
information:
release, build and checksum of the software loaded on the active memory bank
release, build and checksum of the software loaded on the stand-by memory bank.
In case of error on the stand-by bank, the possibility to execute the switching of the
memory banks is disabled (Switch Banks push-button inactive) and the following
signaling is disabled:
Stand-by Bank Status: WRONG !
In the central part of the IDU Software Banks window, in case of login with administrator
privileges, there are two command push-buttons for the memory banks:
Switch Banks
This push-button issues the switching of the memory banks: the stand-by bank
becomes active, vice versa the bank that was active becomes standby. When the
switching command is executed, the Switch Banks window opens (Fig. 6.128),
where it is necessary to click on the Switch Banks push-button to confirm the
switching of the memory banks.
In order to signal that the management of the CPU is temporarily impossible due
to the operation (but the payload is saved), the following message is always
displayed:
With Security disabled, the command push-buttons of the IDU Software Banks
window are available also in case of login with Anonymous and Read Write user
class.
6 - OPERATING GUIDE
6-84
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006

THE CPU MANAGEMENT WILL BE TEMPORARILY LOST!
(all payload saved)
The switching operation runs the IDU software version contained in the bank that
became active; the pre-existing software continues running on the slave units.
Banks Alignment
This push-button copies the content of the active bank to the stand-by bank,
allowing to align the two banks.
In the lower part of the IDU Software Banks window, there is the table of the unit
software, composed by the Run Version fields, which indicate the version of the
software currently running on each BB-Modem unit.
The FPGA Version Alignment push-button allows aligning the FPGA versions on the
two BB-Modem units. When a IDU SW download is executed, this contains also FPGA
SW (with a given SW version-SW release). In this case, it is possible that the active SW
in FPGA is different (it has a different SW version-SW release) from that contained in
the new SW of the IDU unit. It is possible to replace the FPGA SW with the new one
(contained in the new SW of the IDU unit) using the FPGA Version Alignment
push-button. During the alignment of the FPGA version, there is traffic loss.
6.7.2.2 ODU Software Banks window (only for ODU Wideband)
Selecting Software Bank ODU in Software menu (Fig. 6.126) the ODU Software
Banks window opens, which allows managing the memory banks of the ODU unit and
checking the embedded software and/or the firmware running on the equipment units.
The commands relevant to the memory banks and the unit software are available only
in case of login with administrator privileges (Admin user class); in case of login without
administrator privileges, the ODU Software Banks window (Fig. 6.129) is displayed
without command push-buttons, as only read-only operations are possible.
The command for the switching of the banks causes a reset of the Controller, with
temporary loss of the equipment from NetViewer/LCT, without traffic loss. In case
of connection through F interface, it is necessary to run again the dial-up
connection.
In case of Read Only users, the IDU Software Banks window is composed only by
the upper part of the window for Read Write users. Furthermore, the checksum
indication is not displayed.
With disabled Security, the command push-buttons of the ODU Software Banks
window are available also in case of login with Anonymous and Read Write user
class.
6 - OPERATING GUIDE
6-85
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.129 ODU Software Banks window
The upper part of the ODU Software Bank window displays, in table format, the
operating status of the memory banks of the ODU, with the indication of the following
information:
release, build and checksum of the software loaded on the active memory bank
release, build and checksum of the software loaded on the stand-by memory bank.
In case of error on the stand-by bank, the possibility to execute the switching of the
memory banks is disabled (Switch Banks push-button inactive) and the following
signaling is disabled:
Stand-by Bank Status: WRONG !
In the central part of the ODU Software Banks window, in case of login with
administrator privileges, there are two command push-buttons for the memory banks:
Switch Banks
This push-button issues the switching of the memory banks: the stand-by bank
becomes active, vice versa the bank that was active becomes standby. When the
switching command is executed, the Switch Banks window opens, where it is
necessary to click on the Switch Banks push-button to confirm the switching of the
memory banks.
Fig. 6.130 Warning for payload loss
In order to signal that the management of the CPU is temporarily impossible due
to the operation (but the payload is saved), the following message is always
displayed:

PAYLOAD WILL BE LOST!
The switching operation runs the ODU software version contained in the bank that
bemame active.
Banks Alignment
This push-button pastes the content of the active memory bank to the stand-by
6 - OPERATING GUIDE
6-86
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
bank, allowing the alignment of the two banks.
If all the embedded software and/or firmware of all the units must be aligned, the
sequence to follow is this:
(1+0) configuration
Align in sequence the FPGA firmware of the IDU and the ODU software.
(1+1) H/S protected configuration
The sequence to follow depends on the ODU currently in service:
ODU 1 in service
First force in service the ODU 1; then align the software of ODU 2.
Then, force in service the ODU 2; then, align the software of ODU 1.
ODU 2 in service
First force in service the ODU 2; then align the software of ODU 1.
Then, force in service the ODU 1; then, align the software of ODU 2.
In Wideband ODUs, if a software version not compatible with the hardware is
downloaded, the Switch Banks push-button is inactive and a warning message is
displayed.
Fig. 6.131 Warning for not compatible SW
6.7.2.3 FTP Transfer
The FTP Transfer command of the Software menu (Fig. 6.126) runs the FTP Client
program, which allows the receiving/transmission of a file from/to the NE through the
FTP protocol.
This allows, for example, the download of the Controller software to the equipment.
The download operation loads the software build only to the standby banks of the
Controller; the pre-existing software continues running on the active banks of the
Controller.
The download of the software build of the equipment is possible only in case of login with
administrator privileges (Admin user class); in case of login without administrator
privileges, the FTP Transfer option of the Software menu is inactive.
For the details of the description of the graphic interface of FTP Client, refer to the
operating guide of NetViewer/LCT.
6 - OPERATING GUIDE
6-87
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.2.4 SW Reset window
Selecting SW Reset in Software menu (Fig. 6.126), the Software Reset window
opens. This command allows the user executing a software reset from Manager.
Fig. 6.132 Software Reset window
The THE CPU MANAGEMENT WILL BE TEMPORARILY LOST! (all payload saved),
message is displayed, informing the user about the consequence of the operation.
Press the Software Reset button to reset.
6.7.3 Management of the network parameters
Network menu contains the commands which allow the management of the network
element address, of the static routing table (par. 6.7.3.1) and of the equipment
interfaces:
IP Address, opens the IP Address window (par. 6.7.3.2);
NE Parameters, opens the NE Parameters window (par. 6.7.3.3);
Static Routing Table, opens the Static Routing Table window (par. 6.7.3.4).
Fig. 6.133 Network menu
With disabled Security, the download of the software build of the equipment is
allowed also in case of login with Anonymous user class.
6 - OPERATING GUIDE
6-88
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.3.1 Access to the dynamic routing table
The dynamic routing tables can be accessed in format of text file via an anonymous
FTP.
An anonymous FTP can be executed using any password (empty string included) in
combination with any of the following usernames: anonymous, guest or ftp. The
structure of the directories is displayed in the following figure.
Home directory for the anonymous FTP is DATA and then, once logged, it is necessary
to choose the DYNROUTE folder to open the file table.txt, which contains the
information related to the routing tables.
Fig. 6.134 Directory tree
The table.txt file has the following structure.
Fig. 6.135 Structure of table.txt file
The meaning of the different fields is the following:
IP_address is the IP address of the radio unit (example: 138.132.99.218)
equipment name is the equipment type (for example: SRA 4)
Date and Time is dd Mmm yyyy hh:mm:ss; the month is identified by the first three
characters of the English name and the time is base on 24 hours (example: 1 Feb
2003 19:54:06).
Each line is composed by the following fields:
Network Dest,
the destination IP address (host, subnet or network);
Subnet Mask,
which bits of the destination address are meaningful;
Gateway,
the IP address of the next hop;
6 - OPERATING GUIDE
6-89
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Interface,
interface (Q, F, R, etc...) identifier; where the route is directed (Q, F, R ecc); when
more interfaces of the same categories are present, an underscore character (_)
and a number identify each one of them (e.g.: R_1, R_2);
Metric,
number of hops for RIP protocol;
Protocol,
protocol that generates the entry. IANA names must be used: RIP, OSPF, LOCAL.
Besides the IANA names, the STAT string is used to identify the static route;
Additional,
indicates an additional route. The asterisk sign (*) in this column means that the
corresponding route is not used because an existing route exists and points to the
same destination;
Flag,
set of 4 hexadecimal digits (16 bits) indicating the status of some additional part of
information, according to IANA coding.
Fig. 6.136 Example of routing table seen by FTP
6.7.3.2 IP Address
The SRA 4 radio equipment is managed via the TNMP protocol, while the network
protocol is TCP/IP. Selecting IP Address in Network menu (Fig. 6.133), the IP
Address window opens, where the user can configure the IP Address and the Net Mask
for the selected network element.
The SRA4 equipment has, as default IP address: 192.168.255.3
In this condition, the Network Element is reachable at the default address both on
F interface and on Q interface.
When the IP address is changed, the equipment will be reachable:
on F interface, both at default IP address and to the new one
on Q interface, only at the new address.
Be careful in the execution of this operation, because a wrong configuration of the
NE parameters can make the network element unreachable.
After that the IP address of the equipment has been modified, it is necessary to
wait some minutes before reconnecting as administrator.
Never set these IP addresses:
0.x.x.x (network address = 0)
127.x.x.x (addresses reserved to loopback)
192.168.255.x (network addresses 192.168.255)
Y.x.x.x con 224<= Y<= 254 (network addresses of D and E classes)
255.x.x.x
for each subnetwork, the address with all 1 or all 0
6 - OPERATING GUIDE
6-90
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
The window opens in read-only modality. In order to modify one of the values displayed
in the window, click on the Modify push-button: the fields change to write modality and
the Modify push-button change name becoming OK.
The configuration of the IP address is possible only in case of login with administrator
privileges (Admin user class); in case of login without administrator privileges, the
Network window is displayed without the Modify push-button, as only read-only
operations are possible.
To remember the risks associated to the configuration of the IP address of thre
equipment, the following message is always displayed in the Network IP Address
window:
DANGEROUS OPERATION !
IF WRONGLY CONFIGURED,
THE NE WILL BE PERMANENTLY UNREACHABLE
Fig. 6.137 IP Address window (write modality)
Configuration of the parameters
IP Address
The IP address is the address through which the system identifies the equipment
into the IP network and it has to be an univocal one inside the entire IP network.
The configuration procedure is the following one:
click twice on the IP Address field; the system displays the configuration
window
insert the IP address of the equipment and then confirm the insertion clicking
on OK.
With disabled Security, the configuration of the IP address is alloed also in cae of
login with Anonymous user class.
All the configuration parameters (operating parameters, system parameters,
network parameters) are stored into the EEPROM memory of the hardware key,
except the IP address that is stored both on the hardware kewy and on the
Controller unit. When the equipment is switched on with hardware key inserted,
the IP address stored in the hardware key (if present) is always loaded.
6 - OPERATING GUIDE
6-91
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.138 Configuration of IP Address
Net Mask
The net-mask allows the solving of the IP address, because it has the function to
point out how many bits are used to address the sub-network and how many bits
are used to address the host. The net-mask has to be the same for all the
equipment belonging to the same sub-network. The configuration procedure is the
following one:
click twice on the Net Mask field; the system displays the configuration
window
insert the net-mask coupled with the equipment IP address and then confirm
the insertion clicking on OK.
Fig. 6.139 Configuration of Net Mask
6.7.3.3 Interface network parameters
If the user selects NE Parameters into the Network menu (Fig. 6.133), the NE
Parameters window (Fig. 6.140) opens, where it is possible to configure the network
parameters for the different interfaces used for the transport of the supervisory
information.
The supervisory of the radio networks is based upon IP networks that use the RIPv1
protocol for the distribution of the routing information.
Each equipment is an host of the IP network, that has to be able correctly to execute as
the routing of the supervisory information as the propagation of the routing information
towards other hosts and towards other networks/sub-networks.
For such an aim, the user has correctly to configure the network parameters for each
interfaces used for the transport of the supervisory information.
Into the NE Parameters window, there are the following interfaces:
It is necessary to pay particular attention during the configuration of the
parameters relevant to the NE interfaces, because a wrong setting can make
unreachable the equipment and/or can make unreachable the equipment of other
networks/sub-networks.
In case of login with reading only privileges (Read Only user class), the setting
fields are all reading only type ones.
6 - OPERATING GUIDE
6-92
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
F: it corresponds to the RS-232 serial interface, used for the connection between
LCT and equipment
Q: 10/100BaseT Ethernet interface, user for the connection between the
equipment Controller and the NetViewer supervisory system
R1 and R2: channels embedded into the radio frame, reserved for the
transmission, via radio, of the supervisory information; for each radio system, it is
present a R embedded channel:
in case of System Type (1+1) H/S and (1+1) FD, it is available one R channel
only; the other R channel ensures the redundancy
in case of System Type (2+0), if the Different Destination modality is
configured, two R1 and R2 channels are available. In case of Same
destination configuration, the radio channel is one and it is associated to the
stream of the system 1 (upper BB-modem)
in case of System Type (1+0), it is available only one R channel, because the
equipment is equipped with one radio system only.
Fig. 6.140 NE Parameters window (with ETH MTU = default value)
To point out the hazards connected with the configuring operation of the network
parameters, in the NE Parameters window, the following message is permanently
displayed:

DANGEROUS OPERATION !
IF WRONGLY CONFIGURED,
THE NE WILL BE PERMANENTLY UNREACHEABLE
6 - OPERATING GUIDE
6-93
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
ETH MTU (starting from SVR 4.5)
The operator can configure the number of octects on the Ethernet port. The
maximum allowed value is 1500. The default value is 1362. LCT/NetViewer
supports the following preset values: 500, 1362, 1492 and 1500.
Fig. 6.141 Configuration of ETH MTU
The operator can also insert a wished value, if included between 500 and 1500. To do
this, the operator must select the Other value in the Field Editing window, which opens
after a double click on the ETH MTU field. In this case, the NE Parameters window
displays another field on the right of ETH MTU.
Fig. 6.142 NE Parameters window with ETH MTU field set to Other
A double click on the field for the insertion of the value opens the following Field Editing
window.
Fig. 6.143 Window for the insertion of an arbitrary value of ETH MTU
Telnet Port
Telnet is an Internet protocol used to create a connection to a remote computer.
This field allows enabling/disabling the relevant communication port. A double click
on the insertion field opens the following Field Editing window. The possible
6 - OPERATING GUIDE
6-94
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
values are Enabled (port enabled) and Disabled (port disabled). Confirm ones
choice with OK.
Fig. 6.144 Enabling/disabling of the Telnet port
For each network interface, the operator must configure the parameters:
RIPv1
It allows managing the information for the updating of the routing tables. Possible
values are:
Enable, the interface is used to propagate and receive the RIPv1 information
Disable, the RIPv1 information are not propagated in output on the interface
and the RIPv1 received in input are ignored
Silent, the interface does not propagate the RIPv1 information in output; the
RIPv1 information received on the interface are however processed to update
the routing tables.
Fig. 6.145 Configuration of RIPv1
Static Route Propagation
It allows enabling/disabling, clicking on the Enable check-box, the propagation of
all the static routing information through the interface; the propagation is enabled
when it is present the marking symbol !, on the contrary it is disabled without the
marking symbol.
The subject option is a significant one only if the RIPv1 protocol is enabled on the
interface.
Border Gateway
It allows enabling/disabling, clicking on the Enable check-box, the Border Gateway
function on the interface; the subject function is enabled when it is present the
marking symbol !, on the contrary it is disabled without the marking symbol.
When the Border Gateway function is enabled, the system excludes the
information relevant to the sub-network from the routing tables forwarded through
If the RIPv1 parameter is Disable, the configuration of the Static Route
Propagation, Border Gateway and Ingress Summarization parameters is not
meaningful.
6 - OPERATING GUIDE
6-95
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
the interface; it is present only the information relevant to the network.
The Border Gateway function can be applied when a device connects two or more
different IP networks and it is used the RIPv1 protocol for the distribution of the
routing information.
Then, the Border Gateway function can be enabled only if the interface is used for
the direct connection with a different IP network.
interface.
Ingress Summarization (starting from SVR 4.4)
It allows enabling/disabling, clicking on the Enable check-box, the Ingress
Summarization function on the interface; the subject function is enabled when it is
present the marking symbol !, on the contrary it is disabled without the marking
symbol.
Though the RIPv1 protocol does not spread the subnet-mask, the Ingress
Summarization option allows pointing out the interpretation mode of the IP
addresses present into the routing tables received through the interface:
when the Ingress Summarization option is enabled, the system sees the
IP addresses as network/sub-network addresses; it applies the subnet-mask
of the IP address network/subnetwork or, as an alternative solution, it is
applied the subnetmask coming from the class of the IP address itself
when the Ingress Summarization option is disabled, the system sees the
IP addresses as host addresses (it is applied the subnet-mask
255.255.255.255).
The user can disable the Ingress Summarization option only in IP networks that
do not foresee the use of subnetworks.
Therefore, it is advisable, with the exception of specific cases, to enable always the
Ingress Summarization option.
interface.
6.7.3.4 Static Routing Table
Select Static Routing Table in Network menu (Fig. 6.133): the Routing Table window
opens. In this window the operator can configure the supervision network in order to
execute a correct routing of the IP packets. It is possible to manually set up to 16 static
routes associated to certain destinations. For each static route, it is necessary to
configure:
the destination IP address (Destination Address);
the SubNet Mask, which allows specifying the IP subnetwork, which the destination
IP address belongs to;
the IP address of the next hop (Gateway);
the distance (number of hops) to reach the destination (Metric).
This window opens in read only modality. To modify one of the value displayed in the
window, click on Modify button: the fields switch to write modality and the Modify button
This window displays a message informing the user to take care in the execution
of this operation, because a wrong configuration of the NE parameters can make
the network element unreachable.
6 - OPERATING GUIDE
6-96
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
changes name becoming OK.
Fig. 6.146 Static Routing Table window
Per each entry of the static route table, the parameters to configure are the following:
Destination Address
It is the destination IP address of the routing entry, which can be both the IP
address of an host and the IP address of a different network/subnetwork. The
configuration procedure is the:
click twice on the Destination Address field; the system displays the
configuration window
insert the destination address and then confirm the insertion clicking on OK.
Fig. 6.147 Configuration of Destination Network Routing Entry
SubNet Mask
It is the subnet -mask associated to the destination IP address of the routing entry.
The configuration procedure is the:
click twice on the SubNet Mask field; the system displays the configuration
window
insert the subnet-mask and then confirm the insertion clicking on OK.
6 - OPERATING GUIDE
6-97
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.148 Configuration of Subnet Mask
Gateway
It is the IP address of the gateway through which the destination of the routing entry
is reached. The configuration procedure is the:
click twice on the Gateway field; the system displays the configuration
window
insert the gateway address and then confirm the insertion clicking on OK.
Fig. 6.149 Configuration of Gateway Routing Entry
Metric
It is the number of hops which separate the equipment from the destination
indicated in the routing entry. The configuration procedure is the:
click twice on the Metric field; the system displays the configuration window
insert the metric and then confirm the insertion clicking on OK.
Fig. 6.150 Configuration of Metric
6.7.4 Configuration of the error notification thresholds
Selecting TCN Setting in Status&Config menu (Fig. 6.3), the TCN - Threshold
Settings window opens, where the operator can configure, on radio and tributary side
for the BB-Modem units, the BER value over which an alarm is notified.
The Notification Name column displays the name used for the notification of the
exceeding of the alarm thresholds to the operators.
To delete a static entry, it is sufficient to set 0.0.0.0 into its Gateway field.
6 - OPERATING GUIDE
6-98
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.151 TCN - Threshold Settings window
B1 Threshold for SD Alarm (tributary side)
The user can configure the B1 threshold on the signal in input to tributary from tributary
side, over which the related alarm of degradated signal is activated. The range of
selectable values is 10E-5 - 10E-9 (default: 10E-5). Clicking twice with the left button of
the mouse on the insertion field, the Field Editing window opens for the choice of the
wished threshold value.
Fig. 6.152 Configuration of B1 Threshold for SD alarm (tributary side)
B1 Threshold for SD Alarm (radio side)
The user can configure the B1 threshold on the signal in input to demodulator on radio
side, over which the related alarm of degradated signal is activated. The range of
selectable values is 10E-5 - 10E-9 (default: 10E-5). Clicking twice with the left button of
the mouse on the insertion field, the Field Editing window opens for the choice of the
wished threshold value.
Fig. 6.153 Configuration of B1 Threshold for SD alarm
6 - OPERATING GUIDE
6-99
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.7.5 Setting of date and time
The Date and Time option of the Status and Config menu (Fig. 6.3) runs an application
program of Netviewer/LCT, that allows the manual setting of date and time.
The date and time get a particular importance during the execution and the analysis of
the measurements and recordings on the equipment.
The date and time configuration can now be executed only in case of login with
administrator privileges (Admin user class); in case of login without administrator
privileges, the Date and Time option displays only a window for the displaying of the
current NE date and time (Fig. 6.154).
Fig. 6.154 Date & Time window
With Security disabled, the date and time configuration is allowed also in case of
login with Anonymous user class.
The manual setting of date and time is significant only if for the NE it has been
disabled the network synchronization. If for the NE, it is enabled the network
synchronization, the manual setting of date and time will be overwritten at the
next synchronization. The NEs are synchronized each 24 hours.
In case of date and/or time change, the performance windows of the NE are in an
incongruent status up to the end of the polling cycle. Then, it is necessary to wait
for some seconds (until to the refresh of the windows) before executing the
reading or the recording of the performances.
The Time Mode parameter points out the timing mode set for the network
synchronization:
Local mode: NE synchronized on the local time of the Server PC
GMT: NE synchronized on the Greenwich time.
For the description of the configuration procedure of date and time, refer to the
operating guide of NetViewer/LCT.
It is always possible to modify the date and time of the Network Element using
LCT/NetViewer when the recording of the long period performance is not active.
If the recording of the long period performance is started, LCT/NetViewer does not
allow the access to the window for the change of the date and time.
6 - OPERATING GUIDE
6-100
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.8 Alarms
Alarms menu allows to operator to display the status of the physical and functional
alarms present on SRA 4 equipment. Alarms menu contains the following commands:
Physical and Functional,
opens the Physical and Functional Alarms window (par. 6.8.1);
TCN,
opens the TCN-Alarm Threshold window (par. 6.8.2) (starting from SVR 4.4)
Station Alarms,
opens the Station Alarms window (par. 6.8.3) for the displaying of the station
alarms.
Fig. 6.155 Alarms menu
6.8.1 Physical and functional alarms
Selecting the Physical and Functional command in Alarms menu (Fig. 6.155), the
Physical and Functional Alarms window opens, where the general alarm status on the
equipment is displayed.
The window is subdivided into three parts: the Functional Alarms section, the Physical
Alarms section and the Severity Alarms section.
As regards the description of the alarm signaling LEDs present on the frontal
panel of the IDU, refer to the UMN manual of SRA 4.
In the alarm windows, the occurrence of a malfunction is signaled by:
the switching on of the red LED relevant to the alarm
the displaying of the ! symbol before the alarm acronym.
In normal conditions, the LEDs are switched on and of green color.
6 - OPERATING GUIDE
6-101
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.156 Physical and Functional Alarms window
Functional Alarms section
This section contains three buttons with the related signaling LEDs:
Tx Payload,
pressing this button, the TX Way Payload Functional Alarms window (Fig. 6.157)
opens, showing the detail of the alarms in the transmission section. The LED
summarizes the alarm status related to the transmission section:
green (normal condition)
red (alarm presence)
Rx Payload,
pressing this button, the RX Way Payload Functional Alarms window
(Fig. 6.159) opens, showing the detail of the alarms in the reception section. The
LED summarizes the alarm status related to the reception section:
Others,
pressing this button, the Other Functional Alarms window (Fig. 6.161) opens,
showing the functional alarm status of the other communication channels. The LED
summarizes the alarm status related to the this section:
Severity Alarms section
This section contains the four LEDs related to the four possible alarm severities present
on the equipment (Critical, Major, Minor, Warning). The possible statuses of the
signaling LEDs are:
6 - OPERATING GUIDE
6-102
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Physical Alarms section
Physical Alarms section subdivides the physical alarms according to the faulted
equipment component. Four main areas are highlighted:
IDU unit (IDU),
this area shows the alarm status of the sub-units composing the IDU and allows
opening, pressing the corresponding button, to detailed alarm window:
Alarms button: it opens the User Physical Alarms window for the Alarm unit
(Fig. 6.162)
Controller button: it opens the User Physical Alarms window for the
Controller unit (Fig. 6.163)
Mem Key button: it opens the User Physical Alarms window for the
hardware key (Fig. 6.164)
FAN button: it opens the User Physical Alarms window for FAN unit
(Fig. 6.166)
BB-Modem button: it opens the User Physical Alarms window for the
BB-Modem unit (Fig. 6.167)
The LEDs next each button have the following meaning:
IDU-ODU connection cable (Cable)
the LED displays the alarm status related to IDU-ODU cable:
Cable button opens the User Physical Alarms window related to IDU-ODU
interface (Fig. 6.168)
ODU unit (ODU)
the LED displays the alarm status related to ODU unit:
ODU button opens the User Physical Alarms window related to ODU unit
(Fig. 6.170)
system (System Alarms)
the LED displays the summarized alarm status of the system:
System Alarms button opens the User Physical Alarms window related to the
system alarms (Fig. 6.169).
CPU Cable push-button (starting from SVR 4.4)
It opens the User Physical Alarms window related to the cable connecting the two
CPUs (Fig. 6.173).
Exp Cable push-button (starting from SVR 4.4)
It opens the User Physical Alarms window related to the expansion cable connecting
the two BB-Modem cards (Fig. 6.174).
Cable push-button
It opens the User Physical Alarms window related to the i/f cable connecting the IDU
and ODU units (Fig. 6.168).
6 - OPERATING GUIDE
6-103
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.8.1.1 TX Way Payload Functional Alarms window
Pressing the Tx Payload button in the Physical and Functional Alarms window
(Fig. 6.156), the TX Way Payload Functional Alarms window opens, where the status
of the functional alarms of the transmission section is displayed.
For the BB-Modem and ODU units, the connection status is displayed.
Fig. 6.157 TX Way Payload Functional Alarms window (example)
The alarms are subdivided according to the transmission section they belong to.
SPI section
LOS Trib,
it is an alarm related to the tributary interface card, signaling a Loss Of Signal on
tributary side. This alarm can be caused by a loss of the clock signal or by payload
missing.
RST section (drop)
Pressing the STM-1 #1 button (or STM-1 #2 for System Type 2xSTM-1), the RST
Section STM-1 #1 window related to transmission side (Fig. 6.158) opens.
RST section (insert)
Tx AIS Ins.
it is an alarm related to the tributary interface card, signaling that the equipment has
inserted an AIS signal in the frame on tributary side.
The possible indications, relative to the light signalings of the alarm statuses and
the operational statuses, are: green (normal) and red (fault).
6 - OPERATING GUIDE
6-104
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.8.1.1.1 RST Tx STM-1 (BB-Modem) window
Pressing the STM-1 #1 button (or STM-1 #2 for System Type (2+0)) in the TX Way
Payload Functional Alarms window (Fig. 6.157), the RST Tx STM-1 (BB-Modem)
window opens.
Fig. 6.158 RST Tx STM-1 (BB-Modem) window
The status of the following alarms is displayed:
LOF Trib,
it is an alarm related to the main board, signaling a loss of the SDH frame on
tributary side.
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 and the J0 Inserted for
the tributary side. The received value is restituted by J0 Dropped measure.
B1 SD Trib,
it is an alarm related to the main board, signaling the exceeding of the threshold
set for the signal degradation related to byte B1 on tributary side.
Range of values to set the threshold: 10E-5 - 10E-9 (default: 10E-5).
6.8.1.2 RX Way Payload Functional Alarms window
Pressing the Rx Payload button in the Physical and Functional Alarms window
(Fig. 6.156), the RX Way Payload Functional Alarms window opens, where the status
of the functional alarms of the reception section is displayed.
For the BB-Modem and ODU units, the connection status is displayed.
6 - OPERATING GUIDE
6-105
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.159 RX Way Payload Functional Alarms window (example)
The alarms are subdivided according to the reception section they belong to.
RST section (insert)
Rx AIS Ins.
it is an alarm related to the tributary interface card, signaling the equipment has
inserted an AIS signal in the frame on the radio side
RST section (drop)
Pressing the STM-1 #1 button (or STM-1 #2 for System Type 2xSTM-1), the RST
Section STM-1 window related to reception side (Fig. 6.160) opens.
RSPI section
High BER
this alarm occurs when the S/N level in input to demodulator generates a BER
(about between 10E-7 and 10E-9)
Radio LOF
this alarm occurs in case of loss of synchronization of the proprietary frame
transmitted on radio channel
RF LOS
this alarm occurs when there is a loss of the radiofrequency signal
Early Warning HIGH
this alarm occurs when the S/N level in input to the demodulator generates a BER
indicatively between 10E-9 and 10E-11.
6 - OPERATING GUIDE
6-106
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Early Warning LOW
this alarm occurs when the S/N level in input to the demodulator generates a BER
indicatively between 10E-11 and 10E-13.
6.8.1.2.1 RST Rx STM-1 (BB-Modem) window
Pressing the STM-1 #1 (or STM-1 #2 for the 2xSTM-1 configuration in the RX Way
Payload Functional Alarms window (Fig. 6.157), the RST Rx STM-1 (BB-Modem)
window opens.
Fig. 6.160 RST Rx STM-1 (BB-Modem) window
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 and the J0 Inserted for the
radio side. The received value is restituted by J0 Dropped measure.
B1 SD Radio
it is an alarm related to the main board, signaling the exceeding of the threshold
set for the signal degradation related to byte B1 on radio side.
Range of values to set the threshold: 10E-5 - 10E-9 (default: 10E-5).
RX LOF
it is an alarm related to the main board, signaling a loss of SDH frame on radio side.
Rx Align
it is an alarm signaling the misalignment between the streams of BB-Modem 1 and
BB-Modem 2.
6.8.1.3 IDU Other Functional Alarms window
Pressing the Others button in the Physical and Functional Alarms window
(Fig. 6.156), the IDU Other Functional Alarms window opens, where the status of the
functional alarms related to the service, expansion and networking channels is
displayed.
The first three indications are to be intended as Early Warning alarms and not as
BER on line.
6 - OPERATING GUIDE
6-107
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
For BB-Modem unit, the connection status is displayed.
Fig. 6.161 IDU Other Functional Alarms window
The alarms are subdivided according to the section they belong to.
BB-Modem section
64kb/s G703 LOS Tx
it is an alarm related to the loss of signal of the 64 kbit/s channel in transmission
WS LOS Tx
it is an alarm related to the loss of signal of the Way-Side channel in transmission
Networking Channel section
R1 i/f
this alarm signals a wrong operation of the R radio channel used for the transport
of the supervision information.
RS-Controller section
SCS1 e SCS2
SCS1 and SCS2 activate when the correspondent cyclic SCS are not received
within a specific timeout.
RPS Locked (local)
it is the condition of switching block. It is activated as consequence of a fault in the
switching, for example for missing of both the SCS. In this condition, the stand-by
is released if it was occupied.
Refused Switching Ch St-by
it is the alarm of refused switching. This alarm is activated by the switching logic
when the switching procedure has not been terminated.
6 - OPERATING GUIDE
6-108
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.8.1.4 A.U. IDU User Physical Alarms window
Pressing the Alarms button in the Physical and Functional Alarms window
(Fig. 6.156), the A.U. IDU User Physical Alarms window opens, where the status of
the physical alarms of the Alarm unit is displayed.
Fig. 6.162 A.U. IDU User Physical Alarms window
Card Fail
it signals a fault on the Alarm unit
Power Supply to FAN Unit Protection Lost (Card Fail)
it signals the loss of the protection relevant to the power supply of the fan units
Power Supply to FAN Unit Lost (Card Fail)
it signals the loss of the power supply of the fan units.
6.8.1.5 Controller IDU User Physical Alarms window
Pressing the Controller button in the Physical and Functional Alarms window
(Fig. 6.156), the Controller IDU User Physical Alarms window opens, where the
status of the physical alarms of the Controller unit is reported.
Fig. 6.163 Controller IDU User Physical Alarms window
The status of the following alarm is displayed:
Card Fail
it signals a fault in the Controller unit.
6 - OPERATING GUIDE
6-109
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.8.1.6 Mem Key User Physical Alarms window
Pressing the Mem Key button in the Physical and Functional Alarms window
(Fig. 6.156), the Mem Key User Physical Alarms window opens, where the status of
the physical alarms of the hardware key is displayed.
Fig. 6.164 Mem Key User Physical Alarms window
Key Missing or Key Mismatch
it signals that the hardware key is not inserted in the IDU unit or the presence of a
key mismatch
Key Fault
it signals a fault of the hardware key
Double Key Inserted,
in case of systems with double IDUs (2+1, 3+1), it indicates that both the IDUs have
the hardware key inserted.
Pressing the Maintenance button, the Finestra Physical Maintenance Alarms -
hardware key window (Fig. 6.165) opens.
6.8.1.6.1 Mem Key Maint Physical Alarms window
Pressing the Maintenance button in the Mem Key User Physical Alarms window
(Fig. 6.164), the Mem Key Maint Physical Alarms window opens, where the status of
the physical maintenance alarms for the hardware key is displayed.
Fig. 6.165 Mem Key Maint Physical Alarms window
The red signalling hardware key Not Inserted or Mismatch is reported in the
different configuration and status windows of the equipment, in case of hardware
key not inserted in the IDU or in case of use of a wrong hardware key.
6 - OPERATING GUIDE
6-110
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Key Mismatcth
indicates a mismatch detected between the data of the hardware key and the data
stored in the IDU controller.
Key Missing
indicates that the hardware hardware key is not inserted in the IDU.
6.8.1.7 FAN IDU User Physical Alarms window
Pressing the FAN button in the Physical and Functional Alarms window (Fig. 6.156),
the FAN IDU User Physical Alarms window opens, where the status of the physical
alarms of FAN unit is displayed.
Fig. 6.166 FAN IDU User Physical Alarms window
Card Fail
it signals a fault in the FAN unit
All FANs Failure
it signals a fault in all the FAN units
Fan Protection Lost
it signals a loss of protection on the fan.
6.8.1.8 BB-Modem User Physical Alarms window
Pressing the BB-Modem button in the Physical and Functional Alarms window
(Fig. 6.156), the BB-Modem User Physical Alarms window opens, where the status of
the physical alarms of the BB-Modem unit is displayed.
The possible indications, relative to the light signallings of the alarm statuses and
The possible indications, relative to the light signallings of the alarm statuses and
6 - OPERATING GUIDE
6-111
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.167 BB-Modem User Physical Alarms window
BB Side Fail (Card Fail)
it signals a fault to the BB-Modem unit on BB side
Modem Side Fail (Card Fail)
it signals a fault to the BB-Modem unit on Modem side
VBAT Missing
it signals the missing of power supply to the POW connector of BB-Modem unit
Data Missing on Int Expansion
it signals the presence of a fault on the communication channel between the two
BB-Modem units.
XPIC IF Input (Co-channel)
it signals the loss of the canceller signal coming from the orthogonal Demodulator.
6.8.1.9 i/f User Physical Alarms window
Pressing the Cable button in the Physical and Functional Alarms window (Fig. 6.156),
the i/f User Physical Alarms window opens, where the status of the physical alarms of
the connection cable between IDU unit and ODU unit is displayed.
Fig. 6.168 User Physical Alarms - IDU-ODU i/f window
6 - OPERATING GUIDE
6-112
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
The status of the following alarm is displayed:
IDU-ODU i/f
it signals a malfunction or a fault on the IDU-ODU connection cable.
IDU ==> ODU IF Tx LOS
it indicates that the ODU does not detect the signal in input transmitted by the IDU.
6.8.1.10 System User Physical Alarms window
Pressing the System button in the Physical and Functional Alarms window
(Fig. 6.156), the System User Physical Alarms window opens, where the status of the
system physical alarms is displayed.
Fig. 6.169 System User Physical Alarms window
HW Mismatch
it signals that the equipped hardware does not allow the correct operation of the
system
FPGA Version Mismatch IDU #1 (#2)
it signals a mismatch between the FPGA version currently running and the FPGA
version contained in the software
Switch HSBY Mismatch (only HSBY system)
it signals a mismatch between the switch command, issued by IDU to the ODU
switch, and the effective status of the switch
SW Controller Mismatch
in the systems which foresee more than one IDU, it indicates that the two
controllers have a different software version.
Wrong Configuration CC Pair #n
in the co-channel system, it points out a wrong configuration of the Co-Channel
pair.
Wrong ODU Config for All CC Pair
in the co-channel system, it points out a wrong configuration of the frequency of all
the ODUs for the co-channel operation.
6 - OPERATING GUIDE
6-113
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.8.1.11 ODU User Physical Alarms window
Pressing the ODU button in the Physical and Functional Alarms window (Fig. 6.156),
the ODU User Physical Alarms window opens, where the status of the physical alarms
of ODU unit is displayed.
Fig. 6.170 ODU User Physical Alarms window
Card Fail
it signals a fault to the ODU unit
Cable Compensation Out of Range (Wideband ODU only)
this alarm occurs if the power compensation of the signal in input to ODU fails
because the power in input is too low or too high (if there is incongruence between
the real cable length and the setting of cable length on the BB-Modem unit)
Freq Plan Fail (Wideband ODU only)
this alarm occurs when the Frequency Plan configuration is meaningless or not
valid
Mem CK (Wideband ODU only)
this alarm is related to the ODU synchronism sources.
If the ODU is configured as master sync (internal synchronism source), the alarm
is related to the current status of the synchronism sources.
If ODU is configured as slave sync (synchronization signal taken by the other
ODU), the alarm indicates the condition of the synchronism sources stored the
last time that the ODU has been set as Master.
RF HSBY Switch Alarm (Narrowband ODU only)
this alarm occurs in case of a malfunction of the switching in radiofrequency.
Pressing the Maintenance button in the window of the previous figures, the windows of
the physical maintenance alarms for ODU Wideband (Fig. 6.171) and ODU Narrowband
(Fig. 6.172) open.
6 - OPERATING GUIDE
6-114
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.8.1.11.1 Physical Maintenance Alarms
*** Narrowband ODU ***
Pressing the Maintenance button in the ODU User Physical Alarms window
(Fig. 6.170), the ODU Maint Physical Alarms window opens.
Fig. 6.171 ODU Maint Physical Alarms window
Power Supply
it signals a fault in the ODU power supply section
Tx Amplifier
it signals a fault in the transmission amplifier
Rx OL Alarm
it signals a malfunction of the reception oscillator
Tx OL Alarm
it signals a malfunction of the transmission oscillator
Synt Alm
it signals a malfunction of the synthetizer
*** Wideband ODU ***
Pressing the Maintenance button in the ODU User Physical Alarms window
(Fig. 6.170), the ODU Maint Physical Alarms window opens.
Fig. 6.172 ODU Maint Physical Alarms window - Wideband ODU
6 - OPERATING GUIDE
6-115
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Power Supply
it signals a fault in the ODU power supply section
Tx Alarm
it signals an hardware fault in the ODU transmission chain (RF part excluded)
Rx Alarm
the activation in the ODU Physical Maint Alarms window of the RX Alarm
indication followed by the (due to NO ID 140) indication signals the missing of the
IF 140 MHz signal in ODU caused by the loss of the received field. The
continuation of this condition indicated a failure. This means that the persistency of
the NO IF 140 alarm for twenty minutes activates the Card Fail alarm.
Tx BIAS
it signals a fault in the RF TX part of ODU: the equipment does not transmit RF
signal.
6.8.1.12 i/f CPU User Physical Alarms window
Pressing the CPU Cable button in the Physical and Functional Alarms window
(Fig. 6.156), the i/f CPU User Physical Alarms window opens, where the status of the
physical alarms of the cable between the CPUs of the systems are displayed.
Fig. 6.173 i/f CPU User Physical Alarms window
CPU Expansion i/f
indicates a fault in the expansion interface cable.
6.8.1.13 i/f Exp Cable User Physical Alarms window
Pressing the Exp Cable button in the Physical and Functional Alarms window
(Fig. 6.156), the i/f Exp Cable User Physical Alarms window opens, where the status
of the physical alarms of the Expansion cable between the baseband cards of the
system is displayed.
6 - OPERATING GUIDE
6-116
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.174 i/f Exp Cable User Physical Alarms window
BB EXP i/f
indicates a fault in the expansion cable between the baseband cards.
6.8.1.13.1 i/f Exp Cable Maint Physical Alarms window
Press the Maintenance button in the i/f Exp Cable User Physical Alarms window
(Fig. 6.174): the i/f Exp Cable Maint Physical Alarms window.
Fig. 6.175 i/f Exp Cable Maint Physical Alarms window
BB EXP Cable Missing
indicates that the expansion cable between the baseband cards misses.
BB EXP Cable Fault
indicates that the expansion cable between the baseband cards is faulted.
6.8.2 Alarm Thresholds
Selecting TCN in Alarms menu (Fig. 6.155), the TCN - Alarm Threshold window
opens.
The TCN functionality is present starting from SVR 4.4.
6 - OPERATING GUIDE
6-117
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.176 TCN - Alarm Threshold window
This window displays, for each IDU present in the equipment, both on tributary side and
radio side, if the alarm threshold for the B1 byte has been exceeded on STM-1 stream.
Possible indications are:
green No (normal condition)
red Yes (fault)
6.8.3 Station alarm
Selecting Station Alarms in Alarms menu (Fig. 6.155), the Station Alarms window
opens, where the alarm signalings of the station are reported (max 4).
Fig. 6.177 Station Alarms window
Each alarm can be defined by the user in the Station Alarms window (Fig. 6.39). The
possible indications are:
red (fault)
Generally, the station alarms signal problems of the site where the network element is
located (e.g.: fire, open door, ecc...).
6 - OPERATING GUIDE
6-118
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.9 Management of Measurements
The operator can measure the value of the power received by the ODUs installed in the
system by means of the commands of Measurements menu.
Fig. 6.178 Measurements menu
The items in the Measurements menu are the following:
View, which opens the Unit Measurements window (Fig. 6.179);
Record submenu, which allows selecting on which of the two ODUs, installed in
the system, the measure of the received power will be made (par. 6.9.2).
6.9.1 Unit Measurements window
Selecting the View command in the Measurements menu (Fig. 6.178), the Unit
Measurements window opens, where
the destination of the radio channels (only for (2+0) System Types);
the temperature measures related to the IDU units present in the equipment;
the measures of the transmission and reception power related to the ODU units
installed in the system
are displayed.
Fig. 6.179 Unit Measurements window
6 - OPERATING GUIDE
6-119
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Radio Channel Destination indication (only (2+0) System Types)
In this System Type, the two radio beams are completely independent. They can be
routed in two different direction or in the same direction. This setting is useful to manage
correctly the supervision channels. Possible cases are:
Same destination
a single remote radio exists in correspondence to the two independent channels;
Different destinations
two different remote radio exist in correspondence to two independent radio
channels.
Parameters displayed in IDU section
BB-Modem Temperature
condition of the temperature of the BB-Modem board
Parameters displayed in the ODU section (Narrowband)
Rx Power: value of the power in reception (dBm);
Tx Power: value of the power in transmission: Nominal Power or Nominal Power -
8 dB.
Parameters displayed in the ODU section (Wideband)
Tx Power: value of the power in transmission (dBm);
Rx Power: value of the power in reception (dBm);
Tx Power min: minimum value of the power transmitted from when the equipment
starts to operate (dBm);
Tx Power max: maximum value of the power transmitted from when the equipment
starts to operate (dBm);
IF Cable Tx Att: value of the attenuation of the transmission on the IF cable (dBm);
ODU Temperature: temperature of the ODU unit (C).
6.9.2 Measurement of RX and TX ODU power
Selecting one of the options in the Measurement>Record menu, the RF RX Power
window opens for the selected ODU unit. This command runs an external application of
NetViewer/LCT program, which allows measuring the RF RX Power for the system.
The value of the TX Power could not to update correctly.
If LCT 6.1 is used for the recording of the received performance, it is necessary
that the Unit Measurements window is closed during the whole recording.
6 - OPERATING GUIDE
6-120
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.180 Measurement - Record menu
6.10 Performance Management
The event counters and parameters monitored by the equipment are divided into 4
classes:
Quality event counters (radio and tributary; applied to each STM-1)
Unavailability event counters (radio and tributary; applied to each STM-1)
RSPI parameters (radio only; applied to each transceiver)
RPS event counters (radio only; applied to each switching.
Only near end measurements are available (no far end reporting) and the
monodirectional approach is used. Measurement periods are 15 minutes and 24 hours.
Beyond the current periods, the NE will store the last 16 completed 15 minute periods
and the last 4 completed 24 hour periods. Each interval is characterized by:
all the applicable event counters/parameters;
a time counter for each measurement point: the actual number of seconds in the
interval (namely 900 and 86400);
a suspect interval flag for each measurement point: Boolean indication of abnormal
situation.
In case of System Type (1+0), the RF RX Power Rec command opens directly the
RF RX Power window.
For the description of the measuring procedure, refer to operating guide of the
NetViewer/LCT program.
If LCT 6.1 is used for the recording of the received performance, it is necessary
that the Unit Measurements window is closed during the whole recording.
Radio quality event counters and radio unavailability event counters are
measured in a way in line with ITU-T G.826 Recommendation. G.784 G.826
G.827 G.828 G.829 M.2100 M.2101 M.2110 M.2120 contain the relevant
specifications.
6 - OPERATING GUIDE
6-121
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Suspect Interval is a binary information associated to a measurement point and a
specific 15 minute or 24 hour interval. It is set when the measurement has not been run
on the complete interval or for any reason the results are not fully meaningful (for
example because a threshold has been modified within the interval or a manual
operation on the radio unit has impacted the performance results.
6.10.1 RST Parameters
There are 4 major types of measurement points:
Radio measurements before protection switching, relevant to transmitted and
received power levels (one point per transceiver)
Radio measurements after protection switching, relevant to regenerator
termination point of STM-1 signal (one point per STM-1 signal in N+0; one per each
protected STM-1 signal in protected configurations)
Radio Protection switching measurements (one point per network element)
Tributary measurements before protection switching, relevant to regenerator
termination point of STM-1 signal (one point per each STM-1 tributary signal
regardless STI or DTI System Type)
The quality counters are often called Error Performance event counters; they apply to
Radio and to Tributary interfaces (always before protection even in double protected
tributary configurations). In the radio side, in case of protection.
Errored Block (EB) is the elementary unit used to measure equipment performances.
SRA 4 equipment is always configured without MST, so only regenerator section
performance have to be measured (B1 parity check only has to be monitored). There is
one set of event counters and one suspect flag for each supported STM-1 signal. If one
of the two STM-1 is disabled the correspondent parameters are set to unavailable both
in the televalue exchange and in the XML file; the time interval during which the STM-1
signal changes status (from enable to disable or vice-versa) shall contain the measured
values and suspect flagging is required.
Quality event counters are listed in the following:
ES: Errored Second, defined as a second in which at least one errored block is
measured
SES: Severely Errored Second. Defined as a second in which more than 30% of
Errored Block is measured.
BBE: Number of Errored Blocks measured during a time period without SES.
6.10.2 Unavailability Parameters
They apply to Radio and to Tributary interfaces (always before protection even in double
protected tributary configurations). In the radio side, in case of protection, they are
calculated after protection switching.
SRA 4 appliance is always configured without MST, so only regenerator section
performance have to be measured (B1 parity check only has to be monitored). There is
one set of event counters and one suspect flag for each supported STM-1 signal. If one
of the two STM-1 is disabled the correspondent parameters are set to unavailable both
in the televalue exchange and in the XML file; the time interval during which the STM-1
signal changes status (from enable to disable or vice-versa) shall contain the measured
6 - OPERATING GUIDE
6-122
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
values and suspect flagging is required.
The following list contains the required event counters that qualify the unavailability of
the radio/tributary channel:
UAS: Unavailability Seconds, defined as the period during the link is out of service.
It is detected counting the number of consecutive SES. The Unavailability is
declared when 10 consecutive SES are detected on the radio/tributary link while it
is removed when 10 consecutive non-SES are detected.
OI: Outage Intensity, defined as the number of unavailability events measured
during a fixed time period T (a unavailability period starting in a measurement
period and ending in another one will be counted just once OI will be incremented
in the first measurement period or in the last measurement period affected by the
unavailability period).
6.10.3 RSPI parameters
These parameters apply to each radio channel and they are calculated on each radio
transceiver regardless possible protection switching.
The performance primitives related to the power are:
RL, Received Level is the received power measured by each Receiver.
TL, Transmitted Level, is the transmitted power measured by each active
Transmitter.
The measurement point for these events is Radio measurement point before protection.
RL (and related performance parameters described in the following 5.8.4.1) are related
to each Radio Receiver.
TL (and related performance events described in the following 5.8.4.2) are only
interesting when ATPC is enabled but they are collected regardless ATPC enabling (no
conditioning based on ATPC enabling is required).
In case of HSBY protection configuration TL of the stand-by transmitter reports a
Stand-By value (an unusually low and never applicable power level can be used, such
as -99 dBm). Performance parameters are calculated in accordance.
Received Power performance parameters
Required performance parameters related to the received power are:
RLTM: Received Level Tide Mark, provides both the minimum and the maximum
value of the received power, for both time intervals (15 minutes and 24 hours).
RLTS-i (with between 1 and 4): Received Level Threshold Seconds, the operator
can define 4 different thresholds on the received power; RLTS-1 counts the
number of the seconds during which the received power is below the first threshold
level; the same for RLTS-2, RLTS-3 and RLTS-4 for the other thresholds. Each
counter is automatically reset whenever the operator changes the corresponding
threshold value.
Transmitted Power performance parameters
Required performance parameters related to the transmitted power are:
TLTM: Transmitted Level Tide Mark, provides both the minimum and the maximum
value of the transmitted power, for both time intervals (15 minutes and 24 hours)
6 - OPERATING GUIDE
6-123
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
TLTS-i (with between 1 and 2): Transmitted Level Threshold Seconds, the
operator can define 2 different thresholds on the transmitted power; TLTS-1 counts
the number of the seconds during which the transmitted power is higher than the
first threshold; the same for TLTS-2 for the second threshold. These 2 counters are
automatically reset when the operator changes threshold values; each time interval
(15 minutes or 24 hours) where the measure is not completed, will be marked as
suspect interval.
Power Level Measurement implementation
In order to implement RSPI measurements, Hardware and Software need to interact to
produce a reasonable sampling of the Power Level measurements. Software will
sample Hardware registers once per second (this is the time resolution requested by
standards). The Hardware will make the following registers available (for each
transceiver):
Minimum received power after the last register reading
Maximum transmitted power after the last register reading
Threshold values
The configured threshold values at the end of each measurement interval for all the
above mentioned RSPI parameters shall be stored in appropriate televalues for each
measurement point and for each measurement interval.
6.10.4 RPS Counters
RPS performance event counter are referred to the Radio Protection Switching
measurement point. Channel switching performance is described by the following
performance events, and are not applicable to 1+0 and 2+0 System Types:
PSAC: Protection Switch Actual Count, defined as the number of switching events:
for the protected channel it is the number of Protection Switch Actual (PSA)
from the protected channel to the protection channel during a fixed time
interval (15 minutes and 24 hours).
for the protection channel, it is the number of switching (PSA) towards the
protection channel from any protected channel during a fixed time interval (15
minutes and 24 hours)
PSAD: Protection Switch Actual Duration, it is meaningful for revertive switching
only and it counts the number of second during which:
each protected channel has been switched on the protecting channel during
a fixed time interval (15 minutes and 24 hours);
for the protection channel, it is the time it has been used to protect any of the
protected channels during a fixed time interval (15 minutes and 24 hours).
FSRC: Failed Switch Request Count, it counts how many times at least one PSR
(Protection Switching Request) is not served during a fixed time interval (15
minutes and 24 hours). It is meaningful for protected channels only.
FSRD: Failed Switch Request Duration, for each channel it represents the number
of seconds during which at least one PSR (Protection Switching Request) is not
served during a fixed time interval (15 minutes and 24 hours).
6 - OPERATING GUIDE
6-124
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.10.5 Suspect Interval
There is a boolean suspect interval flag for each measurement point. Rules for defining
an interval as suspect depend on the specific measurement point. An interval is defined
as suspect if there are chances that performance counters and parameters report wrong
or meaningless values.
RST Suspect on Tributary side
The interval is marked as suspect when any of the following occur:
change of the network element timer;
software reset of the controller;
loss of communication from the controller to the base band card;
physical fault alarms (only alarms impacting the performance measurement
functionality);
any manual operation (configuration and commands) which has an impact on the
relevant performance counters.
RST Suspect on radio side
physical fault alarms (only alarms impacting the performance measurement
functionality; for example an ODU failure does not imply a suspect interval in this
measurement);
RPS Suspect
loss of communication from the controller to the base band card in 1+1 System
Types or to the RS Controller in N+1 System Types;
physical fault alarms (only alarms impacting the switching functionality and related
performance measurements; for example a failure in the switching hardware but
not an ODU failure);
any forcing of the switching (due to either a manual setting or a quality level request
via Element Manager operator configuration);
The PSAD, FSRC and FSRD counters are foreseen only for (N+1) systems.
6 - OPERATING GUIDE
6-125
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
RSPI Suspect
physical fault alarms (any fault in the modem - ODU chain including ODU failure);
change of any measurement threshold (RLT-i or TLT-i);
relevant performance parameters.
Change of transmitter conditions, such as ATPC enabling or disabling, change of
transmitted power, ODU squelch (due to protection switching) will give some anomalous
measurement values but measurement periods will NOT be flagged as suspect ones.
6.10.6 Performance menu
The operator can display and manage the performance of SRA 4 equipment by means
of the commands of Performance menu.
Fig. 6.181 Performance menu (example)
The items of the Performance menu are:
PM Setting
it opens the Performance-PM Setting window (par. 6.10.7) (starting from SVR
4.4);
View,
it opens the PM Monitoring View window (par. 6.10.8),
6 - OPERATING GUIDE
6-126
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Record,
it starts the recording procedure for the desired STM-1 stream. It is an external
application of NetViewer/LCT program, which allows recording the performance for
possible following processing.
6.10.7 Performance - PM Setting window
Selecting PM Setting in Performance menu (Fig. 6.181), the Performance - PM
Setting window opens.
Fig. 6.182 Performance PM Setting window - Common Thresholds
For the description of the recording procedures and the related windows, refer to
the operating guide of the NetViewer/LCT program.
The tool for the recording of the performance to file (Record menu) is not
available:
in NetViewer starting from release V7.0 Service Pack 3
in NCT starting from release V7.1.
The PM Setting option is present starting from SVR 4.4.
6 - OPERATING GUIDE
6-127
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.183 Performance PM Setting window - Independent Thresholds
6 - OPERATING GUIDE
6-128
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Signalings
System Type
It displays the current System Type of the equipment. It can be configured from the
System Configuration window (par. 6.7.1.1).
System Config
It displays the modulation type. It can be configured from the System
Configuration window (par. 6.7.1.1).
Configurations
RSPI Thresholds Setting
It allows establishing if the RSPI threshold set by the operator are the same for all
the ODU units installed in the system (Common) or if they change from ODU to
ODU (Independent). Clicking twice with the left button of the mouse, the following
Field Editing window opens for the choice of the desired value.
Fig. 6.184 Configuration of RSPI Thresholds Setting
RLTi (i=1..4) ODU
It allows setting the value of the RLT parameter for the selected ODU. Clicking
twice with the left button of the mouse, the following Field Editing window opens
for the choice of the desired value.
Fig. 6.185 Configuration of RLT ODU
TLTi (i=1..2) ODU
It allows setting the value of the TLT parameter for the selected ODU. Clicking
twice with the left button of the mouse, the following Field Editing window opens
for the choice of the desired value.
Fig. 6.186 Configuration of TLT ODU
6 - OPERATING GUIDE
6-129
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.10.8 Performance Monitoring View window
Selecting View in Performance menu (Fig. 6.181), the Performance Monitoring View
window. In the upper part of the wondow, the following fields are reported in read-only:
System Type and System Config (par. 6.7.1).
Fig. 6.187 Performance Monitoring View window
The Quarter and Day push-buttons allows the access to the displaying window of the
performances for each BB-Modem and ODU units present in the system.
RST Performance View: BB-Modem - Trib Side STM-1 (Quarter) window
RST Performance View: BB-Modem - Trib Side STM-1 (Day) window
RST Performance View: RX Chain - Radio Side STM-1 (Quarter) window
RST Performance View: RX Chain - Radio Side STM-1 (Day) window
RPS Performance View: RX Chain (Quarter) window
RPS Performance View: RX Chain (Day) window
RSPI Performance View: ODU Tx Side (Quarter) window
RSPI Performance View: ODU Rx Side (Quarter) window
RSPI Performance View: ODU (Day) window
Depending on the current System Type, only the push-buttons meaningful for that
System Type are displayed.
6 - OPERATING GUIDE
6-130
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.10.8.1 RST Performance View: BB-Modem - Trib Side STM-1 (Quarter)
window
Pressing a Quarter button related to the tributary side in the Performance Monitoring
View window (Fig. 6.187), the RST Performance View: BB-Modem Trib Side
(Quarter) window opens, corresponding to the BB-Modem unit and to the selected
stream (STM-1 #1 or STM-1 #2).
The performance relevant to the current quarter of an hour (Current Quarter) are into
the last row of the table.
At the beginning of a new measuring intervals, the measurements slides of one position
from the bottom towards up, replacing row by row the data relevant to the previous
intervals.
The Suspect Period column allows the identification of the intervals into which there
have been conditions such as to consider the measured performance as suspect and
then not correct one. These intervals are marked through the marking symbol !.
Fig. 6.188 RST Performance View: BB-Modem Trib Side (Quarter)
This read only window displays the measures of the quality and unavailability
parameters (par. 6.10.2) on the tributary side for the last 16 ranges of quarters and the
related measurement seconds.
6.10.8.2 RST Performance View: BB-Modem - Trib Side STM-1 (Day) window
Pressing a Day button related to the tributary side in the Performance Monitoring View
window (Fig. 6.187), the RST Performance View: BB-Modem Trib Side (Day) window
opens, corresponding to the BB-Modem unit and to the selected stream (STM-1 #1 or
STM-1 #2).
The performance relevant to the current interval of 24 hours (Current Day) are into the
last row of the table.
intervals.
then not correct ones. These intervals are marked by the marking symbol !.
6 - OPERATING GUIDE
6-131
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.189 RST Performance View: BB-Modem Trib Side (Day) window
This read only window displays the measures of the quality and unavailabilty
parameters (par. 6.10.2) on the tributary side for the last 4 days and the related
measurement seconds.
6.10.8.3 RST Performance View: RX Chain - Radio Side STM-1 (Quarter)
window
Pressing a Quarter related to the radio side in the Performance Monitoring View
window (Fig. 6.187), the RST Performance View: RX Chain - Radio Side STM-1
(Quarter) window opens, corresponding to the selected BB-Modem and stream (STM-1
#1 or STM-1 #2).
intervals.
Fig. 6.190 RST Performance View: RX Chain - Radio Side STM-1 (Quarter) window
parameters (par. 6.10.2) on the radio side for the last 16 ranges of quarters and the
related measurement seconds.
6 - OPERATING GUIDE
6-132
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.10.8.4 RST Performance View: RX Chain - Radio Side STM-1 (Day) window
Pressing a Day button related to the radio side in the Performance Monitoring View
window (Fig. 6.187), the RST Performance View: RX Chain - Radio Side STM-1 (Day)
window opens, corresponding to the selected BB-Modem and stream (STM-1 #1 or
STM-1 #2).
intervals.
Fig. 6.191 RST Performance View: RX Chain - Radio Side STM-1 (Day) window
parameters (par. 6.10.2) on the tributary side for the last 4 days and the related
measurement seconds.
6.10.8.5 RPS Performance View: RX Chain (Quarter) window
Pressing a Quarter button in the RPS column of the Performance Monitoring View
window (Fig. 6.187), the RPS Performance View: RX Chain (Quarter) window opens,
corresponding to the selected ODU unit and stream (STM-1 #1 or STM-1 #2).
intervals.
6 - OPERATING GUIDE
6-133
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.192 RPS Performance View: RX Chain (Quarter) window
This read only window displays the measures of the RPS parameters (par. 6.10.4) for
the last 16 ranges of quarters and the related measurement seconds.
6.10.8.6 RPS Performance View: RX Chain (Day) window
Pressing a Day button in the RPS column of the Performance Monitoring View
window (Fig. 6.187), the RPS Performance View: RX Chain (Day) window opens,
corresponding to the selected ODU unit stream (STM-1 #1 or STM-1 #2).
intervals.
Fig. 6.193 RPS Performance View: RX Chain (Day) window
This read only window displays the measures of the RPS parameters (par. 6.10.4) for
the last 4 days and related measurement seconds.
6 - OPERATING GUIDE
6-134
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.10.8.7 RSPI Performance View: ODU Tx Side (Quarter) window
Pressing a Quarter Tx button in the RSPI section of the Performance Monitoring View
window (Fig. 6.187), the RSPI Performance View: ODU Tx Side (Quarter) window
opens, corresponding to the selected ODU unit.
intervals.
Fig. 6.194 RSPI Performance View: ODU - Tx Side (Quarter) window
This read only window displays the measures of the RSPI parameters (par. 6.10.3) on
the transmission side for the last 16 ranges of quarters and the related measurement
seconds.
6.10.8.8 RSPI Performance View: ODU Rx Side (Quarter) window
Pressing a Quarter Rx button in the RSPI section of the Performance Monitoring View
window (Fig. 6.187), the RSPI Performance View: ODU Rx Side (Quarter) window
opens, corresponding to the selected ODU unit.
intervals.
6 - OPERATING GUIDE
6-135
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.195 RSPI Performance View: ODU - Rx Side (Quarter) window
This read only window displays the measures of the RSPI parameters (par. 6.10.3) on
the reception side for the last 16 ranges of quarters and the related measurement
seconds.
6.10.8.9 RSPI Performance View: ODU (Day) window
Pressing a Day button in the RSPI section of the Performance Monitoring View
window (Fig. 6.187), the RSPI Performance View: ODU (Day) window opens,
corresponding to the selected ODU unit.
intervals.
6 - OPERATING GUIDE
6-136
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.196 RSPI Performance View: ODU (Day) window
This read only window displays the measures of the RSPI parameters (par. 6.10.3) for
the last 4 days and related measurement seconds.
6.11 Inventory
Selecting Inventory in the operative menu (Fig. 6.2), the Inventory window opens,
allowing the access to the inventory data (stored in EEPROM) of the equipment units,
to read or write possible annotations (e.g.: date of commissioning, type of malfunction,
ecc.) and record them.
The number of units present in the system and displayed in the Inventory window
changes depending on the System Type of the equipment.
6 - OPERATING GUIDE
6-137
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.197 Inventory window
The window is divided into two parts: the area related to the hardware and the area
related to the software.
In the HW section, there are the command buttons to access to the windows which
display the equipment identificative data (par. 6.11.1) and allow writing the user data
(par. 6.11.2).
In the SW section, there are the buttons:
Equipment, which opens the Equipment Software window (Fig. 6.201) to display
the software data of the system units;
NetViewer (if the management software is NetViewer), which opens the About
NetViewer window (Fig. 6.202) to display the software data of the NetViewer
program
LCT (if the management software is LCT), which opens the About LCT window
(Fig. 6.203) to display the software data of the LCT program.
Report button opens the Inventory Data window to record the equipment data to file
(par. 6.11.5).
6 - OPERATING GUIDE
6-138
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.11.1 PID window
The operator can display the product identificative data (PID) for each equipment
component pressing the correspondent button of the PID column in the Inventory
window (Fig. 6.197): the PID window related to the selected component opens. The
reported data are the following:
Hardware Code, extension and release
Serial Number;
Manufacturer;
Equipment code;
Unit code;
Date of Last Modification;
Location of Last Repair;
Date of Last Repair.
Fig. 6.198 PID window (e.g.: Controller)
6.11.2 Management of the user inventory data
The user can insert some information or notes regarding the units composing the
equipment. This information are written into EEPROM and can be read anytime. To write
the unit data, follow this procedure:
in the Inventory window (Fig. 6.197), press the button of the User column
corresponding to the component whose data must be written: the USER window
opens;
Fig. 6.199 USER window (e.g.: Controller)
click twice on the data field: the Field Editing window opens for the data insertion;
6 - OPERATING GUIDE
6-139
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.200 User Inventory window
enter the data in the insertion field and click on OK to confirm and close the
window.
6.11.3 Equipment Software window
Pressing the Equipment button in the Inventory window (Fig. 6.197), the Equipment
Software window opens, where the Software Code and the Software Release of the
units present in the system are displayed.
Fig. 6.201 Equipment Software window
6.11.4 About window (NetViewer/LCT)
Pressing the NetViewer button in the Inventory window (Fig. 6.197), the About
NetViewer window opens, where:
Software Code of the Engine and the Plug-in of NetViewer;
Software Release of the Engine and the Plug-in of NetViewer.
are displayed.
The number of units present in the system and displayed in the Equipment
Software window changes depending on the System Type of the equipment.
6 - OPERATING GUIDE
6-140
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Fig. 6.202 About NetViewer window
Pressing the LCT button in the Inventory window (Fig. 6.197), the About NetViewer
window opens, where:
Software Code of LCT program;
Software Release of Engine and Plug-in of LCT
are displayed.
Fig. 6.203 About LCT window
6.11.5 Report
Pressing the Report button in the Inventory window (Fig. 6.197), the Inventory Data
window opens for the recording of the system data to file.
Report command runs an external application of NetViewer/LCT program, which allows
executing the report of the unit inventory data to file. It is possible to open the report file
and display the data using any text editor.
The inventory data recorded for each unit present in the equipment are the following.
They are recorded in a file with extension .INV, readable by the operator through a
standard text editor.
IDU
Software Code
Software Release
IDU Controller Software Release (only IDU Master)
CONTROLLER
Hardware Code
Serial Number
Manufacturer's Code
Equipment Code
Unit Code
For the description of the report procedure, refer to operating guide of
NetViewer/LCT program.
6 - OPERATING GUIDE
6-141
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Date of Last Modification
Location of Last Repair
Date of Last Repair
ALARMS UNIT
Hardware Code
Serial Number
Manufacturer's Code
Equipment Code
Unit Code
Date of Last Repair
BB-MODEM
Hardware Code
Serial Number
Manufacturer's Code
Equipment Code
Unit Code
Date of Last Repair
FAN
Hardware Code
Serial Number
Manufacturer's Code
Equipment Code
Unit Code
Date of Last Repair
MEM KEY
Hardware Code
Serial Number
Manufacturer's Code
Equipment Code
Unit Code
Date of Last Repair
6 - OPERATING GUIDE
6-142
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.12 Security
The Security menu allows configuring the parameters relevant to the NE Security, that
defines the access privileges of the Element Manager towards the equipment.
Into the Security window (Fig. 6.204), the user can execute the following operations:
to check the current user class and the enabling status of the NE Security
to change the enabling status of the NE Security and the access password for the
different user classes.
The layout of the Security window depends on the SVR of NetViewer/LCT.
Fig. 6.204 Security window (Admin user class)
In case of login a user class different from Admin, the Security window is available in
reading only mode.
Security
The procedure to enable/disable the password of a user class is the following:
a double click on the Security field: the following Field Editing window opens
Fig. 6.205 Window to enable the Security
to enable (disable) the password, select Enabled (Disabled)
The NE Security has to be necessarily enabled if:
two or more Managers (e.g.: two LCTs) can accesse at the same time
if the use of NetViewer is foreseen.
6 - OPERATING GUIDE
6-143
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
confirm the setting pressing the OK push-button.
Password
The procedure to modify a password is the following:
double click on the User Password field in the Set New Password section,
relevant to the interested user class: the following Field Editing window opens
Fig. 6.206 Field Editing for the insertion of the new password
type in the New Password field the new password and repeat the insertion in the
Confirm Password field;
press OK to confirm.
Accounting Log (starting from SVR 4.6)
When the Security is enabled, the NE embedded software stores in the non volatile
memory (memory of the Controller of NE and memory key) a list of (at most) 120 records
relevant to log actions (login or logout) executed by the operator. When the memory
reserved for this operation is full, the next log action deletes the oldest one (which is
overwritten).
Each record includes the following fields:
IP address of the operator
user class (Admin, ReadWrite, ReadOnly)
log action
date and time of the log action
This information are available uploading a file via FTP.
The operator can enable (Account Log Enable check box checked) or disable
(Account Log Enable check box uncheked) the accounting log functionality by means
of a click of the left button of the mouse on the corresponding box.
The default configuration value is Disabled, that is no connection/disaconnection action
is saved in the non volatile memory.
Only the user of Admin class can execute the download of the account.log file.
When the functionality id disabled, it is however possible to get the account.log
file, which contains the last 120 (at most) connection/disaconnection actions
executed when the function was enabled.
6 - OPERATING GUIDE
6-144
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.13 NE Severity
In network map the background color of the equipment name signals the summarized
alarm status of the equipment itself, that coincides with the one that has major severity.
The possible equipment severity status are:
Critical (CR): a service affecting condition has occurred and an immediate
corrective action is required (par. 6.13.1).
Major (MA): a service affecting condition has developed and it is possible to
postpone the corrective action (par. 6.13.2).
Minor (MI): a non-service affecting fault condition has occurred and it is possible
to postpone the corrective action (par. 6.13.3).
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 (par. 6.13.4).
Indeterminate (IND): severity level not included in the previous classification.
The formation of the summarized alarm signalizations and, than, the consequent NE
severity depends also on equipment System Type , because the singles alarm roots
severities can be different according to the System Type.
6 - OPERATING GUIDE
6-145
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.13.1 Critical
Alarm roots that determines Critical severity status:
IDU unit
Alarm Description System Type
Cable Fail (Unit Allarmi) Alarm unit fault ALL
Cable Fail (Controller) Controller unit fault ALL
Cable Fail (BB-Modem) BB-Modem unit fault ALL
Cable Fail (FAN) FAN unit fault ALL
IDU-ODU i/f IDU-ODU interface fault
(1+0)
(2+0)
All FANs i/f All fans fault ALL
Power Supply to FAN Unit
Lost (Card Fail)
Power supply missing to all the
fans
ALL
LOS Trib Loss of signal on tributary side
(1+0)
(2+0)
(1+1) STI
(2+1)
(3+1)
2x(1+1) STI
Tx AIS Ins. Insertion of AIS in TX
(1+0)
(2+0)
(1+1) STI
(2+1)
(3+1)
2x(1+1) STI
LOF Trib Loss of frame on tributary side
(1+0)
(2+0)
(1+1) STI
(2+1)
(3+1)
2x(1+1) STI
TIM Trib
Trail Identifier Mismatch -
tributary side
(1+0)
(2+0)
(1+1) STI
(2+1)
(3+1)
2x(1+1) STI
BB Side Fail (Card Fail) Unit faulted on BB side
(1+0)
(2+0)
(1+1) DTI
(2+1)
(3+1)
2x(1+1) DTI
Modem Side Fail (Card Fail) Unit faulted on Modem side
(1+0)
(2+0)
6 - OPERATING GUIDE
6-146
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
XPIC IF INPUT Alarm
Loss of signal from the
hortogonal Demodulator
(2+0)
High BER
BER about between 10E-9 and
10E-7 in RX
(1+0)
(2+0)
Radio LOF Loss of frame on radio side
(1+0)
(2+0)
TIM Radio
Trail Identifier Mismatch - radio
side
(1+0)
(2+0)
(1+1) STI
(2+1)
(3+1)
2x(1+1) STI
RX LOF Loss of frame in RX
(1+0)
(2+0)
(1+1) STI
(2+1)
(3+1)
2x(1+1) STI
6 - OPERATING GUIDE
6-147
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
ODU unit
Card Fail Fault of ODU unit
(1+0)
(2+0)
Cable Compensation Out of
Range
Compensation of the cable out of
range
(1+0)
(2+0)
Freq Plan Fail
Error in the configuration of the
frequency plan
(1+0)
(2+0)
PSALM Fault in ODU power supply
(1+0)
(2+0)
TX Amplifier Fault to transmission amplifier
(1+0)
(2+0)
RX OL Alarm Fault to reception oscillator
(1+0)
(2+0)
TX OL Alarm Fault to transmission oscillator
(1+0)
(2+0)
Synt Alm Fault of synthetizers for IF/RF
(1+0)
(2+0)
Power Supply Fault to power supply
(1+0)
(2+0)
Tx Alarm Alarm in transmission
(1+0)
(2+0)
Rx Alarm Alarm in reception
(1+0)
(2+0)
Tx BIAS Fault in RF part of TX of ODU
(1+0)
(2+0)
RF LOS Loss of RF signal
(1+0)
(2+0)
6 - OPERATING GUIDE
6-148
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
System
Switch HSBY Mismatch
Mismatch between command
and status of ODU
(1+1) HSBY
Wrong Configuration for CC
pair #n
Wrong Co-Channel Configuration
(2+0)
2x(1+1) HSBY
Cable Fail (IDU-ODU) 1 Connection cable 1 fault
(1+0)
(2+0)
IDU-ODU i/f 1 IDU-ODU interface 1 fault
(1+0)
(2+0)
IDU-ODU i/f 2 IDU-ODU interface 2 fault (2+0)
Cable Fail (IDU-ODU) 2 Connection cable 2 fault (2+0)
IDU==>ODU IF TX LOS
ODU does not detect the signal
of the IDU
(1+0)
(2+0)
Wrong ODU Freq
Configuration for CC Pair #n
Wrong configuration of the
frequency of the ODU #n for the
Co-Channel operation
2x(1+1) HSBY
Wrong ODU Freq
Configuration for All CC Pair
frequency of all the ODU for the
2x(1+1) HSBY
6 - OPERATING GUIDE
6-149
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.13.2 Major
Alarm roots that determines Major severity status:
ODU unit
(1+1)
(2+1)
(3+1)
2x(1+1)
Cable Fail (IDU-ODU) Connection cable fault
(1+1) HSBY STI
(1+1) FD DTI
IDU-ODU i/f IDU-ODU interface fault
(1+1)
(2+1)
(3+1)
2x(1+1)
(1+1)
(2+1)
(3+1)
2x(1+1)
Cable Compensation Out of
Range
Compensation of the cable out of
range
(1+1)
(2+1)
(3+1)
2x(1+1)
Freq Plan Fail
frequency plan
(1+1)
(2+1)
(3+1)
2x(1+1)
PSALM Fault in ODU power supply
(1+1)
(2+1)
(3+1)
2x(1+1)
TX Amplifier Fault to transmission amplifier
(1+1)
(2+1)
(3+1)
2x(1+1)
RX OL Alarm Fault to reception oscillator
(1+1)
(2+1)
(3+1)
2x(1+1)
TX OL Alarm Fault to transmission oscillator
(1+1)
(2+1)
(3+1)
2x(1+1)
Synth Fault of synthetizers for IF/RF
(1+1)
(2+1)
(3+1)
2x(1+1)
6 - OPERATING GUIDE
6-150
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Power Supply Fault to power supply
(1+1)
(2+1)
(3+1)
2x(1+1)
Tx Alarm Fault to transmission
(1+1)
(2+1)
(3+1)
2x(1+1)
(1+1)
(2+1)
(3+1)
2x(1+1)
(1+1)
(2+1)
(3+1)
2x(1+1)
IDU==>ODU IF TX LOS
of IDU
(2+1)
(3+1)
Refused Switching ChStby Alarm of refused switching
(2+1)
(3+1)
Refused Switching Ch 1 Alarm of refused switching
(2+1)
(3+1)
(2+1)
(3+1)
(2+1)
(3+1)
Mem CK
Malfunctioning of the
synchronism sources of the ODU
ALL
RF HSBY Switch Alarm
Malfunctioning of the switching in
radiofrequency
(1+1) HSBY
Wrong ODU Freq
Configuration for CC Pair #n
frequency of ODU #n for
(2+0)
Wrong ODU Freq
Configuration for All CC Pair
frequency of all the ODUs for
(2+0)
6 - OPERATING GUIDE
6-151
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
IDU unit
HIGH BER High value of BER on the line
(1+1)
(2+1)
(3+1)
2x(1+1)
(1+1)
(2+1)
(3+1)
2x(1+1)
TIM Radio
Trail Identifier Mismatch on radio
dise
(1+1) DTI
2x(1+1) DTI
(1+1) DTI
2x(1+1) DTI
RX Align
Mismatch between the frames
received by the demodulator of
BB-modem 1 and BB-modem 2
(1+1)
2x(1+1)
(1+1) DTI
2x(1+1) DTI
(1+1) DTI
2x(1+1) DTI
(1+1) DTI
2x(1+1) DTI
TIM Trib
Trail Identifier Mismatch -
tributary side
(1+1) DTI
2x(1+1) DTI
BB Side Fail
Fault of BB-Modem unit on BB
side
(1+1) DTI
2x(1+1) DTI
Data Missing on Int
Expansion
Fault of the communication
channel between the two
BB-modem card
(1+1)
(2+1)
(3+1)
Protection Lost (Card Fail)
Loss of FAN unit power supply
protection
ALL
BB Exp Cable Missing
The expansion cable misses
between the baseband cards
(2+1)
(3+1)
BB Exp Cable Fault
Expansion cable betwen the BB
unit in fault
(2+1)
(3+1)
BB Exp i/f
Fault in the interface cable
between the BB cards
(2+1)
(3+1)
VBAT Missing
Loss of power supply to
BB-Modem
ALL
Modem Side Fail
Fault to BB-Modem unit on
modem side
(1+1)
(2+1)
(3+1)
6 - OPERATING GUIDE
6-152
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
System
HW Mismatch Hardware mismatch ALL
FPGA Version Mismatch Mismatch of FPGA versions
(1+0)
(1+1)
(2+0)
The two Controllers has a
different SW version
2x(1+1)
(1+1)
(2+1)
(3+1)
CPU Expansion i/f
Fault in the interface expansion
cable
2x(1+1)
(1+1)
(2+1)
(3+1)
Double Key Inserted
Both the IDUs have the hardware
key inserted
2x(1+1)
(1+1)
(2+1)
(3+1)
Cable Fail (IDU-ODU) Connection cable fault (1+1)
IDU/ODU i/f IDU-ODU interface fault
(1+1)
(2+1)
(3+1)
RPS Locked
RPS locked condition (Radio
Protection Switch Locked) doesw
not allow the use of the
protection channel. If the channel
was used it is made free, if it was
free it is forced free until the
clearing oft he RPS locked
condition itself.
(2+1)
(3+1)
FAN Protection Lost FAN unit power supply loss ALL
6 - OPERATING GUIDE
6-153
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.13.3 Minor
Alarm roots that determines Minor severity status:
IDU unit
System
Key Fault Faulted hardware key ALL
SCS1 SCS1 not received within timeout
(2+1)
(3+1)
SCS2 SCS2 not received within timeout
(2+1)
(3+1)
64 Kb/s G703 LOS Tx Loss of signal ALL
WS LOS Tx
Loss of signal on Wayside
channel
ALL
R1 i/f Wrong operation of R channel
(1+0)
(1+1)
(2+0)
6 - OPERATING GUIDE
6-154
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
6.13.4 Warning
Alarm roots that determines Warning severity status:
IDU unit
B1 SD Trib B1 Signal Degrade ALL
Key Missing Hardware key not inserted in IDU ALL
Key missing or Key
Mismatch
Hardware key not inserted into
IDU or incongruence in the
hardware key
ALL
Key Mismatch Incongruence of hardware key ALL
Early Warning High
BER between 10E-11 and 10E-9
in RX
ALL
Early Warning Low
BER between 10E-13 and
10E-11 in RX
ALL
B1 SD Radio B1 Signal Degrade ALL
7 - ALARM MANAGEMENT
7-1
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
7 ALARM MANAGEMENT
7.1 Overview
The SRA4 equipment is provided with an alarm system, with different signaling modes
(via software, LED, connector returns), that starting from an alarm signal allows to the
operator to identify quickly the failed module or function.
The present document describes all the alarms available for the equipment, subdividing
them as according the functions as according to the different signaling modes.
7.2 Summary Alarm Signalings
The alarms are grouped according to the following severity resuming signals:
Critical: Alarm condition that involves the operation ability and that requires for an
immediate corrective action.
Major: Alarm condition that involves the operation ability and that requires for an
urgent corrective action.
Minor: Alarm condition that involves the operation ability and that requires for the
execution of a corrective action to prevent higher damages.
Warning: Condition of potential alarm or of potential service prevention, detected
before it can cause some effects on the system; it is necessary to execute an action
for an additional diagnosis operation (if it is necessary) and the trouble has to be
corrected to prevent that it can cause greater failures.
Indeterminate (IND): severity level not included in the previous classification.
7.3 Alarm Signaling via Software
Here below, all the single alarm roots regarding the operation of the equipment and
available via software are reported, subdivided by function.
As regards the description of the LEDs for alarm signaling, present on the front
panel of the IDU unit, refer to UMN manual of SRA4.
In the following table, where not clearly specified, the severity is considered valid
for all the System Types.
7-2
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Tab. 7.1 Functional Alarms: description and severity
Section Alarm Description Severity
TX Payload
CR: (1+0), (2+0), (1+1) STI,
(2+1), (3+1), 2x(1+1) STI
MAJ: (1+1) DTI, 2x(1+1)
DTI
CR: (1+0), (2+0), (1+1) STI,
(2+1), (3+1), 2x(1+1) STI
MAJ: (1+1) DTI, 2x(1+1)
DTI
CR: (1+0), (2+0), (1+1) STI,
(2+1), (3+1), 2x(1+1) STI
MAJ: (1+1) DTI, 2x(1+1)
DTI
TIM Trib Trail Identifier Mismatch - lato trib
CR: (1+0), (2+0), (1+1) STI,
(2+1), (3+1), 2x(1+1) STI
MAJ: (1+1) DTI, 2x(1+1)
DTI
B1 SD Trib B1 Signal Degrade WAR
RX Payload
Rx AIS Ins. AIS inserted in RX CR
High BER BER about 10E-3 in RX
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
TIM Radio
Trail Identifier Mismatch - radio
side
CR: (1+0), (2+0), (1+1) STI,
(2+1), (3+1), 2x(1+1) STI
MAJ: (1+1) DTI, 2x(1+1)
DTI
CR: (1+0), (2+0), (1+1) STI,
(2+1), (3+1), 2x(1+1) STI
MAJ: (1+1) DTI, 2x(1+1)
DTI
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
7-3
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Other
64 Kb/s G703 LOS Tx (User
Channel)
Loss of signal
MIN
WS LOS Tx (Way-Side
Channel)
Loss of signal on Wayside
channel
MIN
R i/f Wrong operation of R channel MIN
SCS1 SCS1 not received within timeout MAJ: (2+1), (3+1)
SCS2 SCS2 not received within timeout MAJ: (2+1), (3+1)
Refused Switching ChStby Alarm of refused switching MAJ: (2+1), (3+1)
Refused Switching ChStby 1 Alarm of refused switching MAJ: (2+1), (3+1)
Tab. 7.1 Functional Alarms: description and severity
7-4
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Tab. 7.2 Physical Alarms: description and severity
IDU: Alarm unit
Card Fail Alarm unit fault IND
Lost (Card Fail)
Power supply missing to all the
FAN units
CR
Protection Lost (Card Fail)
Loss of power supply to FAN
unit
MAJ
IDU: Controller Card Fail Controller unit fault IND
IDU: FAN
Card Fail FAN unit faulted CR
FAN Protection Lost FAN unit protection fault MAJ
All FANs Failure All fan units faulted CR
IDU: Mem Key
Key Fault Faulted hardware key MIN
Double Key Inserted
Both the IDUs have the
hardware key inserted
MAJ: 2x(1+1), (1+1), (2+1),
(3+1)
Key Missing
Hardware key not inserted in
IDU
WAR
Key Mismatch Incongruence of hardware key WAR
Key missing or Key
Mismatch
Hardware key not inserted into
IDU or incongruence in the
hardware key
WAR
IDU:
BB-Modem
BB Side Fail (Card Fail) BB-Modem unit fault
CR: (1+0), (2+0), (1+1) DTI,
(2+1), (3+1), 2x(1+1) DTI
Modem Side Fail (Card
Fail)
BB-Modem unit fault
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
VBAT Missing
Loss of power supply to
BB-Modem
MAJ
Data Missing on Int
Expansion
Fault of the communication
channel between the two
BB-modem card
MAJ: (1+1), (2+1), (3+1)
Card Fail Fault of BB-Modem unit CR
XPIC IF Input Alarm
(Co-Channel)
Loss of signal from the
hortogonal Demodulator
CR: (2+0)
CPU Cable CPU Expansion i/f
Fault in the interface expansion
cable
MAJ: 2x(1+1), (1+1), (2+1),
(3+1)
Exp Cable
BB Exp Cable Missing
The expansion cable misses
between the baseband cards
MAJ: (2+1), (3+1)
BB Exp Cable Fault
Expansion cable betwen the BB
unit in fault
MAJ: (2+1), (3+1)
BB Exp i/f
Fault in the interface cable
between the BB cards
MAJ: (2+1), (3+1)
7-5
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
ODU
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
Cable Compensation Out
of Range
Compensazione del cavo fuori
dai limiti
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
Freq Plan Fail
frequency plan
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
Mem CK
Malfunctioning of the
synchronism sources of the
ODU
MAJ
Power Supply Power supply faulted
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
Tx Alarm Transmission fault
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
TX Amplifier Transmission amplifier faulted
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
RX OL Alarm Reception oscillator faulted
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
TX OL Alarm Transmission oscillator faulted
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
Synt Synthetizers for IF/RF faulted
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
RF HSBY Switch Alarm
Malfunctioning of the switching
in radiofrequency
MAJ:(1+1) HSBY
Wrong ODU Freq
Configuration for CC Pair
#n
frequency of ODU #n for
MAJ:(2+0)
Wrong ODU Freq
Configuration for All CC
Pair
frequency of all the ODUs for
MAJ:(2+0)
7-6
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
IDU-ODU cable
IDU-ODU i/f IDU-ODU interface faulted
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
IDU==>ODU IF Tx LOS
of the IDU
CR: (1+0), (2+0)
MAJ: (1+1), (2+1), (3+1),
2x(1+1)
System
HW Mismatch Hardware mismatch MAJ
FPGA Version Mismatch Mismatch of FPGA versions MAJ: (1+0), (1+1), (2+0)
The two Controllers has a
different SW version
MAJ: 2x(1+1), (1+1), (2+1),
(3+1)
Switch HSBY Mismatch
Mismatch between command
and status of ODU
CR: (1+1) HSBY
Wrong Configuration for
CC Pair #n
Wrong Co-Channel
Configuration
MAJ: (2+0)
A - LICENSE UPGRADE PROCEDURE FOR SRA4 EQUIPMENT
A-1
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
A LICENSE UPGRADE PROCEDURE FOR
SRA4 EQUIPMENT
A.1 General
For IDU SRA4 Equipment the following features can be configured only if you have the
corresponding license privileges:
High Density RF: it enables possibility to set 128-TCM modulation
2xSTM1: it enables the possibility to set double capacity
Co-Channel: it enables possibility to set Co-Channel configuration
(*) You can upgrade your license type to 2xSTM1 only if you have High Density RF
In order to upgrade the License Type of IDU Sra4 an Upgrading kit is provided.
It is composed of:
A Smart Key (with USB interface): this key is programmed with specific number of
credits and allows to upgrade a specific license feature.
A CD-Rom with the following files:
Tab. A.1 License Type
License Type Allowed configurations
STM-1 Normal Density, Alternate
Polarization
32 TCM modulation AP
STM-1 Normal Density, Co-Channel 32 TCM modulation AP and CC
STM-1 High Density, Alternate
Polarization
STM-1 High Density, Co-Channel 32 TCM modulation AP and CC
64 TCM modulation AP and CC
2xSTM-1 High Density, Alternate
Polarization (*)
2xSTM1 128 TCM modulation AP
2xSTM-1 High Density,Co-Channel (*) 32 TCM modulation AP and CC
2xSTM1 128 TCM modulation AP and CC
Downgrade of License value is not foreseen.
A-2
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
Readme --> this file contains important notes and instruction
LicenseManager --> it contains file for install LicenseManager tool
SmartKey_Drivers --> it contains port drivers for Smart Key
A.2 Upgrading Procedure Steps
1. Install LicenseManager tool running the lm*_***SETUP.exe file (where *_***
corresponds to the version of LicenseManager tool, for example:
lm3_4b2SETUP.exe) on the CD of Upgrading License Kit:
2. Select SRA4
only
3. Press Next >
button
4. Press Install
button
5. Press Close
button
A-3
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
At the end of installation, lm_Sra4 shortcut is available on desktop or in Start Menu (in
SIEMENS License Manager folder)
2. Have a connection with LCT or NetViewer to SRA4 equipment, open the Feature
Control window and read License-Mask and Challenge-Number fields.
A-4
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
3. Connect Smart Key (contained in Upgrading License Kit) to appropriate PC port
4. Run LicenseManager tool (lm_Sra 4 shortcut):
5. Press OK button on Status window and DO NOT CLOSE the License Key
Generation window (for more safety memorize the four License-Key fields in a text
file).
6. Press Modify button on Feature Control window of SRA4 in order to enable
License Mask writing:

From this point, make sure that SRA4 equipment is in stable condition: do not
switch IDU off, do not perform SW reset up to the end of license upgrading
procedure!
(*) ATTENZIONE
Press Generate button only when you filled all boxes with the correct and real
values.
When License key is generated the value of the updated feature is subtracted
from the available total Credits on key.
Moreover every License-Key is strictly associated to the IDU that has the
specified License-Mask and Challenge-Number.
9. Write SRA4 current
License-Mask
10. Write SRA4current
Challenge-Number
11. Press Show License
button to verify the existing
license
12. Check feature you want
to enable
13. Press Generate button
(*)
14. License-Key is
generated
A-5
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
7. Copy the first filed of generated License-Key into the License Key #1 field.
8. Repeat previous step for the other three fields of License-Key and press Upgrade
button on Feature Control window.
Double
mouse
click
Copy and
Paste
A-6
SRA 4 - OMN
911-381/02A0460 - Issue 1, March 2006
9. The Feature Control window automatically closes. Open it again and verify that
License Type has the new value:
10. Close the License Key Generation window (Quit button).
PRINTED in ITALY
SRA 4
SVR 4.6
D.45
D.55
D.25
D.30
D.20
SRA 4
SVR 4.6
911-381/02A0460 Issue 1, March 2006
SRA 4
SVR 4.6
911-381/02A0460 Issue 1, March 2006
SRA 4
SVR 4.6
911-381/02A0460 Issue 1, March 2006 SRA 4
SVR 4.6
911-381/02A0460 Issue 1, March 2006
SRA 4
SVR 4.6
911-381/02A0460 Issue 1, March 2006
911-381/02A0460 Issue 1, March 2006

Siemens Sra4 Svr4.6 Omn - Operating Manual

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Siemens Sra4 Svr4.6 Omn - Operating Manual

Transféré par

Droits d'auteur :

Formats disponibles

Operating Manual

Vous aimerez peut-être aussi