Saral Alarms Notes

Operating ManualSRA L XD (IDU Plug-in)SVR 3.3

OMN

911-380/02A0330Issue 1, October 2003

Copyright (C) Siemens Mobile Communications S.p.A. 2003V.le Piero e Alberto Pirelli, 10I-20126 Milano

Issued by Customer Documentation DepartmentS.S. 11 Padana Superiore, km 158I-20060 Cassina de’ Pecchi MI

Technical modifications possible.Technical specifications and features are binding only insofar asthey are specifically and expressly agreed upon in a written contract.

SRA L XD (IDU Plug-in) - OMN911-380/02A0330 - Issue 1, October 2003

STATUS OF MANUAL

The subject Manual is the operating guide of the SRAL XD equipment for the versionwith IDU Plug-in and SVR 3.3.

STATUS OF MANUAL

– Current: Issue 1, October 2003

– Previous:

R-1SRA L XD (IDU Plug-in) - OMN911-380/02A0330 - Issue 1, October 2003

STATUS OF MANUAL

BLANK PAGE

R-2SRA L XD (IDU Plug-in) - OMN

911-380/02A0330 - Issue 1, October 2003

INDEX

INDEX

STATUS OF MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R.1

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.1

LIST OF ILLUSTRATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.5

LIST OF TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.9

1 GENERAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1

1.1 Object and purpose of the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1

1.2 Equipment functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1

1.3 Testing and Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3

1.4 Responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3

1.5 Supplying conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4

1.6 Correlated Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4

1.7 List of the Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5

2 PLUG-IN INSTALLATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

2.2 Plug-In Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

2.3 Plug-In Disinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3

3 DOWNLOAD OF THE EQUIPMENT SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

3.2 Download via FTP of the Equipment Build Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3

3.3 Switching of the Banks and Alignment of the Unit Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9

4 OPERATING GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1

4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1

4.2 Software Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.14.2.1 Plug-in functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.14.2.2 Memory hardware key and operating status of the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . 4.34.2.3 License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.54.2.4 Unit software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.64.2.5 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.64.2.6 Unit connection status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7

4.3 NE Profile Uploading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8

4.4 Structure of the Operating Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9

I-1SRA L XD (IDU Plug-in) - OMN911-380/02A0330 - Issue 1, October 2003

INDEX

4.5 Status and Config Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.114.5.1 Equipment configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.114.5.1.1 System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.154.5.1.1.1 System Type configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.184.5.1.1.2 System activation option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.194.5.1.1.3 ODU power supply option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.194.5.1.1.4 Configuration of the system payload capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.204.5.1.1.5 Configuration of the parameters for the link identification. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.214.5.1.1.6 ODU type configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.234.5.1.2 Configuration of the external interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.244.5.1.2.1 Configuration of the Access unit interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.254.5.1.2.2 Configuration of the Controller unit interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.304.5.1.2.3 Configuration of the BB unit tributaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.324.5.1.3 Configuration of the protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.344.5.1.4 Test configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.394.5.1.5 Updating of the license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.424.5.1.6 Uploading/memorization of the NE configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.434.5.1.7 ODU configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.444.5.1.7.1 Configuration of the RF density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.474.5.1.7.2 Configuration of the RF TX power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.484.5.1.7.3 Configuration of the coupling loss for Hot-Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.484.5.1.7.4 Configuration of the modulation index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.494.5.1.7.5 Configuration of the frequency mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.504.5.1.7.6 Continuous frequency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.514.5.1.7.7 Frequency plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.524.5.2 Management of the equipment software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.564.5.2.1 Management of the memory banks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.564.5.2.2 Download of the equipment build software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.604.5.2.3 Reset of the Controller unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.614.5.3 Configuration of the network parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.624.5.3.1 Configuration of the IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.624.5.3.2 Configuration of the network parameters for the interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 4.654.5.3.3 Configuration of the static routing table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.704.5.4 Configuration of NE date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.73

4.6 Alarms Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.754.6.1 Functional and physical alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.754.6.1.1 Unit physical alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.764.6.1.1.1 Alarms of the Access unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.774.6.1.1.2 Alarms of the Controller unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.784.6.1.1.3 Alarms of the memory hardware key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.784.6.1.1.4 Alarms of the BB unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.794.6.1.1.5 Alarms of I/F cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.804.6.1.1.6 Alarms of ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.814.6.1.2 Functional alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.824.6.1.2.1 Alarms of TX payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.834.6.1.2.2 Alarms of RX payload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.864.6.1.2.3 Alarms of tributary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.894.6.1.2.4 Network alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.904.6.1.3 Resuming signals of the alarm severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.914.6.2 Station alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.92

4.7 Measurements Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.934.7.1 Reading of the RF TX - RX power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.934.7.2 Measurement of the RF RX power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.94

4.8 Performance Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.95

I-2SRA L XD (IDU Plug-in) - OMN

911-380/02A0330 - Issue 1, October 2003

INDEX

4.8.1 Displaying of the performance data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.964.8.1.1 Performance data referred to the quarters of an hour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.984.8.1.2 Perfomance data referred to the 24 hours. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.994.8.2 Recording on file of the perfomance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1004.8.3 Summary of the measuring interventions relevant to the perfomance data . . . . . . . . . . . . . 4.101

4.9 Inventory Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1024.9.1 Hardware data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1034.9.1.1 PID data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1034.9.1.2 User data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1044.9.2 Software data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1044.9.2.1 Equipment software data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1054.9.2.2 LCT software data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1064.9.2.3 NetViewer software data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1064.9.3 Report of the inventory data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.106

4.10 Security Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.107

4.11 NE Severity in NetViewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1084.11.1 Alarms with Critical severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1094.11.2 Alarms with Major severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1144.11.3 Alarms with Minor severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1204.11.4 Alarms with Warning severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1214.11.5 Alarms with Indeterminate severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1224.11.6 Events with Test severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.123

2 ALARM MANAGEMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

2.2 Alarm Resuming Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

2.3 Alarm Signal via Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.142.3.1 Physical alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.142.3.2 TX alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.172.3.3 RX alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.192.3.4 Tributary alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.212.3.5 Network alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.222.3.6 Station alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.22

2.4 Alarm Signalling LED’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.23

2.5 Connector Returned Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.24

2.6 AIS logics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.252.6.1 AIS insertion in TX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.252.6.2 AIS insertion in RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.25


INDEX


911-380/02A0330 - Issue 1, October 2003

LIST OF ILLUSTRATIONS


Fig. 2.1 Plug-in installation (1/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2Fig. 2.2 Plug-in installation (2/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2Fig. 3.1 Download procedure via FTP (1/8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3Fig. 3.2 Download procedure via FTP (2/8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3Fig. 3.3 Download procedure via FTP (3/8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4Fig. 3.4 Download procedure via FTP (4/8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4Fig. 3.5 Download procedure via FTP (5/8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5Fig. 3.6 Download procedure via FTP (6/8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6Fig. 3.7 Download procedure via FTP (7/8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7Fig. 3.8 Download procedure via FTP (8/8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8Fig. 3.9 Software Bank command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10Fig. 3.10 Equipment Software Bank window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11Fig. 4.1 Example of map with SRA L XD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8Fig. 4.2 SRA L XD operating menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10Fig. 4.3 Status and Config menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.11Fig. 4.4 Equipment Status & Configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.12Fig. 4.5 System Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.16Fig. 4.6 System Type Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.18Fig. 4.7 System activation configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.19Fig. 4.8 ODU power supply configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.19Fig. 4.9 Capacity Setting window (reading only mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.20Fig. 4.10 Capacity Setting window (read/write mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.20Fig. 4.11 Configuration window of the payload capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.20Fig. 4.12 Link Identification Parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.21Fig. 4.13 Link Id Code Inserted configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.22Fig. 4.14 Link Id Code Expected configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.22Fig. 4.15 ODU type configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.23Fig. 4.16 External Interfaces Setting window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.24Fig. 4.17 Enabling/disabling window for the D channel transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.28Fig. 4.18 Selection window of the D channel transport tributary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.28Fig. 4.19 Selection window for the D channel transport slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.28Fig. 4.20 Add/Drop Config window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.29Fig. 4.21 Configuration window for the tributary add/drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.30Fig. 4.22 Configuration window for the user channel add/drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.30Fig. 4.23 Station Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.30Fig. 4.24 Configuration window for the name of the station alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.31Fig. 4.25 Configuration window for the polarity of the station alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.31Fig. 4.26 BB Payload window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.32Fig. 4.27 Configuration window of all the tributary at the same time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.33Fig. 4.28 Configuration window of a single tributary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.34Fig. 4.29 Protection Status & Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.35Fig. 4.30 Configuration window for the BB forcing via software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.36Fig. 4.31 Configuration window for the channel forcing via software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.36Fig. 4.32 Configuration window for the Hot-Standby protection mode of BB. . . . . . . . . . . . . . . . . . . . . . . . . 4.37Fig. 4.33 Configuration window of the static delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.37Fig. 4.34 Testing Mode & Loop-Backs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.39Fig. 4.35 Configuration window of the local loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.40Fig. 4.36 Configuration window of the remote loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.41Fig. 4.37 Configuration window for the temporary turning off timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.41Fig. 4.38 Feature Control window (reading only mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.42



Fig. 4.39 Feature Control window (read/write mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.43Fig. 4.40 Insertion of License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.43Fig. 4.41 ODU Config window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.45Fig. 4.42 Configuration window of RF density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.48Fig. 4.43 Configuration window of the RF TX power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.48Fig. 4.44 Configuration window for the coupling loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.49Fig. 4.45 Configuration window of the modulation index mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.50Fig. 4.46 Configuration window of the modulation index (in Free mode only) . . . . . . . . . . . . . . . . . . . . . . . 4.50Fig. 4.47 Configuration window of the frequency mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.50Fig. 4.48 Configuration window of the RF TX frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.51Fig. 4.49 Configuration window of the RF RX frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.51Fig. 4.50 Frequency Plan Setup window (reading only mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.53Fig. 4.51 Frequency Plan Setup window (read/write mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.53Fig. 4.52 Configuration window of the N0 channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.53Fig. 4.53 Configuration window of the NN channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.54Fig. 4.54 Configuration window for the frequency of the first channel (TF0) . . . . . . . . . . . . . . . . . . . . . . . . 4.54Fig. 4.55 Configuration window of the spacing between two adjacent channels . . . . . . . . . . . . . . . . . . . . . 4.54Fig. 4.56 Selection window of the payload capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.55Fig. 4.57 Selection window of the channel RF density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.55Fig. 4.58 Configuration window of the RF Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.56Fig. 4.59 Software menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.56Fig. 4.60 Equipment Software Bank window (with administrator privileges) . . . . . . . . . . . . . . . . . . . . . . . . 4.59Fig. 4.61 Equipment Software Bank window (without the administrator privileges) . . . . . . . . . . . . . . . . . . . 4.60Fig. 4.62 Warning for bank switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.60Fig. 4.63 FTP Transfer option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.61Fig. 4.64 Error of FTP Client not installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.61Fig. 4.65 Controller Reset option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.61Fig. 4.66 Controller Reset window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.62Fig. 4.67 Network menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.62Fig. 4.68 Network IP Address window (reading only mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.63Fig. 4.69 Network IP Address window (read/write mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.64Fig. 4.70 Configuration window of the IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.64Fig. 4.71 Configuration window of the subnet-mask. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.64Fig. 4.72 NE Parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.67Fig. 4.73 Configuration window of the interface network protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.68Fig. 4.74 Configuration window of the metric reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.70Fig. 4.75 Static Routing Table window (reading only mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.71Fig. 4.76 Static Routing Table window (read/write mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.71Fig. 4.77 Configuration window of the routing IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.72Fig. 4.78 Configuration window for routing subnet-mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.72Fig. 4.79 Selection window for routing interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.73Fig. 4.80 Configuration window for routing gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.73Fig. 4.81 Date and Time menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.73Fig. 4.82 Date & Time window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.74Fig. 4.83 Alarms menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.75Fig. 4.84 Physical & Functional Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.75Fig. 4.85 Access User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.77Fig. 4.86 Access Maint Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.77Fig. 4.87 Controller User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.78Fig. 4.88 Controller Maint Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.78Fig. 4.89 Mem Key User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.78Fig. 4.90 BB User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.79Fig. 4.91 BB Maint Physical Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.79Fig. 4.92 Cable User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.80Fig. 4.93 Cable Maint Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.80


911-380/02A0330 - Issue 1, October 2003


Fig. 4.94 ODU User Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.81Fig. 4.95 ODU Maint Physical Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.81Fig. 4.96 Tx Functional Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.83Fig. 4.97 BB Tx Functional Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.84Fig. 4.98 Rx Functional Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.86Fig. 4.99 BB Tributaries Functional Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.90Fig. 4.100 Networks Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.90Fig. 4.101 Station Alarms window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.92Fig. 4.102 Measurements menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.93Fig. 4.103 Unit Measurements window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.94Fig. 4.104 Performance menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.96Fig. 4.105 System Performance Monitoring View window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.97Fig. 4.106 System Performance Monitoring on B1 Byte (Quarter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.99Fig. 4.107 System Performance Monitoring on B1 Byte (Day) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.99Fig. 4.108 Record menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.100Fig. 4.109 Events Presence Summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.101Fig. 4.110 Inventory window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.102Fig. 4.111 PID data window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.103Fig. 4.112 User data window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.104Fig. 4.113 Insertion window of the user data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.104Fig. 4.114 Equipment Software window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.105Fig. 4.115 About LCT window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.106Fig. 4.116 About NetViewer window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.106Fig. 4.117 Security window (read/write mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.107Fig. 4.118 Security window (reading only mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.107




911-380/02A0330 - Issue 1, October 2003

LIST OF TABLES

LIST OF TABLES

Tab. 4.1 Structure of the SRA L XD operating menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10Tab. 4.2 Supported payload capacities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.21Tab. 4.3 User/D-Ext interfaces and embedded D channels according to the System Type . . . . . . . . . . . . . 4.26Tab. 4.4 Max. number of channels into the frequency plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.52Tab. 4.5 Alarms with Critical severity in protected configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.109Tab. 4.6 Alarms with Critical severity in not protected configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.110Tab. 4.7 Alarms with Major severity in protected configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.115Tab. 4.8 Alarms with Major severity in not protected configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.119Tab. 4.9 Alarms with Minor severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.120Tab. 4.10 Alarms with Warning severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.121Tab. 4.11 Alarms with Indeterminate severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.122Tab. 4.12 Eventi di severità Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.123Tab. 2.1 Alarm resuming signals in protected configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2Tab. 2.2 Alarm resuming signals in not protected configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8Tab. 2.3 Physical alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.14Tab. 2.4 TX alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.17Tab. 2.5 RX alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.19Tab. 2.6 Tributary alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.21Tab. 2.7 Network alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.22Tab. 2.8 Station alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.22Tab. 2.9 Alarm signalling LED’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.23Tab. 2.10 Connector returned alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.24


LIST OF TABLES


911-380/02A0330 - Issue 1, October 2003

1 - GENERAL INFORMATION

1 GENERAL INFORMATION

1.1 Object and purpose of the ManualThe subject OMN Manual provides to the user the information necessary for themanagement via software of the SRAL XD digital radio equipment with low capacity inits version with IDU Plug-in and SVR 3.3. The management via software of theequipment can be executed as by NetViewer (management system of radio networks)as by LCT (management system of the local terminal and/or of the radio link).

1.2 Equipment functionsThe equipment SVR 3.3.0 supports the following functions:

– System configurations (System Type):• Single terminal: (1+0)• Double terminal: 2x(1+0)• Terminal with protection (1+1) at frequency diversity: (1+1) FD• Terminal with (1+1) Hot-Standby protection: (1+1) H/S• Repeater with possibility of tributary Add/Drop: A/D-Rep

– Equipment configuration and equipping with the management of the slave units:• ODU ND• ODU HP, as in ND mode as in HD one• Hardware memory key• Access NxE1 unit (coax/sub-D version)• BB NxE1 unit

– Configuration of the payload capacity:• 2xE1• 4xE1• 8xE1• 16xE1

– Configuration of the system parameters:• System activation command (ODU transmitter ON/OFF)• Enabling/disabling of the 2 Mbit/s tributaries, with possibility to work on a

single tributary or on all the tributaries at the same time.

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 thecontents 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-1SRA L XD (IDU Plug-in) - OMN911-380/02A0330 - Issue 1, October 2003


• Selection of the RF TX/RX frequencies• RF TX output power (fixed)• Frequency planing and RF channel spacing• Link identification code• Setting of the NE IP address• Enabling/disabling of the Security and setting of the passwords for the several

user classes• Setting of the modulation type (ND/HD)• Selection between the external D channel and the user one• Enabling/disabling of the embedded D channel with selection of the tributaty

and of the transport slot• Selection of the interface type for user channel (codirectional or

counterdirectional)• Power-up command of the ODU• Setting and reading of the static delay in protect configuration (1+1) according

to the detected dynamic delay

– System measurements:• Recording of the received RF field• Inner temperature of the ODU• Received power (RF RX) and transmitted one (RF TX)

– Alarm management:• Creation and return of the alarm resuming signals• Equipment diagnostics, by means of the single alarm roots subdivided

according to units and functions• Management of the alarm severity• Alarm return on connector• Transport of the station alarms (4 input lines for the alarms of the local station,

4 output lines for the alarms of the remote station)

– Software download:• Local/remote download of the equipment software build that contains the

entire unit software• Switching of the Controller unit banks• Alignment of the unit software

– SRA L interoperability:• Universal SRA L and SRAL XD (with ODU ND) mixed radio links (R channel)• SRA L and SRAL XD mixed link on D channel

– Network:• TCP/IP protocol on F interface and on LAN Q and V interfaces• IP SRA L compatibility on R channel and on D channel• RIPv1 protocol for transport of the routing information• Entry insertion/removal into the static routing tables

– Management system:• Local supervisory of NE and of the radio link via LCT• Remote supervisory of the NE’s into the radio network via NetViewer

– Management of the test loops-back on the tributaries

– Local and remote reset of the equipment controller

– Monitoring of the G.826 performance parameters

1-2SRA L XD (IDU Plug-in) - OMN

911-380/02A0330 - Issue 1, October 2003


– License management

– Management of the hardware memory key

– Management of the inventory data:• hardware data (unit PID data, user data)• software data

– Support of the TNMP protocol (as base protocol as extended one) as themanagement application protocol

1.3 Testing and WarrantyRefer to the contract clauses for the information concerning the equipment testing andwarranty.

1.4 ResponsibilityRefer to the contract clauses for the information concerning the responsibility.Then, please note that:

– the manufacturer declines all the responsibilities coming from an incorrect use ofthe equipment, from the use of not authorized pieces, components and circuits andfrom violations of the system software

– the responsibility for the application of the safety rules and of the usingprescriptions is at charge of the responsible technical personnel of the severalactivities. Such a responsible technical personnel has to ensure that the authorizedpersonnel is properly qualified for the execution of the requested activities and hasthe requested know-how.



1.5 Supplying conditions

The SRAL XD plug-in is provided on CD-ROM and it is comprised into the equipmentsupplying together with the LCT program.The equipment CD-ROM contains the following elements:

– the LCT program for the management of the radio link and/or of the local radioequipment

– the SuperTCP program for the download of the equipment software build

– the SRAL XD plug-in.

The SRAL XD plug-in can be included at customer’s request into the NetViewerCD-ROM.

1.6 Correlated ManualsFor additional information concerning the SRAL XD equipment, refer to the UMNManual for the installation and the start-up of the equipment.For additional information concerning the management systems, refer to the followingManuals:

– OMN Installation Manual and operating guide of LCT

– OMN Installation Manual and operating guide of NetViewer

– OMN Manual for NetViewer System Administrator.

It is foreseen a single plug-in for all the equipment of the SRAL XD group.

The plugs-in available on the NetViewer CD-ROM depend on the supplyingconditions of NetViewer.By default, the plugs-in for Cisco router and for the SNMP generic device arealways available.All the other plugs-in are provided at customer’s request only.


911-380/02A0330 - Issue 1, October 2003


1.7 List of the AbbreviationsA/D-RepAdd/Drop Repeater

AISAlarm Indication Signal

ALMAlarm

BBBase Band

BERBit Error Rate

CHChannel

CMDCommand

CONConnected

CRICritical

DCEData Communication Equipment

DEMDemodulator

DISDisconnected

DTEData Terminal Equipment

EEPROMElectrically Erasable Programmable Read Only Memory

EXTExternal

FDFrequency Diversity

FEBEFar End Block Error

FERFFar End Receive Failure

FTPFile Transfer Protocol

GNDGround



HDHigh Density

H/SHot-Standby

HWHardware

I/OInput/Output

IDIdentifier

IDUIndoor Unit

IFIntermediate Frequency

INInput

INDIndeterminate

IPInternet Protocol

LANLocal Area Network

LCTLocal Craft Terminal

LOSLoss of Frame Alignment

CONConnected

MAJMajor

MINMinor

MISMismatch

MODModulator

NDNormal Density

NENetwork Element

ODUOutdoor Unit


911-380/02A0330 - Issue 1, October 2003


OLLocal Oscillator

onLOn-Line

OMNOperating Manual

OUTOutput

OWOverflow

PCPersonal Computer

PWPower

RepRepeater

RFRadio Frequency

RIPRouting Information Protocol

RXReception

R/ORead Only

R/WRead/Write

SRA LSystem Radio Access at Low Capacity

SVRSoftware Version Release

SWSoftware

TCPTransmission Control Protocol

TFTransmission Frequency

TNMPTrivial Network Management Protocol

TMNTelecommunications Management Network

TRIBTributary



TXTransmission

UMNUser Manual

VCOVoltage Controlled Oscillator

WARWarning


911-380/02A0330 - Issue 1, October 2003

2 - PLUG-IN INSTALLATION

2 PLUG-IN INSTALLATION

2.1 GeneralThe SRAL XD plug-in implemens, in NetViewer/LCT, the Element Manager function forthe management of the equipment belonging to the SRAL XD group that contains alsothe SRAL XD with IDU Plug-in.

NetViewer/LCT can detect and then manage only the types of radio equipment and ofdevices for which it has been installed the relevant plug-in.The installation of a plug-in gets the capacity of NetViewer/LCT to manage thecorresponding equipment type.The setup of the plug-in automatically executes the copying of the plug-in files into thesame folder where it has been installed NetViewer/LCT.

2.2 Plug-In InstallationThe plug-in can be installed during the setup procedure of NetViewer/LCT or it can beadded/replaced later on; If it is added/replaced later on, the installation procedure is thefollowing one:

– Run the installation of the SRAL XD plug-in (“..\Disk1\setup.exe” file). If the systemdetects the presence of an already installed version of the plug-in, it requires forthe confirmation to continue the installation procedure and then toreplace/overwrite the already installed version.

– The system displays the Welcome window (Fig. 2.1).Click on Next to run the installation procedure.

– At the end of the installation procedure, the system displays the Setup Completewindow (Fig. 2.2). Click on Finish to close and to exit.

It is supplied a single SRAL XD plug-in that provides the support for all theequipment of the SRAL XD group.

For additional information concerning NetViewer/LCT, refer to the OMN Manual ofNetViewer/LCT.

After the installation of the plug-in, it is necessary to restart NetViewer/LCT, if it ison execution, in such a way to make effective the executed changes.



Fig. 2.1 Plug-in installation (1/2)

Fig. 2.2 Plug-in installation (2/2)


911-380/02A0330 - Issue 1, October 2003


2.3 Plug-In DisinstallationTo realize the plug-in disinstallation, it is not requested any special procedure; then,execute the typical disinstallation mode foreseen for an application program of MicrosoftWindows (Add/Remove Programs in Control Panel).



BLANK PAGE


911-380/02A0330 - Issue 1, October 2003

3 - DOWNLOAD OF THE EQUIPMENT SOFTWARE

3 DOWNLOAD OF THE EQUIPMENT SOFTWARE

3.1 GeneralThe equipment software is composed by the assembly (build software) of all the unitembedded software.The equipment units provided with embedded software on non volatile memory are thefollowing ones:

– Controller unit: embedded software

– FPGA module BB unit: firmware

– FPGA module Access unit : firmware

– ODU: embedded software.

The unit that manages the equipment operation if the Controller unit. It is a unit withmicroprocessor provided with two banks of non volatile memory over which it isuploaded the equipment software: an active bank and a standby one.The standby bank ensures the redundancy of the equipment software and it operates ifthe active bank fails; the system uses the standby bank also for the download of theequipment build software.The ODU is provided with a non volatile memory bank over which the system uploadsonly the corresponding embedded unit software.Into the FPGA modules of the Access and BB units, the system uploads the firmware atthe starting-up of the Controller unit.The Controller unit and the ODU are equipped with already uploaded embeddedsoftware.From NetViewer/LCT, the user can, via FTP (application program of the TCP/IP stack),update or upload newly on the Controller unit, the equipment build sofware.The download procedure via FTP uploads the software build on the standby bank of theController unit only; the system keeps running the pre-existing software on the activebank of the Controller unit and on the other units.

To make active the new build software, it is necessary to execute the switching of thebanks on the Controller unit.The switching operation runs the new version of the Controller unit software; on theother units, the system keeps on execution the pre-existing software.The Controller unit executes the comparison between the versions of the unit softwarepresent into the build software uploaded over the active bank and the versions of theunit software currently on progress, signalling the possible misalignment situations.From NetViewer/LCT, the user can, by means of manual command, execute the

The download procedure via FTP does not cause any interruption of theController unit operation, such a unit remains always On Line.



software alignment of every unit. Such a procedure consists of the download operationof the unit software from the active bank of the Controller unit to the unit memory. It runsthe new version of the unit software.The download of the build software can be executed as through local mode as throughremote one:

– local download: from LCT (on F, Q, and V interface)

– remote download: from LCT and from NetViewer.In case of download from LCT, each time that the system executes the switchingof the memory bank on the Controller unit, the user has to run again the TNMPconnection and also to deactivate the dial-up one with the equipment and later onto restore it.

In a radio link, to prevent the loss of the remote terminal, it is necessary to executethe bank switching command before on the remote terminal and later on the localone.

It is advisable to use the V interface for the local download of the build softwarefrom LCT.


911-380/02A0330 - Issue 1, October 2003


3.2 Download via FTP of the Equipment Build Software

– Run the Element Manager (NetViewer/LCT).

– From Element Manager, execute the login, with Admin user class, to theSRA L XD equipment over which the user wants to execute the downloadprocedure.

– Run the FTP Client program, selecting Status and Config > Software > FTPTransfer into the equipment operating menu (Fig. 3.1); the system displays theFTP window (Fig. 3.2).

Fig. 3.1 Download procedure via FTP (1/8)


– Select the Connect option into the Connect menu; the system displays theConnect window (Fig. 3.3).

To be able to execute the download procedure of the build software via FTP, thePC with the file to be transferred has to be powered up and connected into thenetwork with the equipment.




– Fill in, into the Hostname field, the IP address of the SRAL XD equipment overwhich the user wants to execute the download procedure and then, click on OK;the system displays the Connection Information window (Fig. 3.4).



911-380/02A0330 - Issue 1, October 2003


– Set the following parameters into the Connection Information window:• Username: admin• Password: sysmanagerand click on OK to activate the connection via FTP with the equipment Controllerunit.

– Select Preferences into the Options menu of the FTP window (Fig. 3.5); thesystem opens the FTP Preferences window (Fig. 3.6). Into the List View tab,select the Don’t Use Extra Flags radio button.


Using the FTP default settings, also if the system has correctly finished thedownload procedure, it ends displaying an error message “Cannot get remotedirectory listing”. To prevent such a situation, it is necessary to select the option“Don’t Use Extra Flags” nel tab “List View”.




– Into the Local window (Fig. 3.7), select the drive and the directory where there isthe file of the new build software to be uploded on the Controller unit; then selectthe file to be transferred. The file must have as name “application.pec”.When the user selects the file to be transferred, the system activates thepush-buttons for the file management.


911-380/02A0330 - Issue 1, October 2003



– Into the Transfer section (Fig. 3.8), select Binary as transfer mode.

– Force the start-up of the download operation pressing the Copy push-button(Fig. 3.8). If into the standby bank of the Controller unit it has already beenuploaded a build software, the system requires for the confirmation of theoverwriting operation relevant to the existing “application.pec” file. After thestart-up of the download procedure, the system displays a status bar that showsthe progress status of the download operation (lower part of the window).

– At the end of the operation, the new version of the build software has been uplodedon the standby bank of the Controller unit (Fig. 3.8).The contents of the standby bank are displayed into the Files filed of the Remotesection into the FTP window.To run the versions of the software present into the new equipment build software,the user has to execute the switching of the banks on the Controller unit and thento execute the alignment of the unit software (par. 3.3).





911-380/02A0330 - Issue 1, October 2003


3.3 Switching of the Banks and Alignment of the Unit Software– At the end of the download procedure, via FTP, of the new version relevant to the

equipment build sofware (par. 3.2), open the window for the management of thebanks (Fig. 3.10), selecting Status and Config > Software > Software Bank intothe equipment operating menu (Fig. 3.9).

– To make active the standby bank and to upload the new version of the buildsoftware, force the switching of the banks on the Controller unit, clicking on SwitchBanks (Fig. 3.10).

– Now on the Controller unit it is on execution the new software version, while on theother units the system keeps on execution the pre-existing software; for the otherunits, the system displays the currently on execution software version into the RunVersion field (Fig. 3.10) and not the one present into the build software uploadedon the active bank of the Controller unit.

– The Controller unit executes the comparison between the versions of the unitsoftware present into the build uploaded on the active bank and the versions of theunit software currently on execution; the system points out the software alignmentsignal of every unit into the Status field (Fig. 3.10): • aligned software: the version of the software running on the unit is the same

one of the unit software present into the build uploaded on the active bank ofthe Controller unit

• misaligned software: the version of the software running on the unit is differentfrom the version of the unit software present into the build uploaded on theactive bank of the Controller unit.

– Now, through a manual command (Download push-buttons of the Alignmentfield), the user can update the software of the units with misaligned software. Thealignment command runs the version of the unit software present into the buildcurrently uploaded on the active bank of the Controller unit; the alignmentprocedure consist of executing the download of the unit software from the activebank of the Controller unit to the memory of the unit.

The switching command of the banks causes a reset of the Controller unit, withthe temporary loss of the equipment from NetViewer/LCT and without payloadloss. In case of connection through F interface, it is necessary to run again fromLCT the dial-up connection.



– The updating of the equipment software is finished when all the units has thesoftware aligned.

Fig. 3.9 Software Bank command

The alignment operation of the unit software can cause a payload loss:– Not protected configuration

• Alignment of the ODU embedded softwareIt is present a payload loss for approximately 1 minute due to the ODUstart-up.

• Alignment of the BB unit firmwareIt is present a payload loss for approximately 5 seconds.

• Alignment of the Access unit firmwareIt is present a payload loss for approximately 3 seconds.

– Protected configuration• Alignment of the BB 1 unit firmware and/or of the ODU 1 embedded

softwareTo reduce at the minimum level the payload loss, it is necessary (beforestarting the alignment procedure) to force the protection on BB 2 and onRX 2 channel; in such a way the BB 2 and the ODU 2 units on which thesystem has not to execute the download operation are on service.Now the user can execute the download of the firmware relevant to theBB 1 unit and/or if the ODU 1 embedded software embedded insequence.The system has a maximum payload loss approximately for 2 secondsdue to the switching operation.

• Alignment of the BB 2 unit firmware and/or of the ODU 2 embeddedsoftwareTo reduce at the minimum level the payload loss, it is necessary (beforestarting the alignment procedure) to force the protection on BB 1 and onRX 1 channel; in such a way the BB 1 and the ODU 1 units on which thesystem has not to execute the download operation are on service.Now the user can execute the download of the firmware relevant to theBB 2 unit and/or if the ODU 2 embedded software embedded insequence.The system has a maximum payload loss approximately for 2 secondsdue to the switching operation.


Therefore, in protected configuration, for the complete download on all theunits, the system has a maximum payload loss equal to 7 seconds.


911-380/02A0330 - Issue 1, October 2003


Fig. 3.10 Equipment Software Bank window

System Type (1+0)

System Type 2x(1+0), (1+1) H/S, (1+1) FD, A/D-Rep



BLANK PAGE


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4 OPERATING GUIDE

4.1 GeneralThe management via software of the SRA L XD can be executed as by NetViewer as byLCT.NetViewer allows the supervisory of radio equipment networks while LCT allows themanagement of the equipment relevant to a radio link and/or of the local equipment.The SRAL XD plug-in adds to NetViewer/LCT, the capacity to manage all the equipmentbelonging to the SRAL XD group.

4.2 Software FunctionsThe main aspects of the equipment management via software are the following ones:

– Plug-in functions

– Memory hardware key and operating status of the Controller

– License

– Unit software

– Security

– Unit connection status

4.2.1 Plug-in functions

The SRA L XD plug-in supports the following functions:

– System configurations (System Type):• Single terminal: (1+0)• Double terminal: 2x(1+0)• Terminal with (1+1) protection at frequrncy diversity: (1+1) FD• Terminale with (1+1) protection Hot-Standby: (1+1) H/S• Repeater with Add/Drop possibility of tributaries: A/D-Rep

– Configuration and equipment equipping with management of the slave units:• ODU ND• ODU HP, as in ND mode as in HD one

For the using modes of NetViewer/LCT, refer to the relevant operating guide.

The SRAL XD supports, as management application protocol, as the base TNMPprotocol as the extended TNMP one.


4 - OPERATING GUIDE

• hardware memory key• NxE1 Access unit (coax/sub-D version)• BB NxE1 unit

– Configuration of the payload capacity:• 2xE1• 4xE1• 8xE1• 16xE1

– Configuration of the system parameters:• System activation command (ODU transmitter ON/OFF)• Enabling/disabling of the 2 Mbit/s tributaries, with the possibility to work on a

single tributary or on all the tributaries at the same time• Selection of the RF TX/RX frequencies• RF TX output power • Frequency plan and RF channel spacing • Link identification code• Setting of the NE IP address• Enabling/disabling of the Security and setting of the passwords for the

different user classes• Setting of the modulation type (ND/HD)• Selection between external D channel and user channel• Enabling/disabling of the embedded D channel, with selection of tributary and

transport slot • Selection of the interface type for user channel (codirectional or

counterdirectional)• Power-up command of the ODU• Setting and reading of the static delay in (1+1) protect configuration according

to the detected dynamic delay

– System measurements:• Recording of the received field• Inner temperature of the ODU• Received power (RF RX) and transmitted one (RF TX)

– Alarm management:• Creation and return of the alarm resuming signals• Equipment diagnostics, through the single alarm roots subdivided according

to units and functions• Management of the alarm severity• Alarm return on connector• Transport of the station alarms (4 input lines for alarms of the local station, 4

output lines for the alarms of the remote station)

– Software download:• Local/remote download of the equipment software build that contains all the

unit software• Switching of the banks relevant to the Controller unit• Alignment of the unit software

– SRA L interoperability:• Universal SRA L and SRAL XD (with ODU ND) mixed radio links (R channel)• SRA L and SRAL XD mixed link on D channel


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

– Network:• TCP/IP protocol on F interface and on LAN Q and V interfaces• SRA L compatibility on R channel and on D channel• RIPv1 protocol for transport of the routing information• Entry insertion/extraction into the static routing tables

– Management system:• Local supervisory of NE and of the radio link via LCT• Remote supervisory of the NE’s in the radio network via NetViewer

– Management of the loops-back for the test on the tributaries

– Local and remote reset locale of the equipment controller

– Monitoring of the G.826 performance parameters

– Management of the licenses

– Management of the hardware memory key

– Management of the inventory data:• hardware data (unit PID data, user data)• software data

– Support of the TNMP protocol (as base protocol as extended one) as managementapplication protocol

4.2.2 Memory hardware key and operating status of the Controller

The hardware memory key has the following characteristics:

– it is the backup key of the equipment configuration, all the operating and systemparameters are memorized into the EEPROM memory of the hardware key

– after the start-up, it is strictly coupled with the equipment Controller (the Controllerstores the hardware Key Serial Number)

– it contains the license (par. 4.2.3); each hardware key delivered with the equipmentcontains the customer ordered license.

Management of the hardware key

At the starting-up, the Controller checks that the hardware key is inserted and that it iscoherent with the equipment type:

– if the check is successfully executed, the system upload into the memory theequipment configuration present into the hardware key and the Controllermemorizes the serial number of the hardware key; the Controller switches to theRUN/SET status

– if the check gets a negative result, it is present the condition of hardware keymismatch; the Controller switches to the IDLE status.

The extraction of the hardware key is allowed only in the two following situations:

– Replacement/repairing of IDU out of orderIn such a case, it is necessary to execute the following operations:• remove the hardware key, that contains the equipment configuration, before

executing the replacement/repairing of the IDU


4 - OPERATING GUIDE

• insert again the hardware key, after the replacement/repair of the IDU, beforestarting-up again the equipment.

In such a way the system restores the equipment configuration present before thecorrective maintenance intervention.

– Replacement of hardware key out of orderIn such a case, it is necessary to execute the following operations:• do not power off the equipment, to prevent the loosing of the correct

equipment configuration and license (if the user turns off the equipment, thesystem looses the current configurations and it is not possible longer torecover them because the hardware key is out of order)

• require to the service for the maintenance hardware key; such a key has beenspecifically foreseen for the execution of corrective maintenanceinterventions on the hardware key

• insert the maintenance hardware key, in such a way to save on such a keythe current equipment configuration and the license.

Controller statuses

The equipment Controller can get one of the following operating statuses:

– RUN/SETThe inner (towards the slaves) and external interfaces are enabled; the system canexecute the configuration operations (within the limits foreseen by the license andby the user class). This is the normal functioning condition.

– RUN/NO SETThe inner (towards the slaves) and external interfaces are enabled but the user canexecute reading only operations (within the limits foreseen by the license). Thesubject situation is present when the equipment is turned on and the user extractsthe memory key or there is an alarm condition on the hardware key or with havinginserted the hardware key of another equipment.

– IDLEThe inner interfaces (towards the slaves) are disabled while the external ones areenabled (the system does not displays queries of the slaves). In the subjectcondition, the F interface remains on operating status to allow the download of theequipment software. The subject situation is present when the user starts up theequipment without having inserted before the hardware key or with having thehardware key of another equipment.

Diagnostics for the hardware key

The system provides for the hardware key, via software, the following diagnostic signals:

– Disconnected status signalIt points out the condition of disconnected hardware key; the system detects thephysical availability of the hardware key through polling (devoted sense pin). If thecondition of disconnected hardware key is present at the equipment starting up. theController switches to the IDLE status; vice versa, if such a condition appears withthe equipment started up, the Controller switches on the RUN/NO SET status.

– Mismatch status signalThe hardware key is not coherent with the equipment type. The subject conditionis present when the user inserts by mistake the hardware key relevant to a differentequipment type. If at the starting up of the equipment it is present the condition of


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

not coherent hardware key, the Controller switches to the IDLE status; vice versa,if such a condition appears when the equipment has already been turned on, theController switches to the RUN/NO SET status.

– Key E2prom Fail AlarmThe EEPROM of the hardware key is out of order; in the subject situation, thehardware key can not be accessed.If the Key E2prom Fail alarm is present at the equipment starting up, the Controllerswitches to the IDLE status; vice versa, if the alarm appears when the equipmenthas already been turned on, the Controller switches to the RUN/NO SET status.

– Alignment Fail AlarmThe serial number of the hardware key is different from the one memorized into theController at the switch-on. When the system displays the Alignment Fail Alarm,the Controller switches to the RUN/NO SET status. The subject condition can bepresent only when the equipment has been started up (e.g.: when the equipmentis turned on, the user extracts the hardware key presebt at the power-on time andinserts an hardware key with different serial number.

4.2.3 License

The license released to the user is not relevant to the software version only, but also tothe system configurations and to the payload capacities defined at the supply time. Theprogram functions relevant to the system configurations and to the payload capacitiesnot foreseen by the supply are disabled. It is necessary to require for a new license keyto be able to manage the function disabled submitted to the license.The license key and all the information relevant to the system configurations arememorized into the hardware key.The functions submitted to the license are the following ones:

– System Type:• (1+0)• All (it comprises all the System Types that foresee the equipping of two BB

units and of two ODU’s )

– Payload capacity:• 4xE1• 8xE1• 16xE1

– Density of the RF radio channel:• ND• HD.

The factory default license foresees the following functions:

– System Type: (1+0)

– payload capacity: 4xE1

– Density of the RF radio channel: ND.


4 - OPERATING GUIDE

4.2.4 Unit software

The equipment units provided with embedded software on non volatile memory are thefollowing ones:

– Controller unit: embedded software

– Slave unit:• FPGA module BB unit: firmware• FPGA module Access unit: firmware• ODU: embedded software.

The unit that manages the equipment functioning is the Controller unit. It is a unit withmicroprocessor provided with two banks of non volatile memory, over which the systemuploads the equipment software: an active bank and a standby one.The equipment software is composed by the assembly (build software) of all the unitsoftware (embedded and/or firmware).The standby bank ensures the redundancy of the equipment software and it works if theactive bank is out of order; the system uses the standby bank also for the download ofthe equipment build software.The ODU is provided with a bank of non volatile memory over which the system uploadsthe software embedded for the unit.The Controller unit and the ODU are provided with already uploaded embeddedsoftware.Into the FPGA modules of the Access and BB units, the system uploads the firmware atthe starting-up of the Controller unit.From NetViewer/LCT, the user can update or upload again on the Controller unit, viaFTP, the equipment build sofware and control the switching of the banks relevant to theController unit.The Controller unit executes the comparison between the versions of the unit softwarepresent into the build software uploaded on the active bank and the versions of the unitsoftware currently on progress, pointing out possible misalignment situations.From NetViewer/LCT, the user can, through manual command, execute the softwarealignment of each unit.

4.2.5 Security

The plug-in allows enabling/disabling the equipment Security, that is the possibility toaccess to the equipment only for authorized users; each user is characterized by a userclass 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 theequipment 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 theexception of the functions reserved to the Admin user class

– Admin: access to the all the functions as in reading as in writing mode.

In case of equipment Security disabled, in NetViewer/LCT, it is available also theAnonymous user class, that does not require for a password and has the sameprivileges of the Read Write class.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

It is possible to set/change, through the operating menu, the configuration of theSecurity 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

– switching of the Controller memory banks

– alignment of the unit software

– reset of the Controller

– configuration of the NE date and time

– configuration of the Security

– copy/paste operation of the NE configuration file.

4.2.6 Unit connection status

The plug-in reports the connection status with the Controller unit of each slave one.

– Disconnected

– Connected

– On Line

– Mismatch.

In the Disconnected status, the system considers the slave unit as extracted (the systemgets the same message also if the unit is inserted into the equipment but it is not able tocommunicate correctly with the Controller unit).The Connected status identifies the connection and control starting phase executed bythe Controller unit; it is an intermediate temporary status.In the Mismatch status, the slave unit is present into the slot and it communicates withthe Controller unit, but the unit type does not correspond to the one foreseen into thecurrent equipment configuration or the version of the unit software does not support therequested functioning mode.The On Line status is the correct functioning one of the slave unit: the unitcommunicates correctly with the Controller unit, the insertion slot and the unit type arethe ones foreseen into the current equipment configuration and the version of the unitsoftware supports the requested functioning mode.The Controller unit automatically updates the signal of the connection statuses while theuser executes, via software, the equipping setting of the units.It is possible to have some errors due to the misalignment between the equipping statusset via software by the user and the equipment hardware.

Only one user at a time can access the equipment using writing privileges (Adminor Read Write user class).


4 - OPERATING GUIDE

4.3 NE Profile UploadingIn NetViewer/LCT, to activate the Element Manager functions, it is necessary to uploadthe equipment profile and then to access to the equipment (NE opening).The map (Fig. 4.1) represents the graphical interface of NetViewer/LCT for the accessto the radio equipment.At the map opening, NetViewer/LCT tries to connect itself with all the equipment recalledinto the map itself; for each equipment the connection phase is executed in the followingway:

– if it is detected a communication error, the system displays a generic NE icon withgrey background color (unvoluntary disabling status)

– if the connection is successfully executed, the program executes the login and theuploading of the equipment profile and it displays the icon that identifies theequipment type.

When the profile has been uploaded, it is necessary to open the NE (Open commandfrom NetViewer/LCT) to upload the operating menu for the equipment control andconfiguration.

Fig. 4.1 Example of map with SRA L XD

In case of connection towards an equipment of which it has not been installed therelevant plug-in, the system displays the “unknown” equipment icon; theequipment is not supported.

In NetViewer, the background color of the equipment name points out thesummarized status of the equipment itself, that coincides with the alarm with thehighest severity. Such a function is not supported by LCT.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.4 Structure of the Operating MenuThe user can access to the equipment operating menu clicking through the R.H.push-button of the mouse on the equipment icon into the NetViewer/LCT map.The equipment menu, pointed out by the name or by the IP address of the NE, containsthe following elements:

– a pre-defined part that depends by the SVR of NetViewer/LCT and it does notdepends by the equipment type (NE)

– a dynamic part, that contains the control and configuration operating menu. Thesystem uploads such a part at the NE opening only (Open command fromNetViewer/LCT).

The SRA L XD operating menu (Fig. 4.2) is composed by a series of sub-menus incascade (Tab. 4.1) and it is provided with the following options:

– Status and Config Menu: it allows checking the current functioning status of theequipment and configuring, according to the available hardware and using license,the system type and the system, network and operating parameters of theequipment.

– Alarms Menu: it allows checking the status of the equipment alarms and detectingthe cause of a possible malfunctioning.

– Measurements Menu: it allows executing the reading of the current values of theRF TX - RX power and the recording on file of the received RF field.

– Performance Menu: it allows analyzing and detecting on file the performance dataof the equipment.

– Inventory Menu: it allows accessing to the inventory data, to read them or to writepossible notes (e.g.: installation date, malfunctioning type, etc.) or to execute theirdownload operation on file.

– Security Menu: it allows enabling/disabling the equipment Security and setting thepasswords for the different user classes.

Into the equipment operating menu, there are also the following NE applications ofNetViewer/LCT:

– History Report: function that provides a report with all the events successed on theequipment

– Alarm List: function that provides the list of all the alarm currently activated on theequipment.

For the description of the commands relevant to the pre-defined part of theequipment menu, refer to the operating guide of NetViewer/LCT.

The NE applications of NetViewer and of LCT have different characteristics andoperating modes.

For the description of the NE applications, refer to the operating guide ofNetViewer/LCT.


4 - OPERATING GUIDE

Fig. 4.2 SRA L XD operating menu

1. In System Type (1+0), (1+1) H/S, (1+1) FD, it is present only a System sub-menu (without the indication of thesystem number)

2. In System Type (1+0), it is present only a RF RX Power sub-menu (without the indication of the system number)

Tab. 4.1 Structure of the SRA L XD operating menu

Main Menu Sub-menu/

Status and Config Equipment

Software Software Bank

FTP Transfer

Controller Reset

Network IP Address

NE Parameters

Static Routing Table 1...10

Static Routing Table 11...20

Date and Time

Alarms Physical and Functional

Station

Measurements View

RF RX Power 12

RF RX Power 22

Performance View

Software System 11 B1 Byte

System 21 B1 Byte

Summary

Inventory

Security

Operating menu(Dynamic Part)

Pre-definedPart

NE Applications


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.5 Status and Config MenuThe Status and Config menu allows checking the functioning status of the equipmentand configuring, according to the available hardware and license, all the system,operating and network parameters.The Status and Config menu (Fig. 4.3) contains the following options:

– Equipment: Equipment configuration

– Software: Management of the equipment software

– Network: Configuration of the network parameters

– Date and Time: Configuration of NE date and time

Fig. 4.3 Status and Config menu

4.5.1 Equipment configuration

The Equipment option into the Status and Config menu (Fig. 4.3) displays theEquipment Status & Configuration window (Fig. 4.4), that represents the basewindow for the equipment management.The Equipment Status & Configuration window provides the access, through properpush-buttons, to the following configuration windows:

– System configuration: System push-button

– Configuration of the external interfaces: Ext Interfaces push-button

– Configuration of the protection: Protection push-button

– Test configuration: Testing push-button

– Updating of the license: License Upgrade push-button

– Uploading/memorization of the NE configuration file: Copy Config and PasteConfig push-buttons

– ODU configuration: Configure push-button present into the ODU box.

The Equipment Status & Configuration window resumes the current functioningstatus of the equipment, through the displaying of a functional layout of the equipmentand of status and alarm signals.

The functional layout of the equipment, displayed into the “Equipment Status &Configuration” window, depends on the System Type:– in System Type (1+0), the system displays the equipment provided with a BB

unit and a ODU one.– into the other System Types, the system displays the equipment provided

with two BB units (identified with BB 1 and BB 2) and two ODU’s (identifiedwith ODU 1 and ODU 2).


4 - OPERATING GUIDE

Fig. 4.4 Equipment Status & Configuration window

System Type 2x(1+0), A/D-Rep

System Type (1+1) H/S, (1+1) FD

The “Protection” push-button is available only in case of System Type (1+1) H/Sand (1+1) FD.The “Copy Config” and “Paste Config” push-buttons are activated only in case oflogin with administrator privileges (Admin user class).

In case of login with reading only privileges (Read Only user class), the settingfields of the configuration windows are all reading only ones.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

System Type (1+0)

The Equipment Status & Configuration window provides the following status andalarm signals:

Status signals

– Unit connection statusFor each equipment unit (comprised the hardware key), the system reports thecurrent connection status; the possible displayings are the following ones:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch

– Equipping status of the BB unitsFor each provided BB unit, the system points out the current equipping status, thepossible displayings are the following ones:• Unequipped: not equipped units• NxE1: BB unit of NxE1 type

– ODU equipping statusFor each equipped ODU, the system points out the current equipping status; thepossible options are the following ones:• Unequipped: unequipped ODU• HD/ND: ODU of HP type (ODU that can work as in Normal Density as in High

Density)• ND: ODU of ND type (ODU that can work in Normal Density only)

– Type of tributary interfaceInto the Access unit box, the system points out the characteristics of the equippedtributary physical interface.

– System TypeIn the System Type field, the system points out the System Type currently set forthe equipment.

– Payload capacityFor each system, into the System Capacity field, it is pointed out the currently setsystem payload capacity.


4 - OPERATING GUIDE

Signals and alarm messages

– Unit fail alarmFor each equipment unit (included the hardware key also), the system provides asignalling LED for the unit resuming alarm (condition of unit out of order).In normal conditions, the LED is turned on with green color, while in alarmcondition, it is turned on with red color.

– Resuming signals of the alarm severityInto the Severity Alarms section, the system points out, through a LED, thecurrent status of the resuming signals of the alarm severity:• LED turned on with green color: resuming signal not activated• LED turned on with red color: resuming signal activated (the system displays

also the symbol “!” in front of the signalling code).The system groups the alarms according to the following severity resumingsignals:• 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 for which the user

has to execute 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 toexecute an action for an additional diagnosis (if it is necessary) and the userhas to correct the trouble to prevent that it can cause the most serious fails.

• Indeterminate: alarm situation with indeterminate character that does notrequire for the executuion of any corrective action or diagnosis.

– Alarm for not congruent configurationIf the equipment configuration set via software it is a not congruent one with theactual System type requirements, the system displays the following alarm signal:! Configuration Not Congruent with HW

– Signal of manual operation on progressIf on the equipment the user has activated a manual forcing and/or test control, thesystem displays the following signal:! Manual Operation on EquipmentThe possible manual operations are the following ones:• forcing on line of the BB unit• forcing on line of the RX channel• local loop on tributary• remote loop on tributary• temporary system turning-off.

– Operating status of the ControllerThe system displays an alarm signal if the Controller is into an operating statuswhere the user can not execute configuration operations on the equipment(par. 4.2.2):• with Controller into a RUN/NO SET status, the system displays the following

signal:! No Setting Mode

• with Controller in IDLE status, the system displays the following signal:! IDLE Mode


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.5.1.1 System configuration

To set the system parameters, click on the System push-button into the EquipmentStatus & Configuration window (Fig. 4.4); the system displays the SystemConfiguration window (Fig. 4.5), where the user can check and execute the followingsystem configurations:

– System Type configuration

– System activation option (ODU transmitter power on)

– ODU power supply option

– Configuration of the system payload capacity

– Configuration of the parameters for the link identification

– ODU type configuration

Into the System Configuration window, the system resumes the current configurationstatus of the equipment, through the displaying of a functional layout of the equipmentand through the status and alarm signals.

The functional layout of the equipment is displayed into the “Equipment Status &Configuration” window and it depends on the System Type:– in System Type (1+0), the system displays the equipment equipped with a BB

unit and a ODU– in the other System Types, the system displays the equipment equipped with

two BB units (identified with BB 1 and BB 2) and two ODU (identified withODU 1 and ODU 2).


4 - OPERATING GUIDE

Fig. 4.5 System Configuration window



System Type (1+0)


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Into the System Configuration window, there are the following status and alarmsignals:

Status signals and system parameters

– Unit connection statusFor each equipment unit (included the hardware key), the program points out theconnection current status; the possible displayings are the following ones:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch

– Equipping status of the BB units• Unequipped: unequipped unit• NxE1: BB unit of NxE1 type

– Type of tributary interfaceInto the box of the Access unit, the program points out the characteristics of theequipped tributary physical interface.

– Payload capacityFor each system, on the side of the corresponding System Capacity push-button,the program points out the currently set payload capacity.

Alarm signals and messages

– Alarm for not congruent configurationIf the equipment configuration set via software is not congruent with the actualSystem Type requirements, the program displays the following alarm signal:! Configuration Not Congruent with HW

– Signal of manual operation on progressIf on the equipment it is activated a manual forcing and/or test command, theprogram displays the following signal:! Manual Operation on Equipment The possible manual operations are the following ones:• forcing on line of the BB unit• forcing on line of the RX channel• local loop on tributary• remote loop on tributary• temporary system turning-off.

– Payload capacity not alignedIf for a system, for any kind of reason (System Type change, replacement of a unit,ODU temporary disconnection, ...), it is present an incongruence conditionbetween the current configurations of the tributary interface, of the BB payloadcapacity and of the ODU payload one, the program displays the following warningmessage:

CAPACITY NOT ALIGNED ! In such a case, the user has to reset or to confirm again the system payloadcapacity (par. 4.5.1.1.4).


4 - OPERATING GUIDE

– Operating status of the ControllerThe program displays an alarm signal if the Controller is in an operating status thatdoes not allow the execution of configuration operations on the equipment(par. 4.2.2):• with Controller in RUN/NO SET status, the program displays the following


• with Controller in IDLE status, the program displays the following signal:! IDLE Mode

4.5.1.1.1 System Type configuration

According to the equipped hardware and to the current license (par. 4.2.3), for theequipment it is possible to have the following system configurations (System Type):

– Single terminal

– Double terminal

– Terminal with (1+1) protection at frequency diversity

– Terminal with (1+1) protection Hot-Standby

– Repeater with tributary Add/Drop possibility.

The configuration procedure of the System Type is the following one:

– click twice on the System Type field, the system displays the configuration window

– select the desired System Type; the possible options are the following ones:• (1+0): Single Terminal• 2 x (1+0): Double terminal • (1+1) FD: Terminal with (1+1) protection at frequency diversity• (1+1) H/S: Terminal with (1+1) protection Hot-Standby• Add/Drop - Rep: Repeater with tributary Add/Drop possibility

– confirm the setting clicking on OK.

Fig. 4.6 System Type Configuration window


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.5.1.1.2 System activation option

For each radio system, it is available the manual command for the system consisting onthe switch on/off of the ODU transmitter The configuration procedure is the followingone:

– click twice on the System Activation field of the desired system; the programdisplays the configuration window

– select the system activation command (On) or the deactivation one (Off) and thenconfirm the setting clicking on OK.

Fig. 4.7 System activation configuration window

4.5.1.1.3 ODU power supply option

For each ODU, it is available the power supply manual command. The configurationprocedure is the following one:

– click twice on the ODU Power UP field of the desired ODU; the program displaysthe configuration window

– enable (Enabled) or disable (Disabled) the ODU power supply and then confirmthe setting clicking on OK.

Fig. 4.8 ODU power supply configuration window


4 - OPERATING GUIDE

4.5.1.1.4 Configuration of the system payload capacity

The available payload capacities depend on the license (par. 4.2.3), on the SystemType and on the equipment hardware. Into the System Configuration window(Fig. 4.5), click twice on the System Capacity push-button to display the configurationwindow of the payload capacity (Fig. 4.9); the program displays the window in readingonly mode.To set the payload capacity, switch to the read/write mode (Fig. 4.10), clicking onModify; the program switches the push-button name from Modify to OK.

Fig. 4.9 Capacity Setting window (reading only mode)

Fig. 4.10 Capacity Setting window (read/write mode)

The configuration procedure of the payload capacity is the following one:

– click twice on the System Capacity field, the program displays the configurationwindow

– select the desired payload capacity among the available ones


Fig. 4.11 Configuration window of the payload capacity

The following table points out all the payload capacities supported into the severalSystem Types according to the ODU RF density.

In case of System Type H/S and (1+1) FD, it is available only one “SystemCapacity” push-button, because the two systems must necessarily have the samepayload capacity.In case of System Type 2x(1+0) and A/D-Rep, the user can set different payloadcapacities on the two radio systems.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Into the Capacity Setting window, the program displays an alarm signal if the Controlleris into an operating status that does not allow the execution of configuration operationson the equipment (par. 4.2.2):

– with Controller in RUN/NO SET status, the program displays the following signal:! No Setting Mode

– with Controller in IDLE status, the progam displays the following signal:! IDLE Mode

4.5.1.1.5 Configuration of the parameters for the link identification

For each radio system, it is foreseen a radio link identification control; for such anaim, the program insert a link ID into the radio frame of each system.Into the System Configuration window (Fig. 4.5), click twice on the Link IDpush-button to open the configuration window of the link identification parameters(Fig. 4.12).

Fig. 4.12 Link Identification Parameters window

Tab. 4.2 Supported payload capacities

System Type RF DensityPayload capacity

2xE1 4xE1 8xE1 16xE1

(1+0)ND � � � �

HD � �

2x(1+0)ND � � �

HD �

(1+1) H/SND � � � �

HD � �

(1+1) FDND � � � �

HD � �

A/D-RepND � � � �

HD � �

In case of System Type (1+0), the “Link ID” push-button is not present, becausethe configuration fields of the link identification parameters (“Link Id CodeInserted” and “Link Id Code Expected”) are directly available into the “SystemConfiguration” window.

In case of System (1+1) H/S and (1+1) FD, the user has to set the same link ID forboth the systems (System 1 and System 2).


4 - OPERATING GUIDE

For each radio system, the program foresees the two following link identificationparameters:

– Link Id Code Inserted It allows setting the identification code (ID) inserted into the radio frame andtrasmitted to the remote system.The subject ID must be equal to the one that the remote system has to receive(Link Id Code Expected parameter of the remote system).The configurationprocedure is the following one:• click twice on the Link Id Code Inserted field, the program displays the

configuration window• insert the value of the link ID to be inserted into the radio frame, such a value

has to be comprised between 1 and 15• confirm the setting clicking on OK.

Fig. 4.13 Link Id Code Inserted configuration window

– Link Id Code Expected It allows setting the identification code (ID) that the local system has to receive fromthe remote system.The subject ID has to be equal to the one that the remote system inserts into theradio frame (Link Id Code Inserted parameter of the remote system). Theconfiguration procedure is the following one:• click twice on the Link Id Code Expected field, the program displays the

configuration window• insert the value of the expected link ID, such a value has to be comprised

between 1 and 15• confirm the setting clicking on OK.

Fig. 4.14 Link Id Code Expected configuration window

Into the Link Identification Parameters window, the system displays an alarm signal ifthe Controller is into an operating status that does not allow the execution ofconfiguration operations on the equipment (par. 4.2.2):

– with Controller in RUN/NO SET status, the program displays the following signal:! No Setting Mode

– with Controller in IDLE status, the program displays the following signal:! IDLE Mode


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.5.1.1.6 ODU type configuration

The system foresees two ODU types:

– ODU ND: ODU with the capacity to work in Normal Density only

– ODU HP: ODU with the capacity to work as in Normal Density as in High Density

The configuration procedure is the following one:

– click twice on the configuration field of the ODU; the program displays theconfiguration window

– select the ODU type; the possible options are the following ones:

– HD/ND: ODU with the capacity to work as in HD as in ND

– ND: ODU with the capacity to work in ND only


Fig. 4.15 ODU type configuration window

Mixed radio link SRAL XD - SRA L are possible only with ND type ODU’s.


4 - OPERATING GUIDE

4.5.1.2 Configuration of the external interfaces

To configure the external interfaces, click on the Ext Interfaces push-button into theEquipment Status & Configuration window (Fig. 4.4); the system displays theExternal Interfaces Setting window (Fig. 4.16), where the user can check and executethe following setting operations:

– Configuration of the Access unit interfaces

– Configuration of the Controller unit interfaces

– Configuration of the BB unit tributaries

Fig. 4.16 External Interfaces Setting window

System Type 2x(1+0)

System Type A/D-Rep


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE


System Type (1+0)

Into the External Interfaces Setting window, the program displays an alarm signal ifthe Controller unit is into an operating status that does not allow the execution of settingoperations on the equipment (par. 4.2.2):

– with Controller in RUN/NO SET status, the system displays the following signal:! No Setting Mode

– with Controller in IDLE status, the system displays the following signal:! IDLE Mode

4.5.1.2.1 Configuration of the Access unit interfaces

Into the Access section of the External Interfaces Setting window (Fig. 4.16), the usercan execute the following setting operations:

– Configuration of the User/D-Ext interfaces (User/D-Ext 1 and User/D-Ext 2)

– Configuration of the embedded D channels

– Add/drop configurations (the add/drop function is available only in A/D-Rep SystemType)

The configurations of the User/D-Ext interfaces and of the embedded D channels areconnected one each other, because the external D channels constitute an alternativesolution to the embedded D channels. The following table points out the interfacesavailable for the different System Types, with the indication of the connection between


4 - OPERATING GUIDE

the configurations of the User/D-Ext interfaces and of the embedded D channels.

Tab. 4.3 User/D-Ext interfaces and embedded D channels according to the System Type

System Type

Available InterfacesConnection between the User/D-Ext interfaces and the

embedded D Channels

2x(1+0)e

A/D-Rep

The following channels are available:– two User/D-Ext 1 and

User/D-Ext 2 interfaces– two embedded D1 and D2

channels.

The external D channels of the User/D-Ext interfaces and the embedded D channels represent alternative solutions:– when the embedded D1 channel is enabled, the Dext and

Dext SRA L Compatible options of the User/D-Ext 1 interface are deactivated

– when the embedded D2 channel is enabled, the Dext and Dext SRA L Compatible options of the User/D-Ext 2 interface are deactivated

– when the User/D-Ext 1 interface is configured as Dext or Dext SRA L Compatible, the embedded D1 channel is deactivated

– when the User/D-Ext 2 interface is configured as Dext or Dext SRA L Compatible, the embedded D1 channel is deactivated.

(1+1) H/Se

(1+1) FD


User/D-Ext 2 interfaces, with User/D-Ext 2 interface pre-fixed as Dext and that can not be changed

– one protected embedded D channel only.

The external D channel of the User/D-Ext 1 interface and the protected embedded D channel represent alternative solutions:– when the protected embedded D channel is enabled, the

Dext and Dext SRA L Compatible options of the User/D-Ext 1 interface remain activated

– when the User/D-Ext 1 interface is configured as Dext or Dext SRA L Compatible, the protected embedded D channel is deactivated.

(1+0)


User/D-Ext 2 interfaces, with User/D-Ext 2 interface pre-fixed as Dext and that can not be changed

– one embedded D channel only.

The external D channel of the User/D-Ext 1 interface and the embedded D channel represent alternative solutions:– when the embedded D channel is enabled, the Dext and

Dext SRA L Compatible options of the User/D-Ext 1 interface remain activated

– when the User/D-Ext 1 interface is configured as Dext or Dext SRA L Compatible, the embedded D channel is deactivated.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Configuration of the User/D-Ext interfaces

On the Access unit, there are two available User/D-Ext interfaces, each one of suchinterfaces can be used for a user channel or for an external D channel devoted to thetransport of the supervisory information.For both the User/D-Ext interfaces, the system provides four different configurationoptions:

– User Codirectional: interface used for codirectional type user channel

– User Contradirectional: interface used for contradirectional type user channel

– Dext: interface used for external D channel

– Dext SRA L Compatible: interface used for external D channel compatible withSRA L;

Please note that, in case of connection between two equipment through external Dchannel, the interface of an equipment has to be configured as Dext while the interfaceof the other equipment has to be configured as Dext SRA L Compatible; in case ofconnection through external D channel between a SRAL XD equipment and anequipment belonging to the SRA L family, the user has to configure the D interface onthe SRAL XD as Dext.To set a specific type of interface, click twice on the corresponding check-box.The set interface type is marked through the selection symbol !.The configuration options really available for the User/D-Ext interfaces depend on theSystem Type and on the current enabling status of the embedded D channels (Tab. 4.3).

Configuration of the embedded D channels

The D channels embedded into the radio frame transport the supervisory information.It is possible to insert each D channel into a 2 Mbit/s tributary slot in such a way to allowto the supervisory information to cross over different transmission systems (e.g.: opticalfiber systems) and to reach other SRAL XD networks/links. The availability and theconfiguration possibility of the embedded D channels depends on the System Type andon the current configuration status of the User/D-Ext interfaces (Tab. 4.3).

– OperationIt allows enabling/disabling the transport of the embedded D channel. Theconfiguration procedure is the following one:• click twice on the Operation field, the system displays the configuration

window• enable (Enabled) or disable (Disabled) the transport of the embedded D

channel

In System Type (1+1) H/S and (1+1), it is available only one protected embeddedD channel.However, into the “External Interfaces Setting” window, there are two sections forthe protected embedded D channel because the equipment software requires forthe separated insertion of the transport parameters for the two BB units.In case of enabling of the protected embedded D channel, the configuration of theparameters relevant to the two “Embedded D-Channel” sections has to be thesame one.

In System Type (1+0), it is available only one embedded D channel, because theequipment equipping kit foresees one system only.


4 - OPERATING GUIDE

• confirm the setting clicking on OK.

Fig. 4.17 Enabling/disabling window for the D channel transport

– Trib SelectedIt allows selecting the 2 Mbit/s tributary to be used for the transport of the Dchannel. The configuration procedure is the following one:• click twice on the Trib Selected field, the system displays the configuration

window• select the 2 Mbit/s tributary to be used for the transport of the embedded D

channel; it is possible to select only the tributaries 1 - 4• confirm the setting clicking on OK.

Fig. 4.18 Selection window of the D channel transport tributary

– Slot SelectedIt allows selecting the slot of the 2 Mbit/s tributary to be used for the transport of theD channel. The configuration procedure is the following one:• click twice on the Slot Selected field, the system displays the configuration

window• select the slot to be used for the transport of the embedded D channel; the

value has to be comprised between 1 and 31• confirm the setting clicking on OK.

Fig. 4.19 Selection window for the D channel transport slot

The transport function of the D channel is available only for the tributaries 1 - 4,independently by the set payload capacity of the system.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Add/drop configurations

To execute the add/drop configurations (function available in A/D-Rep System Typesonly), click on the Add/Drop push-button of the Access section (Fig. 4.16); the systemdisplays the Add/Drop Config window (Fig. 4.26), where the user can check and setthe enabling status of the tributary insertion/extraction of every system and of the userchannel.The Add/Drop push-button into the Access section is deactivated if the connectionstatus of the Access unit is not On Line.

Fig. 4.20 Add/Drop Config window

The system allows the following add/drop configurations:

– Tributary add/dropThe user can enable/disable the insertion/extraction of each single tributary. Theconfiguration procedure is the following one:• click twice on the tributary field to be configured; the system displays the

configuration window• enable (Enabled) or disable (Disabled) the tributary add/drop• confirm the setting clicking on OK.

For each system, the number of the tributaries displayed into the “Add/DropConfig” window depends on the set payload capacity of the system.The add/drop operation is possible only on the enabled tributaries.

The maximum add/drop capacity is equal to the 50% of the maximum payloadcapacity 16x2 Mbit/s. If for the system it is set the payload capacity of 16x2 Mbit/s,the user can configure the add/drop of a maximum of eight tributaries.The tributaries 1 - 8 are reserved for the add/drop on system 1, the tributaries 9 -16 are reserved for the add/drop on system 2.

The add/drop of the user channel is available only if both the User/D-Extinterfaces of the Access unit are configured for codirectional type user channel;on the contrary, the system does not display the “Add/Drop User Channel” field.


4 - OPERATING GUIDE

Fig. 4.21 Configuration window for the tributary add/drop

– Add/drop of the user channelIf both the User/D-Ext interfaces of the Access unit have been configured for acodirectional type user channel, the user can enable/disable theinsertion/extraction of the user channel. The configuration procedure is thefollowing one:• click twice on the Add/Drop User Channel filed, the system displays the

configuration window• enable (Enabled) or disable (Disabled) the add/drop of the user channel• confirm the setting clicking on OK.

Fig. 4.22 Configuration window for the user channel add/drop

4.5.1.2.2 Configuration of the Controller unit interfaces

Into the Controller section of the External Interfaces Setting window (Fig. 4.16), theuser can check the current baud-rate of the F interface (F-Interface field) and executethe configurations relevant to the input lines of the station alarms (Station Alarmspush-button).For the F interface the possible values of the baud-rate are the following ones: 9600,19200, 38400, 57600, 115200.Click on the Station Alarms push-button to display the configuration window of the inputlines relevant to the station alarms (Fig. 4.23).

Fig. 4.23 Station Alarms window


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

For the input lines of the station alarms, the user can configure the following parameters:

– Line IN NameAt each input line of the station alarm, the user can assign a name for theidentification of the coupled alarm. The configuration procedure is the followingone:• click twice on the Name field of an alarm line; the system displays the

configuration window• insert the name to be assigned to the selected alarm line• confirm the setting clicking on OK.

Fig. 4.24 Configuration window for the name of the station alarms

– PolarityThe user can configure the polarity relevant to the alarm condition for the input linesof the station alarms. The configuration procedure is the following one:• click twice on the Polarity field; the system displays the configuration window• select the polarity; the system provides the two following options:

•Floating: alarm condition = open circuit•GND: alarm condition = GND

• confirm the setting clicking one OK.The setting of the Polarity parameter depends on the characteristics of theinterface circuits that provide the station alarms.

Fig. 4.25 Configuration window for the polarity of the station alarms


4 - OPERATING GUIDE

4.5.1.2.3 Configuration of the BB unit tributaries

To configure the tributaries of a BB unit, click on the Payload push-button into therelevant BB section of the External Interfaces Setting window (Fig. 4.16); the systemdisplays the BB Payload Setting window (Fig. 4.26), where the user can check and setthe enabling status of the tributaries relevant to the BB unit.The Payload push-button of a BB unit is deactivated if the connection status of the BBunit is not On Line.The user can execute on the tributaries the following configurations:

– Enabling/disabling of all the tributaries at the same time

– Enabling/disabling of a single tributary

Into the BB Payload Setting window, in case of System Type (1+1) H/S and (1+1) FD,the system displays some warning messages to point out the rules to be respectedduring the configuration of the tributaries.

Fig. 4.26 BB Payload window

System Type (1+0), 2x(1+0), A/D-Rep

In case of System Type (1+0), the system display a BB section into the “ExternalInterfaces Setting” window, because the equipment is equipped with one BB unitonly; in the other System Types, there are two BB sections, because theequipment is equipped with two BB units, identified by BB 1 and BB 2.

The number of the tributaries displayed into the “BB Payload Setting” window,depends on the set payload capacity of the system.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

System Type (1+1) H/S, (1+1) FD, A/D-Rep

Enabling/disabling of all the tributaries at the same time

Through the All Tributaries field, the user can control the enabling/disabling at thesame time of all the tributaries. The configuration procedure is the following one:

– click twice on the All Tributaries field; the system displays the configurationwindow

– select the enabling command (All Enabled) or the disabling one (All Disabled) atthe same time of all the tributaries

– confirm the setting clicking on OK

– the selected command (All Enabled/All Disabled) remains into the All Tributaryfield for some seconds (the time necessary to enable/disable all the tributaries),after that the system automatically restores, into the All Tributary field; theInactive status (it is the status where the command for the contemporary forcingon all the tributaries is deactivated and then the user can executed the forcing ofthe single tributaries).

Fig. 4.27 Configuration window of all the tributary at the same time

Enabling/disabling of a single tributary

When the All Tributary field is in Inactive status, the user can enable/disable eachsingle tributary. The configuration procedure is the following one:

– click twice on the field of the tributary to be configured; the system displays theconfiguration window

– enable (Enabled) or disable (Disabled) the tributary



4 - OPERATING GUIDE

Fig. 4.28 Configuration window of a single tributary

Configuration rules in System Type (1+1) H/S e (1+1) FD

In case of System Type (1+1) H/S and (1+1) FD, when the user executes theconfiguration of the tributaries, he has to respect the following rules:

– the configuration of the tributaries has to be the same one on both the BB units

– the enabling of the tributaries has to be executed before on the BB unit currentlynot on service

– the disabling of the tributaries has to be executed before on the BB unit currentlyon service.

For such an aim, in case of System Type (1+1) H/S and (1+1) FD, into the BB PayloadSetting window (Fig. 4.26):

– the system points out always the signal of the BB unit currently on service (BB 1on Line or BB 2 on Line); if the system does not point out any signal, it means thatit is present an alarm condition for which both the BB units are not on service

– the system displays some warning messages that point out the rules to berespected.

4.5.1.3 Configuration of the protection

To manage the protection (1+1) of the system, click on the Protection push-button intothe Equipment Status & Configuration window (Fig. 4.4); the system displays theProtection Status & Configuration window (Fig. 4.29), where the user can check andset the configuration of the system protection (1+1).

The “Protection” push-button of the “Equipment Status & Configuration” windowis available only in case of System Type (1+1) H/S e (1+1) FD.

In case of System Type (1+1) H/S the ODU1 is prioritary with respect to ODU 2.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Fig. 4.29 Protection Status & Configuration window

System Type (1+1) H/S

System Type (1+1) FD

Configuration of the protection

For the configuration of the protection (1+1) the system provides, into the ProtectionStatus & Configuration window, the following configuration fields:

– Manual Forced BB The user can force on service, via software, the desired BB unit and thecorresponding channel. The configuration procedure is the following one:• click twice on the Manual Forced BB field, the system displays the

configuration window• select the forcing mode; the possible options are the following ones:

• Normal: no one BB unit forced on service via software• 1: BB 1 unit forced on service via software• 2: BB 2 unit forced on service via software

• confirm the setting clicking on OK.After a forcing operation via software, the system provides the signal of manualoperation on progress (par. 4.5.1).


4 - OPERATING GUIDE

Fig. 4.30 Configuration window for the BB forcing via software

– Manual Forced Channel The user can force on service, via software, the desired channel. The configurationprocedure is the following one:• click twice on the Manual Forced Channel field; the system displays the

configuration window• select the forcing mode; the possible options are the following ones:

• Normal: no one channel forced on service via software• 1: channel 1 forced on service via software• 2: channel 2 forced on service via software• Local: forcing on both the BB units, via software, of its own local channel

(channel 1 on BB 1 unit and channel 2 on BB 2)• confirm the setting clicking on OK.After a forcing operation via software, the system provides the signal of manualoperation on progress (par. 4.5.1).

Fig. 4.31 Configuration window for the channel forcing via software

– Protection Mode

It allows selecting the Hot-Standby protection mode of BB, that has to be the sameone for both the BB units. The configuration procedure is the following one:• click twice on the Protection Mode field, the system displays the

configuration window

In case of System Type (1+1) H/S, the BB forcing command concerns also thetransmitting ODU:– forcing on BB 1: the system forces on service the BB 1 unit, with the

subsequent forcing of the ODU 1 on transmission– forcing on BB 2: the system forces on service the BB 2 unit, with the

subsequent forcing of the ODU 2 on transmission.

The “Protection Mode” configuration field is available only in case of SystemType (1+1) H/S.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

• select the protection mode; the possible options are the following ones:• Unrevertive: when the cause that has forced the intervention of the

protection disappears, the protection system remains into the status getafter the intervention of the protection

• Revertive: when the cause that has forced the intervention of theprotection disappears, the protection system returns on main channel(ODU 1 on service)


Fig. 4.32 Configuration window for the Hot-Standby protection mode of BB

– StaticThe user can configure, for each BB unit (BB 1 (CH1-CH2 delay) and BB 2(CH2-CH1 delay) sections) a static delay in such a way to recover, that is to bringto zero the possible dynamic delay present on the BB unit between the channels 1and 2. The configuration procedure is the following one:• click twice on the Static field of the BB 1 (CH1-CH2 delay) or BB 2 (CH2-CH1

delay) section; the system displays the configuration window• insert the value of the static delay, the value has to be comprised between -31

and +31 bit• confirm the setting clicking on OK.

Fig. 4.33 Configuration window of the static delay

Status and alarm signals

Into the Protection Status & Configuration window, (Fig. 4.29), there are the followingstatus and alarm signals:

– System TypeInto the heading field of the window, the system points out the current SystemType. The possible displayings are the following ones:• System Type: (1+1) H/S: Hot-Standby protection (1+1) • System Type: (1+1) FD: protection (1+1) at frequency diversity.

– Connection/fail status of BB unit

The system displays a warning message if for an error the user sets differentprotection modes for the two BB units.


4 - OPERATING GUIDE

For both the BB units, it is possible to have the following displayings:• in normal functioning conditions, the system does not display any signal• the system displays the connection current status of the BB unit

(Disconnected, Connected, Mismatch), if it is differents from On Line• with BB unit on alarm, the system displays the alarm signal:

! Card Fail.

– Status of the hardware protectionFor both the BB units, into the HW Protection field, the system points out thestatus of the hardware protection. The possible displayings are the following ones:• Not Required: no request of the hardware protection• ! Required: forcing request of the hardware protection in case of serious

transmission alarm.

– Activation status of BB unitFor both the BB units, into the Status field, the system points out the activationstatus of the unit. The possible displayings are the following ones:• ON• off.

– Status of the hitless protectionFor both the BB units, into the on Line field, the system points out the status of thehitless protection (the system points out the channel over which it is switched thehitless switch of the BB unit). The possible displayings are the following ones:• CH1: hitless switch on channel 1• CH2: hitless switch on channel 2.

– Switching criteria of the hitless protectionFor both the channels into the Switching Criteria Alarms filed, the systemdisplays the status of the alarms that constitute the switching criteria of the hitlessprotection; such alarms are the following ones:• High Alm: serious alarm on the RX channel• High EW: condition of “early warning high”• Low EW: condition of “early warning low”.The occurrence of an alarm condition is signalled:• by the turning on with red color as of the alarm code as of the LED coupled

with the alarm• by the displaying of the symbol “!” in front of the alarm code.In normal condition, the LED’s are turned on with green color.

– Dynamic delayFor both the BB units, into the Dynamic field, the system displays the value of thedynamic delay currently present between the channels 1 and 2.

– Operating status of the ControllerThe system displays an alarm signal if the Controller is into an operating status thatdoes not allow executing configurating operations on the equipment (par. 4.2.2):• with Controller in RUN/NO SET status, the system displays the following


• with Controller in IDLE status, the system displays the following signal:! IDLE Mode

– Not congruent configuration of BB protectionIn case of System Type (1+1) H/S, the system displays the following warning


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

message BB1 and BB2 must have the same value !

if ti has been set different protection modes for the two BB units.

4.5.1.4 Test configuration

For the test configurations, click on the Testing push-button into the Equipment Status& Configuration window (Fig. 4.4); the system displays the Testing Mode &Loop-Backs window (Fig. 4.34), where the user can check and execute the followingconfigurations:

– Configuration of the local and remote loops on the tributaries

– Temporary turning off command of the radio system

Into the Testing Mode & Loop-Backs window, in case of System Type (1+1) H/S and(1+1) FD, the system displays some warning messages to point out the rules to berespected during the configuration of the loops.In case of remote loop, the tests are executed on the local equipment that has thefunction to transmit back the tributary received by the remote equipment.After a test condition (enabling of a local/remote loop, system temporary turning off) thesystem provides the signal of manual operation on progress (par. 4.5.1)

Fig. 4.34 Testing Mode & Loop-Backs window


In case of System Type (1+0), into the “Testing Mode & Loop-Backs” window, it ispresent one BB section, because the equipment is equipped with one BB unitonly; in the other System Types, there are two BB sections, because theequipment is equipped with two BB units, identified with BB 1 and BB 2.

For each BB unit, the number of the tributaries displayed into the “Testing Mode& Loop-Backs” window depends on the set payload capacity of the system.

The remote loops are possible on the enabled tributaries only.


4 - OPERATING GUIDE


System Type (1+0)

Configuration of the local and remote loops on the tributaries

Into the Testing Mode & Loop-Backs window (Fig. 4.34), the user can execute thefollowing loop configurations on the tributaries:

– Enabling/disabling of local loopIt is possible to enable/disable the local loop on each single tributary. Theconfiguration procedure is the following one:• into the Local Loop column, click twice on the field relevant to the tributary to

be configured; the system displays the configuration window• enable (Enabled) or disable (Disabled) the local loop on the tributary• confirm the setting clicking on OK.

Fig. 4.35 Configuration window of the local loop


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

– Enabling/disabling of remote loopThe user can enable/disable the remote loop on each single tributary. Theconfiguration procedure is the following one:• in the Remote Loop column, click twice on the field relevant to the tributary

to be configured; the system displays the configuration window• enable (Enabled) or disable (Disabled) the remote loop on the tributary• confirm the setting clicking on OK.

Fig. 4.36 Configuration window of the remote loop

Temporary turning off command of the radio system

For maintenance and testing purposes, it is foreseen the possibility to control thetemporary turning off of a radio system; the system is automatically turned on again atthe expiring of the predefined timeout range.To configure the timeout range, execute the following procedure:

– click twice on the Timeout field, the system displays the configuration window

– insert the desired value (expressed by seconds) of the time during which the radiosystem has to be temporary turned off and then confirm the setting clicking on OK.

Fig. 4.37 Configuration window for the temporary turning off timeout

To execute the temporary turning off command, click on the Temporary System OFFpush-button; the system automatically turns on again itself at the expiring of the timeoutrange set into the Timeout field.

Configuration rules in System Type (1+1) H/S and (1+1) FD

In case of System Type (1+1) H/S and (1+1) FD, when the user executes theconfiguration of the loops on the tributaries, he has to respect the following prescriptions:

– the enabling of the loops on the tributaries has to be executed before on the BBunit not on service

– the disabling of the loops on the tributaries has to be executed before on the BBunit on service.

For such an aim, in case of System Type (1+1) H/S and (1+1) FD, into the Testing Mode& Loop-Backs window (Fig. 4.34):


4 - OPERATING GUIDE

– the system always points out the signal of the BB unit currently on service (BB 1on Line or BB 2 on Line); if it is not pointed out any signal, it means that it ispresent an alarm condition for which both the BB units are not on service

– the system displays some warning messages that point out the prescriptions to berespected.

4.5.1.5 Updating of the license

Pressing the License Upgrade push-button into the Equipment Status &Configuration window (Fig. 4.4), the system displays the Feature Control window(Fig. 4.38), where the user can execute the following operations:

– to check the payload capacity and the equipment configurations available with thecurrent license

– to insert a new license to expand the functions of the software.

Fig. 4.38 Feature Control window (reading only mode)

The system displays the Feature Control window in reading only mode. To update thelicense, switch to read/write mode (Fig. 4.39), clicking on Modify; the system switchesthe name of the push-button from Modify up to Upgrade. Into the window there are twosections:

– the Available Functionality section where the system displays the functionsavailable with the current license

– the License Upgrading section for the upgrading of the license.

To change the license, it is necessary, before creating the value of License Key to beinserted, using the proper upgrade tool of the licenses.The value of License Key is created according to the Challenge Number and LicenseMask parameter and to the requested additional functions.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Fig. 4.39 Feature Control window (read/write mode)

The License Key parameter is composed by four fields; click twice on each field todisplay the relevant insertion window (Fig. 4.40).To apply the new value of License Key and then to make effective the new license, it isnecessary to click on the Upgrade push-button.

Fig. 4.40 Insertion of License Key

4.5.1.6 Uploading/memorization of the NE configuration file

Into the Equipment Status & Configuration window (Fig. 4.4), the system providestwo push-buttons that run an application program of NetViewer/LCT for theuploading/memorization of the NE configuration file:

– Copy Config: memorization on file of the equipment configuration

– Paste Config: equipment configuration with the parameters present into the NEconfiguration file.

The two Copy Config and Paste Config push-buttons are activated only in case of loginwith administrator privileges (Admin user class).The use of NE configuration files, memorized on a PC or on a network central archive,has the following double function:

– to make available some backup copies of the equipment configuration, in such away to allow a quick restore of the configuration in case of loss of the configurationitself

– to provide different base configurations, in such a way to make easier and toreduce the configuring operations of the equipment present into the network/link.

The configurations present into the NE configuration file are the following ones:

For the description of the copy/paste procedure relevant to the NE configurationfile, refer to the operating guide of NetViewer/LCT.


4 - OPERATING GUIDE

– configuration of the system parameters: payload capacity, ID of TX and RX link

– configuration of the tributaries

– add/drop configuration of the tributaries and of the user channel

– configuration of the User/D-Ext external interfaces and of the embedded Dchannels

– configuration of the Hot-Standby protection mode (1+1)

– configuration of the RF TX power

– configuration of the frequency mode and of the frequency parameters (Continuousfrequency or frequency plan)

– configuration of the alarm polarity for the input lines of the station alarms.

4.5.1.7 ODU configuration

To configure the transmission parameters of the ODU, click on the correspondingConfigure push-button into the Equipment Status & Configuration window (Fig. 4.4);the system displays the ODU Config window (Fig. 4.41), where the user can executethe following configurations:

– Configuration of the RF density

– Configuration of the RF TX power

– Configuration of the coupling loss for Hot-Standby

– Configuration of the modulation index

– Configuration of the RF frequency:• Configuration of the frequency mode• Continuous frequency• Frequency plan

The Configure push-button of an ODU is deactivated if the connection status of theODU is not On Line.Into the ODU Config window, the system resumes the functioning status of the ODU,through the displaying of the operating parameters and of the status and alarm signals.

In case of System Type (1+1) H/S, the configurations concerning the RF frequencyhave to be the same ones for the two ODU’s.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Fig. 4.41 ODU Config window

ODU HP (HD/ND)

ODU ND

Into the ODU Config window, the system provides the following information and signals:

Parameters

– Parameters of the RF powerFor the RF power, the system points out the following parameters:• P-min

It points out the minimum allowed value of the RF TX power.• P-max

It points out the maximum allowed value of the RF TX power In case of ODU HP, the system points out two values, because the maximumallowed value of the RF power depends on the used RF density (HD/ND):• P-max (CH Density ND): maximum value in case of RF ND density• P-max (CH Density HD): maximum value in case of RF HD density.

• RF Rx PowerIt points out the current value of the RF RX power.

• Rx ThresholdIt points out the RF RX power value relevant to BER 10-6 threshold.


4 - OPERATING GUIDE

– Temperature of the ODU (Temperature)It points out the current value of the ODU temperature (the value that can bedisplayed is comprised between -103°C and +152°C).

– Parameters of the frequency planThe system points out the current configuration of the frequency plan:• First User Channel Number (N0)

It represents the number of the first channel into the frequency plan.• Last User Channel Number (NN)

It represents the number of the last channel into the frequency plan.• First User Channel Freq (TF0)

It represents the transmission frequency (expressed by kHz) of the firstchannel into the frequency plan

• Channel Spacing (Step)It represents the distance (expressed by kHz) between two adjacent channelsinto the frequency plan.

• CapacityIt represents the payload capacity for which the frequency plan has been set.

• CH DensityIt represents the channel RF density for which the frequency plan has beenset.

– Hardware parameters of the ODUInto the HW Parameters filed, the system points out the frequency parametersspecific of the ODU hardware:• TF-Min

It represents the minimum transmission frequency of the ODU.• TF-Max

It represents the maximum transmission frequency of the ODU• Shift

It represents the shift frequency of the ODU.

Status and alarm signals

– Status of the TX sectionThe signal is available only in System Type (1+1) H/S and it points out if thetransmission section of the ODU is on service or if it is on standby. The possibledisplayings are the following ones:• Tx on Line• Tx on Stby

– Status of the RF transmitterWhen the RF transmitter is in normal functioning conditions, the system does notdisplay any signal; in case of silenced RF transmitter, the system displays thefollowing signal: ! Tx Squelched.

– Alarm of ODU checkIf the ODU start-up phase has been finished without detecting errors, the systemdoes not display any signal; on the contrary, it displays one of the following signals:• ! ODU Check in Progress

It points out that the ODU check is again on progress.• ! ODU Whitout HW Parameters

It points out that it has not been possible to detect the hardware parametersof the ODU and/or they are not present.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

• ! IDU/ODU MisalignmentIt points out that some setting on the ODU has not been correctly executedand the IDU and ODU parameters are misaligned.

– Alarm for not congruent frequency planAs into the ODU Config window (Fig. 4.41) as into the Frequency Plan Setup one(Fig. 4.51), the system provides the alarm signalling LED called Freq Plan Fail;which signals the incongruency between the traffic capacity abd RF density of thesystems and those of the frequency plan.The occurrence of the alarm condition is pointed out by:• the turning on with red color of the LED coupled with the alarm• the displaying of the symbol “!” in front of the alarm code.In normal conditions the LED is turned on with green color.

4.5.1.7.1 Configuration of the RF density

If the ODU is a HP type one, The user can set the RF density (ND or HD) to be used.The availability of the RF HD density depends on the equipped ODU type, by the license(par. 4.2.3) and by the payload capacity of the system (par. 4.5.1.1.4).However, independently from other conditions, the CH Density field, for theconfiguration of the RF density, is deactivated if the currently set RF TX power is higherthan the allowed value for the RF HD density (P-max (CH Density HD)); in such a caseto be able to set the RF HD density, the user has to set before a value of the RF TXpower equal to or lower than the maximum allowed value for the RF HD density, in sucha way to activate the CH Density configuration field, naturally the system must complywith all the other conditions that enable for the use of the RF HD density).


– click twice on the CH Density field; the system displays the configuration window

– select the desired RF density; the possible options are the following ones:• ND: Normal Density• HD: High Density


In case of System Type (1+1) H/S, it is necessary to set the same density for boththe ODU’s.

The user can set the RF HD density only on systems with payload capacity equalto 8xE1 e 16xE1.

The “CH Density” field is a reading only one in the following cases:– ODU of ND type only– ODU of HP type with the setting of a not congruent system payload capacity

(2xE1 e 4xE1)– ODU of HP type and license with limitation to the RF ND density only– ODU of HP type with the setting of a RF TX power value higher than the

maximum value allowed for the HD density.


4 - OPERATING GUIDE

Fig. 4.42 Configuration window of RF density

4.5.1.7.2 Configuration of the RF TX power

For the transmission RF power (RF Tx Power parameter), it is necessary to set a valuecomprised between the minimum allowed value (P-min) eand the maximum allowedone (P-max).


– click twice on the RF Tx Power field; the system displays the configuration window

– insert the value of the RF TX power (expressed by dBm) and then confirm thesetting clicking on OK.

Fig. 4.43 Configuration window of the RF TX power

4.5.1.7.3 Configuration of the coupling loss for Hot-Standby

In case of System Type (1+1) H/S, the user has to point out the value of the couplingloss (Coupling Loss parameter) for the RF connection of the ODU.The value of the coupling loss depends on the hardware used for the realization of theHot-Standby protection (1+1) (the typical value of the coupling loss relevant to the RFcouplers are 0 dB and 10 dB).


– click twice on the Coupling Loss field; the system displays the configurationwindow

– insert the value of the coupling loss (expressed in dB); the user can set a valuecomprised between 0 and 15 dB

In case of ODU HP (HD/ND), the maximum allowed value of the RF TX powerdepends on the used RF density (ND or HD) (the maximum allowed value with RFHD density is always lower than the allowed one with RF ND density).

The “Coupling Loss” parameter is available into the “ODU Config” window onlyin case of System Type (1+1) H/S.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE


Fig. 4.44 Configuration window for the coupling loss

4.5.1.7.4 Configuration of the modulation index

If the ODU is a ND type one, the user has to set the assigning mode of the modulationindex (Modulation Index parameter).


– click twice on the Modulation Index field; the system displays the configurationwindow

– select the assignment mode of the modulation index; the possible options are thefollowing ones:• SRAL XD: modulation index of SRAL XD type• SRAL Like: modulation index of SRA L type; it has to be selected only in case

of SRAL XD - SRA L mixed radio links• Free: free modulation index; for each payload capacity, the modulation index

is assigned manually


When the Free option has been set, the system activates the Modulation Indexpush-button that allows displaying the configuration window of the modulation index forthe different payload capacities; for each payload capacity, the configuration procedureis the following one:

– click twice on the insertion field; the system displays the configuration window

– insert the modulation index; it is possible to set a value comprised between 0 and255


The “Modulation Index” parameter is available into the “ODU Config” windowonly if the ODU is a ND type one.

In case of System Type (1+1) H/S, the configuration of the modulation index hasto be the same one for both the ODU’s.


4 - OPERATING GUIDE

Fig. 4.45 Configuration window of the modulation index mode

Fig. 4.46 Configuration window of the modulation index (in Free mode only)

4.5.1.7.5 Configuration of the frequency mode

The system provides two different setting modes of the operating frequencies:

– Continuous frequency (Continuous)The user can set for the transmission frequency every value comprised into thefunctioning band of the equipment.

– Frequency plan (Freq Plan)The user can arrange a channelling plan that stays inside the functioning band ofthe equipment and he can use for the transceiving one of the predefined channels.

To select the frequency setting mode, click twice on the Freq Mode field; the systemdisplays the configuration window where the user can select the frequency setting mode(Continuous or Freq Plan) and then confirm the setting clicking on OK.

Fig. 4.47 Configuration window of the frequency mode

In case of System Type (1+1) H/S, it is necessary to set the same frequency modefor both the ODU’s.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.5.1.7.6 Continuous frequency

In continuous frequency mode (Freq Mode: Continuous), it si necessary to setmanually the values of the transmission and reception RF frequencies. It is sufficient toset one of the two RF power values, because the system automatically calculates andsets the other one according to the shift frequency through the following formula:

RF TX - RF RX = shift frequency of the ODUThe user can set every value of the frequency but such a value has to be comprised intothe functioning band of the ODU (TF Min and TF Max).

Configuration of the parameters

The parameters to be set in continuous mode are the following ones:

– RF Tx FreqIt represents the value of the transmission RF frequency (expressed by kHz). Theconfiguration procedure is the following one:• click twice on the RF Tx Freq field; the system displays the configuration

window• insert the value of the RF TX frequency and then confirm the insertion clicking

on OK.

Fig. 4.48 Configuration window of the RF TX frequency

– RF Rx FreqIt represents the value of the reception RF frequency (expressed by kHz). Theconfiguration procedure is the following one:• click twice on the RF Rx Freq field; the system displays the configuration

window• insert the value of the RF RX frequency and then confirm the insertion clicking

on OK.

Fig. 4.49 Configuration window of the RF RX frequency

In case di System Type (1+1) H/S, the configurations of the RF frequency have tobe the same ones for both the ODU’s.


4 - OPERATING GUIDE

4.5.1.7.7 Frequency plan

In frequency plan mode (Freq Mode: Freq Plan), it is necessary to set before thefrequency plan and then to select the channel to be used (RF Channel parameter)between the ones available into the channelling plan.

The frequencies of the channelling plan have to stay within the functioning range of theODU:

range RF TX: TF0 ... TF0 + (NN - N0) x STEPrange RF RX: (TF0 - SHIFT) ... [(TF0 - SHIFT) + (NN - N0) x STEP]

The following conditions have always to be verified:RF TX - RF RX = shift frequency of the ODUN0 ≤ NN

The maximum number of channels that the user can use into the channelling plandepends on the payload capacity of the system and on the RF density, as it is pointedout into the following table; come indicato nellaseguente tabella; the following conditionhas always to be verified:

(NN - N0) < max. number of channels

Into the ODU Config window (Fig. 4.41), click on the RF Frequency Settingpush-button to display the configuration window of the frequency plan (Fig. 4.50); thesystem displays the window in reading only mode.To set the parameters of the frequency plan, switch in read/write mode (Fig. 4.51),clicking on Modify; the system switches the name of the push-button from Modify up toOK.

The “RF Channel” parameter is available into the “ODU Config” window onlywhen it has been set the frequency plan mode.

In case of System Type (1+1) H/S, the configuration of the frequency plan has tobe the same one for both the ODU’s.

Tab. 4.4 Max. number of channels into the frequency plan

Payload capacity RF density Max. number of Channel

2xE1 ND 128

4xE1 ND 64

8xE1 ND 32

8xE1 HD 64

16xE1 ND 16

16xE1 HD 32


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Fig. 4.50 Frequency Plan Setup window (reading only mode)

Fig. 4.51 Frequency Plan Setup window (read/write mode)


In frequency plan mode, it is necessary to configure the parameters of the channellingplan into the Frequency Plan Setup window (Fig. 4.51) and the RF Channel parameterof the ODU Config window (Fig. 4.41).

– First User Channel Number (N0)It represents the number of the first channel that can be used for the transmissionof the signal into the frequency plan. The configuration procedure is the followingone:• click twice on the First User Channel Number (N0) field; the system displays

the configuration window• insert the number of the first channel; the user can set a value comprised

within the range 0 - 255• confirm the insertion clicking on OK.The following condition has always to be verified: N0 ≤ NN.

Fig. 4.52 Configuration window of the N0 channel

– Last User Channel Number (NN)It represents the number of the last channel that can be used for the transmissionof the signal into the frequency plan. The configuration procedure is the followingone:• click twice on the Last User Channel Number (NN) field; the system displays

the configuration window• insert the number of the last channel; the user can set a value comprised

within the range 0 - 255


4 - OPERATING GUIDE

• confirm the insertion clicking on OK.The following condition has always to be verified: NN ≥ N0.

Fig. 4.53 Configuration window of the NN channel

– First User Channel Freq (TF0)It represents the transmission frequency (expressed by kHz) of the first channel inthe frequency plan. The configuration procedure is the following one:• click twice on the First User Channel Freq (TF0) field; the system displays

the configuration window• insert the value of the frequency relevant to the first channel and then confirm

the insertion clicking on OK.

Fig. 4.54 Configuration window for the frequency of the first channel (TF0)

– Channel Spacing (Step)It represents the distance (expressed by kHz) between two adiacent channels. Theconfiguration procedure is the following one:• click twice on the Channel Spacing (Step) field; the system displays the

configuration window• insert the value of the spacing between two adiacent channels and then

confirm the insertion clicking on OK.

Fig. 4.55 Configuration window of the spacing between two adjacent channels

– CapacityIt represents the payload capacity for which the user wants to set the frequencyplan. The configuration procedure is the following one:• click twice on the Capacity field; the system displays the configuration

window• select the value of the payload capacity; the possible options are the following

ones:• 2xE1• 4xE1• 8xE1


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

• 16xE1• confirm the setting clicking on OK.The setting of the Capacity parameter has to be congruent with the equippedhardware and with the payload capacity set into the system configuration(par. 4.5.1.1).

Fig. 4.56 Selection window of the payload capacity

– CH DensityIt represents the channel RF density for which the user wants to set the frequencyplan. The configuration procedure is the following one:• click twice on the CH Density field; the system displays the configuration

window• select the channel RF density; the possible options are the following ones:

• HD: RF High Density • ND: RF Normal Density

• confirm the setting clicking on OK.The setting of the CH Density parameter has to be congruent with the equippedhardware and with the ODU type set into the system configuration (par. 4.5.1.1).

Fig. 4.57 Selection window of the channel RF density

– RF ChannelIt represents the number of the RF channel assigned to the transceiving system.The configuration procedure is the following one:• click twice on the RF Channel field; the system displays the configuration

window• insert the number of the RF channel (it has to correspond to the number of a

channel included into the channelling plan, that is comprised between N0 andNN)



4 - OPERATING GUIDE

Fig. 4.58 Configuration window of the RF Channel

4.5.2 Management of the equipment software

The Software menu allows, through operations on the Controller unit, the managementof the equipment software.The Software menu (Fig. 4.59) provides the following options:

– Software Bank: Management of the memory banks

– FTP Transfer: Download of the equipment build software

– Controller Reset: Reset of the Controller unit

Fig. 4.59 Software menu

4.5.2.1 Management of the memory banks

The Software Bank command into the Software menu (Fig. 4.59) displays theEquipment Software Bank window (Fig. 4.60), where the user can manage thememory banks of the Controller unit and check the embedded and/or firmware softwarerunning on the equipment units.The commands concerning the memory banks of the Controller unit and the unitsoftware are available only in case of login with administrator privileges (Admin userclass); in case of login without administrator privileges, the system displays theEquipment Software Bank window (Fig. 4.61) without the command push-buttons,because the user can execute only reading operations.The upper part of the Equipment Software Bank window points out, through a table,the operating status of the two memory banks of the Controller unit, with the indocationof the following information:

– release, build and checksum of the software uploaded on the active memory bankof the Controller unit

– release, build e checksum of the software uploaded on the standby memory bankof the Controller unit.

In case of error over the standby bank, the system disables the possibility to execute theswitching of the memory banks (Switch Banks push-button deactivated), the systemdisplays the following signal:Stand-by Bank Status: WRONG !.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

In the central part of the Equipment Software Bank window, in case of login with theadministrator privileges, there are two control push-buttons for the memory banks of theController unit:

– Switch BanksThe subject push-button controls the switching of the memory banks of theController unit: the bank that was on standby switches to the active status, on thecontrary the bank that was on active status switches on standby one. When theuser executes the switching operation, the system displays a warning window(Fig. 4.62), to point out that in some special situations, the switching of the bankson the Controller unit can cause the loss of the payload and/or the loss of theequipment supervisory; to confirm the command and then to execute the switchingclick on the Software Banks push-button of the warning window. The switchingoperation runs the version of the software relevant to the Controller unit presentinto the bank that has become active; the system keeps on progress thepre-existing software on the slave units.

– Copy Active in Stand-by bankThe subject push-button copies the contents of the active bank into the stand-byone, allowing the alignment of the two banks.

In the lower part of the Equipment Software Bank window, the system displays thetable of the unit software, composed by the following fields:

– Run VersionIt points out the version of the software currently on progress on each unit.

– StatusIt points out the alignment status of the software for each slave unit:• Software Aligned: the version of the software on progress on the unit is the

same one of the unit software present into the build uploaded on the activebank of the Controller unit.

• Software Not Aligned: the version of the software on progress on the unit isdifferent from the one of the unit software present into the build uploaded onthe active bank of the Controller unit.

– Alignment (available only in case of login with administrator privileges)It contains the alignment commands of the software relevant to the slave units(Download push-buttons); each push-button is activated only if the software of thecorresponding unit has not been aligned. The alignment command runs the versionof the unit software present into the build currently uploded on the active bank ofthe Controller unit; the alignment procedure consists of the execution of the unitsoftware download from the active bank of the Controller unit to the unit memory.

The switching command of the banks causes a reset of the Controller unit, withtemporary loss of the equipment from NetViewer/LCT and without payload loss.In case of connection through F interface, the user has to run again the dial-upconnection from LCT.


4 - OPERATING GUIDE

The alignment operation of the unit software can cause a payload loss:– Not protected configuration

• Alignment of the ODU embedded softwareIt is present a payload loss for approximately 1 minute due to the ODUstart-up.

• Alignment of the BB unit firmwareIt is present a payload loss for approximately 5 seconds.


– Protected configuration• Alignment of the BB 1 unit firmware and/or of the ODU 1 embedded

softwareTo reduce at the minimum level the payload loss, it is necessary (beforestarting the alignment procedure) to force the protection on BB 2 and onRX 2 channel; in such a way the BB 2 and the ODU 2 units on which thesystem has not to execute the download operation are on service.Now the user can execute the download of the firmware relevant to theBB 1 unit and/or if the ODU 1 embedded software embedded insequence.The system has a maximum payload loss approximately for 2 secondsdue to the switching operation.

• Alignment of the BB 2 unit firmware and/or of the ODU 2 embeddedsoftwareTo reduce at the minimum level the payload loss, it is necessary (beforestarting the alignment procedure) to force the protection on BB 1 and onRX 1 channel; in such a way the BB 1 and the ODU 1 units on which thesystem has not to execute the download operation are on service.Now the user can execute the download of the firmware relevant to theBB 2 unit and/or if the ODU 2 embedded software embedded insequence.The system has a maximum payload loss approximately for 2 secondsdue to the switching operation.


Therefore, in protected configuration, for the complete download on all the units,the system has a maximum payload loss equal to 7 seconds.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Fig. 4.60 Equipment Software Bank window (with administrator privileges)

System Type (1+0)



4 - OPERATING GUIDE

Fig. 4.61 Equipment Software Bank window (without the administrator privileges)

System Type (1+0)


Fig. 4.62 Warning for bank switching

4.5.2.2 Download of the equipment build software

The FTP Transfer option of the Software menu (Fig. 4.63) runs the FTP Clientprogram, that allows executing the download via FTP of the equipment build software.The download operation uploads the build software only on the standby bank of theController unit; on the active bank of the Controller unit and on the other units, thesystem keeps running the pre-existing software.If the FTP Client program has not been installed; the system displays an error windowat the command execution.The download of the equipment build software can be executed only in case of login withthe administrator privileges (Admin user class); in case of login without the administratorprivileges, the FTP Transfer option of the Software menu is deactivated.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Fig. 4.63 FTP Transfer option

Fig. 4.64 Error of FTP Client not installed

4.5.2.3 Reset of the Controller unit

Select Controller Reset into the Software menu (Fig. 4.65). The system displays the Controller Reset window (Fig. 4.66) where the user canexecute the reset command of the Controller unit, clicking on the Controller Resetpush-button.To point out the hazards coupled with the reset operation of the Controller unit, thesystem displays permanently, into the Controller Reset window, the followingmessage:

UNDER SPECIAL CIRCUMSTANCES,LOSS OF PAYLOAD OR/AND LOSS OF NE SUPERVISION

CANNOT BE EXCLUDED AFTER THIS COMMAND IS ISSUED.

The reset of the Controller unit can be executed only in case of login with theadministrator privileges (Admin user class); in case of login without the administratorprivileges, the Controller Reset option of the Software menu is deactivated.

Fig. 4.65 Controller Reset option

In particular situations, the reset of the Controller unit can cause the payload lossand/or the equipment supervisory loss. Therefore, the user has to execute thereset of the Controller unit only when it is strictly necessary.


4 - OPERATING GUIDE

Fig. 4.66 Controller Reset window

4.5.3 Configuration of the network parameters

The Network menu allows configuring all the parameters for the connection of theequipment to the IP network used for the supervisory of the radio network.The Network menu (Fig. 4.67) provides the following options:

– IP Address: Configuration of the IP address

– NE Parameters: Configuration of the network parameters for the interfaces

– Static Routing Table 1...10: Configuration of the static routing table (entry from 1up to 10)

– Static Routing Table 11...20: Configuration of the static routing table (entry from11 up to 20)

Fig. 4.67 Network menu

4.5.3.1 Configuration of the IP address

If the user selects IP Address into the Network menu (Fig. 4.67), the system displaysin reading only mode the Network IP Address window Fig. 4.68), that displays theequipment IP address and the coupled subnet-mask.To set/change the IP address and the coupled subnet-mask, switch to read/write mode,clicking on Modify; the system switches the name of the push-button from Modify toOK.The configuration of the IP address can be executed only in case of login withadministrator privileges (Admin user class); in case of login without administratorprivileges, the system displays the Network window without the Modify push-button,because the user can execute only reading operations.

The parameters of the Network menu have to be assigned by the networkadministrator.

It is necessary to pay particular attention during the configuration of the NE IPaddress, because a wrong setting can make unreachable the equipment and/orcan make unreachable the equipment of other networks/subnetworks.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

To point out the hazard connected with the configuration operation of the equipment IPaddress, the system permanently displays, into the Network IP Address window, thefollowing message:

DANGEROUS OPERATION ! IF WRONGLY CONFIGURED,

THE NE WILL BE PERMANENTLY UNREACHABLE

Fig. 4.68 Network IP Address window (reading only mode)

With administrator privileges

Without administrator privileges

All the configuration parameters (operating parameters, system parameters,network parameters) are memorized into the EEPROM memory of the hardwarekey, with the exception of the IP address that is memorized as into the hardwarekey as into the Controller unit. When the user starts up the equipment withhardware key inserted, the system always uploads the IP address memorized intothe hardware key (if it is present).


4 - OPERATING GUIDE

Fig. 4.69 Network IP Address window (read/write mode)


– IP AddressThe IP address is the address through which the system identifies the equipmentinto 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.

Fig. 4.70 Configuration window of the IP address

– Sub-Net MaskThe subnet-mask allows the solving of the IP address, because it has the functionto point out how many bits are used to address the sub-network and how many bitsare used to address the host. The subnet-mask has to be the same for all theequipment belonging to the same sub-network. The configuration procedure is thefollowing one:• click twice on the Sub-Net Mask field; the system displays the configuration

window• insert the subnet-mask coupled with the equipment IP address and then

confirm the insertion clicking on OK.

Fig. 4.71 Configuration window of the subnet-mask


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.5.3.2 Configuration of the network parameters for the interfaces

If the user selects NE Parameters into the Network menu (Fig. 4.67), the systemdisplays the NE Parameters window (Fig. 4.72), where he can configure the networkparameters for the different interfaces used for the transport of the supervisoryinformation.

The supervisory of the radio networks is based upon IP networks that use the RIPv1protocol for the distribution of the routing information.Each equipment is an host of the IP network, that has to be able correcly to execute asthe routing of the supervisory information as the propagation of the routing informationtowards other hosts and towards other networks/sub-networks.For such an aim, the user has correctly to configure the network parameters for eachinterfaces used for the transport of the supervisory information.Into the NE Parameters window, there are the following interfaces:

– Q/V: it contains the following two Ethernet interfaces:• V interface: 10BaseT Ethernet interface used for the connection between the

equipment and a supervisory system (e.g.: equipment connection withNetViewer)

• Q interface: 10/100BaseT Ethernet interface with hub function used for theconnection between the Controller units of equipment belonging to the samestation and for the connection between the equipment Contoller and asupervisory system

– R1 and R2: channels embedded into the radio frame, reserved for thetransmission, via radio, of the supervisory information; for each radio system, it ispresent 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 2x(1+0) and A/D-Rep, both the R1 and R2 channels

are available (the R1 channel is reserved for the system 1 and the R2 channelis reserved for the system 2)

• in case of System Type (1+0), it is available only one R channel, because theequipment is equipped with one radio system only.

– D1 and D2: They are two interfaces of the Controller that can be used for thetransport of the external D channels (User/D-Ext external interfaces of the Accessunit) and of the D channels embedded into the radio frame.

It is necessary to pay particular attention during the configuration of theparameters relevant to the NE interfaces, because a wrong setting can makeunreachable the equipment and/or can make unreachable the equipment of othernetworks/sub-networks.

In case of login with reading only privileges (Read Only user class), the settingfields are all reading only type ones.


4 - OPERATING GUIDE

The availability and the using mode of the D interfaces depends on the System Typeand on the configuration of the external interfaces relevant to the Access unit(par. 4.5.1.2.1):

– System Type 2x(1+0) and A/D-Rep:• D1 interface: it is used for the transport of the external D1 channel or of the

embedded D1 channel• D2 interface: it is used for the transport of the external D2 channel or of the

embedded D2 channel

– System Type (1+1) H/S and (1+1) FD:• D1 interface: it is used for the transport of the external D1 channel or of the

protected embedded D channel;• D2 interface: it is used for the transport of the external D2 channel, because

the User/D-Ext 2 external interface is pre-fixed as external D channel

– System Type (1+0):• D1 interface: it is used for the transport of the external D1 channel or of the

embedded D channel• D2 interface: it is used for the transport of the external D2 channel, because

the User/D-Ext 2 external interface is pre-fixed as external D channel.

To point out the hazards connected with the configuring operation of the networkparameters relevant to the interfaces, the system permanently displays the followingmessage:


THE NE WILL BE PERMANENTLY UNREACHEABLE

A D interface is not available into the “NE Parameters” window, if both thefollowing conditions are verified:– the corresponding embedded D channel is disabled– the corresponding external D channel is not used (User/D-Ext interface

configured for user channel).In case of System Type (1+0), (1+1) H/S and (1+1) FD, the D2 interface is alwaysavailable, because the User/D-Ext 2 external interface is pre-fixed as external Dchannel.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Fig. 4.72 NE Parameters window


System Type (1+0), (1+1) H/S, (1+1) FD


For each interface, the network parameters to be configured are the following ones:

– Network ProtocolIt is the network protocol of the interface. The configuration procedure is thefollowing one:• click twice on the Network Protocol field; the system displays the

configuration window• select the protocol; the available options are the following ones:

• None: interface not used for the transport of the supervisory information• IP: IP on PPP and PPP on HDLC standard• IP SRA L Compatible: IP on proprietary HDLC; it has to be set only in

case of direct connection, via radio or through external D (External orEmbedded D Channel), with an equipment belonging to the SRA Lfamily

For each interface, the default configuration is the following one:– Network Protocol: IP– RIPv1 Enable: enabled– RIPv1 Silent: disabled– Static Route Propagation: enabled– Border Gateway: disabled– Ingress Summarization: enabled– Metric Override: disabled.


4 - OPERATING GUIDE

• confirm the setting clicking on OK.For the Ethernet Q/V interface, the network protocol is pre-fixed on IP and it cannot be changed.

Fig. 4.73 Configuration window of the interface network protocol

– RIPv1 It allows enabling/disabling, clicking on the Enable check-box, the support on theinterface of the RIPv1 protocol, for the propagation, the reception and theprocessing of the routing information; the subject option is enabled when themarking symbol ! is present, on the contrary it is disabled without the markingsymbol.When the RIPv1 option is enabled, the system uses the interface as to spread asto receive the RIPv1 information with the aim to update the routing tables.When the RIPv1 option is disabled, the system does not spread at output on theinterface the RIPv1 information and it ignores the RIPv1 information received atinput.If the subject option is disabled, the other options concerning the RIPv1 protocolare not significant ones: RIPv1 Silent, Static Route Propagation, BorderGateway, Ingress Summarization, Metric Override.

– RIPv1 Silent It allows enabling/disabling, clicking on the Enable check-box, the silenced RIPv1option at output from the interface; the subject option is enabled when it is presentthe marking symbol !, on the contrary it is disabled without the marking symbol.When the RIPv1 Silent option is disabled, the interface does not spread at outputthe RIPv1 information; however, the system processes the RIPv1 informationreceived on the interface for the updating of the routing tables.The subject option is a significant one only if the RIPv1 protocol is enabled on theinterface.

– Static Route PropagationIt allows enabling/disabling, clicking on the Enable check-box, the propagation ofall the static routing information through the interface; the propagation is enabledwhen it is present the marking symbol !, on the contrary it is disabled without themarking symbol.The subject option is a significant one only if the RIPv1 protocol is enabled on theinterface.

– Border GatewayIt allows enabling/disabling, clicking on the Enable check-box, the Border Gatewayfunction on the interface; the subject function is enabled when it is present themarking symbol !, on the contrary it is disabled without the marking symbol.When the Border Gateway function is enabled, the system excludes theinformation relevant to the sub-network from the routing tables forwarded throughthe interface; it is present only the information relevant to the network.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

The Border Gateway function can be applied when a device connects two or moredifferent IP networks and it is used the RIPv1 protocol for the distribution of therouting information.Then, the Border Gateway function can be enabled only if the interface is used forthe direct connection with a different IP network.The subject option is a significant one only if the RIPv1 protocol is enabled on theinterface.

– Ingress SummarizationIt allows enabling/disabling, clicking on the Enable check-box, the IngressSummarization function on the interface; the subject function is enabled when it ispresent the marking symbol !, on the contrary it is disabled without the markingsymbol.Though the RIPv1 protocol does not spread the subnet-mask, the IngressSummarization option allows pointing out the interpretation mode of the IPaddresses 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-maskof the IP address network/subnetwork (if it is possible to calculate it) or, as analternative solution, it is applied the subnetmask coming from the class of theIP address itself

• when the Ingress Summarization option is disabled, the system sees theIP addresses as host addresses (it is applied the subnet-mask255.255.255.255).

The user can disable the Ingress Summarization option only in IP networks thatdo not foresee the use of subnetworks.Therefore, it is advisable, with the exception of specific cases, to enable always theIngress Summarization option.The subject option is a significant one only if the RIPv1 protocol is enabled on theinterface.

– Metric OverrideIt allows forcing, as on transmission as on reception, the reset of the metric on theinterface. The configuration procedure is the following one:• click twice on the Metric Override field; the system displays the configuration

window• set the forcing (Reset) or not (None) of the metric reset and then confirm the

insertion clicking on OK.The reset of the metric is a function that allows exceedinf the threshold of 15 jumpsforeseen by the RIPv1 protocol.When the Metric Override option is enabled, the system applies the metric valueequal to 1 to the RIPv1 information received and transmitted through the interface.The subject option is a significant one only if the RIPv1 protocol is enabled on theinterface.


4 - OPERATING GUIDE

Fig. 4.74 Configuration window of the metric reset

Alarm signals

For each R and D interface, it is available a alarm signalling LED for protocol error (onlayer 2 of the TCP/IP stack). The occurrence of an alarm condition is pointed out by theturning on with red color of the LED coupled with the alarm. In normal conditions, theLED’s are turned on with green color.

4.5.3.3 Configuration of the static routing table

If the user selects Static Routing Table (1...10 or 11 ... 20) into the Network menu(Fig. 4.67), the system displays in reading only mode the Static Routing Table window(Fig. 4.75), that displays the static routing table.To set the entries of the static routing table, switch to read/write mode (Fig. 4.76),clicking on Modify; the name of the push-button switches from Modify to OK.The configuration of the static routing table can be executed only in case of login withadministrator privileges (Admin user class); in case of login without the administratorprivileges, the system displays the Static Routing Table window without the Modifypush-button, because it is possible to execute reading operations only.The user can manually set up to 20 entries for the static routing table, subdivided intotwo windows: one window for the first ten entries (from 1 up to 10) and one window forthe other 10 entries (from 11 up to 20).The user has to click on OK to confirm and to apply to the static routing table the settingsexecuted on the entries.To point out the hazards connected with the operation on progress, the systempermanently displays, into the Static Routing Table window, the following message


THE NE WILL BE PERMANENTLY UNREACHEABLE

It is necessary to pay special attention during the configuration of the staticrouting table, because a wrong setting can make unreachable the equipmentand/or can make unreachable the equipment belonging to othernetworks/subnetworks.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Fig. 4.75 Static Routing Table window (reading only mode)

With administrator privileges

Without administrator privileges

Fig. 4.76 Static Routing Table window (read/write mode)


4 - OPERATING GUIDE


For each entry of the static routing table, the user has to configure the followingparameters:

– Destination Address It is the destination IP address of the routing entry, that can be as the IP addressof a host as the IP address of a different network/subnetwork. The configurationprocedure is the following one:• 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. 4.77 Configuration window of the routing IP address

– SubNet MaskIt is the subnet-mask coupled with the destination IP address of the routing entry.The configuration procedure is the following one:• 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.

Fig. 4.78 Configuration window for routing subnet-mask

– InterfaceIt is the interface to which applies the routing entry. The configuration procedure isthe following one:• click twice on the Interface field; the system displays the configuration

window• select the interface; the possible options are the following ones:

• None: none• Ethernet: Ethernet Q/V interface• R1: R1 channel• R2: R2 channel (available only in System Type 2x(1+0) and A/D-Rep)• D1: D1 channel• D2: D2 channel

• confirm the insertion clicking on OK.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Fig. 4.79 Selection window for routing interface

– Gateway It is the IP address of the gateway, through which it is possible to reach thedestination of the routing entry. The configuration procedure is the following one:• click twice on the Gateway field; the system displays the configuration

window• insert the IP address of the gateway and then confirm the insertion clicking on

OK.

Fig. 4.80 Configuration window for routing gateway

– Propagation It allows enabling/disabling, clicking on the Enable check-box, the propagation ofthe corresponding routing entry.The marking symbol ! points out the routing entries for which it is enabled thepropagation.

4.5.4 Configuration of NE date and time

The Date and Time option of the Status and Config menu (Fig. 4.81) runs anapplication 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 ofthe measurements and recordings on the equipment.The date and time configuration can now be executed only in case of login withadministrator privileges (Admin user class); in case of login without administratorprivileges, the Date and Time option displays only a window for the displaying of thecurrent NE date and time (Fig. 4.82).

Fig. 4.81 Date and Time menu


4 - OPERATING GUIDE

Fig. 4.82 Date & Time window

The manual setting of date and time is significant only if for the NE it has beendisabled the network synchronization. If for the NE, it is enabled the networksynchronization, the manual setting of date and time will be overwritten at thenext synchronization; the system synchronizes the NE’s every 24 hours.

In case of date and/or time change, the performance windows of the NE are in anincongruent status up to the end of the polling cycle. Then, it is necessary to waitfor some seconds (until to the refresh of the windows) before executing thereading or the recording of the performances.

The Time Mode parameter points out the timing mode set for the networksynchronization:– 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 theoperating guide of NetViewer/LCT.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.6 Alarms MenuThe Alarms menu allows checking the status of the equipment alarms and detecting thecause of a possible malfunctioning.The Alarms menu (Fig. 4.83) provides the following options:

– Physical and Functional: Functional and physical alarms

– Station: Station alarms

Fig. 4.83 Alarms menu

4.6.1 Functional and physical alarms

The Physical and Functional option of the Alarms menu (Fig. 4.83) displays thePhysical & Functional Alarms window (Fig. 4.84), that displays the current status ofthe equipment alarms.The Physical & Functional Alarms window is subdivided into three sections:

– Physical Alarms: Unit physical alarms

– Functional Alarms: Functional alarms

– Severity Alarms: Resuming signals of the alarm severity

Fig. 4.84 Physical & Functional Alarms window

System Type (1+0)

The system points out the occurrence of an alarm condition into the alarmdisplaying windows:– by means of the turning on through red color of the LED coupled with the

alarm– by means of the displaying of the symbol “!” in front of the alarm code.In normal conditions, the LED’s are turned on with green color.


4 - OPERATING GUIDE


4.6.1.1 Unit physical alarms

The Physical Alarms section of the Physical & Functional Alarms window (Fig. 4.84),displays the functional layout of the equipment, with the indication of the physical alarmssubdivided by unit:

– Alarms of the Access unit

– Alarms of the Controller unit

– Alarms of the memory hardware key

– Alarms of the BB unit

– Alarms of I/F cable

For each unit of the equipment (comprised the I/F cable) the system makes available:

– a signalling LED of the unit resuming alarm

– a push-button for the displaying of the single roots of the unit resuming alarm; thesubject push-button is deactivated if the corresponding unit is not On Line

– possible alarm signals that are not summarized into the resuming alarm (for BBand ODU units only).

In case of fail to the I/F cable for the IDU - ODU connection, the system displays thesymbol X on the graphic symbol of the cable.

The functional layout of the equipment displayed into the “Physical & FunctionalAlarms” window depends on the System Type:– in System Type (1+0), the system displays the equipment equipped with one

BB unit and one ODU– in the other System Types, it is displayed the equipment equipped with two

BB units (identified with BB 1 and BB 2) and with two ODU’s (identified withODU 1 and ODU 2).


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.6.1.1.1 Alarms of the Access unit

To display the physical alarms of the Access unit, click on the correspondingpush-button into the Physical & Functional Alarms window (Fig. 4.84); thepush-button displays the Access User Physical Alarms window (Fig. 4.85), thatdisplays the Card Fail resuming alarm of the Access unit Access.Into the Access User Physical Alarms window, it is available also the Maintenancepush-button that allows displaying the single roots of the Card Fail resuming alarmrelevant to the Access unit (Fig. 4.86).

Fig. 4.85 Access User Physical Alarms window

Fig. 4.86 Access Maint Physical Alarms window

Alarm signals

– Card Fail Resuming alarm of unit fail; it is the summarization of the single alarm rootsrelevant to the Access unit (Fig. 4.86).

– Roots of the Card Fail alarm• Power Fail

Alarm for the absence of the inner voltages.• SPI Fail

Alarm for fail on the SPI inner communication bus.• I2C Fail

Alarm for fail on the I2C inner communication bus.• SW Mismatch

Alarm for unit software not congruent with the hardware.• Download Failure

Alarm for error during the download of the unit software.


4 - OPERATING GUIDE

4.6.1.1.2 Alarms of the Controller unit

To display the physical alarms of the Controller unit click on the correspondingpush-button into the Physical & Functional Alarms window (Fig. 4.84); the subjectpush-button displays the Controller User Physical Alarms window (Fig. 4.87), thatpoints out the Card Fail resuming alarm of the Controller unit.Into the Controller User Physical Physical Alarms window, it is available also theMaintenance push-button that allows displaying the single roots of the Card Failresuming alarm relevant to the Controller unit (Fig. 4.88).

Fig. 4.87 Controller User Physical Alarms window

Fig. 4.88 Controller Maint Physical Alarms window

Alarm signals

– Card Fail Resuming alarm of unit fail; it is the summarization of the single alarm rootsrelevant to the Controller unit (Fig. 4.88).

– Roots of the Card Fail alarm:• SPI Fail

Alarm for fail on the SPI inner communication bus.• I2C Fail

Alarm for fail on the I2C inner communication bus.

4.6.1.1.3 Alarms of the memory hardware key

To display the physical alarms of the memory hardware key, click on the correspondingpush-button into the Physical & Functional Alarms window (Fig. 4.84); the subjectpush-button displays the Mem Key User Physical Alarms window (Fig. 4.89), thatpoints out the alarms of the memory hardware key.

Fig. 4.89 Mem Key User Physical Alarms window


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Alarm signals

– Key E2prom Fail Alarm for fail of the EEPROM.

– Alignment Fail Alarm for alignment error: the serial number of the memory hardware key isdifferent from the one memorized into the Controller unit.

4.6.1.1.4 Alarms of the BB unit

Into the Physical & Functional Alarms window (Fig. 4.84), the system groups all thealarms concerning the BB units into the relevant boxes.To display the physical alarms of the BB unit, that are summarized into the unit resumingalarm, click on the corresponding push-button; the subject push-button displays the BBUser Physical Alarm window (Fig. 4.90), that points out the Card Fail resuming alarmof the BB unit.Into the BB User Physical Alarm window, it is available also the Maintenancepush-button that allows displaying the single roots of the Card Fail resuming alarmrelevant to the BB unit (Fig. 4.91).

Fig. 4.90 BB User Physical Alarms window

Fig. 4.91 BB Maint Physical Alarms window

Alarm signals

– Power Supply Alarm for the absence and/or low battery voltage (battery 1 for BB 1, battery 2 forBB 2).

– Card Fail Resuming alarm of unit fail; it is the summarization of the single alarm roots(Fig. 4.91).

– Roots of the Card Fail alarm:• Power Fail

Alarm for absence of the inner voltages.


4 - OPERATING GUIDE

ASIC Fail Alarm for fail of the ASIC circuit.

• SPI Fail Alarm for fail of the SPI inner communication bus.

• I2C Alarm for fail of the I2C inner communication bus.

• ODU DC Alarm for fail of the ODU power supply circuit.

• SW Mismatch Alarme for unit software not congruent with the hardware.

• Download Failure Alarm for error during the download of the unit software.

4.6.1.1.5 Alarms of I/F cable

To display the physical alarms of a I/F cable, click on the corresponding push-button intothe Physical & Functional Alarms window (Fig. 4.84); the subject push-buttondisplays the Cable User Physical Alarms window (Fig. 4.92), that points out the CableFail resuming alarm of the I/F cable.Into the Cable User Physical Alarms window, it is available also the Maintenancepush-button that allows displaying the roots of the Cable Fail resuming alarm relevantto the I/F cable (Fig. 4.93).

Fig. 4.92 Cable User Physical Alarms window

Fig. 4.93 Cable Maint Physical Alarms window

Alarm signals

– Cable Fail Resuming alarm for cable fail; it is the summarization of the single alarm rootsrelevant to the I/F cable (Fig. 4.93).

– Roots of the Cable Fail alarm:• Open Cable

Alarm for I/F cable interrupted/open.• Cable Overload

Alarm for overload on the I/F cable.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.6.1.1.6 Alarms of ODU

Into the Physical & Functional Alarms window (Fig. 4.84), the system groups all thealarms concerning the ODU’s into the relevant boxes.To display the physical alarms of the ODU, that are summarized into the unit resumingalarm, click on the corresponding push-button; the subject push-button displays theODU User Physical Alarms window (Fig. 4.94), that points out the Card Fail resumingalarm of the ODU unit.Into the ODU User Physical Alarms window, it is available also the Maintenancepush-button that allows displaying the single roots of the Card Fail resuming alarmrelevant to the ODU (Fig. 4.95).

Fig. 4.94 ODU User Physical Alarms window

Fig. 4.95 ODU Maint Physical Alarms window

Alarm signals

– SW Mismatch Alarm for ODU sofware not congruent with the hardware.

– Download FailureAlarm for error during the download of the ODU software.

– ODU Power FailAlarm for absence of the ODU power supply voltage; the threshold check on thepower supply line is executed on the I/F cable interface circuit of the IDU.

– ODU µP AlarmAlarm for fail to the µP of the ODU.

– Card FailResuming alarm of ODU fail; it is the summarization of the single alarm roots.

– Roots of the Card Fail alarm:• Power Supply

Alarm for absence of the ODU power supply.The Power Supply alarm can be distinguished by the ODU Power Fail alarmbecause it is different the detection point; the threshold check on the powersupply line is executed inside the ODU.


4 - OPERATING GUIDE

• I2C Fail Alarm for inner I2C communication bus fail.

• IF Tx OLAlarm for fail to the local oscillator of the transmission IF section.The subject signal is available for ODU HP only.

• IF Rx OLAlarm for fail to the local oscillator of the reception IF section.The subject signal is available for ODU HP only.

• MOD FailAlarm for modulator fail.

• RF Tx OLAlarm for fail to the local oscillator of the transmission RF section.

• RF Rx OLAlarm for fail to the local oscillator of the reception RF section.

• Tx BiasAlarm for fail to the bias circuit of the transmission section.The subject signal is available for ODU HP only.

• Tx DetAlarm for fail to the RF transmitter.The detection point of the RF TX power is at the output of the RF transmitter.

4.6.1.2 Functional alarms

Into the Functional Alarms section of the Physical & Functional Alarms window(Fig. 4.84), the system points out the current status of the functional alarms that aresubdivided into the following functional groups:

– Alarms of TX payload (TX Payload)

– Alarms of RX payload (Rx Payload)

– Alarms of tributary (BB 1/2 Tributaries)

– Network alarms (Networks)

For each functional group, the system provides:

– a signalling LED of the resuming alarm relevant to the alarms of the functionalgroup

– a push-button for the displaying with details of the alarms relevant to the functionalgroup.

In case of System Type (1+0), the transceiving chain foresees a single radiochannel; the equipment is equipped with one BB unit and with one ODU.In the other System Types, the transceiving chain foresees two radio channels;the equipment is equipped with two BB units (identified by BB 1 and BB 2) andtwo ODU’s (identified by ODU 1 and ODU 2).


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.6.1.2.1 Alarms of TX payload

To display the alarms relevant to the transmission chain, click on the TX Payloadpush-button into the Functional Alarms field (Fig. 4.84); the push-button displays theTx Functional Alarms window (Fig. 4.96), that resumes the current status of all thetransmission chain relevant to the payload.The Tx Functional Alarms window displays the functional layout of the transmissionchain with the indication of the connection status relevant to each single unit and of thestatus relevant to all the alarms concerning the transmission of the payload.For the BB units, it is available also the Tx Alarms push-button that allows displayingthe single roots of the BB transmission alarm (Fig. 4.97); the Tx Alarms push-button isdeactivated if the BB unit is not On Line.

Fig. 4.96 Tx Functional Alarms

System Type (1+0)


The functional layout of the transmission chain depends on the System Type:– in System Type (1+0), the system displays the equipment equipped with one

BB unit and with one ODU– in the other System Types, it is displayed the equipment equipped with two

BB units (identified with BB 1 and BB 2) and two ODU’s (identified with ODU1 and ODU 2).


4 - OPERATING GUIDE

Fig. 4.97 BB Tx Functional Alarms window

Status signals

– Connection status of the Access unit:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch

– Connection status of the Controller unit:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch

– Connection status of the hardware key:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch

– Connection status of the BB unit:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch

– Connection status of the ODU:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch

Alarm signals

– Alarms of the Access unit• Card Fail

Alarms of unit fail.In normal functioning conditions, the system does not display any signals;with unit on alarm the system displays the following alarm signal: ! Card Fail.

– Alarms of the Controller unit • Card Fail

Alarms of unit fail.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

In normal functioning conditions, the system does not display any signals;with unit on alarm the system displays the following alarm signal: ! Card Fail.

– Alarms of the hardware key• Card Fail

Alarms of hardware key fail.In normal functioning conditions, the system does not display any signals;with unit on alarm the system displays the following alarm signal: ! Card Fail.

– Alarms of the ODU• Card Fail

Alarm of ODU fail.In normal functioning conditions, the system does not display any signals;with unit on alarm the system displays the following alarm signal: ! Card Fail.

– Alarms of the BB unit• Card Fail

Alarm of unit fail.In normal functioning conditions, the system does not display any signals;with unit on alarm the system displays the following alarm signal: ! Card Fail.

• Tx AlarmsTransmission resuming alarm; it is the summarization of the singletransmission alarm roots relevant to the BB unit (Fig. 4.98).

• HW ProtectionIn normal functioning conditions, the system displays the following signal: HWProtection: Not Required.In case of transmission serious alarm, the system requires for the hardwareswitching of the TX channel through the displaying of the signal:! HW Protection: Required.

• Trib LOS Alarm relevant to the absence of the input signal on tributary.It is available an alarm signal for each tributary; for the disabled tributaries,the alarm signals are deactivated.

– Alarms of I/F cable• Card Fail

Alarm of I/F cable fail.In normal functioning conditions, the system does not display any signals; incase of cable interruption/absence or of overload, the system displays the Xsymbol on the cable graphic symbol.

• FERFAlarm for reception fail on the ODU.

– Channel alarms• Tx On Line CH1

Serious alarm on the TX 1 channel.• Tx On Line CH2

Serious alarm on the TX 2 channel.

In case of System Type (1+0), it is present one signal only of channel alarm (“TXOn Line CH”), because the equipment is equipped with one radio channel only.


4 - OPERATING GUIDE

4.6.1.2.2 Alarms of RX payload

To display the alarms relevant to the reception chain, click on the Rx Payloadpush-button into the Functional Alarms field (Fig. 4.84); the push-button displays theRx Functional Alarms window (Fig. 4.98), that resumes the current status of all theentire reception chain.The Rx Functional Alarms window displays the functional layout of the reception chainwith the indication of the connection status relevant to each single unit and of the statusrelevant to all the alarms concerning the reception of the payload..

Fig. 4.98 Rx Functional Alarms window

System Type (1+0)


The functional layout of the reception chain depends on the System Type:– in System Type (1+0), the system displays the equipment equipped with one

BB unit and with one ODUin the other System Types, it is displayed the equipment equipped with two BBunits (identified with BB 1 and BB 2) and two ODU’s (identified with ODU 1 andODU 2).


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE


Status signals

– Connection status of the Access unit:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch

– Connection status of the Controller unit:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch

– Connection status of the memory key:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch

– Connection status of the BB unit:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch

– Connection status of the ODU:• OnL (green): On Line• Dis (red); Disconnected• Con (red): Connected• Mis (red): Mismatch


4 - OPERATING GUIDE

Alarm signals

– Alarms of the Access unit• Card Fail


– Alarms of the Controller unit• Card Fail


– Alarms of the memory key• Card Fail

Alarm of the hardware key fail .In normal functioning conditions, the system does not display any signals;with hardware key on alarm the system displays the following alarm signal: !Card Fail.

– Alarms of the BB unit• Card Fail


• High AlmSerious alarm on the RX channel.The subject signal is present only in case of protected configurations (1+1).

• LOF Alarm for frame loss on aggregate signal at BB level.

• EBER Alarm for high error degree (BER ≥ 10-3) on aggregate signal at BB level.

• EW HighAlarm for “early warning high” condition.

• EW LowAllarme for “early warning low” condition.

• TIMAlarm for error on the link identification code (ID of link received from remoteterminal different from the attended one).

• FEBEAlarm for error on remote terminal block.

• FERFAlarm for reception fail on remote terminal.

• AlignAlarme for alignment error of the hitless logics.The subject signal is present only in case of protected configurations (1+1).

– Alarms of I/F cable• Cable Fail

Alarm of I/F cable fail.In normal functioning conditions, the system does not display any signals; incase of cable interruption/absence or of overload, the system displays the Xsymbol on the cable graphic symbol.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

• LOF Alarm for frame loss on aggregate signal at cable level.

• EBER Alarm for high error degree (BER ≥ 10-3) on aggregate signal at cable level.

• Path Fail Alarm for IDU - ODU path error (detected ODU type different from theexpected one).

– Alarms of ODU • Card Fail

Alarm of ODU fail.In normal functioning conditions, the system does not display any signals;with ODU on alarm the system displays the following alarm signal: ! CardFail.

• RF LOSAlarm for absence of RF RX signal.

• DEM FailAlarm for demodulator fail.

– Channel alarms• AIS Ins CH1

Alarm for AIS presence on the signal of the RX 1 channel (signal availableonly with RX1 channel on line).

• AIS Ins CH2Alarm for AIS presence on the signal of the RX 2 channel (signal availableonly with RX2 channel on line).

4.6.1.2.3 Alarms of tributary

To display the tributary alarms of one BB unit, click on the corresponding BBTributaries push-button into the Functional Alarms field (Fig. 4.84); the subjectpush-button displays the BB Tributaries Functional Alarms window (Fig. 4.99), thatresumes the status of the alarms relevant to all the tributaries of the BB unit.

In case of System Type (1+0), it is present a single alarm signal of channel (“AISIns CH”), because the equipment is equipped with a single radio channel.

In case of System Type (1+0), the equipment is equipped with one BB unit onlytherefore it is present only one push-button for the tributary functional alarms.In the other System Types, the equipment is equipped with two BB units,therefore there are two push-buttons for the tributary alarms: one for thetributaries of the BB 1 unit and the other for the tributaries of the BB 2 one.


4 - OPERATING GUIDE

Fig. 4.99 BB Tributaries Functional Alarms window

Alarm signals

– ConfigAlarm of tributary configuration (input signal present on disabled tributary).

– LOS Alarm for absence of input signal.The alarm signal is deactivated in case of disabled tributary.

– AIS INAlarm for AIS presence on the input signal.The alarm signals is deactivated in case of disabled tributary.

– AIS OUTAlarm for AIS presence on the output signal.The alarm signal is deactivated in case of disabled tributary.

– HDB3Alarm for HDB3 code error on the input signal.The alarm signal is deactivated in case of disabled tributary.

4.6.1.2.4 Network alarms

To display the network alarms, click on the Networks push-button into the FunctionalAlarms (Fig. 4.84); the subject push-button displays the Networks Alarms window(Fig. 4.100), that resumes the alarms of the embedded D channels.

Fig. 4.100 Networks Alarms window

System Type (1+0)

In case of System Type (1+0), it is present only one embedded D channel, while inthe other System Types, there are two embedded D channels respectively calledD1 and D2.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE


Alarm signals

– D-CH IN LOFAlarm for frame loss on input embedded D channel.

– D-CH OUT LOFAlarm for frame loss on output embedded D channel.

4.6.1.3 Resuming signals of the alarm severity

Into the Severity Alarms section of the Physical & Functional Alarms window(Fig. 4.84), the system points out the current status of the resuming signals of the alarmseverity.The alarms are grouped according to the following severity resuming signals:

– Critical: alarm condition that involves the operation ability and that requires for animmediate corrective action.

– Major: alarm condition that involves the operation ability and that requires for anurgent corrective action.

– Minor: alarm condition that involves the operation ability and that requires for theexecution of a corrective action to prevent higher damages.

– Warning: condition of potential alarm or of potential service prevention, detectedbefore it can cause some effects on the system; it is necessary to execute an actionfor an additional diagnosis operation (if it is necessary) and the trouble has to becorrected to prevent that it can cause higher fails.

– Indeterminate: alarm situation with indeterminate character that does not requirefor the execution of corrective or diagnostic actions.

The creation of the resuming signals relevant to the alarm severity depends also on theequipment System Type, because the severity of the single alarm roots can be differentaccording to the situation of equipment in protected or not protected configuration.


4 - OPERATING GUIDE

4.6.2 Station alarms

The Station option of the Alarms menu (Fig. 4.83) displays the Station Alarms window(Fig. 4.101), that shows the status of the station alarms.

Fig. 4.101 Station Alarms window

Alarm signals

– Alarms on input lines (Line IN)These are the alarm signals (Line IN 1 - Line IN 4) relevant to the four input linesavailable for the user for the station local alarms.

– Alarms on output lines (Line OUT)These are the alarm signals (Line OUT 1 - Line OUT 4) rrelevant to the four outputlines available for the user for the station remote alarms.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.7 Measurements MenuThe Measurements menu (Fig. 4.102) provides the following options:

– View: Reading of the RF TX - RX power

– RF RX Power 1: Measurement of the RF RX power for the radio system 1

– RF RX Power 2: Measurement of the RF RX power for the radio system 2.

Fig. 4.102 Measurements menu

System Type (1+0)


4.7.1 Reading of the RF TX - RX power

The View option of the Measurements menu (Fig. 4.102) displays the UnitMeasurements window (Fig. 4.103), that shows the current values of the RF TX and Rxpower of each ODU.

Parameters

– RF Tx Power It displays the current value of the RF TX power, expressed by means of dBm.

– RF Rx Power It displays the current value of the RF RX power, expressed by means of dBm.

In case of System Type (1+0), on the contrary of the situation for the other SystemType, it is available only one option for the measurement of the RF RX power,because the equipment is equipped with one radio system only.

In case of System Type (1+0), it is present one ODU only, while into the otherSystem Types, there are always two ODU’s, identified by ODU 1 and ODU 2.


4 - OPERATING GUIDE

Status/alarm signal

– Connection status of the ODUWith the ODU in On Line status, the system does not display any signal; on thecontrary, it displays the current status of the ODU.The possible configurations are the following ones:• Disconnected • Connected • Mismatch.

– Status of the RF transmitterWith the RF transmitter on normal functioning conditions, the system does notdisplay any signal; in case of silenced RF transmitter, it displays the followingsignal: ! Tx Squelched (signal available only with ODU On Line).

Fig. 4.103 Unit Measurements window

System Type (1+0)


4.7.2 Measurement of the RF RX power

The RF RX Power option of the Measurements menu (Fig. 4.102) runs an applicationprogram of NetViewer/LCT, that allows executing the measurement of the RF RX powerfor the selected radio system.The system saves the data of the measurement on a file for possible subsequentprocessing operations. It is necessary to have at disposal the Microsoft Excel programto be able to display the graphical diagram that shows the time trend of the received RFpower.

The measuring application programs of the RF RX power in NetViewer and in LCThave different characteristics and operating modes. For the description of themeasuring procedure, refer to the operating guide of NetViewer/LCT.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.8 Performance MenuThe Performance menu allows the execution of the analysis and the recording on fileof the performance data.The Performance menu (Fig. 4.104) provides the following options:

– View: Displaying of the performance data

– Record: Recording on file of the perfomance data

– Summary: Summary of the measuring interventions relevant to the perfomancedata

The performance data are parameters of quality and unavailability that allows checkingthe efficiency and the quality of the radio transmission; the quality parameters arecalculated according with the ITU-T G.826 recc.The Rec. G.826 foresees that the calculation of the quality parameters is based uponthe counting of the errored blocks.For the SRAL XD, the frame of the aggregate radio signal (proprietary format) has beenmade equivalent with a block.The performance monitoring is executed only on point-point hops and it is realizedaccording to the base of the direct measurement of the detected “errored blocks”.The approach is a single-direction one, because the two directions of the connection areconsidered as separate ones. In fact, the counting of the quality parameters relevant to the A → B direction of a A - Bconnection is executed for all the periods during which the connection in that directionis available, without taking into account the availability or not of the connection in B →A direction.The performance data are the following ones:

– UAS (Number of Seconds of Unavailability): it provides the unavailability secondsof the connection into a specified observation period.

– SES (Number of Severely Errored Seconds): it represents the seconds duringwhich it is present one of the following conditions:• percentage of errored blocks equal to or higher than 30%• presence of at least a special event called “defect” (the classification of the

“defects” for the PDH systems is the following one: Loss of Signal (LOS),Alarm Indication Signal (AIS), Loss of Frame Alignment (LOF)).

– ES (Number of Errored Seconds): it represents the seconds during which it ispresent at least one errored block.

– BBE (Number of Background Block Errors): it represents the number of erroredblocks into a not SES second.

– OI (Number of Outage Intensity): it is the number of unavailability events into adefined observation interval.

The system foresees two measuring intervals for the performance data:

– interval of quarters of an hour

– interval of 24 hours.

Into the windows, the system shows the counting of the quality parameters (SES, ES,BBE) and of the unavailability ones (UAS, OI) for the current quarter of an hour/24 hoursand for the previous 16 quarter of an hour/4 days.Then, it provides the number of seconds counted into each of the “nominal” quarters of


4 - OPERATING GUIDE

an hour/24 hours: this feature to allow the correct evaluation of the performances seennot as absolute measurement, but as relevant one with respect to a time interval withwell known duration.The time measuring unit is the second.The measurement of the quarter of an hour has the tolerance of ±1 second; themeasurement of the 24 hours has the tolerance of approximately 10 seconds.It is necessary to keep always in mind that it can be present a displacement of themeasurements due to the tolerance of the quartzs equipped into the different units.The inner time reference is provided by the Controllor unit.Usually, it is enabled for the NE the network synchronization. Then, the user can setmanually also the date and time (par. 4.5.4).

Fig. 4.104 Performance menu

4.8.1 Displaying of the performance data

The View option of the Performance menu (Fig. 4.104) displays the SystemPerformance Monitoring View window (Fig. 4.105), that contains the push-buttons forthe displaying of the performance data:

– Quarter: Performance data referred to the quarters of an hour

– Day: Perfomance data referred to the 24 hours.

The composition of the System Perfomance Monitoring View window depends on theequipment System Type.

System Type (1+0)

In case of System Type (1+0), the equipment is equipped with only one radio system,then the measuring points of the single equipped BB unit are activated.Then, the PM View section contains only two Quarter and Day push-buttons for thedisplaying of the performance data.Into the upper part of the window, the system displays the following system information:

– Equipment System Type (System Type)

– System payload capacity (System Capacity).


In case of System Type 2x(1+0) and A/D-Rep, two independent radio links areconnected with the tributary interface then the measuring points of both the BB units areactivated at the same time.Then, the PM View section contains two couples of Quarter and Day push-buttons forthe displaying of the performance data: the first couple refers to the radio system 1 andthe second one to the radio system 2.For each system, it is available also the signal of the connection status relevant to thecorresponding BB unit; the possible displayings are the following ones:


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

– no one displaying: unit On Line

– Dis: Disconnected unit

– Con: Connected unit

– Mis: Mismatch unit.

In the upper part of the window, the system displays the following system information:


– Payload capacity of the radio system 1 (System 1 Capacity)

– Payload capacity of the radio system 2 (System 2 Capacity).

System Type (1+1) H/S e (1+1) FD

In case of System Type (1+1) H/S and (1+1) FD, one radio link only is connected withthe tributary interface then the measuring points of the BB units currently on service areactivated only.Then, the PM View section contains only two Quarter and Day push-buttons for thedisplaying of the performance data.In the upper part of the window, the system displays the following system information:


– Payload capacity of the radio system (System Capacity)

– Activation status of the BB units (Status)The possible displayings are the following ones:• ON• Off.

– Status of the hitless protection on the BB unit (on Line)The possible displayings are the following ones:• CH1: switch hitless on channel 1• CH2: switch hitless on channel 2.

Fig. 4.105 System Performance Monitoring View window

System Type (1+0)


4 - OPERATING GUIDE



4.8.1.1 Performance data referred to the quarters of an hour

To open the window relevant to the performance data referred to the intervals of quarterof an hour (Fig. 4.105), the user has to click on the corresponding Quarter push-buttoninto the PM View section of the System Performance Monitoring View window(Fig. 4.105).The window displays through a table the performance data relevant to the currentquarter of an hour and the ones relevant to the previous sixteen quarters of an hour.The data relevant to the current quarter of an hour (Current Quarter) are into the lastrow of the table.At the beginning of a new measuring intervals, the measurements slides of one positionfrom the bottom towards up, replacing row by row the data relevant to the previousintervals.The Suspect Period column allows the identification of the intervals into which therehave been conditions such as to consider the measured performance data as suspectand then not correct ones; such intervals are marked through the marking symbol !.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Fig. 4.106 System Performance Monitoring on B1 Byte (Quarter)

4.8.1.2 Perfomance data referred to the 24 hours

To open the window of the performance data referred to the 24 hours (Fig. 4.107), theuser has to click on the corresponding Day push-button into the PM View section of theSystem Performance Monitoring View window (Fig. 4.105).The window points out through a table the performance data relevant to the currentinterval of 24 hours and the ones relevant to the previous four intervals of 24 hours.The data relevant to the current interval of 24 hours (Current Day) are into the last rowof the table.At the beginning of a new measuring intervals, the measurements slides of one positionfrom the bottom towards up, replacing row by row the data relevant to the previousintervals.The Suspect Period column allows the identification of the intervals into which therehave been conditions such as to consider the measured performance data as suspectand then not correct ones; such intervals are marked through the marking symbol !.

Fig. 4.107 System Performance Monitoring on B1 Byte (Day)


4 - OPERATING GUIDE

4.8.2 Recording on file of the perfomance data

The B1 Byte options of the Record menu (Fig. 4.108) run an application program ofNetViewer/LCT, that allows executing the recording on file of the perfomance datareferred to the quarters of an hour.The Record menu foresees before the B1 Byte option a selection sub-menu of the radiosystem.The structure of the Record menu depends on the equipment System Type:

– System Type (1+0) It is present only one B1 Byte option for the recording of the performance data,because the equipment is equipped with a single radio system only

– System Type 2x(1+0) e A/D-RepThere are two B1 Byte options for the recording of the perfomance data, the firstone for the radio system 1 and the second one for the radio system 2.

– System Type (1+1) H/S e (1+1) FDThere is only one B1 Byte option for the recording of the perfomance data,because the protected configurations foresee only one radio link connected withthe tributary interface.

Fig. 4.108 Record menu

System Type (1+0), (1+1) H/S, (1+1) FD


For the recording on file fo the performance data procedure refer toNetViewer/LCT Operating Guide.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.8.3 Summary of the measuring interventions relevant to the perfomance data

The Summary option of the Performance menu (Fig. 4.104) displays the EventsPresence Summary window (Fig. 4.109), that shows, into a table, the summary of themeasuring intervals relevant to the performance data.Into the Events Presence Summary window, the system resumes the followinginformation:

– for the performance data referred to the quarters of an hour:• the date and the interval of the 16 previous quarters of an hour (Time

Interval)• the date and the interval of the current quarter of an hour (Current Time)

– for the performance data referred to the 24 hours:• the date of the 4 previous days (Day)• the date of the current day (Current Day).

The Summarization column allows the identification of the intervals where there are theperformance data; such intervals are marked through the symbol X.

Fig. 4.109 Events Presence Summary window


4 - OPERATING GUIDE

4.9 Inventory MenuThe Inventory menu allows accessing to the inventory data (memorized into nonvolatile memories) to read them or to write possible notes (e.g.: installation data,malfunctioning type, etc.) or to execute their download on a file.If the user selects the Inventory menu, the system directly displays the Inventorywindow (Fig. 4.110), that contains all the push-buttons for the access to the inventorydata; the push-buttons are subdivided into the following categories:

– push-buttons of the HW section (par. 4.9.1)

– push-buttons of the SW section (par. 4.9.2)

– Report push-button (par. 4.9.3).

Fig. 4.110 Inventory window

System Type (1+0)


In case of System Type (1+0), the equipment is equipped only with one BB unitand with one ODU.In the other System Types, the equipment is equipped with two BB units(identified with BB 1 and BB 2) and with two ODU’s (identified with ODU 1 andODU 2).


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.9.1 Hardware data

The HW section (Fig. 4.110) is subdivided into two sub-sections:

– PID: PID data

– User: User data

The two sub-sections are symmetric ones because both are provided with the samepush-buttons, one for each equipped units. The composition of the two sub-sections PIDand User depends on the equipment System Type.Then, for each unit, it is available, on the side of the corresponding push-button, thesignal of the connection status; in case of On Line unit, the system does not display anysignal, while on the contrary, it is displayed the current status of the unit.The possible displayings are the following ones:

– Dis: disconnected unit

– Con: connected unit

– Mis: mismatch unit.

4.9.1.1 PID data

For each unit, it is possible to display the hardware identification data (PID), that arememorized into a non volatile memory.To open the window of the unit PID data (Fig. 4.111), it is necessary to click on thecorresponding push-button of the PID section (Fig. 4.110).For each unit, the system provides the following PID data:

– hardware code, with the indication of the extension and of the edition

– serial number

– manufacturer’s code

– equipment code

– unit code

– date of the last change executed on the unit

– place of the last corrective maintenance intervention executed on the unit

– date of the last corrective maintenance intervention executed on the unit.

Fig. 4.111 PID data window (example)


4 - OPERATING GUIDE

4.9.1.2 User data

For each equipment unit, it is possible to insert the user data (information or notes) thatare memorized into a non volatile memory and that can be always re-read.To open the window of the user data relevant to a unit (Fig. 4.112), it is necessary toclick on the corresponding push-button of the User section (Fig. 4.110).To insert/change the user data of a unit, it is necessary to execute the followingprocedure:

– open the window of the unit data relevant to the unit (Fig. 4.112)

– click twice on the data field to open the insertion window (Fig. 4.113)

– insert, through keyboard, the data into the filling-in box and click on OK to confirmthe data insertion.

Fig. 4.112 User data window (example)

Fig. 4.113 Insertion window of the user data

4.9.2 Software data

Into the SW section (Fig. 4.110), the system provides the following push-buttons:

– Equipment: Equipment software data

– LCT: LCT software dataor as an alternative solutionNetViewer: NetViewer software data


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.9.2.1 Equipment software data

The Equipment push-button of the SW section (Fig. 4.110) displays the EquipmentSoftware window (Fig. 4.114), that shows the following software data:

– code, release and build of the software uploaded on the active memory bank of theController unit

– code, release and build of the software uploaded on the standby memory bank ofthe Controller unit

– version of the software running on each equipment hardware module; the list of thehardware modules provided with software depends on the System Type and on theequipping kit of the equipment.

In case of error on the standby bank, the system displays the following signal:Stand-by Bank Status: WRONG !.

Fig. 4.114 Equipment Software window

System Type (1+0)



4 - OPERATING GUIDE

4.9.2.2 LCT software data

The LCT push-button into the SW section (Fig. 4.110) displays the About LCT window(Fig. 4.115), that displays the following software data:

– code of the software for the equipment management

– version of the equipment software plug-in

– version of LCT.

Fig. 4.115 About LCT window

4.9.2.3 NetViewer software data

The NetViewer push-button of the SW section (Fig. 4.110) displays the AboutNetViewer window (Fig. 4.116), that shows the following software data:

– code and version of the equipment software plug-in

– code and version of NetViewer.

Fig. 4.116 About NetViewer window

4.9.3 Report of the inventory data

The Report push-button of the Inventory window (Fig. 4.110) runs an applicationprogram of NetViewer/LCT, that allows executing the report of the inventory data and tosave it on a file.The user can use every text editor to open the report file and to display the inventorydata.

The report applications of the inventory data provided by NetViewer and by LCThave different characteristics and operating modes.For the description of the report procedure, refer to the operating guide ofNetViewer/LCT.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.10 Security MenuThe Security menu allows configuring the parameters relevant to the NE Security, thatdefines the access privileges of the Element Manager towards the equipment.Into the Security window (Fig. 4.117), 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 thedifferent user classes.

The layout of the Security window depends on the SVR of NetViewer/LCT.

The parameters of the Security window can be configured only in case of login withAdmin user class.In case of login a user class different from Admin, the Security window is available inreading only mode (Fig. 4.118).

Fig. 4.117 Security window (read/write mode)

Fig. 4.118 Security window (reading only mode)

The NE Security has to be enabled if two or more Managers (e.g.: NetViewer andLCT) can execute accesses at the same time.


4 - OPERATING GUIDE

4.11 NE Severity in NetViewerInto the network map, the background color of the equipment name points out thesummarized alarm status of the equipment itself that coincides with the highest severityone.The possible severity status of the equipment, in On Line conditions, are the followingones:

– Critical (par. 4.11.1)

– Major (par. 4.11.2)

– Minor (par. 4.11.3)

– Warning (par. 4.11.4)

– Indeterminate (par. 4.11.5)

– Test (par. 4.11.6).

The creation of the alarm resuming signals and then the subsequent NE severity dependon the equipment System Type also, because the seriousness of the single alarm rootscan be different if the equipment is in a protected configuration or in a not protected one.

The management of the NE severity into the network map and the networkapplications is a function of NetViewer, and it is not currently available in LCT.


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.11.1 Alarms with Critical severity

The following tables resumes all the alarms with Critical severity.The creation of the resuming signal of Critical alarm is different if the equipment is inprotected configuration (Tab. 4.5) or in not protected one (Tab. 4.6).

Tab. 4.5 Alarms with Critical severity in protected configuration

Event on Code Description Notes

Controller unit Dis Disconnected unit

Mis Mismatch unit

Configuration Not Congruent with HW

Equipment configuration set via software not congruent with the actual System Type requirements

Access unit Dis Disconnected unit

Mis Mismatch unit

Card Fail Unit fail

Power Fail Absence of the inner voltages Root of the Card Fail alarm

SPI Fail Fail on SPI inner communication bus Root of the Card Fail alarm

I2C Fail Fail on I2C inner communication bus Root of the Card Fail alarm

SW Mismatch Unit software not congruent with the hardware

Root of the Card Fail alarm

Download Failure Error during the download of the unit software


Canali TX Tx On Line CH1 Presence of serious alarm on the TX 1 channel

Tx On Line CH2 Presence of serious alarm on the TX 2 channel


4 - OPERATING GUIDE

Tab. 4.6 Alarms with Critical severity in not protected configuration



Mis Mismatch unit


Equipment configuration and/or set via software not congruent with the actual System type requirements

BB 1 unit Power Supply Absence low battery 1 voltage In System Type (1+0) only; in the other System Types it has Minor severity

Dis Disconnected unit

Mis Mismatch unit

Card Fail Unit fail


ASIC Fail ASIC circuit fail Root of the Card Fail alarm



ODU DC Fail on the control circuit for the ODU power supply






LOF Frame loss on aggregate signal

EBER High error degree (BER ≥ 10-3) on aggregate signal

TIM Error of link identification code (ID of received link different from the expected one)

Trib 1 LOS..

Trib 16 LOS

Absence of signal on tributary 1..

Absence of signal on tributary 16

Tributaries 9..16 not managed by the BB 1 unit in System Type 2x(1+0)


911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

BB 2 unit(not present in System Type (1+0))


Mis Mismatch unit

Card Fail Unit fail















Trib 1 LOS..

Trib 16 LOS




I/F 1 cable Cable Fail Cable fail

Open Cable Interrupted/disconnected cable Root of the Card Fail alarm

Cable Overload Overload on the cable Root of the Card Fail alarm

FERF Reception fail on the ODU

LOF Frame loss on aggregate signal at cable level

EBER High error degree (BER ≥ 10-3) on aggregate signal at cable level

Path Fail IDU - ODU path error (the IDU not detects the ODU)




4 - OPERATING GUIDE

I/F 2 cable(not present in System Type (1+0))

Cable Fail Cable fail

Open Cable Interrupted/disconnected cable Root of the Card Fail alarm

Cable Overload Overload on the cable Root of the Card Fail alarm




Path Fail IDU - ODU path error (the IDU not detects the ODU)

ODU 1 Dis Disconnected ODU

Mis ODU mismatch

SW Mismatch ODU Software not congruent with the hardware

Download Failure Download error of the ODU software

ODU Power Fail Absence of the ODU power supply voltage (detected on the IDU)

ODU µP Alarm Fail for the ODU µP

Card Supply ODU fail

I2C Fail on I2C inner communication bus Root of the Card Fail alarm

Power Fail Absence of the ODU power supply voltage (detected on the ODU)


IF Tx OL Fail of the local oscillator relevant to the IF TX section

Root of the Card Fail alarm; available for ODU HP only

IF Rx OL Fail of the local oscillator relevant to the IF RX section


MOD Fail Modulator fail Root of the Card Fail alarm

RF Tx OL Fail of the local oscillator relevant to the RF TX section


RF Rx OL Fail of the local oscillator relevant to the RF RX section


Tx Bias Fail to the bias circuit of the TX section Root of the Card Fail alarm; available for ODU HP only

Tx Det Fail to the RF transmitter Root of the Card Fail alarm

RF LOS Absence of the RF RX signal

DEM Fail Demodulator fail

Freq Plain Fail Not congruent configuration of the frequency plan




911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

ODU 2(not present in System Type (1+0))

Dis Disconnected ODU

Mis ODU mismatch


Download Failure Error during the download of the ODU software


ODU µP Alarm Fail to the µP of the ODU


I2C Fail on I2C inner communication bus Root of the Card Fail alarm

Power Fail Absence of the ODU power supply voltage (detected inside the ODU)


IF Tx OL Fail of the local oscillator relevant to the IF TX section


IF Rx OL Fail of the local oscillator relevant to the IF RX section



RF Tx OL Fail of the local oscillator relevant to the RF TX section


RF Rx OL Fail of the local oscillator relevant to the RF RX section







Canali TX Tx On Line CH1 Presence of serious alarm on the TX 1 channel

Tx On Line CH2 Presence of serious alarm on the TX 2 channel

Not present in System Type (1+0)




4 - OPERATING GUIDE

4.11.2 Alarms with Major severity

The following tables resume all the alarms with Major severity.The creation of the resuming signal of Major alarm is different if the equipment is inprotected configuration (Tab. 4.7) or in not protected one (Tab. 4.8).


Mis Mismatch unit

Card Fail Unit fail











911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Tab. 4.7 Alarms with Major severity in protected configuration


Hardware key Dis Disconnected hardware key

Mis Hardware key mismatch

Controller unit Card Fail Unit fail



BB 1 unit Dis Disconnected unit

Mis Mismatch unit

Card Fail Unit fail











Align Alignment error of the hitless logics

High Alm Presence of serious alarm on RX channel on service




Trib 1 LOS..

Trib 16 LOS




HW Protection: Required

Request for switching of the TX channel for transmission serious alarm


4 - OPERATING GUIDE

BB 2 unit Dis Disconnected

Mis Mismatch unit

Card Fail Unit fail











Align Alignment error of the hitless logics

High Alm Presence of serious alarm on RX channel on service




Trib 1 LOS..

Trib 16 LOS





Request for switching of the TX channel for transmission serious alarm


Open Cable Interrupted/disconnected cable Root of the Cable Fail alarm

Cable Overload Overload on cable Root of the Cable Fail alarm




Path Fail Error of IDU - ODU path (the IDU not detects the ODU)




911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE








ODU 1 Dis ODU Disconnected

Mis ODU mismatch

SW Mismatch ODU Software not congruent with the hw

Download Failure Error during the download of the ODU sw







IF Tx OL Fail on the local oscillator of the IF TX section


IF Rx OL Fail on the local oscillator of the IF RX section



RF Tx OL Fail on the local oscillator of the RF TX section


RF Rx OL Fail on the local oscillator of the RF RX section










4 - OPERATING GUIDE


Mis ODU mismatch





Card Fail ODU fail


Power Supply Absence of the ODU power supply voltage (detected inside the ODU)







RF Tx OL Fail on the local oscillator of the RF TX section









RX channels AIS Ins CH1 AIS presence on RX 1 channel (only if the channel is On Line)

AIS Ins CH2 AIS presence on RX 2 channel (only if the channel is On Line)




911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

Tab. 4.8 Alarms with Major severity in not protected configuration


Hardware key Dis Disconnected hardware key





BB 1 unit HW Protection: Required

Request for switching of the TX channel due to serious transmission alarm




RX channels AIS Ins CH1 AIS presence on RX 1 channel (only if the channels is On Line)

AIS Ins CH2 AIS presence on RX 2 channel (only if the channels is On Line)

Not available in System Type (1+0)


4 - OPERATING GUIDE

4.11.3 Alarms with Minor severity

The following table resumes the alarms with Minor severity.

Tab. 4.9 Alarms with Minor severity


Hardware key Key E2prom Fail Fail of the EEPROM

BB 1 unit Power Supply Absence and/or low voltage on the battery 1

In System Type (1+0) it has Critical severity


Power Supply Absence and/or low voltage on the battery 2

Embedded D1 channel

D-CH IN LOF Frame loss of the input embedded D1 channel

D-CH OUT LOF Frame loss of the output embedded D1 channel

Embedded D2 channel(not present in System Type (1+0))




911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.11.4 Alarms with Warning severity

The following table resumes the alarms with Warning severity.

Tab. 4.10 Alarms with Warning severity


Hardware key Alignment Fail Serial number of the hardware key different from the one saved into the Controller unit

Access unit Software Not Aligned

Version of the running software on the Access unit different from the version present into the memory of the Controller unit

ODU 1 Software Not Aligned

Version of the running software on the ODU different from the version present into the memory of the Controller unit


Software Not Aligned

Version of the running software on the ODU different from the version present into the memory of the Controller unit

BB 1 unit Software Not Aligned

Version of the running software on the BB unit different from the version present into the memory of the Controller unit

EW High Condition of “early warning high”

EW Low Condition of “early warning low”

FEBE Block error on remote terminal

FERF Reception fail on remote terminal

Trib 1 Config..

Trib 16 Config

Configuration error on tributary 1..

Configuration error on tributary 16


Trib 1 AIS IN..

Trib 16 AIS IN

AIS presence at input on tributary 1..

AIS presence at input on tributary 16


Trib 1 AIS OUT..

Trib 16 AIS OUT

AIS presence at output on tributary 1..

AIS presence at output on tributary 16


Trib 1 HDB3..

Trib 16 HDB3

HDB3 code error on tributary 1..

HDB3 code error on tributary 16



4 - OPERATING GUIDE

4.11.5 Alarms with Indeterminate severity

The following table resumes the alarms with Indeterminate severity.



Version of the running software on the BB unit different from the version present into the memory of the Controller unit





Trib 1 Config..

Trib 16 Config




Trib 1 AIS IN..

Trib 16 AIS IN




Trib 1 AIS OUT..

Trib 16 AIS OUT




Trib 1 HDB3..

Trib 16 HDB3




Tab. 4.11 Alarms with Indeterminate severity


Input lines for station alarms

Line IN 1 Alarm on line 1




Tab. 4.10 Alarms with Warning severity



911-380/02A0330 - Issue 1, October 2003

4 - OPERATING GUIDE

4.11.6 Events with Test severity

The following table resumes the events with Test severity.

Tab. 4.12 Eventi di severità Test


Protection circuit Manual Forced BB Forcing on service, through manual command, of the BB unit and of the TX channel

Available in System Type (1+1) H/S and (1+1) FD only

Manual Forced Channel

Forcing on service, through manual command, of the channel and of the TX channel

Available in System Type (1+1) H/S and (1+1) FD only

BB 1 unit Trib 1 Local Loop..

Trib 16 Local Loop

Local loop command on tributary 1..

Local loop command on tributary 16


Trib 1 Remote Loop..

Trib 16 Remote Loop

Remote loop command on tributary 1..

Remote loop command on tributary 16


Temporary System 1 OFF

Temporary power off of the system, through local command

Temporary condition that automatically ends at the expiring of the set turning off time


Trib 1 Local Loop..

Trib 16 Local Loop

Local loop command on tributary 1..

Local loop command on tributary 16

Tributaries 1..8 not managed by the BB 2 unitin System Type 2x(1+0)

Trib 1 Remote Loop..

Trib 16 Remote Loop

Remote loop command on tributary 1..

Remote loop command on tributary 16

Tributaries 1..8 not managed by the BB 2 unitin System Type 2x(1+0)


Temporary power off of the system, through local command

Temporary condition that automatically ends at the expiring of the set turning off time


4 - OPERATING GUIDE

BLANK PAGE


911-380/02A0330 - Issue 1, October 2003

2 - ALARM MANAGEMENT

2 ALARM MANAGEMENT

2.1 GeneralThe SRA L XD equipment is provided with an alarm system, with different signalingmodes (via software, LED, connector returns), that starting from an alarm signal allowsto the operator to identify quickly the failed module or function. The present document describes all the alarms available for the equipment, subdividingthem as according the functions as according to the different signaling modes.With details, the system points out all the single roots that participate to the creation ofthe alarm resuming signals and the guide lines to be respected for the diagnosticexecuted through service PC. Then, it is described the AIS insertion logics into the 2 Mbit/s tributary streams, as at TXas at RX.

2.2 Alarm Resuming SignalsThe alarms are grouped according to the following severity resuming signals:

– Critical: Alarm condition that involves the operation ability and that requires for animmediate corrective action.

– Major: Alarm condition that involves the operation ability and that requires for anurgent corrective action.

– Minor: Alarm condition that involves the operation ability and that requires for theexecution of a corrective action to prevent higher damages.

– Warning: Condition of potential alarm or of potential service prevention, detectedbefore it can cause some effects on the system; it is necessary to execute an actionfor an additional diagnosis operation (if it is necessary) and the trouble has to becorrected to prevent that it can cause higher fails.

– Indeterminate: Alarm situation with indeterminate character that does not requirefor the execution of corrective or diagnostic actions.

– Test: Equipment in test or manual forcing condition via software.

As connector returns, the system provides also the following alarm resuming signals:

– IDU: summarization of the IDU and of the I/F cable physical alarms.

– ODU: summarization of the ODU physical alarms.

The following tables resume, with reference to the single alarm roots, the activationstatus of the alarm resuming signals; the creation of such signals is different if theequipment is in protected configuration (Tab. 2.1) or in not protected one (Tab. 2.2).



Tab. 2.1 Alarm resuming signals in protected configuration

Event on Code Description

CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU

Access unit Dis Disconnected unit �

Mis Mismatch unit �

Card Fail Unit fail � �

Power Fail Absence of the inner voltages � �

SPI Fail Fail on SPI inner communication bus � �

I2C Fail Fail on I2C inner communication bus � �


� �


� �


Version of the running software on the Access unit different from the version present into the memory of the controller unit

�

Controller unit Dis Disconnected unit �




�




Hardware key Dis Hardware key Disconnected �

Mis Hardware key mismatch �

Alignment Fail Serial number of the hardware key different from the one memorized into the Controller unit

� �

Key E2prom Fail Fail on the EEPROM � �

Lines for station alarms

Line IN 1 Alarm on input line 1 �




Line OUT 1 Alarm on output line 1





911-380/02A0330 - Issue 1, October 2003



�

Dis Disconnected unit �




ASIC Fail ASIC circuit fail � �



ODU DC Fail on the ODU power supply circuit � �

SW Mismatch Software not congruent with the hardware � �


� �

LOF Frame loss on aggregate signal �

EBER High error degree (BER ≥ 10-3) �

TIM Error of link identification code �


Version of the running software on the BB unit different from the version present into the memory of the controller unit

�

EW High Condition of “early warning high” �

EW Low Condition of “early warning low” �

FEBE Block error on remote terminal �

FERF Reception fail on remote terminal �

Align Alignment error of the hitless logics �

High Alm Serious alarm on RX channel �

Trib 1..16 LOS Absence of signal on tributary 1..16 �

Trib 1..16 Config Configuration error on tributary 1..16 �

Trib 1..16 AIS IN AIS presence at input on tributary 1..16 �

Trib 1..16 AIS OUT AIS presence at output on tributary 1..16 �

Trib 1..16 HDB3 HDB3 code error on tributary 1..16 �

Trib 1..16 Local Loop

Local loop command on tributary 1..16 �

Trib 1..16 Remote Loop

Remote loop command on tributary 1..16 �


Temporary system turning off through manual command

�


Switching request of the TX channel for serious transmission alarm

�



CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU



I/F 1 cable Cable Fail Cable fail � �

Open Cable Interrupted/disconnected cable � �

Cable Overload Overload on cable � �

FERF Reception fail on the ODU �


�


�


�

ODU 1 Dis ODU Disconnected �

Mis ODU mismatch �


� �

Download Failure Error during the download of the ODU sw � �


� �

ODU µP Alarm Fail on µP of the ODU � �

Card Supply ODU fail � �



� �


� �


� �

MOD Fail Modulator fail � �

RF Tx OL Fail on the local oscillator of the RF RX section

� �


� �

Tx Bias Fail to the bias circuit of the TX section � �

Tx Det Fail to the RF transmitter � �

RF LOS Absence of the RF RX signal �

DEM Fail Demodulator fail �


�


Version of the running software on the ODU different from the one present into the memory of the Controller unit

�



CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU


911-380/02A0330 - Issue 1, October 2003



�











� �





Version of the running software on the BB unit different from the one present into the memory of the Controller unit

�





Align Alignment error of the hitless logics �

High Alm Serious alarm on RX channel �












�



�



CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU








�


�


�



SW Mismatch ODU Software not congruent with the hw � �



� �

ODU µP Alarm Fail on µP of the ODU � �




� �


� �


� �



� �


� �






�



�



CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU


911-380/02A0330 - Issue 1, October 2003


Protection circuits Manual Forced BB Forcing of the BB unit and of the TX channel on service, through manual command

�

Manual Forced Channel

Forcing of the RX channel on service, through manual command

�

TX 1 channels Tx On Line CH1 Presence on serious alarm on the TX 1 channel on service

�

TX 2 channels Tx On Line CH2 Presence on serious alarm on the TX 2 channel on service

�

RX channels 1 AIS Ins CH1 AIS presence on RX 1 channel (only if the channel is on line)

�

RX channels 2 AIS Ins CH2 AIS presence on RX 2 channel (only if the channel is on line)

�

Embedded D1 channel

D-CH IN LOF Frame loss on input D1 channel �

D-CH OUT LOF Frame loss on output D1 channel �

Embedded D2 channel



R interface R1 Protocol error alarm on R interface

D1 interface D1 Protocol error alarm on D1 interface of the Controller




CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU



Tab. 2.2 Alarm resuming signals in not protected configuration


CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU

Access unit Dis Disconnected unit �







� �


� �


Version of the running software on the Access unit different from the one present into the memory of the Controller unit

�

Controller unit Dis Disconnected unit �




�




Hardware key Dis Hardware key Disconnected �

Mis Hardware key mismatch �

Alignment Fail Serial number of the hardware key different from the one memorized into the Controller unit

� �

Key E2prom Fail Fail on the EEPROM � �

Lines for station alarms










911-380/02A0330 - Issue 1, October 2003


BB 1 unit Power Supply Absence and/or low voltage on the battery 1 (in System Type (1+0) it has Critical severity)

� �











� �






�
















�



�



CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU








�


�


�






� �

ODU µP Alarm Fail on the µP of the ODU � �




� �


� �


� �



� �


� �






�



�



CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU


911-380/02A0330 - Issue 1, October 2003




� �











� �






�
















�



�



CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU




Cable Fail Cable fail � �





�


�


�


Dis ODU Disconnected �





� �

ODU µP Alarm Fail on the µP of the ODU � �




� �


� �


� �



� �


� �






�



�



CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU


911-380/02A0330 - Issue 1, October 2003


TX 1 channel Tx On Line CH1 Presence on serious alarm on the TX 1 channel on service

�

TX 2 channel(not present in System Type (1+0))

Tx On Line CH2 Presence on serious alarm on the TX 2 channel on service

�

RX 1 channel AIS Ins CH1 AIS presence on RX 1 channel (only if the channel is on line)

�

RX 2 channel(not present in System Type (1+0))

AIS Ins CH2 AIS presence on RX 2 channel (only if the channel is on line)

�

Embedded D1 channel






R1 interface R1 Protocol error alarm on R1 interface

R2 interface(not present in System Type (1+0))

R2 Protocol error alarm on R2 interface





CRI

MAJ

MIN

WAR

IND

TEST

IDU

ODU



2.3 Alarm Signal via SoftwareThe following table points out all the single alarm root concerning the equipmentfunctioning and available via software, subdivided according to function.

2.3.1 Physical alarm

Tab. 2.3 resumes all the physical alarms available via software.

Tab. 2.3 Physical alarms


Access unit Card Fail Unit fail












Card Fail Unit fail












911-380/02A0330 - Issue 1, October 2003




Card Fail Unit fail




I2C Fail Fail on I2C inner communication bu Root of the Card Fail alarm







ODU 1 SW Mismatch ODU Software not congruent with the hw

Download Failure Error during the download of the ODU sw


ODU µP Alarm Fail on µP of the ODU
























ODU µP Alarm Fail on µP of the ODU























Hardware key Alignment Fail Serial number of the hardware key different from the one memorized into the Controller unit

Key E2prom Fail Fail on the EEPROM




911-380/02A0330 - Issue 1, October 2003


2.3.2 TX alarms

Tab. 2.4 resumes all the alarms relevant to the transmission section available viasoftware.

Tab. 2.4 TX alarms



Mis Mismatch unit

Card Fail Unit fail

Hardware key Dis Hardware key Disconnected


Card Fail Avaria Hardware key


Mis Mismatch unit

Card Fail Unit fail


Mis Mismatch unit

Card Fail Unit fail

Tx Alarms Transmission resuming fail



Root of the Tx Alarms

Trib 1 LOS..

Trib 16 LOS



Roots of the Tx Alarm; the tributaries 9..16 are not managed by the BB 1 unit in System Type 2x(1+0)



Mis Mismatch unit

Card Fail Unit fail

Tx Alarms Transmission resuming fail



Root of the Tx Alarms

Trib 1 LOS..

Trib 16 LOS



Roots of the Tx Alarm; the tributaries 1..8 are not managed by the BB 2 unit in System Type 2x(1+0)









Mis ODU mismatch

Card Fail ODU fail


Dis ODU Disconnected

Mis ODU mismatch

Card Fail ODU fail

TX channels Tx On Line CH1 Presence of serious alarm on TX 1 channel

Tx On Line CH2 Presence of serious alarm on TX 2 channel Not present in System Type (1+0)

Tab. 2.4 TX alarms



911-380/02A0330 - Issue 1, October 2003


2.3.3 RX alarms

Tab. 2.5 resumes all the alarms relevant to the reception section available via software.

Tab. 2.5 RX alarms



Mis Mismatch unit

Card Fail Unit fail

Hardware key Dis Hardware key Disconnected


Card Fail Avaria Hardware key


Mis Mismatch unit

Card Fail Unit fail

RX channels AIS Ins CH1 AIS presence on RX 1 channel (only if the channel in on line)

AIS Ins CH2 AIS presence on RX 2 channel (only if the channel in on line)

Not available in System Type (1+0)


Mis Mismatch unit

Card Fail Unit fail

Align Alignment error of the hitless logics Available only in the System Type (1+1)

High Alm Presence of serious alarm on RX channel Available only in the System Type (1+1)






EBER High error degree (BER ≥ 10-3) su segnale aggregato






Mis Mismatch unit

Card Fail Unit fail

Align Alignment error of the hitless logics Available only in the System Type (1+1)

High Alm Presence of serious alarm on RX channel Available only in the System Type (1+1)


















Mis ODU mismatch

Card Fail ODU fail




Dis ODU Disconnected

Mis ODU mismatch

Card Fail ODU fail



Tab. 2.5 RX alarms



911-380/02A0330 - Issue 1, October 2003


2.3.4 Tributary alarms

Tab. 2.6 resumes all the alarms relevant to the reception section available via software.

Tab. 2.6 Tributary alarms


BB 1 unit Trib 1 Config..

Trib 16 Config




Trib 1 LOS..

Trib 16 LOS




Trib 1 AIS IN..

Trib 16 AIS IN




Trib 1 AIS OUT..

Trib 16 AIS OUT




Trib 1 HDB3..

Trib 16 HDB3





Trib 1 Config..

Trib 16 Config




Trib 1 LOS..

Trib 16 LOS




Trib 1 AIS IN..

Trib 16 AIS IN




Trib 1 AIS OUT..

Trib 16 AIS OUT




Trib 1 HDB3..

Trib 16 HDB3






2.3.5 Network alarms

Tab. 2.7 resumes all the network alarms available via software.

2.3.6 Station alarms

Tab. 2.8 resumes all the station alarms available via software.

Tab. 2.7 Network alarms


Embedded D1 channel






R1 interface R1 Protocol alarm on R1 interface Not present in System Type (1+0), (1+1) H/S, (1+1) FD

R2 interface R2 Protocol alarm on R2 interface

D1 interface D1 Protocol alarm on D1 interface of the Controller

D2 interface D2 Protocol alarm on D2 interface of the Controller

Tab. 2.8 Station alarms


Input lines for station alarms

Line IN 1 Alarm on input line 1 (CEN-IN 1)




Output lines for station alarms

Line OUT 1 Alarm on output line 1 (CEN-OUT 1)



Line OUT 4 Alarm on output line 4 (CEN-OUT a)


911-380/02A0330 - Issue 1, October 2003


2.4 Alarm Signalling LED’sTab. 2.9 resumes all the alarm signalling LED’s present on the front panels of the IDUunits.

Tab. 2.9 Alarm signalling LED’s

Unit LED Color Description

Controller unit ∆\ Red Unit fail (Card Fail alarm)

C/MJ Red Critical or Major resuming alarm

MN/W Red Minor or Warning resuming alarm

TEST YellowTest or manual forcing condition via software

Access unitGreen

Inserted power supply voltage (main breaker on “ON”)

Red Unit fail (Card Fail alarm)

BB 1 unit ∆\ Red Unit fail (Card Fail alarm)

ODU RedODU alarm (summarization of the ODU alarms or disconnected ODU )

CBL

Yellow I/F cable disconnected/interrupted

Red Overload on I/F cable

FlashingIDU - ODU interface alarm (summarization of the FERF, LOF, EBER and Path Fail cable alarms)


∆\ Red Unit fail (Card Fail alarm)

ODU RedODU alarm (summarization of the ODU alarms or disconnected ODU)

CBL

Yellow I/F cable disconnected/interrupted

Red Overload on I/F cable

FlashingIDU - ODU interface alarm (summarization of the FERF, LOF, EBER and Path Fail cable alarms)



2.5 Connector Returned AlarmsTab. 2.10 resumes all the alarms available as returns on the equipment “ALMs”connector.

Tab. 2.10 Connector returned alarms

Alarm Description

ALIM OFF Alarm for power supply absence

CRITICAL Critical resuming alarm

MAJOR Major resuming alarm

MINOR/WARNING Minor or Warning resuming alarm

TEST Inner alarm

IDU IDU and/or I/F cable alarm

ODU ODU alarm

CEN-OUT 1 Line 1 for transported alarm output (from remote)




CEN-IN 1 Line 1 for transported alarm input (from remote)





911-380/02A0330 - Issue 1, October 2003


2.6 AIS logicsThe AIS insertion consists of filling all the tributary streams with a signal composed byall “1”.The AIS insertion, as at TX as at RX, is managed by the BB units.

2.6.1 AIS insertion in TX

At trasmission, there is the AIS insertion on the tributary stream when the BB unitdetects the absence of signal on the input tributary (TRIB LOS alarm).

2.6.2 AIS insertion in RX

The AIS insertion logics on the tributary streams at reception are the following one:

– Protected configurationThe system executes the AIS insertion when the BB unit on service detects one ofthe following alarm conditions:• ODU Demodulator fail (DEM Fail alarm) with switch hitless switched on local

RX channel• Frame loss on aggregate signal (LOF alarm) with switch hitless switched on

local RX channel• High error degree (BER ≥ 10-3) on aggregate signal (EBER alarm) and BB

unit itself on service• Error of link identification code (TIM alarm) and BB unit itself on service.

– Not protected configurationThe system executes the AIS insertion when the BB unit on service detects one ofthe following alarm conditions:• ODU demodulator fail (DEM Fail alarm)• Frame loss on aggregate signal (LOF alarm)• High error degree (BER ≥ 10-3) on aggregate signal (EBER alarm)• Error of link identification code (ID of received link different from the expected

one) (TIM alarm).



BLANK PAGE


911-380/02A0330 - Issue 1, October 2003

PRINTED in ITALY

SRA L XD (IDU Plug-in)SVR 3.3

Operating Manual (OMN)

D.45 D.55

D.25

D.30

D.20

SRA L XD (IDU Plug-in)

SVR 3.3

911-380/02A0330 Issue 1, October 2003


SVR 3.3


911-380/02A0330 Issue 1, October 2003


SVR 3.3


911-380/02A0330 Issue 1, October 2003SRA L XD (IDU Plug-in)

SVR 3.3

911-380/02A0330 Issue 1, October 2003SRA L XD (IDU Plug-in)

SVR 3.3


911-380/02A0330 Issue 1, October 2003



911-380/02A0330 Issue 1, October 2003

Documents

Saral Alarms Notes