Commissioning LCT

8/3/2019 Commissioning LCT

1/90

4 - COMMISSIONING VIA LCT

4-1SRAL XD (IDU Plug-in) - OMN911-380/02A0380 - Issue 4, January 2008

4 COMMISSIONING VIA LCTThis Chapter lists all the configuration and activation operations which must be executed

via LCT for the commissioning of the equipment.

The sequence of the operations is described in tabular format by means of a

step-by-step procedure; for each operation, the heading of the table (box in the top right

part of the title) indicates the paragraph of the operating guide, which it is necessary to

refer to, in order to get more details.

Before starting the commissioning procedure, execute the following preliminary

operation:

Connect the LCT terminal to the F interface or the Q/V Ethernet interface of the

equipment.

Verify that the memory hardware key is inserted, before starting-up the equipment.

The IDU Plug-in is provided with a memory hardware key, which stores the equipment

configuration to allow an easy and fast replacement of the Controller.

The hardware memory key has the following characteristics:

it is the backup key of the equipment configuration, each change of a configuration

parameter is stored in the non volatile memory of the Controller and, immediately,

also in the non volatile memory (EEPROM) of the hardware key

it is identified by:

serial number, which is univocal equipment type which it has been configured for

The following IP addresses are assigned by default in factory to the interfaces of

SRAL XD:

Q/V Ethernet interface:

IP address: 10.10.10.10

Net-Mask: 255.255.255.0

F interface:

IP address: 192.168.255.3

Net-Mask: 255.255.255.0.

Hardware Key F Interface

Ethernet Q/VInterface


2/90


4-2SRAL XD (IDU Plug-in) - OMN

911-380/02A0380 - Issue 4, January 2008

after the start-up, it is strictly associated to the equipment Controller (the controller

memorizes the hardware key serial number)

it contains the license; each hardware key delivered with the equipment contains

the license ordered by the Customer.Also the management of the System Type unknown is foreseen; it is a temporary

condition of the equipment that can occur in the following cases:

when the upgrading of the SVR is required, to manage a System Type not

supported by the current SVR

during the acquisition of the content of the hardware key, in order to solve the

possible mismatch commands.

Diagnostics for the hardware key

The following diagnostic signals are available via software for the hardware key:

Disconnected status signal

Condition of disconnected hardware key; the system detects the physical

availability of the hardware key through polling (devoted sense pin). If the condition

of disconnected hardware key is present at the equipment start up, the Controller

switches to the IDLE status; vice versa, if this condition occurs with the equipment

on, the Controller switches to the RUN/NO SET status.

Mismatch status signal

The hardware key is not congruent with the equipment type. This condition is

present when the user inserts, by mistake, the hardware key relevant to a different

equipment type. If at the start up of the equipment, the condition of not congruent

hardware key is present, the Controller switches to the IDLE status; vice versa, if

this condition occurs when the equipment is switched on, the Controller switches

to the RUN/NO SET status.

Key E2prom Fail Alarm

The EEPROM of the hardware key is out of order; in this situation, the hardware

key can not be accessed.If the Key E2prom Fail alarm is present at the equipment start up, the Controller

switches to the IDLE status and the equipment configuration stored in the

non-volatile memory of the Controller is loaded; vice versa, if the alarm occurs

when the equipment is switched on, the Controller switches to the RUN/NO SET

status.

Alignment Fail Alarm

The serial number of the hardware key is different from the one memorized into the

Controller at the start-up. When the Alignment Fail Alarm occurs, the Controller

switches to the RUN/NO SET status. This condition can be present only when the

equipment is turned on, the user extracts the hardware key present at the power-on

time and inserts an hardware key configured for the same type of equipment.

Starting from SVR 3.6, a new management modality of the memory hardware key

is foreseen.

In case of downgrading of a SVR 3.6 equipment to a previous SVR 3.6 or higher,it is necessary to execute the defrag of the hardware key, in order to allow a

possible successive upgrading to SVR higher without problems.


3/90



Controller status

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

RUN/SET

The internal (towards the slaves) and external interfaces are enabled; the systemcan execute the configuration operations (within the limits foreseen by the license

and by the user class). This is the normal operating condition.

RUN/NO SET

The internal (towards the slaves) and external interfaces are enabled but the user

can execute reading only operations. In this condition, the F interface is still

operative to allow the download of the equipment software. This situation is present

when the equipment is turned on and the user extracts the memory key or there is

an alarm condition on the hardware key.

IDLE

The internal interfaces (towards the slaves) are disabled while the external onesare enabled (the system does not display queries of the slaves). In this condition,

the F interface is still operative to allow the download of the equipment software.

This situation is present in the following cases:

the equipment is switched on without hardware key inserted

the equipment is switched on, but the inserted hardware key is faulted or not

congruent

the System Type present in the configuration of the hardware key is not

supported (condition of System Type unknown).

Start-up of the Controller

At start-up, the Controller executes a series of controls on the hardware key:

if the hardware key is not connected, the signalling of Disconnected hardware key

activates and the Controller switches to the IDLE status

if the hardware key is out-of-order, the alarm signalling of Key E2prom Fail

activates and the Controller switches to the IDLE status

if the configuration stored in the hardware key is not congruent with the equipment

type, the signalling of Mismatch hardware key and the Controller switches to the

IDLE status

if all the checks on the hardware key are OK (hardware key is connected,

congruent, properly operating and acknowledged as equipment hardware key,

System Type supported), the equipment configuration and the licenses contained

in the hardware key are loaded and the Controller stores the serial number of the

hardware key and switches to the RUN/SET status.

In the following flow diagram, the management of the hardware key during the

switching-on phase of the equipment or after a command of software reset of the

Controller is displayed.


4/90



911-380/02A0380 - Issue 4, January 2008

Run-time operation of the Controller

During the normal run-time operation:

the Controller is in the RUN/SET status if the hardware key is On Line and without

alarms

the Controller is in the RUN/NO SET status if an alarm condition of the hardware

key is present (Mismatch, Disconnected, Alignment Fail, Key E2prom Fail); in this

condition, the Controller is enabled only to maintain the configuration in its volatile

memory.

In the following flow diagram, the conditions which determine the passage of the

Controller from the RUN/SET status to the RUN/NO SET status are illustrated.

IDU Plug-in switching orSoftware Reset of Controller

IDLE status

Loading of configuration of thehardware key; the serial number

of hardware key is stored in

the non volatile memoryof the Controller

Hardware andSoftwareCheck

No

Yes No

(Mismatchalarm)

(Disconnectedalarm)

Yes

No

(System Type unknown)

Yes

Hardwarekey

connected?

Hardwarekey

congruent?

System Typesupported?


5/90



Extraction/replacement of the hardware key

The hardware key must be always connected to the IDU Plug-in during the normal

operation of the equipment.

The key extraction is allowed only for the corrective operations following.

In case of replacement/repairing of the faulted IDU, the procedure is the following:

remove the hardware key that contains the equipment configuration and the

current license, before executing the replacement/repairing of the IDU

insert again the hardware key, after the replacement/repair of the IDU, beforeswitching on again the equipment

at start-up, if all the checks are OK, the equipment configuration and the license

stored in the hardware keys, which are the same of those present before the

intervention of corrective maintenance, are loaded.

In case of fault of the hardware key provided with the equipment, the same can be

provided as spare parts.

For the codes of the licenses to require the spare hardware key, refer to the UMN

manual of the equipment.

The insertion of the spare hardware key, as replacement of the faulted hardware

key, causes the activation of the Key E2prom Fail alarm, which can be clearedonly by switching off and, then, switching on the IDU, with consequent loss of

traffic and loss of the configuration (the equipment restarts with the default

configuration that is loaded at the first start-up of the equipment)

Controller Run-Time (RUN/SET)

Hardware keynot congruent(Mismatch or

Alignment Fail)

Hardware keyout of order

(Key E2prom Fail)

Hardware keydisconnected

(Disconnected)

RUN/NO SET Status


6/90



911-380/02A0380 - Issue 4, January 2008

Step 1 Login to NE par. 5.3

Create, using NetBuilder, a map for the connection to the local NE: in case of connection via F interface, in the map, assign to NE the 192.168.255.3 IP address (F interface

default address)

in case of connection via Q/V interface, in the map, assign to NE the 10.10.10.10 IP address (Q/V interface

default address).

It is also possible to use the map for local connection provided together with LCT (LOCALNE.MAP), with192.168.255.3 IP address presetted.Start LCT and load the map for the connection to the local NE (by default: LOCALNE.MAP).Verify that the connection to the equipment has been successfully executed; this causes the loading of theequipment profile, and the consequent displaying of the SRAL XD icon.Open the NE (Open command), executing the login with the Admin user class, and check that the operatingmenu for the control and the configuration of the equipment is loaded.
http://-/?-http://-/?-


7/90



Step 2 Configuration of the System Type par. 5.5.1.1.2

Open the Status and ConfigEquipmentSystemSystem Type window.Select the wished System Type; the possible options are: (1+0): Single Terminal

2x(1+0): Double Terminal (option available only with 16xE1/16xT1 Access unit)

(1+1) H/S: Terminal with (1+1) Hot-Standby protection

(1+1) FD: Terminal with (1+1) protection at frequency diversity

Add/Drop - Rep: Repeater with possibility of tributary Add/Drop (option available only with

16xE1/16xT1Access unit)

Ring: Terminal/repeater with path protection (option available only with 32xE1 Access unit).

The System Type is a parameter subjected to license; the license options are: (1+0): only (1+0) System Type is available

All: all the System Type foreseen for the equipment are available.
http://-/?-http://-/?-


8/90



911-380/02A0380 - Issue 4, January 2008

Step 3 Access Unit Type Configuration par. 5.5.1.1.1

Open the Status and ConfigEquipmentSystem window.Select the type of equipped Access unit in the box; the possible options are: 16xE1: Access unit with 16xE1 tributary ports.

16xT1: Access unit with 16xT1 tributary ports.

1xE3: Access unit with 1xE3 interface and 1xE1 way-side tributary ports.

DATA: Access unit with external access interface with four LAN ports and 8xE1 tributary ports.

32xE1: Access unit with external access interface with 32xE1 tributary ports.

Note that the support of the T1 tributaries is available only with ODU of ND/ND2 type.

The 16xE1, 32xE1, 1xE3 and DATA-8xE1 tributary interfaces are foreseen for the use in

Countries that use the ETSI standard.

The 16xT1 tributary interfaces is foreseen for the use in Countries that use the ANSI standard.
http://-/?-http://-/?-


9/90



Step 4 Configuration of the Type of BB Unit par. 5.5.1.1.3

Open the Status and ConfigEquipmentSystem window.Select, in the box of the BB unit, the type of the equipped BB unit; the possible options are: 16xE1/T1: 16xE1/T1 BB unit

1xE3: 1xE3 BB unit

32xE1: 32xE1 BB unit.

In the configurations with two BB units, the operation must be executed on both the BB units.The BB 16xE1/T1 unit is associated to 16xE1 Access, 16xT1 Access, and DATA Access Unit.The BB 1xE3 is associated to 1xE3 Access unit.The BB 32xE1 is associated to 32xE1 Access unit.

In 2x(1+0) and A/D-RPT System Types, only the 16xE1/T1 BB unit is supported and then the

configuration of the type of the BB unit is not foreseen. The system automatically sets both

the BB units, displaying 16xE1 or 16xT1 according to the type of equipped Access unit.

In Ring System Type, only the 32xE1 BB unit is supported and then the configuration of thetype of the BB unit is not foreseen. The system automatically sets both the BB units.
http://-/?-http://-/?-


10/90



911-380/02A0380 - Issue 4, January 2008

Step 5 ODU Type Configuration par. 5.5.1.1.8

Open the Status and ConfigEquipmentSystem window.The following type of ODU are foreseen: ODU ND: ODU able to operate only in Normal Density

ODU ND2: ODU able to operate only in Normal Density

ODU HD/HP: ODU able to operate both in Normal Density and in High Density

ODU HDe: ODU able to operate both in Normal Density and in High Density with support of the radio

capacity 32xE1.

Select, in the ODU section, the corresponding equipped ODU type; the possible options are: ND: ODU of ND type or of ND2 type

HD/HDe: ODU of HD/HP type or of HDe type.

In the configurations with two ODUs, the operation must be executed on both the ODUs.Note that the T1 tributary support is available only with Normal Density/ND2 ODUs.
http://-/?-http://-/?-


11/90



Step 6 System Radio Capacity Configuration par. 5.5.1.1.6

Open the Status and ConfigEquipmentSystem window.Click on System Capacity to open the window for the configuration of the system radio capacity.Click on Modify to pass to the modify modality of the configuration fields.Set the system radio capacity and then confirm clicking on OK; the possible options are: with Access 16xE1 unit:

2xE1

4xE1

8xE1

16xE1

with Access 16xT1 unit:

2xT1

4xT1

8xT1

16xT1 with Access 1xE3 unit:

1xE3

with Access DATA unit:

2xE1

4xE1

8xE1

16xE1

with Access 32xE1 unit:

4xE1

8xE1

16xE1

32xE1

The system radio capacity is a parameter subjected to license; the license options are: 4xE1-T1

8xE1-T1

16xE1-T1 - 1xE3

32xE1

In the configurations with two unprotected systems, the operation must be executed for both the systems.The following table indicates the system capacities supported in the different System Types based onmodulation type, on Access unit type and on ODU type.
http://-/?-http://-/?-


12/90



911-380/02A0380 - Issue 4, January 2008


System

Type

RF

Density

ODU

Type

Traffic capacity

16xE1 Access unit 16xT1 Access unit1xE3

Access

unit

DATA Access unit 32xE1 Access unit

2xE14xE1 8xE1 16xE12xT14xT1 8xT1 16xT1 1xE3 2xE1 4xE18xE1 16xE1 4xE1 8xE1 16xE1 32xE1

(1+0)

ND ND/ND2

ND HD/HP

ND HDe

HD HD/HP

HD HDe

2x(1+0)

ND ND/ND2

ND HD/HP

ND HDe

HD HD/HP

HD HDe

(1+1)

H/S

ND ND/ND2

ND HD/HP

ND HDe

HD HD/HP

HD HDe

(1+1)

FD

ND ND/ND2

ND HD/HP

ND HDe

HD HD/HP

HD HDe

A/D-Rep

ND ND/ND2

ND HD/HP

ND HDe

HD HD/HP

HD HDe

Ring HD HDe


13/90





14/90



911-380/02A0380 - Issue 4, January 2008

Step 7 ODU Power Supply Command par. 5.5.1.1.5

Open the Status and ConfigEquipmentSystem window.Verify that the ODU Power UP command is in Enabled status; force it to Enabled if it was in Disabled status.In the configurations with two ODUs, the operation must be executed for both the ODUs.
http://-/?-http://-/?-


15/90



Step 8A Configuration of HD/HDe Type ODU par. 5.5.1.9

Open the Status and ConfigEquipment window.In the ODU section, click on Configure to open the window for the ODU configuration.Set all the ODU operating parameters.In the configurations with two ODUs, the operation must be executed for both the ODUs.

Note that the ATPC configuration parameters are not automatically aligned between the two

ODUs in case of (1+1) Hot-Standby configuration.

Starting from SVR 3.6, in case of (1+1) Hot-Standby configuration, the functionality of

automatic alignment of the configuration of the RF frequency parameters between the two

ODUs is implemented; in this case, it is sufficient to configure the RF frequency parameters

on only one of the two ODUs
http://-/?-http://-/?-


16/90



911-380/02A0380 - Issue 4, January 2008

RF Channel DensitySet the wished RF channel density (ND or HD)The channel RF density is a parameter subject to license.Note that the RF HD density can be applied only for the 8xE1, 16xE1 and 32xE1 system capacities.The CH Density field for the configuration of the density, independently from other conditions, is howeverinactive if the currently set RF TX power is greater than the maximum allowed value for the RF HD density(P-max (CH Density HD)); in this case, to activate the CH Density configuration field and to set the RF HDdensity, it is necessary: to modify the value of the RF TX power, currently set for the ND density, in such a way that it is equal to or

lower than the maximum value allowed for the HD density

to modify the ATPC management range (ATPC Range), currently set for the ND density, in such a way that

it is congruent with the maximum value of RF TX power allowed for the HD density; this operation must be

executed even if the ATPC management of the RF TX power is disabled.

Naturally, all the other conditions that enable the use of the HD density must be satisfied.


Both the terminals of a radio link must use the same modulation modality.


17/90



RF TX Power

Set the RF TX power according to the used adjusting modality (ATPC management or fixed RF TX power): Fixed RF TX power

Click on Tx Power Setting to open the window for the configuration of the RF TX power.

Disable the ATPC management (ATPC ManagementDisabled). Set the value of the RF TX power (RF

Tx Power), which must be between the allowed minimum and the maximum value. In case of (1+1)

Hot-Standby configuration, set the value of the coupling loss (Coupling Loss); the value to set depends on

the type of used frame (from 0 to 15 dB). For both the ODUs, the same value must be set.


On both the terminals of a radio link the same modality of management of the RF TX powermust be used (both the terminals with ATPC management or both the terminals with RF TX

power fixed).

For ODU HD/HDe, independently from the management modality which will be used, it is

necessary to configure both the value of rated fixed RF TX power (RF TX Power parameter)

and the minimum value of RF TX power of ATPC (P-min ATPC parameter) in order to avoid

conflicts and/or malfunctions.

The max. value of RF TX power depends on the channel density of the ODU (HD or ND).

For the 26 GHz range, the performance data are not ensured when the ODU works in HD

modality with radio capacity 8xE1 and the RF TX power is greater than 13 dBm.


18/90



911-380/02A0380 - Issue 4, January 2008

RF TX Power with ATPC management

Click on Tx Power Setting to open the window for the configuration of the RF TX power.First, disable the ATPC management (ATPC ManagementDisabled)Set the minimum value of the RF TX power for ATPC (P-min ATPC), which must be between the minimumand maximum allowed values.Set the ATPC management range for the RF TX power (ATPC Range).The following condition must always be true:

P-min ATPC + ATPC Range P-maxSet the threshold value of the received RF power (ATPC Threshold) which determines the intervention ofthe ATPC circuit on the RF transmitter of the remote terminal.Enable the ATPC management (ATPC Management Enabled).


In case of configuration of the RF TX power with ATPC management, the ATPC management

must be activated and configured both on the local terminal and on the remote terminal.

In order to avoid conflicts and/or malfunctions, it is necessary to correctly configure the

P-min ATPC parameter even if the ATPC management of RF TX power is not used.

For the 26 GHz range, the performance data are not ensured when the ODU works in HD

modality with radio capacity 8xE1 and the RF TX power is greater than 13 dBm.


19/90



Frequency modalitySelect the frequency modality (continuous frequency or frequency plan): Continuous frequency

Select the Continuous option.

Set the wished RF TX (or RF RX) frequency value; the value of the RF RX (or RF TX) frequency is manually

set, on the basis of the following formula

RF TX - RF RX = ODU shift frequencyThe values of the RF TX and RX frequencies must be within the operating range of the ODU.

Frequency plan

Select the Freq Plan option.

Click on RF Frequency Setting to open the configuration window of the frequency plan.

Set all the parameters of the frequency plan and then confirm clicking on OK.

The channelling frequencies must be within operating range of the ODU:

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

The following conditions must always be verified:

RF TX - RF RX = ODU shift frequencyN0 NN

The following condition must always be verified:

(NN - N0) < max. number of channelsThe maximum number of channels, which can be used in the channelling plan, depends on the system traffic

radio capacity and on the RF density: 2xE1 with ND density: max. 128 channels

4xE1 with ND density: max. 64 channels


8xE1 with HD density: max. 64 channels





32xE1 with HD density: max 16 channels.


With ODU HDe in ND modulation, the 2xE1 radio capacity is not supported.


20/90



911-380/02A0380 - Issue 4, January 2008



21/90


22/90



911-380/02A0380 - Issue 4, January 2008

Capacity

Select the system radio capacity for which the frequency plan is defined, that must be congruent withthe equipped hardware and with the system radio capacity set in the configuration system.

CH Density

Select the RF channel density for which the frequency plan is defined, that must be congruent with

the equipped hardware and with the ODU type set in the system configuration.

RF Channel

Once ended the setting of the frequency plan, select the number of the RF channel to assign to the

system.



23/90



Step 8B Configuration of ND/ND2 Type ODU par. 5.5.1.9

Open the Status and ConfigEquipment window.In the ODU section, click on Configure to open the window for the ODU configuration.Set all the ODU operating parameters.In the configurations with two ODUs, the operation must be executed for both the ODUs.

Starting from SVR 3.6, in case of (1+1) Hot-Standby configuration, the functionality of

automatic alignment of the configuration of the RF frequency parameters between the two

ODUs is implemented; in this case, it is sufficient to configure the RF frequency parameters

on only one of the two ODUs
http://-/?-http://-/?-


24/90



911-380/02A0380 - Issue 4, January 2008

RF TXPower

Set the RF TX power according to the used adjusting modality (ATPC management or fixed RF TX power): Fixed RF TX power

Click on Tx Power Setting to open the window for the configuration of the RF TX power.

Disable the ATPC management (ATPC ManagementDisabled)Set the value of the RF TX power (Tx Power), which must be between the minimum and maximum allowedvalues.In case of (1+1) Hot-Standby configuration, set the value of the coupling loss (Coupling Loss); the value toset depends on the type of used frame (from 0 to 15 dB).The same value must be set for both the ODUs.


On both the terminals of a radio link, the same modality of management of the RF TX powermust be used (both the terminals with ATPC management or both the terminals with fixed RF

TX power).


25/90



RF TX power with ATPC management

Click on Tx Power Setting to open the window for the configuration of the RF TX power.First, disable the ATPC management (ATPC ManagementDisabled)Set the value of the start-up power of the RF transmitter (P-min Start), which must be between theminimum and the maximum allowed values.Enable the ATPC management (ATPC Management Enabled).Set the threshold value of the received RF power (ATPC Threshold) that causes the intervention of theATPC circuit on the RF transmitter of the remote terminal.


In case of configuration of the RF TX power with ATPC management, the ATPC management

must be activated and configured both on the local terminal and on the remote terminal.


26/90



911-380/02A0380 - Issue 4, January 2008

Frequency modalitySelect the frequency modality (continuous frequency or frequency plan): Continuous frequency

Select the Continuous option.

Set the wished RF TX (or RF RX) frequency value; the value of the RF RX (or RF TX) frequency is manually

set, on the basis of the following formula

RF TX - RF RX = ODU shift frequencyThe values of the RF TX and RX frequencies must be within the operating range of the ODU.



27/90



Frequency plan

Select the Freq Plan option.Click on RF Frequency Setting to open the configuration window of the frequency plan.

Set all the parameters of the frequency plan and then confirm clicking on OK.

The channelling frequencies must be within operating range of the ODU:

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

The following conditions must always be verified:

RF TX - RF RX = ODU shift frequencyN0 NN

The following condition must always be verified:

(NN - N0) < max. number of channelsThe maximum number of channels, which can be used in the channelling plan, depends on the system traffic

radio capacity and on the RF density: 2xE1/2xT1 with ND density: max. 128 channels

4xE1/4xT1 with ND density: max. 64 channels



1xE3 with ND density: max. 16 channels.



28/90



911-380/02A0380 - Issue 4, January 2008

N0

Set the number of the first channel of the frequency plan.The following condition must be always verified: N0 NN.

NNSet the number of the last channel of the frequency plan.

The following condition must be always verified: NN N0.

TF0

Set the frequency of the first transmission channel of the frequency plan.

Step

Set the spacing of the two RF channels adjacent in the frequency plan.



29/90



Capacity

Select the system radio capacity for which the frequency plan is defined, that must be congruent withthe equipped hardware and with the system radio capacity set in the configuration system.

CH Density

Set the RF channel density to Normal Density (ND).

The RF channel density for which the frequency plan is defined that must be congruent with the

equipped hardware and with the ODU type set in the system configuration.

RF Channel

Once ended the setting of the frequency plan, select the number of the RF channel to assign to the

system.



30/90



911-380/02A0380 - Issue 4, January 2008

Modulation indexGenerally set the preset modulation index for the used standard (ETSI or ANSI option according to the type ofequipped Access unit).There is also the possibility of free setting of the modulation index for the different system radio capacities(Free option): select the Free option

click on Modulation Index to open the window for the manual configuration of the modulation index

set the modulation index for the different system radio capacities.



31/90



Step 9 Link ID Configuration par. 5.5.1.1.7

Open the Status and ConfigEquipmentSystem window.Set the parameters for the link identification: Link Id Code Inserted: it must be the same of that expected from the remote system (value of Link Id Code

Expected on a remote system)

Link Id Code Expected: it must be the same of that transmitted by the remote system (value of Link Id Code

Inserted on a remote system).

In the configuration with two unprotected systems, the operation must be executed for both the systems; in thiscase, it is necessary to click on Link ID to open the window for the configuration parameters of the linkidentification. In case of SRAL XD - SRA L mixed radio links, the default value (15) of link ID must be left set, asthis is the only value managed in this condition. The link ID is a number between 1 and 15 (only in case of32xE1 Access unit it can be between 1 and 255).
http://-/?-http://-/?-


32/90



911-380/02A0380 - Issue 4, January 2008

Step 10 System Activation Command par. 5.5.1.1.4

Open the Status and ConfigEquipmentSystem window.Verify that the System Activation command is On; force to On if it was Off.In the configurations with two radio systems, the operation must be executed for both the systems.
http://-/?-http://-/?-


33/90



Step 11 LAN Ethernet Port Configuration par. 5.5.1.3

Open the Status and ConfigEquipmentExt InterfacesLAN Settings window.Enable and configure the Ethernet LAN port to be used for traffic transport.For each Ethernet port the parameters to be configured are the following: enable port (Enable Port)

enable autonegotiation (Autoneg.)

bit-rate and Duplex modality (Default Type); this parameter is to be configurated only if the autonegotiation

is disabled

reception - transmission scheme (Crossover)

enable to long cable support (length cable > 100 m) (Ext. Distance); this parameter is meaningful only with

bit-rate 10 Mbit/s.

The Ethernet LAN ports are available only with DATA Access.
http://-/?-http://-/?-


34/90



911-380/02A0380 - Issue 4, January 2008

Step 11 LAN Ethernet Port Configuration par. 5.5.1.3


35/90



Step 12 Bridge Ethernet Configuration par. 5.5.1.4

Open the Status and ConfigEquipmentExt InterfacesBridge Settings window.Configure the bridge Ethernet if it is foreseen the use of LAN Ethernet traffic ports.

The bridge Ethernet is available only with DATA Access unit.
http://-/?-http://-/?-


36/90



911-380/02A0380 - Issue 4, January 2008

Bridge functioning modalityThe parameters to be configured are the following: Bridging Mode

It allows selecting the modality used by the bridge for the routing of the frames received in input from the

LAN and Trunk ports.

Four different operating modalities are present:

Normal bridging: Fully connected LAN ports

Each frame in input is routed on the basis of the destination MAC address and the LAN ports are fully

interconnected (the frames in input from a LAN port can be sent to any other port, without no restriction).

Normal bridging: Isolated LAN ports

Each frame in input is routed on the basis of the destination MAC address and the LAN ports are isolated

(the frames in input from a LAN port can be sent only to the Trunk port).

VLAN bridging: Selective VLAN forwarding

The frames in input from a port are routed on the basis of the VLAN ID which they contain. Only thepassage of frame that contain a VLAN tag with value of VLAN ID included in the list of the VLAN IDs

associated to the port is allowed

VLAN bridging: Uplink VLAN tagging & replacing

In each frame in input from a LAN port containing or not a VLAN tag, a tag is inserted with VLAN ID equal

to that associated to the input port

Priority Scheme

It allows selecting the priority scheme used by the bridge to send the frames in output.

Two different priority schemes are present

Fixed Priority

The frames with highest priority are always transmitted as first.

WFQThe transmission of the frame is executed by means of four queues of different weight, each one

associated to a different priority level.

Age time of MAC Address

It allows setting the age time during which a MAC address remains stored in the MAC DB, starting from the

moment when the last frame containing as source this MAC address; once the age time is expired, if in the

meanwhile no other frame has been received containing as source this MAC address, the MAC address is

deleted from the MAC DB.

The age time can be set at steps of 16 seconds and it is calculated multiplying by 16 the set value.



37/90



Default VLAN IDIn VLAN bridging: Uplink VLAN tagging & replacing modality, it is necessary to associate to each LAN port theVLAN ID that will be inserted in the frames in input from the LAN port.

A single VLAN ID can be defined for each LAN port.The default configuration is the following: LAN port 1: VLAN ID = 1

LAN port 2: VLAN ID = 2




The Default VLAN ID configuration is available only if the VLAN bridging: Uplink VLAN

tagging & replacing modality is selected.


38/90



911-380/02A0380 - Issue 4, January 2008

VLAN ID TableIn VLAN Bridging: Selective VLAN forwarding modality it is necessary to configure the VLAN ID table,because, only frames that contain a VLAN tag with determinate values of a VLAN ID can pass through eachport.

It is possible to configure up to 64 different VLAN IDs, specifying the LAN ports associated to each VLAN ID.All the configured VLAN IDs are always automatically associated to the Trunk port.


The VLAN ID table is available only if one of the two VLAN Bridging modalitites is selected;

in VLAN Bridging: Uplink VLAN tagging & replacing modality, the VLAN ID table opens in

read-only modality and displays the current configuration of Default VLAN ID.


39/90



Priority managementThe bridge manages the transmission of the frames received in input from the LAN ports according to fourdifferent priority levels, listed below in increasing priority order: 0 Priority (lowest priority level)

1 Priority

2 Priority

3 Priority (highest priority level)

The frames in input to the Trunk port are always assigned with the highest priority level (3 Priority), in order toavoid the possibility that these frames can be discarded.The parameters to be configured for the priority level to be assigned to the LAN port input frame are thefollowing: 802.1P Priority Table

If for one of more LAN ports is enabled the assignment of the priority level, configure the 802.1p Priority table

according to the value of the User Priority field of the VLAN tag contained in the frame in input to the LANport.

A single 802.1p Priority table is foreseen, whose configuration is valid for all the four LAN ports.



40/90



911-380/02A0380 - Issue 4, January 2008

IP Priority Table

If for one or more LAN ports is enabled the assignment of the priority level, configure the IP Priority tableaccording to the value of the ToS field (IPv4 packets) or of the TC field (IPv6 packets) contained in the IP

packets in input to the LAN port (IP Priority criterion).

A single IP Priority table is foreseen, whose configuration is valid for all the four LAN ports.



41/90



LAN Priority

On each Ethernet LAN port used for traffic transport it is necessary to configure the rules of priority levelassignment to the input frames of the LAN port.

802.1p Priority: the criterion can be enabled or disabled for each single LAN port

IP Priority: the criterion can be enabled or disabled for each single LAN port

Default Priority: for each LAN port, it is possible to select the priority level to assign to the frames in input

to the bridge of the LAN port; the criterion is always enabled for all the four LAN ports.

For a LAN port, the Default Priority criterion is used in the following cases:

no other criterion is enabled for the LAN port

a possible other priority criterion enabled for the LAN port cannot be applied to the frames in input (e.g.:

the IP Prioritycriterion is enabled and the packets in input are not of IP type).

If on a LAN port both criteria 802.1p Priority and IP Priority are enabled, it is necessary to specify the first

criterion to be used to assign the priority level to the input frame (802.1p IP Priority).

In case of VLAN bridging: Uplink VLAN tagging and replacing modality, set the value of the third bit of theUser Priority field (802.1p LSB) contained in the VLAN tag that is inserted in the frame in input from the LAN

port; the other two bits of the User Priority field are determined on the basis of the priority level associated

to the frames in input.



42/90



911-380/02A0380 - Issue 4, January 2008

Step 13A Configuration of Cross-Connections with 16xE1/16xT1 Access Unit par. 5.5.7

Open the Status and ConfigEquipmentExt Interfaces window.Click on Cross Connection to run the application for the configuration of the cross-connection matrix.Create and enable the connections between tributary interface of Access unit and BB radio tributary interfaceaccording the established station configuration.

For the cross-connection matrix configuration with 16xE1/16xT1 Access unit:

up to SVR 3.7 a graphical Java application is available

starting from SVR 3.8 a new Java table application is available.
http://-/?-http://-/?-


43/90



The cross-connection matrix is located between the tributary ports of the Access unit and the BB radio tributaryinterface.Depending on the System Type, the following types of connections are possible: local loop on an external tributary on Access side, (functionality available for all the System Type)

bidirectional unprotected connection of an external tributary on Access side with a radio tributary BB side

(functionalty available for all the System Type)

bidirectional unprotected repeater connection (functionality available only with System Type A/D-Rep).

Starting from SVR 3.8, with the new cross-connection matrix, the following limitations are removed in SystemType A/D-Rep for Access unit 16xE1/16xT1: max add/drop capacity: 8xE1 (50% of the max. capacity)

support of the add/drop connection (unprotected bidirectional cross-connections) only on radio tributaries 1

- 8 on BB side

radio tributaries 9 - 16 on BB side reserved for the repeater connections, with connections allowed only for

radio tributaries corresponding to BB 1 and BB 2.With the removal of these limitations, the System Type 2x(1+0) becomes pointless, as it is a systemconfiguration that can be derived from System Type A/D-Rep by means of a proper configuration of thecross-connection matrix.

On the cross-connection matrix the following operations are possible:

creation of a connection enabling/disabling of a connection

deletion of a connection

Crossed & Enable All command

Updated Crossed & Enable command.

The table of the cross-connections is updated each time that a change of the configuration of thecross-connection matrix is made.Depending on the cases, when the System Type is changed, the existing connections in the matrixcross-connections can be preserved or deleted.

Step 13A Configuration of Cross-Connections with 16xE1/16xT1 Access Unit par. 5.5.7

For System Type 2x(1+0) with Access unit 16xE1/16xT1, the limitation of maximum capacity

of 8xE1/8xT1 for each system is still present.

In case of System Type (1+1) H/S and (1+1) FD, all the unprotected connections from Access

side to BB 1 side are automatically duplicated on the corresponding ports of BB 2 side.

The System Types (1+1) H/S and (1+1) FD are equivalent regarding the cross-connection

matrix.

The cross-connection matrix supports up to 32 connections.


44/90



911-380/02A0380 - Issue 4, January 2008

Step 13B Configuration of Cross-Connections with DATA Access Unit par. 5.5.6

Open the Status and ConfigEquipmentExt Interfaces window.Click on Cross Connection to run the graphycal application for the configuration of the cross-connectionmatrix.Create and enable the connections between the tributary interface of Access unit and BB radio tributaryinterface according the established station configuration.
http://-/?-http://-/?-


45/90



In case of DATA Access unit, the available tributary interfaces in the cross-connection matrix are the following: TRIB i/f: external tributary interface

8xE1 external tributaries are available.

The external tributaries are identified by the Tr code followed by the tributary number (e.g.: Tr #1).

RADIO i/f: radio tributary interface.

The number of available radio tributaries depends on the on air radio capacity set for the radio system

(max. 16xE1 radio tributaries).

The radio tributaries are identified by the R wording followed by the tributary number (e.g.: R#1).

DATA E1 i/f: Ethernet tributary interface.

16 E1 tributary ports are available on the Trunk port of the bridge for the transmission of the traffic on

Ethernet LAN network.

The Ethernet tributaries are identified only by the tributary number (e.g.: #1).

The allowed cross-connections are between:

radio tributaries and external tributaries radio tributaries and Ethernet tributaries

No cross-connection is allowed between Ethernet tributaries and external tributaries and no loopcross-connection is allowed between tributaries of the same interface.The cross-connections on the Ethernet tributaries must be created starting from the first tributary (tributary #1)and following to the next tributaries.A cross-connection is active when the relevant tributary cross-connected on user side is enabled (externaltributary or Ethernet tributary).When it is necessary to set the traffic capacity to be used on the Ethernet interface (Data Capacity).For the traffic capacity of the Ethernet interface, also the 0xE1 value (default value) is foreseen, whichrepresents the condition of Ethernet interface not used for the traffic transport.The enabling of the Ethernet tributaries depend on the traffic capacity set for the Ethernet tributary interface; an

Ethernet tributary can then result enabled and not connected.For each external tributary cross-connected with a radio tributary, also the manual enabling/disabling possibilityis foreseen.

Step 13B Configuration of Cross-Connections with DATA Access Unit par. 5.5.6


46/90



911-380/02A0380 - Issue 4, January 2008

Step 13C Configuration of Cross-Connections with 32xE1 Access Unit par. 5.5.7

Open the Status and ConfigEquipmentExt Interfaces window.Click on Cross Connection to run the application for the configuration of the cross-connection matrix.Create and enable the connections between tributary interface of Access unit and BB radio tributary interfaceaccording the established station configuration.

For 32xE1 Access unit, the cross-connection matrix is a functionality supported starting fromSVR 3.8.
http://-/?-http://-/?-


47/90



The cross-connection matrix is located between the tributary ports of the Access unit and the BB radio tributaryinterface.Depending on the System Type, the following types of connection are possible: bidirectional unprotected connection of an external tributary on Access side with a radio tributary BB side

(functionality available for all the System Types)

bidirectional unprotected repeater connection between a radio tributary on BB 1 side and a radio tributary on

BB 2 side (functionality available only in System Type Ring)

bidirectional protected connection of an external tributary on Access side with a radio tributary on BB 1 side

and a radio tributary on BB 2 side (functionality available only in System Type Ring).

The cross-connection table is updated each time a change is made to the configuration of the cross-connectionmatrix.In case of Access 32xE1 unit with Ring System Type, the cross-connection matrix allows realizingconfigurations with any combination of the three different types of connection (unprotected connections,protected connections, repeater connections), with the only limitation of max. 32 connections.This limitation does not allow a complete configuration of the cross-connection matrix in case of 32xE1 Accessunit with Ring System Type (in theory up to 48 connections would be possible: 16 unprotected connectionsfrom Access side to BB 1 side, 16 unprotected connections from Access side to BB 2 side, 16 repeaterconnections between BB1 side and BB 2 side).The 2x(1+0) and A/D-Rep System Types are not available anymore with 32xE1 Access unit; these systemconfigurationscan be however implemented in Ring System Type by means of a proper configuration of thecross-connection matrix:

The 2x(1+0) functionality foresees two independent systems, with no interconnection between them. Torealize the 2x(1+0) functionality, it is necessary to create only unprotected connections from Access side to

BB 1 side and from Access side to BB 2 side.

The A/D-Rep functionality foresees two independent systems, with interconnections passing at BB level.

To realize the A/D-Rep functionality, it is necessary to create only the following unprotected connections:

unprotected repeater connections between BB 1 side and BB 2 side (Repeater functionality)

unprotected connections from Access side to BB 1 side and from Access side to BB 2 side (Add/Drop

functionality).

The table of the cross-connections is updated each time that a change of the configuration of thecross-connection matrix is made.Depending on the cases, when the System Type is changed, the existing connections in the matrixcross-connections can be preserved or deleted.

On the cross-connection matrix the following operations are possible: Creation of a connection

Enabling/disabling of a connection

Deletion of a connection

Crossed & Enable All command

Updated Crossed & Enable command.

Step 13C Configuration of Cross-Connections with 32xE1 Access Unit par. 5.5.7

In case of System Types (1+1) H/S and (1+1) FD, all the unprotected connections from Access

side to BB 1 side are automatically duplicated on the corresponding ports of the BB 2 side.

The System Types (1+1) H/S and (1+1) FD are equivalent as regards the cross-connection

matrix.

The cross-connection matrix supports up to 32 connections.


48/90



911-380/02A0380 - Issue 4, January 2008

Step 14 Payload configuration with 32xE1 Access unit par. 5.5.1.2.5

Open the Status and ConfigEquipmentExt Interfaces window.Click on Payload to open the window for the configuration of the tributaries.Enable the tributaries according the planned station configuration.The command for the contemporary enabling of all the tributaries is available too.The number of available tributaries depends on the set system capacity.

The configuration of the tributaries for the transport of the payload is a functionality availablein SVR 3.7, as the cross-connection matrix is not supported.
http://-/?-http://-/?-


49/90



Step 15 E1 Way-Side Tributary Configuration par. 5.5.1.2.7

Differently from E3 tributary (that is always inserted and cannot be disabled), there is the possibility toenable/disable the transport of the E1 way-side tributary on each one of the two BB units .

The E1 way-side tributary is available only with 1xE3 Access unit.

In (1+1) H/S and (1+1) FD System Types, the configuration of the E1 way-side tributary must

be the same on both the BB units.
http://-/?-http://-/?-


50/90



911-380/02A0380 - Issue 4, January 2008

Step 16A Configuration of (1+1) H/S Protection par. 5.5.1.5

In case of (1+1) H/S protected configuration, it is necessary to configure the parameters for the operation of(1+1) H/S protection.Open the Status and ConfigEquipmentProtection window.Set the command to force the BB unit (Manual Forced BB) and the RX channel (Manual Forced Channel) toNormal.It is possible to set, for each BB unit, a static delay to recover the possible dynamic delay between the channels1 and 2.It is necessary to set also the protection operating modality, which must be the same for both the BB units; thepossible options are: Unrevertive modality: when the cause that determined the intervention of protection ends, the protection

system remains in the status assumed after the intervention of the protection

Revertive modality: when the cause that determined the intervention of the protection ends, the protection

system returns on the main channel (ODU 1 is prioritary with respect to ODU 2).
http://-/?-http://-/?-


51/90



Step 16B Configuration of (1+1) FD Protection par. 5.5.1.5

In case of (1+1) FD protected configuration, it is necessary to configure the parameters for the operation of(1+1) FD protection.Open the Status and ConfigEquipmentProtection window.Set the command to force the BB unit (Manual Forced BB) and the RX channel (Manual Forced Channel) toNormal.It is possible to set, for each BB unit, a static delay to recover the possible dynamic delay between the channels1 and 2.
http://-/?-http://-/?-


52/90



911-380/02A0380 - Issue 4, January 2008

Step 17 Configuration of F interface par. 5.5.1.2.6

Open the Status and ConfigEquipmentExt Interfaces window.Set the wished baud-rate to be used on the F interface.
http://-/?-http://-/?-


53/90



Step 18 Configuration of the Station Alarms par. 5.5.1.2.6

Open the Status and ConfigEquipmentExt Interfaces window.Click on Station Alarms to open the window for the configuration of the station alarms.Depending on the electrical interface of the station alarms, set the polarity corresponding to the alarm conditionon each input line.Moreover it is possible to associate at each input line a description that identifies the function relevant to thecarried station alarm.
http://-/?-http://-/?-


54/90



911-380/02A0380 - Issue 4, January 2008

Step 19 Configuration of IP Address par. 5.5.3.1

Open the Status and ConfigNetworkIP Address window.Click on Modify to pass to the modify modality of the configuration fields.Set the IP address of the equipment and the related Net-Mask, which must be assigned by the networkadministrator according to the planning of the supervision network. Confirm clicking on OK.
http://-/?-http://-/?-


55/90



Step 20AConfiguration of the User Channels and of the D Channels with 16xE1

Access Unitpar. 5.5.1.2.1

Open the Status and ConfigEquipmentExt Interfaces window.

Configure the User/D-Ext interfaces of the Access unit and the embedded D channels according to whatforeseen by the planning of the supervision network.The configuration of the User/D-Ext interfaces and of the embedded D channel are related, as the external Dchannels are in alternative to the embedded D channels.

System

TypeAvailable Interfaces

Correlation between the User/D-Ext Interfaces and

the Embedded D Channels

2x(1+0)

and

A/D-Rep

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

2 interfaces

two embedded D1 and D2

channels.

The external D channels of the User/D-Ext interfacesand the embedded D channels represent alternativesolutions: when the embedded D1 channel is enabled, the

Dext and Dext SRA L Compatible options of theUser/D-Ext 1 interface are deactivated

when the embedded D2 channel is enabled, the

Dext and Dext SRA L Compatible options of the

User/D-Ext 2 interface are deactivated

when the User/D-Ext 1 interface is configured as

Dext or Dext SRA L Compatible, the embedded

D1 channel is deactivated


Dext or Dext SRA L Compatible, the embedded

D2 channel is deactivated.

(1+1) H/S

and

(1+1) FD


2 interfaces, with User/D-Ext 2

interface pre-fixed as Dext and

that can not be changed

one protected embedded D

channel only.

The external D channel of the User/D-Ext 1 interfaceand the protected embedded D channel representalternative solutions: when the protected embedded D channel is

enabled, the Dext and Dext SRA L Compatible

options of the User/D-Ext 1 interface are

deactivated


Dext or Dext SRA L Compatible, the protected

embedded D channel is deactivated.

(1+0)


2 interfaces, with User/D-Ext 2interface pre-fixed as Dext and

that can not be changed

one embedded D channel only.

The external D channel of the User/D-Ext 1 interfaceand the embedded D channel represent alternative

solutions: when the embedded D channel is enabled, the Dext

and Dext SRA L Compatible options of the



Dext or Dext SRA L Compatible, the embedded D

channel is deactivated.
http://-/?-http://-/?-


56/90



911-380/02A0380 - Issue 4, January 2008

User channels

In case of use of the user channel, it is necessary to specify the type of user channel: codirectional orcontradirectional.There is the possibility of add/drop of the user channel (functionality available only in case of A/D-Rep SystemType).The add-drop of the user channel is available only if both the User/D-Ext interfaces of the Access unit areconfigured for the user channel of codirectional type.




57/90



External D channels

In case of connection between two equipment via external D channel, the interface of an equipment must beconfigured as Dext and the interface of the other equipment must be configured as Dext SRA L Compatible; incase of connection via external D channel between a SRAL XD equipment and an equipment of the SRA Lfamily, it is necessary that the D interface on SRAL XD is configured as Dext SRA L Compatible.




58/90



911-380/02A0380 - Issue 4, January 2008

EmbeddedD channel

In case of use of the embedded D channel, it is necessary: to enable the embedded D channel

to set the tributary and the slot used for the transport of the embedded D channel.

The selection of the E1 tributary to transport the embedded D channel is executed at level of external accessinterface (it is possible to select one of the available 16xE1 external tributaries).The external tributary selected for the transport must be cross-connected with one of the tributary 1-4 of theradio interface, as the transport of the embedded D channel is supported only on the radio tributaries 1-4;otherwise, the mismatch condition for the embedded D channel occurs.The value of the slot must be between 1 and 31.In the (1+1) protected systems, the configuration of the slot to be used for D embedded channel transport mustbe the same for both the BB units, as only one embedded protected D channel is present from the operatingpoint of view.



The real operability of the embedded D channel depends on the enabling status of the E1

tributary selected for the transport.


59/90



Step 20B Configuration of User Channels and D Channels with 16xT1 Access Unit par. 5.5.1.2.2

Open the Status and ConfigEquipmentExt Interfaces window.In case of use of the user channels and/or external D channels, configure the User/D-Ext interfaces of theAccess unit according to what foreseen by the supervision network planning.The following table resumes the channels available for the different System Types.

System Type Available Interfaces

2x(1+0) and A/D-RepThe following channels are available: two User/D-Ext 1 and User/D-Ext 2 interfaces.

(1+1) H/S and (1+1) FD

The following channels are available: two User/D-Ext 1 and User/D-Ext 2 interfaces, with User/D-Ext 2

interface pre-fixed as Dext and that can not be changed.

(1+0)

The following channels are available: two User/D-Ext 1 and User/D-Ext 2 interfaces, with User/D-Ext 2

interface pre-fixed as Dext and that can not be changed.
http://-/?-http://-/?-


60/90



911-380/02A0380 - Issue 4, January 2008

User channelsIn case of use of the user channel, it is necessary: to specify the type of user channel: codirectional or contradirectional

to set the type of code used for the transmission of the information: B8ZS or AMI.

There is the possibility of add/drop of the user channel (functionality available only in case of A/D-Rep SystemType).The add-drop of the user channel is available only if both the User/D-Ext interfaces of the Access unit areconfigured for codirectional type user channel.



61/90



External D channelsIn case of connection between two equipment via external D channel, the interface of the first equipment mustbe configured as Dext and the interface of the other equipment must be configured as Dext SRA L Compatible;in case of connection via external D channel between a SRAL XD equipment and an equipment of the SRA Lfamily, it is necessary that on SRAL XD the D interface has been configured as Dext SRA L Compatible.



62/90



911-380/02A0380 - Issue 4, January 2008

Step 20C Configuration of User Channels and D Channels with 1xE3 Access Unit par. 5.5.1.2.3

Open the Status and ConfigEquipmentExt Interfaces window.Configure the User/D-Ext interfaces of the Access unit and the embedded D channels according to whatforeseen by the planning of the supervision network.The configuration of the User/D-Ext interfaces and of the embedded D channel are related, as the external Dchannels are in alternative to the embedded D channels.

System


Correlation between the User/D-Ext Interfaces and the

Embedded D Channels

(1+0)

The following channels areavailable: two User/D-Ext 1 and

User/D-Ext 2 interfaces, with

User/D-Ext 2 interface

pre-fixed as Dext and that

can not be changed


channel only.

The external D channels of the User/D-Ext1 interfaces andthe embedded D channels represent alternative solutions: when the embedded D channel is enabled, the Dext

and Dext SRA L Compatible options of the User/D-Ext

1 interface are deactivated

when the User/D-Ext 1 interface is configured as Dext

or Dext SRA L Compatible, the embedded D channel

is deactivated

(1+1) H/S

and

(1+1) FD





can not be changed

one protected embedded Dchannel only.

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

the Dext and Dext SRA L Compatible options of the


when the User/D-Ext 1 interface is configured as Dext

or Dext SRA L Compatible, the protected embedded Dchannel is deactivated.
http://-/?-http://-/?-


63/90



User channelsIn case of use of the user channel, it is necessary to specify the type of user channel: codirectional orcontradirectional.


For the transport of the user channel, only the User/D-Ext 1 interface can be used.


64/90



911-380/02A0380 - Issue 4, January 2008

External D channelsIn case of connection between two equipment via external D channel, the interface of an equipment must beconfigured as Dext and the interface of the other equipment must be configured as Dext SRA L Compatible; incase of connection via external D channel between a SRAL XD equipment and an equipment of the SRA Lfamily, it is necessary that the D interface on SRAL XD is configured as Dext SRA L Compatible.


Only the configuration of the User/D-Ext 1 interface can be used, because the User/D-Ext 2

interface is fixed as Dext and cannot be modified.


65/90



EmbeddedD channelIn case of use of the embedded D channel, it is necessary: to enable the embedded D channel

to set the slot of the E1 way-side tributary used for the transport of the embedded D channel.

The value of the slot must be between 1 and 31.In the (1+1) protected systems, the configuration of the embedded D channel must be the same for both the BBunits, as only one embedded protected D channel is present from the operating point of view.


The embedded D channel is transported on a slot of the E1 way-side tributary.

The real operability of the configuration of the embedded D channel (enabling and transport

slot) is then related to the enabling status of the E1 way-side tributary.


66/90



911-380/02A0380 - Issue 4, January 2008

Step 20D Configuration of User Channels and D Channels with DATA Access Unit par. 5.5.1.2.4

Open the Status and ConfigEquipmentExt Interfaces window.Configure the User/D-Ext interfaces of the Access unit and the embedded D channels according to whatforeseen by the planning of the supervision network.The configuration of the User/D-Ext interfaces and of the embedded D channel are related, as the external Dchannels are in alternative to the embedded D channels.

System


Correlation between the User/D-Ext Interfaces and the

Embedded D Channels

(1+1) H/S

and(1+1) FD





can not be changed


channel only.

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

the Dext and Dext SRA L Compatible options of the


when the User/D-Ext 1 interface is configured as Dext or

Dext SRA L Compatible, the protected embedded D

channel is deactivated.

(1+0)





can not be changed

one embedded D channelonly.

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

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

interface are deactivated

when the User/D-Ext 1 interface is configured as Dext or

Dext SRA L Compatible, the embedded D channel is

deactivated.
http://-/?-http://-/?-


67/90





For the transport of the user channel, only the User/D-Ext 1 interface can be used.


68/90



911-380/02A0380 - Issue 4, January 2008



Only the configuration of the User/D-Ext 1 interface can be used, because the User/D-Ext 2

interface is fixed as Dext and cannot be modified.


69/90





The selection of the E1 tributary to transport the embedded D channel is executed at level of external accessinterface (it is possible to select one of the available 8xE1 external tributaries).The external tributary selected for the transport must be cross-connected with one of the tributaries 1-4 of theradio interface, as the transport of the embedded D channel is supported only on the radio tributaries 1-4;otherwise, the mismatch condition for the embedded D channel occurs.The value of the slot must be between 1 and 31.In the (1+1) protected systems, the configuration of the slot to be used for D embedded channel transport mustbe the same for both the BB units, as only one embedded protected D channel is present from the operatingpoint of view.


The real operability of the embedded D channel depends on the enabling status of the E1

tributary selected for the transport.


70/90



911-380/02A0380 - Issue 4, January 2008

Step 20E Configuration of User Channels and D Channels with 32xE1 Access Unit par. 5.5.1.2.5

Open the Status and ConfigEquipmentExt Interfaces window.Configure the User/D-Ext interfaces of the Access unit and the embedded D channel according to whatforeseen by the planning of the supervision network.The configuration of the User/D-Ext interfaces and of the embedded D channel are related, as the external Dchannels are in alternative to the embedded D channel.

System


Connection between the User/D-Ext Interfaces and the

Embedded D Channel

(1+1) H/S

and

(1+1) FD


User/D-Ext 2 interfaces

one protected embedded

D channel only.

The external D channel of the User/D-Ext 1 interface and theprotected embedded D channel are in alternative: with protected embedded D channel enabled, the Dext and

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

interface are inactive

with the User/D-Ext 1 interface configured as Dext or DextSRA L Compatible, the protected embedded D channel is

inactive.

(1+0)



one embedded D channel

only.

In SVR 3.8 the User/D-Ext 2interface is configurable (it isnot prefixed like Dext).

The external D channel of the User/D-Ext 1 interface and theprotected embedded D channel are in alternative: with embedded D channel enabled, the Dext and Dext

SRA L Compatible optionsare inactive

with the User/D-Ext 1 interface configured as Dext or Dext

SRA L Compatible, the embedded D channel is inactive.

Ring



one embedded D channel

only.

The external D channel of the User/D-Ext 1 interface and theembedded D channel are in alternative: with embedded D channel enabled, the Dext and Dext

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

are inactive

with the User/D-Ext 1 interface configured as Dext or Dext

SRA L Compatible, the embedded D channel is inactive.
http://-/?-http://-/?-


71/90






72/90



911-380/02A0380 - Issue 4, January 2008



In SVR 3.7 it is possible only the configuration of the User/D-Ext 1 interface can be used,

because the User/D-Ext 2 interface is fixed as Dext and cannot be modified.


73/90





The selection of the E1 tributary to transport the embedded D channel is executed at level of external accessinterface (it is possible to select one of the available 32xE1 external tributaries).The value of the slot must be between 1 and 31.



74/90



911-380/02A0380 - Issue 4, January 2008

Step 21 Configuration of the Alarms par. 5.5.4

Open the Status and ConfigAlarms Config window.For each network interface of point - point connection, it is possible to enable/disable the notification alarm.Starting from SVR 3.8, there is the possibility to enable/disable the propagation of the AIS IN and AIS OUTalarms of the tributaries.
http://-/?-http://-/?-


75/90



Step 22 Configuration of the Network interfaces par. 5.5.3.2

Open the Status and ConfigNetworkNE Parameters window.Set the wished value of ETH-MTU (it is possible to choose among preset values or set a wished value).Starting from SVR 3.8, it is possible: enable/disable the following ports:

port used for the execution of remote commands on NE

Telnet (enabled by default)

SSH (disabled by default)

port used for the file transfer from/to NE

FTP (enabled by default)

sFTP (disabled by default)

enable/disable the NAPT functionality on the F interface (disabled by default)

select the routing protocol; the allowable options are:

no routing protocol

RIPv protocol (option by default) OSPF protocol.

The OSPF protocol support is a parameter subject to licence; the possible options are: OSPF protocol not supported

OSPF protocol supported.

The NAPT functionality is available only if the F interface is configured to support only the

connection of LCT (IP SRA L disable setting).

Only in case of SVR 3.8, with support of the SSH protocol, even the SSH and sFTP ports are

available.
http://-/?-http://-/?-


76/90



911-380/02A0380 - Issue 4, January 2008

Step 23A Configuration of the Routing Parameters with RIPv1 Protocol par. 5.5.3.2.1

Open the Status and ConfigNetworkNE Parameters window.Select the RIPv1 protocol and open the Interface Parameters window, by clicking on Details push-button.Set the parameters of the network interfaces of the equipment; they must be assigned by the networkadministrator according to the planning of the supervision network.For each network interface, it is necessary to set the following parameters: Network Protocol: it is the network protocol of the interface:

for the F interface, the configuration options of the network protocol are:

IP SRA L Disable: support only of the connection to LCT

IP (default option): support both of the connection to LCT and the point-point connection with an

equipment of the SRA L family.

for the V-bus interface, the configuration options of the network protocol are:

None: disabled interface

IP SRA L Compatible: interface enabled with the IP protocol on proprietary HDLC; it must be set in

case of direct connection with an equipment of the SRA L family for the Q/V interface, the configuration options of the network protocol are:

None: disabled interface

IP: interface enabled with IP protocol on PPP and PPP on standard HDLC.

for the R and D interfaces, the configuration options of the network protocol are:

None: disable interface

IP: interface enabled with IP protocol on PPP and PPP on standard HDLC

IP SRA L Compatible: IP on proprietary HDLC; it must be set in case of direct connection with an

equipment of the SRA L family.

RIPv1 Enable: option for enabling of the interface as support of the RIPv1 routing protocol; with this option

disabled, all the other routing options are not meaningful.

RIPv1 Silent: option of RIPv1 protocol squelched in output from the interface.

Static Route Propagation: option of propagation of all the static routing information through the interface. Border Gateway: option of esclusion of the subnetwork information in the routing tables propagated through

the interface.

Ingress Summarization: option of resolution of the IP addresses contained in the routing tables received

through the interface:

with enabled option, the IP addresses are seen as network/subnetwork addresses

with disabled option, the IP addresses are seen as host addresses.

Metric Override: option of forcing of the metric reset.

The V-bus and Q/V interfaces are in alternative. The enabling of the V-bus interface involves

the automatic disabling of the Q/V interface and viceversa.

In case of use of the V-bus interface, it is suggested to physically disconnect the Q/Vinterface.

It is necessary to disable the Ethernet Q/V interface (None option) when the F interface is

used for the connection to a SRA L in the same IP subnetwork.

For the F interface is not available the None option, because the F interface has to be

always enabled to allow the equipment local connection.
http://-/?-http://-/?-


77/90



Step 23A Configuration of the Routing Parameters with RIPv1 Protocol par. 5.5.3.2.1


78/90



911-380/02A0380 - Issue 4, January 2008

Step 23B Configuration of the Routing Parameters with OSPF Protocol par. 5.5.3.2.1

Open the Status and ConfigNetworkNE Parameters window.Select the OSPF protocol and open the Interface Parameters window, by clicking on Det

Documents

Commissioning LCT