Linkra

CIPHOP IP
Medium Capacity Ethernet Over Radio System

Release 3.2
OMN
ZZZA500007AC PQ A Ed. 03
March 23, 2012
Copyright (C) LINKRA 2012
a COMPEL GROUP COMPANY
Technical modifications are possible.

Technical specifications and features are binding only insofar as they are specifically and expressly
agreed upon in a written contract.
All rights reserved. Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from LinKra.
Other product and brand names are trademarks of their respective owners.
ZZZA500007AC PQ A - ed. 03
page 1 of 88
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from LinKra. Other product and brand names are trademarks of their respective owners.
Operators Manual
Contents
1.
Foreword.....................................................................................................................................6
1.1.
Customer documentation organization........................................................................................ 6
1.2.
Handbook applicability ................................................................................................................. 7
1.3.
Purpose of the document ............................................................................................................... 7
1.4.
Handbook structure....................................................................................................................... 8
1.5.
Regulatory issues............................................................................................................................ 8
1.5.1.
Use of Unlicensed Bands......................................................................................................... 8
1.5.2.
Use of Equipments in EU countries ........................................................................................ 9
1.5.3.
Declarations and Marking ..................................................................................................... 12
1.6.
Handbook history......................................................................................................................... 12
2.
Functions and Handling of the Craft Terminal (CT) ...........................................................13

2.1.
Overview ....................................................................................................................................... 13
2.2.
Hardware and Software Configuration ..................................................................................... 15
2.3.
Installation .................................................................................................................................... 15
2.4.
Getting the Connection................................................................................................................ 15
2.5.
Setting Date and Time ................................................................................................................. 18
2.6.
CT Screen Layout ........................................................................................................................ 18
2.7.
Main Window ............................................................................................................................... 19
2.7.1 Summary System Status ............................................................................................................ 20
2.7.2 Main Menu................................................................................................................................. 21
2.7.3 System Status............................................................................................................................. 22
2.8.
Radio Interface............................................................................................................................. 25
2.8.1 Radio Frequency Seeker ............................................................................................................ 27
2.9.
Ethernet Interface ........................................................................................................................ 29
2.10. TDM Interface.............................................................................................................................. 31
2.11. System Settings............................................................................................................................. 35
2.12. Inventory and Housekeeping ...................................................................................................... 40
2.13. Logs ............................................................................................................................................... 41
2.14. Statistics ........................................................................................................................................ 43
2.15. Performances................................................................................................................................ 45
2.16. Configuration Files....................................................................................................................... 49
2.16.1
Backup................................................................................................................................... 49
2.16.2
Restore................................................................................................................................... 49
2.17. External Links .............................................................................................................................. 50
2.18. Admin............................................................................................................................................ 51
2.18.1
Upgrade ................................................................................................................................. 51
2.18.2
Change Password .................................................................................................................. 52
2.18.3
Logout ................................................................................................................................... 53
2.19. Export Tx and Rx Power Data to OS ......................................................................................... 53
3.
4.
Perform Configuration by CT ................................................................................................55

Supervision by RCT or OS......................................................................................................68
4.1
4.2
4.3
4.4
4.5
5.
General.......................................................................................................................................... 68
Configuring the equipment connected to RCT or OS .............................................................. 68
Working with the RCT ................................................................................................................ 69
Working with the OS ................................................................................................................... 69
Recovery from abnormal conditions .......................................................................................... 69
Fault Management ...................................................................................................................70

5.1
5.2
5.3
General Fault Management Functions....................................................................................... 70

Equipment and Transmission Alarm List ................................................................................. 71
Replacing Faulty Parts ................................................................................................................ 74
Page 2 of 88
6.
Replacing the ODU.................................................................................................................... 74

Replacing the IDU (PSE or IDUnE1 configurations)............................................................... 77
Safety Rules and Precautions..................................................................................................79

6.1
First Aid for Electric Shocks....................................................................................................... 79
6.2
Artificial Respiration ................................................................................................................... 79
6.3
Treatment of Burns...................................................................................................................... 80
6.4
Safety Rules .................................................................................................................................. 80
6.4.1 General Rules............................................................................................................................. 80
6.4.2 Warnings for the electrical safety .............................................................................................. 81
6.4.3 Microwave radiations ................................................................................................................ 81
6.4.4 Dangerous materials .................................................................................................................. 81
6.5
ESDS Precautions ........................................................................................................................ 81
7.
Annex - Front Panel and Connectors.....................................................................................83

7.1
7.2
7.3
7.4
7.5
8.
PSE Front Panel ........................................................................................................................... 83

IDUnE1 Front Panel .................................................................................................................... 83
AC/DC Front Panel..................................................................................................................... 83
General Connectors ..................................................................................................................... 84
E1 Connectors (only on IDUnE1) ............................................................................................... 86
List of abbreviations ................................................................................................................87
ZZZA500007AC PQ A - Ed. 03
Page 3 of 88
5.3.1
5.3.2
Figures
Figure 2.1-1: Reference Configuration for IDUnE1 and PSE ...........................................................14
Figure 2.4-1: Login Window .............................................................................................................16
Figure 2.4-2: Login Window - Alerts ................................................................................................17
Figure 2.6-1: CT screen functional areas ...........................................................................................18
Figure 2.7-1: Main Window (configuration with PSE or PoE) .........................................................20
Figure 2.8-1: Radio Interface Window ..............................................................................................25
Figure 2.8-2: Radio Frequency Seeker window for Unlicensed Bands .............................................28
Figure 2.9-1: Ethernet Interface window ...........................................................................................29
Figure 2.10-1: TDM window .............................................................................................................32
Figure 2.11-1: System Settings window ............................................................................................35
Figure 2.12-1: Inventory and Housekeeping window.......................................................................40
Figure 2.13-1: Logs window..............................................................................................................42
Figure 2.13-2: Pop-up window for file export ...................................................................................43
Figure 2.14-1: Statistics window .......................................................................................................43
Figure 2.15-1: Performances window: Radio Link............................................................................46
Figure 2.15-2: Performances window: Rx Power.............................................................................46
Figure 2.16-1: Pop-up window opened to perform MIB Back-up....................................................49
Figure 2.16-2: Pop-up window opened to perform MIB Restore .....................................................50
Figure 2.17-1: Upgrade window ........................................................................................................51
Figure 2.17-2: SW Download pop-up window..................................................................................52
Figure 2.17-3: Change Password window .........................................................................................53
Figure 5.3-1: Configuration Module position ....................................................................................76
Figure 6.2-1: Artificial respiration procedure (1/4) ...........................................................................79
Figure 7.1-1: PSE Front Panel and Connectors ................................................................................83
Figure 7.2-1: IDUnE1 Front Panel and Connectors..........................................................................83
Figure 7.3-1: AC/DC Front Panel and Connectors ..........................................................................83
Figure 7.4-1: Scheme of RJ45 Wire Pair Colour ..............................................................................84
Figure 7.4-2: Power Connector (-48 V Battery) ..............................................................................85
Figure 7.5-1: E1 Connector (SCSI HD68 120 balanced).........................................................86
Page 4 of 88
Table 1-1: CIPHOP IP .........................................................................................................................7

Table 1-2: EU countries list where equipments CIPHOP IP 6/7 GHz may operate ............................9
Table 1-3: EU countries list where equipments CIPHOP IP 8 to 13 GHz may operate....................10
Table 1-4: EU countries list where equipments CIPHOP IP 15 to 26 GHz may operate ..................11
Table 2-5: Parameters displayed in the System Status - Settings ......................................................23
Table 2-6: Status and Alarm information displayed in the System Status - Alarms .........................24
Table 2-7: Parameters displayed in the Radio Interface Radio Info ...............................................26
Table 2-8: Parameters displayed in the Radio Interface Radio Configuration ...............................27
Table 2-9: Ethernet Interfaces supported for each configuration ......................................................29
Table 2-10: Ethernet Interface parameters.........................................................................................30
Table 2-11: TDM parameters to manage E1 ports and connections..................................................33
Table 2-12: System Settings parameters............................................................................................38
Table 2-13: System Settings parameters (contd) ...............................................................................39
Table 2-14: Data recorded for each Statistics set of counters............................................................44
Table 2-15: Counters reported by the Performances Radio Link ...................................................48
Table 2-16: Counters reported by the Performances Rx Power......................................................48
Table 3-17: System Configuration .....................................................................................................55
Table 3-18: System Configuration (optional features) ......................................................................56
Table 3-19: Setting the Radio Channel (Licensed Bands)................................................................57
Table 3-20: Estimation of radio Interferences from other systems - Unlicensed Bands ...................58
Table 3-21: Scan results display of the Frequency Seeker ................................................................59
Table 3-22: Setting the Radio Channel (manually) - Unlicensed Bands ...........................................59
Table 3-23: Setting Radio Channel (using Radio Frequency Seeker) - Unlicensed Bands ...............60
Table 3-24: Setting Radio Channel (using Radio Frequency Seeker) - Unlicensed Bands ...............61
Table 3-25: Ethernet Data Interface configuration ............................................................................62
Table 3-26: Provisioning a E1 circuit (Transparent Transport of an Unframed E1) .........................63
Table 3-27: Provisioning a E1 circuit (Transparent Transport of an Unframed E1) .........................64
Table 3-28: Disconnecting or deleting an existing E1 circuit...........................................................65
Table 3-29: Provisioning a NxE0 circuit between Framed E1 (cont.)...............................................66
Table 3-30: Provisioning a NxE0 circuit between Framed E1 (cont.)...............................................67
Table 3-31: Deleting an existing NxE0 circuit ..................................................................................67
Table 5-32: Internal Alarm Contacts .................................................................................................71
Table 5-33: Housekeeping Contacts ..................................................................................................71
Table 5-34: Housekeeping Alarms ....................................................................................................71
Table 5-35: Alarm List (Ethernet Interface, Equipment and others) .................................................72
Table 5-36: Alarm List (Radio Interface) ..........................................................................................73
Table 5-37: Alarm List (TDM Alarms) .............................................................................................74
Table 7-38: ODU External Interface (RJ45 waterproof connector) ..................................................84
Table 7-39: Interface to ODU (PoE connector RJ45).....................................................................84
Table 7-40: Interface to the Network (User) (eth connector RJ45) ...............................................85
Table 7-41: Alarm and Housekeeping Interface (9-pins Sub-D male connector) .............................85
Table 7-42: LCT Interface (lct connector RJ45)...........................................................................85
Table 7-43: E1 Interface (SCSI HD68 120 balanced) ..............................................................86
Page 5 of 88
Tables
1.
1.1.
Foreword
Customer documentation organization
The Customer Documentation for CIPHOP IP Medium Capacity Ethernet over Radio System
is subdivided into the following documents:
ZZZA500005AC PN A
Technical Description (TED)
The Technical Description TED gives an overview of the application, composition, performance,
features, interfaces, functions and maintenance of the CIPHOP IP product.
It also contains the most important technical data.
The Technical Description does not contain any instructions to be carried out.
ZZZA500006AC PP A
Installation and Test Manual (ITMN)
The Installation and Test Manual ITMN contains instructions about mounting, connecting and
commissioning the CIPHOP IP product, connecting and commissioning the CT operating terminals.
Any work using the Installation and Test Manual ITMN presumes knowledge of the Operators
Manual OMN.
ZZZA500007AC PQ A
Operators Manual (OMN)
The Operators Manual document provides information on how to operate, monitor and maintain
the CIPHOP IP product using the Element Manager software (Application Software) running on the
CT operating terminal.
In addition to Graphical User Interface (GUI) window descriptions and task instructions, the
Operators Manual describes remedial actions to be followed in the case of alarms.
Page 6 of 88
Handbook applicability
This handbook is applicable to the following products of CIPHOP IP listed in Table 1 -1:
Title
System CIPHOP IP
Part Number
PRAM000001xx
Comment
CIPHOP 905 IP FL
PRAM000029xx
CIPHOP 905 IP
PRAM000015xx
CIPHOP 906 IP
PRAM000002xx
CIPHOP 907 IP
PRAM000003xx
CIPHOP 908 IP
PRAM000023xx
CIPHOP 910 IP
PRAM000004xx
CIPHOP 913 IP
PRAM000005xx
CIPHOP 915 IP FL
PRAM000030xx
CIPHOP 915 IP
PRAM000006xx
CIPHOP 917 IP FL
PRAM000026xx
CIPHOP 917 IP
PRAM000007xx
CIPHOP 918 IP
PRAM000008xx
CIPHOP 923 IP FL
PRAM000031xx
CIPHOP 923 IP
PRAM000025xx
CIPHOP 924 IP
PRAM000009xx
CIPHOP 926 IP FL
PRAM000032xx
CIPHOP 926 IP
Table 1-1: CIPHOP IP

Moreover the present edition of the document is valid for the following Software Package (SWP)
versions:
Title
SW Package
1.3.
Part Number
SWAA000235AC
Comment
SWP CIPHOP IP Release 3.2
Purpose of the document
The document aims at providing information how to operate and maintain CIPHOP IP system in
the field, to be used by the customer together with the other manuals (Installation and Test Manual
and Technical Manual) to manage in the most effective way the product.
Page 7 of 88
1.2.
1.4.
Handbook structure
The handbook is structured in the basic parts :

Handbook guide part: providing information about the document (chap. 1)
Functions and handling of the Operating Terminal (CT) part: giving information and
instructions how to operate the system by the CT (chap.2)
How to perform the most common configuration actions part: giving the procedures
most commonly required to configure the system (chap. 3)
How to control the system remotely part: describing how the system can be controlled
by a remote location either by a remote CT or an OS (chap. 4)
Fault Management part: dedicated to alarms and consequent actions useful for
maintenance purposes (chap. 5)
Safety Rules and Precautions summarized in chap. 6
1.5.
Regulatory issues
1.5.1. Use of Unlicensed Bands

Special regulations apply to the use of CIPHOP 905 IP, CIPHOP 917 IP and CIPHOP 924 IP in the
unlicensed frequency bands 5470 5725 MHz, 17,1 17,3 GHz and 24,00 24,25 GHz in EU
countries: specifically they must conform to the applicable regulations for the Equivalent Isotropic
Radiated Power (EIRP) and therefore the Max allowed Transmit Power is equal to EIRP limit antenna gain + cable loss.
Limits of EIRP and applicable regulations are shown on ERC/REC 70-03:
100mw (+ 20dBm) for frequency band 17,1 17,3GHz and 24,00 24,25GHz
1W (+30dBm) for frequency band 5470 5725MHz
Operators should note that regulations are subject to change.
In order to be compliant with such regulations Linkra strongly suggests:
1) to use antennas with diameter equal or less than 0.3m (0,99ft) for CIPHOP 917 IP while for
CIPHOP 924 IP the antenna diameters must be equal or less than 0.2m (0,66ft).
2) that the minimum and maximum operating frequency for CIPHOP 917 IP and CIPHOP 924 IP
should be between the values shown in the below table:
CS
CIPHOP 917 IP
CIPHOP 924 IP
3,5 MHz
7 MHz
14 MHz
28 MHz
F min MHz
F max MHz
F min MHz
F max MHz
F min MHz
F max MHz
F min MHz
F max MHz
17106,75
24006,75
17293,25
24243,25
17108,50
24008,50
17291,50
24241,50
17112,00
24012,00
17288,00
24238,00
17119,00
24019,00
17281,00
24231,00
CIPHOP 905 IP equipment may be used in the following EU states and EFTA countries (lists of
countries as for ISO3166 2 letter code):
AT, BE, BG, CZ, CY, DK, EE, FI, FR, DE, GR, HU, IS, IE, IT, LV, LI, LT, LU, MT, NL, NO, PL, PT,
RO, SK, SI, ES, CH, SE, GB, BA, GE, HR, MK, ME, RS, TR.
(RU, UA, limited implementation).
AT, BG, DK, EE, FI, GR, IS, IE, IT, LV, LI, LT, MT, NL, NO, PL, PT, RO, CH, SE, BA, HR, MK, ME,
RS.
(CZ, HU, planned).
(GE, limited implementation).
AT, BE, BG, CZ, CY, DK, EE, FI, DE, GR, HU, IS, IE, IT, LV, LI, LT, LU, MT, NL, NO, PL, PT, RO,
SK, SI, ES, CH, SE, BA, GE, HR, MK, ME, RS, TR, UA.
(FR, GB, limited implementation).
(Annexes 1 & 3: date 6 August 2010)
Page 8 of 88
In the Tables 1-2, 1-3 and 1-4 list of the EU countries where the CIPHOP IP equipments may
operate Y=Yes (lists of countries as for ISO3166 2 letter code):
Table 1-2: EU countries list where equipments CIPHOP IP 6/7 GHz may operate
Page 9 of 88
1.5.2. Use of Equipments in EU countries
Table 1-3: EU countries list where equipments CIPHOP IP 8 to 13 GHz may operate
Page 10 of 88
Page 11 of 88
Table 1-4: EU countries list where equipments CIPHOP IP 15 to 26 GHz may operate
1.5.3. Declarations and Marking

Hereby, Linkra S.r.l , declares that this CIPHOP 900 IP system is in compliance with the essential
requirements and other relevant provisions of Directive 1999/5/EC.
The declaration of conformity may be consulted at www.Linkra.it
Equipment marking (CE-Marking, NB-Identification Number, Alert-sign).
All the equipment except the CIHOP917 IP are marked as follow:
CIPHOP 917 IP is marked as follow:
0682
1.6.
Handbook history
In this paragraph there is shown the history of technical handbook document across the
successive editions with reference to the main chapters.
Cpt
Handbook edition
01 02 03 04 05
Foreword
Functions and handling of the Craft Terminal (CT)
Perform configuration by CT
Supervision by RCT or OS
Fault Management
Safety Rules and Precautions
Annex Front Panel and Connectors
Legenda : n=new part
Page 12 of 88
m = modified part
blank= unchanged part
Functions and Handling of the Craft

Terminal (CT)
Introductory Note
The current Manual supports equipment running Rel. 3.2 and replaces the previous Manuals
supporting Rel. 3.0 and 3.1. From this Release the CT presentation has been significantly changed
using more modern SW technology to support screen presentation, with the purpose to make more
user friendly the use of CT and to increase the CT capabilities with the addition of new functions.
The new CT is therefore quite different from the previous versions and in case of migration to
Rel. 3.2 proper operator training has to be planned.
2.1.
Overview
The equipment can be used in four configurations using:

1) IDU16E1 or IDU8E1 (jointly referred to as IDUnE1): the ODU is connected to an Indoor Unit
providing both a FE User Interface and 16 or 8 E1 Interfaces. These configurations allow
for a mixed PDH and Data Service
2) PSE: the ODU connected to a PSE providing a FE User Interface for Data Service only
3) PoE: the ODU is directly connected to the User equipment using a PoE device
In both cases 1) and 2) the Indoor Unit (either IDUnE1or PSE) provides to the system:
power feeding
interface for a LCT locally connected to the equipment
visual indications (LED) and housekeeping signals
In case 3) the power feeding is provided by the PoE device and no local LCT or visual indications
are available.
In the following reference is made to the configuration as shown in Fig. 2.1-1.
The PC (Operating Terminal) can be connected in Local Mode (LCT) to the LCT port on PSE or to
the LCT port on IDUnE1 to supervise the local terminal of the radio link (local terminal) or the
remote terminal of the link (remote terminal).
It is possible to configure the system to be supervised:
- by CT only: in this case the SNMP interface is inhibited and cannot control the equipment
- by OS and CT: an OS (connected via SNMP protocol) and CT work simultaneously and
there is no exclusion rule between the two.
Page 13 of 88
2.
10/100 FE
user
interface
Remote
Terminal
ODU
Radio Channel: 3.5/7/14/28 MHz
PSE
E1
(max 16)
ODU
IDUnE1
Local
Terminal
10/100 FE
user
interface
LCT
LCT Port
LCT
IP Network
IP Network
TMN
TMN routed
via IP network
OS
Terminal equipped
with IDUnE1
RCT routed
via IP
network
Terminal equipped
with PSE
Figure 2.1-1: Reference Configuration for IDUnE1 and PSE
Page 14 of 88
Hardware and Software Configuration
To run the CIPHOP IP System User Interface a standard PC is required supporting the following
SW configuration:
Windows Operating System Windows 2000
Browser Internet Explorer, Version 7.0
Browser Firefox, Version 4.0
Java Virtual Machine, Version 1.6
2.3.
Installation
The PC (Ethernet LAN port) implementing the LCT function has to be connected to the LCT
connector on the front panel of the IDUnE1or PSE by means of a standard Ethernet cable with
RJ45 connectors. A RCT can be connected to any of the terminals of the link via the IP network the
radio link is included within and shall be used with the PoE configuration.
It is possible to have access of each terminals LCT via PC, setting them with an IP address.
Each terminal and the PC has to have a different IP address and they must be within the subnet
defined by the subnet mask.
Factory default values are:
IP Address
Subnet Mask
Default Gateway
192.168.0.50
255.255.255.0
192.168.0.1
which can be used at the installation to connect each equipment from the CT (either LCT or RCT).
Before any other action, after having opened a session (see par 2.4), the IP addressing has to be
modified assigning the unique IP address defined by the customer according to the network
addressing plan. This can be done using the System Settings window (see par. 2.12).
The IP address loaded during this session has to be used to control the equipment until modified
using the same procedure.
2.4.
Getting the Connection
Before opening any session as LCT, the LAN port of the PC used as LCT has to be assigned an IP
Address belonging to the same Subnet defined for the equipment.
The user can set up the required IP configuration by means of the following procedure:
1. Open Network Connections in the Control Panel of the PC
2. Select LAN Connection and with the right button of the mouse open the window
3. Click on Properties
4. In the window General select Internet Protocol and open Properties
5. Enter the IP address consistent with the Subnet of the equipment
6. Close (OK) the transaction
To open a session as LCT or RCT it is required to use a standard browser and to enter the IP
Address of the equipment to be accessed in the Address field of the browser:
1. Open the Internet Browser
2. Enter the IP Address of the Terminal (as defined at installation or previously assigned - see
par. 2.3) and open the connection.
3. Enter Username and Password in the pop-up login window which opens (Fig. 2.4-1).
Page 15 of 88
2.2.
Figure 2.4-1: Login Window
The Username has the default value operator which cannot be changed.
The default value for the Password is o. The Password can be changed by the operator through
the procedure detailed in par. 2.19.2)
If another user is already logged, instead of the Login window the pop-up window of Fig. 2.4-2-a
will be opened and the user cannot login.
If an existing connection with the CT is lost, the alert of Fig. 2.4-2-b is displayed.
Note: After a period of about 30 minutes when the CT has been inactive the CT connection is
released. If the operator reopens again the CT afterwards, the login windows of Fig. 2.4-1 is
displayed and the operator user has to login again to access the system, inserting Username and
Password.
Note: To access the Remote Terminal of a link (or the Mate and Remote Terminals in case of 1+1
HSB configuration) from a CT it is possible to establish the connection to the Local terminal and
clicking the link External LinksRemote Terminal/Mate Terminal available in the Main Menu (see
par. 2.18).
Note: The Remote Terminal of the link can be reached only if the radio link is in normal operation.
Warning: Obviously, using the RCT, any terminal can be reached using its own IP address, but in
this case the operator must be careful not to issue commands that could put out of service the
remote system because the system is not able to filter dangerous operations. Otherwise cutting the
radio link makes in this case the terminal unreachable and a manual local intervention in the
terminal to restore service becomes necessary.
Page 16 of 88
b Alert: connection is lost
Figure 2.4-2: Login Window - Alerts
a Alert: another user is already logged
Page 17 of 88
2.5.
Setting Date and Time
During system installation it is required to set the date and time of the ODU in order to have valid
timestamps in the log files and performance files. The date and time can be set in two different
modes by using the System Settings menu (see par. 2.12), locked to the
Local PC time
NTP server: in this case the user need to enter the IP address of an NTP (Network Time
Protocol) server and the ODU contacts the server to synchronize its clock with it.
Note: The system doesnt have a backup battery and therefore the date and time is lost every time the
system is restarted. To maintain time and date the ODU automatically attempts a re-synchronization with the
NTP server (if defined) every 30 minutes. Moreover an automatic re-synchronization with the NTP server is
executed when the system is restarted,
2.6.
CT Screen Layout
Logo
Summary System Status
Menu
Variable Window
Figure 2.6-1: CT screen functional areas
In Fig. 2.6-1 the main areas of the screen are defined.

1) Browser Area. Proprietary of the specific browser used by the customer. Includes the IP
address area where the IP address of the equipment is displayed. If more equipment have
been opened, tabs are available for each of them and it is possible to switch between the
equipment by clicking on the appropriate tab. In each tab SystemName (LocationName) is
displayed to identify the equipment.
Page 18 of 88
3) Summary System Status. This area is always displayed providing the key information
about the current system operation. It is therefore possible to supervise continuously the
operation of the system, to have a summary view of the system status and to have
immediate alert when any abnormal condition appears in any phase of the CT operation.
4) Menu Area. In this area links are provided to open the required specific window in the
Variable Window area by clicking on the relevant line of the menu.
5) Variable Window area. Here the different windows can be opened to perform all
management actions and enquires supported by the CT. One window is displayed at a
time, but for all open windows a tab is present in the top line of the area allowing to switch
between the open windows simply by clicking on the tab. A window is displayed until it is
closed or a new one is opened.
The System Status window is displayed by default and its tab is always present.
For all windows the following general rules apply.

Each window is made of one or several functional areas

In a window there can be displayed:
o Information to the operator. Areas only displaying values of system parameters
that cannot be modified have a light blue background.
These items are marked in the following Tables with I.
o Parameters configurable by the operator: the current value can be modified by the
operator entering the new value, but the modification (new configuration) is
executed only when the <apply> button associated to the window is clicked.
These items are marked in the following Tables with M.
o Buttons to directly execute some standard operation by clicking them.
Combo-box fields are used to represent attributes that can assume several values.
A Text area is used for attributes with a list of possible values. (i.e. alarm list)
To facilitate understanding of the displayed information, colors are used with the following
meaning:
o Green
indicates no problem and normal operation of the system
o Red
indicates a critical or urgent alarm status
o Yellow
indicates non urgent alarms, warning or abnormal conditions
Detailed information about the areas are included in the following paragraphs.
2.7.
Main Window
When a session is opened accessing the CT from the browser (par. 2.4) the Main Window as
shown in Fig. 2.7-1 is displayed.
Note: This Figure is applicable to PSE and PoE configurations. When the system is configured
with IDUnE1 some fields are different as described in details in the relevant paragraphs.
The Main Window is normally displayed when no specific actions by CT are required with the key
reporting of the system operation.
From the Main Window, clicking on the suitable links in the Main Menu (left area of the screen) it is
possible to open in the Variable Window area the dedicated windows implementing the different
functions of the CT.
Page 19 of 88
2) Logo Area. The Logo of the equipment is displayed.
Figure 2.7-1: Main Window (configuration with PSE or PoE)
2.7.1
Summary System Status
In the upper Summary System Status area the following info is displayed and continuously
refreshed every few seconds:
6 LED: used to display summary alarms and functionality of the system reporting the
status of the Local and Remote Ends of the radio link:
for the Local End
o In Service (Transmitter On)
o Alm (Major Alarm)
o Warn (Warning Information)
o RDI (Remote Defect Indicator)
for the Remote End:
o RemAlm (Major Alarm)
o RemWarn (Warning information)
Date field: reports (yyyy/mm/dd hh:mm:sec format) the system date and hour. The
System Date can be updated and/or aligned to a reference Date using the System
Settings menu.
Temperature: indication of the current temperature of the ODU.
Page 20 of 88
Tx/Rx Radio parameters:

Tx Freq. - Transmitter frequency (MHz)
Rx Freq. - Receiver frequency (MHz)
Tx Pwr - Transmitted power (dBm)
Rx Pwr - Received power (dBm)
CS Channel spacing between Tx and Rx (MHz)
Rem Rx Pwr - Received power by the Far-End terminal of the link (dBm)
Tx Rate Net Data rate transmitted (link load) (Mbps)
Rx Rate - Net Data rate received (link load) (Mbps)
Note: For Power measurements -128 dBm is shown in case of signal below measuring threshold
2.7.2 Main Menu

In the left Main Menu area the following links (grouped in functional classes) are displayed and
can be used to open the relevant Variable Windows or perform the required operations by clicking
on the name:

Interfaces
Radio management of ODU Tx/Rx parameters (see par. 2.8)
Ethernet management of Ethernet User Network Interfaces available on the
system (see par. 2.9)
TDM management of the E0/E1 interfaces and connections (only for IDUnE1
configuration) (see par. 2.10)
Equipment
System Settings management of system information (see par. 2.11)
Inventory and Housekeeping management of inventory information and
housekeeping interfaces (see par. 2.12)
Logs access to log files (see par. 2.13)
Statistics access and management of statistical counters to monitor traffic on
the system (see par. 2.14)
Performances access and management of counters and indicators
monitoring the quality of service (see par. 2.15)
Configuration Files
Backup create backup files of the system configuration (see par. 2.16.1)
Restore recover system configuration from the backup files (see par. 2.16.2)
External Links (par. 2.1)
Remote Terminal allows to open and access directly the CT of the Remote
Terminal of the link (i.e. the equipment of the radio link located in the Remote
station). In case of 1+1 radio links, the Remote Terminal is defined as the
equipment of the remote station with the same protection role in the protection
group.
Mate Terminal available only in 1+1 HSB configuration. Allows to open and
access directly the CT of the Mate Terminal of the link (i.e. the equipment of the
radio link collocated in the same Local station)
Mate-Remote Terminal available only in 1+1 HSB configuration. Allows to
open and access directly the CT of the Mate-Remote Terminal of the link (i.e.
the Equipment of the radio link located in the Remote station and with the
opposite protection role in the protection group)
Admin
Upgrade management of download of new SW loads (see par. 2.18.1)
Change Password allows to modify the system password (see par. 2.18.2)
Logout closes the CT session (see par. 2.18.3)
Page 21 of 88
2.7.3 System Status

In the Variable Window area System Status is displayed by default when no other windows are
open or by clicking on the System Status tab in the top line of the area.
Three functional areas are displayed.
a) Settings
The parameters displayed in this area are described in Table 2.2.
Note: All parameters cannot be modified in this window, but to perform any change it is
necessary to open the System Setting window (link EquipmentSystem Setting in the Main
menu) (see par. 2.11)
b) Radio Measures
For the same radio parameters displayed in the Summary System Status
Tx Power
Rx Power
RemRx Power
Tx Data rate
Rx Data rate
there are reported the min, max and mean value measured in the last 15 min. period (moving
measuring window). The operator can restart measurements by the <Clear> button at the bottom
of the area.
c) Alarms
The current status of the functional blocks of the equipment and the active alarms can be
monitored in this area, subdivided by the following functional areas. The display is automatically
refreshed. Alarm and warning indications are in red.
Ethernet
There is a row for each Ethernet port equipped in the system (depending on the system
configuration: POE, USER, ETH, LCT) where the current status is displayed and active
alarms are indicated. The current status is a function of the port settings (see par. 2.9) and
of the result of autonegotiation on the interface if enabled.
Radio
There is a row where the current status of the radio subsystem (settings are defined in par.
2.8) is displayed and active alarms are indicated.
Equipment
There is a line where the other active alarms of the equipment are indicated.
TDM (available only in IDUnE1 configuration)

There is a row for each E1 port reporting how each E1 port is configured (see par. 2.10)
and the active alarm list of the port and associated connections. The ports not configured
(status = down) are not displayed.
In Table 2.3 there is reported the list of the Status and Alarms values used in each area.
Page 22 of 88
Link Name
Location name
System Name
Configuration
License Status
IP Address
Description
Name assigned by the customer to the link
(Note 1)
Name assigned by the customer to the
station where the terminal is located (Note 1)
system to identify it inside the station (Note 1)
Define the type of configuration of the system
(IDU type)
Define which service license is enabled on
the equipment. The different licenses allow to
operate with different system capacity
(Channel Spacing sets)
IP Address assigned to the equipment
(required to access it from CT or OS)
Protection
Define if the link is unprotected or protected

and in this case the role in the protection
group
ODU Status
Only displayed in 1+1 HSB configurations:

this field reports the current status of the
ODU
Remote Address
Mate Address
Mate-Remote
Address
SW Version
TDMoIP Device
Address 1-8
TDMoIP Device
Address 9-16
IP Address assigned to the Remote Terminal.

IP Address assigned to the Mate Equipment
IP Address assigned to the Mate-Remote
Equipment in the Remote station.
Label identifying the SW load used currently
by the system.
MAC address assigned to the device where
E1 ports 1 to 8 are interfaced. Required to
establish TDM connections in the network. It
is calculated adding +1 to the equipment
MAC address.
(Note 2)
MAC address assigned to the device where
E1 ports 9 to 16 are interfaced. Required to
establish TDM connections in the network. It
is calculated adding +2 to the equipment
MAC address.(Note 2)
Values
Text
Text
Text
-
PoE
PSE
IDU16E1
IDU8E1
- Basic (CS=3.5, 7 MHz)

- Entry (CS= 3.5 ,7,14 MHz)
- Advanced (CS= all)
Dec. No. (xxx.xxx.xxx.xxx)
Unprotected (1+0): operation
in non-protected mode
1+1 HSB Main: 1+1 HSB
system, the ODU is defined
as Main in the Protection
Group
1+1 HSB Protection: 1+1
HSB system, the ODU is
defined as Protection in the
Protection Group
Active: ODU transmitting
and Receiving the signal
Active
Forced:
ODU
transmitting and Receiving
the signal in Forced mode
Stand-by: Tx is switched off.
Stand-by Lockout: Tx is
switched off in Lockout mode
Text (xxxxx.xx.xx.xx_xx)
Hex No. (xx.xx.xx.xx.xx.xx)
Hex No. (xx.xx.xx.xx.xx.xx)
Note 1) These parameters can be optionally defined by the customer

Note 2) Only in case of IDUnE1. For IDU8E1 only the first address is defined and displayed
Table 2-5: Parameters displayed in the System Status - Settings
Page 23 of 88
Parameter
Functional
Area
Ethernet
(a row per
Interface)
Description
Status
100M FDX Asym FlowControl

100M FDX No FlowControl
10M FDX Asym FlowControl
10M FDX No FlowControl
Alarms
LinkDown
RemoteFault
AutonegotiationFailure
Status
Up (manual mode)
atpc
Down (squelched)
Alarms
Alarms
OlAlm
DemAlm
TxPwAlm
RxPwAlm
RxFrame
ATPCLoop
RxPwRem
LowBER
HighBER
txContinuousWave
Radio
Interface
Equipment
Values
Status
TDM
(a row per
E1 port)
Alarms
100M HDX Asym FlowControl

100M HDX No FlowControl
10M HDX Asym FlowControl
10M HDX No FlowControl
AlmRem
WarnRem
RemChan
IduNotOper
TempAlm
mateLinkFail (only for 1+1 HSB systems)
Down
Up
OutwardLoop
InwardLoop
Dual Loop
ForcedAis
UpAlmDisable
e1Los
e1Ais
e1Lof (only in case of E1 Framed)
EthLos (only for E1 bundles)
EthLos_xxx (only for N x E0 bundles)
Note: More detailed information about each alarm can be found in Par. 5.2
Table 2-6: Status and Alarm information displayed in the System Status - Alarms
Page 24 of 88
Radio Interface
In this window (which can be opened by the Main Menu link InterfacesRadio) the operation of
the Radio subsystem can be configured and monitored. The window is shown in Fig. 2.8-1.
Figure 2.8-1: Radio Interface Window
The window is subdivided in functional areas hereby described.

The operation of the system is different according to the type of band:
- Licensed Bands (6, 7, 8, 10.5, 15, 18 and 23 GHz)
- Unlicensed Bands (5, 17, 24 GHz)
as detailed in the following.
a) Radio Info
The parameters of Table 2.4 are displayed. They are defined by the specific ODU and by the
system parameters loaded in the factory and cannot be modified by the operator in field.
Page 25 of 88
2.8.
Parameter
Type
Tx Min Frequency
Tx Max Frequency
Rx Min Frequency
Rx Max Frequency
Tx Rx Shift
Band Frequency
Band Descriptor
Tx Min Power
Tx Max Power
I
I
Description
Display the minimum value allowed for the
TX Frequency (Tx frequency range)
Display the maximum value allowed for the
Tx Frequency (Tx frequency range)
Display the minimum value allowed for the
TX Frequency (Rx frequency range)
Display the maximum value allowed for the
Tx Frequency (Rx frequency range)
Display the Shifter frequency difference
between Tx and Rx frequencies
Display the Band supported by the ODU
Display the Band Descriptor (High or Low
Band ODU)
Minimum settable transmission power level
Maximum settable transmission power level
Values
Value in MHz (xxxxx.yy)
Value in MHz (xxxx)
5 GHz, 6GHz, 7GHz, 8Ghz,
10.5GHz, 15GHz, 17 GHz,
18GHz, 23GHz, 24 GHz
- 1L
- 1H
Value in dBm (e.g. 0 )
Value in dBm (e.g. 20)
Table 2-7: Parameters displayed in the Radio Interface Radio Info

b) Radio Configuration
The parameters defining the radio operation can be defined using the four functional areas:
Interface
Modem
Frequency
Power
In each of them it is possible to set and/or modify the relevant parameters as defined in Table 2.5.
Note that the new settings of each area will be executed only when the <Apply> button at the
bottom of each area is pressed.
The following specific remarks apply for unlicensed bands:
It is possible to set independently Tx and Rx frequencies, within the limits displayed in the
Radio Info for each of them. Therefore a value can be entered by the operator also in the
RxFrequency field of the Frequency area.
The Tx-Rx Shift shows as default the standard shift between the Tx and Rx frequencies
set in the system. If Tx or Rx frequencies are set differently by the operator Tx-Rx Shift
shows the actual value (difference between the two frequencies). Note that the Radio Info
is not automatically refreshed, so that the new value is displayed only reopening the Radio
Interface window
The default operation (with Tx and Rx separated by the default Tx-Rx Shift) is the start up
condition and can be restored typing the value 0.00 in the Rx Frequency field and clicking
on <Apply>. After <Apply>, Rx Frequency will display the actual value corresponding to
the default Shifter.
a <Radio Frequency Seeker> button is added in the Frequency area to open the dedicated
tool described in the following par. 2.8.1
Page 26 of 88
Type Description
Values
- up: enable transmission,
manual mode
- atpc: enable transmission,
ATPC mode
- down: squelched
- none : normal
- tx Cw : Continuous Wave
Admin status
The user can set up the desired state of the

transmitter.
Testing Mode
The user can set up the test mode
Enabling ULA the forwarding to the Tx of

ethernet frames is inhibited when Rx is out
of service to prevent creation of
unidirectional connections
- Enabled: ULA operates

- Disabled: Tx and Rx frames
flow independently
Channel Spacing
Select the RF channel bandwidth and the

associated radio transmission rate
Clock Transparency
When Enabled allows the clock to be

transparently transported in both directions
(for details see TED par. 2.4.4)
- Enabled
- Disabled
Unidir Link Avoidance

(ULA)
Modem
3.5 MHz Bitrate 4.5 Mbps
7 MHz Bitrate 9 Mbps
Frequency
TxFrequency
RxFrequency
I (M)
Display the Frequency of the transmitter

The user can set the transmitter frequency
entering the required value. Tx Frequency
must be set between TxMinFrequency and
TxMaxFrequency
Display the frequency of the receiver for
ITU licensed bands (given by TxFrequency
Shifter Frequency).
For Unlicensed bands the value can be
entered between RxMinFrequency and
RxMaxFrequency.
Value in MHz. (xxxxx.yy)
Value in MHz. (xxxxxx.yy)
Power
Tx Power
Atpc Min
Atpc Max
Atpc Target
Required transmission power level in the

manual mode of operation
Min Transmission power level in ATPC
mode
Max Transmission power level in ATPC
mode
Target value of the received signal in
ATPC mode
Value in dBm.
Must be set in the range
TxMinPower / TxMaxPower
Value in dBm
Table 2-8: Parameters displayed in the Radio Interface Radio Configuration
2.8.1 Radio Frequency Seeker

For Unlicensed Bands (CIPHOP IP 905, 917 and 924) a radio frequency seeker tool is
available to help the operator to determine the optimum working conditions for a link (i.e.
frequency selection where interference from other systems is minimum). The tool is specifically
designed to be used at the system installation and/or when it is required during the life of the
link to re-optimize its operating conditions This tool can be started clicking on the <Radio
Frequency Seeker> button in the Frequency area of the Radio Interface window: the dedicated
pop-up window of Fig. 2.8-2 will open.
Important: run the tool only in Administrative status UP (ATPC function OFF).
Page 27 of 88
Parameter
Interface
Figure 2.8-2: Radio Frequency Seeker window for Unlicensed Bands

Step1) A set of TX and Rx frequencies is initially manually configured in the two terminals using
the Frequency area allowing the system to start to communicate, even if in a non-optimal
condition.
Step 2) It is possible now to perform a scan, searching for possible interferences along the
available RX bandwidth. During this process transmitters are switched off and no traffic
flows. The equipment will analyze and record in both stations the received power level for
each channel. The bar show the progress of the scan process up to the end (100%).
Step 3) At the end of the scanning process, the system will turn on transmitters and it is possible
to display the results of the scan for both the terminals (A=Local B= Remote) of the link
either as a graph (click on Show Graphics button) or as a Table (click on Show Tables
button).
Step 4) In the Found Frequencies fields the tool suggest the pair of frequencies (Tx and Rx)
where the analyzer recorded the lower interference power level. It is now possible to
automatically apply the suggested frequencies to both terminals clicking on the Apply
Frequencies button. The automatic selection is confirmed if demodulator alarms in the
two terminals disappear within 60s, otherwise the two terminals automatically switch back
to the initial configuration.
Note: The Radio Frequency Seeker can be started even in the case only the local terminal is accessible
(radio link down). In this case only the scan for the local terminal will be provided and no automatic frequency
selection is possible.
The procedures to be used are described in more details in Chap. 3 Table 3.17/18/19/20/21.
Page 28 of 88
Ethernet Interface
In this window (which can be opened by the Main Menu link Interfaces/Ethernet) the operation of
the Ethernet Interfaces available to connect external traffic on the system can be configured and
monitored. The window is shown in Fig. 2.9-1.
Note: Table 2.6 shows the Ethernet Interfaces supported in each configuration
Configuration
(IDU Type)
PoE
PSE
IDUnE1
Protection
Unprotected 1+0
Protected 1+1 HSB
POE
n.a.
ETH, LCT
ETH
USER, LCT
n.a.
Note: in the 1+1 HSB with PSE the LCT port is used for the Mate link to connect the two systems
Table 2-9: Ethernet Interfaces supported for each configuration

Note: The port labeled ETH in the case of PSE is denominated in the LCT windows USER as in
the case of IDUnE1.
The ETH Interfaces of the system can support 10T and 100T Fast Ethernet connections.
The speed can be automatically negotiated with the User Equipment (auto-negotiation).
The LCT port can be used both as a second User port or to connect the LCT: UserMode field
allows to select if the port is used as:
User Interface (Enable). In this case the other parameters can be set by the operator
LCT interface (Disable). In this case the Interface configuration is predefined and the
other parameters cannot be modified.
Figure 2.9-1: Ethernet Interface window
Page 29 of 88
2.9.
Parameter
Config
Type Description
Port
Label on HW designating the port

Note: the ETH port on PSE is
Type
Display the type of interface
Values
-
Define is the port is used to interface the User

network and carry user traffic or as LCT.
Note: as LCT the port is configured:
- Autoneg. Enabled
- All speed/modes are advertised
- limited to 400 kbps max throughput
Define is the autonegotiation is enabled with the
other side of the interface
User Mode
Autonegotiation
Speed
Define the speed allowed for the interface

(see Note 1)
Duplex
Define the Full/Half duplex mode of operation

(see Note 1)
Flow Control
Rate Shape
Default VID
Default Prio
Port Alarm
Allows to suppress the Interface alarms if required
Port
Identify the port the parameters are referred to.
Speed/Duplex
Show the actual operating status of the interface
Flow Control
Show the actual operating status of the interface

Flow Control
QoS key
Allows to enable to the QoS functionality
Queues mapping
Priority 0
The user can define the Flow Control options at

the Ethernet interface.
(see Note 2)
Allows to define the input shaping applied to the
port interface
If VID is greater than zero, a VLAN TAG with VID
is added to every untagged packet.
If Prio is greater than zero, a VLAN TAG with prio
set to this value is added to every untagged
packet.
USER
LCT
POE
LCT
User1
User2
MateLink
- Enabled (User)
- Disabled (LCT)
- Enabled
- Disabled
- all (no limitation)
- 10M
- 100M
- both
- FDX
- HDX
- Asymmetric
- Disabled: the flow control is
disabled
0-100 (% of the FE max
capacity)
0-4093
0-7
- Enabled
- Disabled
Status
- USER
- LCT
- POE
- 100 FDX - 10 FDX
- 100 HDX - 10 HDX
- Asymmetric
- Disabled
QoS Settings
- Disabled
- CoS
List of COS values for Priority 0
queue: e.g. : x,y,z-w
Allows to list the CoS which are associated to the

Priority 0 (higher) queue
Display the list of CoS associated to Priority 1
Queues mapping
List of COS values Priority 1
I
(lower) queue.
Priority 0
queue: e.g. : x,y,z-w
Automatically updated based Priority 0.
Note 1) The user can select the combinations (one or more) of speed (10 or 100) and Half/Full duplex (FDX or HDX) to
be used. In case autonegotiation is enabled the resulting mode will be negotiated with the network equipment
within the allowed combinations. In case autonegotiation is disabled the max speed in the list will be
configured. The resulting operation mode is displayed to the operator.
Note 2) If autonegotiation is enabled the result will be subject to partner ability to support flow control. The resulting
operation mode is displayed to the operator.
Table 2-10: Ethernet Interface parameters
Page 30 of 88
Config: all configuration parameters of the port are displayed and can be modified by the
operator entering the new value. The new configuration is executed only when the <Apply>
button at the bottom of the area is pressed.
QoS Settings: QoS Management is implemented to assign different types of traffic to the
two priority queues available on the system:
o Queue 0 with Strict Priority
o Queue 1 with lower priority
The Ethernet frames are queued on the basis of the PCP (Priority Code Point) field of the
frame according to the CoS Table set by the User.
By setting the QoS Key field it is possible to select one of the following modes of operation:
o without QoS (disabled)
o with priority according to CoS (enabled)
The configuration table allows to assign each of the 8 CoS Classes (0 to 7) to the
appropriate Priority Queue (0 or 1) available in the system.
The parameters relevant to the management of the QoS are displayed and can be
modified entering the new value. The new configuration is executed only when the <Apply>
button at the bottom of the area is pressed.
Note: if the system carries TDM traffic, TDM frames are in any case managed with Strict
Priority (Queue 0). It is recommended in this case that all Ethernet traffic is assigned to Low
Priority Queue1.
Status: the key information about each interface is displayed as also reported in the
Alarms/Ethernet area of the System Status window.
All parameters are defined in Table 2.7.
2.10.
TDM Interface
This window (which can be opened by the Main Menu link InterfacesTDM) is available only for
the IDUnE1 configuration and allows to manage the E1 Interfaces and the TDM connections
terminated onto these interfaces. The window is shown in Fig. 2.10-1.
The connections are identified in the Source (src) Local equipment and in the Destination (dst)
Remote equipment (where the other end of the connection is terminated) by the:
Bundle. Identifies the group of timeslots which are bound together creating a single
connection. A bundle can be made of a whole E1 (E1 bundle, in this case transported
transparently) or of selected timeslots in a E1 (consecutive or not) (n x E0 bundle). The
two bundles in Source and Destination equipment connected together must be consistent
(i.e. with the same No. of timeslots, even if the timeslots may be not corresponding one to
one).
Address. Identifies MAC address of the TDMoIP device where the E1 port(s) to be
connected are located. Only the last 6 digits of the MAC address are managed.
Two types of connections can be managed:
E1 Connections: a bidirectional E1 circuit created connecting two E1 bundles (transparent
connection between a E1 local port and a E1 port in the Destination equipment). The two
ports operate in unframed mode
N x E0 Connections: bidirectional connection between two consistent n x E0 bundles
associated to a E1 local port and a E1 port in the Destination equipment. The two E1 ports
must operate in framed mode.
Page 31 of 88
The window is subdivided in three functional areas:
Figure 2.10-1: TDM window

In the window the list of connections (one per row) is shown: the relevant parameters are
described in the Table 2.8. The list can be ordered in ascending or descending order of the
different fields, but the normal recommended display is by ascending order of Port Number and
src bundle (default).
a) Operation with E1 connections only
A default list of 16 rows is defined in the window, one per each E1 port. These rows are sufficient
for E1 only operation and no other row needs to be defined: therefore in this case the button
<NewRow> at the bottom of the window should not be used.
For this operation mode:
All E1 port are configured as unframed in the Type field
all srcBundle are automatically created as xx.00 where xx=Port Number
srcAddress is automatically created by the equipment inventory data
timeslots is automatically set to all
Port Name and Connection Name can be optionally entered by the operator
If a E1 Connection has to be created it is necessary to
o enter DstBundle and DstAddress in the relevant fields
o in the Connect field select:
true if the connection has to be immediately set-up
false if data have to stored but the connection is deferred to a later time
o press the button <SaveChanges> to execute the command.
Page 32 of 88
Description
Port Number
Display the number of the E1 port
Port Name
This variable contains an identifier assigned

by the operator to the E1 port
Value
1 to16 (IDU16E1)
1 to 8 (IDU8E1)
Text
- Down. The port is disabled
AIS is forced in output and all
alarms are inhibited.
- Up. The port is configured
and works normally
- OutwardLoop: The input
signal is looped back as
output of this port (Input port
loop)
- InwardLoop
The
output
signal is looped back as
input to this port (Remote
End port loop)
- DualLoop sets both loops
- Forced AIS:
AIS is
generated at the output of the
E1 interface
- upAlmDisable: the port is
configured
and
works
normally, but alarm reporting
is inhibited.
- unframed
- framed
Dec xx-yy where
xx = No. of the port
yy = first E0 of the bundle
Note 1)
Hex xx-xx-xx
Last 6 digits of the MAC Add.
- All (in case of E1 connection unframed)
- x, y, t-w (in case of n x E0
connection)
Admin Status
Allow to display and setup the status of the E1

interface.
Note: in the loop condition the looped signal is
also forwarded to its normal output.
Type
Indicates the variety of E1 Interface
Src Bundle
Identifier of the Bundle in the local (source)

equipment (local termination of the
connection)
Src Address
TDMoIP Device MAC address in the local

equipment where the connection is terminated
Timeslots
List of the timeslots of the E1 port associated

to the bundle which constitute a E1 or nxE0
connection
Connection
Name
This parameter contains an identifier assigned

by the operator to the TM connection
managed in the line
Text
Dst Bundle
Identifier of the Bundle in the companion

remote equipment (destination) where the
connection is terminated
Dec xx-yy where

xx = No. of the port
yy = first E0 of the bundle
Note 1)
Dst Address
TDMoIP Device MAC address in the

companion remote equipment where the
connection is terminated
Hex xx-xx-xx
Last 6 digits of the MAC Add.
Allows to set-up or delete the connection

defined in the line
- true. The connection is

established
- false. The connection is
disconnected, but data are
kept
- delete. Data e row related to
the connection are cancelled.
Connect
Note 1): in case of unframed E1 yy=00.
Table 2-11: TDM parameters to manage E1 ports and connections
Page 33 of 88
Item
a connection only defined (Connect = false) can be connected setting the field Connect to
true and pressing the button <SaveChanges
an existing connection can be disconnected, saving its data, by setting the field to false
and pressing the button <SaveChanges
all data of an existing connection can be deleted setting the Connect field to delete and
pressing the button <SaveChanges
Note: Please note that only data of one connection at a time should be set up or modified with a command.
Note: E1 traffic flows in a normal mode in the network only if the E1 port has the AdminStatus = up and
Connect is true.
b) Operation with both E1 and N x E0 connections

If a N x E0 connection needs to be created it is necessary to insert in the current connection list a
new row where the data of the new N x E0 connection can be stored. This can be done pressing
the button <NewRow> at the bottom of the window. The new row is normally inserted as first row in
the list.
In the new row to define the connection:
Enter the relevant Port Number
Select framed in the Type field
Enter the list of the E0 timeslots belonging to the n x E0 bundle in the Timeslots field
Enter srcBundle as xx.yy where xx=Port Number, yy= first E0 of the timeslot list
srcAddress is automatically created by the equipment inventory data
Port Name and Connection Name can be optionally entered by the operator
Enter DstBundle and DstAddress in the relevant fields using Bundle Number and
Address of the destination equipment
in the Connect field select true
press the button <SaveChanges> at the bottom of the window to execute the command.
Note: that traffic flows in a normal mode in the network only if the E1 port has the AdminStatus = up and
Connect is set to true.
Pressing the button, if the new connection is the first to be defined as N x E0 for the given E1 port,
the new row will replace the existing row unframed, otherwise it will be added to the list which is
ordered by SrcBundle number.
Consistency checks are implemented to avoid to enter inconsistent data:
a N x E0 connection can be defined for an E1 port only if no E1 connection is active (true)
for this port
timeslots can be associated to a N x E0 bundle only the Type is Framed.
Timeslots associated to a bundle must be different from timeslots already associated to
existing other bundles on the same E1 port.
As in the case of E1 connections:
an existing connection can be disconnected, saving its data, by setting the Connect field to
false and pressing the button <SaveChanges
all data of an existing connection can be deleted setting the Connect field to delete and
pressing the button <SaveChanges>
Note: delete is accepted only if the existing connection is already set to false.
Page 34 of 88
2.11.
System Settings
This window (which can be opened by the Main Menu link Equipment/System Settings) is
available to configure and manage all parameters associated to the equipment and its
configuration. The window is shown in Fig. 2.11-1.
Figure 2.11-1: System Settings window

The window is subdivided in the following functional areas (All parameters are described in details
in Tables 2.9 and 2.10):
System Config: the system configuration (IDU type) is displayed and can be modified by
the operator selecting the values in the combo-box. The new configuration is executed only
when the <Apply> button at the bottom of the area is pressed.
Page 35 of 88
Notes:
1) Deleting all N x E0 connections related to a E1 port automatically recreate the E1 unframed
row in the list. Port Status and Name are kept.
2) If the new configuration set up in a new row is non correct the <SaveChanges> command
is not accepted and changes are not applied to the connection list leaving the previous
status
3) When more rows (N x E0 connections) are listed for the same E1 Port, the AdminStatus
and Port Name of the port can be modified in any of the rows and pressing the
<SaveChanges> button the modification is automatically displayed on all the rows.
4) Alarm reporting related to a E1 port can be disabled (e.g. during installation or
maintenance) setting the AdminStatus of the port to upAlmDisable.
The field Add new license is used if a new license has to be installed (license upgrade). In
this case the string provided with the new license has to be entered in this field and the
<Apply> button at the bottom of the area pressed. In the System Status (Settings) the new
license is displayed.
Note: a License downgrade is not allowed.
Clicking on the <Info> button a pop-up window is shown detailing the installed SW license
and the allowed Channel/Modulation configurations i.e. the system capacity supported by
the license (see Fig. 2.11.2).
Figure 2.11-2: Info pop-up window about SW licence
Protection: this area is available only with the PSE configuration and only if the system
has been configured as 1+1 HSB Main or 1+1 HSB Protection in the system
configuration. It allows to define the specific features associated to the Protection group.
The new settings is executed only when the <Apply> button at the bottom of the area is
pressed.
Note: All parameters relevant to the Protection Group have to be defined only on the Main ODU: the
Protection ODU is automatically updated in a consistent status by SW. Therefore the <Apply> button
is effective only if the Protection field in the System Conf. is set to 1+1 ODU Main.
Important Warning: For the correct operation of the Protection Group the Mate Link
connecting the two PSE must allow the exchange of Status information between the two
ODUs. Therefore it is mandatory not to disconnect the Mate Link cable if the Protection
Group is operating in the normal mode to avoid to make Active both systems. If the Mate
Link cable has to removed/replaced, it is mandatory before to put the Protection Group in a
Forced status.
IDU management: dedicated to the management of the IDU MAC Address required to
associate the IDU to the system. The MAC Address can be either manually entered or auto
discovered by enabling the automatic procedure. In both cases the new MAC Address is
activated only when the <Apply> button at the bottom of the area is pressed.
Important Note: To assure the correct interworking of the ODU and Indoor card, the MAC Address
of the indoor card (either PSE or IDUnE1 depending on the configuration) must be defined at the
system start up. In case of replacement (e.g. repair, etc.) the MAC address must be updated:
Page 36 of 88
Automatically, setting the IDU MAC Autodiscovery field to Enabled and clicking on the
<Apply> button. A SW procedure is started which uploads the IDU MAC Address, which is
then displayed in the IDU MAC Address field.
- Manually, entering the new MAC Address in the IDU MAC field and clicking on the <Apply>
button. The MAC Address to be entered can be read from the label on the case of the indoor
unit
If the PSE MAC address is not configured or incorrect, the indoor unit cannot be reached and its
functions are not supported.
System Identity: the parameters identifying the system are displayed and can be entered
in the relevant fields and modified by this window. The same information is also displayed
in the Settings area of the System Status window.
The Link Identity (unique within the same network) is used for administration purposes (e.g.
on an OS). The following rules must be met:
o The two terminals of a 1+0 link must have the same Link Identity
o The four terminals of a 1+1 HSB link must have the same Link Identity
The Encryption Key (0-255) is used to cipher the radio bitstream. If the field is left empty
(default), no ciphering is performed. The following rules must be met:
o The two terminals of a 1+0 link must have the same Encryption Key
o The four terminals of a 1+1 HSB link must have the same Encryption Key
New parameters are activated only when the <Apply> button at the bottom of the area is
pressed
System Time: this area allows to manage information related to system time and sources
to be used to synchronize it. The System Date can be set up by manual resynchronization
with the CT or NTP server after setting the appropriate fields in the window by pressing the
<Apply> button at the bottom of the area.
Note: System Date information is not maintained at power shut down. After the equipment is again
powered up, an automatic synchronization with the NTP server is performed and if successful realign
Time and Date. Automatic resynchronization with the defined NTP is also performed every 30
minutes.
Management Interface: this area is dedicated to enter and manage information related to
Management Interface and its addressing. New parameters are activated only when the
<Apply> button at the bottom of the area is pressed
System Restart: an <Apply> button is available to execute a SW restart of the equipment

on operators command. After pressing the button, the pop-window of Fig. 2.4-1 appear
and the operator must reenter UserName and Password.
Page 37 of 88
Parameter
System Config
Configuration
Add New License
Protection
Type Description
Values
PoE
PSE/C
IDU16E1
IDU8E1
Define the type of configuration of the

system (IDU type)
Allows to enter the licence key to upgrade

the license level. (see par x.x.x).
Pressing the associated <Info> button the
existing license is displayed.
A string of 32 hex digits.
Displayed only for PSE configuration. Allows

to define the type of protection of the radio
link and the role of the ODU in the protection
group.
Unprotected (1+0): operation

in non-protected mode
1+1 HSB Main: operation in
1+1 HSB, the ODU is defined
as Main in the Protection
Group
1+1 HSB Protection:
operation in 1+1 HSB, the
ODU is defined as Protection
in the Protection Group
Protection (displayed only if the configuration is 1+1 HSB)
Revertive Mode
Forced Mode
Allows to define if the protection is revertive

or not.
The command has to be executed only on
the ODU Main and the status of the
Protection will be set accordingly).
On the Protection ODU the parameter is only
displayed.
Allow to force the ODU status.

The command has to be executed only on
the ODU Main and the status of the
Protection will be set accordingly)
On the Protection ODU the parameter is only
displayed.
Revertive: ODU main returns

Active as soon as its alarmed
status ends (recommended in
case of RF asymmetrical
coupler)
NotRevertive: the protection
group does not switch back
when an alarmed status ends
(the ODU Active remains
Active).
Clear (no forcing): normal
operation of the Protection
Group.
Forced: the ODU (Main) is
forced Active
Lockout: the ODU (Main) is
lockout and the Protection
ODU is forced active
Idu Management
Idu MAC
Autodiscovery
Display the MAC Address of the InDoor Card

(either PSE or IDUnE1). Not used with PoE c
If Enabled, pressing the <Apply> button
starts the procedure to upload the MAC
hexadecimal
xx-xx-xx-xx-xx-xx
- Enabled
- Disabled
Table 2-12: System Settings parameters
Page 38 of 88
Type Description
Location Name
System Name
Link Name
Encryption Key
M
M

station where the terminal is located
system to identify it inside the station
Name assigned by the customer to the link
Key used to cipher the radio digital stream
Values
Text
Text
Text
Dec (o to 255)
System Time
NTP Server
Time Zone
Sync Source
Daylight Saving
Define the IP Address of the NTP to be

accessed to time synchronization
The Time Zone information (vs. Greenwich
time) has to be entered to obtain the correct
local hour from the NTP time.
Define the source of the Reference time
used to synchronize the equipment
The user can enable it during the appropriate
periods of the year
Dec. xxx.xxx.x.xx
+xx h
- Manual (PC of the CT)
- NTP
Management Interface
IP Address
Network
Default Gateway
Inner Tag
Outer Tag
Mode (Note 2
Remote IP (Note 3)
Mate IP (Note 4)
Mate-Remote IP(Note 5)
M
I
M
IP Address defining the address of the

equipment (used to access the equipment
from CT or OS).
Subnet Mask of the equipment in the IP
network
Default Gateway of the equipment in the IP
network
VLAN identifier (C-TAG) used to segregate
management traffic from user traffic (see
Note 1)
VLAN Identifier (S-TAG) used to segregate
management traffic from user traffic (see
Note 1)
Defines which Access Mode is allowed to
monitor and control the equipment
IP Address of the Remote Terminal
IP Address of the Mate Equipment ..
IP Address of the Mate-Remote Equipment

Dec. No. (xxx.xxx.xxx.x)
Default 0
Dec. No. (2 - 4094)
Default 0
Dec. No. (2 - 4094)
- WebOnly
- osAndWeb.
Note 1): In case the default value 0 is used no C or S Tag is associated to the management traffic. If a specific VLAN is
reserved to the management traffic this value has to be used consistently in all equipment of the whole L2
network.
Note 2): By the Mode field it is possible to control the remote access capability, defining if
only access from a CT (WebOnly) is allowed with SNMP interface inhibited
both CT and SNMP (for access to an OS) can operate (osAndWeb).
see chapter 4 Supervision by Remote Craft Terminal (RCT) and Operation System (OS)
Note 3): Equipment of the radio link located in the Remote station. For 1+1 HSB radio links, as Remote IP enter the IP
address of the equipment having the same protection role in the protection group
Note 4): Only for 1+1 HSB radio links. The other Equipment of the radio link collocated in the local station. The IP address
is automatically set from the Mate equipment when the Mate link is connected.
Note 5): Only for 1+1 HSB radio links. Equipment of the radio link located in the Remote station: as Mate-Remote IP enter
the IP address of the equipment having the opposite protection role in the protection group
Table 2-13: System Settings parameters (contd)
Page 39 of 88
Parameter
System Identity
2.12.
Inventory and Housekeeping
This window (which can be opened by the Main Menu link EquipmentInventory and
Housekeeping) is available to display all inventory information about the components of the
system and to manage the Housekeeping external signals.
The window is shown in Fig. 2.12-1.
Figure 2.12-1: Inventory and Housekeeping window

The window is subdivided in two functional areas:
Inventory Data: for each HW component (board) of the system a line is displayed with the
Inventory information retrieved from the inventory EEPROM memory of the equipment and
written in the factory at shipment.
The following parameters are available
Item
Board
Part Number
Serial Number
Customer Data
MAC
Page 40 of 88
Values
ODU Card
Card Type: the textual name of the board.
The HW identification code/version
The board serial number
Item identification code customer defined
The MAC Address associated to the board.
Text
Text
Dec Number
Text
Hex (xx.xx.xx.xx.xx.xx)
Housekeeping: for the two input (Sensors) and output (Actors) signals available at the
Housekeeping interface it is possible to read the current active/inactive status and to
configure the operating mode. The status is automatically periodically refreshed when the
window is open.
Note: This area is not available with PoE configuration.
The parameters of the input contacts allow to enable/disable monitoring of the signal and to
define their polarity.
Input signal if active affects the LED and Summary Alarms Indications:
Sensor 1 affects the Alm LED and Summary Alarm
Sensor 2 affects the Warn LED and Summary Alarm.
The parameters for output contacts allow defining their polarity and forcing active/inactive
status. The following info is available for the housekeeping signals:
Name
Name of the signal
Label
Enable
Status
Mode
Define the contact input mode (Active closed or open)
Status
Report the contact status
A textual string for entering customers information of

the interface
Applicable only to Sensors.
Allows to define the contact administrative status (if the
signal is monitored or not)
Actor1, Actor2
Sensor1, Sensor2
Text
- Enabled
- Disabled
- CloseActive
- OpenActive
- Inactive
- Active
When new parameters are entered they are activated only when the <Apply> button at the
bottom of the area is pressed.
2.13.
Logs
This window (which can be opened by the Main Menu link EquipmentLogs) is available to
display the system log which collects and displays autonomous events (generated by the system
itself like alarms) and command execution results, each of them generating a trap. The window is
shown in Fig. 2.13-1.
The Logs Table is automatically refreshed every few seconds and can collect up to 200 entries
comprehensive of time stamp and event description.
The Logs Table is used as a circular buffer; therefore as soon as the table is full, a new entry will
overwrite the oldest one.
The Logs list can be scrolled for access to all records using the lateral cursor.
For an easier and immediate comprehension of the different classes of events and to facilitate
logger analysis, the log traces of the events are displayed with different background colors:
-
Alarms (affecting Alm) (Raised or Cleared)

Warning Information (affecting Warn) (Raised or Cleared)
System Configuration Commands and Generic information
red
yellow
no colour
The logs can be sorted in Ascending or descending order by Time, Type or Event.
Page 41 of 88
Figure 2.13-1: Logs window

For a detailed description of the meaning of each alarm indication refer to Tables 5.32, 5.33 and
5.34 in Chapter 5 using the Alarm Name in the Description as a key.
In the Log there are also reported Micro Interruption Notification messages which are inserted
when signal interruptions shorter than 1 sec. (which do not raise any alarm) are detected in the
received signal. The format of the message is the following:
Radio Micro-interruption detected for xxx msec where xxx is the No. of msec when the signal was
below the HighBER Alarm threshold in the last second.
These messages have yellow background colour.
The Micro Interruption Notification can be Enabled [ ]or Disabled [
] clicking in the box
Microinterruption at the bottom of the window.
Three buttons are available at the bottom of the window:
<Refresh>: Pressing the button Refresh, the displayed list is updated.
<Delete All>: all logger entries are cancelled.
<Export> : By pressing this button the window here below (Fig. 2.13-2) is displayed,
allowing to save the log on file on the CT PC. The file is formatted with Comma Separated
Values format which can be opened by most known spreadsheets applications.
The file name is: Logs_<SysName>_<LocationName>_yyyy_mm_dd_hh.mm.ss.csv
Once the file has been downloaded, it can be processed opening the relevant application on PC.
Page 42 of 88
2.14.
Statistics
This window (which can be opened by the Main Menu link Equipment/Statistics) allow to access
and display a set of statistical counters available in the system to monitor traffic flowing through the
system and its quality. The window is shown in Fig. 2.14-1.
Figure 2.14-1: Statistics window
Page 43 of 88
Figure 2.13-2: Pop-up window for file export
Ethernet Traffic Data related to one of the Ethernet Interfaces of the system can be displayed by
selecting in the combo-box Port the appropriate value:
- USER (only for PSE or IDUnE1 configuration)
- LCT (only for PSE or IDUnE1 configuration)
- POE (available in all configurations; in case of PSE or IDUnE1 configurations POE
counters are also approx. representative of the traffic on the Radio Port of the link)
For each set of counters the data of Table 2.11 are displayed and three set of counters are
provided for each interface:
Free Running Counters displayed in the Free Running Counters area. These counters
are manually operated. The counters are always freely running and a new observation
period can be started by clicking on the <Reset> button. The current counters values are
displayed when the window is opened and can be updated by pressing the button
<Update>.
15 minutes Historical Counters displayed in the Records area by selecting the 15

minutes tab. When the data collection is enabled, the relevant events start to be counted in
the current (Interval = 0) 15min counter up to the end of the next 15min period.
At the end of each 15min period the current 15min counter:
o is stored as new Interval with the its timestamp
o is added to the current 24h counter
o restarts counting
Counters related to the past collected 15min periods (Intervals) are displayed (one Interval
per row) up to a max of 96 periods (1 day).
24 hours Historical Counters displayed in the Records area by selecting the 24 hours
tab When the data collection is enabled, the current (Interval = 0) 24h counter is
incremented at the end of each 15 period. At the end of each 24h period the current
(Interval = 0) 24h counter.
o Is stored as a new Interval
o restarts counting.
Counters related to the past collected 24h periods (Intervals) are displayed (one Interval per
row) up to a max of 7 periods (1 week).
Parameters
Type
Interval
Timestamp
In Packets
In Octets
In Errors
In Discards
Out Packets
Out Octets
Out Discards
Monitored
Time
Description
Data provided for each Ethernet Interface
Progressive Number of the collected period
Date and time (year, month, day and hour, min, sec)
of the end of the counting period
Total number of Ethernet Frames received on the port
Total number of bytes received on the port, including
framing bytes
Total number of Ethernet Frames received on the port
that contain errors
Total number of Ethernet Frames received on the
port discarded due to internal lack of resources
Total number of Ethernet Frames transmitted out of
the port
Total number of bytes transmitted out of the port
including framing bytes
Total number of Ethernet Frames which have been
discarded due to lack of link capacity
Values
-
0 for Free Running

0 to 96 for 15
0 to 7 for 24h
Format
yyyy/mm/dd hh:mm:ss
Dec. Number
Duration of the counting period (stop-start time)
Dec. Number
Dec. Number
Dec. Number
Dec. Number
Dec. Number
Dec. Number
Seconds
Table 2-14: Data recorded for each Statistics set of counters
Page 44 of 88
<Reset>: The Free Running Counters are always freely running: a new observation period
can be started by clicking on the <Reset> button which reset the counters and start a new
monitoring period
<Update>: The window displays the current counters values and stored interval records
when the window is opened: they can all be refreshed by the operator by clicking on the
<Update>button.
<EnableDisable>: this button is relevant to the set of Historical Counters selected by the
active tab in the Records area. By clicking on the button the status is reversed
o When Enabled () the counters are regularly incremented
o When Disabled ( ) the counters are frozen at the last value
o The transition from Disabled to Enabled clears all historical counters
<Export> : By pressing this button a dedicated pop-up window is opened (see Fig. 2.13-2)
and the set of Historical Counters selected by the active tab in the Records area can be
saved on the CT PC. The file is formatted with Comma Separated Values format which can
be opened by most known spreadsheets applications. The name of the file is:
Statistics15min_<SysName>_<LocationName>_yyyy_mm_dd_hh.mm.ss.csv
or
Statistics24h_<SysName>_<LocationName>_yyyy_mm_dd_hh.mm.ss.csv
Once the file has been downloaded, it can be processed opening the relevant application on
PC.
2.15.
Performances
This window (which can be opened by the Main Menu link EquipmentPerformances) allow to
access and display a set of statistical counters available in the system to monitor quality
performances of the link. Two types of Performances parameters can be monitored by selecting in
the combo-box PM type the appropriate value:
- Radio Link (Fig. 2.15-1): reports statistics about errors (Errored Seconds) on the received
radio signal. The performances are evaluated by counting seconds of transmission when
errors are detected in the received signal by controlling the parity checks of the GFP
frames both when ETH frames or dummy frames are received. The information displayed
is described in the Table 2.12.
- Rx Power (Fig. 2.15-2): reports statistics about the received power level of the radio signal
The performances are evaluated by counting seconds when the signal level is below two
reference thresholds (related to levels with degraded operation). The information displayed
is described in the Table 2.13.
Page 45 of 88
A number of command buttons in the top line of the window allow to manage the data collected by
the counters relevant to the selected Interface.
Note: As a restriction of the current release the buttons affect all interfaces.
Figure 2.15-1: Performances window: Radio Link
Figure 2.15-2: Performances window: Rx Power
Page 46 of 88
Current Counters displayed in the Current area. These counters display the counters
related to the present 15 minutes period (Interval 0) when the data collection is enabled,
the relevant events start to be counted up to the end of the next 15min period. The current
counters values are displayed when the window is opened and can be updated by pressing
the button <Update>.
15 minutes Historical Counters displayed in the Records area by selecting the 15

minutes tab. At the end of each 15min period the current 15min counter:
o is stored as new Interval with the its timestamp
o is added to the current 24h counter
o restarts counting
Counters related to the past collected 15min periods (Intervals) are displayed (one Interval
per line) up to a max of 96 periods (1 day).
24 hours Historical Counters displayed in the Records area by selecting the 24 hours
tab When the data collection is enabled, the current (Interval = 0) 24h counter is
incremented at the end of each 15 period. At the end of each 24h period the current
(Interval = 0) 24h counter.
o Is stored as a new Interval
o restarts counting.
Counters related to the past collected 24h periods (Intervals) are displayed (one Interval per
line) up to a max of 7 periods (1 week).
A number of command buttons in the top line of the window allow to manage the data collected by
the counters relevant to the selected PM type.
<Reset>: The <Reset> button clears simultaneously all the historical records
<Update>: The window displays the current counters values and stored interval records
when the window is opened: they can all be refreshed by the operator by clicking on the
<Update>button.
<EnableDisable>: this button is relevant to the set of Historical Counters selected by the
active tab in the Records area. By clicking on the button the status is reversed
o When Enabled () the counters are regularly incremented
o When Disabled ( ) the counters are frozen at the last value
<Export> : By pressing this button a dedicated pop-up window is opened (see Fig. 2.14-2)
and the set of Historical Counters selected by the active tab in the Records area can be
saved on the CT PC. The file is formatted with Comma Separated Values format which can
be opened by most known spreadsheets applications. The name of the file is:
Performances15min_<SysName>_<LocationName>_yyyy_mm_dd_hh.mm.ss.csv
or
Performances24h_<SysName>_<LocationName>_yyyy_mm_dd_hh.mm.ss.csv
Once the file has been downloaded, it can be processed opening the relevant application
on PC.
Page 47 of 88
Two set of counters are displayed in two window areas:
Parameter
Type
Interval
Timestamp
ES
SES
UAS
Monitored
Time
Description
Values
Show date and time (year, month, day and hour, min,
sec) of the end of the counting period.
Total Number of seconds where in the received signal
at least a frame has been detected in error by parity
checks
Total Number of seconds in which > than 10% of GFP
frames are received in error (detected either by CRC
or FCS)
Total Number of seconds in which the radio link has
been unavailable. The link is unavailable when a
valid Rx signal is not present (RxPwAlm or DemAlm)
or from the onset of 10 contiguous SES. The
unavailability period ends with no Rx alarms at the
onset of 10 contiguous seconds with no SESs
0 for Current
0 to 96 for 15
0 to 7 for 24h
Format
yyyy/mm/dd hh:mm:ss
Dec. Number
Dec. Number
Dec. Number
Duration of the counting period
Seconds
Table 2-15: Counters reported by the Performances Radio Link

Parameter
Type
Interval
Timestamp
LSS
NSS
UAS
Monitored
Time
Description
Values

Show date and time (year, month, day and hour, min,
sec) of the end of the counting period.
Low Signal Seconds: Total Number of seconds in
which the received power has been at least for a
sampling period less than the following threshold
(related to the CS):
CS= 3.5 kHz < -88 dBm
CS= 7 kHz < -86 dBm
CS= 14 kHz < -83 dBm
CS= 28 kHz < -80 dBm
Note: These thresholds are approximatively
corresponding to LowBER operation.
No Signal Seconds: Total Number of seconds in
which a Rx Power defect (see Table 5-8 RxPwAlm)
has been detected at least for a sampling period.
Total Number of seconds in which the radio link has
been unavailable. The link is unavailable when a
valid Rx signal is not present (RxPwAlm or DemAlm)
or from the onset of 10 contiguous NSS. The
unavailability period ends with no Rx alarms at the
onset of 10 contiguous seconds with no NSSs
0 for Current
0 to 96 for 15
0 to 7 for 24h
Format
yyyy/mm/dd hh:mm:ss
Duration of the counting period
Dec. Number
Dec. Number
Dec. Number
Seconds
Table 2-16: Counters reported by the Performances Rx Power
Page 48 of 88
Configuration Files
In the Main Menu these links (e.g. Configuration FilesBackup) allow to save in an external
back-up file and to retrieve all configuration data (MIB) of an equipment, avoiding the need to
reconfigure these data manually by CT in case of ODU replacement or whenever it is required to
restore the configuration.
Note:
see par. 5.3.1 for more details about ODU replacement
it is recommended to perform Backup at any modification of the station configuration
2.16.1 Backup
Station configuration can be saved by clicking on the link Configuration FilesBackup of the
Main Menu .
<Export> : By pressing this button the pop-up window here below (Fig. 2.16-1) is displayed
and a file with all system Configuration Data is saved on the PC used as CT.
The name of the file is
MIB_<SysName>_<LocationName>_yyyy_mm_dd_hh.mm.ss.csv
and it is downloaded in the Desktop/Documents/Download directory.
The operator can afterwards move (operating on the CT PC) the file in the assigned
directory for backup.
Figure 2.16-1: Pop-up window opened to perform MIB Back-up
2.16.2 Restore
The configuration (MIB) of the equipment can be restored retrieving from the CT in case of need
the back-up MIB file (previously saved with the Backup procedure) by clicking on the link
Configuration FilesRestore of the Main Menu.
The pop-up window of Fig. 2.16-2 opens and it is required to:
- first press the <Select file> button in the pop-up window
- in the directory used for backup select the configuration file to be restored
- press the <Upgrade> button of the pop-up window
At the end of the transfer (100%) of the MIB file, the equipment will reboot and restore the desired
configuration.
Page 49 of 88
2.16.
Figure 2.16-2: Pop-up window opened to perform MIB Restore
2.17.
External Links
In the Main Menu are links (External LinksRemote Terminal) which allow to access and open a
CT connection with the other equipment of the same radio link simply by clicking on the link name.
The normal Password authorization is requested when the connection is opened.
Depending on the type of radio link access is provided to:
Remote Terminal allows to open and access directly the CT of the Remote Terminal of
the link (i.e. the equipment of the radio link located in the Remote station. In case of 1+1
radio links, the Remote Terminal is defined as the equipment of the remote station with the
same protection role in the protection group)
Mate Terminal available only in 1+1 HSB configuration. Allows to open and access
directly the CT of the Mate Terminal of the link (i.e. the equipment of the radio link
colocated in the same Local station)
Mate-Remote Terminal available only in 1+1 HSB configuration. Allows to open and
access directly the CT of the Mate-Remote Terminal of the link (i.e. the Equipment of the
radio link located in the Remote station and with the opposite protection role in the
protection group)
The IP Addresses of the Terminal must be previously configured by using the System Settings
window.
It has to be noted that:
1. The Remote Terminal(s) of the link could be accessible only if the radio link is in normal
operation.
2. As in the case of connecting any terminal using its own IP address, the operator must be
careful not to issue commands that could put out of service the remote system because the
system is not able to filter dangerous operations. Otherwise if the radio link is cut by
improper operators commands, the remote terminal could become unreachable and a
manual local intervention in the terminal to restore service may be necessary.
Page 50 of 88
Admin
The Admin links in the Main Menu (e.g. AdminUpgrade) allow to execute some system
administration tasks. In the following the available tasks are described in details.
2.18.1 Upgrade
The Upgrade window can be opened by clicking on the link AdminUpdate and allows the
management of the SW loads of the system and the download of new SW.
The window is shown in Fig. 2.18-1.
In the window there are displayed:
Active SW information (Version, Date, Checksum) associated to the SW load currently
running on the system
StandBy SW information (Version, Date, Checksum) associated to the SW load currently
stored in the back-up memory.
Figure 2.17-1: Upgrade window

In the StandBy SW area two buttons are available:
a. Activate: by pressing this button a soft system restart is initiated loading as Active SW the
StandBy SW load available as back-up. At the end of the restart the old StandBy SW
becomes Active SW and the old Active SW is stored as back-up. In the case the new SW
does not operate correctly and generates continuous restarts, after five restarts the system
is automatically switched back to the stand-by bank and operates with the previous SW
release.
Page 51 of 88
2.18.
Download: a new SW load can be retrieved from a network server on the system and
transferred to the FTP server running on the system. The new SW load is stored as
StandBy SW.
The download procedure is as follows:
o Pressing the button the SW Download pop-up window (Fig. 2.18-2) opens
o In the SW Download pop-up window click on Select File and write the path
where the file to be downloaded is located in the PC.
o check that in the window that the correct path is displayed
o click on the button Upgrade in the window to start the file download.
o The pop-up window is closed and Download in progress appear in the Standby
Software area
o When the transfer is completed, the info about the StandBy SW is updated.
o In case of a correct transfer cannot be completed an error message is displayed
Note: Differently from past Releases the new SW is not automatically activated. Therefore
to execute the SW upgrade the <Activate> button has to be pressed.
During the download of new software the system is operating normally and the traffic is not
affected. A short traffic interruption happens during the bank switch with restart.
Figure 2.17-2: SW Download pop-up window

Specific instructions for SW download in 1+1 HSB Systems. The SW download has to be
executed only on ODU in Stand-by status. Therefore it is required to put the Protection Group in a
Forced status using the Protection window on the ODU Main with External Request set to:
Forced if SW download has to be executed on the ODU Protection
Lockout if SW download has to be executed on the ODU Main
2.18.2 Change Password

It allows the management of the password changing the current password when required. Clicking
on the link AdminChange Password open the dedicated pop-up window as shown in Fig. 2.18-3.
Page 52 of 88
After the operation is executed, the pop-up window closes automatically and the new Password is
active.
Figure 2.17-3: Change Password window
2.18.3 Logout
It allows to close the CT session and to release the connection with the equipment closing all
windows open.
The logout is performed by clicking on the link AdminLogout of the Main Menu.
2.19.
Export Tx and Rx Power Data to OS
The system stores in dedicated files Tx and Rx Power data which can be retrieved on request by
the OS by means of a FTP transfer to the OS itself.
Separate files buffers Tx and Rx data. Each file includes 900 power measurements samples, which
are stored every sec.: therefore each file includes the data of a 15min period.
In the system up to 192 are maintained for a total time of measurement of 48 hours. The 192 files
are a cyclic buffer where the oldest file is replaced by the most recent one.
Page 53 of 88
It is required to enter:
1. the Username (Username has the default value operator which cannot be changed)
2. the old Password
3. the new Password
4. again the new Password in the Repeat New Password field
5. click on the button <Change> when all fields are properly set
Each file is named:

YYYYMMDDhhmm.rxlog for the files with Rx Power data
YYYYMMDDhhmm.txlog for the files with Tx Power data
where YYYYMMDDhhmm is the date (year, month, hour, minute) of the first sample recorded in
the file (timestamp).
Each file is a binary array where each sample is stored in a record of:
- 6 bits for txlog files
- 7 bits for rxlog files
The records are stored sequentially in the file.
The record is an unsigned integer, coding the Tx and Rx power in dBm at steps of 1 dB as in the
Table.
txlog
rxlog
Code
(binary)
000000
000001
Tx Power
(dBm)
-30
-29
Code
(binary)
0000000
0000001
Rx Power
(dBm)
-120
-119
......
......
......
......
......
......
......
......
111110
111111
+32
+33
1111110
1111111
+6
+7
Therefore the size of each file is:

- 675 bytes for txlog files
- 788 bytes for rxlog files
To retrieve the files from OS an FTP client must be used with:
User = operator
Password = o
In case of system restart the txlog and rxlog files stored in the system are not cleared.
Page 54 of 88
Perform Configuration by CT
In this chapter reference is made to a configuration where a LCT is directly connected to the PSE
or to the IDUnE1: in case the CT is connected remotely (RCT) via an IP network (e.g. in case of
PoE configuration) the same procedures can apply with the required minor adaptations.
In the Tables 3.14 to 3.28 there is detailed how to proceed to perform the most common
configuration actions on the system.
CT Window
Procedure
For the initial connection of the CT see installation instructions in par. 2.4 and 2.5.
It is recommended at the first installation to immediately change the default password with a new
one by the procedure detailed in par. 2.18.2
Define Configuration (IDU Type) according to the HW configuration
System Settings:
In case of PSE configuration only: It is required to define the protection
System Config
type - unprotected or protected with associated protection role. (main or
(par. 2.11)
protection)
System Settings:
Protection
(par. 2.11)
System Settings:
IDU Management
(par. 2.11)
System Settings:
Management
Interface (par. 2.11)
System Settings
System Time
(par. 2.11)
System Settings:
System Identity
(par. 2.11)
Radio Interface
Backup (par. 2.16.1)
Only In case of 1+1 HSB link, Protection Group parameters must be

defined on the ODU Main.
For configuration with an IDU, setting at system start of the IDU MAC
Address is required (manual or automatic upload). The same has to be
repeated when the IDU is replaced (maintenance)
The networking data required to allow the connection to the OS or the
Craft Terminal (CT) can be configured and later modified during the life of
the system by this window.
Data and Time can be synchronized with the CT PC clock by entering
Local in the Sync Source field and press <Apply>.
Note: even if Local is displayed in the Sync Source field, synchronization
is executed only when <Apply> is pressed.
Data and Time can be synchronized with an NTP server by entering:
- NTP in the Sync Source field
- the NTP IP address in the NTP Server field
- the relevant Time difference in the Time Zone field
- press <Apply>.
Note: an immediate synchronization is executed when pressing <Apply>.
Afterwards with this setting a resynchronization is automatically executed
every 30. In any case a synchronization is executed at system restart if
the NTP Server has been defined.
Daylight Saving time shift can be applied using the DaylightSavings field.
Names for Location, System and Station are not mandatory for the
operation of the system. They can be entered by the operator to facilitate
administration of the system or interworking with OS.
Before configuring the Radio Channel is mandatory to squelch the
Transmitter
Enter down in the AdminStatus in Interface and press <Apply>.
Verify that the TxPwr in the Summary System Status has the value -128
Warning: Squelching Tx cuts service on the link and on the Remote
terminal may make the terminal unreachable
After any new configuration or modification of the system it is
recommended to save the MIB file on the CT.
Table 3-17: System Configuration
Page 55 of 88
3.
CT Window
Procedure
Only when it is required to Cipher the radio Channel.
System Settings:
System Identity
(par. 2.11)
To avoid that the receiver could detect a signal from another interfering
link (specifically when its own received signal is off) it is possible to cipher
the radio signal in Tx and decipher in RX using as a key the Encryption
Key to be entered in System identity.
The two (four in case of 1+1 HSB) equipment terminating the link must be
set with the same Encryption Key to allow correct ciphering operation.
Note: if the Encryption Keys are different the radio link does not operate
Note: to avoid to cipher the radio signal, the Encryption Key must be null.
Only when it is required to Enable SynchE operation

Radio Interface
Modem
(par. 2.8)
When the system is required to work in a SynchE network the clock must
be transported transparently in both directions. In rel. 2.1 this is supported
only in the PoE configuration setting Enabled in the Clock Transparency
field in both terminals of a link.
In such a case the outgoing FE signal out of the local ODU is
synchronized with the incoming FE signal into the remote ODU and
viceversa.
Inventory &
Housekeeping
Housekeeping
(par. 2.12)
Only when Housekeeping signals are used

Note: Not applicable to PoE configuration
The characteristics associated to these signals can be configured and
modified entering CloseActive or OpenActive options in the Mode field
relevant information (see par. 2.13)
Table 3-18: System Configuration (optional features)
Page 56 of 88
Radio Interface
Interface
(par. 2.8 )
Procedure
Turn off the Tx as described in Table 3.14.
This action is mandatory before any modification is applied to Radio
Channel and Channel Bandwidth.
Setting the Radio Channel bandwidth and Transmission rate:
In the Modem section of the window select the Channel Spacing and
press <Apply>
Radio Interface
Modem
(par. 2.8)
Verify that the CS in the Summary System Status displays the correct
value. The corresponding capacity is
Channel Bandwidth (CS)
Capacity
28 MHz
14 MHz
7 MHz
3.5 MHz
Setting the Channel Frequency:
36 Mbps
18 Mbps
9 Mbps
4.5 Mbps
Enter Tx Frequency in Frequency and press <Apply>
Radio Interface
Frequency
(par. 2.8)
The value has to be in the range (Tx Min Frequency Tx Max Frequency)
displayed in RadioInfo
Verify that Tx Frequency and Rx Frequency in Summary System Status
displays the correct values according to the shifter value displayed in TxRx Shift of RadioInfo
Setting the power level if fixed power operation is selected.
Enter the value in Tx Power in Power and press <Apply>
The value has to be in the range (Tx Min Power to Tx Max Power)
Enter up in the AdminStatus in Interface and press <Apply>
Verify that the TxPwr indication in the Summary System Status has the
correct value
Radio Interface
Power/Interface
(par. 2.8)
Setting the power level if atpc operation is selected.

Enter the values in
ATPC Min
ATPC Max
ATPC Target
in Power and press <Apply>
The Min and Max Power Lev values have to be in the range (Tx Min
Power -Tx Max Power) displayed in RadioInfo
Enter atpc in the AdminStatus in Interface and press <Apply>
Verify that the TxPwr indication in the Summary System Status has a
value compatible with current operation conditions of the link

Table 3-19: Setting the Radio Channel (Licensed Bands)

Note: the setting must be executed on both terminals of the link in a consistent way
Page 57 of 88
CT Window
CT Window
Procedure
Radio Interface
Modem
(par. 2.8)
To have a more detailed view of the interfering spectrum set up the link
with CS= 3.5 MHz
Configuration to be
made on both terminals
of the link
In the Modem section of the window select the Channel Spacing and
press <Apply> Verify that the CS in the Summary System Status
displays the correct value.
Radio Interface
Frequency
(par. 2.8)
Set up the link frequencies manually using two frequencies working even
if not optimized.
Configuration to be
of the link
Radio Interface
Power/Interface
(par. 2.8)
Configuration to be
of the link
Radio Interface
Frequency
(par. 2.8)
Operating on the Local
terminal of the link
Enter Tx Frequency and Rx Frequency in Frequency and press <Apply>

.The values have to be in the range (Min /Max Frequency displayed in
RadioInfo
displays the correct values as well as Tx-Rx Shift of RadioInfo
correct value
Open on the Local terminal the Radio Frequency Seeker by clicking on
the dedicated button in Frequency.
The Seeker window will open (see Fig. 2.8-2)
Click on the <Interference Power Scan Start> button.
Both Tx at the ends of the link are shut down.
Seeker Window
Both Rx at the ends of the link scan in parallel the available band Tx
Freq.min-Tx Freq. max measuring the PRx power level (due to interfering
signals from other systems) at steps of 7 MHz and an equivalent
bandpass filter of 3.5 MHz. Ten measurements at each frequency are
recorded and the Min, Mean and Max values of the PRx power
measured in both terminals (local A and remote B) of the link are stored in
a file. This process takes about 100 s.
When the scan is completed (100% in the Progress bar) the link is again
turned on and it is possible to open the file and read the results as a Table
(by clicking on <Show Tables> button) or as a graph (by clicking on
<Show Graphics> button) (see Fig. 2.8-2). In the FOUND FREQUENCIES
window there are shown the two frequencies where the lowest PRx Max
has been measured in A and B terminals.
Close the procedure.
Table 3-20: Estimation of radio Interferences from other systems - Unlicensed Bands
Note: This procedure can be used to evaluate the radio interferences in the unlicensed bands before
setting up a new link by making use of the Radio Frequency Seeker tool provided by the system.
It is recommended to execute such an analysis before setting up the link (Table 3.19 or 3.20/21).
If the link is not up and only the local terminal is accessible by the LCT, it is possible to perform in any
case the power scan to measure the interference power in the local terminal.
Page 58 of 88
Table 3-21: Scan results display of the Frequency Seeker
CT Window
Radio Interface
Modem (par. 2.8)
Radio Interface
Frequency (par. 2.8)
Radio Interface
Power/Interface
(par. 2.8)
Procedure
In the Modem section of the window select the actual Channel Spacing to
be used and press <Apply> Verify that the CS in the Summary System
Status displays the correct value.
Set up the link frequencies manually using two frequencies working even
if not optimized.
Enter Tx Frequency and Rx Frequency in Frequency and press <Apply>
.The values have to be in the range (Min /Max Frequency displayed in
RadioInfo
Setting the power level if fixed power operation is selected.
correct value
Setting the power level if atpc operation is selected.
Enter the values in ATPC Min, ATPC Max, ATPC Target in Power and
press <Apply>
The Min and Max Power Lev values have to be in the range (Tx MinPower
-Tx MaxPower) displayed in RadioInfo
Table 3-22: Setting the Radio Channel (manually) - Unlicensed Bands

Note: After a power scan it is possible not to use the Apply Frequency button and input manually the
two operating frequencies (chosen based on the power scans) in the appropriate fields (Tx Frequency
and Rx Frequency of both terminals)
Note: Configurations are to be made on both terminals of the link in a consistent way
Page 59 of 88
Scan results - Graphics
Scan results - Table
CT Window
Radio Interface
Modem
(par. 2.8)
Configuration to be
Radio Interface
Frequency
(par. 2.8)
Configuration to be
Radio Interface
Power/Interface
(par. 2.8)
Configuration to be
Radio Interface
Frequency (par. 2.8)
Seeker Window
Procedure
In the Modem section of the window select the actual Channel Spacing
to be used and press <Apply>
Verify that the CS in the Summary System Status displays the correct
value.
After having selected the frequencies to be used in both directions on the
link:
Enter Tx Frequency and Rx Frequency in Frequency and press <Apply>.
The values have to be in the range (Min /Max Frequency displayed in
RadioInfo
Note: if a value 0.00 is entered in Rx Frequency the default Tx-Rx Shift
value will be applied and Rx frequency will be set automatically according
to this shift.
Enter a suitable value in Tx Power in Power and press <Apply>
correct value
Open on the Local terminal the Radio Frequency Seeker by clicking on
the dedicated button in Frequency.
The Seeker window will open (see Fig. 2.9-2)
Click on the <Interference Power Scan Start> button.
Both Tx at the ends of the link are shut down.
Both Rx at the ends of the link scan in parallel the available band Tx
Freq.min-Tx Freq. max measuring the PRx power level (due to interfering
signals from other systems) at steps of 7 MHz and an equivalent
bandpass filter of 3.5 MHz. Ten measurements at each frequency are
recorded and the Min, Mean and Max values of the PRx power
measured in both terminals (local A and remote B) of the link are stored in
a file. This process takes about 100 s.
When the scan is completed (100% in the Progress bar) the link is again
turned on and it is possible to open the file and read the results as a Table
(by clicking on <Show Tables> button) or as a graph (by clicking on
<Show Graphics> button) (see Fig. 2.9-2). In the FOUND FREQUENCIES
window there are shown the two frequencies where the lowest PRx Max
has been measured in A and B terminals, which should be selected as
optimum working points for the link. The Tx in the opposite terminal are
configured with the same frequencies.
By clicking on the <Apply Frequencies> button it is possible to
automatically set the Tx and Rx frequencies of both terminals consistently
with the above values. The resulting shifter parameter (TX-RX) is not the
default. Whenever It is necessary it is possible to set the default value of
this parameter just entering the value 0.00 in the RX frequency field of the
radio interface.
The procedure checks that within 60 s. all alarm of the link are cleared,
indicating that a normal status has been reached in the new configuration
with lowest interferences. If he link does not reach this normal condition
an automatic reset is executed and frequencies are set again to the initial
preset values.
Table 3-23: Setting Radio Channel (using Radio Frequency Seeker) - Unlicensed Bands
Page 60 of 88
Procedure
Setting the final power level if fixed power operation is selected.
Radio Interface
Power/Interface
(par. 2.8)
Configuration to be

correct value
Setting the final power level if atpc operation is selected.
Enter the values in ATPC Min, ATPC Max, ATPC Target in Power and
press <Apply>
The Min and Max Power Lev values have to be in the range (Tx MinPower
-Tx MaxPower) displayed in RadioInfo
Table 3-24: Setting Radio Channel (using Radio Frequency Seeker) - Unlicensed Bands
Note: This procedure can be used to optimize the working conditions of the link by making use of the Radio
Frequency Seeker tool provided by the system.
All interference power measurements are made using a bandwidth equal to the actual radio capacity
previously chosen in the Modem: Channel Spacing field.
Note: Configurations are to be made on both terminals of the link in a consistent way
Page 61 of 88
CT Window
CT Window
Procedure
Physical connection in case of PoE configuration

Verify that the User equipment is properly connected to the POE unit feeding the ODU both in the
local and remote terminals of the link.
Physical connection in case of PSE or IDUnE1
The relevant ETH port (either User or Lct) on the front panel of the IDU must be cabled to the user
equipment both in the local and remote terminals of the link by a cat.5 Cable.
To configure an User port (connecting an User equipment) operate on the
relevant row (Label = lct, usr or poe) of the Config area.
- Set Enable in the UserMode field
- Configure the other fields (Autonegotiation, Speed, Duplex,
FlowControl) according to the operation mode to be used.
in case Autonegotiation is disabled the Interface will operate
according
to
the
parameters
set
by
the
operator.
in case autonegotiation is enabled the resulting mode of operation will
be the result of the autonegotiation process and could change
Ethernet Interface
according to settings of the User equipment also during the operation
of the system.
Config (Par. 2.9)
- Optionally define the appropriate Rate Shaping, Default VID and Prio
using the corresponding fields. If VID and Prio are set to 0 no VLAN
Tag will be added.
- Optionally enter a symbolic name in the Name field to facilitate
identification of the port for administration and maintenance.
- Port Alarm field should be normally set to Enabled. Set it to Disabled
to suppress Alarm reporting (particularly in case of maintenance or
out-of-service of the interface).
- Press<Apply> to execute any change to the configuration
To be configured (Enabled) only if the data traffic has to be managed
with different priority based on its COS.
Note: Priority is applied to all data traffic flowing in the equipment
independently from the originating Ethernet Interface.
- Set QoS key to Enabled.
Ethernet Interface
- Enter in the Priority0 field the list of the values of COS which need to
be forwarded with higher priority
QoS
Enter
in the Priority1 field the list of the values of COS which need to
(par. 2.9)
be forwarded with lower priority
- Press<Apply> to execute any change to the configuration
Otherwise if traffic has to be managed without priority Set QoS key to
Disabled and press <Apply>.
Ethernet Interface
Status (Par. 2.9)
Radio Interface
Radio Config
System Status
Alarms
Ethernet Interfaces
(par. 2.7.3)
Verify in the relevant row (Label = lct, usr or poe) the actual settings of
the port.
In case it is required by the protection protocols used in the Ethernet L2
Network to assure that any unidirectional operation of connections is
avoided it is required to set to Enabled the UnidirLinkAvoidance (ULA)
field in the Interface area.
After all Ethernet interfaces have been configured in both Local and
Remote terminals of the link the correct operation of the data connection
should be checked for both local and remote terminals.
Specifically no ETH Interface Alarms should be present on the radio
terminals.
Data continuity checks can be arranged at network level in cooperation
with the Data Network manager.
Table 3-25: Ethernet Data Interface configuration
Page 62 of 88
Procedure
The network is operated to support only E1 circuits on a L2 Ethernet network including two
terminals equipment where the circuits are ended
In the case only E1 service is supported, all configurations can be made using the TDM Interface
window with the default 16 (8) rows associated to each port. The button <NewRow> should not be
used.
Before starting the procedure connect the CT to both Local and Remote equipment, opening a
window for each equipment (see par. 2.4)
Physical connection
The E1 port (input and output connectors) must be cabled to the external network (User) both on the
local and remote ends of the circuit.
Configuration of the E1 port (L) in the Local End
Operate on the row L in the area with the Port Number identifying the
port to be connected.
Select Unframed in the Type field
Select up in the Admin Status
Optionally Select ForcedAis in the Admin Status
local CT window
Note: This to inform the outside equipment that traffic is not flowing
TDM Interface
regularly
Optionally enter a symbolic name in the PortName field to facilitate
Config.
(par. 2.10)
Select False in the Connect field
Press <Save Changes> to execute the commands.
srcBundle and srcAddress are automatically displayed
timeslots is set to all
ConnectionName , dstBundle, dstAddress are normally null
Note: this step can be skipped if the port is already configured
local CT window
Verify the status of the relevant port L
Note: In case the physical connection to the user is not in place or the
System Status
user equipment is not in a normal operating condition, other alarms
Alarms TDM
indications could appear (e.g. LOS, etc.)
(par. 2.7.3)
remote CT window
Configuration of the E1 port (R) in the remote End

Operate on the row R in the area with the Port Number identifying the
port to be connected.
Select Unframed in the Type field
Select up in the Admin Status
Optionally Select ForcedAis in the Admin Status
Note: This to inform the outside equipment that traffic is not flowing
regularly
Optionally enter a symbolic name in the PortName field to facilitate
Select False in the Connect field
srcBundle and srcAddress are automatically displayed
timeslots is set to all
ConnectionName , dstBundle, dstAddress are normally null
Note: this step can be skipped if the port is already configured
Verify the status of the relevant port R.
System Status
Alarms TDM
(par. 2.7.3)
Note: In case the physical connection to the user is not in place or the
user equipment is not in a normal operating condition, other alarms
indications could appear (e.g. LOS, etc.)
remote CT window
TDM Interface
Config.
(par. 2.10)
Table 3-26: Provisioning a E1 circuit (Transparent Transport of an Unframed E1)
Page 63 of 88
CT Window
CT Window
Local CT window
TDM Interface
Config.
(par. 2.10)
remote CT window
TDM Interface
Config.
(par. 2.10)
Both Local and

Remote CT window
System Status
Alarms TDM
(par. 2.7.3)
Procedure
Configuration of the Connection in the Local End
Operate on the row L in the area with the Port Number= L identifying the
port used by the connection.
Enter R.00 in the dstBundle field (R is the Port No. in the remote
terminal)
Enter the MAC Address (last six digits) associated to the Remote
equipment in the dstAddress (equal to the srcAddress in row R of the
remote equipment)
Optionally enter a symbolic name in the ConnectionName field to
facilitate identification of the Connection for administration and
maintenance. It is recommended that the ConnectionName is defined
equal in Local and Remote ends.
Select False in the Connect field if the connection has not to be
immediately executed
Or
Select True to immediately operate the connection
Note: If the connection was defined previously and needs to be made
effective it is only required to Select True in the Connect field and press
<Save Changes> to execute the command.
Configuration of the Connection in the remote End
Operate on the row R in the area with the Port Number= R identifying the
port used by the connection.
Enter L.00 in the dstBundle field (L is the Port No. in the local
terminal)
Enter the MAC Address (last six digits) associated to the Local
equipment in the dstAddress (equal to the srcAddress in row L of the
Local equipment)
facilitate identification of the Connection for administration and
Or
Note: If the connection was defined previously and needs to be made
effective it is only required to Select True in the Connect field and press
<Save Changes> to execute the command.
Verify the connection: Verify the status of the relevant ports (row L on
local end and row R in the Remote end) once the Connection has been
executed.
If ports were configured with AdminStatus = ForcedAIS
No Alarm should be raised and the User equipment connected to the L
and R ports should report: no LOS alarm, AIS indication
If ports were configured with AdminStatus = up
No Alarm should be raised and Traffic is flowing through the network.
Table 3-27: Provisioning a E1 circuit (Transparent Transport of an Unframed E1)

Note: The two ends of the circuit are here referred to as Local and Remote ends and correspond to two E1
interfaces on two IDUnE1or EMX different equipment in the network. In some special cases the connection
can be terminated at one side on other commercial equipment of other supplier supporting SAToP
compatible mapping of E1 on Ethernet.
Page 64 of 88
Procedure
Local and Remote CT

window
TDM Interface
Config.
(par. 2.10)
Both Local and

Remote CT window
System Status
Alarms TDM
(par. 2.7.3)
Disconnect an E1 Connection.
An existing E1 circuit set up in the network can be disconnected operating
by the Local or Remote CT (TDM interface window) on the row of the
Connection List with PortName = No. of the E1 port associated to the
circuit:
- Setting Connect field to False
- Press <Save Changes> button.
Forwarding of outgoing frames to the network and E1 signal to the port is
inhibited. dstBundle,
dstAddress and ConnectionName information
associated to the connection is maintained in the MIB.
Note: connection can be re-established by setting again Connect field to
true and pressing <Save Changes> button.
Note: the circuit is disconnected operating either in the Local or Remote
equipment. To avoid that frames related to the circuit are sent by one
terminal even if the other is disconnected, it is required to disconnect the
circuit in both Local and Remote equipment. If only one terminal is
disconnected an EthLos alarm is raised in the other.
Delete an E1 Connection
An E1 circuit (either connected or disconnected) can be deleted and its
data erased from the MIB operating by the Local and Remote CT (TDM
interface window) on the row of the Connection List with PortName = No.
of the E1 port associated to the circuit:
- Set Connect field to Delete
The connection is cleared and the dstBundle,
dstAddress and
ConnectionName information associated to the connection is set to null.
To delete a circuit it is recommended to perform this operation in both
Local and Remote equipment.
Table 3-28: Disconnecting or deleting an existing E1 circuit
Page 65 of 88
CT Window
CT Window
Procedure
The network is operated to support both E1 and NxE0 circuits on a L2 Ethernet network
including the two terminals equipment where the circuit are ended.
Differently from the case of Table 2.8 (Networks with E1 circuits only) in the Connection List in the
TDM Interface more rows can be defined for a single port (each for a different connection).
In case a E1 circuit is implemented, the ports to be connected must be configured as Unframed and
only one row is displayed in both Local and Remote terminals. In such a case the procedure to
manage a connection is identical to the one described in Table 2.8 operating on the two rows of the
two relevant ports in the Local and Remote ends.
In case a NxE0 connection is implemented, the procedure of this Table apply. In the following the
two ports connected by the NxE0 circuit will be referred to as L in the Local equipment and R in the
Remote equipment. E1 ports are supposed already configured and their status should be not
modified when adding a new NxE0 connection. Before starting the procedure connect the CT to both
Local and Remote equipment, opening a window for each equipment (see par. 2.4)
Configuration of the E1 port (L) in the Local End and bundle creation
Create a new row at the top of the list pressing the button <NewRow> at
the bottom of the window
Operate on this row :
Enter the No. of the port (L) in the Port Number field
Select Framed in the Type field if not already configured
Optionally enter a symbolic name in the PortName field
Select up in the Admin Status if not already configured
Enter in the Timeslots field a list of E0 (N timeslots) to be associated
for the circuit (Bundle). The list is of the type: x,y,t-w, etc where t-w
means all E0 between t and w included.
Enter in the field srcBundle its identification L.xx where xx is the No.
of the first timeslot of the bundle
Enter R.yy in the dstBundle field (where R is the Port No. and yy is
the No. of the first timeslot of the bundle in the Remote terminal)
Enter in the dstAddress the MAC Address
(last six digits)
associated to the Remote equipment = the srcAddress in the Remote
equipment
local CT window
facilitate
identification of the Connection for administration and
TDM Interface
Config.
(par. 2.10)
Or
Press <Save Changes> to execute the commands. The row is
reordered in the list and will replace the existing row L if previously it
was configured as unframed or will be added as a further row with the
same Port Number L to the list if other connections were previously
defined for that port.
srcAddress is automatically displayed
Note: Consistency checks are implemented when defining a new
connection to avoid to enter data conflicting with the existing connections
already defined. If these checks fail the command execution is refused
and the new data are not entered in the system.
Note: Care has to be taken to verify that the No. of timeslots is the same
in both Local and Remote bundles, even if they can be different.
Warning: when more rows (NxE0 connections) are defined for the same
port, any change to the port attributes (Name, AdminStatus, etc.) is
modified for all connections
Table 3-29: Provisioning a NxE0 circuit between Framed E1 (cont.)
Page 66 of 88
Remote CT window
TDM Interface
Config.
(par. 2.10)
Both Local and
Remote CT window
System Status
Alarms TDM
(par. 2.7.3)
Procedure
Configuration of the E1 port (R) in the remote End and bundle
creation.
The same steps performed on the Local terminal (see above) must be
repeated in the remote terminal, with the relevant parameters for the
remote Terminal.
Verify the connection: Verify the status of the relevant ports (row L on
local end and row R in the Remote end) once the Connection has been
executed.
No Alarm should be raised and Traffic is flowing through the network.
Table 3-30: Provisioning a NxE0 circuit between Framed E1 (cont.)
CT Window
Both Local and

Remote CT window
System Status
Alarms TDM
(par. 2.10)
Procedure
Delete a NxE0 Connection
A NxE0 circuit can be deleted and its data erased from the MIB operating
by the Local and Remote CT (TDM interface window) on the row of the
Connection List with:
PortName = No. of the E1 port associated to the circuit
srcBundle indicator associated to the circuit.
The following steps are required:
- Set Connect field to Delete
The connection is cleared and the row related to the circuit is deleted from
the Connection List.
The other rows related to other NxE0 bundles of the same E1 are not
affected as well as the port status and configuration.
Note: If the deleted row is the last one related to a E1 port, it is
recommended to recreate manually the default row for the E1 port by
using the <NewRow> button.
To delete a circuit it is recommended to execute at the same time the
procedure in both Local and Remote equipment.
Table 3-31: Deleting an existing NxE0 circuit
Page 67 of 88
CT Window
4.
Supervision by RCT or OS
4.1
General
In addition to the supervision by a Local Craft Terminal (LCT) connected to the PSE or IDU16E1,
the CIPHOP IP supervision can be performed and the system can be operated remotely:
by means of a Remote Craft Terminal (RCT)
in TMN OS mode.
Note: the remote operation is the only possible in the PoE configuration.
The RCT mode allows the possibility to connect one computer (PC) to the same IP network where
the radio link is included to supervise a group of equipments at the same time from a remote
location. All the facilities offered by the Web Manager interface available for LCT mode are
supported by RCT after the PC is properly connected to the relevant equipment by an IP
connection.
TMN OS mode allows to insert CIPHOP equipment inside a higher level of network management
using a SMNP interface.
For more information about the TMN IP network characteristics required to remotely operate the
equipment please refer to TED par. 2.6.
4.2
Configuring the equipment connected to RCT or OS
The following configuration actions are required to enable each equipment to be connected to a
RCT or OS:
1. Connect a PC as LCT to the PSE or IDUnE1 RJ45 port (lct) devoted to Local Craft
Terminal supervisory
2. Access locally the equipment (see par 2.4)
3. Open the System Settings window (par. 2.11) from the Web Manager Main Menu (par. 2.7.2)
4. In the IP Address field of the Management Interface area, enter a unique/different IP
address previously established according to the IP Private Network addressing plan
5. In the Subnet Mask and Default Gateway fields, enter the number of the same subnet and
gateway address identifying the IP Private Network to be set up.
The same setting must be configured for these parameters on all equipments connected to
the IP network which constitute the group of equipment to be remotely managed.
6. Press the <Apply> button of the area to activate the selected configuration
7. Disconnect the PC from the lct port
Note: inside the above mentioned IP address, subnet and gateway fields some default values are
preloaded in the factory with standard values. These values must be modified according to the
network addressing plan to assign to each equipment an unique IP address within the same
management subnet. LCT and RCT/OS addresses are the same.
The above configuration must be executed on all the equipment to be connected remotely.
Page 68 of 88
Working with the RCT
In case of remote supervision by a RCT, connect a PC to the IP Network which has been set up.
Then open the browser (e.g. Internet Explorer) and write in the Address field of the browser the IP
Address previously assigned to the equipment to be supervised.
The main window Web Manager will be displayed as in the LCT mode (see Fig. 2.7-1) and the
operator will be able to perform all the operations described for the LCT in Chap. 2.
Other equipments can be simultaneously supervised opening new Internet Explorer browser
connections and entering the relevant IP Addresses of the different equipments to be supervised.
Note 1) On an equipment only one CT can be logged in at the same time.
Note 2) Care must be used when an equipment can be reached by RCT via the IP network only
by using the same radio link the equipment terminates. All commands which put the radio
link out of service must be avoided because they make the equipment unreachable and
therefore service can be restore only by a local manual intervention.
4.4
Working with the OS
Through the IP private network, configured as described above, a group of equipment can be
supervised by an OS.
The protocol between equipment and OS is a standard SNMP version v2c.
The MML interface supported by the OS is described in the relevant OS Operator Manual.
Note: The supervision from OS can work simultaneously with operation from CT and there is no
exclusion rule between the two operators. A careful coordination is therefore required between the
two operators if connected simultaneously.
4.5
Recovery from abnormal conditions
Due to some abnormal events it may happen that an equipment cannot any longer be reached by
CT or OS using the IP address defined by the operator ( e.g. this may happen if the IP address of
the equipment is forgotten by the operator).
To recover from such cases the operator is requested to:
Restart the equipment three times waiting a time between 1 to 10 minutes between each
restart (switching Off/On the power).
After the third restart the default IP Address 192.168.0.50 is enabled in addition to the IP
Address stored in the equipment MIB.
Within a period of 10 minutes the operator can access the equipment by CT using such
default IP Address and regain control of the equipment. After such time the default Address
is in any case disabled and cannot any longer be used.
The operator is requested to redefine immediately by the TMN Settings window the normal
IP Address and reconnect itself using such normal Address. When the new IP Address is
defined the default Address is immediately disabled.
It has to be noted that using the default Address the SW Download is not allowed (except
the case where the operator set once again the IP address equal to the default address).
Page 69 of 88
4.3
5.
Fault Management
5.1
General Fault Management Functions
Fault Management performs the detection, localisation, isolation and reporting of failures of the
transmission signals processed by the equipment. The failures may occur due to:
Transmission Failures
Equipment Failures.
Failures are reported via the management interface to the CT/OS and generate alarm indications
at the CT/OS.
In addition the system supports :
Visual indication by means of LEDs on the front panel of the PSE or IDUnE1
External alarm contacts, which can be used for summary signalling to supervisory systems.
Note: These additional facilities are not available in the PoE configuration.
IDU Card Alarms Indication
The following LEDs are provided at the front plate unit:
Name
Power LED
InService LED
Color
green
green
rdi
RDI LED
yellow
WARN LED
yellow
Label
on
odu w
Indicates
On/Off Equipment powered/not powered
On/Off Transmitter active/turned off.
On/Off Presence/Absence of a Remote End
Failure condition.
On/Off Presence/Absence of non-urgent alarms
or warning of abnormal system operation
On/Off Presence/Absence of urgent alarms
ALL LED
red
.
In case the link between ODU and PSE or IDUnE1 does not work properly, all LEDs (except the
Power LED) blink.
This condition may occur for at least three reasons:
IDU-ODU cable disconnected
No communication between IDU and ODU
IDU/PSE MAC ADDRESS not properly inserted in System SettingsIDU Management
window
Alarm Contacts and Housekeeping Contacts
The system provides some dry contacts which can be used to:
Flag failures detected inside the system (summary alarms) by 3 output contacts (Actors)
Send configuration commands to outside equipment by 2 output contacts (Actors). These
commands are controlled by CT (Inventory and Housekeeping window par. 2.12)
receive failure conditions detected outside the unit (external alarms) by 2 input contacts
(Sensors). This external alarms are displayed by the CT (Inventory and Housekeeping
window par. 2.12)
Page 70 of 88
Activation Criteria
In case of:
- Urgent Alarms
- Battery Fail
In case of Non-Urgent Alarms or
warnings
When transmitter ON
ALL
WARN
ODU_W
Table 5-32: Internal Alarm Contacts

Housekeeping
Contact
SENSOR_1
SENSOR_2
ACTOR_1
ACTOR_2
Activation Criteria
By external input for
customer purposes
By operators command
for customer purposes
Table 5-33: Housekeeping Contacts

The Housekeeping Sensors are managed as alarms and they can be included in the Summary
Alarms ALL and WARN and the corresponding LEDs as well as their transitions are reported in the
Alarm Log.
Housekeeping Alarm
SENSOR_1
SENSOR_2
LED / Summary
Alarm Contact
LED/ Summary
Alarm Contact
ALL
WARN
Table 5-34: Housekeeping Alarms
5.2
Equipment and Transmission Alarm List
The following Tables 5.32, 5.33 and 5.34 report the alarms detected by the system.
The Tables show:
- the name/label of the alarm as reported in the CT or OS
- LED indication which is raised by the alarm
- Raise/Clear integration time before the alarm is raised or cleared
- How the alarm is detected (by HW, SW, etc.)
- a short description of the root causes of the alarm
- Other alarms inhibiting the alarm (Alarm correlation)
Page 71 of 88
Summary Alarm Contact
Alarm Name
LED
Raise
Clear
time
From
Description
Inhibited
from
Note
Ethernet Interface Alarms
These alarms are related to the Ethernet ports. Therefore:

in case of PoE configuration they monitor the POE port on the ODU (User Interface to the equipment)
in case of PSE or IDUnE1 configurations there are alarms related to
POE port of the ODU (internal alarms controlling the IDU/ODU cable)
USER and LCT ports on the PSE or IDUnE1 (controlling User Interface to the equipment)
LinkDown
RemoteFault
Autonegotiation
Failure
ALL
1/1s
WARN
1/1s
ALL
1/1s
SW
SW
SW
The local ETH I/F has not established a

valid connection with the User
(Network) ETH I/F because of link
down
The local ETH I/F has received (by
Auto-Negotiation process) from the
User (Network) ETH I/F this indication
of fault condition.
The local ETH I/F has not established a
valid connection with the User
(Network) ETH I/F because of
autonegotiation not completed
Equipment and other Alarms

AllRem
RDI
1/1s
SW
WarnRem
RDI
1/1s
SW
RemChan
WARN
IduNotOper
LEDs
blink
TempAlm
WARN
MateLinkFail
BATT
WARN
No
SW
3/3s
1/1s
An ALL alarm on the far-end ODU is

reported on the local ODU by the radio
channel.
A WARN alarm on the far-end ODU is
reported on the local ODU by the radio
channel.
Communication channel ODU-ODU out
of service (No Status information
received from/to the Far End)
RxPwAlm
Failures on secondary
voltages that affect the
ODU/PSE controllers
may lead to this alarm
SW
PSE-ODU Communication channel

does not work and IDI is isolated
HW
ODU Temperature out of range.
SW
The link connecting the two PSE in the

Protection Group is not working:
Information exchange between Main
and Protection ODUs is blocked
Only applicable to 1+1

HSB systems
HW
Battery Failure (-48V), detected on the

PSE or IDUnE1
Alarm Contact (ALL)

only.
No LED and CT/OS
indication.
Table 5-35: Alarm List (Ethernet Interface, Equipment and others)
Page 72 of 88
LED
Raise
Clear
time
From
Description
Inhibited
from
Note
Radio Interface
olAlm
ALL
1/1s
HW
DemAlm
ALL
10/10s
FPGA
TxPwAlm
ALL
1/1s
SW
RxPwAlm
ALL
1/1s
SW
RxFrame
WARN
1/1s
HW
ALL
1/1s
SW
ATPC Loop
RxPwRem
WARN
HighBER
ALL
LowBER
WARN
TxContinuousWa
ve
WARN
Synthesizer alarm (VCO): reports

problems on the VCO of OL
Demodulator alarm: reports a wrong
state due to a bad working on the
demodulator (criterion SDR > ..)
Transmitted Power is different more
than 6 dB versus the operator defined
value or above a threshold when Tx is
squelched
Loss of GFP Frames in case of

misalignment on received radio signal
after demodulation.
Communication channel ODU-ODU out
of service (No information about Rx
Power from/to the Far End)
SW
HW
SW
HW
SW
BitErrorRate 10-3 (based on MSE

evaluation)
BitErrorRate 10-6 (based on MSE
evaluation)
Transmission of an unmodulated carrier
set by the operator
PM records UAS
CS
RxPw
(kHz)
(dBm)
3.5
-95
7
-93
14
-90
28
-87
PM records UAS
Received Power is below threshold

(function of the CS see the Note)
Received power at the Far end terminal

below threshold.
Oper.
RxPwAlm
RxPwAlm
HighBER
RxPwAlm
ATPC
Loop
Only if the radio

channel works
correctly.
RxPwAlm
RxPwAlm
HighBER
This mode can be set
by the operator for link
testing purposes.
The link is not
operational.
Table 5-36: Alarm List (Radio Interface)
Page 73 of 88
Alarm Name
Alarm Name
LED
Raise
Clear
time
From
Inhibited
from
Description
Note
TDM Alarms (only applicable to IDUnE1 configurations)

e1Los
ALL
1/1 s
WARN
1/1 s
e1Lof
WARN
1/1 s
EthLos
WARN
1/1 s
e1Ais
EthLos_xxx
WARN
1/1 s
A LOS condition is detected at the Input

of the E1 Port
An AIS condition is detected at the
Input of the E1 Port
A Loss of Frame is detected at the input
of the E1 port. Applicable only to E1
ports Framed.
Applicable to E1 ports unframed.
The E1 is not receiving packets from the
other terminal via the radio and L2
network or in any case the network does
not operate correctly.
Applicable to E1 ports framed for which
NxE0 bundles are defined.
xxx is equal to the bundle indicator
(srcBundle).
The bundle (NxE0) is not receiving
packets from the other terminal via the
radio and the L2 network or in any case
the network does not operate correctly.
LOS is signaled to the

remote end of the
connection(s) and
generates AIS outside
AIS is propagated
through the network to
the remote end
E0 service is impacted
with this alarm raised
AIS generated at the

E1 output port
AIS generated at the

E1 output port on the
timeslots included in
the bundle
Table 5-37: Alarm List (TDM Alarms)
5.3
Replacing Faulty Parts
When replacing parts you must comply with the safety regulation as described in Chapter 6.
After having replaced a faulty unit with a spare one, it is necessary to check that the previous alarm
indications disappear and service is restored.
In CIPHOP depending on configuration the following parts can be replaced to remove a fault,
depending on the localization of the fault:
- ODU
- PSE
- IDUnE1
5.3.1
Replacing the ODU
When required the ODU can be replaced following the steps here indicated (in the procedure IDU
means PSE or IDUnE1 depending on configuration):
1)
Take from the stock a spare unit with the same P/N of the unit to replace
2)
If the ODU is part of a Protection Group (1+1 HSB system) put the system in a Forced
status:
a) To replace the ODU Main, set in its CT System SettingsProtection window (par.
2.11) the field Forced Mode to Lockout (this operation could not be possible if the
ODU is faulty). Verify that the ODU Protection status in the System Status window is
Active.
b) To replace the ODU Protection, set on the ODU Main (System SettingsProtection
window (par. 2.11)) the field Forced Mode to Forced and verify that the ODU Main
status in the System Status window is Active.
Page 74 of 88
Switch off the IDU (power switch on the front) or PoE
4)
Disconnect the IDU/ODU cable from the RJ45 waterproof connector on the ODU
5)
Depending from the type of installation (for more details reference can be made to
Installation Manual)
i.
Remove the RF connection towards the external antenna and remove the
ODU from its support
ii.
Or disassemble the ODU from the integrated antenna
6)
Assemble the new ODU to the relevant support according to the type of installation (see
Installation Manual for more details) and reconnect the RF connection in case of external
antenna
7)
Reconnect the IDU/ODU cable to the ODU (RJ45 Connector)
8)
Switch ON (position I) the power switch on the IDU (or PoE) to power the system.
9)
Wait a while for the system automatic restart
10) Open a CT session (LCT can be connected to the LCT port of the IDU for PSE or
IDUnE1 configurations) par. 2.4
11) The Main Window opens and set time and date (see par. 2.5).
12) Once the main window is open reconfigure the system parameters reloading the
configuration data of the station. To avoid reloading manually all configuration data of the
station it is recommended to save off-line the configuration file and keep it available on
the PC acting as CT (Backup - par. 2.16.1) and reload it using the Restore procedure
(par. 2.16.2) available in the Main Menu.
Note: Until the station is fully configured the Tx status should remain down to avoid
interfering with other systems.
13) If for any reason the back-up configuration file is not available, it is necessary to reload
manually the station configuration and specifically it is required to:
a.
b.
c.
d.
e.
Enter all configuration parameters by using the System Settings window ( par.
2.11). In case of 1+1 HSB systems the same protection role (Main or Protection)
of the replaced ODU has to be set, with the ForcedMode to Lockout if Main.
Configure the Radio Interface by using the Radio Interface window (par. 2.8)
Configure the Ethernet Interfaces by using the Ethernet Interface window (par. 2.9)
Configure (when required) the TDM interfaces and connections using the TDM
window (par. 2.10)
Verify Equipment and Inventory data (par. 2.12) and the SW version loaded on
the ODU (par. 2.18.1). If the SW preloaded on the new ODU is not consistent
with the release actually used in the network a SW download should be
performed to load the correct SW load and make it active. Procedure for SW
upgrade are described in par. 2.18.
13) Once the system is properly configured activate the transmitter (Tx status up or ATPC as
required par. 2.8)
14) Check through LEDs visual inspection and basic CT procedures that the system works
properly
15) Configure Housekeeping and Activate Statistics, Logs and Performance Monitoring as
required
16) If the ODU is part of a Protection Group (1+1 HSB systems) after the ODU is restored to
service the Forced Mode has to be removed acting on the ODU Main and the original
setting of the protection group restored.
Page 75 of 88
3)
Note 1: No action for antenna pointing readjustment is required.

Note 2: The procedure can be simplified if the optional Configuration Module is equipped on the
ODU. In this case after step 4) the operator has to extract the Configuration Module from
the replaced ODU (see Fig. 5.3-1 to locate the Configuration Module on the ODU) and
insert it in the new ODU to be installed. A dedicated tool is available to help extracting
and reinserting the Configuration Module.
After the automatic restart (step 9) the system will recover automatically the station data
from the Configuration Module, step 10, 11 and 12 can be skipped and the system will
restart service immediately. If the CT is available it is in any case recommended to
performs the checks of step 13.
Configuration
Module
Removable Flash
Memory Card
Figure 5.3-1: Configuration Module position
Page 76 of 88
Replacing the IDU (PSE or IDUnE1 configurations)
In case the replacement of the IDU is required the following procedure has to be followed.
1)
Take from the stock a spare unit with the same P/N of the unit to replace
2)
In case the IDU (PSE) is part of a Protection Group (1+1 HSB system) the following actions
are required.
First put the system in a Forced status:
i. To replace the IDU of the Main, set in ODU Main System SettingsProtection
window (par. 2.11) the field Forced Mode to Lockout (this operation could not be
possible if the IDU is faulty). Verify that the ODU Protection status in the System
Status window is Active.
ii. To replace the IDU of the Protection, set on the ODU Main (System
SettingsProtection window (par. 2.11)) the field Forced Mode to Forced and verify
that the ODU Main status in the System Status window is Active.
If the User traffic is only connected to the USER port of the IDU to be replaced, a manual
reconfiguration has to done, moving the User cable to the USER port of the other PSE in
order to guarantee service continuity and configuring properly the USER interface of this
PSE.
If the User traffic is connected to both USER ports of the two PSE, USER ETH interface
configuration of the PSE remaining in service has to be modified in order to guarantee that
User traffic is only routed through this interface.
3)
Wear the antistatic armlet and connect its termination to a grounded structure
4)
Turn off (position O) the power switch on the front of the IDU unit to replace.
5)
Disconnect all the cables from the front panel, taking care of putting marking labels (if not
yet present) to facilitate a correct connection afterwards. In case of 1+1 HSB systems also
the Interconnection cable between the two PSE has to be disconnected.
6)
Extract the IDU box from the shelf unscrewing the two screws
7)
Insert the new IDU unit in the support frame
8)
Reconnect all the cables on the IDU front in the original position
9)
Turn ON (position I) the power switch on the front of the replaced IDU unit
10) Wait a while to allow re-initialization of the unit. During this phase the LED on the front
Panel are blinking.
11) Connect a PC as a LCT to the LCT port on the IDU front panel. A IDU not operational is
raised because the IDU MAC Address is not correct.
12) Using the System SettingsIDU Management window (par. 2.12) execute an automatic
upload of the IDU MAC Address.
If the procedure is successful the MAC Address will be displayed in the IDU MAC Address
field. The MAC address can be checked reading the label on the IDU (see TED par. 6.4.2).
After the new MAC Address is acquired, the "IDU not operational" alarm disappears and
the IDU LEDs will stop blinking.
The alternative procedure of next point 12) can be used if the automatic upload does not work.
13) Alternative procedure to manually enter the IDU MAC Address. The IDU MAC Address can
be manually entered in the same System SettingsIdu Management window reading it
from the IDU label.
Page 77 of 88
5.3.2
14) Check through LEDs visual inspection and basic CT procedures that the system works
properly
15) Take off the antistatic protection armlet
16)
If the IDU (PSE) is part of a Protection Group (1+1 HSB system) the Forced status of the
Protection Group has to be cancelled, acting on the ODU Main and restoring the original
configuration.
Important Note: in case a IDUnE1 is replaced, for all the E1 connections terminated in this IDU
the connections must be remade using the new MAC address of the IDU. This requires to
operate both on the system where the IDUnE1 has been replaced and on all other systems
where these connections are terminated at the other end.
Page 78 of 88
6.1
Safety Rules and Precautions

First Aid for Electric Shocks
Do not touch the patient with bare hands until the circuit has been opened. Open the circuit by
switching the line switches off. If that is not possible, protect yourself with dry material and free the
patient from the conductor.
6.2
Artificial Respiration
It is important to start mouth to mouth resuscitation at once and seek doctor help immediately. The
mouth to mouth method to apply is described here below.
Mouth to mouth resuscitation method
1. Lay the patient supine with his arms parallel with the body. If the patient is laying on a inclined
plane, make sure that his stomach is slightly lower than his chest.
Open the patients mouth and check that there are no extraneous bodies in his mouth
(dentures, chewing-gum, etc.).
2. Kneel beside the patient level with his head. Put a hand under the patients head and one
under his neck (Fig. 6.2-1)
Lift the patients head and let it recline backwards as far as possible.
Figure 6.2-1: Artificial respiration procedure (1/4)
3. Shift the hand from the patients neck to his chin: place your thumb between his chin and his
mouth, the index along his jawbone, and keep the other fingers closed together (Fig. 6.2-2).
While performing these operations take a good supply of oxygen by taking deep breaths with
your mouth open.
4. With your thumb between patients chin and mouth keep his lips together and blow into his
nasal cavities (Fig. 6.2-3).
5. While performing these operations, observe if the patients chest rises (Fig. 6.2-4). If not, it is
possible that his nose is blocked: in that case, open the patients mouth as much as possible
by pressing on his chin with your hand, place your lips around his mouth and blow into his oral
cavity.
Page 79 of 88
6.
Observe if patients chest heaves. This second method can be used instead of the first even
when the patients nose is not obstructed, provided his nose is kept closed by pressing the
nostrils together by using the hand you were holding his head with.
The patients head must be kept sloping backwards as much as possible.
6. Start with ten rapid expirations, hence continue at a rate of twelve/fifteen expirations per
minute. Go on like this until the patient has regained consciousness, or until a doctor has
ascertained his death.
6.3
Treatment of Burns
This treatment should be used after the patient has regained consciousness. It can also be
employed while the artificial respiration is being applied (in this case, there should be at least two
persons present).
Important:
Do not attempt to remove his clothing from the burnt parts.
Apply dry gauze on the burns.
Do not apply ointments or other oily substances.
6.4
6.4.1
Safety Rules
General Rules
Before carrying out any installation, turnon, tests & operation and maintenance operations
carefully read the related Handbooks.
When equipment is operating nobody is allowed to have access inside on the equipment parts
which are protected with Cover Plate Shields removable with tools.
In case of absolute need to have access inside, on the equipment parts when it is operating this is
allowed exclusively to properly trained personnel.
For the eventual cleaning of the external parts of the equipment, absolutely do not use any
inflammable substance or substances which in some way may alter the markings, inscriptions etc.
It is recommended to use a slightly wet cleaning cloth.
Whenever the safety protection features have been impaired, REMOVE POWER.
To cut off power proceed to switch off the power supply units as well as cut off power station
upstream (rack or station distribution frame).
Page 80 of 88
Warnings for the electrical safety
All product parts are to be designed in compliance with EN 60950-1:2001-12 information

technology equipment- Safety. The equipment must be installed, started up, managed and
repaired only by properly trained personnel.
The following plate defines the points on the inner units of the system that can have
voltages exceeding the SELV and/or TNV levels described into EN60950 (>120 Vdc).
Please take care that:
Before supplying the equipment, it is necessary to complete the wiring of the connections to
the protection ground, the insertion of all the units and/or modules provided for the requested
configuration and also the connection of all the necessary connectors.
The connection to the protection ground must not be removed or damaged.
The equipment supplying system must be provided with a sectioning device upstream the
connector.
Before disconnecting the connectors, check that the supply has been removed by means of
the sectioning device installed upstream.
6.4.3
Microwave radiations
Microwave radiations can endanger your health. Ensure the transmitters are switched OFF
before working close to and in front of the antennas.
No dangerous level of microwave radiations exists outside the antenna feeder. Nevertheless, body
should not be exposed to the radiation in front of the antenna ( < 0.5 m ) for a long time ( > 6
minutes ).
6.4.4
Dangerous materials
For the elimination at the end of life, this equipment is inside the 160214 class (other electronic
material out of order) of the EUROPEAN CATALOGUE OF WASTES defined with
CEE/CEEA/CECA decision NR. 2001/118/CE of 16-01-2001.
Inside this product, some materials can be present that must not be exposed to flames or to high
temperatures. Such conditions can cause toxic fumes that must not absolutely be inhaled.
Some metallic elements, necessary for the EMC shielding, content beryllium. Then it is necessary
to pay high attention during the use of such elements to avoid their breakage or abrasion.
6.5
ESDS Precautions
The ESDS (Electro Static Discharge Sensitive) electronic devices can be partially or permanently
damaged by the static electricity that is commonly present in the operating environment.
The main ESDS devices are:
CMOS components.
Page 81 of 88
6.4.2
Large Scale Integration components in MOS technology.

SAW (Surface Acoustic Wave) components.
Operational amplifiers with MOS/FET inputs.
MOS/FET components and arrays.
Microwave semiconductors and microcircuits at frequencies > 1 GHz.
Modules containing ESDS devices are identified by following adhesive labels:
In order avoid any damage while handling the modules, the user should wear an antistatic elastic
bracelet, grounded by means a spiral cord. Those modules that are mounted on the equipment
(faulty or spare parts) shall be stores in their original antistatic package marked by the labels above
shown.
Page 82 of 88
7.1
Annex - Front Panel and Connectors

PSE Front Panel
RJ45 8 pins
Sub-D male 9 pins
3W3 male
Note: the port labelled ETH is referred to as USER in the LCT windows.
Figure 7.1-1: PSE Front Panel and Connectors
7.2
IDUnE1 Front Panel

RJ45 8 pins
3W3 male
Sub-D female 9 pins
Sub-D male 9 pins
SCSI HD68
Figure 7.2-1: IDUnE1 Front Panel and Connectors
7.3
AC/DC Front Panel
3W3 female
Figure 7.3-1: AC/DC Front Panel and Connectors
Page 83 of 88
7.
7.4
General Connectors
PIN
1
2
3
4
5
6
7
8
Signal
ETH OUT_A
ETH OUT_B
ETH IN_A
+ VDC
+ VDC
ETH IN_B
- VDC
- VDC
Table 7-38: ODU External Interface (RJ45 waterproof connector)

PIN
1
2
3
4
5
6
7
8
ODU
ETH OUT_A
ETH OUT_B
ETH IN_A
+ VDC
+ VDC
ETH IN_B
- VDC
- VDC
Table 7-39: Interface to ODU (PoE connector RJ45)
Figure 7.4-1: Scheme of RJ45 Wire Pair Colour
Page 84 of 88
ODU
ETH OUT_A
ETH OUT_B
ETH IN_A
ETH IN_B
Table 7-40: Interface to the Network (User) (eth connector RJ45)
PIN
1
2
3
4
5
6
7
8
9
Alarms and Housekeeping

SENSOR 2
Input
WAR
Output
Ref. GND (ALARMS)
Output
ACTOR 2
Output
SENSOR 1
Input
ALL
Output
ODU_W
Output
ACTOR 1
Output
Ref. GND (Sensors/Actors)
Input
Table 7-41: Alarm and Housekeeping Interface (9-pins Sub-D male connector)
PIN
1
2
3
4
5
6
7
8
LCT
OUT_A
OUT_B
IN_A
IN_B
-
Table 7-42: LCT Interface (lct connector RJ45)
A1
A 2
A3
A1 Positive
A2 Mechanical Ground
GND_M
A3 Negative
3W3 D-Sub male input power connector

pins A3 (NBAT -) and A1 (PBAT +) are connected to the battery pin A2 is used as ground connection
Figure 7.4-2: Power Connector (-48 V Battery)
Page 85 of 88
PIN
1
2
3
4
5
6
7
8
7.5
E1 Connectors (only on IDUnE1)

PIN 34
PIN 1
PIN 68
PIN 35
Figure 7.5-1: E1 Connector (SCSI HD68 120 balanced)
PIN
E1
PIN
E1
PIN
E1
PIN
E1
36
CH8_TX-_0
35
CH8_RX-_0
CH8_TX+_0
CH8_RX+_0
38
CH7_TX-_0
37
CH7_RX-_0
CH7_TX+_0
CH7_RX+_0
40
CH6_TX-_0
39
CH6_RX-_0
CH6_TX+_0
CH6_RX+_0
42
CH5_TX-_0
41
CH5_RX-_0
CH5_TX+_0
CH5_RX+_0
44
CH4_TX-_0
43
CH4_RX-_0
10
CH4_TX+_0
CH4_RX+_0
46
CH3_TX-_0
45
CH3_RX-_0
12
CH3_TX+_0
11
CH3_RX+_0
48
CH2_TX-_0
47
CH2_RX-_0
14
CH2_TX+_0
13
CH2_RX+_0
50
CH1_TX-_0
49
CH1_RX-_0
16
CH1_TX+_0
15
CH1_RX+_0
52
GND
51
GND
18
GND
17
GND
54
CH8_TX-_1
53
CH8_RX-_1
20
CH8_TX+_1
19
CH8_RX+_1
56
CH7_TX-_1
55
CH7_RX-_1
22
CH7_TX+_1
21
CH7_RX+_1
58
CH6_TX-_1
57
CH6_RX-_1
24
CH6_TX+_1
23
CH6_RX+_1
60
CH5_TX-_1
59
CH5_RX-_1
26
CH5_TX+_1
25
CH5_RX+_1
62
CH4_TX-_1
61
CH4_RX-_1
28
CH4_TX+_1
27
CH4_RX+_1
64
CH3_TX-_1
63
CH3_RX-_1
30
CH3_TX+_1
29
CH3_RX+_1
66
CH2_TX-_1
65
CH2_RX-_1
32
CH2_TX+_1
31
CH2_RX+_1
68
CH1_TX-_1
67
CH1_RX-_1
34
CH1_TX+_1
33
CH1_RX+_1
Table 7-43: E1 Interface (SCSI HD68 120 balanced)
Page 86 of 88
A
AGC
ALL
AM
APS
ATPC
B
BATT
BCH
BER
C
CK
CoS
CPM
CRC
CS
CSV
CT
CW
D
Dec
DSCP
E
EMC
ES
ESDS
ETH
ETSI
F
FE
FER
FTP
G
GbE,
GE
GND
GUI
H
Hex
HTML
HTTP
HW
I
IDU
IDUnE1
IEEE
IF
I/F
IN
IP
ITMN
ITU
L
LAN
LCT
LED
LOG
LO
LSS
List of abbreviations
Automatic Gain Control
Urgent Alarm
Adaptive Modulation
Application Software
Automatic Transmit Power Control
BATT
Bose,Chaudhuri,Hocquenghem Code
BER
Clock
Class of Service
Continuous Phase Modulation
Cyclic Redundancy Check
Channel Spacing
Comma Separated Values (format)
Craft Terminal
Continuous Wave
Decimal Numbers
Differentiated Services Code Point
Electromagnetic Compatibility
Errored Seconds
Electro Static Discharges Sensitive
Ethernet
European Telecom. Standard Institute
Fast Ethernet (10T or 100T)
Frame Error Rate
File Transfer Protocol
Gigabit Ethernet
Gigabit Ethernet
Ground
Graphical User Interface
Hexadecimal Number
Hyper Text Mark-up Language
Hyper Text Transfer Protocol
Hardware
In-Door Unit
IDU with n x E1 Interfaces (PDH&Data)
Instit. Electrical & Electronic Engineer.
Intermediate Frequency
Interface
Input
Internet Protocol
Installation and Test Manual
International Telecomm. Union
Local Area Network
Local Craft Terminal
Light Emission Diode
Event and Command Logger
Local Oscillator
Low Signal Seconds
M
C
MAC
MEF
MI
MIB
MII
MSE
N
NFD
NTP
NSS
O
OAM
ODU
OMN
OS
OUT
P
PC
PCP
PHY
Pkts
PoE
PRx
PSE
PSE/L
PSE/W
PTx
PW
R
RCT
RDI
RF
RoHS
RSSI
RTPC
RX
S
SES
SFP
SNMP
SW
T
TED
TMN
TX
U
UAS
UNI
V
VCO
Vac
Vdc
VLAN
W
WARN
WRR
Micro Controller
Media Access Control
Metro Ethernet Forum
Modulation Index
Management Information Base
Media Independent Interface (Ethernet)
Demodulator Mean Square Error Index
Net Filter Discrimination
Network Time Protocol
No Signal Seconds
Operation Administration Maintenance
Out-Door Unit
Operator Manual
Operation System (Network Manager)
Output
Personal Computer
Priority Code Point
Physical Ethernet Interface Function
Packets in an Ethernet connection
Power Over Ethernet
Receive Power
Power Supply Equipment
PSE Basic features
PSE Full Feature
Transmit Power
Pseudo Wire
Remote Craft Terminal
Far End Remote Failure
Radio Frequency
Restriction Of Hazardous Substances
Receive Signal Strength Indicator
Remote Transmit Power Control
Receiver/Received
Severely Errored Seconds
Small Form-factor Pluggable Module
Simple Network Management Protocol
Software
Technical Description Manual
Telecommunic. Management Network
Transmitter/Transmitted
Un Available Seconds
User Network Interface
Voltage Controlled Oscillator
Voltage (alternate current)
Voltage (direct current)
Virtual LAN
Warning or Non-Urgent Alarm
Weighted Round Robin (priority)
Page 87 of 88
8.
END OF DOCUMENT
page 88 of 88

Linkra

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Linkra

Enviado por

Direitos autorais:

Formatos disponíveis

CIPHOP IP

Medium Capacity Ethernet Over Radio System

a COMPEL GROUP COMPANY

Technical modifications are possible.

Functions and Handling of the Craft Terminal (CT) ...........................................................13

Perform Configuration by CT ................................................................................................55

Fault Management ...................................................................................................................70

General Fault Management Functions....................................................................................... 70

Replacing the ODU.................................................................................................................... 74

Safety Rules and Precautions..................................................................................................79

Annex - Front Panel and Connectors.....................................................................................83

PSE Front Panel ........................................................................................................................... 83

List of abbreviations ................................................................................................................87

Table 1-1: CIPHOP IP .........................................................................................................................7

Table 1-1: CIPHOP IP

Purpose of the document

The handbook is structured in the basic parts :

1.5.1. Use of Unlicensed Bands

1.5.2. Use of Equipments in EU countries

1.5.3. Declarations and Marking

CIPHOP 917 IP is marked as follow:

Functions and handling of the Craft Terminal (CT)

Safety Rules and Precautions

Annex Front Panel and Connectors

Legenda : n=new part

blank= unchanged part

Functions and Handling of the Craft

The equipment can be used in four configurations using:

Figure 2.1-1: Reference Configuration for IDUnE1 and PSE

Hardware and Software Configuration

Getting the Connection

Figure 2.4-1: Login Window

b Alert: connection is lost

Figure 2.4-2: Login Window - Alerts

a Alert: another user is already logged

Setting Date and Time

Summary System Status

Figure 2.6-1: CT screen functional areas

In Fig. 2.6-1 the main areas of the screen are defined.

Each window is made of one or several functional areas

2) Logo Area. The Logo of the equipment is displayed.

Figure 2.7-1: Main Window (configuration with PSE or PoE)

Summary System Status

Tx/Rx Radio parameters:

2.7.2 Main Menu

2.7.3 System Status

TDM (available only in IDUnE1 configuration)

Define if the link is unprotected or protected

Only displayed in 1+1 HSB configurations:

IP Address assigned to the Remote Terminal.

- Basic (CS=3.5, 7 MHz)

Hex No. (xx.xx.xx.xx.xx.xx)

Hex No. (xx.xx.xx.xx.xx.xx)

Note 1) These parameters can be optionally defined by the customer

Table 2-5: Parameters displayed in the System Status - Settings

100M FDX Asym FlowControl

100M HDX Asym FlowControl

Figure 2.8-1: Radio Interface Window

The window is subdivided in functional areas hereby described.

Table 2-7: Parameters displayed in the Radio Interface Radio Info

The user can set up the desired state of the

The user can set up the test mode

Enabling ULA the forwarding to the Tx of

- Enabled: ULA operates