Web Lct-Alfoplus2 1.1 Mn00351e 002

WEB LCT
ALFOplus2
ALFOplus2 in Full Outdoor configuration
management software application
Release 1.1
User manual
MN.00351.E - 002
The information contained in this handbook is subject to change without notice.
Property of SIAE MICROELETTRONICA. All rights reserved according to the law and to the international reg-
ulations. No part of this document may be reproduced or transmitted in any form or by any means, elec-
tronic or mechanical, without written permission from SIAE MICROELETTRONICA.
Unless otherwise specified, any reference to a Company, name, data and address produced on the screen
display is purely indicative and aims to illustrate the use of the product.
MS-DOS®, MS Windows® are trademarks of Microsoft Corporation.
HP®, HP OpenView NNM and HP–UX are Hewlett Packard Company registered trademarks.
UNIX is a UNIX System Laboratories registered trademark.
Oracle® is a Oracle Corporation registered trademark.
Mozilla Firefox is a Mozilla Foundation registered trademark.
Linux term is a trademark registered by Linus Torvalds, the original author of Linux operating system. Linux
is freely distributed according to GNU General Public License (GPL).
Other products cited here in are manufacturer’s registered trademarks.
Contents
MANUAL CONTENT ................................................................................................................. 11
WEB LCT APPLICATION.......................................................................................................... 12
FUNCTIONALITIES .............................................................................................................. 13
LIMITS.............................................................................................................................. 14
CHARACTERS SET .............................................................................................................. 15
INSTALLATION ................................................................................................................... 16
WEB LOCAL CRAFT TERMINAL (WEB LCT) PAGE..................................................................... 17
OPEN/CLOSE THE WEB LCT PAGE ......................................................................................... 18

Open the WEB LCT page ................................................................................................ 18
Open more WEB LCT pages............................................................................................ 19
Close the WEB LCT page................................................................................................ 19
ELEMENTS OF THE WEB LCT PAGE ........................................................................................ 20

Equipment Menu area ................................................................................................... 21
Equipment info area...................................................................................................... 22
Users area ................................................................................................................... 23
User Profile parameter............................................................................................. 23
[Logout] parameter ................................................................................................ 23
[Open Far End] parameter ....................................................................................... 23
Open the WEB LCT page of equipment (Remote Link) ............................................ 24
[Help] parameter.................................................................................................... 24
Remote elements list area ............................................................................................. 25
Add a station to the list ........................................................................................... 26
Rename a station of the list ..................................................................................... 26
Remove a station of the list...................................................................................... 26
Add equipment to the list......................................................................................... 27
Remove equipment from the list ............................................................................... 27
Reset the remote equipment list ............................................................................... 28
Open the WEB LCT page of equipment of the list (Remote Link) .................................... 28
Remote equipment list (info) .................................................................................... 29
Context area................................................................................................................ 30
Equipment status area .................................................................................................. 31
Verify the active manual operations .......................................................................... 32
Verify/modify the manual operation timeout ............................................................... 32
MESSAGES DISPLAYED IN THE WEB LCT PAGE ....................................................................... 33
WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 1

MENU AND COMMANDS (EQUIPMENT MENU) ......................................................................... 34
MAIN ................................................................................................................................ 35
Equipment Properties .................................................................................................... 36
Verify the basic configuration of the equipment........................................................... 36
Modify the equipment identifier ................................................................................ 36
Modify the IP address of the agent SNMP of the equipment .......................................... 36
Execute the equipment software reset ....................................................................... 36
Align the reference date/time of the equipment to the current date/time of the PC .......... 37
Verify the equipment feature .................................................................................... 37
Enable a new equipment feature ............................................................................... 37
Verify the equipment units ....................................................................................... 38
Equipment Properties context ................................................................................... 39
General Info tab ............................................................................................... 39
Equipment Features tab ..................................................................................... 40
Equipment Units tab.......................................................................................... 40
Performance Monitoring................................................................................................. 42
Verify the status, the results and the threshold exceeding alarms of a PM measure.......... 42
Activate one or more PM measures ........................................................................... 43
Deactivate one or more PM measures ........................................................................ 43
Reset the threshold exceeding alarms of one or more PM measures............................... 43
Reset the values of the records daily and primary of one or more PM measures............... 43
Set the thresholds of the control parameters and alarms of a PM measure...................... 44
Performance Monitoring context................................................................................ 46
Performances window........................................................................................ 47
PM measures available ............................................................................................ 51
G828 ><transceiver> ....................................................................................... 51
RxPwr ><transceiver> ...................................................................................... 51
TxPwr ><transceiver> ...................................................................................... 51
ACM > <Radio Link name> (<transceiver>) ......................................................... 52
PM measures (info) ................................................................................................. 53
Report & Logger ........................................................................................................... 55
Save the log of the equipment alarms ....................................................................... 55
Delete the log of the equipment alarms ..................................................................... 56
Save the log of the operations executed by the users .................................................. 56
Delete the log of the operations executed by the users ................................................ 56
Save the equipment configuration ............................................................................. 57
Report & Logger context .......................................................................................... 58
NMS Wake Up Config. ................................................................................................... 59
Verify the Wake Up functionality status...................................................................... 59
Set the execution parameters and activate the Wake Up functionality ............................ 59
Disable the Wake Up functionality ............................................................................. 59
NMS Wake Up Config. context .................................................................................. 60
Wake Up functionality (info) ..................................................................................... 61
Software Info & Maint. .................................................................................................. 62
Verify the software/firmware version of the equipment ................................................ 62
Update the software/firmware of the equipment ......................................................... 62
Switch the functioning of the memory benches relevant to the controller........................ 63
Restore Factory Default of the equipment .................................................................. 64
Execute the equipment software reset ....................................................................... 64
Software Info & Maint context .................................................................................. 65
Equipment Firmware tab .................................................................................... 65
Advanced tab ................................................................................................... 66
2 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

Equipment software/firmware (info) .......................................................................... 67
Factory Default of the equipment (info) ..................................................................... 68
Backup/Restore Config. ................................................................................................. 69
Save the whole equipment configuration (backup configuration) ................................... 69
Transfer the equipment configuration previously saved (restore configuration)................ 70
Retrieve the equipment configuration automatically saved by the program before
the last operation of configuration restore (revert configuration) ................................... 70
Backup/Restore Config. context ................................................................................ 72
Backup/restore of the equipment configuration (info) .................................................. 73
Alarm Severity Config. .................................................................................................. 74
Verify the severity and the enabling/forwarding status of the alarms ............................. 74
Enable/disable an alarm .......................................................................................... 74
Enable/disable the forwarding of the trap of an alarm .................................................. 74
Change the severity of an alarm ............................................................................... 75
Alarm Severity Config. context ................................................................................. 76
Alarms management (info) ...................................................................................... 77
Group/User Management ............................................................................................... 78
Groups .................................................................................................................. 79
Verify the user groups ....................................................................................... 79
Add a user group .............................................................................................. 79
Modify a user group .......................................................................................... 80
Delete a user group........................................................................................... 81
Groups context ................................................................................................. 82
HTTP/HTTPS protocol (info) ................................................................................ 84
SNMP protocol (info) ......................................................................................... 87
FTP/SFTP protocol (info) .................................................................................... 89
Installation and configuration of SSH server ................................................... 91
SSH protocol (info) ........................................................................................... 93
Users .................................................................................................................... 94
Verify the user list............................................................................................. 94
Add a user ....................................................................................................... 94
Modify a user ................................................................................................... 95
Delete a user ................................................................................................... 96
Users context ................................................................................................... 97
Users management (info) .................................................................................. 98
Permanent Login ...................................................................................................101
Verify the IP address of Permanent Login ............................................................101
Set/modify the IP address of Permanent Login .....................................................101
Permanent Login context ..................................................................................102
Logged Users ........................................................................................................103
Verify the users connected to the equipment .......................................................103
Force the logout of a user .................................................................................103
Logged Users context .......................................................................................104
Security Management ..................................................................................................105
Access Control List .................................................................................................106
Verify the rules used by the ACL ........................................................................106
Add a rule to ACL.............................................................................................106
Modify a rule of ACL .........................................................................................107
Remove a rule from ACL ...................................................................................107
Access Control List context................................................................................108
ACL function (info) ...........................................................................................109
Services Status Config............................................................................................111
Verify the operating of the communication protocols .............................................111

Enable/disable the operating of a communication protocol .....................................111
Services Status Config context...........................................................................112
SSL/HTTP Secure...................................................................................................113
Verify the configuration of the SSL protocol .........................................................113
Modify the list of CipherSuite managed by the equipment......................................113
Generate the Certificate Signing Request for an equipment....................................114
Download the SSL certificate in an equipment......................................................114
SSL/HTTP Secure context..................................................................................115
Radio Encryption ...................................................................................................116
Verify the status and configuration of Radio Encryption function .............................116
Modify the allocation of memory for Radio Encryption function ...............................116
Modify the enabling of Radio Encryption function ..................................................117
Modify the data encryption algorithm..................................................................117
Modify the encryption key .................................................................................117
Radio Encryption context ..................................................................................118
Radio Encryption (info) .....................................................................................119
Clients .................................................................................................................120
Ftp/Sftp..........................................................................................................121
Verify the operating status of the FTP and SFTP protocols ................................121
Enable/disable the FTP and/or SFTP protocol..................................................121
Modify the FTP access credentials.................................................................121
Modify the SFTP access credentials ...............................................................122
Ftp/Sftp context.........................................................................................123
EQUIPMENT ......................................................................................................................124
Radio Configurator.......................................................................................................125
Verify the Radio Link configuration ...........................................................................125
Create a Radio Link................................................................................................125
Modify a Radio Link ................................................................................................126
Delete a Radio Link ................................................................................................127
Radio Configurator context......................................................................................128
Radio Link (info) ....................................................................................................129
BW & Mod./Link ID ......................................................................................................130
Verify the reference band/modulation, the operating status and the configuration
parameters of the adaptive modulation.....................................................................130
Modify the reference band.......................................................................................130
Modify the reference modulation ..............................................................................131
Modify the operating status of the adaptive modulation...............................................131
Modify the lower threshold and the upper threshold of the modulation (ACM enabled) .....131
Verify/modify the Link identification number..............................................................131
BW & Mod./Link ID context .....................................................................................132
Modulation & Capacity tab.................................................................................132
Local Link ID tab..............................................................................................133
General Preset ............................................................................................................134
Verify/modify the threshold level of the signal at reception ..........................................134
Verify/modify the radio Link label.............................................................................134
General Preset context ...........................................................................................135
Xpic ...........................................................................................................................136
Verify the configuration parameters of the XPIC function .............................................136
Disable temporarily the function XPIC for a single transceiver ......................................136
Restore the XPIC function of the single transceiver .....................................................136
Enable/disable XPIC fault management procedure (FMP) .............................................137
Restore the function XPIC after a fault detection ........................................................137
Xpic context..........................................................................................................138

XPIC function (info) ...............................................................................................140
BASE BAND ......................................................................................................................141

Ethernet.....................................................................................................................142
Bridge Mode Conf. .................................................................................................143
Verify the Bridge mode of the Ethernet Switch .....................................................143
Modify the Bridge mode of the Ethernet Switch ....................................................143
Bridge Mode Conf. context ................................................................................144
Port Manager ........................................................................................................145
Verify the Ethernet ports configuration................................................................145
Modify the enabling status of a port....................................................................145
Activate the loop on line side of a port ................................................................146
Deactivate the loop on line side of a port ............................................................146
Modify the activation state of the autonegotiation for a port...................................146
Restart the auto negotiation procedure for a port .................................................147
Modify the transmission speed of a port ..............................................................147
Modify the inversion status of the Tx and Rx lines of a port....................................147
Modify the maximum dimension of the packet accepted by a ports .........................147
Modify the Bridge Port Type for a port ................................................................148
Verify the optical module configuration of the Ethernet ports .................................148
Verify the flow control configuration of the Ethernet ports .....................................149
Verify/modify the traffic class which a packet, in input from a port, is assigned to,
depending on its priority (User Priority) ..............................................................149
Verify the status of the ports as regards the Link Aggregation function....................150
Verify the parameters for the Tunneling management ...........................................150
Port Manager context .......................................................................................151
Physical Interface tab .................................................................................151
Optical tab ................................................................................................153
Data Flow tab ............................................................................................154
Traffic Class 802.1p Mapping tab..................................................................155
LA Status tab ............................................................................................155
Tunneling tab ............................................................................................156
VLAN ...................................................................................................................158
Verify the basic configuration of the VLAN management ........................................158
Enable/disable the learning of the addresses in the MAC Table ...............................158
Modify the aging time of the addresses stored in the MAC Table .............................159
Modify the limit of MAC unicast addresses per VLAN managed by the Switch ............159
Modify the type of packets accepted in input by a port/LAG ...................................159
Modify the check modality (filtering) applied to the packets in input on a port/LAG ...159
Modify the default VLAN identifier of a port/LAG (Port VID)....................................160
Modify the default value to enter in the User Priority field of the packets without
priority 802.1p received on the port/LAG.............................................................160
Verify the existing static VLANs..........................................................................160
Create one or more static VLANs........................................................................160
Modify the configuration of a static VLAN ............................................................161
Delete one or more static VLANs ........................................................................162
VLAN context ..................................................................................................163
Basic Settings tab ......................................................................................163
Port Settings tab ........................................................................................164
Static VLANs tab ........................................................................................165
Prov. Bridge-VLAN .................................................................................................167
Verify the C-VID registration table (C-VID Registration) ........................................167
Verify the Provider Edge Port configuration table (PEP Configuration) ......................167
Prov. Bridge-VLAN context ................................................................................168

C-VID Registration tab ................................................................................168
PEP Configuration tab .................................................................................169
Prov. Bridge-EtherType...........................................................................................171
Verify the EtherType values in the S-Tag field of the Ethernet ports ........................171
Modify the EtherType values in the S-Tag field of a port/LAG .................................171
Prov. Bridge-EtherType context .........................................................................172
Header Compression ..............................................................................................173
Verify the status of the function for the compression of the headers of Ethernet
packets ..........................................................................................................173
Enable/disable the functionality for the compression of the headers of Ethernet
packets ..........................................................................................................173
Verify/modify the context depth to compress in the header of the Ethernet packets ..173
Verify/modify the parsing mode applied to the header of the Ethernet packets .........174
Header Compression context .............................................................................175
Header Compression (info)................................................................................176
RSTP....................................................................................................................177
Enable/disable the use of STP/RSTP protocol for the equipment .............................177
Verify/modify the allocation of memory for the STP/RSTP function ..........................178
Verify/modify the ports set for the STP/RSTP function ...........................................178
Verify/modify the enabling of STP/RSTP function ..................................................179
Verify/modify the dynamic path cost calculation functions (STP/RSTP) ....................179
Verify/modify the version of the protocol (STP/RSTP)............................................180
Verify/modify the priority assigned to the Switch (STP/RSTP).................................180
Verify/modify the maximum number of BPDU packets in transmission (STP/RSTP)....180
Verify/modify the parameters for the transmission of BPDU packets (STP/RSTP) ......180
Verify/modify the priority of a port (STP/RSTP) ....................................................181
Verify/modify the status of the STP/RSTP function of a port ...................................181
Verify/modify the cost of the a port (STP/RSTP) ...................................................182
Verify/modify the interoperability of the equipment with other equipment (RSTP) .....182
Verify the information stored by every single Switch port (STP/RSTP) .....................182
RSTP context...................................................................................................183
Settings tab ..............................................................................................183
Port Settings tab ........................................................................................185
Port Status tab ..........................................................................................186
STP/RSTP Protocol (info)...................................................................................188
LLF ......................................................................................................................190
Verify the status of the LLF functionality for the Ethernet ports ..............................190
Configure a port for the management of LLF functionality ......................................190
Remove a port of the switch from the management of LLF functionality...................191
Configure the radio circuit for the forwarding of the LOS alarm present on LAN ........191
Remove a radio circuit from the management of LLF functionality for a given LAN ....192
Enable/disable the LLF functionality for a LAN ......................................................192
Enable/disable the forwarding of LLF alarm on the radio ........................................192
Modify the hysteresis value for the LLF functionality .............................................193
Modify the propagation modality of LLF alarm ......................................................193
Modify the forwarding of LOS alarm of a LAN to the radio ......................................193
Modify the modality used to forward the alarm LOS on the radio circuit ...................193
LLF context .....................................................................................................195
Bidirectional LLF (info)......................................................................................197
Queue Depth.........................................................................................................198
Verify the policy for the management of the depth of the queues in output ..............198
Modify the policy for the management of the depth of the queues in output .............198
Queue Depth context........................................................................................199

LA Manager ..........................................................................................................201
Verify the status and configuration of Link Aggregation function .............................201
Modify the allocation of memory for the Link Aggregation function..........................201
Modify the enabling of Link Aggregation function ..................................................202
Verify the static LAGs .......................................................................................202
Create a static LAG ..........................................................................................202
Create a static LAG for protection (ELP) ..............................................................203
Modify the configuration of a static LAG (Admin State, MTU and/or Max Ports) .........203
Delete a static LAG...........................................................................................204
Verify the ports member of one LAG ...................................................................204
Define the ports member of one LAG ..................................................................204
Add/remove the ports to/from one LAG...............................................................205
Remove all the ports from one LAG ....................................................................205
Verify the LACP settings for the ports member of one LAG .....................................206
Modify the LACP settings for the ports member of a LAG (Activity and/or Timeout) ...206
Verify/modify the policy for the distribution of the Ethernet traffic (Link Aggregation)206
LA Manager context .........................................................................................207
General Settings tab...................................................................................207
LAG tab ....................................................................................................208
LACP tab...................................................................................................209
Load Balancing tab .....................................................................................210
Link Aggregation (info) .....................................................................................212
Statistics ..............................................................................................................215
Interface ........................................................................................................216
Verify the counters of the Ethernet interfaces (Interfaces group) ......................216
Reset the counters’ results (Interfaces group) ................................................216
Verify the counters of the Ethernet interfaces (Ethernet-like Statistics group).....216
Reset the counters’ results (Ethernet-like Statistics group) ..............................216
Interface context .......................................................................................218
Interface tab ......................................................................................218
Ethernet tab .......................................................................................218
DCN...........................................................................................................................221
MNGT Port Configuration ........................................................................................222
Verify the configuration of the management port..................................................222
Modify the IP Address/NetMask of the management port .......................................222
Modify the IP Address used as Default Gateway ...................................................223
Modify the VLAN reserved for the in-band management ........................................223
Modify the enabling status of management port ...................................................223
Modify the 802.1p priority for the management VLAN ...........................................223
Modify the DSCP value for the management VLAN ................................................224
Modify the activation state of the autonegotiation for the management port.............224
Modify the transmission speed of the management port ........................................224
Modify the inversion status of the Tx and Rx lines of the management port..............224
Modify the Bridge Port Type for the management port ..........................................225
Restart the auto negotiation procedure for the management port ...........................225
Enable/disable the Loss of Signal Alarm for the management port ..........................226
MNGT Port Configuration context .......................................................................227
Routing Table........................................................................................................229
Verify the Routing Table of the equipment ...........................................................229
Add an element to the Routing Table ..................................................................229
Remove one or more elements from the Routing Table .........................................230
Routing Table context.......................................................................................231

SYNCHRONISATION...........................................................................................................232
Verify the status and configuration of the T0 synchronism .................................................232
Force the status of the T0 synchronisation ......................................................................232
Set the Hold Off Time parameter ...................................................................................233
Set the WTR Time parameter ........................................................................................233
Set the threshold levels of the LTI alarm.........................................................................233
Enable/disable the use of the source quality as criterion to select the synchronism ...............234
Verify/modify the management of synchronisation ...........................................................234
Verify the status and configuration of the synchronism sources..........................................234
Enable/disable the use of a synchronism source...............................................................234
Modify the use priority of a synchronism source ...............................................................235
Force the use of a synchronism source ...........................................................................235
Set a synchronism source as preferential ........................................................................235
Force the quality level in input and/or output of a synchronism source................................236
Restore the availability of a source for the selection of the T0 synchronism without waiting
for the expiry of Wait Time ...........................................................................................236
Verify/modify the management of SSM messages ............................................................237
Verify/modify the line synchronism direction of the LAN’s..................................................237
Synchronisation context ...............................................................................................238
General tab...........................................................................................................238
T0 tab ..................................................................................................................239
LAN SSM tab .........................................................................................................241
1000Base-T Role tab ..............................................................................................242
Synchronisation (info) ..................................................................................................243
Management of synchronisation...............................................................................243
Synchronism sources .............................................................................................243
Enabling of the synchronism sources ..................................................................244
Priority of the synchronism source......................................................................244
Quality of synchronism source ...........................................................................244
Forcing of a synchronism source ........................................................................245
Function of preferential synchronism source ........................................................246
Internal synchronism T0 .........................................................................................246
RADIO .............................................................................................................................247
Radio Branch ..............................................................................................................248
Verify/modify the duplex frequency ..........................................................................248
Verify/modify the frequency which the equipment transmitter is tuned on .....................248
Verify/modify the resolution of the received power (Prx) .............................................249
Verify/modify the resolution of the transmitted power (Ptx) .........................................249
Verify/modify the functioning status of the ATPC ........................................................249
Verify/modify the maximum output power value at the transmitter...............................250
Verify/modify the range of the ATPC regulation..........................................................250
Verify/modify the threshold of the ATPC device ..........................................................250
Radio Branch context .............................................................................................251
ODU Settings tab .............................................................................................251
ODU Powers tab ..............................................................................................252
MAINTENANCE ..................................................................................................................253
S/N Meas ...................................................................................................................254
Verify the value of the S/N measure .........................................................................254
Update the value of the S/N measure .......................................................................254
S/N Meas. context .................................................................................................255
Radio BER ..................................................................................................................256
Verify the status and the configuration parameters of Radio BER measure .....................256

Activate the measure (BER and error count) ..............................................................256
Deactivate the measure (BER and error count) ..........................................................256
Radio BER context .................................................................................................257
MAB...........................................................................................................................258
Verify the existing MAB instances.............................................................................258
Create a MAB Monitor instance ................................................................................258
Modify the configuration of a Monitor MAB instance ....................................................259
Delete one or more Monitor MAB instance .................................................................259
Create a MAB Sender instance .................................................................................260
Modify the configuration of a Sender MAB instance .....................................................260
Delete one or more Sender MAB instances ................................................................261
MAB context .........................................................................................................262
MAB function (info) ................................................................................................264
Radio Loop & Cmd .......................................................................................................266
Verify the digital loops status ..................................................................................266
Activate a digital loop .............................................................................................266
Deactivate a digital loop .........................................................................................267
Verify/modify the operation of the transmitter ...........................................................267
Verify/modify the modulation status of the RF carrier .................................................267
Radio Loop & Cmd context ......................................................................................269
Manual Operations.......................................................................................................270
Verify the manual operations status .........................................................................270
Turn-off/turn-on the transmitter ..............................................................................270
Disable/enable the modulation of the RF carrier .........................................................271
Activate/deactivate a digital loop .............................................................................271
Disable temporarily/restore the XPIC function............................................................272
Force the status of the T0 synchronisation ................................................................272
Force the use of a synchronism source .....................................................................272
Manual Operations context......................................................................................273
RMON ........................................................................................................................274
Settings ...............................................................................................................275
Verify the count status of the RMon statistics.......................................................275
Activate the count of the RMon statistics .............................................................275
Deactivate the count of the RMon statistics .........................................................276
Reset the counters’ results of the RMon statistics .................................................276
Set a RMon instance per Port to the count of the RMon statistics ............................276
Delete a RMon instance per Port for the count of the RMon statistics .......................277
Set a RMon instance Port & Priority or Port & VLAN to the count of the RMon
statistics .........................................................................................................277
Delete a RMon instance Port & Priority or Port & VLAN for the count of the RMon
statistics .........................................................................................................278
Set a RMon instance per Port to the count of the RMON history ..............................278
Delete a RMon instance per Port for the count of the RMON history.........................279
Set a RMon instance Port & Priority or Port & VLAN to the count of the RMON
history ...........................................................................................................279
Delete a RMon instance Port & Priority or Port & VLAN for the count of the RMON
history ...........................................................................................................281
Settings context ..............................................................................................282
Ethernet Statistics tab ................................................................................282
Ethernet History tab ...................................................................................283
Ethernet Service Statistics tab .....................................................................283
Ethernet Service History tab ........................................................................284
RMon standard (info)........................................................................................286
Ethernet Statistics .................................................................................................290

Display the values of the RMon statistic counters (RMon instances per Port) ............290
Ethernet Statistics context ................................................................................291
Ethernet Service Statistics ......................................................................................293
Display the values of the RMon statistic counters (RMon instances Port & Priority
and Port & VLAN).............................................................................................293
Ethernet Service Statistics context .....................................................................294
Ethernet History ....................................................................................................296
Display the history of the RMon statistic (RMon instances per Port).........................296
Filter the history of RMon statistic (RMon instances per Port) .................................296
Ethernet History context ...................................................................................297
Ethernet Service History .........................................................................................299
Display the history of the RMon statistic (RMon instance Port & Priority and
Port & VLAN) ...................................................................................................299
Filter the history of RMon statistic (RMon instance Port & Priority and Port & VLAN) ..299
Ethernet Service History context ........................................................................300
ALARMS LIST ....................................................................................................................... 301
OPERATIONS LIST ............................................................................................................... 305
PARAMETERS LIST ............................................................................................................... 313
ASSISTANCE SERVICE.......................................................................................................... 319

MANUAL CONTENT
This manual describes the commands and the functionalities of the WEB Local Craft Terminal application
(release 1.1) present in the equipment ALFOplus2.
The WEB LCT release present in the equipment can be verified opening the relevant WEB Local Craft Ter-
minal page and selecting Main > Equipment Properties - General Info tab - WEB LCT Version parameter.
In this manual, to make the writing easier, the wording:

• WEB LCT identifies the WEB Local Craft Terminal application for ALFOplus2.
• WEB LCT page identifies the WEB Local Craft Terminal page for ALFOplus2.

WEB LCT APPLICATION
WEB LCT application allows a user connecting to equipment via his own machine (PC, Workstation, etc.)
using the operating system and the Web browser at his disposal.
WEB LCT is an application resident in the equipment controller. It does not require any additional module
installed on the user PC (see Installation).
At start-up of WEB LCT, the browser displays the WEB Local Craft Terminal (WEB LCT) page that is the
application graphical interface (GUI).
The WEB LCT page can be opened directly from browser (see Open/close the WEB LCT page - Fig.1).
Through WEB LCT application, the user can check the equipment operating status and directly intervene
to manage it, verifying/modifying the configuration parameters (see Functionalities and Menu and com-
mands (Equipment Menu).
Fig.1 WEB LCT application (start-up of the WEB LCT page from browser)
User PC
Equipment
(e.g. 172.18.60.33) NE management Browser
(HTTP/
Controller MNGT WEB LCT page
HTTPS)
port *
equipment
WEB LCT (172.18.60.33) Help file
application IP
network
SFTP/SSH
SSH Server Help Web Server
FTP **
FTP Server Web Lct Console
* See MNGT Port Configuration)

** See Installation

FUNCTIONALITIES
Through WEB LCT application, it is possible to manage:
• The properties (identifier, addresses, reference date/time, hardware, features key, etc.) and to
execute the reset of the equipment software (Equipment Properties).
• The measures of Performance Monitoring (Performance Monitoring).
• The log of the equipment alarms, the log of the operations executed by the users and the equip-
ment configuration (Report & Logger).
• The Wake Up trap (NMS Wake Up Config.).
• The equipment software/firmware and the restore of the default equipment settings (Software
Info & Maint.).
• The backup/restore of the whole equipment configuration (Backup/Restore Config.).
• The forward status of the alarms and their severity (Alarm Severity Config.).
• The equipment users list (Group/User Management).
• The equipment communication protocols (SNMP, HTTP, Telnet, FTP, SSH, SFTP, HTTPS), the Ra-
dio Encryption function and the control list of IP accesses (Access Control List) (Security Man-
agement).
• The equipment general configuration (radio configuration, modulation/capacity, adaptive mod-
ulation, etc.) (Equipment).
• The Ethernet Switch configuration, the management ports (Base Band).
• The sources and the outputs of synchronism (Synchronisation).
• The radio parameters (Radio).
• The maintenance parameters (S/N, Radio BER, MAB, digital loops, RMon) (Maintenance).
• The remote element list (Remote elements list area)
• The manual operations and the relevant timeout (Equipment status area).

LIMITS
The following limits must be considered for every single piece of equipment.
Remote equipment list

Maximum number of equipment in the list: 100
Maximum number of stations in the list: 30
Remote equipment list (info)
User list
Maximum number of groups in the list: 10
Maximum number of users in the list: 10
Users management (info)
WEB LCT Session

Maximum number of equipment which can be connected at the same time by means of a single
WEB LCT session: 1
Login to equipment
Maximum number of contemporary connections (login): 10
The system supports at most 10 groups, 10 users and 10 login at the same time.
As regards the logged users, these are distributed in the following mode:
CLI users* connected at the same time to a piece of equipment: 7.
SNMP users** connected at the same time to a piece of equipment: 10.
WEB users*** connected at the same time to a piece of equipment: 4.
* CLI user. User of SM-OS (Siae Microelettronica - Operating System) application.

** SNMP user. User of NMS system.
*** WEB user. User of WEB LCT application.
Area Events
Maximum number of signals in the area Events: 500

CHARACTERS SET
The GUI accepts and recognizes the character set defined by the ISO/IEC 8859-1.
Only exception are the fields relevant to the management of user/groups, which accept and recognize only
the characters 0÷9, a÷z and A÷Z.

INSTALLATION
WEB LCT
WEB LCT is an application resident in the equipment controller.
It does not require any installation on the user PC.
At the first equipment switch-on, the user can immediately connect to it via WEB LCT because
the application is already present in the controller (see Open the WEB LCT page).
Then you can Update the software/firmware of the equipment.
Add-ins
As help to equipment WEB LCT for the management of:
• FTP protocol, it is necessary to install the program WEB Lct Console (WLC) or a FTP
Server (see FTP/SFTP protocol (info).
• Help online of WEB LCT (Help Web Server), it is necessary to install the program
WEB Lct Console.
• SFTP protocol, it is necessary to install a SSH server on one’s PC (see Installation and
configuration of SSH server).
The instructions for the installation of the WLC are reported in the relevant manual. WEB LCT
Console work in MS Windows® environment.
WARNING ALFOplus2 equipment is managed from version 1.2.0 of WLC or later.
Help online
WEB LCT is equipped with a help on-line which can be opened selecting the option [Help] or
in WEB LCT page.
The help on-line must be installed on one’s PC using the installation file specific for the WEB LCT
of the equipment you wish to use.

WEB LOCAL CRAFT TERMINAL (WEB LCT) PAGE
Open/close the WEB LCT page

Elements of the WEB LCT page
Messages displayed in the WEB LCT page

OPEN/CLOSE THE WEB LCT PAGE
Open the WEB LCT page

Open more WEB LCT pages
Close the WEB LCT page
Open the WEB LCT page
WARNING If Ethernet connection is used, checks or settings are not generally necessary. Only if more net-
work cards are equipped, it will be necessary to select the card you wish to use (Host Adapter) (see Web
Lct Console user manual).
When the equipment is connected to the PC via LAN network, the relevant WEB LCT page can be opened
also selecting the equipment from the address book of Web Lct Console (see relevant documentation).
The following procedure requires that:
• The relevant WEB LCT application is present on the equipment which you are connecting to.
• The user, you wish to use to open the WEB LCT page, is valid. With valid user (username/pass-
word) we mean a user present in the users list stored in the controller. The user must be asso-
ciated to a group for which the protocol HTTP and/or HTTPS is active (see Users management
(info).
For the first connection or after a Factory Default operation (see Advanced tab) use the creden-
tials Username: admin, Password: admin.
The opening of the WEB LCT page is supported with:

• Internet Explorer 9 or later.
• Firefox 4.0 or later.
As help for the WEB LCT application in order to manage the:

• FTP Server and Help Web Server, run the program WEB Lct Console version 1.2.0 or later. Al-
ternatively, for the management of FTP, it is possible to use a FTP Server already present on PC
(see FTP/SFTP protocol (info).
• SFTP protocol, it is necessary to install and configure a SSH server (see Installation and config-
uration of SSH server).
1. Run a browser.
2. In the address box type the IP Address of the equipment.

WARNING If the use of HTTPS protocol is active on the equipment (see Services Status Config), an error
page could be displayed, indicating that the connection you are activating is not secure because trou-
bles have been detected with the security certificates.
For the detailed description of the error messages of the browser, refer to the relevant documentation.
To download the SSL certificate see Download the SSL certificate in an equipment.
Generally, the browser asks the user to accept or refuse the connection. If you decide to accept how-
ever the connection with the equipment, the confidential transfer of the data is nor ensured.
The WEB LCT login page opens.
3. Type the name of the user, in the Username box.
4. Type the password, in the Password box.
5. Check the Remember Me box if you wish that, on the next opening of the application, the current user
name and password are automatically displayed; otherwise uncheck the considered box.
6. Press Login.
If the typed values are correct, the system displays the WEB LCT page of the equipment (see Fig.2).
As regards the messages that can be displayed during the start procedure of WEB LCT see Messages
displayed in the WEB LCT page.

Open more WEB LCT pages
It is possible to open:
• More WEB LCT pages on more machines or on the same machine, using the same user or dif-
ferent users.
• Only one WEB LCT page relevant to the same equipment.
• More WEB LCT pages relevant to different equipment.
For more information about the limits of the application, refer to the Limits paragraph.
Close the WEB LCT page
Select the [Logout] parameter.

ELEMENTS OF THE WEB LCT PAGE
1 - Equipment Menu area

2 - Equipment info area
3 - Users area
4 - Remote elements list area
5 - Context area
6 - Equipment status area
Fig.2 shows an example of WEB LCT page on an ALFOplu2 equipment.
Fig.2 Elements of the WEB LCT page (ALFOplu2)
3
1 2
5
6

Equipment Menu area
This area contains the commands to manage the equipment configuration (see Fig.2).
Commands
The commands are subdivided in groups:
Main. Commands to manage the general equipment parameters: management ports,
Routing Table, Performance Monitoring measures, etc.
Equipment, Synchronisation, etc. Commands to manage the configuration parame-
ters typical of the equipment type which the WEB LCT page refers to.
For the description of every group/command see Menu and commands (Equipment Menu).
The selection of a group expands or compresses the list of the underlaying commands. At each
selection, the list takes the status complementary to the previous one (if compressed it becomes
expanded, or vice versa). The symbol:
identifies an expanded group.
identifies a compressed group.
It is possible:
• Expand all the groups at the same time, pressing
• Compress all the groups at the same time, pressing .
The symbol identifies a command which, once selected, displays the parameters associated
to it in the context area (see Context area).
Display/hide area
When the WEB page is opened, the Equipment Menu area is displayed.
Press to hide the area. Press to display the area again.

Equipment info area
This area shows the equipment general properties.
Parameters
Equipment Type. Equipment type.
Equipment ID. Equipment identifier.
Agent IP. IP Address assigned to the agent SNMP of the equipment.
Bridge Mode. Bridge mode (according to IEEE 802.1ad) of the Ethernet Switch:
• Customer Bridge. The Switch is in Customer Bridge mode. In this mode, the Switch
operates as a Bridge 802.1Q VLAN.
• Provider Bridge (802.1ad). The Switch is in Provider Bridge mode. In this mode, the
Switch operates as a Bridge Q-in-Q.
• Provider Edge Bridge. The Switch is in Provider Edge Bridge mode. In this mode, the
Switch operates as a Provider Edge Bridge 802.1ad with one S-VLAN component and
at least one C-VLAN component.
Tables
LEFT TABLE (see Fig.2). Status and radio parameters of the transmitter and receiver.
Every row of the table corresponds to a transceiver for which is displayed:
Transceiver which the data, present in the relevant row, refer to:
• Tx <transceiver>. Operating status and parameters of the specific transceiver
relevant to transmission (TRX A/TRX B).
• Rx <transceiver>. Operating status and parameters of the specific transceiver
relevant to reception (TRX A/TRX B).
RF frequency. The wording:
• ODU Hardware Failure. Hardware problem.
• Must be Set (Dplx). The specific frequency is not set.
Power in input to the receiver (lines Rx...) and in output to the transmitter (lines Tx...).
Both the powers are measured at the antenna flange.
The wording Tx Off (lines Tx...) indicates that the transmitter is off because of an action
of the user (see Verify/modify the operation of the transmitter - selection of Off or Per-
manent Off option) or because of the activation of one or more alarms which cause the
switch-off of the transmitter (for example ...Vco Fail Alarm).
RIGHT TABLE. Channel/modulation and Ethernet radio traffic (Tx/Rx):

Bandwidth & Modulation. Current channel and modulation.
ETH Capacity. Radio capacity reserved to Ethernet tributaries.
The parameters are subdivided by transceiver:

<Radio Link name> [1+0] Tx and <Radio Link name> [1+0] Rx. Respectively
transmission and reception radio branches of a Radio Link in not protected configuration.
<Radio Link name> [2+0 XPIC] Tx <transceiver> and <Radio Link name> [2+0
XPIC] Rx <transceiver>. Respectively transmission and reception radio branches of a
Link with two radio directions in XPIC configuration.
The presence of two different Radio Links in 1+0 configuration indicates that the equipment is
in radio configuration 2x(1+0).
If a Radio Link has not been defined yet, the parameters present in the table are not meaningful.
The area displays the wording Data Unavailable.
Update data
The information present in the Equipment Info area is updated every 15 seconds (timeout).
Press to force the Equipment Info area updating.
Display/hide area
When the WEB page is opened, the Equipment Info area is displayed.

Users area
User Profile parameter

[Logout] parameter
[Open Far End] parameter
[Help] parameter
User Profile parameter
Profile of the user who has opened the WEB LCT page.
Options
Admin. The user has Administrator profile.
The user with this profile can both verify the parameters and send commands or change the
equipment configuration with no exception.
Read/Write. The user has Read/Write profile.

The user with this profile can as check the parameters as send commands or execute changes
to the equipment configuration except for the following operations: modifying the user list,
aligning the date/time of the equipment, force the logout of a user and all those operations avail-
able only to the Admin. user.
Maint. The user has Maintenance profile.

The user with this profile can check the parameters and execute only maintenance operations
(MAN. OP) in the Manual Operations context and Radio BER context.
Read Only. The user has Read Only profile.

The user with this profile can only check the parameters.
Login/Logout
At the opening of the WEB LCT page, the user will be connected to the equipment with the user/
profile entered during the login request.
In any moment it is possible to execute the logout and re-execute the login using the same or
a different user with respect to that used for the login.
NMS
If the equipment is managed also by the NMS5UX-B/NMS5LX supervisory system (NMS GUI,
NMS5WI GUI), the supervisory system considers the connection of a WEB user with Read Only
or Maintenance profile a WEB LCT connection in Monitoring mode.
While the supervisory system considers the connection to the equipment of a WEB user with
Read/Write or Administrator profile a WEB LCT connection in Configuration mode.
[Logout] parameter
This parameter executes the logout of the current user.

When selected, the WEB LCT page to login to the equipment is displayed.
To reconnect equipment, set Username and Password and press Login.
[Open Far End] parameter
This parameter opens the WEB LCT page of remote equipment to contained in the Remote Element Table.

Operations
Open the WEB LCT page of equipment (Remote Link)
Open the WEB LCT page of equipment (Remote Link)
User Profile | Read Only, Maint., Read/Write, Admin.
1. Select the [Open Far End] parameter.

If the remote equipment list contains:
• Only one item of equipment of type Remote Link, the WEB LCT login page of the remote equip-
ment is displayed.
Type the name (Username box) and the access code (Password box) of the WEB user to use to
activate the connection and press Login. In a new page the WEB LCT of the remote equipment
is displayed.
If the WEB LCT login page is not displayed when the login is required, this means that the remote
equipment is unreachable.
• No equipment of type Remote Link, a message is displayed pointing out the absence of the re-
mote equipment.
• More equipment of type Remote Link, the Available Remote Elements window is displayed, con-
taining the list of equipment configured as Remote Link present in the remote equipment list.
For each equipment, the following characteristics are reported:
• Station. Station name.
• Equipment ID. Equipment identifier.
• IP Address. IP address.
• OSI. Parameter not meaningful in this context.
Select the remote equipment and press Open or double click on the equipment.
The WEB LCT page to login to the remote equipment opens.
Type the name (Username box) and the access code (Password box) of the WEB user to use to
activate the connection and press Login. In a new page the WEB LCT of the remote equipment
is displayed.
[Help] parameter
This parameter opens the help online of application.
The message Unable to contact help support... indicates that the program WEB Lct Console necessary for
the management of the Help Web Server has not been started (see Installation).

Remote elements list area
In this area, you can manage the remote equipment list stored in the equipment controller.
Parameters
Station/Equip. Name of the station and equipment in the list.
STATION ( )
Equipment is subdivided into stations.
Selecting the symbol of a station expands or compress the list of underlaying equipment.
At each selection, the list takes the status complementary to the previous one (if com-
pressed it becomes expanded and vice versa).
The name of the station is assigned by the user during the creation of the station itself.
The stations are displayed in the same order as they are inserted in the list.
An empty station, that is a station without associated equipment, cannot be stored in the
list.
EQUIPMENT ( or )
The symbol represents the equipment of type Remote Link (see column Type). The
symbol represents other types of the equipment.
The name of the equipment is automatically assigned by the application during the cre-
ation of the equipment itself: Equipment <progressive number>.
Within the station, the equipment are listed in increasing order with respect to the IP ad-
dress.
IP Addr. IP address (Agent SNMP) of the equipment.
Type. Type of equipment:

• Managed by SCT. Equipment managed by WEB LCT application.
• Remote Link. Equipment, managed by WEB LCT application, constituting the equip-
ment placed on the other end of the radio connection with respect to the local equip-
ment (equipment which the user is connected to by WEB LCT).
• Elem. Manager. Element Manager of the equipment (IP address of the machine where
the NMS5UX-B/NMS5LX system resides).
• Not Managed. Element not managed by the WEB LCT application.
• Nodal X. Equipment belonging to the local node.
With local node we mean a set of minimum 2 and maximum 8 equipment (ALCplus2/
ALCplus2e) interconnected by a Ethernet nodal Bus and/or by a TDM nodal Bus,
where the considered equipment is an element. The X value correspond to a number
between 1 and 8 and indicates the subset.
• 2x1+1-Xpic-Main. IDU Master belonging to an ALCplus2e equipment in XPIC 1+1
configuration.
• 2x1+1-Xpic-Res. IDU Reserve belonging to an ALCplus2e equipment in XPIC 1+1
configuration.
OSI. Equipment NSAP (GOSIP) Address.

Parameter available only for the equipment managed with the OSI protocol.
Buttons
GENERAL
Apply. Confirm the changes.
Refresh. Update the list.
Clear. Reset the remote equipment list
Open. Open the WEB LCT page of equipment of the list (Remote Link)
STATION
Add. Add a station to the list
Remove. Remove a station of the list
Rename. Rename a station of the list

ELEMENT
Add. Add equipment to the list
Remove. Remove equipment from the list
Display/hide area
When the WEB page is opened, the Remote elements list area is hidden.
See also
Add a station to the list
User Profile | Read/Write, Admin.
WARNING It is possible to insert a maximum of 30 stations into a list.
1. In the Remote elements list area, press Add (Station group).
2. Type, into the text box, the name to be assigned to the station (alphanumeric string with minimum 1
and maximum 11 characters).
The program does not create two stations with the same name in the same list. Moreover, a digit cannot
be used as first character and the space character cannot be used at the beginning or within the name
string.
3. Press OK.
The application displays the new station into the Remote elements list area, at the end of the list rele-
vant to the already existing stations.
4. Press Apply and confirm.

An empty station, that is a station without associated equipment, is not saved in the list.
Rename a station of the list
1. In the Remote elements list area, select the station to be renamed.
2. Press Rename.
3. Type, into the text box, the new name (alphanumeric string with minimum 1 and maximum 11 char-
acters).
The program does not create two stations with the same name in the same list. Moreover, a digit cannot
be used as first character and the space character cannot be used at the beginning or within the name
string.
4. Press OK.
The application displays the new name of the station into the Remote elements list area.
Remove a station of the list
WARNING The deleting of the station causes also the removal of all pieces of equipment coupled with such
a station.

1. In the Remote elements list area, select the station to be removed.
2. Press Remove (Station group).

The application removes the station from the Remote elements list area.
Add equipment to the list
WARNING It is possible to add to the list a maximum of 100 equipment.

Equipment cannot be created if at least one station has not been created before.
1. In the Remote elements list area, select the station to which the equipment has to be coupled.
If the user does not select any station, the application will automatically couple the equipment with the
last selected station.
2. Press Add (Element group).
3. Into the IP Address box, type the IP address of the equipment.

The program does not create two pieces of equipment with the same IP Address in the same list (even
if in different stations).
4. Set the Type of element box, selecting the option relevant to the element type to be inserted:
• Managed By SCT. Equipment managed by the WEB LCT application.
• Remote Link. Equipment managed by the WEB LCT application that constitutes the equipment
placed on the other end of the radio connection with respect to the local equipment.
• Element Manager. Element Manager of the equipment (IP address of the machine where the
NMS5UX-B/NMS5LX system resides).
• Not Managed. Element not managed by WEB LCT application.
This option can be used to insert into the remote equipment list for instance the coupling be-
tween the IP address and the NSAP (Gosip) one piece of equipment inserted into an OSI net-
work.
• 2x1+1-Xpic-Main. IDU Master belonging to an ALCplus2e equipment in XPIC 1+1 configuration.
Option to use only if problems have occurred regarding the automatic configuration of the re-
mote equipment list during the creation of a XPIC 1+1 system.
• 2x1+1-Xpic-Res. IDU Reserve belonging to an ALCplus2e equipment in XPIC 1+1 configuration.
Option to use only if problems have occurred regarding the automatic configuration of the re-
mote equipment list during the creation of a XPIC 1+1 system.
5. Press OK.
In the Remote elements list area, under the selected station, a record named Equipment <progressive
number> is displayed with the characteristics of the new equipment.
Remove equipment from the list
1. In the Remote elements list area, select the equipment to be removed.
2. Press Remove (Equipment group).

The application removes the station from the Remote elements list area.

Reset the remote equipment list
1. In the Remote elements list area, press Clear.

The application clears all the records (stations and equipment) present into the Remote elements list
area.
Open the WEB LCT page of equipment of the list (Remote Link)
1. In the Remote elements list area select the equipment of Remote Link type to be opened the WEB LCT
page.
2. Press Open.
The WEB LCT page to login to the remote equipment opens.
3. Type the name (Username box) and the access code (Password box) of the WEB user to use to activate
the connection and press Login.
In a new page the WEB LCT of the remote equipment is displayed.


Each equipment has a remote equipment list stored in its own controller.
With remote equipment list we mean a list containing all the network remote equipment which
you wish to connect to.
For a better vision of the equipment during the setting of the list, it is possible to subdivide the
equipment into stations, in such a way that, at the selection of a station, the application will
display only the detail of the equipment associated with such a specific station. The station does
not have any particular meaning; it has been simply introduced to help the user during the lo-
calization of the equipment.
Into each remote equipment list, it is possible to create a maximum of 100 equipment and 30
station.
WEB LCT
The remote equipment list can be used to define the remote equipment with respect to the local
equipment.
In order to perform this operation, it is necessary to define, within the remote equipment list of
the local equipment, the remote equipment located at the other side (remote equipment) as-
signing the type Remote Link to it (see Add equipment to the list).
In this way, when the button Open Far End present in the GUI is pressed, it will be possible to
open the page WEB LCT of the remote equipment (see Open the WEB LCT page of equipment
(Remote Link).
See also
Remote elements list area
Add a station to the list
Remove a station of the list
Rename a station of the list
Add equipment to the list
Remove equipment from the list
Reset the remote equipment list
Open the WEB LCT page of equipment of the list (Remote Link)

Context area
This area is the part of the WEB LCT page where the equipment parameters are displayed.
Its content changes accordingly to the selected command in the Equipment Menu area, which is indicated
in the top part of the area.
In the remainder of manual, for ease of wording, the contextual area will be simply called “context”.
Buttons
Apply. Selecting it makes the changes, executed on the parameters present in the context, ef-
fective.
Its selection opens a confirmation window. The confirmation windows are timed. When this pe-
riod is elapsed (pointed out by the progress bar), if the user has not confirmed the operation,
the window is closed and the operation cancelled.
The confirmation window displays the option Don’t ask again. Activate the option to avoid the
system displays the confirmation request when Apply is selected in any context of WEB LCT
page. This setting remains valid until the exit from the current session (logout or page closing).
If the Apply button is not available:
• It is not possible to execute changes because the user profile does not allow this or
the equipment is in connected/monitor status.
• No parameter present in the window has been modified. In this case, the button be-
comes available when the value of a parameter is changed.
• Another button is present in the context for the confirmation of the operation or the
change of the parameters.
Refresh. Force the reading of the data from equipment.

If the button is not available, the connection with the equipment is not active.
Help. Open the help on-line.
WARNING For some commands, other buttons are displayed relevant only to the context which
contains them. These buttons are described in the paragraph relevant to the specific command.
Tabs
For some commands, the parameters are subdivided in tabs. The selection of a tab dynamically
changes the content of the context.
Parameters
The parameters present in the context can be read-only or set or modified.
The description of the single commands (see Menu and commands (Equipment Menu) indicates
the parameters which can be modified and modalities to do that.
Generally, for the parameter setting, the following rules are valid:
• Entering a value (alphanumeric string) in a text box.
If a red line is displayed below the text box, the entered value is not allowed because,
for example, a number of characters greater than the allowed one or an invalid value
has been entered (for example, entering of value 172.18.70.334 as IP address).
• Box with possible values displayed in a drop-down menu.
When the value is changed, a red triangle is displayed in the top left edge of the box.
It signals that the value has been changed, but the change has not been communi-
cated yet to the equipment (pressure of button Apply).

Equipment status area
This area shows the functional status of the equipment.
Parameters
URGENT <alarms number>. Number of Critical and/or Major alarms. Colour box:
• Orange. The most serious alarm present into the equipment has Major severity
• Red. The most serious alarm present into the equipment has Critical severity.
• Grey. The equipment has no active alarms with Critical or Major severity.
Select the box to display the active alarm.
NOT URG. <alarms number>. Number of Minor and/or Warning alarms. Colour box:
• Light blue. The most serious alarm present into the equipment has Warning severity.
• Yellow. The most serious alarm present into the equipment has Minor severity.
• Grey. The equipment has no active alarms with Minor or Warning severity.
Select the box to display the active alarm.
DOWNLOAD. Update of the equipment software/firmware. Colour box:

• Light blue. The update is in progress.
• Grey. The update is not in progress.
MAN. OP. Activation of the manual operations. Colour box:

• Light blue. A manual forcing is enabled (e.g. a loop).
• Grey. No manual forcing is active.
Events area
List of the status/alarm signals of the equipment.
Each signal corresponds to a record that is displayed:
• Colour box. Signal type and alarm gravity:
• Green/Status. Status signal.
• Light blue/Warning. Alarm detected with Warning severity.
• Yellow/Minor. Alarm detected with Minor severity.
• Orange/Major. Alarm detected with Major severity.
• Red/Critical. Alarm detected with Critical severity.
• White/Cleared. Alarm detected/cleared.
• Alphanumeric string which details the nature of the signal.
• Logic group which the signal belongs to: COMMON, etc.
• Date/time of the signal detection.
If the row refers to a detected/cleared alarm, the date/time of alarm detection will be
pointed out under the date/time of alarm clearing.
The date/time is set by the network element that has generated the signal. The for-
mat of date/time changes depending on the setting made in the operating system.
Operations
Verify the active manual operations
Verify/modify the manual operation timeout
Update data
The information present in the Events area are dynamically updated when an alarm is generated
or cleared.
Press to force the Events area updating and remove the detected and cleared alarms (box
White/Cleared).
Display/hide area
When the WEB page is opened, the Events area is displayed.

See also
Alarms management (info)
Verify the active manual operations
1. Select the MAN. OP box.

A window displays the manual operations actually activated into the equipment.
The wording None active manual operation shows that no manual operation is active.
The information are not dynamically updated. Press to update the information.
Verify/modify the manual operation timeout
User Profile | Verify: Read Only, Maint. Modify: Read/Write, Admin.
WARNING The timeout setting is common for all the manual forcing operations of the equipment.
1. Select the MAN. OP box.

The Manual Operation Timeout box displays the current timeout of the manual operations.
Value 0 indicates that the timeout has not been activated, this means that the activation of a manual
operation remains active until when the user deactivates it. The activation of a manual forcing (for in-
stance a loop) affects the traffic.
2. To change the parameter, set a value between 0 and 172800 sec. (48 hours).
The setting of the value 0 corresponds to the disabling of the timeout.
3. Press Change and confirm.

MESSAGES DISPLAYED IN THE WEB LCT PAGE
Opening page
Login Failed! Invalid User or Password!. It means that the typed username and/or password is
wrong and/or not present in the equipment user list.
The equipment is update protected by element manager, retry to login as Read Only user. It
means that the equipment is managed also by the NMS5UX-B/NMS5LX supervisory system and
the NMS5UX user has prevented the possibility, for the WEB user, to be able to execute the login
of the equipment. In this case, it is necessary that the NMS5UX user enables again the WEB user
for the execution of the operation.
Too many WEB users!. It means that the equipment has been connected to the maximum num-
ber of allowed users (see Limits).
Open page
When the page is open, self-explanatory messages are usually displayed about the result of an opera-
tion or the impossibility to carry out an action because of the incongruence of the selected parameters.
Moreover, one of the following messages can be displayed:
Warning. Invalid or time-out session. You will be redirected to login form The equipment is in
disconnected status. In this condition, the parameters cannot be verified/modified.
Press Ok to display the WEB LCT page of login to the equipment. Fill the fields Username and
Password and press Login to reconnect to the equipment.
Access Denied. The selected context is available only to the user with profile Administrator.
Warning: You are forcing a manual operation. Operation timeout: <value>. The setting you wish
to execute is a manual operation subjected to timeout.
For each equipment, a timeout can be set after which the relevant active manual operations are
automatically deactivated. The wording No Timeout indicates that the timeout is disabled; this
means that a manual operation remains active until when the user deactivates it.
Loading The request of data is in progress between the PC and the equipment.
Updating, Applying Changes The sending of data is in progress between the PC and the equip-
ment.
Operation Fail! Unable to Get or Update parameter(s). Wrong user profile or not logged yet! The
operation cannot be executed because the user profile in use is not enabled to execute the action
or is not logged to the equipment yet.
Not Implemented Yet!. The command is not available for the current version of the program.

MENU AND COMMANDS (EQUIPMENT MENU)
Main. It manages the general equipment parameters.

Equipment. It manages the radio equipment configuration.
Base Band. It manages the Ethernet Switch configuration, the management ports.
Synchronisation. It manages the sources and the outputs of synchronism.
Radio. It manages the Radio parameters.
Maintenance. It manages the maintenance parameters (S/N, Radio BER, MAB, digital loops, RMon).
The description of every single command indicates the status of login/user profile (User Profile parameter)
necessary to use the command or execute the relevant procedures.

MAIN
Equipment Properties. It manages the basic configuration of equipment.

Performance Monitoring. It manages the Performance Monitoring measures.
Report & Logger. It manages the log of the equipment alarms, the log of the operations executed by
the users and the equipment configuration.
NMS Wake Up Config. It manages the Wake Up trap.
Software Info & Maint. It manages the equipment software/firmware and the restore of the default
equipment settings.
Backup/Restore Config. It manages the backup/restore from file of the whole equipment configuration.
Alarm Severity Config. It manages the alarm transmission and their severity.
Group/User Management. It manages the users list of the equipment.
Security Management. It manages the equipment communication protocols (SNMP, HTTP, Telnet, FTP,
SSH, SFTP, HTTPS).

Equipment Properties
The Equipment Properties command manages the basic configuration of the equipment.
Operations
Verify the basic configuration of the equipment
Modify the equipment identifier
Modify the IP address of the agent SNMP of the equipment
Execute the equipment software reset
Align the reference date/time of the equipment to the current date/time of the PC
Verify the equipment feature
Enable a new equipment feature
Verify the equipment units
GUI
Equipment Properties context
Verify the basic configuration of the equipment
1. Select Main > Equipment Properties.

The General Info tab displays the basic configuration of the equipment.
2. In the Equipment ID field set an alphanumeric string with minimum 1 and maximum 50 characters.
2. In the Agent IP Address box type the new IP address.
WARNING Operation is no traffic affecting.

After the reset, all the values activated before the operation result as valid ones.

2. Press System Restart and confirm.
Align the reference date/time of the equipment to the current date/time of the PC
User Profile | Admin.
WARNING The operation could cause the logout of the user.
2. Press Align to PC time and confirm.

The values present in the System Date/Time area are updated by the values of one’s PC.
Verify the equipment feature

2. Select the Equipment Features tab.
The tab displays the equipment feature enabled on demand.
Enable a new equipment feature
WARNING Depending on the protocol set for the file transfer (see Ftp/Sftp context), check out that:
• Protocol FTP. The program WEB Lct Console or a FTP Server is active, otherwise start them.
If you use an FTP Server, the credentials used to access to the WEB LCT page must be the same
configured for the FTP Server and the file (certificate) must be present into a sub-folder of the
Shared Folder set during the configuration of FTP Server (see FTP/SFTP protocol (info).
• Protocol SFTP. A SSH server is installed on one’s PC (see SSH protocol (info).
The default SFTP credentials are the same used by the user to access to the WEB LCT page. For
a correct management of the data transfer, the SFTP credentials shall correspond to the user
(or to one of the users) defined during the installation of the SSH server (see Installation and
In order to enable one or more features, IT IS NECESSARY to require the enabling certificate, represented
by a file (with sfc extension), to the company that provides the equipment.
For each equipment you wish to enable one or more feature, a specific enabling certificate is required, be-
cause there is an univocal Link between each certificate and each specific equipment.
2. Select the Equipment Features tab.
3. Press Upgrade.
4. In the Cert. file path, type the path/name of the certificate.

If the equipment uses the:
• FTP protocol and the FTP Server activated at start-up of WLC, it is necessary to enter the full
path (c:\..). Otherwise, if you use own FTP Server, it is necessary to enter the partial path (only
the sub-folder and the filename of the Shared Folder).
• SFTP protocol you must set the path defined during the configuration of the SSH server (see
Installation and configuration of SSH server - SFTP tab).

5. Set, in the FTP Server IP Addr. box, the IP address of the FTP Server or the SSH Server (if not otherwise
set at the configuration of Server, it corresponds to the IP address of the PC).
6. Press Send.
A message indicates the end and the result of the operation:
• Operation Done. The operation has been executed with success.
• Invalid operation for this equipment…. The selected certificate and equipment are not compati-
ble (wrong serial number or wrong MIB version, etc.).
Verify the equipment units
2. Select the Equipment Units tab.

The tab displays the characteristics of the equipment units.

Equipment Properties context
The context displays the basic configuration of the equipment.
Tabs
General Info tab. Equipment properties: type, ID, IP address, software/firmware version, date/
time.
Equipment Features tab. Functionalities enabled for the equipment.
Equipment Units tab. Equipment units.
Buttons
Refresh. Update the context.
See also
Equipment Properties (command)
General Info tab
The tab displays the general equipment properties.
Parameters
Equipment Type. Equipment type.
Ethernet Bridge Mode. Bridge mode (according to IEEE 802.1ad) of the Ethernet Switch:
• Customer Bridge. The Switch is in Customer Bridge mode. In this mode, the Switch
operates as a Bridge 802.1Q VLAN.
• Provider Bridge (802.1ad). The Switch is in Provider Bridge mode. In this mode, the
Switch operates as a Bridge Q-in-Q.
• Provider Edge Bridge. The Switch is in Provider Edge Bridge mode. In this mode, the
Switch operates as a Provider Edge Bridge 802.1ad with one S-VLAN component and
at least one C-VLAN component.
Equipment ID. Equipment identifier.
Agent IP Address. IP Address assigned to the agent SNMP of the equipment.
IP Address. IP Address of the equipment.
MAC Address. Physical address of the equipment.
Firmware Version. Identification code and version of the equipment software/firmware pre-
sent on the memory bench in use.
WEB LCT Version. Version of the WEB LCT application for ALFOplus2 present into the equip-
ment.
WEB LCT Product Code. Identification code of the WEB LCT application for ALFOplus2 present
into the equipment.
System Up Time. Days, hours, minutes and seconds since the last restart of the equipment.
SYSTEM DATE/TIME
Date. Reference date of the equipment.
Time. Reference time of the equipment.
The format of date/time changes according to the setting made in the operating system.
Buttons
System Restart. Execute the equipment software reset

Align to PC time. Align the reference date/time of the equipment to the current date/time of
the PC
See also
Equipment Features tab
The tab displays the list of the equipment feature enabled on demand.
Parameters
FEATURE NAME
• Upgrade up to 50 Mbps. Radio profile up to 50 Mb/s.

• XPIC. XPIC functionality (2+0 XPIC radio configuration management).
• 2+0 radio configuration. 2x(1+0) radio configuration management.
• Radio payload encryption. Enabling of Radio Encryption function.
• Eth transport. Enabling of Ethernet transport.
• Security package. Equipment security protocols management.
• Sync Quality management. Synchronisation quality management.
• Packet processing (1). Optional Ethernet processing.
FEATURE STATUS
• Enabled. The functionality is enabled.

• Disabled. The functionality is not enabled.
Buttons
Upgrade. Enable a new equipment feature
Equipment Units tab
The tab displays the characteristics of the equipment units.
Table
Every row of the table corresponds to an unit for which are indicated:
Real Type. Unit type really present into the equipment. The wording Unequipped indi-
cates that the unit is not physically present into the equipment.
Expected Type. Foreseen unit type. The wording Unequipped indicates that the unit is
not foreseen.
HW Ver. Unit version.
Part Number. Part Number of the unit.
Par. Part Number. Part Number of the group that contains the unit. Usually the group
represents the equipment part that can be replaced. Not all the unit are into a group. In

this case the field will result empty and the part that can be replaced will correspond to
the unit itself.
Serial Number. Series Number of the group that contains the unit. If the unit is not con-
tained into a group (Par Part Num field empty), the Series Number refers to the unit.
Unit Alarms. Functional status of the unit. Each box identifies an alarm:
• Fail. The units is affected by a serious malfunctioning.
• Missing. The unit is not present into the equipment (Unequipped wording -
Real Type parameter) also if it is foreseen (unit name - Expected Type param-
eter).
• Not Resp. The unit does not answer to the program interrogations.
• HW Mism. The real unit (Real Type parameter) is different from the foreseen
one (Expected Type parameter).
• SW Mism. The software/firmware version present into the controller of the pe-
ripheral unit (Actual Release) is different from the one of the memory bench
in Running status (Release Bench) (see Verify the software/firmware version
of the equipment).
The colour of the boxes represents the alarm status and severity:
• Red, Orange, Yellow, Light blue. Alarm activated coupled respectively with the
Critical, Major, Minor, Warning severity.
• Green. Alarm activated coupled with the Status severity.
• White. Alarm deactivated.

Performance Monitoring
WARNING Command meaningful only with at least one Radio Link defined.
The Performance Monitoring command manages the Performance Monitoring measures.
Operations
Verify the status, the results and the threshold exceeding alarms of a PM measure
Activate one or more PM measures
Deactivate one or more PM measures
Reset the threshold exceeding alarms of one or more PM measures
Reset the values of the records daily and primary of one or more PM measures
Set the thresholds of the control parameters and alarms of a PM measure
GUI
Performance Monitoring context
See also
PM measures available
PM measures (info)
1. Select Main > Performance Monitoring.

2. Press Open new performance window.
The Performances [none selected] window displays the PM measures.
The measures are subdivided in groups.
The group and the relevant measures (group > measure) available are the following:
G828 ><transceiver>, checks the quality of the received signal at radio side.
RxPwr ><transceiver>, checks the power of the signal at reception.
TxPwr ><transceiver>, checks the power of the signal at transmission.
ACM > <Radio Link name> (<transceiver>), traces the trend of the ACM profiles in the time.
3. Select the group that contains the measure and than the wished measure.
For every measure is pointed out the status:
• (Stop.). The measure is not on progress.
• (Run.). The measure is on progress.
Below the measure, more options are pointed out: seconds, blocks, Rlts, etc. depending on the type of
selected measure.
Every option indicates the measurement unit of the control parameters for which you wish to display
the results and the threshold exceeding alarms.
This subdivision is necessary because the results of the control parameters cannot be graphically dis-
played by means of different measurement units.
4. Select the wished measuring unit.

The Performances [group / measure / measurement unit] window displays the results of the control
parameters, in graphic and table format, and the status of the threshold exceeding alarms.
If the measurement has never been activated, the window will result empty.
The items in the Performances window are described in Fig.3.
It is possible to open more Performances... window pressing again Open new performance window
or pressing Open New Window present in the Performances.... window itself.

3. To activate:
• All measures in a group, select the group.
• Single measure, select the group that contains the measure and than the wished measure.
4. Press Start and confirm.

The not active measure(s) are started and their status passes from (Stop.) to (Run.).
3. To deactivate:
4. Press Stop and confirm.

The active measure(s) are stopped and their status passes from (Run.) to (Stop.).

3. To reset the threshold exceeding alarms of:

4. Press Clear Alarms and confirm.

For the selected measure, active alarms are deactivated except for the unavailability alarms.
3. To reset the values of the records daily and primary of:

4. Press Clear Counters and confirm.

The values displayed into table are reset.

3. Select the group, the measure and the wished measurement unit (for example G828 > TRX A > Sec-
onds).
4. Press Commons.
If G828 ><transceiver> measure is selected, the Commons window displays the following parameters:
• General area. Threshold levels of the UAS parameter:
• N Ses Set UAS(P) (sec.). Threshold (expressed as number of consecutive seconds with
SES) over which starts the UAS unavailability period.
To change the parameter set a value between 1 and 10 sec (default 10), press Apply
and confirm.
• N Ses Reset UAS(Q) (sec.). Threshold (expressed as number of consecutive seconds
without SES) over which ends the UAS unavailability period.
To change the parameter set a value between 1 and 10 sec (default 10), press Apply
and confirm.
The threshold (expressed as percentage of the errored blocks) over which it is declared a SES
is 30% and is not changeable.
Press to compress the area. Press to expand the area.
• 15M Es Threshold (sec.). Threshold (expressed as number of seconds, within a 15 minute peri-
od, when ES has occurred) over which it is activated the alarm 15M ES.
To change the parameter set a value between 1 and 900 (default 0), press Apply and confirm.
The value 0 represents the deactivation of the threshold and accordingly of the alarm.
• 24H Es Threshold (sec.). Threshold (expressed as number of seconds, within a 24 hour period,
when ES has occurred) over which it is activated the alarm 24H ES.
To change the parameter set a value between 1 and 86400 (default 0), press Apply and con-
firm. The value 0 represents the deactivation of the threshold and accordingly of the alarm.
• 15M Ses Threshold (sec.). Threshold (expressed as number of seconds, within a 15 minute pe-
riod, when SES has occurred) over which it is activated the alarm 15M SES.
• 24H Ses Threshold (sec.). Threshold (expressed as number of seconds, within a 24 hour period,
when SES has occurred) over which it is activated the alarm 24H SES.
• 15M Sep Threshold (events). Threshold (expressed as number of SEP events within a 15 minute
period) over which it is activated the alarm 15M SEP.
• 24H Sep Threshold (events). Threshold (expressed as number of SEP events within a 24 hour
period) over which it is activated the alarm 24H SEP.
If RxPwr ><transceiver> measure is selected, the Commons window displays the following parame-
ters:
• 15M Rlts Thresholds area. 15M Rlts alarms threshold:
• Rlts 1 (sec.), Rlts 2 (sec.), Rlts 3 (sec.), Rlts 4 (sec.), Rlts 5 (sec.). Threshold levels (ex-
pressed as number of seconds, within a 15 minute period, when the received power is
lower than the RLT1, RLT2, RLT3, RLT4, RLT5 threshold levels) over which the system
activates the relevant alarms.
To change a threshold, set into the relevant box, a number between 1 and 900 (default
0), press Apply and confirm. The value 0 represents the deactivation of the threshold
and accordingly of the alarm.

• 24H Rlts Thresholds area. 24H Rlts alarms threshold:
• Rlts 1 (sec.), Rlts 2 (sec.), Rlts 3 (sec.), Rlts 4 (sec.), Rlts 5 (sec.). Threshold levels (ex-
pressed as number of seconds, within a 24 hour period, when the received power is lower
than the RLT1, RLT2, RLT3, RLT4, RLT5 threshold levels) over which the system activates
the relevant alarms.
• Rlt Thresholds area. Threshold levels of the received power:
• Rlt 1 (dBm), Rlt 2 (dBm), Rlt 3 (dBm), Rlt 4 (dBm), Rlt 5 (dBm). Respectively the first,
the second, the third, the fourth and the fifth threshold level of the received power.
To change a threshold, set into the relevant box, a number between -100dBm and -
20dBm.
Press to compress an area. Press to expand the area.
If TxPwr ><transceiver> measure is selected, the Commons window displays the following parameters:
• 15M Tlts Thresholds area. 15M Tlts alarms threshold:
• Tlts 1 (sec.), Tlts 2 (sec.), Tlts 3 (sec.), Tlts 4 (sec.). Threshold levels (expressed as num-
ber of seconds, within a 15 minute period, when the transmitted power is higher than the
TLT1, TLT2, TLT3, TLT4 threshold levels) over which the system activates the relevant
alarms.
• 24H Tlts Thresholds area. 24H Tlts alarms threshold:
• Tlts 1 (sec.), Tlts 2 (sec.), Tlts 3 (sec.), Tlts 4 (sec.). Threshold levels (expressed as num-
ber of seconds, within a 24 hour period, when the transmitted power is higher than the
TLT1, TLT2, TLT3, TLT4 threshold levels) over which the system activates the relevant
alarms.
• Tlt Thresholds area. Threshold levels of the transmitted power:
• Tlt 1 (dBm), Tlt 2 (dBm), Tlt 3 (dBm), Tlt 4 (dBm). Respectively the first, the second, the
third and the fourth threshold level of the transmitted power.
To change a threshold, set into the relevant box, a number between -40dBm and 35dBm,
press Apply and confirm.
If ACM > <Radio Link name> (<transceiver>) measure is selected, the Commons window displays the
following parameters:
• 15M Thresholds area. Alarms threshold:
• 15M <modulation> Threshold. Threshold - expressed as number of seconds, within a 15
minute period, when the counter <modulation> has increased - over which it is activated
the alarm.
To change a threshold, set into the relevant box, a number between 1 and 900 (default 0), press
Apply and confirm. The value 0 represents the deactivation of the threshold and accordingly of
the alarm.
• 24H Thresholds area. Alarms threshold:
• 24H <modulation> Threshold. Threshold - expressed as number of seconds, within a 24
hour period, when the counter <modulation> has increased - over which it is activated
the alarm.
To change a threshold, set into the relevant box, a number between 1 and 86400 (default 0),
press Apply and confirm. The value 0 represents the deactivation of the threshold and accord-
ingly of the alarm.
<modulation> = 4QAMS, 4QAM, 16QAMS, 16QAM, 32QAM, 64QAM, 128QAM, 256QAM, 512QAM,
1024QAM, 2048QAM or 4096QAM.

WARNING Context available only with at least one Radio Link defined.
The context manage the PM measures.
Buttons
Open new performance window. Open the Performances window which allows:
Manage the PM measures (activation, deactivation, threshold setting).
Display the activation status of the PM measures
Display the results of the measures in graphic and table format.
Display the status of the threshold exceeding alarms.
It is possible to open more Performances... window pressing again Open new performance
window or pressing Open New Window present in the Performances.... window itself.
See also
Performance Monitoring (command)
PM measures (info)

Performances window
Fig.3 displays the elements of the Performances window.
Fig.3 Performances window
3 4 6
(1) Title bar. When the window is opened, the title bar displays Performances [none selected].
When you select an option which allows displaying the results of a measure ( see note 3), Perfor-
mances [Selected group / Selected measure / Selected measurement unit] will be displayed, for
example Performances [G828 / TRX A / seconds].
Buttons
. Compress the window.
. Expand the window.
. Expand the window to the size of the Browser page.
. Restore the original size of the window.
. Close the window.
(2) Buttons bar:

Start. Activate one or more PM measures.
Stop. Deactivate one or more PM measures.
Clear Alarms. Reset the threshold exceeding alarms of one or more PM measures.
Clear Counters. Reset the values of the records daily and primary of one or more PM measures
stored into the equipment and displayed into the window.
Refresh. Update the data.
Commons. Set the thresholds of the control parameters and alarms of a PM measure. Button
meaningful only if one group is selected.
Open New Window. Open a new Performances window.

The buttons Start, Stop, Clear Alarms and Clear Counters, if a group is selected, execute their
action for all the measures present in the group. Otherwise, if one measure or one option below the
measure is selected, they execute their action only for the selected measure.
(3) List of the PM measures. The measures are subdivided in groups.

Selecting a group, the list of the measures associated to the group can be expanded.
Selecting one measure, the options pointing out the measurement units of the parameters associ-
ated to the measure are displayed. This subdivision is necessary because it is not possible to graph-
ically represent the results of the control parameters by means of different measurement units.
Selecting one measurement unit in the right part of the window (see note 4), the result of the con-
trol parameters and the threshold exceeding alarms are displayed. If the measure has never been
activated, the graph and the table will be empty.
The symbol:
identifies an expanded group or measure.
identifies a compressed group or measure.
identifies a measuring unit.
To every measure, the status is displayed:

(Stop.). The measure is not on progress.
(Run.). The measure is on progress.
The group and the relevant measures (group > measure) available are the following:
G828 ><transceiver> measure, checks the quality of the received signal at radio side.
The results of the control parameters are shown subdivided into the following measuring units:
• seconds. Seconds: ES, SES, SEP, UAS.
• blocks. Blocks: BBE.
RxPwr ><transceiver> measure, checks the power of the signal at reception.
• Rlts. Seconds: Rlts1, Rlts2, Rlts3, Rlts4, Rlts5.
• TM. dBm: TMMax, TMMin, Average Lev.
TxPwr ><transceiver> measure, checks the power of the signal at transmission.
• Tlts. Seconds: Tlts1, Tlts2, Tlts3, Tlts4.
• TM. dBm: TMMax, TMMin, Average Lev.
ACM > <Radio Link name> (<transceiver>) measure, traces the trend of the ACM profiles in the
time.
The results of the control parameters are shown subdivided into the following counters:
• seconds. Counters relevant to the ACM profiles.
• UpDownShift. Counters Unavailable, DownShift and UpShift.
Press to hide the list of measures. Press to display the list again.
(4) Graphical representation of the measure results. This area displays, in graphical format, the
results of the control parameters of the selected measure/measurement unit.
Every bar represents the result of the measure of one parameter in a given observation period (daily
or primary record).
The position of the bar on the x-axis indicates the daily or primary record which it is referred to:
• C.D. Current daily record (24 hours). The X100 suffix indicates that the value must be mul-
tiplied by 100 to obtain the real measured value.
• L. D. Preceding daily record. The displayed value must be multiplied by 100 to obtain the
real measured value.
• Curr. 15 Min. Current primary record (15 minutes).
• 15 Min. ÷ 4 Hours. 16 preceding primary records (each record is of 15 minutes).
Moreover, for every record the relevant status is displayed: (ML), (MF), (IN), (LO), (RE). The de-
scription of every single status is reported in the following note. If the status indication is not pre-
sent, the record is not available, because the measure was not active during the considered
observation period.

The colour of the bar indicates the control parameter that corresponds to the value. The key of the
parameters and their colours is always pointed out above the graph. The displayed control param-
eters changes according to the selected measure/measuring unit (see note 3).
The position on the y-axis indicates the value achieved by the parameter during the specific obser-
vation period (record). The measurement unit on the y-axis changes depending on the type of pa-
rameter represented in the graph. Moreover the y-scale dynamically changes depending on the
entity of the represented values.
The results relevant to a given parameter can be hidden selecting the parameter label located in
the top part of the area (for example ). To display the parameter results again, select the
label again.
(5) Table representation of the measure results. This area displays, in table format, the results of
the control parameters of the selected measure/measurement unit.
For every parameter, the result of the measure is pointed out relevant to a given observation period
(daily or primary record):
• Type. According to the selected measure this field indicates:
• G828, RxPwr and TxPwr measures: Control parameters (see PM measures availa-
ble).
• ACM measure: Counters. One counter is foreseen for every ACM profile (see PM
measures available).
For every counter, the column of the specific observation period indicates (expressed
in seconds) the number of times the counter is increased. Besides one counter per
modulation, the following counters are foreseen:
• Unavailable. Number of seconds, within the specific observation period, for
which the count has not been possible because the current ACM profile was
not connected to the radio.
• DownShift. Number of times the profile, during the specific observation period,
has changed assuming a profile lower than the previous one.
• UpShift. Number of times the profile, during the specific observation period,
has changed assuming a profile higher than the previous one.
Into the table, the system does not point out the results relevant to all the counters. Such
results have been subdivided according to the selected measure/measuring unit (see note
3).
• Curr. Day. Current daily record (24 hours).
• Last Day. Preceding daily record.
• Curr. 15 Min. Current primary record (15 minutes).
• 15 Min. ÷ 4 Hours. 16 preceding primary records (each record is of 15 minutes).
What just said is valid from the second row of the table on, because the first row indicates the status
of the records (Count. Status):
• Meaningless (ML) (green). The record has been completely acquired and the measure is not
affected by errors.
• Meaningful (MF) (green). The record has been completely acquired and it detected some per-
formance errors.
If one or more alarms are active (see note 6) means that the counter(s) have exceeded their
threshold value.
• Incomplete (IN) (yellow). The record has not been completely acquired during the corre-
sponding observation period.
The measure starting record is always in this status. The daily record gets this status also
when only one primary record of the corresponding day is in incomplete status.
The daily record of the current date will be always an incomplete one because the daily re-
cords are acquired at 23.59 of each day.
• Lost (LO) (red). The record has not reached the main controller of the equipment for instance
because the corresponding peripheral card has been physically extracted before it could have
forwarded the record itself or for generic hardware/software troubles.
• Restarted (RE) (red). The record has been lost after a reset of the equipment.
When the equipment has a software restart and checks that the measure is activated for a
certain measure point, all the record coupled with such a measure point will result in this
status.

• ---. The record is not an available one because, during the observation period under exam-
ination, the measure was not activated.
(6) Status of the threshold exceeding alarms and configuration parameters. These fields change
according to the selected measure:
G828 measures
• 15M <control parameter>. Threshold exceeding alarm of the specific control parameter
into one of the primary observation periods (15 minutes) present into the window.
• 24H <control parameter>. Threshold exceeding alarm of the specific control parameter
into one of the daily observation periods (24 hours) present into the window.
• UAS. Unavailability alarm.
RxPwr measure
• Rlt Thresh. Threshold levels of the received power actually set. These parameters can
be configured by the user.
TxPwr measure
• Tlt Thresh. Threshold levels of the transmitted power actually set. These parameters
can be configured by the user.
ACM measure
• 15M <counter>. Threshold exceeding alarm of the specific counter into one of the pri-
mary observation periods (15 minutes) present into the window.
• 24H <counter>. Threshold exceeding alarm of the specific counter into one of the daily
observation periods (24 hours) present into the window.
The colour of the alarm boxes represents the alarm status and severity:
• Red, Orange, Yellow, Light blue. Alarm activated coupled respectively with the Critical,
Major, Minor, Warning severity.
• Grey. Alarm deactivated.

G828 ><transceiver>
RxPwr ><transceiver>
TxPwr ><transceiver>
ACM > <Radio Link name> (<transceiver>)
G828 ><transceiver>
WARNING Measure available only if defined at least one Radio Link.

The availability of the measures depends on the types of Radio Link configured for the equipment.
The G828 > <transceiver> measure checks the quality of the received signal at radio side.
The check consists of measuring the following quality parameters:
BBE (Background Block Error). Number of blocks where it has been detected at least one er-
rored bit not belonging to SES.
ES (Errored Second). The second when there have been one or more errored blocks.
SES (Severely Errored Second). The second when there have been a percentage of errored
blocks > 30% or the second when it has been activated an alarm equivalent to the interruption
of the signal at reception.
SEP (Severely Errored Period). Number of periods with a number of consecutive SES comprised
between 3 and 9. The sequence is ended by a second without SES.
UAS (UnAvailable Seconds). Number of unavailability seconds. The counting of the seconds
starts after P consecutive seconds with SES presence and it ends at the beginning of a period of
Q consecutive seconds without SES. The P seconds are counted into the unavailability period.
The Q and P values can be configured.
The BBE, ES, SES, UAS parameters are implemented according to G.829 ITU-T Recom. The SEP parameter
is implemented according to G.828 ITU-T Recom.
RxPwr ><transceiver>

The RxPwr > <transceiver> measure checks the power of signal at reception.
TMMax (Tide Mark Max). Maximum value reached by the power at reception (RL) during the
observation period (15 min or 24 hours).
TMMin (Tide Mark Min). Minimum value reached by the power at reception (RL) during the ob-
servation period (15 min or 24 hours).
Average Level. Average level of the power at reception (RL) during the observation period (15
min or 24 hours).
Rlts (Received Level Threshold Second). Number of seconds where it has been detected that
the value of the power at reception (RL - Received Level) is lower than the pre-defined threshold
level. It is possible to define up to a maximum of 5 threshold levels.
The parameters are implemented according to Standard EN 301 129 of the ETSI.
TxPwr ><transceiver>


The TxPwr > <transceiver> measure checks the power of signal at transmission.
TMMax (Tide Mark Max). Maximum value reached by the power at transmission (TL) during the
TMMin (Tide Mark Min). Minimum value reached by the power at transmission (TL) during the
Average Level. Average level of the power at transmission (TL) during the observation period
(15 min or 24 hours)
Tlts (Transmitted Level Threshold Second). Number of seconds where it has been detected that
the value of the power at transmission (TL - Transmitted Level) is higher than the pre-defined
threshold level. It is possible to define up to a maximum of 4 threshold levels.
The parameters are implemented according to Standard EN 301 129 of the ETSI.
ACM > <Radio Link name> (<transceiver>)
WARNING Measure available and meaningful if the adaptive modulation is active.

The ACM > <Radio Link name> (<transceiver>) traces the trend of the ACM profiles (receiver) in the time.
The trend is traced using one counter for each ACM profile and further counters (Unavailable, UpShift and
DownShift):
4QAM Str. Number of seconds, within the specific observation period, during which the profile
ACM 4QAM Str has been active.
4QAM. Number of seconds, within the specific observation period, during which the profile ACM
4QAM has been active.
16QAM Str. Number of seconds, within the specific observation period, during which the profile
ACM 16QAM Str has been active.
16QAM. Number of seconds, within the specific observation period, during which the profile
ACM 16QAM has been active.
ACM 512QAM.
Unavailable. Number of seconds, within the specific observation period, during which the count
has not been possible because the current ACM profile was not connected to the radio.
DownShift. Number of times the ACM profile, during the specific observation period, has
changed assuming an ACM profile lower than the previous one.
UpShift. Number of times the ACM profile, during the specific observation period, has changed
assuming an ACM profile higher than the previous one.
WARNING The representation in graphical and table format of the counter results (see Fig.3) uses a counter
resolution with granularity of 1 second. If the modulation change has lasted for less than 1 second, it will
not be indicated by the modulation counters (4QAM Str, 4QAM, etc.) but by the counter DownShift or Up-
shift.

PM measures (info)
Performance Monitoring (PM) measure

A PM measure consists of recording, during a pre-defined time range (observation period), the
values of specific parameters.
Some threshold limits have been assigned to such control parameters (the setting of the thresh-
olds can be changed).
The exceeding of the threshold limit indicates a more or less serious degradation of the signal.
This condition generates an alarm.
Threshold exceeding alarm

The alarms relevant to the threshold exceeding are treated by the equipment and by the appli-
cation as normal alarms.
The only exception is that the alarm is not automatically reset at the return into the threshold
limit but the user has to execute the reset of this kind of alarms.
Control parameters
The control parameters under examination change according to the equipment type and to the
measure type supported by that type of equipment.
Usually, all the executed measures refer to ITU-T Recommendations (eg. G.828, etc.).
PM activation/deactivation
The activation (and the deactivation) of the PM measures can be executed by the user.
When it has been activated a PM measure, the equipment starts the storing of the values rele-
vant to the control parameters.
The results of the measures are sub-divided into records.
Each record contains the values recorded into a specific time range (observation period).
If at the end of the observation period, the measure has not yet been deactivated the system
starts another observation period and so on until when the operator stops the measure.
Record
The equipment group the results of the PM measures into observation period of 15 minutes (pri-
mary records) and of 24 hours (daily records).
The observation periods can not be synchronized with the instant when the measure is activated
but such records refer, for the primary records, to the quarter of an hour (00.00, 00.15, 00.30,
etc.) and, for the daily records, to the time 00.00 UTC (Universal Time, Coordinated).
For instance, if a measure starts at 11.40, the first primary record will have as observation pe-
riod the time 11.4011.45 (corresponding to the time range 11.3011.45), while the first daily
record will have as observation period 11.4000.00.
When the user requires the display of the results of the PM measures, the daily and primary
records relevant to the running PM measures are displayed in the WEB LCT page of the equip-
ment.
For each type of measure, the equipment keeps stored the current records and also the last 16
primary records (corresponding to the last 4 hours) and the last daily one (corresponding to the
preceding day).
The preceding records are overwritten.
When the operator stops a measure, the system stores the uncompleted current record.
If the operator activates and deactivates the measure more times during the same observation
period, the system will store the record that contains the results of the last executed measure.
For instance if the measure has been activated at 9.02 and deactivated at 9.07, then it has been
newly activated at 9.09, the record relevant to the observation period 9.009.15 will contain
the results of the measures relevant to the period 9.099.15, while the ones relevant to the
period 9.029.07 will not be stored.

Equipment restart
If equipment has some PM measures on progress and it is re-started up or turned off, when it
will successively restarted or turned on the measures activated before the turning off will be au-
tomatically re-started.
The records (primary and daily), relevant to the period when measure has been stopped, will
result empty and when it has been reached the limit of 16 primary records and 1 daily one, they
will overwrite the preceding records.
See also
Performance Monitoring (command)
PM measures (info)

Report & Logger
The Report & Logger command manages the log of the equipment alarms, the log of the operations ex-
ecuted by the users and the equipment configuration.
With log of the equipment alarms we mean the list of the status and alarm signals currently active on the
equipment (current alarms) and the signals memorized in the equipment controller (alarm history).
With log of the operations we mean the list of the operations executed by all the users who can connect to
the equipment. The list is stored in the equipment controller.
Operations
Save the log of the equipment alarms
Delete the log of the equipment alarms
Save the log of the operations executed by the users
Delete the log of the operations executed by the users
Save the equipment configuration
GUI
Report & Logger context
See also
Save the log of the equipment alarms
1. Select Main > Report & Logger.

2. Press Alarm Log.
In the Alarm Log window are displayed:
• Equip. Info. General parameters:
• Equipment Type. Equipment type.
• Date. Date/time when it has been generated the report.
• Current Alarm Log and History Alarm Log. Respectively list of the current alarms and history
alarms. Every single record identifies an alarm with the following information:
• Severity. Alarm severity.
• Status. Alarm status.
• Warning, Minor, Major or Critical. Alarm respectively with the Warning, Minor, Ma-
jor or Critical severity.
• Status. Alarm status:
• On. Alarm active.
• Off. Alarm inactive (detected/cleared alarm). Meaningful only for alarm history.
• Date/Time. Detection or reset date and time of the alarm. The format of date/time
changes according to the setting made in the operating system.
• Description. Alphanumeric string that specify the type of the alarm.
3. Press Download Report.

The system saves the log to a file named AlarmLog_<year-month-day-hour-minute>.
The file is automatically saved in the Browser folder predefined for the downloads.
The format, used to save the data to file, is the same displayed in the Alarm Log window.

Delete the log of the equipment alarms
1. Select Main > Report & Logger
2. Press Reset Alarm Log and confirm.

A message indicates the end and the result of the operation.
Save the log of the operations executed by the users
2. Press Command Log.

In the Command Log window are displayed:
• Current Command Log. Operations list. Every record identifies an operation for which are re-
ported:
• Performer. Type of user who has performed the operation:
• web. User of WEB LCT application.
• snmp. User of the NMS5UX-B/NMS5LX supervision system (NMS5UX user - NMS
GUI, NMS5WI GUI).
• cli. User of SM-OS application, connected to the equipment via serial line.
• remoteCli. User of SM-OS application, connected to the equipment via telnet.
• Action. Action performed by the user.
• Instance. Name of the equipment instance to which the operation refers.
• Value Set. Set value.
• User. Name of the user who has executed the operation.
• Source Address. IP address of the machine from which it has been executed the opera-
tion.
• Date/Time. Date and time when it has been executed the operation. The format of date/
time changes according to the setting made in the operating system.
The empty box indicates that the information is not available, because not meaningful for the relevant
type of operation.

The system saves the log to a file named CommandLog_<year-month-day-hour-minute>.
The format, used to save the data to file, is the same displayed in the Command Log window.
Delete the log of the operations executed by the users
1. Select Main > Report & Logger
2. Press Reset Command Log and confirm.

A message indicates the end and the result of the operation.

Save the equipment configuration
2. Press Inventory Report.

In the Inventory Report window are displayed:
• MAC Address. Physical address of the equipment.
• Bridge Mode. Bridge modality of the Ethernet Switch (see Bridge Mode Conf. context).
• HW Inventory, SW Inventory, SW list, etc. Equipment parameters.
The whole equipment parameters are subdivided in groups.
The format of the parameters present in each group is self-explicative and changes according
to the type of represented data.

The system saves the log to a file named Inventory_<year-month-day-hour-minute>.
The format, used to save the data to file, is the same displayed in the Inventory Report window.

Report & Logger context
The context allows to save the log of the equipment alarms, the log of the operations executed by the users
and the equipment configuration.
Buttons
Apply. Not available in this context.
Reset Alarm Log. Delete the log of the equipment alarms

Reset Command Log. Delete the log of the operations executed by the users
Alarm Log. Save the log of the equipment alarms
Command Log. Save the log of the operations executed by the users
Inventory Report. Save the equipment configuration
See also
Report & Logger (command)

NMS Wake Up Config.
The NMS Wake Up Config. command manages the Wake Up trap (Wake Up functionality).
Operations
Verify the Wake Up functionality status
Set the execution parameters and activate the Wake Up functionality
Disable the Wake Up functionality
GUI
NMS Wake Up Config. context
See also
Wake Up functionality (info)
1. Select Main > NMS Wake Up Config.

The NMS Wake Up Config. context displays the sending status of the Wake Up trap and the current
setting of the relevant sending parameters.
WARNING The execution parameters (NMS IP Address, Timeout, etc.) cannot be modified when the Wake
Up functionality is already active. To modify them, it is necessary Disable the Wake Up functionality and
them modify them.
2. Set the IP address of the server, which the Wake Up trap must be sent to, in the NMS IP Address box.
3. Set the time interval, for which the Wake Up trap is sent at the end of which it is automatically disabled,
in the Timeout (Minutes) box.
Typing or selecting the arrows of the box, set a number between 0 and 1440 minutes.
The setting of the value 0 indicates that the trap is sent until when the user manually disables it or the
NMS server automatically disables it when intercepts it.
4. Set the physical location (for example, the name of the site) of the equipment in the NE Location box.
The setting of the parameter is optional.
5. Select the Enable option.
2. Select the Disable option or reset the value present in the NMS IP Address box (value 0.0.0.0).

The context displays the configuration parameters of the Wake Up functionality.
Parameter
Status. Transmission status of Wake Up trap. The sending of the Wake Up trap is:
• Active, when the Enable option is selected and a valid value (different from 0.0.0.0)
is set as IP address of the server (option NMS IP Address).
• Inactive, when the Disable option is selected and the value 0.0.0.0 is set as IP ad-
dress of the server (option NMS IP Address).
NMS IP Address. IP address of the server which the Wake Up trap must be sent to. With server
we mean the machine where the supervision system NMS5UX-B or NMS5LX or a different man-
agement system, able to manage the reception of the Wake Up trap, is installed.
Timeout (Minutes). Time interval for which the Wake Up trap, when enabled, is sent to the
server. The setting of the value 0 indicates that the trap is sent until when the user manually
disables it or the NMS server automatically disables it when intercepts it.
NE Location. Optional parameter. The user can insert the physical location (for example the
name of the site) of the equipment in this field. This information is communicated to the remote
manager together with the characteristics of the equipment. The supervision system NMS5UX-
B or NMS5LX does not use this information.
Buttons
See also
NMS Wake Up Config. (command)

Wake Up functionality
The Wake Up functionality allows the user enabling the spontaneous forward, from the equip-
ment to a remote server, of a SNMP trap for the notification of the equipment commissioning
(Wake Up trap).
This functionality has been implemented as help to the Auto Discovery modality available in the
supervision systems NMS5UX-B and NMS5LX.
The Auto Discovery mode has the purpose to point out new equipment in the network, not man-
aged by the supervision system yet.
More information about the Auto Discovery modality is reported in the supervision system doc-
umentation.
Here below only the management of the Wake Up trap by the equipment is described.
ALFOplus2
The user can configure, via WEB LCT, the parameters for the management of the Wake UP trap:
• IP address of the server where the supervision system, which the trap must be sent
to (NMS IP Address option) is installed.
• Time interval for which the trap must be sent, after which the sending of the trap is
automatically disabled (Timeout option).
If the value 0 is set for the Timeout option, the Wake Up trap will be sent until when
the user manually disables it or the NMS server automatically disables it when inter-
cepts it.
Then, the trap forwarding shall be activated.
To activate the Wake Up functionality, it is necessary to set a valid value (different from 0.0.0.0)
as IP address of the server (NMS IP Address option) and select the Enable option.
To deactivate the functionality, it is necessary to select the Disable option or reset the NMS IP
Address option (value 0.0.0.0).
When the Wake Up functionality is activated, the equipment starts sending the Wake Up trap
every minute for the time interval defined by the user (Timeout option).
For example, if the value 60 has been set as timeout, the trap is sent each 60 minutes. At the
end of 60 minutes, the sending of the trap is automatically disabled.
If, in the period when the sending of the trap is enabled, the supervision system intercepts the
Wake Up notification records the presence of the new equipment in its database and disables
the sending of the Wake Up trap by the equipment (trap switch-off).
See also
NMS Wake Up Config. (command)

Software Info & Maint.
The Software Info & Maint. command manages the equipment software/firmware and the restore of the
default equipment settings.
Operations
Verify the software/firmware version of the equipment
Update the software/firmware of the equipment
Switch the functioning of the memory benches relevant to the controller
Restore Factory Default of the equipment
GUI
Software Info & Maint context
See also
Equipment software/firmware (info)
Factory Default of the equipment (info)
Verify the software/firmware version of the equipment
1. Select Main > Software Info & Maint.

The Equipment Firmware tab shows version, status and composition of the equipment firmware and
the WEB LCT version present into the equipment.
Update the software/firmware of the equipment
configured for the FTP Server and the file for the update must be present into a sub-folder of
the Shared Folder set during the configuration of FTP Server (see FTP/SFTP protocol (info).
The application automatically updates the software/firmware of the memory bench not on progress or not
present (Bench Status parameter - Loaded or Not Loaded value).
This operation cannot be executed when the update is already in progress (Download Status parameter -
Downloading value).
The software/firmware update procedure could change the equipment functions.
1. Main > Software Info & Maint.

2. Press Upgrade.
3. In the box Download file path, type the path/name of the file you wish to use for update.

The file must be on the local PC (PC where the browser used for the display of WEB LCT is running).
4. Set, in the FTP Server IP Addr. box, the IP address of the FTP Server or the SSH Server (if not differently
set at the configuration of FTP Server, it corresponds to IP address of PC).
5. Set the download type to be executed, selecting the option:

• Forced, if you are updating the software/firmware of main controller of the equipment.
• Only difference or not present / peripheral, if you are updating the software/firmware of periph-
eral units (FPGA file and/or application code).
6. Activate the Bench Switch? box, if at the end of the download, the system has automatically to execute
a switching of the memory bench in such a way to use the bench with the software/firmware that has
been updated.
7. Press Start and confirm.

Before executing the updating, the system executes a compatibility check between the file to be for-
warded to the equipment and the one present on the terminal.
The check consists of comparing the technology type of the equipment.
If the parameters are incompatible, the application does not executes the update: the wording Inter-
rupted is displayed in the Download Status box of the bench whose software/firmware you are updat-
ing.
If the parameters are compatible, the operation is started and the Download Status box of the bench
whose software/firmware you are updating dynamically updates the progress of the operation, which
requires some minutes:
• Downloading. The operation is running.
The Abort button, present in the Download Status box during the software/firmware update,
can be used to stop the operation. Its selection requires the confirmation.
During the updating, the system deletes the software/firmware present into the bench memory
and it updates the software/firmware of the equipment one component at a time.
If the operation is stopped, into the memory bench there will be only the already updated com-
ponents. In this case, the new version can result unusable because it is not an integral one (the
bench will be in Not Loaded status).
In this case, the controller keeps the minimum functions necessary to allow a new updating of
the software/firmware.
• Complete. The update operation is ended.
The Software Version box shows the new software/firmware version.
Switch the functioning of the memory benches relevant to the controller
WARNING The operation is traffic affecting.

Memory benches cannot be switched during the software/firmware update (Download Status parameter -
Downloading value) and when the software/firmware of the equipment is not present on a bench (Bench
Status parameter - Not Loaded value).
2. Press Bench Switch and confirm.

The equipment is restarted; on the reconnection, the bench in Running status is forced to Loaded status
and vice versa.

Restore Factory Default of the equipment
WARNING The operation, if executed on equipment subjected to the radio supervision, could cause the loss
of the link because the restore of the factory settings involves the re-channelling of the radios to the default
values.
2. Select the Advanced tab.
3. Activate the Factory Default check-box.

A message signals that the new settings will be active after the software restart to perform with the
command present in this context.
5. Press OK to close the window.
6. Press Restart and confirm.

The default configuration will be automatically applied at the equipment restart (see Factory Default of
the equipment (info).
WARNING After the reset, all the values activated before the operation result as valid ones.
Operation is no traffic affecting.

2. Select the Advanced tab.

The context displays the equipment software/firmware.
Tabs
Equipment Firmware tab. Version and status of the equipment software/firmware.
Advanced tab. Factory default.
Buttons
See also
Software Info & Maint. (command)
Equipment Firmware tab
The tab shows the version, the status and the composition of the equipment software/firmware.
First table
The table displays the version and the status of the equipment software/firmware:
Software Version. File name and version of the equipment software/firmware respec-
tively present on the memory bench 1 (Bench 1 column) and 2 (Bench 2 column).
Bench Status. Functioning status of the memory bench 1 (Bench 1 column) and 2
(Bench 2 column):
• Running. It is on progress the software/firmware relevant to the subject mem-
ory bench.
• Loaded. The software/firmware is present into the bench but actually it is not
on progress (StandBy).
• Not Loaded. The software/firmware is not present into the memory bench.
Download Status. Status of the update operation of the software/firmware respectively
present on memory bench 1 (Bench 1 column) and 2 (Bench 2 column):
• ---. Update is not in progress.
• Downloading. It is on progress the updating relevant to the memory bench.
• Interrupted. The update has been interrupted.
• Complete. The update operation is ended.
Second table
The table displays the list of the codes and of the FPGA files that compose the equipment soft-
ware/firmware. Every row corresponds to a software/firmware element for which is pointed out
in the column:
Unit. Name of the unit or of the equipment part where there is the controller (code) or
the programmable device (FPGA file).
Software. Name which usually identifies the type of component:
• FW_Boot. Boot code. This part of code can not be updated in fact it is not pro-
vided with a version of the memory benches.
• FW_. Application code.
• Conf, Prog, Init or FPGA Configuration file of the programmable devices.
• WEB_LCT. WEB Local Craft Terminal application.
Actual Release. Version of the code or of the FPGA file present into the controller.
For some elements, the system shows the version and also the relevant identification
code composed by the letter E or N followed by a number (each number identifies a dif-
ferent code type).

Release Bench 1. Software/firmware version present into the memory bench 1 of the
controller.
Release Bench 2. Software/firmware version present into the memory bench 2 of the
controller.
Buttons
Upgrade. Update the software/firmware of the equipment.
Bench Switch. Switch the functioning of the memory benches relevant to the controller.
See also
Advanced tab
WARNING Tab available only to users with Administrator profile.
The tab displays the parameters to restore the factory default of the equipment.
Parameters
Factory default. Box to Restore Factory Default of the equipment.
Buttons
Restart. Execute the equipment software reset
See also

Equipment software/firmware
The software/firmware of the equipment is the assembly of all the firmware necessary for the
management of the entire equipment and WEB LCT application.
The software/firmware of the equipment is present into the main controller that is provided with
two memory benches (bench) the first one on service and the other one in waiting status.
Each bench can contain one software/firmware version (also different from the other one) of the
equipment.
Equipment software/firmware update

It is possible to update the software/firmware of the equipment, relevant to a memory bench,
at a time.
The application automatically updates the software/firmware of the memory bench not on pro-
gress or not present (Bench Status parameter - Loaded or Not Loaded value).
Traffic Affecting operation

Here below the impact of every equipment download/restart operation on the traffic is reported.
Operation Traffic
Restart software No traffic affecting
Bench Switch Traffic affecting
Power Off/On Traffic affecting
Download sw/fw No traffic affecting
See also

Factory Default
Through the WEB LCT application, the Factory Default settings of equipment can be restored
(see Restore Factory Default of the equipment).
At the restart or at the new switch-on of the equipment, the Factory Default configuration will
be applied.
All the settings executed until then by the user will be deleted (for example, user list, remote
equipment list, etc.).
Login to equipment after Factory Default

In order to login to the equipment, the default user must be used. Username: admin - Password:
admin.
The communication ports of the equipment will be restored to the addresses pointed out in
Tab.1.
These addresses differ depending on the type (High or Low) of ODU.
Tab.1 Factory Default
Parameter IP Address NetMask ODU
IP Address 172.20.254.14 255.255.0.0 Low

Agent IP Address
172.20.255.15 255.255.0.0 High
Default Gateway 255.255.255.255* - Low
255.255.255.255* - High
* Value equivalent to null.
See also

Backup/Restore Config.
The Backup/Restore Config. command manages the backup/restore from file of the whole equipment
configuration.
Operations
Save the whole equipment configuration (backup configuration)
Transfer the equipment configuration previously saved (restore configuration)
Retrieve the equipment configuration automatically saved by the program before the last oper-
ation of configuration restore (revert configuration)
GUI
Backup/Restore Config. context
See also
Backup/restore of the equipment configuration (info)
configured for the FTP Server (see FTP/SFTP protocol (info).
• Protocol SFTP. A SSH server is installed on one’s PC (see SSH protocol (info)).
1. Select Main > Backup/Restore Config.
set at the configuration of Server, it corresponds to IP address of PC).
Setting the address 0.0.0.0, the system automatically retrieves the IP address of the manager which
has made the request.
3. Type, in the Backup file name box, the path where you wish to save the file and the name of the file
with bak extension.
It is possible to set a name already existing for the file in the chosen path. In this case, the data present
in the file will be overwritten.
4. Press Backup and confirm.

A message displays the result of the operation.

WARNING This operation restores the equipment configuration saved to file, transferring the data of the
file to the same equipment (configuration restore) or, if the equipment is faulted, to the spare equipment
which will replace it.
If this procedure is used to copy a default configuration on more equipment, the correct operation of the
cloned equipment is not ensured.
Depending on the protocol set for the file transfer (see Ftp/Sftp context), check out that:
configured for the FTP Server and the file with the configuration must be present into a sub-
folder of the Shared Folder set during the configuration of FTP Server (see FTP/SFTP protocol
(info).
3. Set, in the Restore file name box, the name of the file you wish to use to restore the configuration.
4. If you wish to activate a previous software/firmware version (Release Downgrade procedure), it is nec-
essary to load on the equipment a configuration coherent with the previous software/firmware.
In order that the configuration is still compatible after the restore procedure, the option Bench switch
after restore has to be activated.
5. Press Restore and confirm.

At the end of the operation, the equipment is automatically restarted.
Retrieve the equipment configuration automatically saved by the program before the
last operation of configuration restore (revert configuration)
configured for the FTP Server (see FTP/SFTP protocol (info).

The Revert parameter shows the date/time of the backup file automatically created by the program
before the last restore operation.
The format of date/time changes according to the setting made in one’s operating system.
The wording --- shows that the file is not available.
3. Press Revert and confirm.

At the end of the operation, the equipment is automatically restarted.

The context displays the parameters to save and restore the whole equipment configuration.
Parameters
Backup file name. Path and name of the file which you wish to save the whole equipment con-
figuration to.
Restore file name. Path and name of the file which you wish to use for the restore of the pre-
viously saved configuration.
Bench switch after restore. Activate this option if you wish to return to the previous software/
firmware version during the configuration restore (Release Downgrade procedure).
FTP Server IP Addr. IP address of the FTP Server or of the SSH Server used for the file trans-
fer.
The address 0.0.0.0 indicates that the system automatically retrieves the IP address of the man-
ager which has made the request.
Revert. Date/time of the backup file automatically created by the program before the last re-
store operation.
The format of date/time changes according to the setting made in one’s operating system. The
wording --- shows that the file is not available.
Buttons
Backup. Save the whole equipment configuration (backup configuration)
Restore. Transfer the equipment configuration previously saved (restore configuration)
Revert. Retrieve the equipment configuration automatically saved by the program before the
last operation of configuration restore (revert configuration)
See also
Backup/Restore Config. (command)

Backup
The WEB LCT allows save the whole equipment configuration (backup configuration).
The saved file is in binary format and can be saved on PC or external support according to the
user needs.
Restore
In any moment, the user can restore the equipment configuration saved to file transferring the
data of the file to the same equipment (configuration restore) or, if the equipment is faulted, to
the spare equipment which will replace it.
Before restoring the configuration:
• The equipment saves its own current configuration and keeps it available until the suc-
cessive restore operation.
• It checks if the version of the equipment sw/fw used to generate the file and the hard-
ware type (Real Type - see Equipment Units tab), which the file refers to, match those
of the equipment where you are performing the restore operation.
Restore - Release Downgrade

During the procedure of configuration restore, it is possible to return back to the previous soft-
ware/firmware version present on the memory bank in status Loaded at the moment of the
backup.
In this case, in order that the configuration is still compatible after the restore operation, it is
necessary to activate the option Bench switch after restore.
Before restoring the configuration, the equipment compares the version of the equipment sw/
fw and unit type present in the file with that present in the Standby bench.
Revert
In any moment, the user can retrieve the equipment configuration automatically saved by the
program before the last operation of configuration restore (revert configuration).
In this way, two backup versions will be always available for equipment: one executed by the
user and the other automatically executed by the program before the last restore operation.
See also
Backup/Restore Config. (command)
Retrieve the equipment configuration automatically saved by the program before the last oper-
ation of configuration restore (revert configuration)

Alarm Severity Config.
The Alarm Severity Config. command manages the alarm transmission and their severity.
Operations
Verify the severity and the enabling/forwarding status of the alarms
Enable/disable an alarm
Enable/disable the forwarding of the trap of an alarm
Change the severity of an alarm
GUI
Alarm Severity Config. context
See also
Verify the severity and the enabling/forwarding status of the alarms
1. Select Main > Alarm Severity Config.

The Alarm Severity Config. context displays the alarms configuration.
Enable/disable an alarm
2. Select the alarm and press Edit Alarm Config or double click on the alarm.
3. Set the Severity parameter, selecting:
• Disable, to disable the alarm.
• Status, Warning, Minor, Major or Critical to enable the alarm. Select the option relevant to the
severity to be assigned to the alarm
4. Press Ok.
The settings are reported in the Alarm Severity Config. context. The symbol [*] is displayed next to the
name of the changed alarm.
Enable/disable the forwarding of the trap of an alarm
WARNING It is possible to change the forwarding status of the trap only if it has been enabled the alarm
(see Enable/disable an alarm).

3. Set the Trap parameter, selecting:
• Enable, to enable the forwarding of the alarm trap to the management system.
• Disable, to disable the forwarding of the alarm trap to a possible management system external
to the equipment (for exampleNMS5UX-B/NMS5LX).
4. Press Ok.
Change the severity of an alarm
3. Set the Severity parameter, selecting the severity you wish to associate to the alarm: Status, Warning,
Minor, Major or Critical.
If the alarm was disabled (Disable option selected), the selection of a different option, besides modify-
ing the alarm severity, automatically enables it.
4. Press Ok.

The context displays the alarms configuration.
Table
Each row of the table corresponds to a group or alarm.
Alarms are subdivided into groups. The groups and the alarms change according to the equip-
ment configuration.
When context is opened in the table, only the groups are displayed (Group/Alarm column).
To expand and compress the list of alarms associated to a group, select the symbol next to
the name of the group. Every selection of the symbol makes the list assumes the status com-
plementary to the previous one (if compress it is expanded and vice versa).
When a group is expanded, for every alarm is displayed the following characteristics:
Group/Alarm. Alarm name.
A colour box is before the name, pointing out the alarm status and severity:
• White box with red X. Alarm disabled.
• Green box. Alarm enabled with severity equivalent to a status signal.
• Light blue box. Alarm enabled with Warning severity.
• Yellow box. Alarm enabled with Minor severity.
• Orange box. Alarm enabled with Major severity.
• Red box. Alarm enabled with Critical severity.
• The presence of an asterisk [*] between the box and the alarm name shows
that at least one characteristic of the alarm has been changed.
Severity. Enabling status of the alarm and, if it is enabled, the relevant severity:
• Disabled. Alarm disabled.
• Status. Alarm enabled with severity equivalent to a status signal.
• Warning, Minor, Major or Critical. Alarm enabled with severity respectively
Warning, Minor, Major or Critical.
• Not available in this SW version. Alarm not supported by the current firmware
version present into the equipment controller.
Trap Notification. Forwarding status of the trap:
• Enabled. The transmission of the alarm trap to the management system is en-
abled.
• Disabled. The transmission of the alarm trap to a possible external manage-
ment system is disabled (for exampleNMS5UX-B/NMS5LX).
• ---. Information not meaningful because the alarm is disabled.
Buttons
Edit Alarm Config. Enable/disable an alarm, Enable/disable the forwarding of the trap of an
alarm or Change the severity of an alarm
See also
Alarm Severity Config. (command)

Alarms, Status signal and Events

The term alarm defines the fault signal generated by an error or malfunction of the equipment
or of any component that composes it.
The signals referring to any event that does not indicates a malfunction but a status change, an
operation in progress or an operating indication are defined status signals.
The term event defines every signal of status, detected alarm and cleared alarm.
A maximum of 500 events are recorded in the equipment controller. When this limit is exceeded,
each new event will overwrite the oldest event.
Displaying alarms
The list of the current alarms is indicates in the Equipment status area.
Enabling/disabling alarms
The equipment alarms can be disabled and re-enabled by the user according to the needs.
Disabling an alarm means that, on the detection of the alarm itself, this is not registered in the
equipment controller and, as consequence, is not communicated to a possible management pro-
gram: as the alarm had never occurred.
On the contrary, enabling an alarm (default condition) means that, when the alarm is detected,
this is registered in the equipment controller and, if the forwarding of the relevant trap is ena-
bled (see next item), the alarm is communicated to the management system and displayed in
the current alarms and the history alarms.
WARNING The enabling/disabling of the alarm is independent for each alarm and local to the
equipment which the operation is executed for. This means that the setting must be executed
for each alarm of each equipment.
Enabling/disabling traps
The trap is a message (in this case of detection or clearing of an alarm) spontaneously sent by
the equipment to a possible external management system, for exampleNMS5UX-B/NMS5LX.
The forwarding of the trap of each alarm can be disabled and re-enabled by the user according
to his own needs.
Disabling a trap means that, on the detection of the alarm, this is not registered in the equip-
ment controller and, as consequence, is not communicated to a possible management program.
On the contrary, enabling a trap (default condition) means that, on the detection of the alarm,
this is registered in the equipment controller and communicated to the management system,
which displays it in the current alarms and the history alarms.
WARNING The enabling/disabling of the forwarding of the trap is independent for each alarm
and local to the equipment which the operation is executed for. This means that the setting must
be executed for each alarm of each equipment.
Alarm severity
Each alarm acknowledged and managed by the local management program has an associated
severity which determinates the importance of the alarm.
This severity is not fixed, but can be changed by the user as he likes.
Alarms log
With log of the equipment alarms we mean the list of the status and alarm signals currently ac-
tive on the equipment (current alarms) and the signals memorized in the equipment controller
(alarm history).
WEB LCT allows to Save the log of the equipment alarms and to Delete the log of the equipment
alarms.
See also
Alarm Severity Config. (command)

Group/User Management
Groups. It manages the user groups.

Users. It manages the users (users list of the equipment).
Permanent Login. It manages the IP address of Permanent Login.
Logged Users. It manages the users connected to equipment.

Groups
The Groups command manages the user groups of the equipment.
Operations
Verify the user groups
Add a user group
Modify a user group
Delete a user group
GUI
Groups context
See also
HTTP/HTTPS protocol (info)
SNMP protocol (info)
FTP/SFTP protocol (info)
SSH protocol (info)
Verify the user groups
1. Select Main > Group/User Management > Groups.

The Groups context displays the list of the user groups currently stored in the equipment.
Add a user group
WARNING It is possible to set a maximum of 10 groups (see Limits).

If the equipment is managed even by NMS5UX-B/NMS5LX supervision system, it is necessary to create the
user used by the supervision system for the connection to the equipment (NMS GUI, NMS5WI GUI). This
user must be associated to a group with profile Administrator and all the protocols enabled.
2. Press Add Group.
3. Into the Name box, type the group name (alphanumeric string with a number of characters from 4 up
to 31, the accepted and recognized characters are 0÷9, a÷z and A÷Z).
The parameter is Case Sensitive; pay attention to uppercase and lowercase characters.
It is not possible to assign the same name to two different groups present into the same list.
The parameter can not be changed later.
4. Set the profile you wish to assign to the user who will belong to the group in the Profile box:
• Administrator. The user with this profile can both verify the parameters and send commands or
change the equipment configuration with no exception.
Moreover, every user belonging to a group with profile Administrator, besides being a WEB user,
is even a CLI user because a user with profile Administrator is automatically enabled by the sys-
tem to access to the equipment even by the application SM-OS (Siae Microelettronica - Operat-
ing System).

• Read/Write. The user with this profile can as check the parameters as send commands or exe-
cute changes to the equipment configuration except for the following operations: modifying the
user list, aligning the date/time of the equipment, force the logout of a user and all those oper-
ations available only to the Admin. user.
• Maintenance. The user with this profile can check the parameters and execute only maintenance
operations (MAN. OP) in the Manual Operations context and Radio BER context.
• Read Only. The user with this profile can only check the parameters.
5. Define the protocols/interfaces available to the users associated to the group (Allowed Protocols pa-
rameter):
• HTTP. HyperText Transfer Protocol. Protocol used to transfer hypertext pages on the WEB.
• HTTPS. HyperText Transfer Protocol over SSL. It is a variation of HTTP protocol and uses, be-
sides TCP/IP protocol, SSL layer (Secure Sockets Layer) which implements the encryption and
the authentication of the transmitted data.
• SNMP. Simple Network Management Protocol. Protocol which allows monitoring and controlling
the network devices.
If you activate this protocol, select the relevant version:
• SNMPv1. First version.
• SNMPv2c. Second version.
• SNMPv3. Third version.
• FTP. File Transfer Protocol. Protocol for the file transfer.
• SFTP. SSH File Transfer Protocol. Protocol for the secure file transfer.
• SSH. Secure SHell. Protocol for the secure and encrypted access.
The active box ( ) indicates that the protocol will be available for the WEB LCT session opened by the
users of the group; the inactive box indicates that the protocol will not be available.
At least one protocol must be activated.
6. Press OK and confirm.

The new group is inserted in the list and communicated to the equipment.
Modify a user group
WARNING The Name and CLI parameter cannot be modified.

A group with at least one associated user cannot be modified. First delete the users and then modify the
group.
2. To modify the profile of the users associated to a group, select the relevant Profile box and then the
option:
• Administrator. The user with this profile can both verify the parameters and send commands or
change the equipment configuration with no exception.
• Read/Write. The user with this profile can as check the parameters as send commands or exe-
cute changes to the equipment configuration except for the following operations: modifying the
user list, aligning the date/time of the equipment, force the logout of a user and all those oper-
ations available only to the Admin. user.
• Maintenance. The user with this profile can check the parameters and execute only maintenance
operations (MAN. OP) in the Manual Operations context and Radio BER context.
The parameter of the last group with profile Administrator cannot be modified.
Pressing Revert changes cancels all the changes executed.
3. To change the protocols/interfaces available to the users associated to a group, select the relevant box:
• HTTP. Protocol HTTP (HyperText Transfer Protocol).
The active box ( ) indicates that the protocol will be available for the WEB LCT session opened
by the users of the group; the inactive box indicates that the protocol will not be available.

• HTTPS. Protocol HTTPS (HyperText Transfer Protocol over SSL).
• SNMP. SNMP protocol. Select the option:
• Disabled. Protocol SNMP disabled.
• SNMPv1. Protocol SNMPv1 enabled.
• SNMPv2c. Protocol SNMPv2c enabled.
• SNMPv3. Protocol SNMPv3 enabled.
• FTP. Protocol FTP (File Transfer Protocol): protocol for the file transfer based on TCP.
• SFTP. SSH File Transfer Protocol: protocol for the secure file transfer.
• SSH. Secure SHell: protocol for the secure and encrypted access.
At least one protocol must be active.
4. Press Apply changes and confirm.
Delete a user group
WARNING A group with at least one associated user cannot be deleted. First delete the users and then the
group.
This operation is not available if the default group Admin is selected.
2. Select the group.

3. Press Remove Group and confirm.

Groups context
The context displays the list of the users groups of the equipment.
Table
Every row of the table corresponds to a group for which are indicated:
Name. Group name
Profile. Profile of the users associated to the group:
• Administrator. The user with this profile can both verify the parameters and
send commands or change the equipment configuration with no exception.
• Read/Write. The user with this profile can as check the parameters as send
commands or execute changes to the equipment configuration except for the
following operations: modifying the user list, aligning the date/time of the
equipment, force the logout of a user and all those operations available only
to the Admin. user.
• Maintenance. The user with this profile can check the parameters and execute
only maintenance operations (MAN. OP) in the Manual Operations context and
Radio BER context.
CLI. Permission of the user to access to the equipment even by the application SM-OS
(Siae Microelettronica - Operating System).
The active box ( ) indicates that the WEB user is even a CLI user, the inactive box in-
dicates that the WEB user is not a CLI User too.
The parameter is read-only because the setting is automatically made by system, accord-
ing to the profile defined during the group creation: only the users belonging to groups
with profile Admin have the functionality CLI enabled.
HTTP. Protocol HTTP (HyperText Transfer Protocol): protocol used to transfer hypertext
pages on the WEB.
The active box ( ) indicates that the protocol will be available for the WEB LCT session
opened by the users of the group; the inactive box indicates that the protocol will not be
available.
HTTPS. Protocol HTTPS (HyperText Transfer Protocol over SSL): variation of HTTP pro-
tocol and uses, besides TCP/IP protocol, SSL layer (Secure Sockets Layer) which imple-
ments the encryption and the authentication of the transmitted data.
available.
SNMP. Protocol SNMP (Simple Network Management Protocol): protocol which allows
monitoring and controlling the network devices. Option:
• Disabled. Protocol SNMP disabled.
• SNMPv1. First version.
• SNMPv2c. Second version.
• SNMPv3. Third version.
FTP. Protocol FTP (File Transfer Protocol): protocol for the file transfer based on TCP.
available.
SFTP. Protocol (SSH File Transfer Protocol): protocol for the secure file transfer.
available.
SSH. Protocol (Secure SHell): protocol for the secure and encrypted access.
available.
Buttons

Add Group. Add a user group.

Remove Group. Delete a user group.
Apply changes. Confirm the changes.
Revert changes. Cancel the changes not confirmed yet.
See also
Groups (command)
SSH protocol (info)

HTTP protocol
HTTP (HyperText Transfer Protocol) is used to transfer hypertext pages within WEB.
All HTTP traffic takes place via the TCP/IP protocol on port 80 of PC.
HTTPS protocol
HTTPS (HyperText Transfer Protocol over SSL) is a variation of HTTP and uses, besides TCP/IP
protocol, SSL layer (Secure Sockets Layer) which implements the encryption and the authenti-
cation of the transmitted data. All HTTPS traffic takes place on port 443 of PC.
In web browsers, URI which refers to this technology is named https.
For more information about RFC 2818 specification (HTTP Over TLS).
ALFOplus2
Equipment can operate with HTTP protocol or HTTPS protocol.
Protocols are implemented in exclusive mode in such a way that, when a user connects via HTT-
PS, HTTP requests will be re-addressed to HTTPS and vice versa.
The use of the protocol HTTP and/or HTTPS at equipment level can be enabled in any moment
(see Enable/disable the operating of a communication protocol).
If the operator enables both the HTTP protocol and the HTTPS protocol, the system will auto-
matically use the more secure protocol (HTTPS).
The operator is advised against the contemporary disabling of the protocols HTTP and HTTPS,
because the connection with the equipment WEB LCT would be lost.
The utilization of a protocol during a WEB LCT session depends even on the enabling state of the
user, who has opened the session, in relation to the use of this protocol. The protocols enabled
for one user depend on the group associated to the user (see Group/User Management).
Example. If the user XY is associated to a group not enabled to the use of HTTPS protocol but
only HTTP, this user can open the WEB LCT session only in HTTP mode even if the HTTPS pro-
tocol is enabled in the Services Status Config context. In the same way, if the user XY is asso-
ciated to a group enabled to the use of HTTPS and HTTP protocol, but the HTTPS protocol is
disabled in the Services Status Config context, the user XY can open the WEB LCT session in
HTTP mode.
As general rule, for the correct use of one protocol, it is necessary that the protocol is enabled
to the use and that the user who opens the WEB LCT session is associated to a group enabled
to the use of the same protocol.
First time equipment is switched-on or after the restore of the Factory Default, equipment uses
HTTP protocol.
NMS5UX-B/NMS5LX
If the equipment is managed even by NMS5UX-B/NMS5LX supervision system, the protocol
(HTTP or HTTPS) used to open the WEB NMS page is defined at level of NMS system.
HTTPS (ALFOplus2) - SSL certificate

Enabling HTTPS protocol is possible only if you have a digital certificate SSL for WEB Server.
Main aim of this certificate is to authenticate the server (for example, ALFOplus2 equipment) at
the customers’ (e.g., user PC where the WEB LCT page relevant to equipment is opened).
SSL foresees that, on connection, the server provides its certificate; if the certificate is signed
by a recognised certification Authority (Trusted certificates), then a secure communication can
be started.
From the physical point of view, the certificate is a file containing the information relevant to the
issuing authority, to the subject of certificate and additional information indicating the use which
the certificate has been released for.
WARNING ALFOplus2 equipment is not provided with SSL certificates when it is put in field.
Moreover, the restore of Factory Default deletes possible certificates already loaded on equip-
ment.

How to get a SSL Trusted certificate
You can get a SSL certificate requiring it to a recognised certification authority (Certification Au-
thority - CA), that is a public authority enable to the univocal emission of certificates.
The Certification Authority ensures the identity of the owner of the certificate signing the public
and private keys by its own private key.
The procedure to request the certificate can change from CA to CA depending on the required
information and on the procedure for the generation and the communication of the pair of key
(see documentation of specific CA).
Generally, all CA’s will require to provide a CSR (Certificate Signing Request), that is a request
containing the data which shall be certificated. To generate the CSR of an equipment see Gen-
erate the Certificate Signing Request for an equipment.
The generation of CSR includes also the generation of a Private Key, which will not be included
in CSR itself will be used only to sign the request of certificate.
The information to include in CSR changes depending on the context for which you request the
certification. CA will define which information is useful.
In any case the name/address of server (Common Name), which you require the certificate for,
will be required.
For the generation of SSL certificates relevant to ALFOplus2 equipment, the Common Name of
the certificate must correspond to the IP address of the equipment for which you wish to use
the certificate (for more information, see Certificate license - ALFOplus2 hereinafter in the chap-
ter).
With IP address we mean the address entered in the URL of the browser to open the page WEB
LCT.
As result of the certification request, CA will provide the file relevant to final SSL certificate. This
file must be loaded on the equipment (see Download the SSL certificate in an equipment).
SSL UnTrusted certificates - ALFOplus2

It is possible to create, and load on the equipment, certificates self-generated by the user (e.g.
via OpenSSL).
The self-signed certificates (UnTrusted certificates) are not generally considered trustworthy by
browsers. They are useful for verification purpose, but the standard use of them does not ensure
the security of server-client connection.
To ensure the security within an equipment network, it is necessary to use certificates signed
by a certification authority (Trusted certificates).
Certificate license - ALFOplus2

The certificate license is valid for only one piece of equipment, because SSL certificates are spe-
cific with respect to the Common Name for which they are required and released.
During the authentication of a server (equipment) at a client (user PC), one of the first executed
check consists in comparing the value of the field Common Name present in the certificate with
the URL of the web page you are opening.
The equipment WEB LCT page is opened at URL //<equipment IP address>. This involves that
the Common Name of the certificate must correspond to the equipment IP address.
So, if you wish to migrate a whole network of ALFOplus2 equipment from HTTP protocol to HTT-
PS protocol, it is necessary to have a SSL certificate for every equipment where the relevant
Common Name corresponds to the equipment IP address.
Certificate expiry - ALFOplus2

Generally, SSL certificates have a quite long expiry.
When the certificates on the equipment expiry, they must be replaced with new valid certificates
by means of the procedures Generate the Certificate Signing Request for an equipment and
Download the SSL certificate in an equipment.
How to implement the protocol HTTPS - ALFOplus2

In summary, the operations to perform in order to implement the use of the protocol HTTPS on
ALFOplus2 are the following:
• Open the WEB LCT page of the equipment for which you wish to generate the request
of the certificate (CSR).

• Generate the Certificate Signing Request for an equipment.
During this operation, set the IP address of the equipment indicated in the URL of the
WEB page to Common Name.
The system, besides generating the CSR, will send the private RSA key to the equip-
ment.
• Copy the CSR and paste it to a text file.
• Send the CST to the chosen CA.
• When CA will send the file containing the SSL certificate signed, load it to the equip-
ment (see Download the SSL certificate in an equipment).
• Verify that the group, which the user used to open the HTTPS session with the equip-
ment is associated to, is enabled. Otherwise, it is necessary to enabled him (see
Groups context/Users context).
• Verify that the protocol HTTPS at equipment level is enabled, otherwise it is necessary
to enable it (see Services Status Config context).
• Close the WEB LCT equipment page and open it again with the user enabled to the
HTTPS connection.
SSL and TLS protocol

The protocols SSL (Secure Socket Layer) and TLS (Transport Layer Security) are encryption pro-
tocols which allow a secure communication in TCP/IP networks.
As indicated at the beginning of the chapter, the protocol HTTPS is a variation of HTTP which
uses the SSL level for the encryption and the authentication of the transmitted data.
In order to do this, the protocols SSL/TLS use three main functionalities:
• Authentication. The authentication of the identity in the connections can be executed
using the encryption with public key (e.g., RSA, DSS etc.).
• Security. In order to ensure a secure connection between two users involved in a
communication, the data are protected using encryption algorithms with symmetric
key (e.g., DES, RC4, etc.).
• Reliability. The transport level includes a check on the integrity of the message based
on a proper MAC (Message Authentication Code) which uses secure hash functions
(e.g., SHA, MD5 etc.). In this way, you can verify that the data transmitted between
client and server have not been altered during the transmission.
SSL and TLS protocol - ALFOplus2

ALFOplus2 equipment uses the protocol TLS version 1.
The user can choose, from the list of CipherSuite, the combination of encryption algorithms sup-
ported by the client, sorted according his preferences.
In detail, the list of CipherSuite indicates:
• The algorithm for the Key Exchange.
• The CipherSpec containing the data encryption algorithm (Cipher) with the possible
implementation characteristics and the algorithm for the Message Authentication
Code (Hash).
ALFOplus2 equipment manages the following CipherSuite.
CipherSuite Key Exchange Cipher Hash

RSA-3DES-SHA RSA 3DES SHA
RSA-WITH-AES-128-CBC-SHA RSA AES-128-CBC SHA
RSA-WITH-AES-256-CBC-SHA RSA AES-256-CBC SHA
See also
Groups (command)
Services Status Config (command)
SSL/HTTP Secure (command)

SNMP protocol
The SNMP protocol is available in 3 versions: SNMPv1, SNMPv2c and SNMPv3.
The main differences between SNMPv1/v2c and SNMPv3 are the management of message se-
curity and the control of the accesses.
SNMPv1/v2c protocol
The versions 1 and 2 of SNMP have the security model based on the community: messages are
passed not-encrypted and can be copied or modified.
SNMPv3 protocol
The version 3 of SNMP, instead, foresees a security model based on the user for the protection
of the messages and the control of the access.
In SMNMPv3, every user has his own authentication password and encryption password for the
packets.
In order to authenticate the packets, SNMPv3 utilizes the HMAC-MD5 or HMAC-SHA1 algorithm.
The secret key used to calculate the HMAC code is the user password; in order to be authenti-
cated, the packet must contain even the user name besides the HMAC code.
Moreover, the SNMPv3 protocol foresees the possibility to cipher the part of the packet contain-
ing the OID of the MIB objects and the relevant values using the cipher algorithm DES56; the
key used for the cipher procedure is different from the key used for HMAC authentication.
This allows defining if allowing the user an access:
• Without authentication (noAuthNoPriv).
• With authentication (AuthNoPriv).
• With authentication and encryption (AuthPriv).
For more information, refer to RFC 3410, 3411, 3412, 3413, 3414, 3415, 3584 specifications.
ALFOplus2
The equipment can work with SNMPv1/v2c protocol and with SNMPv3 protocol.
In order to preserve the security, SNMPv3 protocol must be used.
The use of the protocol SNMPv1/v2c and/or SNMPv3 can be enabled at equipment level in any
moment (see Enable/disable the operating of a communication protocol).
The user can then disable the protocol SNMPv1/v2c or SNMPv3, respecting the following rules:
• The two protocols cannot be disabled at the same time.
• If only one of the two protocols is enabled, it cannot be disabled if the other protocol is
not contextually enabled.
The use of a protocol during a WEB LCT session, however, depends on the enabling state of the
use of this protocol by the user who has opened the session. The protocols enabled for a user
depend on the group associated to the user (see Group/User Management).
Example. If the user XY is associated to a group enabled to the use of the protocol SNMPv3, a
WEB LCT session opened by the user XY will accept and process only SNMPv3 packets; the re-
ceived SNMPv1/v2c packets will be dropped.
In analogous way, if the user YZ is associated to a group enabled to the use of the protocol
SNMPv2c, a WEB LCT session opened by the user YZ will accept and process only SNMPv1/v2c
packets.
First time equipment is switched-on or after the restore of the Factory Default, equipment uses
SNMPv1/v2c protocol.
WARNING If an equipment is configured to work in SNMPv3 and you need to change the site
(operation involving a change of IP address) before the change is necessary to restore the Fac-
tory Default.
Tab.2 displays, for every SNMP version, the security levels (noAuthNoPriv, AuthNoPriv, Auth-
Priv) supported by the equipment and the description of the provided security mechanisms.

Tab.2 Security mechanisms in SNMPv1/v2c and SNMPv3
Security Security level Authentication Encryption Description Notes

model
SNMPv1/v2c noAuthNoPriv Community No Community-based authentica- This security level is automatically as-
String tion: the passwords are trans- signed to a user by the system when the
mitted not encrypted and user is associated, during the creation
displayed in the traces procedure, to a group using the protocol
SNMPv1 or SNMPv2c*.
SNMPv3 noAuthNoPriv Username No Authentication based on user This security level is automatically as-
name signed to a user by the system when the
user is associated, during the creation
procedure, to a group using the protocol
SNMPv3*.
AuthNoPriv MD5 or SHA No Authentication based on algo- This security level is automatically as-
rithms HMAC-MD5 or HMAC- signed to a user by the system when,
SHA during the creation procedure:
• The user is associated to a group us-
ing the protocol SNMPv3*.
• The authentication algorithm/pass-
word is defined to the user*.
AuthPriv MD5 or SHA DES 56 Authentication based on algo- This security level is automatically as-
rithms HMAC-MD5 or HMAC- signed to a user by the system when,
SHA and encryption with algo- during the creation procedure:
rithm CBC-DES (DES-56) in • The user is associated to a group us-
addition to authentication ing the protocol SNMPv3*.
• The authentication algorithm/pass-
word and the encryption algorithm/
password are defined to the user*.
* See Add a user.
See also
Groups (command)
Users (command)

FTP/SFTP protocol
FTP (File Transfer Protocol) and SFTP (SSH File Transfer Protocol) are two protocols for the file
transfer based on TCP.
Main difference between FTP and SFTP is the management of security.
The FTP protocol does not foresee the data encryption, while the SFTP protocol is based on SSH
protocol for the data encryption and the secure file transfer.
ALFOplus2
The equipment can be used for the file transfer (download/upload) the FTP protocol or the SFTP
protocol.
The use of the protocol FTP and/or SFTP can be enabled in any moment (see Enable/disable the
FTP and/or SFTP protocol).
If the operator enables the protocols FTP and SFTP at the same time, the system will automat-
ically use the most secure protocols (SFTP).
The utilization of a protocol during a WEB LCT session depends even on the enabling state of the
user, who has opened the session, in relation to the use of this protocol. The protocols enabled
for one user depend on the group associated to the user (see Group/User Management).
Example. If the user XY is associated to a group not enabled to the use of the protocol SFTP,
even if the protocol SFTP is enabled in the Ftp/Sftp context, the file transfer between PC and
equipment during a WEB LCT session opened by XY will take place via FTP. In the same way, if
the user XY is associated to a group not enabled to the use of the protocol SFTP, but the protocol
SFTP is not enabled in the context area Ftp/Sftp, the file transfer between PC and equipment
during a WEB LCT session opened by XY will take place via FTP.
When the equipment is switched-on for the first time after the restore of the Factory Default
setting the equipment uses the FTP protocol.
NMS5UX-B/NMS5LX
If the equipment is managed even by NMS5UX-B/NMS5LX supervision system, the management
of the protocol for the file transfer (FTP or SFTP) between NMS and equipment is defined at NMS
level.
FTP protocol- ALFOplus2

The default FTP credentials of the equipment are: user Anonymous, no password.
The FTP credentials can be changed at one’s wish (see Modify the FTP access credentials).
The change of FTP credentials is valid only for the current WEB LCT session. When the WEB LCT
page will be re-opened, the default credentials will be used.
The program WEB Lct Console must be used as help for the WEB LCT application, in order to
manage the FTP protocol.
To manage the FTP protocol, as tool auxiliary to WEB LCT application, it is necessary to install
and run one of the following programs:
• Web Lct Console version 1.2.0 or later.
When the program is started, the FTP server provided with the program itself is automat-
ically started.
The server does not perform any check on the credentials.
For the download operations, it is sufficient to enter the complete path where the file re-
sides.
At start-up of WLC, if a FTP Server is already active, the FTP server available with the
program is not started. This condition is signalled by a message.
• Standard FTP Server (e.g., free FTP Server FileZilla).
If you use your own FTP Server, it must be installed and configured if not already present
on the PC.

The configuration consists in defining the users and the path (Shared Folder) used later
for the file transfer.
USERS. For a correct management of the data transfer, the credential used to access to
WEB LCT page must be the same configured for the FTP Server.
For this reason, it is suggested to configure, for the FTP Server, the users present in the
equipment user list with whom the download/upload operations are executed.
PATH. Define the path of Shared Folder for the file transfer.
The path will be used to save the files in the upload operations and shall be the path
(even partial) where are present the files for the download operations.
It is suggested not to save the files in C:\, but to create a sub-folder and set it for the
file saving (e.g. C:\ftp or C:\backup). This allows saving the backup files without being
Administrator users (some Windows versions require to be Administrator user to save the
file in C:\).
SFTP protocol - ALFOplus2

The default SFTP credentials are the same used by the user to access to the WEB LCT page.
The SFTP credentials can be changed at one’s wish (see Modify the SFTP access credentials.
For a correct management of the data transfer, the SFTP credentials shall correspond to the user
(or to one of the users) defined during the installation of the SSH server.
The change of credentials is valid only for the current WEB LCT session. When the WEB LCT page
will be re-opened, the default credentials will be used.
As help for the WEB LCT application in order to manage the protocol SFTP, it is necessary to
install and configure a SSH server (see Installation and configuration of SSH server).
See also
Groups (command)
Ftp/Sftp (command)

Installation and configuration of SSH server
1. Install the free SSH server freeSSHd.
a. Execute the guided installation of freeSSHd.exe.
b. When asked Do you want to run FreeSSHd as a system service? press No.
2. Verify that, during the program installation, a service has not been installed in Windows.
a. Open the Windows Task Manager window.
b. Select the Services tab.
c. Press Services.
d. Verify that the list does not contain the option FreeSSHDServices.
e. If present, select it, open the Properties window and set the parameter Startup type -> Manual.
3. Configure the SSH server.
a. Open the freeSSHd settings window.
b. Select the SSH tab.
c. Activate the Start SSH server on free SSHd startup box and press Apply.
d. Select the Telnet tab.
e. Deactivate the Start Telnet server on free SSHd startup box and press Apply.
f. Select the Authentication tab and verify the setting of the following parameters:
• Password authentication -> Allowed.
• Public key authentication -> Allowed.
If the parameters are set in different way, set them as displayed and press Apply.
g. Select the Encryption box and verify the setting of the parameter:
• Allowed ciphers -> Any.
If the parameter is set in different way, set it as displayed and press Apply.
h. Select the Tunneling tab and verify the setting of the following parameters:
• Allow local port forwarding -> inactive box.
• Allow remote port forwarding -> inactive box.
i. Select the SFTP tab, in the SFTP home path set the path of the home directory for the file trans-
fer and press Apply.
The file path must be in C:\. It is suggested NOT to save the files in C:\, but to create a subfolder
in C and set it to save the files (for instance, C:\ftps or C:\backup).
This allows saving the backup files without being Administrator user (in some version of Win-
dows, in order to save the files in C:\, it is necessary to be Administrator user).
j. Select the Automatic updates tab and verify the setting of the following parameters:
• Check for new version on startup -> inactive box.
• Update without asking me for confirmation -> inactive box.
• Show info messages from freeSSHd.com -> inactive box.
k. Select the Logging tab, in the Log file box set the path/filename to save the log file and press
Apply.
l. Select the Host restrictions tab and verify the setting of the parameter:
• Refuse these IP addresses -> active box.
If the parameter is set in different way, set it as displayed and press Apply.
m. Select the Users tab, press Add and create the SFTP users setting the following characteristics
and press OK.
• Login -> User name
• Authorization -> Password stored as SHA1 hash.

• Password/Password (again) -> Access code.
• User can use -> Shell, SFTP.
WARNING It is suggested to create the users presents in the user list of the equipment because
the equipment uses, as default SFTP credentials, the same of the user used to access the WEB
LCT page.
4. Restart the SSH server and verify its status.
a. Open the freeSSHd settings window.
b. Select the Server status tab and verify that:

• The Telnet server is not running (Telnet server is not running).
• the SSH server is running (SSH server is running).
WARNING After the configuration of SSH server, if the one or more parameters must be changed, to make
the change operative, restart the server selecting the Unload command present in the contextual menu of
the FreeSSHD Service application.
See also

SSH protocol (info)
SSH protocol
SSH (Secure SHell) protocol allows implementing secure connections between two system, us-
ing a client/server architecture.
Documents defining the protocol can be found at http://www.ietf.org.
ALFOplus2
The equipment operate with SSH2 protocol.
By means of WEB LCT, the use of the protocol SSH can be enabled/disabled (see Enable/disable
the operating of a communication protocol).
For the correct use of the protocol SSH, it is necessary that the user, who opens the WEB LCT
session, is associated to a group enabled to the use of the protocol itself (see Group/User Man-
agement).
When the equipment is switched-on for the first time after the restore of the Factory Default
setting, the SSH protocol is disabled.
See also
Groups (command)

Users
The Users command manages the users (WEB and SNMP) of the equipment.
Operations
Verify the user list
Add a user
Modify a user
Delete a user
GUI
Users context
See also
Groups (command)
Verify the user list
1. Select Main > Group/User Management > Users.

The Users context displays the list of the users (WEB and SNMP) currently stored in the equipment.
Add a user
WARNING It is possible to set a maximum of 10 users (see Limits).

If the equipment is managed even by NMS5UX-B/NMS5LX supervision system, it is necessary to create the
user used by the supervision system for the connection to the equipment (NMS GUI, NMS5WI GUI). This
user must be associated to a group with profile Administrator and all the protocols enabled.
2. Select Add User.
3. Into the User box, type the user name (alphanumeric string with a number of characters from 4 up to
31, the accepted and recognized characters are 0÷9, a÷z and A÷Z).
It is not possible to assign the same name to two different users present into the same list.
4. Press Change at the side of the Password parameter.
5. Into the New Password and Confirm New Password box, type the access code of the (alphanumeric
string with a number of characters from 4 up to 31, the accepted and recognized characters are 0÷9,
a÷z and A÷Z) and press OK.
The fields are Case Sensitive. Pay attention to uppercase and lowercase characters.
6. Set the group, to which you wish to associate the user, in the Group box.
The user will inherit the group characteristics: profile and use of the protocols HTTP, HTTPS, SNMP, FTP,
SFTP and SSH.

7. In the Timeout box, set the timeout of the WEB LCT session opened by the user. If you wish:
• The session of WEB LCT opened by the user (even if disconnected) is kept for an infinity period
(session timeout disabled), set the value 0.
• The session of WEB LCT opened by the user, if disconnected, is automatically terminated once
reached a specific time limit (session timeout disabled), set a value between 1 and 3600 sec.
(1h).
With disconnected session we mean a WEB LCT session whose relevant WEB LCT page has been
closed but for which the disconnection from the equipment has not been executed (user logout).
8. Only if the user you are creating belongs to a group for which the SNMP3 protocol has been set, execute
the following steps:
a. Set, in the Auth Protocol box, the authentication protocol (algorithm) associated to the user:
• None. No authentication algorithm.
• MD5. Authentication algorithm MD5 (Message Digest version 5) based on hash code.
• SHA. Authentication algorithm SHA-1 (Secure Hash Algorithm) with 96 bit digest
based on hash code (HMAC).
b. Press Change at the side of the Auth Key parameter.

c. Set, in the New Password and Confirm New Password boxes, the authentication password asso-
ciated to the user and press OK.
The authentication password must be a string with a minimum length of 4 (SNMPv1/V2c) or 8
(SNMPv3) characters and a maximum length of 31 characters. The accepted and recognised
characters are 0÷9, a÷z and A÷Z). The fields are Case Sensitive. Pay attention to uppercase
and lowercase characters.
d. Set, in the Priv Protocol box, the cypher protocol (algorithm) associated to the user:
• None. No cypher algorithm.
• DES. 3DES (Triple Data Encryption Standard) block cypher algorithm based on the
repetition of DES algorithm for three times.
• AES. AES (Advanced Encryption Standard) cypher algorithm.
e. Press Change at the side of the Priv Key parameter.
f. Set, in the New Password and Confirm New Password boxes, the cypher password associated to
the user (alphanumeric string of at least 4 characters and at most 31 characters. The characters
accepted and recognised are 0÷9, a÷z and A÷Z) and press OK.
The cypher password must be a string with a minimum length of 4 (SNMPv1/V2c) or 8 (SNMPv3)
characters and a maximum length of 31 characters. The accepted and recognised characters are
0÷9, a÷z and A÷Z). The fields are Case Sensitive. Pay attention to uppercase and lowercase
characters.

The new user is inserted in the list and communicated to the equipment.
Modify a user
2. Select the user and press Modify User or double click on the user.
3. Execute the changing.
The setting modes of the parameters are the same ones above pointed out into the par. Add a user.
The parameter User, Group, Auth Protocol and Priv Protocol can NOT be changed. To change them, it
is necessary to delete the user and create him again with the wished characteristics.
The fields for the setting of the password are Case Sensitive; pay attention to uppercase and lowercase
characters.

Delete a user
WARNING The operation is not available if the selected user is the current user or the last user with Ad-
ministrator profile.
2. Select the user.
3. Press Remove User and confirm.

Users context
The context displays the user list (WEB and SNMP) currently stored in the equipment.
Table
Every row of the table corresponds to a user for which are indicated:
User. User name.
Group. Group which the user is associated to.
Profile. User profile:
• Administrator. The user with this profile can both verify the parameters and
send commands or change the equipment configuration with no exception.
• Read/Write. The user with this profile can as check the parameters as send
commands or execute changes to the equipment configuration except for the
following operations: modifying the user list, aligning the date/time of the
equipment, force the logout of a user and all those operations available only
to the Admin. user.
only maintenance operations (MAN. OP) in the Manual Operations context and
Radio BER context.
Auth. Authentication protocol (algorithm) associated to the user:
• None. No authentication algorithm.
• MD5. Authentication algorithm MD5 (Message Digest version 5) based on hash
code.
• SHA. Authentication algorithm SHA-1 (Secure Hash Algorithm) with 96 bit di-
gest based on hash code (HMAC).
Parameter meaningful only for users associated to a group with protocol SNMPv3 ena-
bled.
Priv. Cypher protocol (algorithm) associated to the user:
• None. No cypher algorithm.
• DES. 3DES (Triple Data Encryption Standard) block cypher algorithm based on
the repetition of DES algorithm for three times.
• AES. AES (Advanced Encryption Standard) cypher algorithm.
Parameter meaningful only for users associated to a group with protocol SNMPv3 ena-
bled.
Timeout. Timeout of WEB LCT session opened by the user:
• O. Session timeout disabled. WEB LCT session opened by the user (even if dis-
connected) will be kept for an infinity period of time.
• <number>. Session timeout enabled. WEB LCT session opened by the user, if
disconnected, will be automatically ended once reached the set time limit.
With disconnected session we mean a WEB LCT session whose relevant WEB LCT page
has been closed but for which the disconnection from the equipment has not been exe-
cuted (user logout).
Buttons
Add User. Add a user.

Remove User. Delete a user
Modify User. Modify a user.
See also
Users (command)

Users list
The user list is a list of the users who can connect and require to login to the equipment by the
WEB LCT application (WEB user) or the NMS5UX-B/NMS5LX program (SNMP user).
If an user is not present in the list stored in the equipment controller, that user cannot connect
and/or login to the that equipment.
Users are subdivided into groups (for details, see successive paragraphs).
Before creating an user, it is necessary to create the group which the user must be associated
to. One group can contain more users, but one specific user can belong to only one group.
A maximum of 10 groups and 10 users can be created in the equipment user list.
At the first connection with the equipment or after a Factory Default operation, a default group
and a default user are available. Then, through WEB LCT application, new users and groups can
be created, modified and deleted.
The management of the user list can be performed even by NMS5UX-B/NMS5LX system (NMS
GUI).
Groups
The users belonging to the list are organized in groups for which it is possible to define a profile
and the enabling to the use of HTTP, HTTPS, SNMP, FTP, SFTP and SSH protocols.
The profile and the authorization of a group will be automatically assigned to the user who is
associated to that group.
The characteristics of a group are:
• Name of the group. The name of the group must be unique within an user list.
The name of the group, once assigned, cannot be changed.
• Profile which will be automatically assigned to the users associated to the group:
• Administrator. The user with this profile can both verify the parameters and send
commands or change the equipment configuration with no exception.
Moreover, every user belonging to a group with profile Administrator, besides be-
ing a WEB user, is even a CLI user because a user with profile Administrator is
automatically enabled by the system to access to the equipment even by the ap-
plication SM-OS (Siae Microelettronica - Operating System).
• Read/Write. The user with this profile can as check the parameters as send com-
mands or execute changes to the equipment configuration except for the following
operations: modifying the user list, aligning the date/time of the equipment, force
the logout of a user and all those operations available only to the Admin. user.
only maintenance operations (MAN. OP) in the Manual Operations context and Ra-
dio BER context.
• Protocols which will be available to the users assigned to the group:
• Protocol HTTP (HyperText Transfer Protocol), used to transfer hypertext pages on
the WEB.
• Protocol HTTPS (HyperText Transfer Protocol over SSL): variation of HTTP proto-
col and uses, besides TCP/IP protocol, SSL layer (Secure Sockets Layer) which im-
plements the encryption and the authentication of the transmitted data.
• Protocol SNMP (Simple Network Management Protocol), which allows monitoring
and controlling the network device. The user can activate the use of the first ver-
sion (SNMPv1), the second version (SNMPv2c) or the third version (SNMPv3) of
the protocol.
• Protocol FTP (File Transfer Protocol), for the file transfer based on TCP.
• Protocol SFTP (SSH File Transfer Protocol): protocol for the secure file transfer.
• Protocol SSH (Secure SHell Protocol): protocol for the secure and encrypted ac-
cess.
More options can be enabled at the same time.

At the first connection with the equipment or after a Factory Default operation, the following
default groups are available:
Admin
Name: Admin.
Profile: Administrator.
Enabled protocols: CLI, HTTP, FTP and SNMPv1.
The default group can be changed but not deleted.
Root
Name: Root.
Enabled protocols: CLI.
Via WEB LCT page, the user can Verify the user groups and only one user with Administrator
profile can Add a user group, Modify a user group or Delete a user group.
Users
The users belonging to the list are organized in groups for which a profile and the enabling to
the use of the HTTP, HTTPS, SNMP, FTP, SFTP and SSH protocols can be defined.
The profile and the authorization of a group will be automatically assigned to the user who is
associated to that group.
The characteristics of an user are:
• Name/Password. Name and access password, which allow the program recognizing the
user as authorized.
The same user can open more WEB LCT page relevant to different equipment.
The name of an user must be unique within an user list.
The name of an user, once assigned, cannot be changed.
• Group which the user is associated to and from which the user inherits the profile and
the enabling to the use of HTTP, HTTPS, SNMP, FTP, SFTP and SSH protocols.
Every user belonging to a group with profile Administrator, besides being a WEB user, is
even a CLI user because a user with profile Administrator is automatically enabled by the
system to access to the equipment even by the application SM-OS SM-OS (Siae Micro-
elettronica - Operating System).
• Timeout of the WEB LCT session opened by the user. It is possible to:
• Disable the timeout: the WEB LCT session opened by the user (even if disconnect-
ed) will be preserved for an indefinite period of time.
• Enable the timeout: the WEB LCT session opened by the user, if disconnected, will
be automatically terminated once the set time period is reached.
With disconnected session we mean a WEB LCT session for which the relevant
WEB LCT page has been closed, but the disconnection from the equipment has not
been performed (user logout).
At the first connection with the equipment or after a Factory Default operation, the following
default users are available:
admin
User: admin
Password: admin
Group: Admin (default group - see characteristics in previous paragraph).
Auth: None.
Priv: None.
Timeout: 300 sec.
root
User: root
Password: admin123
Group: Root (default group - see characteristics in previous paragraph).
Auth: None.

Priv: None.
Timeout: 1800 sec.
WARNING At the first access, it is suggested to immediately change the password of the default
users in order to limit the risk of intrusion via these accounts.
The default users can be modified or deleted. The only condition is that there must be at least
one other user with Administrator profile in the user list.
Through WEB LCT page, the user can Verify the user list and, only an user with Administrator
profile, Add a user, Modify a user or Delete a user.
NMS5UX user
If the equipment is managed even by NMS5UX-B/NMS5LX supervision system (NMS GUI,
NMS5WI GUI), it is necessary to create the user used by the supervision system for the connec-
tion to the equipment: User: NMS5UX, Password: SIAEMICR.
This user must be associated to a group with profile Administrator and all the protocols enabled.
More information about the NMS5UX-B/NMS5LX supervision system is reported in the relevant
documentation.
See also
Groups (command)
Users (command)
Groups context
Users context

Permanent Login
The Permanent Login command manages the remote users who have the possibility to be connected to
the equipment (Permanent Login).
The remote user has the same characteristics of the NMS5UX user with the only exception that he does
not need for a login password.
A maximum of 2 remote users can be set.
Operations
Verify the IP address of Permanent Login
Set/modify the IP address of Permanent Login
GUI
Permanent Login context
See also
Verify the IP address of Permanent Login
1. Select Main > Group/User Management > Permanent Login.

The Permanent Login context displays the IP address of the remote users who have the possibility to
be connected to the equipment.
1. Select Main > Group/User Management > Permanent Login.
2. To set/modify the IP address of the machine relevant the:

• First remote user, type a valid IP address in the Manager IP Address 1 box.
• Second remote user, type a valid IP address in the Manager IP Address 2 box.
Value 0.0.0.0 indicates the parameter is disabled.

Permanent Login context
The context displays the IP address of the remote users who have the possibility to be connected to the
equipment (Permanent Login).
Parameters
Manager IP Address 1. IP address of the machine relevant the first remote user.
Manager IP Address 2. IP address of the machine relevant the second remote user.
Value 0.0.0.0 indicates the parameter is disabled.
Buttons
See also
Permanent Login (command)

Logged Users
The Logged Users command manages the users connected to the equipment.
Operations
Verify the users connected to the equipment
Force the logout of a user
GUI
Logged Users context
See also
Verify the users connected to the equipment
1. Select Main > Group/User Management > Logged Users.

The Logged Users context displays the list of the users connected to the equipment when the command
is selected.
Press Refresh to update the data present in the window.
Force the logout of a user
WARNING Logging out oneself is not possible.
1. Select Main > Group/User Management > Logged Users.
2. Select the wished user.
3. Press Force Logout and confirm.

Logged Users context
The context displays the list of the users connected to the equipment when the command is selected.
Table
Every row of the table corresponds to a user for which are indicated:
User. User name.
The wording NMS5UX shows the user of the NMS5UX-B/NMS5LX supervisory system
(NMS GUI and NMS5WI GUI) or a remote user who has the possibility to be connected
to the equipment (Permanent Login).
Profile. User profile (see User Profile parameter)
Timeout. Timeout of the WEB LCT session:
• 0 s. Session timeout disabled. WEB LCT session opened by the user (even if
disconnected) will be kept for an infinity period of time.
• <number> s. Session timeout enabled. WEB LCT session opened by the user,
if disconnected, will be automatically ended once reached the set time limit.
With disconnected session we mean a WEB LCT session whose relevant page has been
closed but for which the disconnection from the equipment has not been executed (user
logout).
Login Type. User type:
• WEB. User of the WEB LCT application.
• SNMP. SNMP user or user of the NMS5UX-B/NMS5LX supervision system.
• CLI. User of SM-OS application, connected to the equipment via telnet or serial
line.
IP Address. Machine IP address.
With the wording machine, it is intended the PC/server/workstation on which the appli-
cation used by the user is actually running.
Parameter not meaningful for the user of SM-OS application, connected to the equipment
via serial line.
Buttons
Force Logout. Force the logout of a user
See also
Logged Users (command)

Security Management
Access Control List. It manages the IP Access Control List (ACL).

Services Status Config. It manages the equipment communication protocols (SNMP, HTTP, Telnet, SSH,
HTTPS).
SSL/HTTP Secure. It manages the configuration of the protocol SSL and the SSL certificate (generation
of CSR and loading of the certificate in the equipment).
Radio Encryption. It manages the Radio Encryption function.
Clients. It manages the FTP and SFTP protocols.

Access Control List
The Services Status Config command manages the control list of IP accesses (ACL - Access Control List).
Operations
Verify the rules used by the ACL
Add a rule to ACL
Modify a rule of ACL
Remove a rule from ACL
GUI
Access Control List context
See also
ACL function (info)
Verify the rules used by the ACL
1. Select Main > Security Management > Access Control List.

The Access Control List context shows the IP Access Control List (ACL) of the equipment.
Add a rule to ACL
WARNING A maximum of 20 rules can be inserted in the list.
2. Select the ACL tab.
3. Press Add.
4. Set, in Priority box, the priority used to analyse the rule (value between 1 and 255, where 255 is the
highest priority).
The same priority can be assigned to more rules.
5. Set, in Interface box, the management ports which the rule must be applied to, activating the relevant
check-box ( ):
• vlan.... management VLAN (see MNGT Port Configuration context).
6. Set, in IP Address box, the IP subnetwork or the single IP address which the rule refers to.
7. Set, in Mask, the netmask relevant to the IP subnetwork/IP address which the rule refers to.
The mask format must be expressed in bits (value between 0 and 32) and not in dotted decimal nota-
tion.
8. In the Filter Action box, set the usage condition of the rule:
• drop. The IP subnetwork/IP address is not allowed accessing the equipment.
• allow. The IP subnetwork/IP address is allowed accessing the equipment.

The rule is inserted in ACL and becomes active immediately.

User Profile | Admin.Access | Read & Write
2. In order to modify the priority used to analyse the rule, select the relevant Priority box and set a value
between 1 and 255, where 255 is the highest priority.
The same priority can be assigned to more rules.
3. In order to change the management port which the rules must be applied to, select the relevant Inter-
face box and activate or deactivate the check-box:
• vlan.... Management VLAN (see MNGT Port Configuration context).
The active check-box ( ) indicates that the rule is applied to the port; the inactive check-box indicates
that the rule is not applied to the port.
4. In order to change the IP subnetwork or the single IP address, select the relevant IP Address box and
set the new value.
5. In order to change the netmask relevant to IP subnetwork/IP address which the rules refers to, select
the relevant Mask box and set the new value.
The mask format must be expressed in bits (value between 0 and 32) and not in dotted decimal nota-
tion.
6. In order to change the usage conditions of the rule, select the relevant Filter Action box and set the
value:
• drop. The IP subnetwork/IP address is not allowed accessing the equipment.
• allow. The IP subnetwork/IP address is allowed accessing the equipment.
The rule is changed.
2. Select the row relevant to the rule you wish to delete from the list.
Multiple selections can be executed using the Ctrl or Shift keys.
3. Press Remove and confirm.

The rule is removed from the list and communicated to the equipment.

The context shows the IP Access Control List (ACL) of the equipment.
Table
The table lists the rules used by the equipment for the control of the IP accesses for the man-
agement ports.
Each row identifies a rule:
Index. Value identifying univocally the rule within the ACL table.
Priority. Rule priority: 1 ÷ 255 (1 is the lowest priority, 255 the highest).
For the packet analysis, the rule with highest priority is used.
Interfaces. Management port which the rule must be applied to:
• vlan.... Management VLAN (see MNGT Port Configuration context).
The active box ( ) indicates that the rule is applied to the port; the inactive box indi-
cates that the rule is not applied to the port.
IP Address. IP subnetwork or single IP network which the rule refers to.
Mask. Netmask relevant to the IP subnetwork or to the IP address which the rule refers
to.
The mask format is expressed in bits (value between 0 and 32).
Filter Action. Usage conditions of the rule:
• allow. The IP subnetwork/address is allowed accessing the equipment.
• drop. The IP subnetwork/address is not allowed accessing the equipment.
Selecting the heading of the Index column, the rows of the table are sorted in increasing alpha-
numeric order with respect to the considered column and an arrow is displayed with the tip di-
rected upwards. The next selection sorts the rows in decreasing order (an arrow is displayed
with the tip directed downwards) and so on.
Buttons
Refresh. Updates the context.
Help. Opens the help on-line.
Add. Add a rule to ACL.
Remove. Remove a rule from ACL.
See also
Access Control List (command)
ACL function (info)

ACL function (info)
ACL function
ACL (Access Control List) functionality is a mechanism which allows/blocks new connections to
the equipment in selective mode on the basis of the source IP address (SRC).
The functionality applies to all the management interfaces (MNGT).
This mechanism consists in a list of rules (Access Control Entry) which determine if an IP sub-
network or a single IP address is allowed accessing to the selecting equipment.
Every rule is composed by a descriptive part and a decision-making part.
The descriptive part of the rule is represented by the IP address (or by a set of IP addresses)
source of the packet, by the MNGT ports where the packet enters and by the priority used to
analyse the rule.
The decision-making part is the action to execute: making the packet passes or refusing it.
ALFOplus2
In ALFOplus2 equipment, the rules present in the IP access control list must be defined by the
operator via WEB LCT, CLI or WEB NMS.
When the rule is created, it is immediately inserted in ACL and becomes immediately active.
In ALFOplus2 equipment, when a packet is analysed, the considered conditions are the follow-
ing:
• The rules, once activated, are immediately applied to all the packets (UDP and TCP) ex-
cept for those relevant to TCP connections already open and, for these ones, only to the
closing of the connection.
• The ACL rules apply to the new requests of connection; the existing connections are not
analysed.
• The rules are analysed according to the priority, starting from the highest value. The first
compatible rule is executed, after which no other rule will be checked/executed.
• All the packets not associated to any rule will be correctly forwarded to the higher layers.
Add a rule to ACL

A maximum number of 20 rules can be created (see Add a rule to ACL).
During the creation of the rule, the operator must set the following parameters:
Priority. The rule priority is used to decide which rule can be applied to a packet, if this
packet is associated to more rules. In this case, the rule with highest priority will be ap-
plied.
The priority can be set to a value between 1 and 255, where 1 is the lowest priority and
255 the highest priority.
If more rules have the same priority, the system will use the rule with highest value of
Index.
Interface. MNGT interface where enters the packet which the rule is applied to.
One rule can be associated to more MNGT interfaces.
IP address. IP subnetwork/IP address source of the packet which the rule must be ap-
plied to.
Netmask relevant to IP subnetwork/IP address.
The mask format must be expressed in bit (value between 0 and 32) and not in dotted
decimal format.
In IPv4 addresses, a length of 0 bits indicates the match of any address (decimal value
0.0.0.0), a length of 32 bits indicates the match of a single host address (decimal value
255.255.255.255) and a length between 0 and 32 bits indicates the use of a CIDR (Class-
less Inter-Domain Routing) prefix.
The CIDR prefix indicates the number of bits of IP addresses which belong to net id.
For example, to set the IP address 192.168.58.147, with netmask 255.255.240.0, during
the creation of a rule the field IP Address shall be set to the value 192.167.58.147 and
the field Mask to the value 20.
Action. Action to perform on the packet corresponding to the rule.
If the action is allow, the packet is forwarded according to the forwarding rules. If the
action is drop, the packet is dropped.

See also
Access Control List (command)

Services Status Config
The Services Status Config command manages the equipment communication protocols (services used
by the management program to access to the equipment).
Operations
Verify the operating of the communication protocols
Enable/disable the operating of a communication protocol
GUI
Services Status Config context
See also
SSH protocol (info)
Verify the operating of the communication protocols
1. Select Main > Security Management > Services Status Config.

The Services Status Config context shows the name, the administrative status and the operating status
of the services on the equipment.
1. Select Main > Security Management > Services Status Config.

The parameter Admin State indicates the current administrative status of the protocols:
• Disable. The protocol is disabled.
• Enable. The protocol is enabled.
2. To modify a parameter, select the new value in correspondence of the wished protocol.
The operator is advised against the contemporary disabling of the protocols HTTP and HTTPS, because
the connection with the equipment WEB LCT would be lost.
The protocol HTTPS can be enabled if:
• there is, in the user list, at least one user enabled to use it.
• the relevant SSL certificate is present in the equipment (see HTTP/HTTPS protocol (info).
The user can disable the protocol SNMPv1/v2c or SNMPv3, respecting the following rules:
• The two protocols cannot be disabled at the same time.
• If only one of the two protocols is enabled, it cannot be disabled if the other protocol is not con-
textually enabled.

The message This Feature is not enabled! indicates that the Security package feature is disabled (see
Equipment Features tab).

Services Status Config context
The context shows the equipment communication protocols.
Table
Every table row corresponds to a protocol for which are indicated:
Service Name. Name of the protocol (service):
• SNMPv1v2c. SNMP (Simple Network Management Protocol) protocol first and
second version: protocol which allows monitoring and controlling the network
devices.
• SNMPv3. SNMP protocol third version.
• Telnet. TCP-based Client-server network protocol which provides the user with
sessions of remote login.
• SSH. SSH (Secure SHell) protocol: protocol for the secure and encrypted ac-
cess.
• HTTP. HTTP (HyperText Transfer Protocol) protocol: protocol used to transfer
hypertext pages on the WEB.
• HTTPS. HTTPS (HyperText Transfer Protocol over SSL) protocol: variation of
HTTP and uses, besides TCP/IP protocol, SSL layer (Secure Sockets Layer)
which implements the encryption and the authentication of the transmitted
data.
Admin Status. Administrative state (enabling) of the protocol:
Operative Status. Operating status of the protocol:
• Running. The protocol is operating.
• Stopped. The protocol is not operating (disabling of the protocol or malfunc-
tion).
Selecting the heading of a column, the rows of the table are sorted in increasing alphanumeric
order with respect to the considered column and an arrow is displayed with the tip directed up-
wards. The next selection sorts the rows in decreasing order (an arrow is displayed with the tip
directed downwards) and so on.
Buttons
See also
SSH protocol (info)

SSL/HTTP Secure
The command SSL/HTTP Secure manages the configuration of the protocol SSL and the SSL certificate
(generation of CSR and loading of the certificate in the equipment).
Operations
Verify the configuration of the SSL protocol
Modify the list of CipherSuite managed by the equipment
Generate the Certificate Signing Request for an equipment
Download the SSL certificate in an equipment
GUI
SSL/HTTP Secure context
See also
Verify the configuration of the SSL protocol
1. Select Main > Security Management > SSL/HTTP Secure.

The SSL/HTTP Secure context displays the configuration of the SSL (Secure Socket Layer) protocol.

The area HTTP Secure Ciphersuite lists the CipherSuite managed by the equipment:
• RSA-3DES-SHA. Algorithm for the key exchange: RSA. Data encryption algorithm: 3DES. Algo-
rithm for Message Authentication Code: SHA.
• RSA-WITH-AES-128-CBC-SHA. Algorithm for the key exchange: RSA. Data encryption algo-
rithm: AES-128-CBC. Algorithm for Message Authentication Code: SHA
• RSA-WITH-AES-256-CBC-SHA. Algorithm for the key exchange: RSA. Data encryption algo-
rithm: AES-256-CBC. Algorithm for Message Authentication Code: SHA.
2. Activate ( ) or deactivate ( ) the wished options.
4. In order to make the change effective, it is necessary to disable and re-enable the protocol HTTPS:
a. Select Security Management > Services Status Config.
b. In the Admin State box of the HTTPS option, select the Disable value.
c. Press Apply and confirm.

d. In the Admin State box of the HTTPS option, select the Enable value.
e. Press Apply and confirm.

Generate the Certificate Signing Request for an equipment
WARNING This operation is included in the procedure for the implementation of the protocol HTTP for
equipment. Before executing it, read How to implement the protocol HTTPS - ALFOplus2 in HTTP/HTTPS
protocol (info).
2. Press Generate Certificate Signing Request.
3. Set, in the box RSA Key Size, the length of RSA key: 512 or 1024.
4. Set, in the box Common Name, the IP address of the equipment for which you wish to use the certifi-
cate.
With IP address we mean the address entered in the URL of the browser to open the page WEB LCT.
5. Press Generate.
The text area displays the CSR. Moreover, the key associated to the certificate request is communicated
to the equipment.
6. Select and copy the content of the area into a text file.
The file shall be sent to the Certificate Authority to obtain the relevant SSL certificate.
7. Press Cancel to close the Generate Certificate Signing Request. window.
Download the SSL certificate in an equipment
WARNING Operation available only if you have the file of to the SSL certificate relevant to the equipment
you are connected to.
The certificate license is valid for only one piece of equipment, because SSL certificates are specific with
respect to the Common Name for which they are required and released.
For the equipment ALFOplus2, the Common Name of the certificate must correspond to the IP address of
the equipment for which you wish to use the certificate.
This operation is included in the procedure for the implementation of the protocol HTTP for equipment. Be-
fore executing it, read How to implement the protocol HTTPS - ALFOplus2 in HTTP/HTTPS protocol (info).
2. Press Enter Certificate Signed By Certification Authority.
3. Open, in a text editor, the file relevant to the SSL certificate obtained by the Certificate Authority rel-
evant to the equipment you are connected to and copy it.
4. Paste the SSL certificate to the text area of the window Enter Certificate Signed By Certification Author-
ity.
5. Press Send.
The new certificate is now in use.
The message Invalid certificate indicates that the operation has not been executed because the certi-
fication is corrupted or because the key present on the equipment does not match that of the certificate.

SSL/HTTP Secure context
The context shows the configuration of SSL protocol and allows managing the SSL certificate (generation
of CSR and loading of the certificate in the equipment).
Parameters
HTTP SECURE CIPHERSUITE
SSL Version. Version of the protocol in use:
• TLS-1. Protocol Transport Layer Security version 1.
Read only parameter.
List of CipherSuite managed by the equipment:
• RSA-3DES-SHA. Algorithm for the key exchange: RSA. Algorithm of data en-
cryption: 3DES. Algorithm for the Message Authentication Code: SHA.
• RSA-WITH-AES-128-CBC-SHA. Algorithm for the key exchange: RSA. Algo-
rithm of data encryption: AES-128-CBC. Algorithm for the Message Authenti-
cation Code: SHA
• RSA-WITH-AES-256-CBC-SHA. Algorithm for the key exchange: RSA. Algo-
rithm of data encryption: AES-256-CBC. Algorithm for the Message Authenti-
cation Code: SHA.
The active box ( ) means that the CipherSuite is in use, the inactive box means that it
is not used.
Buttons
SSL DIGITAL CERTIFICATE MANAGEMENT

Generate Certificate Signing Request. Generate the Certificate Signing Request for
an equipment
Enter Certificate Signed By Certification Authority. Download the SSL certificate in
an equipment
See also
SSL/HTTP Secure (command)

Radio Encryption
WARNING Command available only if the Radio payload encryptions feature is enabled (see Equipment
Features tab).
Moreover, the command is available only if the current WEB LCT session has been opened using the HTTPS
protocol and the user who has opened the session has the following security protocols enabled: HTTPS and
SNMPv3 with authentication password.
The Radio Encryption command manages the Radio Encryption function.
Operations
Verify the status and configuration of Radio Encryption function
Modify the allocation of memory for Radio Encryption function
Modify the enabling of Radio Encryption function
Modify the data encryption algorithm
Modify the encryption key
GUI
Radio Encryption context
See also
Radio Encryption (info)
Verify the status and configuration of Radio Encryption function
1. Select Main > Security Management > Radio Encryption.

The Radio Encryption context displays the status and the configuration of Radio Encryption function.
The message Radio Encryption parameters are available only in secure connection using HTTPS protocol
(see “Services Status Config.” to activate) indicates that the functionality can be used only if the WEB
LCT session is opened using the HTTPS protocol (see How to implement the protocol HTTPS -
ALFOplus2).

The System Control parameter indicates the enabling state, by the control system, of the Radio Encryp-
tion function for the equipment:
• Start. The system activates the Radio Encryption function: the necessary memory is allocated
for the function.
• Shutdown. The system stops the Radio Encryption function: the allocated memory is de-allocat-
ed and made available for other activities.
2. To modify the parameter, select the wished value.
WARNING Selecting the value Shutdown involves the disabling and the loss of all the configurations
made by the user for the Radio Encryption function. In fact, when the value Start is selected later, all
the parameters will be available set to their default value.

WARNING Operation available only if the System Control parameter has Start value.

The Admin State parameter indicates the enabling status of Radio Encryption function:
• Enable. The function is active.
• Disable. The function is not active.
2. To change the parameter, select the wished value.

The parameter Encrypt Algo. indicates the encryption algorithm used for the Radio traffic (Payload):
• AES 128. The algorithm AES 128 (Advanced Encryption Standard) has been used for the encryp-
tion. The algorithm has a fixed block size of 128 bits and a 128-bit key.
• AES 256. The algorithm AES 256 has been used for the encryption. The algorithm has a fixed
block size of 256 bits and a 256-bit key.

Modify the encryption key
2. Press Change Encryption Key.
3. In the New Key box, set an alphanumeric string between 1 and 16 (with algorithm AES 128 set) or 32
(with algorithm AES 256 set) characters.
4. Press OK.

WARNING Context available only if the Radio payload encryptions feature is enabled (see Equipment Fea-
tures tab).
Moreover, the context is available only if the current WEB LCT session has been opened using the HTTPS
protocol and the user who has opened the session has the following security protocols enabled: HTTPS and
SNMPv3 with authentication password.
The context shows the status and configuration of Radio Encryption function.
Parameters
System Control. Enabling state of the Radio Encryption function:
• Start. The system activates the Radio Encryption function: the necessary memory is al-
located for the function.
• Shutdown. The system stops the Radio Encryption function: the allocated memory is de-
allocated and made available for other activities.
Default Shutdown.
Admin State. Enabling status of Radio Encryption function:

• Enable. The function is active.
• Disable. The function is not active.
Default Enable.
Parameter available only if the parameter System Control has value Start.
Encrypt Algo. Encryption algorithm used for the Radio traffic (Payload):
• AES 128. The algorithm AES 128 (Advanced Encryption Standard) is used for the encryp-
tion. The algorithm has a fixed block size of 128 bits and a 128-bit key.
• AES 256. The algorithm AES 256 is used for the encryption. The algorithm has a fixed
block size of 256 bits and a 256-bit key.
Default AES 256.
Mismatch Alarm. Radio Encryption Mismatch Alarm status. The color of the box represents the
alarm status and severity:
• Red, Orange, Yellow, Light blue. Alarm activated coupled respectively with the Critical,
Major, Minor, Warning severity.
• Green. Alarm activated coupled with the Status severity level.
Buttons
Change Encryption Key. Modify the encryption key

Button available only if the parameter System Control has value Start.
See also
Radio Encryption (command)

Radio Encryption function

The function Radio Encryption implements a module to encrypt/decrypt the data traffic (pay-
load). This makes possible to:
• Make the transmissions on air secure.
• Protect the radios which transmit and receive data.
• Safe-guard the data against internal and external threats.
The encryption function performed peer to peer allows the encryption of the radio connection
ensuring the privacy as regards the type, the addressing, the packet length and the frequency.
The Radio Encryption function has been developed to protect the data of the Ethernet users
against sniffing when such data are transferred on radio links.
The data in input to/output from the equipment on line side are unprotected Ethernet packets.
Their protection, if required, is at charge of external devices.
ALFOplus2
The ALFOplus2 equipment can be configured to operate with the Radio Encryption function ac-
tive or inactive.
When the function is active, the data encryption is based on the encryption algorithm AES128
or AES 256 (CTR mode).
When the function is inactive, no encryption algorithm is used on the flow of Ethernet data within
the system.
Activate the Radio Encryption function

Before activating the function, check that:
• The Radio payload encryptions feature is enabled on the equipment (see Equipment Fea-
tures tab).
• The user, you wish to use for the WEB LCT session, is enabled to the use of the following
security protocols: HTTPS and SNMPv3 with authentication password (see Users context,
Groups context).
• The protocol HTTPS is enabled for the equipment (see Services Status Config context,
How to implement the protocol HTTPS - ALFOplus2).
To activate the function:

• Allocate the memory for the function (see Modify the allocation of memory for Radio En-
cryption function)
• Define the encryption algorithm (see Modify the data encryption algorithm)
• Define the encryption key (see Modify the encryption key)
• Enable the function (see Modify the enabling of Radio Encryption function)
See also
Radio Encryption (command)

Clients
Ftp/Sftp. It manages the FTP and SFTP protocols.

Ftp/Sftp
The command Ftp/Sftp manages the FTP and SFTP protocols on the equipment.
Operations
Verify the operating status of the FTP and SFTP protocols
Enable/disable the FTP and/or SFTP protocol
Modify the FTP access credentials
Modify the SFTP access credentials
GUI
Ftp/Sftp context
See also
SSH protocol (info)
Verify the operating status of the FTP and SFTP protocols
1. Select Main > Security Management > Clients > Ftp/Sftp.

The Ftp/Sftp context displays the operating status of the protocols FTP and SFTP.
WARNING If the operator enables the protocols FTP and SFTP at the same time, the system will automat-
ically use the most secure protocols (SFTP).
2. To ENABLE the protocol:

• FTP, set, into the Ftp area, the Enable value (Service Status parameter).
• SFTP, set, into the Sftp area, the Enable value (Service Status parameter).
3. To DISABLE the protocol:

• FTP, set, into the Ftp area, the Disable value (Service Status parameter).
• SFTP, set, into the Sftp area, the Disable value (Service Status parameter).
Modify the FTP access credentials
WARNING Operation meaningful only if the management of FTP protocol is active and the equipment op-
erates as SSH Client.
The default FTP credentials are: user Anonymous, no password.
The change of FTP credentials is valid only for the current WEB LCT session. When the WEB LCT page is
re-opened, the default credentials are used.

2. In Ftp area, press Reset Credentials.
3. Type, in the box User, the new user name (alphanumeric string with minimum 1 and maximum 31 char-
acters).
4. Type, in the box Password, the new access code (alphanumeric string with minimum 1 and maximum
31 characters).
Modify the SFTP access credentials
WARNING Operation meaningful only if the management of SFTP protocol is active and the equipment op-
erates as SSH Client.
The default SFTP credentials are the same used by user to access to WEB LCT page.
The change of SFTP credentials is valid only for the current WEB LCT session. When the WEB LCT page is
re-opened, the default credentials are used.
2. In Sftp area, press Reset Credentials.
3. Type, in the box User, the new user name (alphanumeric string with minimum 1 and maximum 31 char-
acters).
4. Type, in the box Password, the new access code (alphanumeric string with minimum 1 and maximum
31 characters).

Ftp/Sftp context
The context displays the operating status of the FTP and SFTP protocols.
Parameters
FTP
Service Status. Operative status of the FTP protocol:
SFTP
Service Status. Operative status of the SFTP protocol:
Buttons
FTP
Reset Credentials. Modify the FTP access credentials
SFTP
Reset Credentials. Modify the SFTP access credentials
See also
Ftp/Sftp (command)
SSH protocol (info)

EQUIPMENT
Radio Configurator. It displays the radio configuration present on the equipment.

BW & Mod./Link ID. It manages the parameters relevant to modulation/capacity, adaptive modulation
and Link identification number.
General Preset. It manages the modem and radio parameters.
Xpic. It manages the XPIC function.

Radio Configurator
The command Radio Configurator displays the radio configuration present on the equipment.
Operations
Verify the Radio Link configuration
Create a Radio Link
Modify a Radio Link
Delete a Radio Link
GUI
Radio Configurator context
See also
Radio Link (info)
Verify the Radio Link configuration
1. Select Equipment > Radio Configurator.

The Radio Configurator shows the Radio Link(s) defined for the equipment.
Create a Radio Link
WARNING Operation not available if all the Radio ports have been already used for other Links.
If you wish to configure the equipment with two Radio Links connected to the same site - 2x(1+0) - you
have to create two different Radio Links in configuration 1+0.
2. Select Create New Link and press Next>.

3. Set, in the Select Link Type box, the Radio Link type you want to create:
• 1+0. Radio Link in unprotected configuration.
• 2+0 XPIC. Radio Link realized with two isofrequential transceivers which transmit on orthogonal
polarizations at the same time.
4. Set, in the Link Name box, the name of the Link (alphanumeric string with minimum 1 and maximum
32 characters).
By default, the name Link <progressive number> is suggested.
5. In the table Available Radio, select the wished TRX’s according to the set type of Radio Link. In detail,
for the Radio Link in configuration:
• 1+0, select TRX A or TRX B.
• 2+0 XPIC, select TRX A and TRX B.
Press <Prev to come back to previous step.
6. Press:
• Next, to set the radio parameters of the Link.
• Done, to create the Radio Link (to set the radio parameters see BW & Mod./Link ID and Radio
Branch).

If at least one parameter has not been properly set, the button Done and Next are not available.
The message This feature is not enabled indicates that the XPIC feature is disabled (see Equipment
Features tab).
7. If selected the button:

• Next, continue the procedure.
• Done, the Radio Link is created and displayed in the table Current Radio Configuration.
8. Set, in the Bandwidth box la reference band.

9. Set, in the Modulation box, the reference modulation.
10.Press:
• Next, to set the duplex frequency of the Link.
• Done, to create the Radio Link.
The message This feature is not enabled indicates that the feature Upgrade up to... specific for the set
band/modulation is disabled (see Equipment Features tab).
11.If selected the button:
• Done, the Radio Link is created and displayed in the table Current Radio Configuration.
12.Set, in the Duplex Frequency Selection table, the duplex frequency (MHz) for the available Radio.
In detail, if the box displays the wording:
• Select Duplex, the parameter can be set.
The displayed value is always positive, independently from the position of the transmission fre-
quency with respect to the receiving frequency.
• Not Available, the parameter is not available.
• HW Failure, the parameter cannot be set due to hardware failure.
13.Press Done.
The Radio Link is created and displayed in the table Current Radio Configuration.
If at least one parameter has not been properly set, the button Done is not available.
Modify a Radio Link
WARNING Operation available if at least one Radio Link is defined.

If the equipment is configured with two different Radio Links in configuration 1+0 (radio configuration
2x(1+0) the Radio Links cannot be modified. If you wish to modify the radio configuration of a Link, it is
necessary to remove one Radio Link and then modify the second Link.
2. Select Modify a Link and press Next>.
3. Set, in the Current Link box the Radio Link you want to modify.
4. Set, in the New Link Type box, the new type of the Radio Link.
Depending on the configuration of the Radio Link selected in the previous step, different values will be
available as indicated here below.
Current Link New Link Type
1+0 2+0 XPIC

2+0 XPIC 1+0
The wording No Configurations means that the Radio Link type cannot be changed.
5. In the table Available Radio, select the wished TRX’s depending on the new type of Radio Link:
• 1+0, select TRX A or TRX B.

• 2+0 XPIC, select TRX A and TRX B.
6. Press:
• Next, to set the radio parameters of the Link.
• Done, to complete the modification of the Radio Link (to set the radio parameters see BW &
Mod./Link ID and Radio Branch).
The message This feature is not enabled indicates that the XPIC feature is disabled (see Equipment
Features tab).
7. If selected the button:

• Done, the Radio Link is changed and displayed in the table Current Radio Configuration.
8. Set, in the Bandwidth box la reference band.
9. Set, in the Modulation box, the reference modulation.
10.Press:
• Next, to set the duplex frequency of the Link.
• Done, to create the Radio Link.
The message This feature is not enabled indicates that the feature Upgrade up to... specific for the set
band/modulation is disabled (see Equipment Features tab).
11.If selected the button:
• Done, the Radio Link is changed and displayed in the table Current Radio Configuration.
12.Set, in the Duplex Frequency Selection table, the duplex frequency (MHz) for the available Radio.
In detail, if the box displays the wording:
• Select Duplex, the parameter can be set.
The displayed value is always positive, independently from the position of the transmission fre-
quency with respect to the receiving frequency.
• Not Available, the parameter is not available.
• HW Failure, the parameter cannot be set due to hardware failure.
13.Press Done.
The Radio Link is changed and displayed in the table Current Radio Configuration.
If at least one parameter has not been properly set, the button Done is not available.
Delete a Radio Link
WARNING Operation available if at least one Radio Link is defined.
2. Select Delete a Link and press Next>.

3. Select ( ), in the Select Link to Delete table, the Radio Link(s) you want to delete.
4. Press Done.
The Radio Link is removed from the table Current Radio Configuration.

The context shows the radio configuration present on the equipment.
Parameters
CURRENT RADIO CONFIGURATION
Link#. Number of the Radio Link.
Link Name. Name of the Radio Link.
Link Type. Type of the Radio Link:
• 1+0. Radio Link in unprotected configuration.
• 2+0 XPIC. Radio Link realized by two isofrequential transceivers which trans-
mit on orthogonal polarization at the same time.
Radio. Transceivers on the equipment: TRX A, TRX B.
Radio Ports. Radio port which every single transceiver is connected to.
Select Operation. Operations for the management of the Radio Links:
Create New Link. Create a Radio Link
Modify a Link. Modify a Radio Link
Delete a Link. Delete a Radio Link
An option in grey is not available in the specific context.
Buttons
Prev. During an operation, it allows going back to the previous step.
Next. During an operation, it allows going to the next step.
Done. Confirm the changes.
See also
Radio Configurator (command)
Radio Link (info)

Radio Link (info)
ALFOplus2 - Radio Link

ALFOplus2 is an double channel outdoor radio system (Dual Channel Full Outdoor) for Ethernet
transport which houses, within a single unit, two radio transceivers.
The equipment manages the radio configuration 1+0, 2+0 XPIC or 2x(1+0) (Radio Link).
1+0
The Radio Link in configuration 1+0 uses a single transceiver.
In this configuration, the radio offers no protection against the hardware failures.
2x(1+0)
The equipment in radio configuration 2x(1+0) uses two transceivers connected to the same site.
In this configuration, two different Radio Links in configuration 1+0 have to be defined, which
use two different frequencies.
The two Radio Links are automatically aggregated by system in such a way to create a single
Bundle routed into the same direction.
The radio parameters can be independent.
2+0 XPIC
The Radio Link in configuration 2+0 XPIC uses two transceivers which transmit on two polariza-
tions of one antenna using the same frequency (functionality XPIC - Cross Polarization Interfer-
ence Cancellation).
In this configuration, one Radio Link in configuration 2+0 XPIC.
The two transceivers are aggregated in such a way to create a single Bundle routed into the
same direction.
The creation of the Radio Link must be executed by the operator via WEB LCT (see Create a
Radio Link). Once created, a Radio Link can be changed or deleted (see Modify a Radio Link and
Delete a Radio Link).
See also
Radio Configurator (command)

BW & Mod./Link ID
WARNING Command available only with at least one Radio Link defined.
For the correct operation of the Radio Link, it is necessary that all the parameters of the considered context
have the same values both on the local and on the remote equipment.
The parameter setting can be performed according to logical groups. For instance, you can change the pa-
rameters of the Bandwidth & Modulation area and confirm, but you cannot change one parameter of the
Bandwidth & Modulation area and one parameter of the ACM Engine Configuration area and confirm. The
system allows changing the parameter of the Bandwidth & Modulation area and confirm; only later you can
change the parameter of the ACM Engine Configuration area and confirm.
For the equipment with Radio Link in 1+0 or 2+0 XPIC configuration is present the BW & Mod./Link ID
command. For the equipment in 2x(1+0) radio configuration there are more BW & Mod./Link ID <Radio
Link name> commands, one per every single Radio Link.
The BW & Mod./Link ID command manages the parameters relevant to modulation/capacity, adaptive
modulation and Link identification number.
Operations
Verify the reference band/modulation, the operating status and the configuration parameters of
the adaptive modulation
Modify the reference band
Modify the reference modulation
Modify the operating status of the adaptive modulation
Modify the lower threshold and the upper threshold of the modulation (ACM enabled)
Verify/modify the Link identification number
GUI
BW & Mod./Link ID context
Verify the reference band/modulation, the operating status and the configuration
parameters of the adaptive modulation
1. Select Equipment > BW & Mod./Link ID.

The Modulation & Capacity tab displays the reference band/modulation, the operating status and the
configuration parameters of the adaptive modulation.

The Bandwidth parameter indicates the current reference band.

The message This Feature is not enabled! indicates that the Upgrade up to... feature is disabled (see


The Reference Modulation parameter indicates the current reference modulation.

The modulation 4096QAM is not available for 14MHz and 20MHz channels.

The message This Feature is not enabled! indicates that the Upgrade up to... feature is disabled (see

The ACM Engine parameter indicates the operating status of the adaptive modulation.
2. To change the parameter, select the option:

• Disabled. Adaptive modulation disabled.
• Enabled. Adaptive modulation enabled.
WARNING Operation available only if the adaptive modulation is enabled.

The Upper Profile and Lower Profile parameters respectively indicates the upper threshold and the lower
threshold of the ACM profile (code and modulation).
2. To change the parameters Upper Profile and Lower Profile, select the value relevant to the wished mod-
ulation.
2. Select the Local Link ID tab.

The Local Link ID parameter indicates the Link identification number.
3. To change the parameter, type the new value in the box (value between 1 and 255).
Set the value 0 to not use the Link identifier.

The setting so executed does NOT automatically modify also the identification number of the remote
equipment.

BW & Mod./Link ID context
WARNING Context available only for equipment with at least one Radio Link defined.
For the equipment with Radio Link in 1+0 or 2+0 XPIC configuration, the BW & Mod./Link ID command
is available which opens the BW & Mod./Link ID context. For the equipment in 2x(1+0) radio configuration
there are more BW & Mod./Link ID <Radio Link name> commands. Every command opens a context
area BW & Mod./Link ID <Radio Link name> containing the parameters relevant to the specific Radio Link.
The context displays the parameters relevant to modulation/capacity, adaptive modulation and Link iden-
tification number.
Tabs
Modulation & Capacity tab. Reference band/modulation, operating status and configuration of
the adaptive modulation.
Local Link ID tab. Link identification number.
Buttons
See also
BW & Mod./Link ID (command)
Modulation & Capacity tab
The tab displays the reference band/modulation, the operating status and the configuration parameters of
the adaptive modulation.
Parameters
BANDWIDTH & MODULATION
Bandwidth. Radio channelling.
Reference Modulation. Modulation.
The modulation 4096QAM is not available for 14MHz and 20MHz channels.
ACM ENGINE CONFIGURATION

ACM Engine. Operating status of the adaptive modulation:
• Enabled. The adaptive modulation is enabled.
• Disabled. The adaptive modulation is disabled.
Lower Profile / Upper Profile. Respectively upper and lower thresholds of the ACM
profile (code and modulation).
Parameter available only if the adaptive modulation is enabled.
Table
The ACM Table shows, for each ACM level, the capacity used by Ethernet tributaries. Depending
on the operating status of the adaptive modulation, one or more profile will be available. If the
adaptive modulation is:
• Disabled. The table contains only the ACM profile relevant to the reference modulation
(Bandwidth & Modulation).
• Enabled. The table contains all the ACM profiles. Among these, the profile included
between the minimum and the maximum modulation are available.
For each ACM profile is pointed out:
Active Modulation. Availability modulations.
Ethernet Capacity. Capacity used by the Ethernet tributaries.

Global Capacity. Total radio pipe capacity associated to the ACM profile.
Update and settings parameters

When the context is opened, the values present in the tab refer to the currently selected refer-
ence band/modulation.
If the currently selected reference band/modulation is modified, it is possible that some param-
eters are disabled. In order to display the parameters relevant to the new selected band, it is
necessary to confirm (Apply button) the new reference band/modulation.
The parameter setting can be performed according to logical groups. For instance, you can
change the parameters of the Bandwidth & Modulation area and confirm, but you cannot change
one parameter of the Bandwidth & Modulation area and one parameter of the ACM Engine Con-
figuration area and confirm. The system allows changing the parameter of the Bandwidth & Mod-
ulation area and confirm; only later you can change the parameter of the ACM Engine
Configuration area and confirm.
WARNING For the correct operation of the Radio Link, it is necessary that all the parameters of
the considered context have the same values both on the local and on the remote equipment.
See also
Local Link ID tab
The tab displays the Link identification number.
Parameters
Local Link ID. Link identification number.
Set the value 0 to not use the Link identifier.
See also

General Preset
WARNING Command available only for equipment with at least one Radio Link defined.
For the equipment with a single Radio Link, the General Preset command is present. For the equipment
with more Radio Links, there are more General Preset <Radio Link name> commands, one for every
single Radio Link.
The General Preset command manages the modem and radio parameters.
Operations
Verify/modify the threshold level of the signal at reception
Verify/modify the radio Link label
GUI
General Preset context
1. Select Equipment > General Preset.

The Rx Signal Level Alarm Threshold: <current value> dBm parameter indicates the threshold level of
the signal at reception. Under this threshold level, it is activated the relevant alarm.
2. To change the parameter, move the cursor to the wished level.
1. Select Equipment > General Preset.

The Link Label parameter indicates the label that identifies the radio Link.
2. To change the parameter, type the new label (alphanumeric string with maximum 30 characters).
The operation changes also the Link Name value present in the Radio Loop & Cmd context.

General Preset context
For the equipment with a single Radio Link, the General Preset command is present, which opens the
General Preset context. For the equipment with more Radio Links, there are more General Preset <Radio
Link name> commands. Every command opens the General Preset <Radio link name> context containing
the parameters relevant to the specific Radio Link.
The context displays the modem and radio parameters.
Parameters
POWER THRESHOLD
Rx Signal Level Alarm Threshold: <current value> dBm. Threshold of the signal at
reception.
Link Label. Label that identifies the radio Link.
Buttons
See also
General Preset (command)

Xpic
WARNING Command available only with Radio Link in 2+0 XPIC configuration.
The Xpic command manages the XPIC function.
Operations
Verify the configuration parameters of the XPIC function
Disable temporarily the function XPIC for a single transceiver
Restore the XPIC function of the single transceiver
Enable/disable XPIC fault management procedure (FMP)
Restore the function XPIC after a fault detection
GUI
Xpic context
See also
XPIC function (info)
Verify the configuration parameters of the XPIC function
1. Select Equipment > Xpic.

The Xpic context displays the configuration parameters of the XPIC function.
WARNING Operation of maintenance (MAN. OP).
2. To disable temporarily the function XPIC of:

• Transceiver A, select the Disable value (TRX A parameter).
• Transceiver B, select the Disable value (TRX B parameter).
3. Press Apply.
A message warns that you are executing a forcing and shows the current setting of timeout.
4. Confirm the operation.

The activation of the forcing activates the MAN. OP alarm. If the equipment is switched off and, then,
switched on, the forcing results inactive, independently from the previous setting.

2. To restore the XPIC function of the:
• Transceiver A, select the Enable value (TRX A parameter).
• Transceiver B, select the Enable value (TRX B parameter).
2. To ENABLE the fault management procedure (FMP), select the Enable value (Status parameter).
To DISABLE the procedure, select the Disable value (Status parameter).
Restore the function XPIC after a fault detection
2. Press Reset Procedure and confirm.

Xpic context
WARNING Context available only for equipment with Radio Link in 2+0 XPIC configuration.
The context displays the configuration parameters of the XPIC function.
Parameters
XPIC
TRX A. Activation of XPIC function for transceiver A:
• Enable. Function active.
• Disable. Function temporarily deactivated (manual operation).
TRX B. Activation of XPIC function for transceiver B:
• Disable. Function temporarily deactivated (manual operation).
FAULT MANAGEMENT PROCEDURE
Status. Status of XPIC fault management procedure (FMP):
• Disable. FMP procedure is inactive.
• Enable. FMP procedure is active.
When XPIC fault management procedure is active, the detection of a fault on a transceiv-
er and the consequent action automatically executed by FMP procedure to save the other
transceiver are pointed out by the faults present in the Fault Management Procedure ar-
ea. If a box becomes red, orange, yellow, light blue or green (depending on the severity
of the relevant to the relevant alarm), the box:
TRX A FMP: Tx Off Under Remote End Request, indicates that, after the de-
tection of a fault on one of the transceivers belonging to Link A, the FMP procedure
has switched off the TRX A from the local terminal.
TRX A FMP: Xpic Disable, indicates that, after the detection of a fault on one of
the transceivers belonging to Link A, the FMP procedure has forced the disabling
of the XPIC function of the TRX A from the local terminal.
TRX B FMP: Tx Off Under Remote End Request, indicates that, after the de-
tection of a fault on one of the transceivers belonging to Link B, the FMP procedure
has switched off the TRX B from the local terminal.
TRX B FMP: Xpic Disable, indicates that, after the detection of a fault on one of
the transceivers belonging to Link B, the FMP procedure has forced the disabling
of the XPIC function of the TRX B from the local terminal.
When the box is grey, this means that the specific fault has not been detected.
XPD
TRX A. Value of Cross Polar Discrimination (XPD) of the transceiver A.
XPIC systems use two different polarizations to transmit two independent signals: H
(Horizontal) and V (Vertical), by means of double input antenna or of the OMT (Ortho
Mode Transducer) module embedded in the ALFOplus2 unit.
Depending on the antenna aiming, a residual of the signal H can reach the polarization
V and vice versa. The power ratio between the useful signal and the residual signal of the
other polarization is the XPD value.
This value is useful to perform the proper aiming of the antenna by means of the rotation
of the OMT module (inside the radio or the antenna) on the pole support.
TRX B. Value of Cross Polar Discrimination of the transceiver B.
Buttons
Reset Procedure. Restore the function XPIC after a fault detection

See also
Xpic (command)

XPIC function
The function XPIC (Crosspolar Interference Canceller) is a modem functionality which allows us-
ing the double polarization (vertical and horizontal) in the transmission system.
In this way, exploiting two polarizations, the transmission capacity of the Radio Link can be dou-
ble using a single frequency.
WEB LCT
In relation to XPIC function, through GUI it is possible:
• To disable temporarily the function XPIC for every single TRX (Disable temporarily the
function XPIC for a single transceiver) and then to re-enable it (Restore the XPIC
function of the single transceiver).
Disabling the function XPIC is a manual operation (MAN. OP). Remember that, if the
timeout of the manual operations is inactive, the function XPIC remains disabled until
when it is restored by the user.
• To enable and disable XPIC fault management procedure (FMP) (see Enable/disable
XPIC fault management procedure (FMP).
In case of detection and signalling of a fault, the function XPIC can be restored (see
Restore the function XPIC after a fault detection).
FMP procedure
Purpose of the FMP (Fault Management Procedure) procedure is to identify a malfunction caused
by equipment faults and by equipment faults and to preserve the horizontal or vertical branch
where there are not problems
The procedure differentiates the alarms due to external causes (e.g., fading) from those due to
equipment faults.
The activation of the FMP procedure involves the switch-off of a transmitter and the disabling of
the Xpic inputs.
The condition is permanent and only an operator by means of WEB LCT or WEB NMS
can restore the normal operating condition.
See also
Xpic (command)
Xpic context

BASE BAND
Ethernet. It manages the Ethernet Switch configuration: port physical Layer, layer 2 forwarding, VLAN
settings, LLF, Link Aggregation, STP/RSTP, interface statistics.
DCN. It manages the configuration of equipment management parameters: IP addressing and Routing
Table.

Ethernet
Bridge Mode Conf.. It manages the Bridge mode (according to IEEE 802.1ad) of the Ethernet Switch.
Port Manager. It manages the ports configuration of the Switch.
VLAN. It manages the virtual LAN (VLAN) configuration.
Prov. Bridge-VLAN. It manages the parameters relevant to VLAN’s when the Switch is in Provider Edge
Bridge modality.
Prov. Bridge-EtherType. It manages the EtherType values in the S-Tag field of the Ethernet ports.
Header Compression. It manages the compression of the headers of the Ethernet packets of streams
on the ports of a Radio Link.
RSTP. It manages the Spanning Tree Protocol.
LLF. It configures the operation of LLF functionality for the equipment.
Queue Depth. It manages the depth of the output queues.
LA Manager. It manages the Link Aggregation module.
Statistics. It displays the trend of the traffic on the Ethernet ports displaying the counters of packets/
bytes in input/output. The counters are based on the standard RFC 1213 (Interfaces group) and RFC
1284 (Ethernet-like Statistics group).

Bridge Mode Conf.
The Bridge Mode Conf. command manages the Bridge mode (according to IEEE 802.1ad) of the Ethernet
Switch.
Operations
Verify the Bridge mode of the Ethernet Switch
Modify the Bridge mode of the Ethernet Switch
GUI
Bridge Mode Conf. context
Verify the Bridge mode of the Ethernet Switch
1. Select Base Band > Ethernet > Bridge Mode Conf.

The Bridge Mode Conf. context displays the current Bridge mode the Switch.
WARNING The operation involves the equipment restart. When the equipment restarts, the Ethernet Switch
shall be reconfigured.
Before performing the operation, it is necessary to disable the Spanning Tree protocol, if in use (see RSTP).
1. Select Base Band > Ethernet > Bridge Mode Conf.
2. In the Bridge Mode box, select the option:

• Customer Bridge. The Switch is in Customer Bridge mode.
In this mode, the Switch operates as a Bridge 802.1Q VLAN. The port of type Customer Bridge
is supported.
This mode is supported for compatibility with the networks that do not manage the Service Tag
(S_Tag). Moreover, in this mode, the transport on the Radio Link is more efficient, because a
double Tag is not added.
• Provider Bridge (802.1ad). The Switch is in Provider Bridge mode.
In this mode, the Switch operates as a Bridge Q-in-Q (system composed by a single S-VLAN
component, actuated in compliance with clause 5 of IEEE Standard 802.1Q). The ports of type
Provider Network and Provider Network (Proprietary) are supported.
• Provider Edge Bridge. The Switch is in Provider Edge Bridge mode.
In this mode, the Switch operates as Provider Edge Bridge 802.1ad with a S-VLAN component
and, at least, one C-VLAN component. The ports of type Provider Network, Provider Network
(Proprietary), Customer Network and Customer Edge are supported.
In Provider Bridge and Provider Edge Bridge modalities, the Ethernet Service model is used to describe
the traffic packets according to the requirements of Metro Ethernet Forum (MEF 10.2 and MEF 6.1).

Bridge Mode Conf. context
The context displays the Bridge mode (according to IEEE 802.1ad) of the Ethernet Switch.
Parameters
Bridge Mode. Operating modality of the Ethernet Switch:
• Customer Bridge. The Switch is in Customer Bridge mode.
In this mode, the Switch operates as a Bridge 802.1Q VLAN. The port of type Cus-
tomer Bridge is supported.
• Provider Bridge (802.1ad). The Switch is in Provider Bridge mode.
In this mode, the Switch operates as a Bridge Q-in-Q (system composed by a single
S-VLAN component, actuated in compliance with clause 5 of IEEE Standard 802.1Q).
The ports of type Provider Network and Provider Network (Proprietary) are supported.
• Provider Edge Bridge. The Switch is in Provider Edge Bridge mode.
In this mode, the Switch operates as Provider Edge Bridge 802.1ad with a S-VLAN
component and, at least, one C-VLAN component. The ports of type Provider Net-
work, Provider Network (Proprietary), Customer Network and Customer Edge are
supported.
In Provider Bridge and Provider Edge Bridge modalities, the Ethernet Service model is used to
describe the traffic packets according to the requirements of Metro Ethernet Forum (MEF 10.2
and MEF 6.1).
Buttons
See also
Bridge Mode Conf. (command)

Port Manager
The Port Manager command manages the configuration of the Switch ports.
Operations
Verify the Ethernet ports configuration
Modify the enabling status of a port
Activate the loop on line side of a port
Deactivate the loop on line side of a port
Modify the activation state of the autonegotiation for a port
Restart the auto negotiation procedure for a port
Modify the transmission speed of a port
Modify the inversion status of the Tx and Rx lines of a port
Modify the maximum dimension of the packet accepted by a ports
Modify the Bridge Port Type for a port
Verify the optical module configuration of the Ethernet ports
Verify the flow control configuration of the Ethernet ports
Verify/modify the traffic class which a packet, in input from a port, is assigned to, depending on
its priority (User Priority)
Verify the status of the ports as regards the Link Aggregation function
Verify the parameters for the Tunneling management
GUI
Port Manager context
Verify the Ethernet ports configuration
1. Select Base Band > Ethernet > Port Manager.

The Port Manager context displays the configuration of the Ethernet ports.
2. In the Admin State box, select the option:

• Disabled. The port is not enabled to use: the port does not transmit/receive traffic.
• Enabled. The port is enabled to use: the port transmits/receives traffic.
The port cannot transmit/receive traffic if the physical connection does not work (Link Status -
Down).


Before activating a loop, it is suggested to verify that the timeout of the manual operations is set. If the
timeout is not active, the loop will be active until its deactivation by the user, the switch-off/switch-on of
the equipment or the equipment reset.
Operation available only if the port is enabled to use (Admin State - Enabled).
2. Set the Loopback value in the Admin State box relevant the wished port.
3. Press Apply.

The activation of the loop activates the MAN. OP alarm. If the equipment is switched off and, then,
switched on, the loop results inactive, independently from the previous setting.
2. Set the Enabled or Disabled value in the Admin State box relevant the wished port.
WARNING Operation meaningful only for the line ports of the Switch.
Remember that a peer-to-peer connection works correctly if the two peers have set the same modality for
the autonegotiation management.
The port with optical interface can negotiate only the transmission speed of 1Gb. If the user activates the
autonegotiation for an optical port with speed of 2.5Gb, the system automatically will re-configure the port
transmission speed to 1Gb.
2. In the Auto Neg. box relevant the wished port, set the box:
• Active ( ). The autonegotiation is enabled. The port negotiates the transmission speed with the
peer at the other end of the Link, in order to find the optimal mutual connectivity. In autonego-
tiation, the Full Duplex without flow control is proposed by default.
The port with optical interface can negotiate only the transmission speed 1Gb.
• Inactive ( ). The autonegotiation is disabled. The port uses the transmission speed configured
in the Speed box (see Modify the transmission speed of a port), the flow control configured in
the Data Flow tab, while the operation modality is Full Duplex.

Restart the auto negotiation procedure for a port
WARNING Operation available only if autonegotiation is enabled (Auto Neg. - ).
2. In the Auto Neg. box relevant the wished port, press Restart and confirm.
WARNING Operation available only with autonegotiation disabled (Auto Neg. - ).

If the autonegotiation is enabled, the speed is automatically configured according to the hardware after
the negotiation with the peer at the other end of the connection.
2. In the Speed box relevant the wished port, select the wished option.
If selected a port with electrical interface, the following values are available:
• 100 Mbps. The data transmission speed through the port is 100 Mbit/s.
• 10 Mbps. The data transmission speed through the port is 10 Mbit/s.
• 1 Gbps. The data transmission speed through the port is 1 Gbit/s.
If selected a port with optical interface, the following values are available:
• 1 Gbps. The data transmission speed through the port is 1 Gbit/s.
• 2.5 Gbps. The data transmission speed through the port is 2.5 Gbit/s.
Operation available only if the SFP optical module supports both the options.
WARNING Operation available only for line ports with electrical interface and disabled (Admin State - Dis-
abled).
2. In the MDI/MDIX box relevant the wished port, select the option:
• MDI. The inversion of the Tx and Rx lines is not active (Network Interface Card modality).
• MDIX. The inversion of the Tx and Rx lines is active (Switch modality).
• Auto. The inversion of the Tx and Rx lines is active in automatic modality.
WARNING Operation available only for the disabled ports (Admin State - Disabled) not belonging to a LAG.
2. In the MTU box relevant the wished port, set a number between 46 and 12266.

The value must correspond to the maximum dimension (in byte) of the data field accepted by the in-
terface without the heading bytes Ethernet and CRC.

The message Unable to set MTU for port... indicates that the selected port belongs to a LAG (see LA
Manager). For these ports, the maximum size of the accepted packet cannot be changed. To change it,
the user has to remove the port from the LAG and then change the relevant value of MTU.
WARNING Operation available only if the current Bridge modality of the Switch is Provider Bridge (802.1ad)
or Provider Edge Bridge (see Bridge Mode Conf. context).
In Customer Bridge modality the port is always of type Customer Bridge.
For the line Ethernet ports, this operation involves the re-configuration of the following port parameters to
the default values: Auto Neg., MTU and Ingress Filtering.
If the port belongs to one LAG, the operation is not available at single port level, but only at Link Aggre-
gation level (see LA Manager).
2. In the Bridge Port Type box relevant the wished port, select the wished option.
If the Switch mode is Provider Bridge (802.1ad), the following options are available:
• Provider Network. Port where S-TAG’s (NNI) are observed and managed if the equipment im-
plements a Provider Bridge or a Provider Edge Bridge. More C-TAG’s can be present within one
S-TAG.
• Provider Network (Proprietary). Not standard port which allows the management of the packets
with C-Tag (EtherType 0x8100) or without Tag within a Provider or Provider Edge Bridge con-
text. It is used for the forwarding of the Management packets from/to the equipment controller.
If the Switch mode is Provider Edge Bridge, the following options are available:
S-TAG.
• Customer Network (port-based). Port which allows the routing of the traffic of a single user, in
case of Provider Edge Bridge. All the packets with C-TAG received on this port are routed on a
single S-VLAN.
If this type of port is selected, the relevant parameter Acceptable Frame Type must be set to
value UnTagged and Priority Tagged (see Port Settings tab).
• Customer Edge - (c-tagged). Port which allows the routing of the traffic of a single user already
associated to one C-TAG, in case of Provider Edge Bridge.
Verify the optical module configuration of the Ethernet ports
2. Select the Optical tab.

The tab displays the configuration of the SFP optical module relevant to Ethernet ports with optical in-
terface available on the equipment.

Verify the flow control configuration of the Ethernet ports
WARNING In the current equipment version, the flow control for the line ports is not available, while for
the port to the Radio it is assigned by default.
The flow control is implemented in the Ethernet connections in Full Duplex modality by means of the com-
mand PAUSE.
2. Select the Data Flow tab.

The tab displays the configuration of the flow control.
Verify/modify the traffic class which a packet, in input from a port, is assigned to, depending
on its priority (User Priority)

2. Select Traffic Class 802.1p Mapping tab.
The tab contains a table which indicates, for each port, the traffic classes which a packet in input is
assigned to depending on its priority 802.1p within Tag VLan (field User Priority).
Tab.3 displays the default values.
3. To change the association priority-traffic class relevant to the packets in input from a port, execute one
of the following actions:
• Double click on the port.
• Select the row relevant to the port and press Show.
The Traffic Class Mapping window shows a table which indicates the traffic class (columns Classes)
which the priority 802.1p (rows Priority) is assigned to, for the packets in input to the selected port.
4. In the table, select the option corresponding to the wished combination: priority value - traffic class.
For the same priority value, only one class can be selected.
The values of the traffic class range from 0 to 7. Every single value represents a type of traffic:
• 0 - Best effort. Traffic not sensitive to QoS metric.
• 1 - Background. Traffic not interfering with the use of the network by users and applications.
• 2 - Standard (spare traffic). Traffic more important than that of Background type, but less im-
portant than the Excellent Load type.
• 3 - Excellent load. Traffic representing the best service offered to the most important customers.
• 4 - Controlled load. Traffic which must be received even when the network is overloaded.
• 5 - Video. Traffic with delay lower than 100 milliseconds (video traffic).
• 6 - Voice. Traffic with delay lower than 10 milliseconds (voice traffic).
• 7 - Network control. Traffic reserved to the network control.

Tab.3 802.1p Priority Map (Layer 2) - Default values
Regen Priority (output queue)
0 1 2 3 4 5 6 7
0 X - - - - - - -
1 - X - - - - - -
2 - - X - - - - -
Internal 3 - - - X - - - -
Priority
(802.1p) 4 - - - - X - - -
5 - - - - - X - -
6 - - - - - - X -
7 - - - - - - - X
Tab.4 indicates the default mapping of the priority IP DSCP (Differentiated Services Code Point) (Layer 3).
WARNING This setting cannot be changed by WEB LCT.
Tab.4 DSCP Priority Map (Layer 3) - Default values
Regen Priority (output queue)
0 1 2 3 4 5 6 7
000xxx X - - - - - - -
001xxx - X - - - - - -
010xxx - - X - - - - -
Internal 011xxx - - - X - - - -
Priority
(DSCP) 100xxx - - - - X - - -
101xxx - - - - - X - -
110xxx - - - - - - X -
111xxx - - - - - - - X
Verify the status of the ports as regards the Link Aggregation function
2. Select the LA Status tab.

The tab displays the current status of every port of the Ethernet Switch as regards the Link Aggregation
function (see LA Manager).
Verify the parameters for the Tunneling management
2. Select the Tunneling tab.

The tab shows the configuration of the parameters for the Tunneling management, that is the modality
for which one protocol is encapsulated within another lower level protocol.

Port Manager context
WARNING The wording [MEF Services Active] next to the name of the context indicates that MEF services
have been activated. The change of the forwarding parameters or of the port type by WEB LCT could pre-
vent its operation.
The context displays the configuration of the Switch ports.
Tabs
Physical Interface tab. General configuration of the ports.
Optical tab. Displays the SFP optical module relevant to Ethernet ports with optical interface
available on the equipment.
Data Flow tab. Configuration of the flow control.
Traffic Class 802.1p Mapping tab. Mapping between priority of the packets in input to the Switch
and the traffic classes.
LA Status tab. Status of the ports as regards the Link Aggregation function.
Tunneling tab. Configuration of the parameters for the Tunneling management.
Buttons
See also
Port Manager (command)
Physical Interface tab
The tab displays the general configuration of the ports.
Table
Every table row corresponds to a port for which are indicated:
Port. Port identifier. The ID value is a combination of slot number and the port number
(slot number/port number).
Description. Name of the port (see Tab.5).
Media. Type of interface:
• Copper. Line Ethernet port with electrical interface.
• Fiber. Line Ethernet port with optical interface.
Parameter not meaningful for the Radio port.
Link Status. Status of the physical connection between the port and a device in network:
• Up (green box). The Link works: the physical connection is active and ready
for the traffic exchange.
• Down. The Link does not work: no physical connection has been enabled or
the established physical connection is not active or is defective.
Admin State. Enabling state/loop of the port:
• Disabled. The port is not enabled to use: the port does not transmit/receive
traffic.
The port cannot transmit/receive traffic if the physical connection does not
work.

• LoopBack. The line side loop is enabled for the port.
Value available only if the port is in Enabled status.
Default Disabled.
Auto Neg. Activation state of the autonegotiation for the port. The box:
• Active ( ) indicates that the autonegotiation is enabled. The port negotiates
the transmission speed with the peer at the other end of the Link, in order to
find the optimal mutual connectivity. In autonegotiation, the Full Duplex mo-
dality without flow control is proposed.
The port with optical interface can negotiate only the transmission speed 1Gb.
In this condition, next to the box the button Restart is displayed: press it to
restart the autonegotiation procedure for the port.
• Inactive ( ), indicates that the autonegotiation is not enabled. The port uses
the transmission speed configured in the Speed box (see Modify the transmis-
sion speed of a port), the flow control configured in the Data Flow tab, while
the operation modality is Full Duplex.
Parameter not meaningful for the Radio port.
Duplex. Transmission modality of the port:
• Full. The transmission modality is Full-Duplex.
• Half. The transmission modality is Half-Duplex.
Speed. Data transmission speed through the port.
MDI/MDIX. Inversion status of the Tx and Rx lines:
• MDI. The inversion of the Tx and Rx lines is not active (Network Interface Card
modality).
• ---. Parameter not meaningful for the port (i.e. Radio port).
Parameter meaningful only for ports with electrical interface.
MTU. Maximum dimension, in byte, of the packet accepted by the port.
The displayed value is the maximum value of the data field accepted by the interface
without the heading bytes Ethernet and CRC.
Bridge Port Type. Type of Bridge port:
• Customer Bridge. Port where C-TAG’s (UNI), are observed and managed if the
equipment implements a Customer Bridge.
Option available only when the Switch is in Customer Bridge modality.
• Provider Network. Port where S-TAG’s (NNI) are observed and managed if the
equipment implements a Provider Bridge or a Provider Edge Bridge. More C-
TAG’s can be present within one S-TAG.
Option available only when the Switch is in Provider Bridge (802.1ad) modality
or Provider Edge Bridge modality.
• Provider Network (Proprietary). Not standard port which allows the manage-
ment of the packets with C-Tag (EtherType 0x8100) or without Tag within a
Provider or Provider Edge Bridge context. It is used for the forwarding of the
Management packets from/to the equipment controller.
• Customer Network (port-based). Port which allows the routing of the traffic of
a single user, in case of Provider Edge Bridge. All the packets with C-TAG re-
ceived on this port are routed on a single S-VLAN.
Option available only when the Switch is in Provider Edge Bridge modality.
• Customer Edge (c-tagged). Port which allows the routing of the traffic of a sin-
gle user already associated to one C-TAG, in case of Provider Edge Bridge.
Selecting the heading of the Port or Description column, the rows of the table are sorted in in-
creasing alphanumeric order with respect to the considered column and an arrow is displayed
with the tip directed upwards. The next selection sorts the rows in decreasing order (an arrow
is displayed with the tip directed downwards) and so on.

Buttons
Restart. Restart the auto negotiation procedure for a port.
See also
Tab.5 Ethernet ports
Name Description Interface
LAN 1 Line Ethernet port Optical

LAN 2 Line Ethernet port Optical
LAN 3 Line Ethernet port Electrical
LAN 4 Line Ethernet port Electrical
MNGT Line Ethernet port for the management Electrical
TRX Ethernet port towards the Radio -
Optical tab
The tab displays the data of the SFP (Small Form-factor Pluggable) optical module relevant to the Ethernet
ports with optical interface available on the equipment.
All parameter are read only.
Table
Fail Alarm. Status of the alarm which indicates the malfunctioning of the optical module
(Plug-in module Fail Alarm). The colour of the box displays the status of the alarm:
Vendor Name. Name of the optical module.
Vendor PN. Part number of the optical module.
Vendor SN. Serial number of the optical module.
Vendor Date. Manufacturing date of the optical module.
Wave Length (nm). Wave length (in nanometres) of the optical module.
Nominal Bit Rate (Mbps)). Nominal data transmission speed in Mbit/sec.
Link Length 9um (m). Maximum distance (in meters) of the 9/125 µm fiber supported
by the optical module.

Link Length 50um (m). Maximum distance (in meters) of the 50/125 µm fiber support-
ed by the optical module.
Link Length 62.5um (m). Maximum distance (in meters) of the 62.5/125 µm fiber sup-
ported by the optical module.
Data Flow tab
The tab displays the configuration of the flow control.

In the current equipment version, the flow control for the line ports is not available, while for the port to
the Radio it is assigned by default.
The flow control is implemented in the Ethernet connections in Full Duplex modality by means of the com-
mand PAUSE.
All parameters in the tab are read only.
Table
Flow Control Admin Status. Management of the flow control assigned by default for
the specific port:
• Disabled. The transmission/reception of the MAC packets used for the trans-
port of the command PAUSE is disabled.
• Transmit. The transmission of the MAC packets used for the transport of the
command PAUSE is enabled towards a remote device, in case of internal con-
gestion due to excess of received traffic.
• Receive. The reception from a remote device of the MAC packets used for the
transport of the command PAUSE is enabled, which interrupts the data trans-
mission if required by an external equipment.
• Transmit & Receive. The transmission/reception to/from a remote device of
the MAC packets used for the transport of the command PAUSE is enabled.
Flow Control Oper Status. It displays the management modality of the flow control
currently used by the specific port:
• Disabled. The transmission/reception of the MAC packets used for the trans-
port of the command PAUSE is disabled.
• Transmit. The transmission of the MAC packets used for the transport of the
command PAUSE is enabled towards a remote device, in case of internal con-
gestion due to excess of received traffic.
• Receive. The reception from a remote device of the MAC packets used for the
transport of the command PAUSE is enabled, which interrupts the data trans-
mission if required by an external equipment.
• Transmit & Receive. The transmission/reception to/from a remote device of
the MAC packets used for the transport of the command PAUSE is enabled.

Traffic Class 802.1p Mapping tab
The tab shows the mapping between the priority 802.1p within the Tag VLan (field User Priority) of the
packets in input to the Switch and the traffic classes managed by the equipment.
The packet received on a port with a specific priority will be forwarded according to the relevant traffic
class. For the packets without Tag, the priority is equivalent to the value of Default User Priority of the port
in input (see Port Settings tab).
Table
Priority 0. This column displays, for every single port, the traffic class which a packet
with User Priority value equal to 0 is assigned to.
Default see Tab.3.
Buttons
Show. Verify/modify the traffic class which a packet, in input from a port, is assigned to, de-
pending on its priority (User Priority)
LA Status tab
The tab displays the current status of every port of the Ethernet Switch as regards the Link Aggregation
function (see LA Manager).
The table is not populated if the parameter System Control has value Shutdown (see General Settings tab).
Table
Each row of the table corresponds to a port for which are indicated:
Port Channel State. Current status of the port as regards the Link Aggregation func-
tion:
• Up In Bundle. The port is an active member of a LAG (Link Aggregation
Group): it is operative and takes part to the aggregation.
• Standby. The port is a member of a LAG, but currently in standby. It can re-
place a port in failure within the LAG.

• Down. The port is not active, or it is active but cannot take part to the aggre-
gation because of a mismatch of the information among the LAG members.
• Up Individual. The port is operative but does not take part to any LAG.
Port Channel. Name of the LAG which the port belongs to (po<identification number>).
Tunneling tab
WARNING L2CP tunneling cannot be partially overlapped: all needed tunnelings must be enabled at the
same port. In case of:
• Cascaded Links without traffic dropping, tunneling can be enabled at the first and the last port.
• Cascaded Links with traffic dropping, tunnellings must be enabled on all intermediate ports.
The tab displays the configuration of the parameters for the Tunneling management, that is the modality
for which one protocol is encapsulated within another lower level protocol.
Parameters
MAC ADDRESS CONFIGURATION
BPDU Priority. Predefined priority for all the BPDU packets encapsulated at level 2 and
received on the tunnel ports: 0 ÷ 7.
Default 7.
STP. Destination MAC address used for the Tunneling of BPDU STP packets.
LACP. Destination MAC address used for the Tunneling of LACP packets.
Dot1x. Destination MAC address used for the Tunneling of Dot1x packets.
GVRP. Destination MAC address used for the Tunneling of PDU GVRP packets.
GMRP. Destination MAC address used for the Tunneling of PDU GMRP packets.
MVRP. Destination MAC address used for the Tunneling of MVRP packets.
MMRP. Destination MAC address used for the Tunneling of MMRP packets.
LLDP. Destination MAC address used for the Tunneling of LLDP packets.
TUNNEL STATUS
The list contains the ports of Customer Network (port-based) or Customer Edge type.
Dot1x. State of the Tunneling for Dot1x protocol:
• Peer. The Dot1x packets received by the Bridge are accepted and processed.
• Tunnel. The received Dot1x packets are transmitted in transparent mode by
the Provider network, this avoids the processing of the packets by PB’s and
PEB’s.
• Discard. The Dot1x packets received by the Bridge are dropped.
LACP. State of the Tunneling for LACP (Link Aggregation Control Protocol) protocol:
• Peer. The LACP packets received by the Bridge are accepted and processed.
• Tunnel. The received LACP packets are transmitted in transparent mode by the
Provider network, this avoids the processing of the packets by PB’s and PEB’s.
• Discard. The LACP packets received by the Bridge are dropped.
STP. State of the Tunneling for STP (Spanning Tree Protocol) protocol:
• Peer. The STP packets received by the Bridge are accepted and processed.
• Tunnel. The received STP packets are transmitted in transparent mode by the
• Discard. The STP packets received by the Bridge are dropped.

GVRP. State of the Tunneling for GVRP (GARP VLAN Registration Protocol) protocol:
• Peer. The GVRP packets received by the Bridge are accepted and processed.
• Tunnel. The received GVRP packets are transmitted in transparent mode by
PEB’s.
• Discard. The GVRP packets received by the Bridge are dropped.
GMRP. State of the Tunneling for GMRP (GARP Multicast Registration Protocol) protocol:
• Peer. The GMRP packets received by the Bridge are accepted and processed.
• Tunnel. The received GMRP packets are transmitted in transparent mode by
PEB’s.
• Discard. The GMRP packets received by the Bridge are dropped.
IGMP. State of the Tunneling for IGMP (Internet Group Management Protocol) protocol:
• Peer. The IGMP packets received by the Bridge are accepted and processed.
• Tunnel. The received IGMP packets are transmitted in transparent mode by
PEB’s.
• Discard. The IGMP packets received by the Bridge are dropped.
MVRP. State of the Tunneling for MVRP (Multiple VLAN Registration Protocol) protocol:
• Peer. The MVRP packets received by the Bridge are accepted and processed.
• Tunnel. The received MVRP packets are transmitted in transparent mode by
PEB’s.
• Discard. The MVRP packets received by the Bridge are dropped.
MMRP. State of the Tunneling for MMRP (Multiple MAC Registration Protocol) protocol:
• Peer. The MMRP packets received by the Bridge are accepted and processed.
• Tunnel. The received MMRP packets are transmitted in transparent mode by
PEB’s.
• Discard. The MMRP packets received by the Bridge are dropped.
LLDP. State of the Tunneling for LLDP (Link Layer Discovery Protocol) protocol:
• Peer. The LLDP packets received by the Bridge are accepted and processed.
• Tunnel. The received LLDP packets are transmitted in transparent mode by the
• Discard. The LLDP packets received by the Bridge are dropped.

VLAN
WARNING In the equipment, VLAN’s work in the Switch in VLAN Aware Bridging modality.
In this modality, the bridge identify the packets with TAG VLAN and can insert and remove TAG’s in the
packet heading.
The Switch operates in compliance with Standard IEEE 802.1q and 802.1ad.
The command VLAN manages the parameters relevant to the configuration and the management of the
virtual LAN’s (VLAN).
Operations
BASIC SETTINGS
Verify the basic configuration of the VLAN management
Enable/disable the learning of the addresses in the MAC Table
Modify the aging time of the addresses stored in the MAC Table
Modify the limit of MAC unicast addresses per VLAN managed by the Switch
PORT SETTINGS
Modify the type of packets accepted in input by a port/LAG
Modify the check modality (filtering) applied to the packets in input on a port/LAG
Modify the default VLAN identifier of a port/LAG (Port VID)
Modify the default value to enter in the User Priority field of the packets without priority
802.1p received on the port/LAG
STATIC VLANS
Verify the existing static VLANs
Create one or more static VLANs
Modify the configuration of a static VLAN
Delete one or more static VLANs
GUI
VLAN context
Verify the basic configuration of the VLAN management
1. Select Base Band > Ethernet > VLAN.

The Basic Settings tab displays the basic configuration of the VLAN management.
WARNING The MAC-based routing functionality in the Switch is available only if enabled this function.
The setting is common for all port of the Switch.
2. In the Global MAC Learning Status box, select the option:

• Enable. The learning of the Source Addresses in the MAC Table is enabled.
• Disable. The learning of the Source Addresses in the MAC Table is disabled. In this condition MAC
Table is not used.

WARNING Operation meaningful only if the learning of the addresses in the MAC Table (Global MAC Learn-
ing Status - Enable) is enabled.
2. In the MAC Addr Table Aging Time box, set the validity period of the MAC addresses, dynamically ac-
quired and stored in the specific table (number between 10 and 1000000 seconds).
Default 300 seconds.
2. Set, in the box Unicast MAC Learning Limit, the limit of MAC Unicast addresses per VLAN managed by
the Switch (number between 0 and 16000).
The limit represents the maximum number of different MAC unicast addresses which can be learned by
the Switch.
WARNING Operation not available for the ports of type Customer Network (port-based) or Customer Edge
(see Bridge Port Type - Physical Interface tab), which have always the value UnTagged and Priority Tagged.
2. Select the Port Settings tab.
3. In the Acceptable Frame Types box relevant the wished port/LAG, select the option:
• All. The port/LAG accepts all the following packets:
• Tagged. Packet containing, in its heading, one TPID identified as valid by the port/LAG,
one VLAN Tag different from 0 and the field User Priority.
• UnTagged. Packet containing, in its heading, one TPID identified as not valid by the port/
LAG.
• Priority Tagged. Packet containing, in its heading, one TPID identified as valid by the
port/LAG, one VLAN Tag equal to 0 and the field User Priority.
• Tagged. The port/LAG accepts only the Tagged packets. UnTagged and Priority Tagged packets
are rejected.
• UnTagged and Priority Tagged. The port/LAG accepts only the UnTagged and Priority Tagged
packets. Tagged packets are rejected.

3. In the Ingress Filtering box relevant the wished port/LAG, select the option:
• Enabled. The port/LAG accepts, in input, only packets with VLAN ID contained in VTU and the
input port/LAG must be member of this VLAN, otherwise the packet is discarded.
• Disabled. The port/LAG does not execute any check: all the packets are accepted.
WARNING The default VLAN identifier of a port/LAG is used to assign a VLAN to the UnTagged or Priority
Tagged packets received on the port/LAG itself. The parameter is used for the classification of the VLAN’s
on port basis (Port-Based VLAN classification).
3. In the PVID box relevant the wished port/LAG, set a value between 1 and 4094.
Modify the default value to enter in the User Priority field of the packets without priority 802.1p
received on the port/LAG

3. In the Default User Priority box relevant the wished port/LAG, set a value between 0 (lowest priority)
and 7 (highest priority).
Verify the existing static VLANs
2. Select the Static VLANs tab.

The tab displays the existing static virtual LANs.
Create one or more static VLANs
3. Press Add.
4. If you wish to create:

• More VLAN’s at the same time, expand the area Group Add.
Set, in the box VLAN ID Start, the identifier (between 2 and 4094) of the first VLAN of the range.
Set, in the box VLAN ID Stop, the identifier of the last VLAN of the range.
The value of VLAN ID Stop must be greater than the value of VLAN ID Start and no VLAN with
identifier between Start and Stop values must not be present in the list.
The system creates a number of VLAN’s (and inserts the corresponding rows in the table) equal
to the difference between the values of the parameters VLAN ID Stop and VLAN ID Start, with
progressive identifiers from the lowest value to the highest value, and automatically assigns the
corresponding VLAN Name using the format <Label> <identifier>.
All the VLAN’s created automatically assume the same enabling policy for the transit of packets
through the ports of the Switch.
The system guarantees the contemporary creation of maximum 100 VLANs.
• A single VLAN, set, in the box VLAN ID, the identifier (between 2 and 4094) you wish to assign
to the virtual LAN.
An identifier greater then that indicated in the field Max. VLAN ID cannot be used.
Set, in the box VLAN Name, the name (alphanumeric string, 32 characters at most) you wish to
assign to the VLAN.
The system automatically suggests, as VLAN name, VLAN <identifier>. This name can be
changed as you wish.
5. Activate ( ), in the box Member Ports, the ports enabled to the transit of packets with VLAN ID equal
to the VLAN’s one.
For every port are indicated the port identifier (slot number/port number), the port name (LAN 1, LAN
2, etc.) and the type of Bridge port (Customer Bridge, Provider Network, etc.) (see Bridge Port Type,
Physical Interface tab).
If two or more ports belong to a LAG, the list will display the LAG and not the single ports.
The label po<identification number> (for example po100) indicates a LAG.
At least one port and/or LAG must be activated to create a VLAN.
One port can be Member of more VLAN’s at the same time.
6. Activate ( ), in the box Untagged Ports, the ports/LAGs whose packets in output the Tag 802.1Q is
removed from.
7. Select, in the box Ether Type, the hexadecimal value of EtherType which the packets must have to be
identified as belonging to the VLAN:
• 0x8100. Customer VLAN Tag in according to Ieee802.1Q specifications.
• 0x88a8. Service VLAN Tag in according to Ieee802.1ad specifications.
8. In the Unicast MAC Limit box, set the maximum number of Unicast MAC addresses for single VLAN (val-
ue between 0 and 1000).

The Static VLANs tab displays the row relevant to the new VLAN.
3. Double click on the box relevant to the parameter of VLAN you wish to change.
Except for the identifier (VLAN ID), all the parameters of a VLAN can be modified (VLAN Name, Member
Ports, Untagged Ports, Ether Type, Unicast MAC Limit).
The parameter setting modes are the same pointed out in par. Create one or more static VLANs.

The changes are confirmed in Virtual Lan Config tab.

Delete one or more static VLANs
3. Select the VLAN you wish to delete.

The multiple selection can be executed using the Ctrl or Shift keys.
The system guarantees the contemporary deletion of maximum 100 VLANs.

VLAN context
have been activated. The change of parameters relevant to the VLAN management from WEB LCT could
preclude the operation of the VLAN’s themselves.
The context displays the parameters relevant to the configuration and the management of the virtual LAN’s
(VLAN).
Tabs
Basic Settings tab. Basic configuration of the VLAN management.
Port Settings tab. VLAN management parameters relevant to the physical ports available in the
equipment.
Static VLANs tab. Configuration of the existing static VLANs.
Buttons
See also
VLAN (command)
Basic Settings tab
The tab displays the basic configuration of the VLAN management.
Parameters
LEARNING OPTIONS
Learning Mode. Learning mode for the addresses in the MAC Table.
The writing Independent VLAN Learning indicates that the partition and the indicization
on VID basis of the Source Addresses in the MAC Table is enabled. The learning registers
them in a MAC Table segment whose index is the value of the VID contained in the VLAN’s
in input to the Switch and registered in VTU.
In this modality, the information learned by a VLAN are not used by other VLAN’s for the
packet forwarding.
Parameter common to all port of the Switch.
Global MAC Learning Status. Enabling status of the learning of the addresses in the
MAC Table:
• Enable. The learning of the Source Addresses in the MAC Table is enabled.
• Disable. The learning of the Source Addresses in the MAC Table is disabled. In
this condition MAC Table is not used.
Parameter common to all port of the Switch.
MAC Add. Table Aging Time. Validity period of the MAC addresses stored in the MAC
Table (expressed in seconds).
Default 300 seconds.
Unicast MAC Learning Limit. Maximum number of different MAC unicast addresses per
VLAN which can be learned by the Switch.
VLAN STATUS
Max. VLAN ID. VLAN identifier accepted by the Switch as maximum value.

Max Supported VLAN. Maximum number of VLAN’s which can be managed by the
Switch.
Num of VLANs in the System. Total number of VLAN’s currently managed by the
equipment.
See also
Port Settings tab
The tab displays the VLAN management parameters relevant to the physical ports or LAGs available in the
equipment.
Table
Each row of the table corresponds to a port or LAG.
If two or more ports belong to a LAG, the list will display the LAG and not the single ports (e.g.
if the ports LAN 1 and LAN 2 belong to the LAG po100, the list will display only the option po100
and not the options LAN 1 and LAN 2). The settings made to a channel will be automatically
performed on all the ports belonging to the LAG.
For each port/LAG are indicated:
Port. Port or channel identifier.
The port ID is a combination of slot and the port number (slot number/port number).
Description. Name of the port (see Tab.5) or LAG.
The parameter is not available for the LAGs created by WEB LCT.
Acceptable Frame Types. Types of BPDU (Bridge Protocol Data Unit) packets accepted
in input by the port/LAG and subjected to control policies (see Ingress Filtering):
• All. The port/LAG accepts all the following packets:
• Tagged. Packet containing, in its heading, one TPID identified as valid by
the port/LAG and one VLAN Tag different from 0 and the field User Priority.
• UnTagged. Packet containing, in its heading, one TPID identified as not val-
id by the port/LAG.
• Priority Tagged. Packet containing, in its heading, one TPID identified as
valid by the port/LAG and one VLAN Tag equal to 0 and the field User Pri-
ority.
• Tagged. The port/LAG accepts only the Tagged packets. The UnTagged and
Priority Tagged packets are rejected.
• UnTagged and Priority Tagged. The port/LAG accepts only the UnTagged and
Priority Tagged packets. The Tagged packets are rejected.
Default All.
The parameter has always value UnTagged and Priority Tagged for the ports of type Cus-
tomer Network (port-based) and Customer Edge (see Bridge Port Type - Physical Inter-
face tab).
Ingress Filtering. Control modality (filtering) applied to the packets in input on the
port/LAG:
• Enabled. The port/LAG accepts in input only packets with VLAN ID contained
in VTU and the port/LAG in input must be a member of this VLAN, otherwise
the packet is discarded.
• Disabled. The port/LAG performs no check: all the packets are accepted.

Default Disabled for the port and Enabled for the LAGs.
PVID. Default VLAN identifier assigned to the UnTagged or Priority Tagged packets re-
ceived on the port/LAG itself: 1 ÷ 4094.
The parameter is used for the VLAN classification on port basis (Port-Based VLAN classi-
fication).
Default User Priority. Default value to insert in the field User Priority (priority 802.1p
within Tag VLan) of the packets without priority value received on the port/LAG: 0 (low-
est priority) ÷ 7 (highest priority).
See also
received on the port/LAG
LA Manager (command)
Static VLANs tab
The tab displays the configuration of the physical ports of the Switch.
The static VLAN’s are configured per port (Port-based VLAN) differently from the dynamic VLAN’s which
are configured according to MAC address or to protocol.
During the creation of a static VLAN, one port of the Switch is assigned to the specific VLAN, so that the
device connected to that port automatically becomes member of the assigned VLAN.
Table
Each row of the table corresponds to a VLAN for which are indicated:
VLAN ID. VLAN identifier.
VLAN Name. VLAN name.
Member Ports. Ports enabled to the transit of packets with VLAN ID equal to that of the
VLAN.
For every port, the port identifier is indicated (slot number/port number) and the name
of the port (LAN 1, LAN 2, etc.).
The ports/LAGs are separated by comma.
Untagged Ports. Ports/LAGs whose packets in output the Tag 802.1Q is removed from.
For every port, the port identifier is indicated (slot number/port number) and the name
of the port (LAN 1, LAN 2, etc.).
The ports/LAGs are separated by comma.
Ether Type. Value of EtherType which the packets in input must have to be identified as
belonging to the VLAN:
Unicast MAC Limit. Number of Unicast MAC addresses for single VLAN.
Selecting the heading of the VLAN ID column, the rows of the table are sorted in increasing al-
phanumeric order with respect to the considered column and an arrow is displayed with the tip

directed upwards. The next selection sorts the rows in decreasing order (an arrow is displayed
Buttons
Add. Create one or more static VLANs
Remove. Delete one or more static VLANs
See also

Prov. Bridge-VLAN
WARNING Command available only when the Switch is in Provider Edge Bridge modality.
The command Prov. Bridge-VLAN displays the parameters relevant to the VLAN’s when the Switch is in
Provider Edge Bridge modality.
Operations
Verify the C-VID registration table (C-VID Registration)
Verify the Provider Edge Port configuration table (PEP Configuration)
GUI
Prov. Bridge-VLAN context
Verify the C-VID registration table (C-VID Registration)
1. Select Base Band > Ethernet > Prov. Bridge-VLAN.

The C-VID Registration tab shows the C-VID registration table.
Verify the Provider Edge Port configuration table (PEP Configuration)
1. Select Base Band > Ethernet > Prov. Bridge-VLAN.

The PEP Configuration tab shows the Provider Edge Port configuration table.

Prov. Bridge-VLAN context
have been activated.
The context shows the parameters relevant to the VLAN’s when the Switch is in Provider Edge Bridge mo-
dality.
Tabs
C-VID Registration tab. C-VID registration table (C-VID Registration).
PEP Configuration tab. Provider Edge Port configuration table (PEP Configuration).
Buttons
See also
Prov. Bridge-VLAN (command)
C-VID Registration tab
The tab displays the C-VID registration table (C-VID Registration).
An internal connection between one Customer Network Port (CNP) on S-VLAN component and one Provider
Edge (PEP) port on C-VLAN component is instanced for every VLAN.
The connection between CNP and PEP is set by the mutual entries in C-VID registration table (C-VID Reg-
istration) and PEP configuration table (see PEP Configuration tab).
In C-VID registration table, one entry is created for every C-VLAN supported in the C-VLAN component
associated with one Customer Edge port (CEP).
The CEP identifier and the C-VID combination identify one PEP. The entry contains (among the other pa-
rameters) a S-VID value corresponding to the PVID of CNP, which associates the PEP to a specific Customer
Network port (CNP).
Table
The list contains the ports of Customer Edge type.
C-VLAN ID. Customer VLAN ID value present in the C-TAG of the packets in input to the
specific port: 1 ÷ 4094.
S-VLAN ID. VLAN ID of the service instance which the port and the Customer VLAN ID
are mapped to: 1 ÷ 4094.
Untagged PEP. Forwarding modality of the packets, with the specific C-VID, in inputs
to the Customer Edge port through the Provider Edge port:
• TRUE. The packets are forwarded without TAG C-VLAN.
• FALSE. The packets are forwarded with a valid C-TAG and C-VID.
Untagged CEP. Forwarding modality of the packets, with the specific C-VID through the
Customer Edge port:
• TRUE. The packets are forwarded without TAG C-VLAN.
• FALSE. The packets are forwarded with TAG C-VLAN. If this is missing, it is
added.

Buttons
Add. Button not available in this version.
Remove. Button not available in this version.
PEP Configuration tab
The tab displays the Provider Edge Port configuration table (PEP Configuration).
For every VLAN, one internal connection is instanced between one Customer Network port (CNP) on S-
VLAN component and one Provider Edge port (PEP) on C-VLAN component.
The connection between CNP and PEP is set by the mutual entries in C-VID registration table (see C-VID
Registration tab) and PEP configuration table.
In PEP configuration table, one entry is created for every S-VID corresponding to one service instance ac-
cessible by the C-VLAN component.
The Customer Edge Port (CEP) identifier and the S-VID combination identify one CNP. The entry contains
(among the other parameters) one C-VID value corresponding to the PVID of PEP, which associates the
CNP to a specific PEP.
Table
The list contains the ports of Customer Edge type.
S-VID. S-VLAN identifier: 1 ÷ 4094.
P-VID. Default VLAN identifier assigned to the UnTagged packets received on the PEP
port: 1 ÷ 4094.
Default User Priority. Default priority value (User Priority) assigned to the UnTagged
packets received on the PEP port: 0 (lowest priority) ÷ 7 (highest priority).
Default 0.
Acceptable Frame Types. Types of BPDU packets accepted in input by the PEP port and
subjected to control policies (see Ingress Filtering):
• All. The port accepts all the following packets:
• Tagged. Packet containing, in its heading, one TPID identified as valid by
the port, one VLAN Tag different from 0 and the field User Priority.
• UnTagged. Packet containing, in its heading, one TPID identified as not val-
id by the port.
• Priority Tagged. Packet containing, in its heading, one TPID identified as
valid by the port, one VLAN Tag equal to 0 and the field User Priority.
• Tagged Only. The port accepts only the Tagged packets. UnTagged and Prior-
ity Tagged packets are rejected.
• Untagged & Priority Tagged. The port accepts only the UnTagged and Priority
Tagged packets. Tagged packets are rejected.
Default Admit-All.
Ingress Filtering. Control modality (filtering) applied to the packets in input on the PEP
port:
• TRUE. The port drops the packets classified to the specific C-VLAN if the port
is not a member of the C-VLAN itself.
• FALSE. The PEP port performs no check: all the packets are accepted.
Default FALSE.
COS Preservation. Enabling status, for the PEP port, of the function Class of Service
Preservation for a Service Provider:
• Enable. Function CoS preservation enabled: the mapping between the priority
of the packets in input to the Switch and the traffic classes is preserved in the
Provider network.

• Disabled. Function CoS preservation disabled: the mapping between the pri-
ority of the packets in input to the Switch and the traffic classes is not pre-
served in the Provider network.
Default Disabled.

Prov. Bridge-EtherType
WARNING Command available only when the Switch is configured in Provider Bridge or Provider Edge
Bridge modality.
The Prov. Bridge-EtherType command manages the EtherType values in the S-Tag field of the Ethernet
ports.
Operations
Verify the EtherType values in the S-Tag field of the Ethernet ports
Modify the EtherType values in the S-Tag field of a port/LAG
GUI
Prov. Bridge-EtherType context
Verify the EtherType values in the S-Tag field of the Ethernet ports
1. Select Base Band > Ethernet > Prov. Bridge-EtherType.

The Prov. Bridge-EtherType context shows the EtherType values in the S-Tag (Service Tag) field for
every Ethernet port.
If two or more ports belong to a LAG, the list will display even the LAG (po<identification number>).
In this case, the values used by the aggregated ports will be that indicated for the relevant LAG.
Modify the EtherType values in the S-Tag field of a port/LAG
WARNING Typical values of EtherType fields:

• 0x9100. Service VLAN Tag related to a “not standard QinQ protocol”.
If two or more ports belong to a LAG, the list will display even the LAG. In this case, in order to change
the values used by the aggregated ports, it is necessary to change the value of the LAG and not of the
single ports.
1. Select Base Band > Ethernet > Prov. Bridge-EtherType.
2. Set, in the field Ingress EtherType of the specific port or LAG, the hexadecimal value of EtherType which
must have the packets in input to the port/LAG.
For the port of PNP (Provider Network Port) type, the default value is 0x8100. For all the other ports,
the default value is 0x88a8.
3. Set, in the field Egress EtherType of the specific port or LAG, the hexadecimal value of EtherType which
must be applied to the packets in output from the port/LAG.
For the port of CEP (Customer Edge Port) and PNP type, the default value is 0x8100. For all the other
ports, the default value is 0x88a8.

Prov. Bridge-EtherType context
WARNING Context available only when the Switch is configured in Provider Bridge or Provider Edge Bridge
modality.
The context displays the EtherType values in the S-Tag field of the Ethernet ports.
Parameters
Each row of the table corresponds to a port or LAG (see LA Manager).
If two or more ports belong to a LAG, the list will display even the LAG. In this case, the value
used by the aggregated ports will be that indicated for the relevant LAG.
For each port/LAG are indicated:
The ID value is a combination of slot number and the port number (slot number/port
number).
Read-only parameter.
Description. Name of the port (see Tab.5) or the LAG.
Ingress EtherType. Value EtherType in the field S-Tag of the packets in input to the
port/LAG.
For the port of PNP (Provider Network Port) type, the default value is 0x8100. For all the
other ports, the default value is 0x88a8.
Egress EtherType. Value EtherType in the field S-Tag applied to the packets in output
from the port/LAG.
For the port of CEP (Customer Edge Port) and PNP type, the default value is 0x8100. For
all the other ports, the default value is 0x88a8.
Buttons
See also
Prov. Bridge-EtherType (command)

Header Compression
The command Header Compression allows managing the compression of the headers of the Ethernet
packets of streams on the ports of a Radio Link.
Operations
Verify the status of the function for the compression of the headers of Ethernet packets
Enable/disable the functionality for the compression of the headers of Ethernet packets
Verify/modify the context depth to compress in the header of the Ethernet packets
Verify/modify the parsing mode applied to the header of the Ethernet packets
GUI
Header Compression context
See also
Header Compression (info)
Verify the status of the function for the compression of the headers of Ethernet packets
1. Select Base Band > Ethernet > Header Compression.

The Header Compression context shows the status of the functionality for the radio port on the equip-
ment.

The parameter H.C. Status indicates the enabling status functionality:
• Enable. The compression of the headers of the Ethernet packets is enabled.
• Disable. The compression of the headers of the Ethernet packets is disabled.
2. To change the enabling status of the functionality, select the wished value.

The parameter Context Depth indicates the total size of the fields of the header you wish to compress.
The number of available contexts (and then the number of streams which can be managed at the same
time on the same Radio Link) changes with inverse relation to the selected context depth:
• 16 bytes (up to 2048 contexts).

2. To change the context depth, select the wished value.

The parameter Parsing Mode indicates the modality used by the compressor to parse the header of the
Ethernet packets in output from the LAN to the radio port:
• IPv4/IPv6 without C.W., EoMPLS with C.W.
• EoMPLS without C.W.
• Always IPv4/IPv6.
2. To change the parsing mode, select the wished value.

The context displays the status of the Header Compression functionality for the Ethernet packets in output
from the LANs to the radio.
The lower part of the context displays the protocols and the modes supported by the Parser of Header Com-
pression functionality.
Table
Every row of the table corresponds to one radio port for which are indicated:
Port. Name of the port (see Tab.5).
H.C. Status. Enabling status of Header Compression functionality.
• Enable. The compression of the headers of the Ethernet packets is enabled.
• Disable. The compression of the headers of the Ethernet packets is disabled.
Context Depth. The context depth is in inverse relation to the number of contexts.
Parsing Mode. Modality used by the header of the Ethernet packets in output to the ra-
dio is examined for the compression:
• IPv4/IPv6 without C.W., EoMPLS without C.W.
• EoMPLS without C.W.
• IPv4/IPv6 without C.W.
Buttons
See also
Header Compression (command)

Header Compression functionality

Packets belonging to the same stream have a great part of their header (up to 90%) that does
not change in time (IP and MAC addresses, TAG Ethernet, MPLS labels, etc).
The Header Compression hop-by-hop functionality allows storing, at the ends of a Radio Link,
all the information which repeats identical packet after packet and transmitting only the variable
fields (Sequence Number, TimeStamp, etc).
This allows achieving good gains in terms of throughput in presence of long communication
streams characterized by a great number of packets (for example, real-time communication).
In order to achieve this result, it is necessary to support a lot of streams at the same time, so
to maximise the gain.
The set of static information of the packets belonging to the same stream is stored by the com-
pression/decompression module and is defined context.
The compression function will operate in the direction from LAN to Radio, while the decompres-
sion function will operate in the opposite direction.
See also
Header Compression (command)

RSTP
The command RSTP manages the Spanning Tree protocol.
Operations
Enable/disable the use of STP/RSTP protocol for the equipment
OPERATIONS AT SWITCH LEVEL
Verify/modify the allocation of memory for the STP/RSTP function

Verify/modify the ports set for the STP/RSTP function
Verify/modify the enabling of STP/RSTP function
Verify/modify the dynamic path cost calculation functions (STP/RSTP)
Verify/modify the version of the protocol (STP/RSTP)
Verify/modify the priority assigned to the Switch (STP/RSTP)
Verify/modify the maximum number of BPDU packets in transmission (STP/RSTP)
Verify/modify the parameters for the transmission of BPDU packets (STP/RSTP)
OPERATIONS AT ETHERNET PORT LEVEL
Verify/modify the priority of a port (STP/RSTP)

Verify/modify the status of the STP/RSTP function of a port
Verify/modify the cost of the a port (STP/RSTP)
Verify/modify the interoperability of the equipment with other equipment (RSTP)
Verify the information stored by every single Switch port (STP/RSTP)
GUI
RSTP context
See also
STP/RSTP Protocol (info)
1. Select Base Band > Ethernet > RSTP.
2. In the System Control box, set the Start value, press Apply and confirm.
This operation activates the STP/RSTP function on every port of the Switch: the memory necessary for
the operation is allocated.
3. Select the box Enable Ports, activate the ports you wish set for the RSTP function, press Apply and
confirm.
This operation creates an instance for every single port activated in the STP/RSTP table (see Port Set-
tings tab and Port Status tab).
If two or more ports belong to a LAG, the list will display the LAG and not the single ports (see LA Man-
ager). For example, if the ports LAN 1 and LAN 2 belong to the LAG po100, the list will display the option
po100 and not the options LAN 1 and LAN 2.
4. In order to change the default values of the general parameters of the Switch, execute the following
procedures:
Verify/modify the dynamic path cost calculation functions (STP/RSTP) (parameters: Dynamic
Path Cost Calculation and Dynamic Path Cost Lag-Speed - Default: Disable).
Verify/modify the version of the protocol (STP/RSTP) (parameter: Version - Default: RSTP Com-
patible).
Verify/modify the priority assigned to the Switch (STP/RSTP) (parameter: Priority - Default:
32768 (8).

Verify/modify the maximum number of BPDU packets in transmission (STP/RSTP) (parameter:
Tx Hold Count - Default: 6).
Verify/modify the parameters for the transmission of BPDU packets (STP/RSTP) (parameters:
Max Age - Default: 20 seconds, Hello Time - Default: 2 seconds, Forward Delay - Default: 15
seconds).
5. Select Port Settings tab.
6. Verify that the parameter RSTP Status is set to Enable for all the ports. Otherwise, set the value Enable,
press Apply and confirm.
The ports in state Enable are enabled to the operation of STP/RSTP protocol: the ports take part to the
Spanning Tree process and are ready to transmit/receive BPDU packets.
7. In order to change the default values of the port parameters, execute the following procedures:
Verify/modify the priority of a port (STP/RSTP) (parameter: Port Priority - Default: 128 (8).
Verify/modify the cost of the a port (STP/RSTP) (parameter: Path Cost - Default: 8000 for Radio
ports and line ports configured at 2.5Gb/s, 20000 for 1Gb/s, 200000 for 100Mb/s and 2000000
for 10Mb/s).
Verify/modify the interoperability of the equipment with other equipment (RSTP) (parameter:
802.1W Interop - Default: Disable).
WARNING If, in this moment of the procedure, a software reset is performed (see Execute the equip-
ment software reset), the ports enabled to the use of STP/RSTP protocol (see step 6) are “locked” even
if the use of STP/RSTP protocol is not completely enabled.
In order to “unlock” them, it is necessary to disable the ports (set the parameter RSTP Status of every
port to Disable) and then re-enable them (setting the parameter RSTP Status of every port to Enable).
8. Select Settings tab.
9. Set the value Enabled in the box Status, press Apply and confirm.
This operation enables the use of the protocol STP or RSTP (depending on the selected version) for the
equipment: the ports begin transmitting/receiving BPDU packets.

The parameter System Control indicates the enabling state, by the control system, of the STP/RSTP
function for the Switch:
• Start. The system activates the STP/RSTP function on every Switch port: the necessary memory
is allocated for the function.
• Shutdown. The system stops the STP/RSTP function on every Switch port: the allocated memory
is de-allocated and made available for other activities.

made by the user for the STP/RSTP function. In fact, when the value Start is selected later, all the pa-
rameters will be available set to their default value.

The parameter Enable Ports indicates the setting of the STP/RSTP function for every Switch port. The
box:

• Active ( ) indicates that the STP/RSTP function is set for the port (the port is inserted in the
STP/RSTP tables: Port Settings and Port Status).
• Inactive ( ) indicates that the port is not set for the STP/RSTP function (the port is not present
in STP/RSTP tables).
The port identifier (slot number/port number) and the port name (LAN 1, LAN 2 etc.) is indicated for
every port.
The label po<identification number> indicates a LAG (see LA Manager).
If two or more ports belong to a LAG, the list will display the LAG and not the single ports (see LA Man-
ager). For example, if the ports LAN 1 and LAN 2 belong to the LAG po100, the list will display the option
2. To change the parameters, activate or deactivate the wished boxes.

The parameter Status indicates the enabling state of STP/RSTP function:
• Enabled. Activates the STP/RSTP function in the Switch: the ports transmit/receive the BPDU
packets.
• Disabled. Disables the STP/RSTP function in the Switch: the ports do not transmit/receive the
BPDU packets.
If the default value of a port is changed (see Verify/modify the cost of the a port (STP/RSTP)), this value
will be used as Path Cost independently from the state (Enable or Disable) of the parameter Dynamic Path
Cost Calculation and Dynamic Path Cost Lag-Speed.

The Dynamic Path Cost Calculation parameter indicates the state of the dynamic path cost calculation
function. The Path Cost represents the distance between the port Root and the port Designated. The
Path Cost, according to the Specification 802.1d, is calculated dividing the bit rate by the bandwidth of
the segment connected to the port:
• Enable. The Path Cost is calculated according to the bit rate of the ports whose administrative
state is active (Enabled) in that moment. The path cost, once calculated, is not changed depend-
ing on the operating state of the ports.
• Disable. The Path Cost is calculated according to the bit rate of the connection when the port is
created.
The Dynamic Path Cost Lag-Speed parameter indicates the status of the function which defines if the
cost of the dynamic path must be calculated for the ports whose speed change dynamically. This func-
tion is mainly used for the LAGs (see LA Manager), whose speed changes according to the addition/
removal of ports to/from the channel:
• Enable. The Path Cost of the ports is dynamically calculated according to their current speed.
The Path Cost is calculated only if the port speed changes.
• Disable. The Path Cost of the ports is not dynamically calculated according to their current
speed.

2. To change the parameters, select the wished options.

The Version parameter indicates the Spanning Tree protocol version currently used by the Switch.
2. To change the parameter, select the option:

• STP Compatible. Spanning Tree Protocol standard IEEE 802.1d.
• RSTP Compatible. Rapid Spanning Tree protocol standard IEEE 802.1D-2004. Protocol charac-
terized by a greater speed (lower convergence time).

The Priority parameter indicates the priority assigned to the Switch. This value is used during the elec-
tion of the Root.
2. To change the parameter, select the wished option.

Values between 0 (highest priority) and 61440 (lowest priority) are available, subdivided by intervals
of 4096: 0, 4096 (1), 8192 (2), 12288 (3), 16384 (4), 20480 (5) and so on up to 61440 (15).
2. The parameter Tx Hold Count indicates the maximum number of BPDU packets which can be transmit-
ted within a given interval.
The parameter is common for all the ports of the Switch.
3. To change the parameter, select a value between 1 and 10.

The parameters are common for all the ports of the Switch.
The parameter setting must respect the formula 2 x (Forward Delay - 1) ≥ Max Age ≥ 2 x (Hello Time +1).

The parameter:
• Max Age, indicates the maximum number of switches which the packet can pass through before
expiring. The passage from a Switch to another one involves the decrease of 1 second per equip-
ment.
• Hello Time, indicates the time interval between two consecutive transmissions of the BPDU
(Bridge Protocol Data Unit) packet, generated by the Switch.
• Forward Delay, indicates the time interval which passes between the passage between the Dis-
carding status and the Learning status and between the Learning status and the Forwarding sta-
tus of the port.
2. To change the parameter in the box:

• Max Age, select a value between 6 and 40 seconds.
• Hello Time, select a value between 1 and 2 seconds.
• Forward Delay, select a value between 4 and 30 seconds.

The parameter Port Priority indicates the priority of every single port.
This value is used during the process for the selection of the port role.
3. In order to change a parameter, select the box Port Priority relevant to the wished port and select a
value between 0 (highest priority) and 240 (lowest priority). Values are subdivided in intervals of 16:
0, 16 (1), 32 (2), 48 (3) and so on up to 240 (15).

The parameter RSTP Status indicates the enabling state for the operation of the STP/RSTP protocol of
every single port:
• Disable. Protocol operation disabled: the port does not take part to the Spanning Tree process
and does not transmit/receive BPDU packets.
• Enable. Protocol operation enabled: the port takes part to the Spanning Tree process and is
ready to transmit/receive BPDU packets.
3. In order to change a parameter, select the box RSTP Status relevant to the wished port and select the
wished option.

WARNING The default value of Path Cost for every single port is automatically set as function of the port
bit rate: 8000 for Radio ports and line ports configured to 2.5Gb/s, 20000 for 1Gb/s, 200000 for 100Mb/s
and 2000000 for 10Mb/s.
If the default value of the port cost is changed, this value will be used as Path Cost independently from the
state (Enable or Disable) of the parameter Dynamic Path Cost Calculation.

The Path Cost parameter indicates the cost of the network portion directly connected to every single
port.
3. In order to modify a parameter, select the box Path Cost relevant to the wished port and set a value
between 1 and 200 000 000.

The parameter 802.1W Interop. indicates the equipment interoperability, as regards the RSTP protocol,
with other equipment:
• Disable. The equipment can interact and operate with equipment using the RSTP protocol im-
plemented according the standard IEEE 802.1D-2004.
• Enable. The equipment can interact and operate even with equipment using the RSTP protocol
implemented according the standard IEEE 802.1w (for example equipment of type ALCplus2e).
3. In order to change a parameter, select the box 802.1W Interop.relevant to the wished port and select
the wished option.

The Port Status tab displays the information stored by every Switch port as regards the STP/RSTP func-
tionality.

RSTP context
The context displays the parameters for management of Spanning Tree protocol.
Tabs
Settings tab. Parameters of the STP/RSTP module, used at global level by the Switch and by all
its ports.
Port Settings tab. Parameters of the Ethernet ports relevant to STP/RSTP function.
Port Status tab. Information stored by every Switch port as regards the STP/RSTP functionality.
Buttons
See also
RSTP (command)
Settings tab
The tab displays the general basic parameters of the STP/RSTP module, used at global level by the Switch
and all its ports.
Parameters
GLOBAL CONFIGURATION
System Control. Enabling state, by the control system, of the STP/RSTP function for the
Switch:
• Start. The system activates the STP/RSTP function on every Switch port: the
necessary memory is allocated for the function.
• Shutdown. The system stops the STP/RSTP function on every Switch port: the
allocated memory is made available for other activities.
Default Shutdown.
Enable Ports. Setting of the STP/RSTP function for every Switch port.
Select the option, the active box ( ) indicates that the STP/RSTP function is set for the
port (the port is inserted in the STP/RSTP tables: Port Settings and Port Status); the in-
active box ( ) indicates that the STP/RSTP function is not set for the port (the port is
not present in the STP/RSTP tables).
The identifier of the port (slot number/port number) and the port name (LAN 1, LAN 2
etc.) is indicated for every port.
The label po<identification number> indicates a LAG (see LA Manager). If two or more
ports belong to a LAG, the list will display the LAG and not the single ports. For example,
if the ports LAN 1 and LAN 2 belong to the LAG po100, the list will display the option
By default, all the ports are disabled.
Parameter available only if the System Control parameter has Start value.
Dynamic Path Cost Calculation. State of the path cost dynamic calculation function.
The Path Cost represents the distance between the port Root and the port Designated.
The Path Cost, according to the Specification 802.1d, is calculated dividing the bit rate
by the bandwidth of the network portion connected to the port:
• Enable. The Path Cost is calculated according to the bit rate of the ports whose
administrative state is active (Enabled) in that moment. The path cost, once
calculated, is not changed according to the operating state of the ports.
• Disable. The Path Cost is calculated according to the bit rate of the connection
when the port is created.

For the LAGs, the cost is updated when the channel is created and when the channel
changes its status, considering the speed of the physical interfaces operating in that mo-
ment. The cost does not change if then operating interfaces are added/removed without
switching the status of the whole LAG. The cost considers the speed and then it is de-
creased by 100.
Default Disable.
Status. Enabling state of the STP/RSTP function:
• Enabled. Activates the STP/RSTP function in the Switch: the ports transmit/
receive the BPDU packets.
• Disabled. Disables the STP/RSTP function in the Switch: the ports do not
transmit/receive the BPDU packets.
Default Disabled.
Dynamic Path Cost Lag-Speed. Status of the function which defines if the cost of the
dynamic path must be calculated for the ports whose speed change dynamically. This
function is mainly used for the LAGs, whose speed changes according to the addition/
removal of ports to/from the channel:
• Enable. The Path Cost of the ports is dynamically calculated according to their
current speed. The Path Cost is calculated only if the port speed changes.
• Disable. The Path Cost of the ports is not dynamically calculated according to
their current speed.
Default Disabled.
RSTP CONFIGURATION
Version. Spanning Tree protocol version currently used by the Switch:
• STP Compatible. Spanning Tree Protocol standard IEEE 802.1d.
• RSTP Compatible. Rapid Spanning Tree protocol standard IEEE 802.1D-2004.
Protocol characterized by a greater speed (lower convergence time).
Default RSTP Compatible.
Priority. Priority assigned to the Switch. This value is used during the election of the
Root.
Values between 0 (highest priority) and 61440 (lowest priority) are available, subdivided
in intervals of 4096: 0, 4096 (1), 8192 (2), 12288 (3), 16384 (4), 20480 (5) and so on,
up to 61440 (15).
Default 32768 (8).
Tx Hold Count. Maximum number of BPDU packets which can be transmitted within a
given interval.
Default 6.
Max Age.Maximum number of switches which the packet can pass through before ex-
piring. The passage from a Switch to another one involves the decrease of 1 second per
equipment.
Default 20 seconds.
Hello Time. Interval between two consecutive transmissions of the BPDU (Bridge Proto-
col Data Unit) packet, generated by the Switch.
Default 2 seconds.
Forward Delay. Time interval which passes between the passage between the Discard-
ing status and the Learning status and between the Learning status and the Forwarding
status of the port.
Default 15 seconds.

See also
Port Settings tab
The tab displays the parameters of the Ethernet ports in relation to STP/RSTP function.
Table
Every table row corresponds to one port set for the STP/RSTP function (parameter Enable Ports,
box active).
The table will be empty if the parameter System Control has value Shutdown or if the parameter
Enable Ports has not active values (see Settings tab).
Port Role. Role assigned by STP/RSTP to the port. The role defines the behaviour of the
port according to the state of the Bridge in the network:
• Disabled. Porta disabled manually (state STP/RSTP) or automatically (Link): it
will not take part to Spanning Tree process.
• Root. Port offering the best path (lowest cost) to the Bridge elected Root. Eve-
ry Bridge can have only one Root port. When the Spanning Tree algorithm is
at steady state, every Root port is in state Forwarding.
• Alternate. Port alternative to the Root port, as it offers an alternative path to
the Bridge Root with cost higher with respect to the Root port. Generally, the
Alternate port is in state Discarding. It is enabled and declared Root if the Root
port is in state Discarding.
• Designated. Port which does not offer paths to the Bridge Root and is used to
forward the information of the Bridge Root to other Bridges. Every Designated
port is in state Forwarding. In every segment, only one port is Designated.
• Backup. Port physically connected to a Lan where a Designated port of the
same Bridge is connected. The Backup port is in state Discarding. It is enabled
and declared Designated if the current Designated port is in state Discarding.
Port Priority. This value is used during the process of selection of the port role (see Port
Role).
Values between 0 (highest priority) and 240 (lowest priority) are available, subdivided in
intervals of 16: 0, 16 (1), 32 (2), 48 (3), 64 (4), 80 (5) and so on up to 240 (15).
Default 128 (8).
RSTP Status. Port enabling state as regards the operation of STP/RSTP protocol:
• Disable. Protocol operation disabled: the port does not take part to Spanning
Tree process and does not receive/transmit BPDU packets.
• Enable. Protocol operation enabled: the port stake part to Spanning Tree pro-
cess and is ready to receive/transmit BPDU packets.

Default Enable.
Path Cost. Cost of the network segment directly connected to the port. It represents the
distance between the port Root and the port Designated.
The default value is automatically set depending on the port bit rate: 8000 for Radio ports
and line ports configured at 2.5Gb/s, 20000 for 1Gb/s, 200000 for 100Mb/s and 2000000
for 10Mb/s.
802.1W Interop. Equipment interoperability, as regards the RSTP protocol, with other
equipment:
• Disable. The equipment can interact and operate with equipment using the
RSTP protocol implemented according to the standard IEEE 802.1D-2004.
• Enable. The equipment can interact and operate even with equipment using
the RSTP protocol implemented according to the standard IEEE 802.1w (for
example equipment of type ALCplus2e).
Default Disable.
See also
Port Status tab
The tab displays the information stored by every Switch port as regards the STP/RSTP functionality.
All the parameters are read-only.
Table
Every table row corresponds to one port set for the STP/RSTP function (parameter Enable Ports,
active box).
The table will be empty if the parameter System Control has value Shutdown or if the parameter
Enable Ports has not active values (see Settings tab).
Port Role. Role assigned by STP/RSTP to the port. The role defines the behaviour of the
port according to the state of the Bridge in the network:
• Disabled. Porta disabled manually (state STP/RSTP) or automatically (Link): it
will not take part to Spanning Tree process.
• Root. Port offering the best path (lowest cost) to the Bridge elected Root. Eve-
ry Bridge can have only one Root port. When the Spanning Tree algorithm is
at steady state, every Root port is in state Forwarding.
• Alternate. Port alternative to the Root port, as it offers an alternative path to
the Bridge Root with cost higher with respect to the Root port. Generally, the
Alternate port is in state Discarding. It is enabled and declared Root if the Root
port is in state Discarding.
• Designated. Port which does not offer paths to the Bridge Root and is used to
forward the information of the Bridge Root to other Bridges. Every Designated
port is in state Forwarding. In every segment, only one port is Designated.
• Backup. Port physically connected to a Lan where a Designated port of the
same Bridge is connected. The Backup port is in state Discarding. It is enabled
and declared Designated if the current Designated port is in state Discarding.
Port State. Current state of the port in relation to RSTP functionality.

Update the
Receive Forward Receive/ Re-transmit
Port status Address Table
traffic traffic process BPDU BPDU
Unit
Discarding No No No Yes No
Learning Yes No Yes Yes Yes
Forwarding Yes Yes Yes Yes Yes
Designated Root. Univocal identifier of the Bridge registered as Root for the segment
of the network which the port is connected to.
Designated Cost. Path Cost of the Designated port of the segment connected to the
porta.
Designated Bridge. Univocal identifier of the Bridge which the port considers the Bridge
Designated for the segment of the port. The Bridge Designated is the only Bridge allowed
to transmit the packets from/to the segment.
Designated Port. Identifier of the port on the Bridge Designated for the relevant seg-
ment. It represents the port through which the Bridge Designated forwards/receive the
packets to/from the segment.
Type. Operating state of the port in relation to the LAN segment connected to the port:
• SharedLan. The port is treated as connected to a shared connection.
• Point-to-Point. The port is treated as connected to a point-to-point connection.
The selection of present in the header of each column, shows the following commands:
Sort Ascending. Not available in this context.
Sort Descending. Not available in this context.
Columns. Activate ( ) or deactivate ( ) the display of a column in the table.
See also

Spanning Tree Protocol (STP)

Spanning Tree is a protocol for the management of the connections, which supports the redun-
dancy of the path avoiding the creation of unwished loops in the network. In order that an Ether-
net network operates correctly, only an active path must exist between two stations. Multiple
active paths cause loops in the network and, as consequence, the possible replication of the
messages to infinity.
The Spanning Tree protocol constitutes a tree logic network which pass through all the bridges
into a complex physical network forcing the possible duplicated paths (possible loops) into a
standby status.
If a network segment becomes unreachable or if the cost of a path changes, the algorithm of
Spanning Tree reconfigures the topology of the network activating an alternative path.
To make this possible, STP needs to know the whole network. The Bridges have to define the
main Bridge (Bridge Root) and calculate the role of the ports (Root, Designated, etc.) using the
known information. To ensure that every bridge has the information, the Bridges use special
packets called Bridge Protocol Data Units (BPDU) for the exchange of information on the ID’s of
the Bridges and on the cost of the path from the Root element.
The BPDU packets are periodically exchanged and allow the Switch keeping trace of the network
changes to start and stop the transmission of the ports, on demand.
A Bridge sends a BPDU packet using the univocal MAC address of the port as source address and
the STP multicast address 01:80:C2:00:00:00 as destination address.
For more information, refer to the standard IEEE 802.1d (Spanning Tree Protocol).
Rapid Spanning Tree Protocol (RSTP)

The protocol Rapid STP decreases, with respect to STP, the time necessary for the re-configu-
ration of the active network when the physical topology or the network configuration parameters
are changed.
The RSTP protocol has been designed to be compatible with the STP protocol.
For more information, refer to the standard IEEE 802.1D-2004 (Rapid Spanning Tree Protocol).
ALFOplus2
The equipment can be configured to work with the STP protocol or the RSTP protocol (see Verify/
modify the version of the protocol (STP/RSTP).
The use of the protocol must be enabled at Switch level and at single port level (see Enable/
disable the use of STP/RSTP protocol for the equipment).
Before enabling the protocol, it is suggested to set the relevant configuration parameters. By
WEB LCT, it is possible to configure:
PARAMETERS AT SWITCH LEVEL
System Control (see Verify/modify the allocation of memory for the STP/RSTP
function).
Enable Ports (see Verify/modify the ports set for the STP/RSTP function).
Dynamic Path Cost Calculation and Dynamic Path Cost Lag-Speed (see Verify/
modify the dynamic path cost calculation functions (STP/RSTP).
Status (see Verify/modify the enabling of STP/RSTP function).
Priority (see Verify/modify the priority assigned to the Switch (STP/RSTP).
Tx Hold Count (see Verify/modify the maximum number of BPDU packets in trans-
mission (STP/RSTP).
Max Age, Hello Time and Forward Delay (see Verify/modify the parameters for the
transmission of BPDU packets (STP/RSTP).
PARAMETERS AT PORT LEVEL
Port Priority (see Verify/modify the priority of a port (STP/RSTP).

RSTP Status (see Verify/modify the status of the STP/RSTP function of a port).
Path Cost (see Verify/modify the cost of the a port (STP/RSTP).
802.1W Interop (see Verify/modify the interoperability of the equipment with oth-
er equipment (RSTP) in such a way that the equipment can interact and operate

even with equipment using the RSTP protocol implemented according to the
standard IEEE 802.1w (for example equipment of type ALCplus2e).
See also
RSTP (command)
RSTP context

LLF
The command LLF allows configuring the operation of LLF (Link Loss Forwarding) functionality for the
equipment.
Operations
Verify the status of the LLF functionality for the Ethernet ports
Configure a port for the management of LLF functionality
Remove a port of the switch from the management of LLF functionality
Configure the radio circuit for the forwarding of the LOS alarm present on LAN
Remove a radio circuit from the management of LLF functionality for a given LAN
Enable/disable the LLF functionality for a LAN
Enable/disable the forwarding of LLF alarm on the radio
Modify the hysteresis value for the LLF functionality
Modify the propagation modality of LLF alarm
Modify the forwarding of LOS alarm of a LAN to the radio
Modify the modality used to forward the alarm LOS on the radio circuit
GUI
LLF context
See also
Bidirectional LLF (info)
Verify the status of the LLF functionality for the Ethernet ports
1. Select Base Band > Ethernet > LLF.

The LLF context displays the status of the LLF functionality for every equipment port.
Configure a port for the management of LLF functionality
2. Press Add in Ports area.
3. Set, in the Port box, the line Ethernet port for the functionality is configured.
It is not possible to select a port already selected for the functionality.
The management port and the Radio port will not be present in the list.
4. Set, in the LLF Status box, the status of LLF functionality:

• Disable. The functionality is disabled.
• Enable. The functionality is enabled.
5. Set, in the Alarm to Circuit box, the status of forwarding of the LLF alarm on a given radio circuit as-
sociated to the considered port:
• Disable. The alarm is not forwarded to the radio.
• Enable. The alarm is forwarded to the radio.
Value meaningful only if at least one radio circuit, where transmitting the LOS signal (see area
Mapped circuits on current port selection), has been created.

6. Set, in the Delay Time box, the interval (hysteresis) (value between 0 and 10 seconds) after which the
modality Link Loss Forwarding in reception is activated.
The alarm received from the radio direction (... Demodulator Fail Alarm, RADIO Link Id Alarm) must
persist for Delay Time seconds before the equipment disables the corresponding LAN.
In the same way, if the LAN is disabled by LLF functionality, the radio alarm must be cleared on the
radio for Delay Time seconds before the equipment enables the considered LAN.
7. Set, in the box Protection Mode, the propagation mode of LLF alarm:
• Disable. The alarm LLF is propagated when at least one radio is alarmed.
• Enable. The alarm LLF is propagated when all the radios are alarmed.
8. Press OK.
Remove a port of the switch from the management of LLF functionality
WARNING A port cannot be removed if there is at least one radio circuit associated to the port itself. If the
operator attempts executing this operation, the system displays an error message. First remove all the
radio circuits associated to the LAN and then remove the port.
2. Select the row of the table in the Ports area corresponding to the port for which you wish not to manage
the LLF functionality.
3. In the Ports area, press Remove and confirm.
Configure the radio circuit for the forwarding of the LOS alarm present on LAN
WARNING Operation available and meaningful only if:

• The equipment has at least one Radio Link defined.
• The specific port has been configured for the management of the LLF functionality.
2. In the Ports area, select the row corresponding to the LAN for which you wish to configure the func-
tionality.
3. In the Mapped circuit on current port selection area, press Add.
4. Set, in the Circuit box, the circuit of the radio where transmitting the LOS signal.
Every radio has eight circuits. It is not possible to select an already used circuit (displayed grey in the
selection menu).
5. Set, in the LOS to Circuit box, the enabling status of the forwarding of LOS alarm on the radio circuit:
6. Set, in the box LOS Insertion Mode, the mode used to forward the LOS alarm on the radio circuit:
• Single. The alarm is forwarded on the radio when the signal is present on one of the LAN which
the circuit is associated to.
For example, if the circuit #1 Link ID... has been configured for the port LAN 1 and even for the
port LAN 2, the LOS alarm will be forwarded to the radio circuit if the alarm is present on LAN 1
or on LAN 2.
• Group. The alarm is forwarded on the radio only if the signal is present on every port associated
to the circuit.

port LAN 2, the LOS alarm will be forwarded to the radio circuit if the alarm is present on LAN 1
and on LAN 2.
7. Press OK.
Remove a radio circuit from the management of LLF functionality for a given LAN
2. Select, in the Ports area, the row of the table corresponding to the port for which you wish to remove
a radio circuit.
3. Select, in the Mapped circuit on current port selection area, the row of the table corresponding to the
radio circuit you wish to remove.
4. In the Mapped circuit on current port selection area, press Remove and confirm.
WARNING Operation available and meaningful only if the management of the LLF functionality has been
configured for the specific port.

The LLF Status box indicates the enabling status of LLF functionality for the considered port:
2. To change the parameter, select the box and then select the wished value in the menu.

The box Alarm to Circuit indicates the enabling status of the forwarding of LLF alarm for the LAN con-
sidered on the radio:
• Disable. The disabled status of the local LAN is not communicated to the remote equipment.
• Enable. The disabled status of the local LAN is communicated to the remote equipment by means
of the selected radio circuit.
2. To change the parameter, select the box and then select the wished value in menu.


The box Delay Time indicates the hysteresis value (in seconds) for the LLF functionality in reception.
The alarm received from the radio direction (... Demodulator Fail Alarm, RADIO Link Id Alarm) must
persist for Delay Time seconds before the equipment disables the corresponding LAN.
In the same way, if the LAN is disabled by LLF functionality, the radio alarm must be cleared on the
radio for Delay Time seconds before the equipment enables the considered LAN.
2. To change the hysteresis value, type the wished value in the box.

The box Protection Mode indicates the propagation modality of the LLF alarm:
• Disable. The alarm LLF is propagated when at least one radio is alarmed.
• Enable. The alarm LLF is propagated when all the radios are alarmed.
2. To change the parameter, select the box and then select the wished value in the menu.
WARNING Operation available and meaningful only if the specific circuit of the radio for the forwarding of
the LOS alarm present on the LAN has been configured.
2. Select, in the area Ports, the row corresponding to the LAN which the wished radio circuit is associated
to.
In the Mapped circuit on current port selection area, the box LOS to Circuit indicates the enabling status
of the forwarding of the LOS alarm on the radio circuit:
• Disable. The LOS alarm of the LAN is not forwarded to the radio.
• Enable. The LOS alarm of the LAN is forwarded to the radio.
WARNING Operation available and meaningful only if the specific circuit of the radio for the forwarding of
the LOS alarm present on the LAN has been configured.

2. Select, in the area Ports, the row corresponding to the LAN which the wished radio circuit is associated
to.
In the Mapped circuit on current port selection area, the box LOS Insertion Mode indicates the modality
used to forward the alarm LOS on the radio circuit:
• Single. The alarm is forwarded to the radio when the signal is present on one of the LAN’s which
the circuit is associated to.
port LAN 2, the alarm LOS will be forwarded to the radio circuit if the alarm is present on LAN 1
or on LAN 2.
• Group. The alarm is forwarded to the radio only if the signal is present on all the ports which the
circuit is associated to.
port LAN 2, the alarm LOS will be forwarded to the radio circuit if the alarm is present on LAN 1
and on LAN 2.

LLF context
The context shows the configuration of the LLF functionality (Link Loss Forwarding).
Ports table
Port. Identifier of the port. The ID value is the combination between the slot number and
the port number (slot number/port number).
Descr. Name of the port (see Tab.5).
LLF Status. Enabling status of LLF functionality for the considered port:
Alarm to Circuit. Enabling status of the forwarding of LLF alarm present on the consid-
ered LAN to the radio:
• Disable. The disabled status of the local LAN is not communicated to the re-
mote equipment.
• Enable. The disabled status of the local LAN is communicated to the remote
equipment by means of the selected radio circuit.
Value meaningful only if at least one radio circuit has been created where for-
warding the signal of LOS (see area Mapped circuits on current port selection).
Delay Time. Hysteresis (in seconds) of LLF functionality in reception.
The alarm received from the radio direction (... Demodulator Fail Alarm, RADIO Link Id
Alarm) must persist for Delay Time seconds before the equipment disables the corre-
sponding LAN.
In the same way, if the LAN is disabled by LLF functionality, the radio alarm must be
cleared on the radio for Delay Time seconds before the equipment enables the considered
LAN.
Protection Mode. Propagation modality of LLF alarm:
• Disable. The LLF alarm is propagated when at least one radio is alarmed.
• Enable. The LLF alarm is propagated when all the radios are alarmed.
Mapped circuits on current port selection table

Each row of the table corresponds to a circuit for which are indicated:
Circuit. Radio circuit where forwarding the LOS signal.
Link ID. Identifier of the considered Radio Link.
LOS to Circuit. Enabling status of the forwarding of the LOS alarm on the radio circuit:
LOS Insertion Mode. Modality used to forward the alarm LOS on the radio circuit:
• Single. The alarm is forwarded to the radio when the signal is present on one
of the LAN’s which the circuit is associated to.
For example, if the circuit #1 Link ID... has been configured for the port LAN
1 and even for the port LAN 2, the alarm LOS will be forwarded to the radio
circuit if the alarm is present on LAN 1 or on LAN 2.
• Group. The alarm is forwarded to the radio only if the signal is present on all
the ports which the circuit is associated to.
For example, if the circuit #1 Link ID... has been configured for the port LAN
1 and even for the port LAN 2, the alarm LOS will be forwarded to the radio
circuit if the alarm is present on LAN 1 and on LAN 2.
Signal Fail. Indication of alarm present on the circuit.

Buttons
Apply. Confirms the changes.
PORTS
Add. Configure a port for the management of LLF functionality
Remove. Remove a port of the switch from the management of LLF functionality
MAPPED CIRCUITS ON CURRENT PORT SELECTION
Add. Configure the radio circuit for the forwarding of the LOS alarm present on LAN
Remove. Remove a radio circuit from the management of LLF functionality for a given
LAN
Refresh Signal Fail. Updates the alarm signal.
See also
LLF (command)

Bidirectional LLF functionality

The bidirectional LLF functionality allows interrupting the connection with the remote equipment
(in both directions) as consequence of the disabling of the LANs of the local equipment due to
Link Loss Forwarding.
Implement the functionality for a radio connection

For the correct configuration of the bidirectional LLF functionality for a radio connection, it is nec-
essary to perform the operations described in the following example.
Suppose you wish to disable the LAN 1 ports (on local and remote equipment) as consequence
of LLF detected by the local LAN 1 port.
Operations to perform for the LOCAL equipment via the GUI:

• Select Base Band > Ethernet > LLF.
• Configure a port for the management of LLF functionality setting the following values:
Port: LAN 1
LLF Status: Enable
Alarm to Circuit: Enable
Delay Time: any value
• Configure the radio circuit for the forwarding of the LOS alarm present on LAN selecting
LAN 1 in the Ports area and setting the following values:
Circuit: #1 Link ID...
LOS to Circuit: Enable
LOS Insertion Mode: any value
• Press Apply and continue.
Operations to perform for the REMOTE equipment via the GUI:

• Select Base Band > Ethernet > LLF.
• Configure a port for the management of LLF functionality setting the following values:
Port: LAN 1
LLF Status: Enable
Alarm to Circuit: Enable
Delay Time: any value
• Press Apply and continue.
With this configuration, an alarm in reception on the remote terminal causes the activation of
LLF alarm and the consequent disabling of the associated LAN 1 port on both the terminals.
See also
LLF (command)
LLF context

Queue Depth
The command Queue Depth manages the depth of the output queues.
Operations
Verify the policy for the management of the depth of the queues in output
Modify the policy for the management of the depth of the queues in output
GUI
Queue Depth context
Verify the policy for the management of the depth of the queues in output
1. Select Base Band > Ethernet > Queue Depth.

The Queue Depth context displays policy used to manage the depth of the queues in output.
Modify the policy for the management of the depth of the queues in output
WARNING The operation involves the equipment restart.
1. Select Base Band > Ethernet > Queue Depth.
2. Press the option Activate relevant to the policy you wish to activate and confirm.

Queue Depth context
The context displays the policy for the management of the depth of the queues in output (8 queues per
port).
The Switch can insert a limited number of packets into every queue. This limit, indicated as depth, can be
configured by the user. During the period of high traffic, a queue is filled by packets waiting for the trans-
mission. When a queue reaches its limit, by default the Switch discards the packets until when the queue
is not full longer.
Parameters
Profile. Available profiles of the output queues:
• Full dynamic memory (All HW). This configuration, identical for every queue, allows
the dynamic allocation of memory per queue up to 1/8 of the total memory available
in every moment.
• Priority based memory allocation This configuration is based on the principle for which
the lower priority traffic needs longer queues. The proper forwarding of the traffic at
the different priorities (and queue) allows achieving the wished length.
• Uniform memory allocation. This configuration provides queues with constant length,
independently from the traffic priority. The use of WRED algorithms allows changing
the method used to store the different traffic types, obtaining different depths.
Profile Description. Detailed description of the configuration of the selected profile.

If the selected option is:
• Full dynamic memory (All HW). The description is the following:
Full dynamic memory allocation (hardware default)
Reference frame length: 2048 byte
Total reserved memory: 0 Mbyte
Total dynamic memory: 96 Mbyte
Radio ports reserved memory [Mbyte]: 0
Radio ports dynamic memory [Mbyte]: 17
Line ports reserved memory [Mbyte]: 0
Line ports dynamic memory [Mbyte]: 17
• Priority based memory allocation. The description is the following:
Memory allocation dependent on scheduling priority
Lower priority queues are wider than higher priority queues
Total reserved memory: 79.5 Mbyte
Total dynamic memory: 16.5 Mbyte
Radio port reserved memory [Mbyte]: 32, 16, 8, 4, 2, 1, 0.512, 0.256
Line ports reserved memory [Mbyte]: 0.512, 0.256, 0.128, 0.064, 0.032, 0.032,
0.032, 0.032.
Line ports dynamic memory per queue [Mbyte]: 1.6
• Uniform memory allocation. The description is the following:
Uniform memory allocation
At each port, all queues have the same length
Total reserved memory: 57.5 Mbyte
Total dynamic memory: 38.5 Mbyte
Radio port reserved memory per queue [Mbyte]: 4
Radio port dynamic memory per queue [Mbyte]: 4
Line ports reserved memory per queue [Mbyte]: 0.512
Line ports dynamic memory per queue [Mbyte]: 4
Action. Status of the profile:

• Currently Active. Profile currently in use.
• Activate. Profile not in use. Select the option to Modify the policy for the management
of the depth of the queues in output.
Buttons

See also
Queue Depth (command)

LA Manager
The command LA Manager manages the Link Aggregation module.
Operations
Verify the status and configuration of Link Aggregation function
Modify the allocation of memory for the Link Aggregation function
Modify the enabling of Link Aggregation function
Verify the static LAGs
Create a static LAG
Create a static LAG for protection (ELP)
Modify the configuration of a static LAG (Admin State, MTU and/or Max Ports)
Delete a static LAG
Verify the ports member of one LAG
Define the ports member of one LAG
Add/remove the ports to/from one LAG
Remove all the ports from one LAG
Verify the LACP settings for the ports member of one LAG
Modify the LACP settings for the ports member of a LAG (Activity and/or Timeout)
Verify/modify the policy for the distribution of the Ethernet traffic (Link Aggregation)
GUI
LA Manager context
See also
Link Aggregation (info)
Verify the status and configuration of Link Aggregation function
1. Select Base Band > Ethernet > LA Manager.

The LA Manager context displays the status and configuration of Link Aggregation function.

The parameter System Control indicates the enabling state, by the control system, of the Link Aggre-
gation function for the Switch:
• Start. The system activates the Link Aggregation function in the Switch: the necessary memory
is allocated for the function.
• Shutdown. The system stops the Link Aggregation function in the Switch: the allocated memory
is de-allocated and made available for other activities.

made by the user for the Link Aggregation function. In fact, when the value Start is selected later, all
the parameters will be available set to their default value.


The parameter LA Status indicates the enabling state of Link Aggregation function:
• Enabled. Activates the Link Aggregation function for all ports of the Switch.
• Disabled. Disables the Link Aggregation function for all ports of the Switch.
Verify the static LAGs

The General Settings tab displays the list and the configuration of the static LAG’s (Link Aggregation
Group) created by the operator.
Create a static LAG
2. In the General Settings tab, press Add.
3. Set, in the box Port Channel ID, the univocal LAG identifier (value between 1 and 65535).
4. Set, in the box Admin State, the enabling state of LAG interface:
• Disabled. The LAG interface is not enabled to the aggregation of the corresponding ports: the
interface does not transmit/receive traffic.
• Enabled. The LAG interface is enabled to the aggregation of the corresponding ports: the inter-
face transmits/receives traffic.
5. Set, in the box MTU, the maximum size in byte of the packet accepted by LAG interface (value between
46 and 12266).
6. Verify that the box ELP is inactive ( ).
7. Set, in the box Max Ports, the maximum number of ports which can be attached to the LAG (value be-
tween 2 and 8).
The best ports are maintained in active state and other ports are maintained in standby state, if the
total number of ports attached to the LAG exceeds the configured value.
8. Set, in the box Bridge Port Type, the type of ports which will be members of the LAG.
If the Bridge is in configuration:
• Customer Bridge. The LAG can aggregate ports of type Customer Bridge (port where C-TAG’s
(UNI) are observed and managed if the equipment implements a Customer Bridge).

• Provider Bridge (802.1ad) or Provider Edge Bridge. The LAG can aggregate only ports of type
Provider Network (port where S-TAG’s (NNI) are observed and managed if the equipment im-
S-TAG).
9. Press Apply.
Create a static LAG for protection (ELP)
If you have created a static LAG for protection (ELP) between two optical ports, it is suggested to enable
the autonegotiation for the considered ports (see Physical Interface tab) in such a way to preserve the con-
nection in case of interruptions of the optical signal in one direction.
2. In the General Settings tab, press Add.
3. Set, in the box Port Channel ID, the univocal LAG identifier (value between 1 and 65535).
4. Set, in the box Admin State, the enabling state of LAG interface:
• Disabled. The LAG interface is not enabled to the aggregation of the corresponding ports: the
interface does not transmit/receive traffic.
• Enabled. The LAG interface is enabled to the aggregation of the corresponding ports: the inter-
face transmits/receives traffic.
5. Set, in the box MTU, the maximum size in byte of the packet accepted by LAG interface (value between
46 and 12266).
6. Activate the ELP box ( ).
7. Set, in the box Bridge Port Type, the type of ports which will be members of the LAG.
If the Bridge is in configuration:
• Customer Bridge. The LAG can aggregate only ports of type Customer Bridge.
Port type where C-TAG’s (UNI) are observed and managed if the equipment implements a Cus-
tomer Bridge.
• Provider Bridge (802.1ad) or Provider Edge Bridge. The LAG can aggregate only ports of type
Provider Network.
Port type where S-TAG’s (NNI) are observed and managed if the equipment implements a Pro-
vider Bridge or a Provider Edge Bridge. More C-TAG’s can be present within one S-TAG.
8. Press Apply.
WARNING Operation available only if the parameter System Control has value Start and if at least one LAG
has been created.
The parameter Max Ports cannot be changed if at least one port is associated to the LAG (see LAG tab).

2. To modify the enabling state of LAG interface, set, in the box Admin State relevant to the wished LAG,
the option:
• Disabled. The LAG interface is not enabled to the aggregation of the relevant ports: the interface
does not transmit/receive traffic.
• Enabled. The LAG interface is enabled to the aggregation of the relevant ports: the interface
transmits/receives traffic.

3. To modify the maximum size in byte of the packet accepted by LAG interface, set, in the box MTU rel-
evant to the wished LAG, a value between 46 and 12266.
This parameter can be changed only if the parameter Admin State has value Disabled.
4. To modify the maximum number of ports which can be attached to the LAG, set, in the box Max Ports
relevant to the wished LAG, a value between 2 and 8.
If the field Max Ports contains the string [ELP], this means that the record refers to a LAG for protection
(ELP). In this case, the change of the value from [ELP] to a number between 2 and 8, besides changing
the maximum number of port, changes the LAG type: from LAG for protection (ELP), it becomes a nor-
mal aggregation LAG.
Setting the value 1 in the field Max Ports changes a normal aggregation LAG to a protection LAG (ELP).
Delete a static LAG
WARNING Operation available only if the parameter System Control has value Start and if at least one LAG
has been created.
2. Select the LAG you wish to delete in the area Port Channel Interface Settings.
Verify the ports member of one LAG
WARNING Operation meaningful only if at least one LAG has been created.
2. Select the LAG tab.

The tab displays the list and the configuration of the Ethernet ports aggregated to each LAG.
Define the ports member of one LAG
Operation available only for the LAG’s which no port has been assigned to and if there are free ports (ports
not associated yet to a LAG).
3. Select the LAG which you wish to associate the ports to.
4. Press New.
The parameter Port Channel ID in the New Aggregation window indicates the selected LAG.
5. Set, in the box Mode, the operating mode of the LACP protocol (Link Aggregation Control Protocol) for
the specific LAG:
• Lacp. The protocol LACP is active. The protocol manages the exchange of information with the
remote device connected to the LAG, in such a way that the Switch is synchronized with the

relevant peer to start the negotiation between the LAG interfaces. The degradation or the loss
of the signal on a LAG port is signalled to the corresponding peer by the LACP protocol.
• Manual. The protocol LACP is inactive. The loss of the signal on a LAG port is signalled to the
relevant peer by the alarm Loss of Signal Alarm.
WARNING If a LAG for protection is selected (ELP), the parameter Mode is not meaningful and is not
available because this type of LAG uses the protocol Ethernet Line Protection to operate.
6. Select the box Ports and activate ( ) the ports you wish to become members of the LAG.
For every port, the port identifier (slot number/port number) and the port name (LAN 1, LAN 2 etc.)
are indicated.
The list will contain only the ports not associated yet to a LAG.
For a correct operation of the LAG, the selected ports must have a homogeneous configuration: same
transmission speed, same transmission mode (Full-Duplex) and same MTU.
If a LAG for protection is selected (ELP), it is necessary to select two ports. The selection of three or
more ports will generate an error message.

The message Error in adding a new port to an aggregation. Check the MTU values (interface and chan-
nel-group) are the same indicates that the operation is failed because the selected ports have different
values of MTU among them and with respect to the MTU value set for the relevant LAG.
Ports can be added to/removed from one LAG without affecting the traffic on the LAG itself.
3. Select the box Ports relevant to the wished LAG.

The box:
• Active ( ) indicates that the port is member of the specific LAG.
• Inactive ( ) indicates that the port is not member of the LAG.
The list does not contain the ports associated to a different LAG.
4. To change the parameters, activate or deactivate the wished boxes.

If a LAG for protection is selected (ELP), it is not possible to select three or more ports.

The message Error in adding a new port to an aggregation indicates that the operation is failed because
the activated ports have a MTU value different from the ports already member of the LAG.
Remove all the ports from one LAG

3. Select the wished LAG.

Button available only if the selected LAG has at least one port associated.

Verify the LACP settings for the ports member of one LAG
WARNING Operation meaningful only:

• If at least one port is member of a LAG.
• For LAGs that using the LACP protocol.
2. Select LACP tab.

The tab displays the LACP (Link Aggregation Control Protocol) settings for the ports member of a LAG.
WARNING Operation available only if at least one port is member of a LAG.
2. Select the LACP tab.

3. To change the mode used by the LACP protocol to manage the LACPDU (Link Aggregation Control Pro-
tocol Data Unit) packets, set, in the box Activity relevant to the wished port, the option:
• Active. The protocol generates LACPDU without waiting for any LACPDU from the remote port
(partner).
• Passive. The protocol generates LACPDU only when one LACPDU is received from the partner
port.
Operation available only for LAGs that using the LACP protocol (parameter Mode, value LACP - see LACP
tab).
4. To change the time within which the LACPDU packets should be received on a port to avoid the timeout
of the aggregated Link (LACP timeout), set, in the box Timeout relevant to the wished port, the option:
• Long. The value of LACP timeout (no packet is received from the peer) is 90 seconds.
• Short. The value of LACP timeout is 3 seconds.
Operation meaningful only for LAGs that using the LACP protocol.
WARNING Operation meaningful only if at least one LAG is created.
2. Select the Load Balancing tab.

The column Policy indicates, for every LAG, the rule used for the balancing of the load of the packets
in egress among the ports member of the LAG:
• MAC Source & Destination. The Switch uses the source and destination MAC addresses of the
received packets to balance the traffic.
• IP Source and Destination. The Switch uses the source and destination IP addresses of the re-
ceived packet to balance the traffic.

LA Manager context
The context displays the parameters for the management of the Link Aggregation module.
Tabs
General Settings tab. Configuration parameters of the Link Aggregation module used by the
Switch.
LAG tab. List and configuration of the Ethernet ports aggregated to every LAG.
LACP tab. LACP settings for the ports member of one LAG.
Load Balancing tab. Policy for the distribution of the Ethernet traffic among the aggregated links.
Buttons
See also
General Settings tab
The tab displays the configuration parameters of the Link Aggregation module used by the Switch.
Parameters
MAIN
System Control. Enabling state, by the control system, of the Link Aggregation function
for the Switch:
• Start. The system activates the function Link Aggregation in the Switch: the
necessary memory is allocated for the function.
• Shutdown. The system interrupts the Link Aggregation function in the Switch:
the allocated memory is made free and available for other activities.
Default Shutdown.
LA Status. Enabling state of the Link Aggregation function:
• Enabled. Enables the Link Aggregation function in the Switch for all the ports.
• Disabled. Disables the Link Aggregation function in the Switch for all the ports.
Default Disabled.
System ID. MAC unicast address used as univocal LACP identifier of the Switch.
Default 00:00:00:00:00:00.
Parameter can be configured via CLI
Table
PORT CHANNEL INTERFACE SETTINGS
The table displays the static LAG’s (Link Aggregation Group) created by the operator.
The table will be empty if the parameter System Control has value Shutdown or if no port chan-
nel has been created.
Port Channel ID. Univocal LAG identifier.
Link Status: Status of the physical link between the LAG interface and a device in the
network:

• Up. The link is working: the LAG interface is available for the aggregation of
the relevant ports and is ready to exchange traffic.
• Down. The link is not working: the LAG interface is available for the aggrega-
tion of the relevant ports, but the physical link is not active or is faulty.
Admin State. Enabling state of LAG interface:
• Disabled. The LAG interface is not enabled to the aggregation of the relevant
ports: the interface does not transmit/receive traffic.
• Enabled. The LAG interface is enabled to the aggregation of the relevant ports:
the interface transmits/receives traffic.
MTU. Maximum size in byte of the packet accepted by LAG interface.
Max Ports. Maximum number of ports that can be attached to the LAG.
The best ports are maintained in active state and other ports are maintained in standby
state, if the total number of ports attached to the LAG exceeds the configured value.
Default 8.
The label [ELP] indicates that the record refers to a LAG for protection (ELP).
Bridge Port Type. Type of ports member of the LAG.
equipment implements a Customer Bridge (Switch in Customer Bridge modal-
ity).
TAG’s can be present within one S-TAG (Switch in Provider Bridge (802.1ad)
modality or Provider Edge Bridge modality).
ceived on this port are routed on a single S-VLAN (Switch in Provider Edge
Bridge modality).
Buttons
Add. Create a static LAG
Remove. Delete a static LAG
See also
LAG tab
The tab displays the list and the configuration of the Ethernet ports aggregated to each LAG.
Table
Each row of the table corresponds to one LAG.
The table will be empty if the parameter System Control has value Shutdown or if no port chan-
nel has been created (see General Settings tab).
Port Channel. LAG identifier: po<identification number>.
Ports. Identifier of the ports which are members of the specific LAG.
number).
Aggregation Type. Type of LAG:
• Static: the ports are manually assigned to the LAG. They remain dedicated
LAG members until when otherwise configured.

Parameter available only if at least one port is assigned to the LAG.
Mode. Operating mode of the LACP protocol (Link Aggregation Control Protocol) for the
specific LAG:
• LACP. The LACP protocol is active. The protocol manages the exchange of in-
formation with the remote device connected to the LAG in such a way the
Switch is synchronized with the peer to start the negotiation between the LAG
interface. The degradation or the loss of the signal on a port of the LAG is sig-
nalled to the relevant peer by the LACP protocol.
• Manual. The LACP protocol is inactive. The loss of the signal on a port of the
LAG is signalled to the relevant peer by the alarm Loss of Signal Alarm.
Parameter available only if at least one port is assigned to the LAG.
Parameter not meaningful for LAG’s for protection (ELP).
Buttons
New. Define the ports member of one LAG
Remove. Remove all the ports from one LAG
See also
LACP tab
The tab displays the LACP (Link Aggregation Control Protocol) settings for the ports member of a LAG.
Table
Every row of the table corresponds to one Ethernet port member of a LAG.
The table will be empty if the parameter System Control has value Shutdown or if no port is
member of a LAG (see LAG tab).
Port. Port identifier.
number).
Port Channel State. Current status of the port as regards the Link Aggregation func-
tion:
• Up In Bundle. The port is an active member of a LAG (Link Aggregation
Group): it is operating and takes part to the aggregation.
• Standby. The port is a member of a LAG, but is currently in standby. It can
replace a port in malfunction in the LAG.
• Down. The port is not active or is active, but currently cannot take part to the
aggregation because of a mismatch of the information among the LAG mem-
bers.
• Up Individual. The port is operating but is not member of any LAG.
Mode. Operating mode of the LACP protocol for the port:
• LACP. The LACP protocol is active. The protocol manages the exchange of in-
formation with the remote device connected to the LAG in such a way the
Switch is synchronized with the peer to start the negotiation between the LAG
interface. The degradation or the loss of the signal on a port of the LAG is sig-
• Manual. The LACP protocol is inactive. The loss of the signal on a port of the
LAG is signalled to the relevant peer by the alarm Loss of Signal Alarm.

Parameter not meaningful for LAG’s for protection (ELP).
Activity. Mode used by the LACP protocol to manage the LACPDU packets (Link Aggre-
gation Control Protocol Data Unit) for the port:
• Active. The protocol generates the LACPDU without waiting for any LACPDU
from the remote port (partner).
• Passive. The protocol generates LACPDU only when one LACPDU is received
from the partner port.
Parameter meaningful only if the parameter Mode has value LACP.
Timeout. Time within which the LACPDU packets should be received on a port to avoid
the timeout of the aggregated Link (LACP timeout):
• Long. The value of LACP timeout (no packet is received from the peer) is 90
seconds.
• Short. The value of LACP timeout is 3 seconds.
Default Long.
Parameter meaningful only if the parameter Mode has value LACP.
Port State. Machine state relevant to the port and transmitted within the LACPDU pack-
ets:
• Agg. Machine state Aggregation. The port is a possible candidate for the ag-
gregation.
• Syn. Machine state Synchronisation. The LAG interface of the local device and
that of the remote device are reciprocally synchronous.
• Col. Machine state Collecting. The port can receive packets and should not be
deactivated in absence of administrative changes or changes in the informa-
tion received by the protocol.
• Dis. Machine state Distributing. The port is enabled to transmit packets.
• Def. Machine state Defaulted. The port uses default operating information of
the remote device.
• Exp. Machine state Expired. The state becomes expired when the LACPDU
packets are not received more by the device for a given time period.
Parameter available only if the parameter Mode has value LACP.
PORT STATE LEGEND
The description of the options is the same reported above.
Agg: aggregation.
Syn: synchronisation.
Col: collectiong.
Dis: distributing.
Def: defaulted.
Exp: expired.
See also
Load Balancing tab
The tab displays the policy for the distribution of the Ethernet traffic among the aggregated links to define
the load balancing.

Table
Each row of the table corresponds to a LAG for which are indicated:
Port Channel. LAG identifier: po<identification number>.
Description. LAG name.
The parameter is not available for the LAG’s created by WEB LCT.
Policy. Rule for the balancing of the load of the packets in output among the ports mem-
ber of the LAG:
• MAC Source & Destination. The Switch uses the source and destination MAC
addresses of the received packets to balance the traffic.
• IP Source and Destination. The Switch uses the source and destination IP ad-
dresses of the received packet to balance the traffic.
See also

Link Aggregation function

The equipment implements the Link Aggregation function in compliance with standard IEEE
802.3ad.
The function allows aggregating single ports/interfaces within an aggregation group named LAG
(Link Aggregation Group) which allows increasing the bandwidth and provides redundancy. For
example, if one of the active Links used for the LAG goes down, the traffic is distributed among
the active Links.
The LAG is considered as a single port/interface by the upper layers, as STP (LAG interface). In
fact, all the packets of the LAG interface can be considered as a single logical packet transported
on separated physical supports by means of standard protocol LACP.
The protocol LACP (Link Aggregation Control Protocol) automatically manages some function-
alities of the aggregation as the synchronisation of the device with the relevant peer. The syn-
chronisation always precedes the transmission of data and takes place by means of an exchange
of LACPDU (Link Aggregation Control Protocol Data Unit) which represent control packets de-
fined by the LACP protocol. The protocol can be used only if the remote device uses this mode
too.
The whole capacity of a LAG is the sum of the capacities of the single links composing the ag-
gregation, in this way providing greater bandwidth to the Client.
The Link Aggregation function is supported only for point-to-point links, in Full Duplex mode and
with ports which operate at the same data transmission speed.
LAG for protection (ELP)

A particular type of LAG is the LAG for protection (ELP).
In this type of aggregation, there is not the creation of an aggregation group among more ports
whose capacity is summed to form a logical channel with greater size, but one port has the func-
tion of protection and another port according the rules of Ethernet Line Protection (ELP).
ELP, in fact, allows realizing a protection of physical level (Level 2) between two Ethernet line
ports.
When a LAG for protection is created (ELP), two LAN’s must be selected which will be one in
service and the other one in protection. When the user enables the LAG, the system automati-
cally enables the management of the ELP switch among the ports.
The switch operates in automatic mode: the equipment actuates the switch when the alarm LOS
is present on the LAN in service.
When the alarm clears, the controller does not actuate the switch again.
Ethernet line protection is implemented via proprietary protocol.
As consequence, the ELP switch is managed without considering alarms or settings made on the
equipment at the other side of the LAN connection.
When the alarm LOS is received on a port, the ELP actuates the switch. The port which has re-
ceived LOS is set to administrative status Down for 2 seconds in such a way to allow the turn-
off even of the corresponding port located at the other side of the link.
If you have created a static LAG for protection (ELP) between two optical ports, it is suggested
to enable the autonegotiation for the considered ports (see Physical Interface tab) in such a way
to preserve the connection in case of interruptions of the optical signal in one direction.
Enable the Link Aggregation mode

By means of WEB LCT, the Link Aggregation mode can be enabled in a point-to-point link, per-
forming the following operations on both the pieces of equipment:
• Allocate the memory in the Switch for the function (see Modify the allocation of mem-
ory for the Link Aggregation function).
• Enable the function (see Modify the enabling of Link Aggregation function).
• Create a static LAG defining the following parameters:
• Univocal LAG identifier (Port Channel ID).
• Enabling state of LAG interface: enabled or disabled (Admin State).
If the LAG is created in disabled state, it shall be enabled later.

• Maximum size of the packet accepted by the LAG interface (MTU).
The value set for MTU must be the same to the one of the single ports which
will become members of the LAG.
• Maximum number of ports which can be aggregated to LAG (Max Ports).
The best ports are maintained in active state and other ports are maintained
in standby state, if the total number of ports attached to the LAG exceeds the
configured value. The best port is calculated based on the Port Identifier and
Port Priority.
Repeat the above operations to create the wished LAG’s.
It is possible to add/remove ports to/from a LAG without affecting the traffic on the
LAG.
• Create a static LAG for protection (ELP) defining the following parameters:
• Univocal LAG identifier (Port Channel ID).
• Enabling state of LAG interface: enabled or disabled (Admin State).
If the LAG is created in disabled state, it shall be enabled later.
• Maximum size of the packet accepted by the LAG interface (MTU).
The value set for MTU must be the same to the one of the single ports which
will become members of the LAG.
Repeat the above operations to create the wished LAG’s.
• Define the ports member of one LAG defining the following parameters:
• Ports you wish to become members of the LAG (Ports)
A port can be member of only one LAG at a time.
For a correct operation of the LAG, the selected ports must have a homogene-
ous configuration: same transmission speed, same transmission mode (Full-
Duplex) and same MTU.
The LAG for protection (ELP) must have only two ports associated to LAG.
• Operating mode of the LACP protocol for the selected ports: active or inactive
(Mode).
In a LAG, when LACP è:
• Active (option LACP), the protocol manages the exchange of information
with the remote device connected to the LAG in such a way the Switch is
synchronized with the peer to start the negotiation between the LAG inter-
face. The degradation or the loss of the signal on a port of the LAG is sig-
• Inactive (option Manual), the loss of the signal on a port of the LAG is sig-
nalled to the relevant peer by the alarm Loss of Signal Alarm.
Setting the parameter Mode is not meaningful and available for the LAG for protection
(ELP).
During the definition of the ports, if the parameter Mode is set to the value LACP, the
system automatically configures the following parameters:
• Modality by which the LACP packets are exchanged among the devices (Ac-
tivity): Active (the protocol generates LACPDU without waiting for any
LACPDU from the port).
• Time within which the LACPDU packets must be received on a port to avoid
the timeout of the aggregated Link (Timeout): Long (the value of LACP
timeout is 90 seconds).
The above parameters can be changed later (see Modify the LACP settings for the
ports member of a LAG (Activity and/or Timeout).
It is suggested to set the parameter Activity to the value Active on both sides of the
link. Avoid to set the parameter to Passive on both the devices.
• Verify/modify the policy for the distribution of the Ethernet traffic (Link Aggregation)
Interaction between LAG and VLAN

The LAG interface, as the other ports of the Switch, can be assigned to a VLAN.
When a port becomes member of a LAG, the LAG does not inherit the membership of the aggre-
gated ports to the VLAN.
This happens because when a port is aggregated to a LAG, this port will not be visible to appli-
cations of level higher than 2 (as VLAN, STP, etc.). These applications can see the LAG interface
as it was a single port.

Then, when a port is aggregated to a LAG, this port is removed from the specific VLAN. When a
port is removed from a LAG does not return to be a member of the original VLAN.
MAC Table
For a correct operation of the LAG’s, the learning of the addresses in the MAC Table must be
active (Global MAC Learning Status: Enable - see Basic Settings tab).
See also
LA Manager context

Statistics
Interface. It displays the trend of the traffic on the Ethernet interfaces displaying the counters of pack-
ets/bytes in input/output.
The counters are based on the standard RFC 1213 (Interfaces group) and RFC 1284 (Ethernet-like Sta-
tistics group).

Interface
The Interface command displays the trend of the traffic on the Ethernet interfaces displaying the counters
of packets/bytes in input/output
The count of a counter is cyclic and always active.
The depth of the events stored by each counter is equal to 2^32; when this limit is reached, the count
restarts from zero. In any moment, you can reset all the counters.
The counters are based on the standard RFC 1213 (Interfaces group) and RFC 1284 (Ethernet-like Statis-
tics group).
Operations
Verify the counters of the Ethernet interfaces (Interfaces group)
Reset the counters’ results (Interfaces group)
Verify the counters of the Ethernet interfaces (Ethernet-like Statistics group)
Reset the counters’ results (Ethernet-like Statistics group)
GUI
Interface context
Verify the counters of the Ethernet interfaces (Interfaces group)
1. Select Base Band > Ethernet > Statistics > Interface.

The Interface tab displays the counters of the Ethernet interfaces (RFC 1213 - Interfaces group).
Reset the counters’ results (Interfaces group)
2. In the Interface tab, press Reset Counters and confirm.

All the counters of the tab are set to zero.
Verify the counters of the Ethernet interfaces (Ethernet-like Statistics group)
2. Select the Ethernet tab.

The tab displays the counters of the Ethernet interfaces (RFC 1284 - Ethernet-like Statistics group).
Reset the counters’ results (Ethernet-like Statistics group)

2. Select the Ethernet tab.
3. Press Reset Counters and confirm.

All the counters of the tab are set to zero.

Interface context
The context displays the trend of the traffic on the Ethernet interfaces displaying the counters of packets/
bytes in input/output.
The counters are based on the standard RFC 1213 (Interfaces group) and RFC 1284 (Ethernet-like Statis-
tics group).
Tabs
Interface tab. Counters of packets/bytes in input/output (Interfaces group).
Ethernet tab. Counters of packets/bytes in input/output (Ethernet-like Statistics group).
Buttons
See also
Interface (command)
Interface tab
The tab displays the counters of the Ethernet interfaces (RFC 1213 - Interfaces group).
Table
Each row of the table corresponds to an interface for which are indicated:
The port ID is a combination of slot and the port number (slot number/port number).
Descr. Name of the port (see Tab.5.) or LAG.
The remnant rows indicate the counters (see Tab.6).
Buttons
Reset Counters. Reset the counters’ results (Interfaces group).
Ethernet tab
The tab displays the counters of the Ethernet interfaces (RFC 1284 - Ethernet-like Statistics group).
Table
Each row of the table corresponds to a physical port for which are indicated:
Descr. Name of the port (see Tab.5.).
The remnant rows indicate the counters (see Tab.7).
Buttons
Reset Counters. Reset the counters’ results (Ethernet-like Statistics group).

Tab.6 Counters of Ethernet port (RFC 1213 - Interfaces group)
Packets with length Packet with length Packet with length

lower than longer than n between 64 and n
Counter 64 octects (MTU value) octets (MTU value) octets
(Undersize packet) (Oversize packet) (Good packet) FCS *
Description
Uni Broad Multi Uni Broad Multi Uni Broad Multi
cast cast cast cast cast cast cast cast cast
Received Octects x x x x x x x x x OK
Total number of octets received
x x x x x x x x x KO
Received Unicast Packets - - - - - - x - - OK

Total number of Unicast packets received
- - - - - - - - - KO
Received Not Unicast Packets - - - - - - - x x OK

Total number of Non-Unicast packets received
- - - - - - - - - KO
Received Discards (Packets) - - - - - - x x x OK

Total number of inbound packets which were discarded due
to forbidden forwarding or policing violation - - - - - - - - - KO
Received Errors x x x - - - - - - OK
Total number of inbound packets discarded because con-
tained errors. x x x x x x x x x KO
Transmitted Octects - - - - - - x x x OK
Total number of transmitted octets
- - - - - - - - - KO
Transmitted Unicast Packets - - - - - - x - - OK

Total number of Unicast packets transmitted
- - - - - - - - - KO
Transmitted Not Unicast Packets - - - - - - - x x OK

Total number of Non-Unicast packets transmitted
- - - - - - - - - KO
Transmitted Discards (Packets) - - - x x x x x x OK

Total number of outbound packets discarded
- - - - - - - - - KO
x Counter incremented
- Counter not incremented.
* OK. Frame Check Sequence (FCS) correct.
KO. Wrong FCS against an integer number (FCS Error) or not integer number of octets (Alignment Error).

Tab.7 Counters of Ethernet port (RFC 1284 - Ethernet-like Statistics group)

Description
Align. Errors - - - - - - - - - OK
A count of frames received on a particular interface that
are not an integral number of octets in length and do not
pass the FCS check.
The count represented by an instance of this object is in-
cremented when the Alignment Error status is returned by
the MAC service to the LLC (or other MAC user). Received x x x x x x x x x KO
frames for which multiple error conditions obtain are, ac-
cording to the conventions of IEEE 802.3 Layer Manage-
ment, counted exclusively according to the error status
presented to the LLC.
FCS Errors - - - - - - - - - OK
are an integral number of octets in length but do not pass
the FCS check.
cremented when the Frame Check Error status is returned
by the MAC service to the LLC (or other MAC user). Re- - - - x x x x x x KO
ceived frames for which multiple error conditions obtain
are, according to the conventions of IEEE 802.3 Layer Man-
agement, counted exclusively according to the error status
This value does not include packets shorter than 64 bytes.
Frame Too Long - - - x x x - - - OK

exceed the maximum permitted frame size.
cremented when the Frame Too Long status is returned by
the MAC service to the LLC (or other MAC user). Received - - - x x x - - - KO
frames for which multiple error conditions obtain are, ac-
cording to the conventions of IEEE 802.3 Layer Manage-
ment, counted exclusively according to the error status


DCN
MNGT Port Configuration. It manages the Ethernet port reserved to supervision of the equipment.
Routing Table. It manages the Routing Table of the equipment.

MNGT Port Configuration
WARNING The system can be managed by means of the:

• In-Band Management. The equipment management is added to the traffic coming from the LAN
ports or from the radio port.
• Out of Band management. The equipment management uses a dedicated port (MNGT).
The MNGT Port Configuration command manages the Ethernet port reserved to local and remote super-
vision of the equipment (management port).
Operations
Verify the configuration of the management port
Modify the IP Address/NetMask of the management port
Modify the IP Address used as Default Gateway
Modify the VLAN reserved for the in-band management
Modify the enabling status of management port
Modify the 802.1p priority for the management VLAN
Modify the DSCP value for the management VLAN
Modify the activation state of the autonegotiation for the management port
Modify the transmission speed of the management port
Modify the inversion status of the Tx and Rx lines of the management port
Modify the Bridge Port Type for the management port
Restart the auto negotiation procedure for the management port
Enable/disable the Loss of Signal Alarm for the management port
GUI
MNGT Port Configuration context
Verify the configuration of the management port
1. Select Base Band > DCN > MNGT Port Configuration.

The MNGT Port Configuration context displays the configuration of the management port.
2. In the IP Address box, set the IP address of the management port.

The address has to be compatible with the setting of the relevant Net Mask field.
3. In the Net Mask box, set the mask for the network address definition.
5. Press Store and confirm.

2. In the Default Gateway box, type the IP Address of the equipment used as Default Gateway.

WARNING The management VLAN must be present in the VLAN Table (see Static VLANs tab) and, in order
to operate correctly as VLAN for the In-band Management, management port must be enabled for the tran-
sit of the packets with VLAN ID equal to that of VLAN.
The VLAN can have, as Member Port, other Ethernet ports. In this case, even these ports will be used for
the contemporary transit of traffic and supervision (In-band Management).
2. Set, in the VLAN ID box, the wished VLAN.

The list will display all the VLAN’s registered in VLAN Table.

2. In the Admin State box, select the option:

• Disabled. The port is not enabled to use: the port does not transmit/receive traffic.
The port cannot transmit/receive traffic if the physical connection does not work (Link Status -
Down).
1. Select Base Band > DCN (LAN 3) > MNGT Port Configuration.
2. In the PCP Priority box, set a value between 0 and 7 (0 = lowest priority, 7 = highest priority).

2. In the DSCP Priority box, set a value between 0 and 63.
WARNING Remember that a peer-to-peer connection works properly if the two peers have set the same
autonegotiation management modality.
The values of the parameters Auto Neg. and Speed cannot be changed at the same time. First change one
of the parameters and confirm after having pressed Apply, then change the other parameter.
2. In the Auto Neg. box, select the option:

• Enabled. The autonegotiation is enabled. The port negotiates the transmission speed with the
peer at the other end of the Link, in order to find the optimal mutual connectivity. In autonego-
tiation, the modality Full Duplex without flow control is proposed.
• Disabled. The autonegotiation is disabled. The port uses the transmission speed configured in
the Speed box (see Modify the transmission speed of the management port), the flow control id
disabled and the operation modality is Full Duplex.
WARNING Operation available only if autonegotiation is disabled (Auto Neg. - Disabled).

If the autonegotiation is enabled, the speed is automatically configured according to the hardware after
having negotiated with the peer at the other end of the connection.
The values of the parameters Auto Neg. and Speed cannot be changed at the same time. First change one
of the parameters and confirm after having pressed Apply, then change the other parameter.
2. In the Speed box, select the option:

• 100 Mb. The data transmission speed through the port is 100 Mbit/s.
WARNING Operation available only if the port is disabled (Admin State - Disabled).
2. In the MDI/MDIX box, select the option:

• MDI. The inversion of the Tx and Rx lines is not active (Network Interface Card modality).
WARNING Operation available only if the current Bridge modality of the Switch is Provider Bridge (802.1ad)
or Provider Edge Bridge (see Bridge Mode Conf. context).
In Customer Bridge modality the port is always of type Customer Bridge.
This operation involves the re-configuration of the following port parameters to the default values: Auto
Neg., MTU and Ingress Filtering.
2. In the Bridge Port Type box, select the wished option.

If the Switch mode is Provider Bridge (802.1ad), the following options are available:
S-TAG.
If the Switch mode is Provider Edge Bridge, the following options are available:
S-TAG.
• Customer Network (port-based). Port which allows the routing of the traffic of a single user, in
case of Provider Edge Bridge. All the packets with C-TAG received on this port are routed on a
single S-VLAN.
If this type of port is selected, the relevant parameter Acceptable Frame Type must be set to
value UnTagged and Priority Tagged (see Port Settings tab).
• Customer Edge - (c-tagged). Port which allows the routing of the traffic of a single user already
associated to one C-TAG, in case of Provider Edge Bridge.
Restart the auto negotiation procedure for the management port
WARNING Operation available only if autonegotiation is enabled (Auto Neg. - Enabled).

2. Press Restart Auto Neg. and confirm.

WARNING The alarm can be enabled/disabled using the Alarm Severity Config. command.
The only difference is that, with this operation, you intervene only on the alarm Loss of Signal of the man-
agement port while, in the context Alarm Severity Config, you intervene on the alarm Loss of Signal of all
the LANs.
Depending on the setting made in the two contexts, the alarm status will be as indicated in Tab.8.
2. In the Port Alarm Report box, select the option:

• Disabled, to disable the alarm. The detection of the alarm is not registered in the equipment
controller and, as consequence, is not communicated to a possible management program: as
the alarm had never occurred.
• Enabled, to enable the alarm. The detection of the alarm is registered in the equipment control-
ler and, if the forwarding of the relevant trap is enabled (see Alarm Severity Config. context),
the alarm is communicated to the management system and displayed in the current alarms and
the history alarms.
Tab.8 Enabling status of the Loss of Signal alarm
Context
MNGT Port Configuration Alarm Severity Config * Loss of Signal Alarm

(Port Alarm Report) (Severity)
Enabled Disabled Disabled alarm
Enabled Status, Warning, Minor, Major or Critical Enabled alarm
Disabled Disabled Disabled alarm

Disabled Status, Warning, Minor, Major or Critical Disabled alarm
* In this context the Loss of Signal Alarm is called ifextLosAlarm.

MNGT Port Configuration context
The context displays the configuration of the Ethernet port reserved to local and remote supervision of the
equipment (management port).
Parameters
IP Address. IP address of the management port.
Net Mask. Mask for the network address definition.
Default Gateway. IP Address of the equipment used as Default Gateway from the management
port.
VLAN ID. VLAN reserved for the in band supervision (In-Band Management).
PHYSICAL INTERFACE
Port Alarm Report. Enabling state of the Loss of Signal Alarm for the management port:
• Disabled. Alarm disabled: the detection of the alarm is not registered in the
equipment controller and, as consequence, is not communicated to a possible
management program: as the alarm had never occurred.
• Enabled. Alarm enabled: the detection of the alarm is registered in the equip-
ment controller and, if the forwarding of the relevant trap is enabled (see
Alarm Severity Config. context), the alarm is communicated to the manage-
ment system and displayed in the current alarms and the history alarms.
Admin State. Enabling state of the management port:
• Disabled. The port is not enabled to use: the port does not transmit/receive
traffic.
The port cannot transmit/receive traffic if the physical connection does not work.
PCP Priority. 802.1p priority present in Tag VLAN of the management VLAN.
DSCP Priority. DSCP (Differentiated Services Code Point) value inserted in the heading
of the IP packets transported by the management Vlan.
Link Status. Status of the physical connection between the management port and a de-
vice in network:
• Up. The physical connection is active and ready for the traffic exchange.
• Down. The physical connection does not work: no physical connection has
been enabled or the established physical connection is not active or is defec-
tive.
Auto Neg. Activation state of the autonegotiation for the management port:
• Enabled. The autonegotiation is enabled. The port negotiates the transmission
speed with the peer at the other end of the Link, in order to find the optimal
mutual connectivity. In autonegotiation, the Full Duplex modality without flow
control is proposed.
• Disabled. The autonegotiation is disabled. The port uses the transmission
speed configured in the Speed box, the flow control is disabled and the oper-
ation modality is Full Duplex.
Speed. Data transmission speed of the management port.
MDI/MDIX. Inversion status of the Tx and Rx lines:
• MDI. The inversion of the Tx and Rx lines is not active (Network Interface Card
modality).
Bridge Port Type. Type of Bridge port:
equipment implements a Customer Bridge.
Option available only when the Switch is in Customer Bridge modality.

TAG’s can be present within one S-TAG.
• Provider Network (Proprietary). Not standard port which allows the manage-
ment of the packets with C-Tag (EtherType 0x8100) or without Tag within a
Provider or Provider Edge Bridge context. It is used for the forwarding of the
Management packets from/to the equipment controller.
ceived on this port are routed on a single S-VLAN.
• Customer Edge (c-tagged). Port which allows the routing of the traffic of a sin-
gle user already associated to one C-TAG, in case of Provider Edge Bridge.
Buttons
Store. Store the values into the equipment controller.
Restart. Execute the equipment software reset.
Retrieve. Read again the values set into the equipment controller.
Restart Auto Neg. Restart the auto negotiation procedure for the management port.
See also
MNGT Port Configuration (command)

Routing Table
WARNING When all pieces of equipment belongs to the same IP network and sending packets to other net-
works is not necessary, the Routing Table must not be necessarily defined because the network can man-
age its own internal traffic. Setting the Routing Table is necessary when equipment must send packets
between two different networks, then the traffic must be re-routed from a network to another one (routing
functionality of the equipment).
The Routing Table command manages the Routing Table of the equipment.
Operations
Verify the Routing Table of the equipment
Add an element to the Routing Table
Remove one or more elements from the Routing Table
GUI
Routing Table context
Verify the Routing Table of the equipment
1. Select Base Band > DCN > Routing Table.

The Routing Table context displays the Routing Table of the equipment.
Add an element to the Routing Table
WARNING A maximum of 128 items can be created.
2. Press Add.
3. Into the Destination box, type the IP Address of the IP network or of the destination element.
4. Into the Subnet Mask box, type the mask for the destination IP network.
5. Set, in Next Hop box, the type of the next element by which the IP network or the destination element
can be reached:
• Interface. Local interface to the equipment, where the management traffic is routed via VLAN
(see MNGT Port Configuration context).
This element is mandatorily associated to the routing via VLAN.
• Gateway. Network element which allows reaching a remote network.
6. If, in the step before, the selected value is Gateway, set the IP address of the Gateway equipment for
the destination network in the Gateway box.
7. Set, in the Distance box, the metric value of the destination (value between 1 and 254).

The new element is inserted into the table.

Remove one or more elements from the Routing Table
2. Select the element of the Routing Table.

Multiple selections can be executed using the Ctrl or Shift keys.

The system deletes the element into the Routing Table of the equipment.

Routing Table context
The context shows the Routing Table currently used by the equipment.
Table
Each row of the table corresponds to an item of the Routing Table for which are indicated:
Destination. IP address of the IP network or of the destination element.
Gateway. IP address of the equipment that acts as Gateway.
Parameter not meaningful for the elements relevant to the equipment local interfaces
(VLAN).
Subnet Mask. IP NetMask of the IP network or of the destination element.
Interface. Equipment local interface (VLAN) by which the IP network of the destination
element can be reached (see MNGT Port Configuration context.
Parameter not meaningful for the elements which identify the Gateway.
Distance. Metric value of the destination.
Protocol. Modality of connection (direct or indirect) between the equipment and desti-
nation IP network or element:
• Connected. The IP network or the element are directly connected to the equip-
ment interface. The IP network or the element are automatically inserted by
the equipment software according to their own IP address and NetMask.
• Static. The IP network or the element are not directly reachable from the
equipment interfaces. The IP network or the element have been manually in-
serted by the user (static element).
Selecting the heading of the Distance column, the rows of the table are sorted in increasing al-
phanumeric order with respect to the considered column and an arrow is displayed with the tip
directed upwards. The next selection sorts the rows in decreasing order (an arrow is displayed
Buttons
Add. Add an element to the Routing Table.

Remove. Remove one or more elements from the Routing Table.
See also
Routing Table (command)

SYNCHRONISATION
The Synchronisation command manages the sources and the outputs of synchronism
Operations
T0 SYNCHRONISM
Verify the status and configuration of the T0 synchronism

Force the status of the T0 synchronisation
Set the Hold Off Time parameter
Set the WTR Time parameter
Set the threshold levels of the LTI alarm
Enable/disable the use of the source quality as criterion to select the synchronism
SYNCHRONISM SOURCES
Verify/modify the management of synchronisation

Verify the status and configuration of the synchronism sources
Enable/disable the use of a synchronism source
Modify the use priority of a synchronism source
Force the use of a synchronism source
Set a synchronism source as preferential
Force the quality level in input and/or output of a synchronism source
Restore the availability of a source for the selection of the T0 synchronism without wait-
ing for the expiry of Wait Time
Verify/modify the management of SSM messages
Verify/modify the line synchronism direction of the LAN’s
GUI
Synchronisation context
See also
Synchronisation (info)
Verify the status and configuration of the T0 synchronism

1. Select Synchronisation.
The General tab displays the configuration parameters and the alarms status of the T0 synchronism.

The Status Control parameter indicates the status of T0 synchronism:

• Free Running. The status of Free Running is forced (synchronism T0 is generated by the equip-
ment internal reference - Internal Source).
• Hold Over. The status of Hold Over is forced.
• Locked. The synchronism is locked to an external source.
3. Press Apply.
Only if you are activating the forcing (selection of the Free Running or Hold Over option) a message
warns that you are executing a forcing and displays the current setting of timeout.


The Hold Off Time parameter indicates the time (expressed in ms) during which the system keeps the
evaluated frequency of an invalid synchronism source (absent or degraded).
At the end of the Hold Off time, the invalid source will be rejected and it will be used the first input
source having a valid signal.
2. To change the parameter, set into the box a value between 300 and 1800 msec.

The WTR Time parameter indicates the time (expressed in minutes) that has to pass in such a way to
allow to the selected input source having a valid signal to be really used within the process for the se-
lection of T0 synchronism.
2. To change the parameter, set a value between 0 and 12 min.

The LTI Set Time and LTI Reset Time parameters point out the threshold level of LTI alarm (Timing
Synk Loss Alarm):
• LTI Set Time. Threshold value - expressed as number of consecutive seconds with the presence
of the LTI alarm - over which the system activates the alarm itself.
• LTI Reset Time. Threshold value - expressed as number of consecutive seconds without the
presence of the LTI alarm - over which the system deactivates the alarm itself.
2. To change the parameter, set the new values in the specific boxes (allowed interval between 0 and 60
seconds).

Enable/disable the use of the source quality as criterion to select the syn-
chronism
WARNING Operation available only if the Sync Quality management feature is enabled (see Equipment Fea-
tures tab).
The parameter Status indicates the status of use of the source quality level as criterion to select the
synchronism:
• On. Use enabled.
• Off. Use disabled.


WARNING Before disabling the synchronisation management (all the sources Dis.), it is suggested to tem-
porarily force the status of synchronism T0 to Free Running (and then reset it to Locked) to avoid the oc-
currence of the alarms BASE BAND Sets T0 Fail Alarm and BASE BAND Sets Holdover Status (see Force
the status of the T0 synchronisation).
2. Select the T0 tab.

The Priority column displays the management of synchronisation:
• If all the sources are disabled (value Dis.), the synchronisation management has been disabled
(the clocks are generated by the internal local reference).
• If at least one source is enabled, the synchronisation management is enabled.
3. To change the management to Enable/disable the use of a synchronism source.
Verify the status and configuration of the synchronism sources


The tab displays the status and configuration of the synchronism sources.


The Priority column shows the usage status of each source.
3. To enable the use of a source, select the specific Priority box and then a number between 1 and 9 ac-
cording to the desired priority level to assign to the source (1: maximum priority, 9: minimum priority).

To disable the use of the source, select the specific Priority box and then the Dis. value.

WARNING Operation available only if the use of the synchronism source is active.

The Priority column shows the priority level of each source.
3. To change the priority level of a source, select the specific Priority box and then a number between 1
and 9 according to the desired priority level to be assigned to the source (1: maximum priority, 9: min-
imum priority).


Operation meaningful only if the use of the synchronism source is active.

The Forced Switch column shows the forcing status of each source.
3. To change the forcing status of a source, select the specific Forced Switch box and then the option:
• Off, not to force the use of the source for the generation of the synchronism.
• On, to force the use of the source for the generation of the synchronism.
4. Press Apply changes.

Only if you are activating the forcing a message warns that you are executing a forcing and displays
the current setting of timeout.


WARNING Operation meaningful only if the use of the synchronism source is active.

The Preferential Switch column shows if the source is used as preferential.

3. To change the preferential status of a source, select the specific Preferential Switch box and then the
option:
• Off. The synchronism source is not preferential as opposed to the other enabled synchronism
sources.
• On. The synchronism source is preferential as opposed to the other enabled synchronism sourc-
es and (in absence of alarms causing its degrade or forced sources) is used for the generation
of the synchronism.

WARNING Operation available only if the use of the quality, as criterion for the selection of the synchro-
nism, is enabled.

For every synchronism source, the parameter Ovw Rx Qlty indicates the forcing status of the quality
level in reception; while the parameter Ovw Tx Qlty indicates the forcing status of the quality level in
transmission.
3. To change the parameters, select the Ovw Rx Qlty or Ovw Tx Qlty box and than the option:
• none. The quality of the synchronism source is not forced. The quality is that taken from the
SSM messages i enabled (see Quality of synchronism source).
• PRC. The source quality complies with the G.781/G.8264 ITU-T Recom. that defines the param-
eters of the primary reference clock.
• SSUT. The source quality complies with the G.781/G.8264 ITU-T Recom. that defines the pa-
rameters of the transit synchronism units.
• SSUL. The source quality complies with the G.781/G.8264 ITU-T Recom. that defines the pa-
rameters of the local synchronism units.
• SEC. The source quality complies with the G.781/G.8264 ITU-T Recom. that defines the param-
eters of the equipment clock.
• DNU. The source has not to be used for the synchronization.
Restore the availability of a source for the selection of the T0 synchronism

without waiting for the expiry of Wait Time
3. Select the source, with valid signal, whose availability you wish to restore for the generation of T0 syn-
chronism.
4. Press Wtr Clear and confirm.
The source is immediately used for the generation of T0 synchronism. The period Wtr Time is consid-
ered elapsed.

WARNING Operation available only if the use of the quality, as criterion for the choice of the synchronism,
is enabled.
2. Select the LAN SSM tab.

The tab shows the configuration parameters and the enabling status of the SSM messages (Synchro-
nization Status Message) for the LAN interfaces.
3. To change the management of the SSM messages, in the SSM Enable box in corresponding of the
wished LAN, select the option:
• On. The SSM messages are managed by the LAN.
• Off. The messages are not managed.

WARNING Operation available only for ports with electrical interface.

Operation available only for the LAN’s not selected as synchronisation sources and for the LAN’s selected
as synchronisation sources which the use of SSM messages is not active for. When one LAN is selected as
synchronisation source and the use of SSM messages is active for it, the role of the line synchronism is
dynamically managed by the system.
2. Select the 1000Base-T Role tab.

The tab shows the configuration parameters and the line synchronism direction for the LAN with elec-
trical interface.
3. To modify the direction of a LAN, select the relevant box in the Role column and then one of the fol-
lowing option:
• Slave. The line synchronism is generated with the clock retrieved from the line (Loop Time).
• Master. The line synchronism is generated starting from the local clock.
• Auto. The assignment of role Master or Slave of the line synchronism is automatically managed
by SSM independently from the setting of the port parameters.

The context displays status and configuration of the sources and the outputs of synchronism.
Tabs
General tab. Configuration and alarms status of the T0 synchronism.
T0 tab. Configuration and status of the synchronism sources.
LAN SSM tab. Enabling status of the SSM messages for the traffic LAN’s.
1000Base-T Role tab. Role of the LAN synchronism sources.
Buttons
See also
Synchronisation (command)
General tab
The tab displays the configuration parameters and the alarms status of the T0 synchronism.
Parameters
ALARMS
Alarms status of the T0 synchronism. The colour of each box displays the status of the
specific alarm:
SETTINGS
Status Control. Status of T0 synchronism:
• Free Running. The status of Free Running is forced (synchronism T0 is gener-
ated by the equipment internal reference - Internal Source).
TIME
Hold Off Time. Time (expressed in ms) during which the system keeps the evaluated
frequency of an invalid synchronism source (absent or degraded). At the end of the Hold
Off time, the invalid source will be rejected and it will be used the first input source having
a valid signal.
WTR Time. Time (expressed in minutes) that has to pass in such a way to allow to the
selected input source having a valid signal to be really used within the process for the
selection of T0 synchronism.
LTI Set Time / LTI Reset Time. Threshold level of LTI alarm (TimingSynkLossAlarm):
• LTI Set Time. Threshold value - expressed as number of consecutive seconds
with the presence of the LTI alarm - over which the system activates the alarm
itself.
• LTI Reset Time. Threshold value - expressed as number of consecutive sec-
onds without the presence of the LTI alarm - over which the system deacti-
vates the alarm itself.

QUALITY
Area available only if the Sync Quality management feature is enabled (see Equipment Features
tab).
Current. Current quality level of the T0 synchronism:
• none. The quality of the synchronism source is not forced. The quality is that
taken from the SSM messages i enabled (see Quality of synchronism source).
• PRC. The source quality complies with the G.781/G.8264 ITU-T Recom. that
defines the parameters of the primary reference clock.
• SSUT. The source quality complies with the G.781/G.8264 ITU-T Recom. that
defines the parameters of the transit synchronism units.
• SSUL. The source quality complies with the G.781/G.8264 ITU-T Recom. that
defines the parameters of the local synchronism units.
• SEC. The source quality complies with the G.781/G.8264 ITU-T Recom. that
defines the parameters of the equipment clock.
Generally the quality of T0 synchronism corresponds to the quality of the source from
which T0 is retrieved.
Status. Status of use of the source quality level as criterion for the selection of the syn-
chronism:
• On. Use enabled.
• Off. Use not enabled.
See also
T0 tab
The tab displays the Configuration and status of the synchronism T0.
Table
Every row of the table corresponds to one source for which are indicated:
Name. Synchronism source name (see Tab.9).
Source. Not meaningful in this context.
Priority. Status and priority use of the source:
• Dis. The synchronism source is not used.
• <1 ÷ 9>. The synchronism source is enabled and has a priority level pointed
out by the number (1: maximum priority, 9: minimum priority).
WARNING If all the sources are disabled, the synchronisation management is disabled.
Forced Switch. Forced use of the source:
• Off. The source has not been manually forced for the generation of the T0 syn-
chronism.
• On <light blue box>. The source has been manually forced for the generation
of the T0 synchronism (Manual Operation).
Preferential Switch. Status of preferential usage of the source:
• Off. The synchronism source is not preferential as opposed to the other ena-
bled synchronism sources.

• On. The synchronism source is preferential as opposed to the other enabled
synchronism sources and (in absence of alarms causing its degrade or forced
sources) is used for the generation of the synchronism.
Sync Loss / Sync Drift. Respectively status of the alarm Timing Synk Loss Alarm and
Timing Synk Drift Alarm relevant to the source. The colour of each box displays the status
of the specific alarm:
Rx Quality. Source quality level in reception:
• UNK. The quality level is unavailable or unknown.
The wording (ovw) indicates that the quality level in reception is forced by the operator.
Tx Quality. Source quality level in transmission.
The quality level in transmission of the synchronism source in input is the result of the
protocol calculation. The displayed values are the same described for the Rx Quality pa-
rameter.
Ovw Rx Qlty. Forcing status of the source quality level in reception:
• UNK. The quality level is unavailable or unknown
• none. The quality of the synchronism source is not forced. The quality is that
taken from the SSM messages i enabled (see Quality of synchronism source).
Ovw Tx Qlty. Forcing status of the quality level in transmission of the source.
The displayed values are the same described for the Ovw Rx Qlty parameter.
The Rx Quality, Tx Quality, Ovw Rx Qlty and Ovw Tx Qlty parameters are present only if the use of
the quality, as criterion for the choice of the synchronism, is enabled.
The source of synchronism whose row has red border indicates the source which the equipment ex-
tracts the synchronization T0 from.
When the source, which the synchronization is extracted from, changes, the row relevant to the new
source will become yellow and will blink before becoming of color sky-blue with red border.
Buttons

Wtr clear. Restore the availability of a source for the selection of the T0 synchronism without
waiting for the expiry of Wait Time.
See also
LAN SSM tab
WARNING Tab available only if the use of the quality, as criterion for the choice of the synchronism, is en-
abled.
The tab shows the enabling status of the SSM messages for the traffic LAN’s.
Table
Every row of the table corresponds to a LAN for which are indicated:
Port. Identifier of the port. The value ID is the combination of the slot number and the
port number (slot number/port number).
Description. Name of the port (see Tab.5.).
• Copper. Ethernet port with electrical interface.
• Fiber. Ethernet port with optical interface.
• ---. Parameter not meaningful for the port (for example, Radio port).
SSM Enable. Management status of the SSM messages for the equipment LAN’s:
• On. The SSM messages are managed by the LAN.
• Off. The messages are not managed.
Rx Pkts. Number of packets received on the corresponding port.
Tx Pkts. Number of packets transmitted by the corresponding port.
Rx Dropped Pkts. Number of packets dropped among those received on the corre-
sponding port.
Rx Errored Pkts. Number of errored packets among those received on the correspond-
ing port.
Buttons
See also

1000Base-T Role tab
The tab displays the direction of the line synchronism for the LAN’s with electrical interface.
Table
Every row of the table corresponds to a LAN for which are indicated:
Port. Identifier of the port. Identifier of the port. The value ID is the combination of the
slot number and the port number (slot number/port number).
• Copper. Ethernet port with electrical interface.
Role. Line synchronism direction for the LAN’s with electrical interface displayed in the
table:
• Slave. The line synchronism is generated with the clock retrieved from the line
(Loop Time).
• Master. The line synchronism is generated starting from the local clock.
• Auto. The assignment of role Master or Slave of the line synchronism is auto-
matically managed by SSM independently from the setting of the port param-
eters.
Buttons
See also

Topics
Management of synchronisation
Synchronism sources
Enabling of the synchronism sources
Priority of the synchronism source
Quality of synchronism source
Forcing of a synchronism source
Function of preferential synchronism source
Internal synchronism T0
See also
Synchronisation (command)
Management of synchronisation
ALFOplus2 equipment can be configured to operate with synchronisation enabled or disabled.

When the synchronisation is disable, the synchronisation is not managed: the clocks are generated by the
local internal reference.
When the synchronisation is enabled, the synchronism source, enabled with the highest priority, is used
to synchronise the equipment (if a forcing or a preferential is not active).
The user can enable or disable the management of synchronisation as he wishes (see Verify/modify the
management of synchronisation).
Synchronism sources
The equipment has more synchronism sources as depicted in Tab.9.
Tab.9 Synchronism sources
Name Type Configuration
TE LAN 1 LAN Eth Source extracted from the LAN 1 of Ethernet Switch
TRX A Radio Synchronism from the remote terminal (transceiver A).

Option meaningful if a Radio Link using the transceiver A is defined
TRX B Radio Synchronism from the remote terminal (transceiver B).

Option meaningful if a Radio Link using the transceiver B is defined
Internal - Source extracted from an its own internal reference (25MHz STRA-
TUM 3e)

Enabling of the synchronism sources
A synchronism source, in order to be used, must be enabled by the user (see Enable/disable the use of a
synchronism source).
Priority of the synchronism source
A priority level can be associated to every synchronism source (see Modify the use priority of a synchronism
source).
The source with the highest priority level and whose signal is valid, is used to synchronize the equipment
(if a forcing or a preferential source is not active).
The priority level of the synchronism source is pointed out by a number between 1 and 9, where 1 indicates
the highest priority and 9 the lowest one.
Generally the equipment takes the synchronism from the source with the highest priority level: if this
source is missing or is degraded, the synchronism is taken from the source with priority level immediately
lower.
When the source with highest priority level returns to be valid, the equipment after the WTR time will au-
tomatically start to use it to take the synchronism. If all the synchronism sources (set by the user) become
unavailable, the equipment automatically takes the synchronism from its own internal reference.
The degradation of the signal is caused by the presence of, at least, one of the following conditions:
• The source is not physically present.
• The difference between the source frequency and the internal reference source (STRATUM 3e)
is greater than ± 7 ppm.
If two or more sources with the same priority are activated, these sources will be inserted into a circular
and not Revertive list.
Quality of synchronism source
Every synchronism source is characterized by a quality level.

When the use of quality is enabled, it concurs in the selection of the source to use for the synchronisation
in the following way: the source with higher quality level, and whose signal is valid, is used to synchronize
the equipment (if a forcing is not active).
The quality level of one source is contained in the Synchronisation Status Messages (SSM). These messag-
es are periodically transmitted; the absence of a message is considered as condition of failure of the syn-
chronisation mechanism.
The availability quality levels, from higher to lower level, are listed here below:
• PRC (Primary Reference Clock). The source quality is in compliance with G.781 ITU-T Recom.
with extension to G.8264 for Ethernet streams which defines the parameters of the primary ref-
erence clock.
• SSUT (Synchronisation Supply Unit Transit). The source quality is in compliance with G.781 ITU-
T Recom. with extension to G.8264 for Ethernet streams which defines the parameters of the
transit synchronism units.
• SSUL (Synchronisation Supply Unit Local). The source quality is in compliance with G.781 ITU-
T Recom. with extension to G.8264 for Ethernet streams which defines the parameters of the
synchronism local units.
• SEC (SDH Equipment Clock). The source quality is in compliance with G.781 ITU-T Recom. with
extension to G.8264 for Ethernet streams which defines the parameters of the equipment clock.
Depending on the type of synchronism source, the modality used to insert and extract the SSM messages
changes as pointed out here below.

Synchronism sources TE LAN 1, TE LAN 2, TE LAN 3 and TE LAN 4 (Ethernet)
For the synchronism sources TE LAN 1, TE LAN 2, TE LAN 3 and TE LAN 4, the quality manage-
ment depends on the LAN interface and by the management of the SSM messages as indicated
here below.
Type of LAN’s on SSM messages Line synchronism Quality management Quality management
the equipment management direction (role) * in input (Rx) in output (Tx)
LAN with electrical Enable Role dynamically Quality value (SSM) is ex- The quality value of T0 or
interface managed by the tracted from the received DNU (if T0 is derived from
system packet the considered LAN) is in-
serted in the transmitted
packet.
Disable Role set by Quality value is DNU SSM messages are not
operator ** transmitted
LAN with optical Enable Quality value (SSM) is ex- The quality value of T0 or
interface tracted from the received DNU (if T0 is derived from
- packet the considered LAN) is in-
packet.
Disable Quality value is DNU SSM messages are not

-
transmitted
* Parameter meaningful only for LAN with 1000Base-T electrical interface.

** See Verify/modify the line synchronism direction of the LAN’s
Synchronism sources Radio

For the synchronism source Radio (TRX A and TRX B), the quality management depends on the
management of the SSM messages as indicated here below.
Synchronism SSM messages Quality management Quality management

sources management in input (Rx) in output (Tx)
Radio Enable Quality value (SSM) is ex- The quality value of T0 or

tracted from the received DNU (if T0 is derived from
packet the considered LAN) is in-
packet.
Disable Quality value is DNU SSM messages are not

transmitted
WEB LCT
As regards the quality management via the GUI, it is possible:
WARNING The quality of the synchronism sources is a feature subjected to enabling (Sync quality man-
agement equipment feature).
If this feature is not enabled, all the parameters relevant to the quality management will not be available
(see Equipment Features tab).
Forcing of a synchronism source
This function foresees the user can force the selection of one synchronism source (see Force the use of a
synchronism source).

This forcing is made without considering the status and the priority of the source.
This function must not be used for the normal operation of the synchronism. It is a maintenance operation
and remains active until the user disables it or the Timeout period of the manual operations expires (if set).
Function of preferential synchronism source
This function foresees the choice of a source to use as preferential among those enabled (see Set a syn-
chronism source as preferential).
When the function of preferential source is not active, the internal synchronism is taken from the enabled
source with highest priority.
When the function of preferential source is activated for a source, this source will be used (in absence of
alarms causing its degradation or forced sources) to take the internal synchronism independently from its
priority level.
This condition is maintained until when the user disables the function of preferential source or the source
signal becomes degraded.
Internal synchronism T0
The synchronism source, which the internal synchronism T0 is extracted from, is determined by the SETS
of the equipment according to the following order of criteria:
• Status of the source (enabled/disabled)
• Forcing of the source
• Status of the signal (valid/degraded)
• Preferential source
• Source priority
The internal synchronism T0 can assume one of the following statuses:

The user can force the status of the internal synchronism T0 (see Force the status of the T0 synchronisa-
tion).
The forcing of the status Hold Over or Free Running is not the normal operation of the synchronism T0.
These forcings are maintenance operations and remain active until when the user does not disable them
or the Timeout period of the manual operation expires (if set).

RADIO
WARNING Option available only for equipment with at least one Radio Link defined.
Radio Branch. It manages the radio parameters.

Radio Branch
For the equipment with Radio Link in 1+0 or 2+0 XPIC configuration is present the Radio Branch com-
mand. For the 2+0 XPIC configuration, the parameters present in the context refer both to transceiver A
and transceiver B.
For the equipment in 2x(1+0) radio configuration the commands Radio Branch TRX A (transceiver A pa-
rameters) and Radio Branch TRX B (transceiver B parameters) are present.
The Radio Branch command manages the radio parameters.
Operations
Verify/modify the duplex frequency (Dplx Freq)
Verify/modify the frequency which the equipment transmitter is tuned on (Tx Freq)
Verify/modify the resolution of the received power (Prx) (Measurements Resolutions)
Verify/modify the resolution of the transmitted power (Ptx) (Measurements Resolutions)
Verify/modify the functioning status of the ATPC (Tx Power Control)
Verify/modify the maximum output power value at the transmitter (Max Ptx)
Verify/modify the range of the ATPC regulation (ATPC Regulation)
Verify/modify the threshold of the ATPC device (ATPC Thresholds on Local PRx)
GUI
Radio Branch context
Verify/modify the duplex frequency
1. Select Radio > Radio Branch.

The Dplx Freq parameter indicates the duplex frequency (MHz) of the equipped radio.
The displayed value is always positive, independently from the position of the transmission frequency
with respect to the receiving frequency.
Verify/modify the frequency which the equipment transmitter is tuned on
WARNING Setting the parameter does NOT automatically modify even the RF frequency of remote equip-
ment.
Before setting the transmission frequency of the equipment, set the duplex frequency value.

The Tx Freq parameter indicates the transmission frequency of the equipment.
2. To change the parameter, it is possible to:
• Set in the Tx Freq box the wished frequency value using the fine tuning step (typically 125 KHz).
• Press Freq. Table to display the table of the frequencies (see ITU-R F2006). Select the wished
value and press Ok. If this value was not present in the table, the radio can be however tuned
with fine tuning.

Buttons available only if the channelling file has been previously loaded on the equipment. In
case of fine-step file (less than 1 MHz), the frequency table does not contain any value to avoid
reading not meaningful values.
Verify/modify the resolution of the received power (Prx)

The Prx: <current value> dB parameter indicates the resolution used to communicate the changes of
the power received by the equipment (Prx) to a possible external management program (trap Prx
change).
2. To change the parameter, move the cursor on the wished value.
Verify/modify the resolution of the transmitted power (Ptx)

The Ptx: <current value> dB parameter indicates the resolution used to communicate the changes of
the power transmitted by the equipment (Ptx) to a possible external management program (trap Ptx
change).
Verify/modify the functioning status of the ATPC
2. Select the ODU Powers tab.

The Tx Power Control area indicates the functioning status of the ATPC:
• Manual. The ATPC device is in manual functioning mode (ATPC function disable).
In this condition, it is possible to adjust the maximum output power (Max Ptx cursor).
• Automatic. The ATPC device is in automatic functioning mode.
In this condition, the transmitted power is automatically adjusted according to the level of the
signal at reception.
The thresholds of the ATPC device can be configured (see Verify/modify the threshold of the
ATPC device). Then, it is possible to adjust the maximum output power (see Verify/modify the
maximum output power value at the transmitter).

Verify/modify the maximum output power value at the transmitter
WARNING Asymmetrical configuration of the Radio Link between local and remote equipment, as regards
the value of Ptx / modulation, are not supported.

The Max Ptx: <current value> dBm parameter indicates the maximum output power value at the trans-
mitter (Ptx nominal value).
3. To change the parameter, move the cursor on the wished value. If you wish to set the maximum value
of available range, activate the box ATPC Full Range.
Verify/modify the range of the ATPC regulation
WARNING Operation available only if the ATPC device is in automatic functioning mode (Tx Power Control
parameter - Automatic value).

The ATPC Regulation: <current value> dB parameter indicates the range of the ATPC regulation (ex-
pressed in dB) with respect to the current value of maximum Tx output, that is intended as the upper
limit of the range.
Verify/modify the threshold of the ATPC device

In the ATPC Thresholds on Local PRx area the threshold of the ATPC is pointed out:
• High: <current value> dBm. Threshold of the ATPC device to decrease the transmitted power
when the received field from the local equipment is equal to or higher than the set threshold
value.
• Low: <current value> dBm. Threshold of the ATPC device to increase the transmitted power
when the received field from the local equipment is equal to or lower than the set threshold val-
ue.
3. To change the threshold move the High and/or Low cursor to the wished value.

Radio Branch context
For the equipment with Radio Link in 1+0 or 2+0 XPIC configuration is present the Radio Branch com-
mand. For the 2+0 XPIC configuration, the parameters present in the context refer both to transceiver A
and transceiver B.
For the equipment in 2x(1+0) radio configuration there are the commands Radio Branch TRX A (which
opens the context area Radio Branch TRX A containing the radio parameters of transceiver A) and Radio
Branch TRX B (which opens the context area Radio Branch TRX B containing the radio parameters of
transceiver B).
The context displays the radio parameters.
Tabs
ODU Settings tab. Radio parameters: RF channel, power resolution.
ODU Powers tab. Radio parameters: ATPC.
Buttons
Apply. Confirms the changes.
See also
Radio Branch (command)
ODU Settings tab
The tab displays the radio parameters (RF channel, measurements resolutions).
Parameters
TX FREQUENCY SELECTOR
Tx Freq. Frequency of the radio transmission. The wording:
• Must be Set indicates that for the radio a channel is not planned.
• HW Fail indicates a hardware problem.
Dplx Freq. Frequency of duplex.
MEASUREMENTS RESOLUTION
Ptx. Resolution used to communicate the changes of the power transmitted by the equip-
ment (Ptx) to a possible external management program (trap Ptx change).
For instance, if the operator sets a resolution of 2 dB and the last communicated Ptx value
corresponds to 10 dBm, the equipment will communicate to the program the changing of
the transmitted power when the Ptx gets a value < 8 or > 12.
Prx. Resolution used to communicate the changes of the power received by the equip-
ment (Prx) to a possible external management program (trap Prx change).
For instance, if the operator sets a resolution of 2 dB and the last communicated PRx val-
ue corresponds to -70 dBm, the equipment will communicate to the program the chang-
ing of the transmitted power when the PRx gets a value <-72 or > -68.
Buttons
Freq. Table. Display the table of the preferential frequencies.
See also
Verify/modify the duplex frequency (Dplx Freq)

Verify/modify the frequency which the equipment transmitter is tuned on (Tx Freq)
Verify/modify the resolution of the received power (Prx) (Measurements Resolutions)
Verify/modify the resolution of the transmitted power (Ptx) (Measurements Resolutions)
ODU Powers tab
The tab displays the radio parameters (ATPC).
Parameters
TX POWER CONTROL
Operating status of the ATPC device:
• Manual. The ATPC device is in manual functioning mode (ATPC function disa-
ble).
• Automatic. The ATPC device is in automatic functioning mode.
Max Ptx <current value> dBm. Maximum output power value at the transmitter. The
parameter affects the ATPC device as when it is in manual functioning mode as in auto-
matic one.
ATPC Regulation <current value> dB. Range of the ATPC regulation (expressed in
dB) with respect to the current value of maximum Tx output, that is intended as the up-
per limit of the range.
Parameter available only if the ATPC device is in automatic functioning mode (Tx Power
Control parameter - Automatic value) and the box ATPC Full Range is not active.
ATPC Full Range. The active box ( ) indicates that the ATPC device operates at the
maximum limit of the range; the inactive box indicates that the maximum limit of the
ATPC device is indicated by the parameter ATPC Regulation.
Parameter available only if the ATPC device is in automatic functioning mode (Tx Power
Control parameter - Automatic value).
ATPC THRESHOLDS ON LOCAL PRX

High: <current value> dBm. Threshold of the ATPC device to decrease the transmitted
power when the received field from the local equipment is equal to or higher than the set
threshold value
Low: <current value> dBm. Threshold of the ATPC device to increase the transmitted
power when the received field from the local equipment is equal to or lower than the set
threshold value.
See also
Verify/modify the functioning status of the ATPC (Tx Power Control)
Verify/modify the maximum output power value at the transmitter (Max Ptx)
Verify/modify the range of the ATPC regulation (ATPC Regulation)
Verify/modify the threshold of the ATPC device (ATPC Thresholds on Local PRx)

MAINTENANCE
S/N Meas. It displays the measure of the signal/noise ratio (S/N).

Radio BER. It manages the measure of Radio BER value.
MAB. It manages the Microwave Adaptive Bandwidth (MAB) function.
Radio Loop & Cmd. It manages the digital loops.
Manual Operations. It manages the manual operations.
RMON. It manages the count of the RMon statistics.

S/N Meas
For the equipment with Radio Link in 1+0 configuration is present the S/N Meas command. For the equip-
ment with Radio Link in 2+0 XPIC configuration or equipment in 2x(1+0) radio configuration are present
the S/N Meas TRX A (transceiver A, S/N measure) and S/N Meas TRX B (transceiver B, S/N measure)
commands.
The S/N Meas command displays the measure of the signal/noise ratio (S/N), which allows evaluating the
quality of the radio communication channel.
Operations
Verify the value of the S/N measure
Update the value of the S/N measure
GUI
S/N Meas. context
Verify the value of the S/N measure
1. Select Maintenance > S/N Meas.

The S/N Meas. context displays the value of the signal/noise ratio.
Update the value of the S/N measure
1. Select Maintenance > S/N Meas.

The S/N parameter indicates the value of the signal/noise ratio.
2. Press Refresh to update the value.

S/N Meas. context
For the equipment with Radio Link in 1+0 configuration the S/N Meas command is available which opens
the S/N Meas context.
For the equipment with Radio Link in 2+0 XPIC configuration or equipment in 2x(1+0) radio configuration
the commands S/N Meas TRX A, which opens the S/N Meas TRX A context containing the parameters
relevant to S/N measure of transceiver A, and S/N Meas TRX B, which opens the S/N Meas TRX B context
containing the parameters relevant to S/N measure of transceiver B, are available.
The context shows the value of the S/N measure.
Parameters
S/N. Value of the signal/noise ratio.
The measure is always in progress.
Buttons
Refresh. Update the value of the S/N measure
See also
S/N Meas (command)

Radio BER
For the equipment with Radio Link in 1+0 configuration is present the Radio BER command. For the equip-
ment with Radio Link in 2+0 XPIC configuration or equipment in 2x(1+0) radio configuration are present
the Radio BER TRX A (transceiver A, BER measure) and Radio BER TRX B (transceiver B, BER measure)
commands.
The Radio BER command allows verifying the quality of the signal received by the equipment.
Operations
Verify the status and the configuration parameters of Radio BER measure
Activate the measure (BER and error count)
Deactivate the measure (BER and error count)
GUI
Radio BER context
Verify the status and the configuration parameters of Radio BER measure
1. Select Maintenance > Radio BER.

The Radio BER context displays the status and the configuration parameters of Radio BER measure.
User Profile | Maint., Read/Write, Admin.
WARNING The operation is traffic affecting.

Operation of maintenance (MAN. OP).
2. Select the On option (Test Mode parameter).
3. Press Apply.

The activation of measure activates the MAN. OP. alarm. If the equipment is switched off and then
switched on again, the measure is inactive independently from the previous setting.
5. Press (Re)Start Measure and confirm.

To restart the measure (reset of BER and number of errors), press (Re)Start Measure and confirming.
2. Select the Off option (Test Mode parameter).

Radio BER context
For the equipment with Radio Link in 1+0 configuration the Radio BER command is available which opens
the Radio BER context.
For the equipment with Radio Link in 2+0 XPIC configuration or equipment in 2x(1+0) radio configuration
the commands Radio BER TRX A, which opens the Radio BER TRX A context containing the parameters
relevant to BER measure of transceiver A, and Radio BER TRX B, which opens the Radio BER TRX B con-
text containing the parameters relevant to BER measure of transceiver B, are available.
The context shows the status and the configuration parameters of Radio BER measure.
Parameters
GENERAL
BER. Bit Error Rate: ratio between the number of received errored bits and the number
of total received bits. BER value is dynamically updated during the measure.
Errors. Number of errors detected from the start of the measure.
Elapsed Time. Time (expressed in seconds) range after the measure active.
Synch Loss events. Number of times that the Sync Loss Alarm activated from the start
of the measure.
Sync Loss Alarm. Status of Synch Loss alarm. The colour of the box represents the
alarm status and severity:
• Green. Alarm activated coupled with the Status severity level.
Test Mode. Activation status of the measure:

• On. The Radio BER measure is active.
• Off. The Radio BER measure is deactivated.
Buttons
(Re)Start Measure. Start or restart the measure.
See also
Radio BER (command)

MAB
The MAB command manages the Microwave Adaptive Bandwidth (MAB) function.
Operations
Verify the existing MAB instances
Create a MAB Monitor instance
Modify the configuration of a Monitor MAB instance
Delete one or more Monitor MAB instance
Create a MAB Sender instance
Modify the configuration of a Sender MAB instance
Delete one or more Sender MAB instances
GUI
MAB context
See also
MAB function (info)
Verify the existing MAB instances
1. Select Maintenance > MAB.

The MAB context shows the created MAB instances (Monitor and Sender).
WARNING A maximum of 8 Monitor MAB instances can be created.
2. Press Add (Sensor Table area).
3. In the ODU Index box, select the Ethernet port to the Radio associated with the instance (see Tab.5).
4. In the Admin Status box, select the administrative status of the instance:
• Down. Instance disabled.
• Up. Instance enabled.
5. In the Link ID box, type the value that identifies the Radio Link in the radio (number between 0 and
4294967294).
The 0 value corresponds to the non-selection of the identification.
6. In the BW Mode box, set the criterion used to calculate the band value available within every transmis-
sion period (Observ Time):
• Average. The BNM messages contain the indication of the average value of the available band
within the observation period.
• Min. The BNM messages contain the indication of the minimum value of the available band within
the observation period.
• Max. The BNM messages contain the indication of the maximum value of the available band
within the observation period.

7. In the Holdoff Time (s) box, set the waiting period (in seconds) before declaring Fading and starting
the transmission of BNM messages (value between 0 and 60).
8. In the Observ. Time (s) box, set the transmission period (in seconds) between one BNM message and
the next one (1, 10 or 60 seconds).
9. Press Apply.
The new instance is added to the list (Sensor Table area).
The message Unable to create Sensor instance 9 indicates that the maximum allowed number of MAB
Monitor instances has been already created. In this case, first it is necessary to Delete one or more
Monitor MAB instance.
2. Select the Monitor MAB instance you wish to modify (Sensor Table area).
For every single instance you can change the following parameters:
• Admin Status. Administrative status of the instance:
Double click on the wished box (Admin Status column) and set the value:
• Link ID. Value that identifies the Radio Link in the radio.
Double click on the wished box (Link ID column) and type a number between 0 and
4294967294. The 0 value corresponds to the non-selection of the identification.
• BW Mode. Criterion used to calculate the band value available within every transmission period
(Observ Time):
Double click on the wished box (BW Mode column) and set the value:
• Average. The BNM messages contain the indication of the average value of the available
band within the observation period.
• Min. The BNM messages contain the indication of the minimum value of the available
• Max. The BNM messages contain the indication of the maximum value of the available
• Holdoff Time (s). Waiting period (in seconds) before declaring Fading and starting the transmis-
sion of BNM messages.
Double click on the wished box (Holdoff Time column) and type a number between 0 and 60.
• Observ. Time (s). Transmission period (in seconds) between one BNM message and the next
one.
Double click on the wished box (Observ. Time column) and set the 1, 10 or 60 value.

The changes are confirmed in the Sensor Table area.
WARNING A MAB Monitor instance with, at least, one MAB Sender option associated cannot be deleted.
First it is necessary to delete the MAB Sender instance and then the Monitor instance.
2. Select the MAN instance you wish to delete (Sensor Table area).

The instance is removed from the list.
WARNING A maximum of 8 Sender MAB instances can be created.

More Sender MAB instances can be associated to the same Monitor MAB instance.
2. Press Add (Sender Table area).

3. In the Sensor Index box, select the identifier of the MAB Monitor instance which you wish to associate
the MAB Sender instance to.
The list contains the numeric identifiers relevant only to the created MAB Monitor instance.
4. Select, in the Port Index box, the identifier of the Ethernet port on line side or to the Radio, which you
wish to associate the MAB Sender instance to (see Tab.5).
The list does not contain the ports belonging to LAG (see LA Manager).
5. In the Admin Status box, select the administrative status of the instance:
6. In the VLAN ID box, type the Tag 802.1Q VLAN value (number between 0 and 4095).
7. In the User Priority box, type the 802.1p priority value (number between 0 and 7).
8. In the OAM Maint Level box, type the maintenance Level of the OAM domain (number between 0 and 7).
9. In the PDU Compliance box, select the standard which the transmitted BNM packets are in compliance
with:
• Standard. The BNM packets are compliant to the MW Capacity Management (MCM) functionality.
• Ext. The BNM packets are compliant to the Microwave Adaptive Bandwidth Extension function-
ality.
• G.8013. The BNM packets are compliant to the G.8013 /Y.1731 (OAM Functions and Mechanisms
for Ethernet based Networks) ITU-T Recom.
10.Press Apply.
The new instance is added to the list (Sender Table area).
The message Unable to create Sensor instance 9 indicates that the maximum allowed number of MAB
Monitor instances has been already created. In this case, first it is necessary to Delete one or more
Sender MAB instances.
2. Select the Sender MAB instance you wish to modify (Sender Table area).
For every single instance you can change the following parameters:
• Admin Status. Administrative status of the instance:
Double click on the wished box (Admin Status column) and set the value:
• VLAN ID. Tag 802.1Q VLAN value.
Double click on the wished box (VLAN ID column) and type a number between 0 and 4095.

• User Priority. 802.1p priority value.
Double click on the wished box (User Priority column) and type a number between 0 and 7.
• OAM Maint Level. Maintenance Level of the OAM domain.
Double click on the wished box (OAM Maint Level column) and type a number between 0 and 7.
• PDU Compliance. Standard which the transmitted BNM packets are transmitted to.
Double click on the wished box (PDU Compliance column) and set the value:
• Standard. The BNM packets are compliant to the MW Capacity Management (MCM) func-
tionality.
• Ext. The BNM packets are compliant to the Microwave Adaptive Bandwidth Extension
functionality.
• G.8013. The BNM packets are compliant to the G.8013 /Y.1731 (OAM Functions and
Mechanisms for Ethernet based Networks) ITU-T Recom.

The changes are confirmed in the Sender Table area.

2. Select the MAB instance you wish to delete (Sender Table area).

The instance is removed from the list.

MAB context
The context displays the configuration of the Microwave Adaptive Bandwidth (MAB) function.
Sensor Table
The table lists the Monitor MAB instances.
Each row of the table corresponds to an instance for which are indicated:
ODU Index. Identifier of the Ethernet port to the Radio associated with the Monitor MAB
instance (see Tab.5).
Sensor Index. Value identifying univocally the instance within the MAB Sensor table.
Admin Status. Administrative status of the Monitor MAB instance:
Default Down.
Link ID. Value that identifies the Radio Link in the radio.
Default 0.
BW Mode. Criterion used to calculate the band value available within every transmission
period (Observ Time):
• Average. The BNM messages contain the indication of the average value of the
available band within the observation period.
• Min. The BNM messages contain the indication of the minimum value of the
• Max. The BNM messages contain the indication of the maximum value of the
Default Average.
Holdoff Time (s). Waiting period (in seconds) before declaring Fading and starting the
transmission of BNM messages.
Default 10 seconds.
Observ. Time (s). Transmission period (in seconds) between one BNM message and the
next one.
Default 10 seconds.
Nom. BW (Mbps). Rated bandwidth in transmission of the Radio connection present in
the BNM messages.
Curr. BW (Mbps). Current bandwidth in transmission of the Radio connection present
in the BNM message.
The parameter indicates the current bandwidth value detected at the moment of the con-
figuration of the MAB instance or that detected after an update of the context.
WARNING The value of Nom. BW and Curr. BW is calculated using a correction factor
equal to ETH Cap x 0,837.
The instances are listed in numerical order with respect to the column Sensor Index.
PDU Sender Table

The table lists the Sender MAB instances.
Each row of the table corresponds to an instance for which are indicated:
Sensor Index. Identifier of the MAB Monitor instance which the MAB Sender instance is
associated to.
Port index. Identifier of the Ethernet port on line side or to the Radio which the MAB
Sender instance is associated to (see Tab.5).
The list does not contain the ports belonging to LAG’s (see LA Manager).
Admin Status. Administrative status of the Sender MAB instance:
Default Down.
VLAN ID. Tag 802.1Q VLAN value.

By default, the BNM message is sent untagged (value 0).
User Priority. 802.1p priority value.
By default, the BNM message is sent without priority (value 0).
OAM Maint Level. Maintenance Level of the OAM domain.
By default, the BNM message is associated with Maintenance Level 0.
PDU Compliance. Standard which the transmitted BNM packets are in compliance with:
• Standard. The BNM packets are compliant to the MW Capacity Management
(MCM) functionality.
• Ext. The BNM packets are compliant to the Microwave Adaptive Bandwidth Ex-
tension functionality.
• G.8013. The BNM packets are compliant to the G.8013 /Y.1731 (OAM Func-
tions and Mechanisms for Ethernet based Networks) ITU-T Recom.
Selecting the heading of the Sensor Index column, the rows of the table are sorted in increasing
alphanumeric order with respect to the considered column and an arrow is displayed with the
tip directed upwards. The next selection sorts the rows in decreasing order (an arrow is dis-
played with the tip directed downwards) and so on.
Buttons
SENSOR TABLE AREA
Add. Create a MAB Monitor instance

Remove. Delete one or more Monitor MAB instance
PDU SENDER TABLE REA
Add. Create a MAB Sender instance

Remove. Delete one or more Sender MAB instances
See also
MAB (command)
MAB function (info)

MAB function (info)
MAB function
The transmission capacity of the radio equipment depends on the propagation conditions of the
radio channels.
In case of Ethernet rings, the signal degradation can influence one side of the ring, while the
other side continues working at rated capacity.
In case of network congestion, the radio will give priority to the Ethernet traffic decreasing or
deleting the low priority traffic.
An analogous situation is present even in other types of network where the changes of the band-
width must be communicated to the upstream Ethernet Switches/Routers in order to adapt the
relevant traffic.
By knowing the radio connection capacity, external equipment can optimize the transport on
ring networks or select additional criteria for the quality management.
The Microwave Adaptive Bandwidth (MAB) function allows achieving optimized performances
even in the worse conditions of radio propagation as it allows forwarding the traffic on the Ether-
net ring according with the bandwidth available on each ring branch.
The function is based on a protocol used by the equipment to notify the changes in the capacity
to connect the Ethernet Switch/Router which, in turn, applies the relevant forward rules.
Notifications take place by means of messages of type E-OAM (Ethernet-Operations, Adminis-
tration and Maintenance) which signal the changes in the band availability (BNM messages -
Bandwidth Notification Message).
Through the management (transmission and reception) of these messages and the proper con-
figuration of the forwarding rules, the ring will be able to change its traffic profile to consider the
degraded path.
During the normal operation of the Radio connection, if there is no Fading, the BNM messages
are not generated.
When the transceiver detects, in the connection quality, a degraded condition which persist
more than the observation period and the equipment changes its modulation scheme, a BNM
message is generated to inform the network equipment about the signal degradation. The mes-
sage contains the indication of the rated and current bandwidth values in transmission.
Later periodical BNM messages will be transmitted for the duration of the Fading event.
At the end of the Fading event, a last BNM message will be sent where the current bandwidth
corresponds to the rated bandwidth. This message determines the interruption of the transmis-
sion of the BNM messages until the next Fading event.
In ALFOplus2 equipment, the BNM messages are forwarded according to the MAB (Monitor and
Sender) instance defined for every equipment (see next paragraph).
The transmitted BNM packets can be in compliance with the MCM (Capacity Management MW)
functionality, the MAB (Microwave Adaptive Bandwidth) extension functionality or the Recom-
mendation ITU-T G.8013 /Y.1731 (OAM Functions and Mechanisms for Ethernet based Net-
works) which you are addressed for further information.
Implement the MAB function

In ALFOplus2 equipment, to implement the MAB function via WEB LCT, it is necessary:
Create the MAB Monitor instance. They must be defined on the Ethernet Switch ports
towards the Radio (see Tab.5).
When the instance is created (or later), it is necessary to define the following port pa-
rameters and forward parameters for the BNM messages:
• Ethernet port to the Radio which you wish to associate the instance to.
For a correct operation of the instance, the port must be active (see Port Man-
ager context).
• Administrative status of the instance: enable/disable the management of the
BNM messages at level of single MAB Monitor instance.
• Value indicating the Radio connection in the network.
• Criterion used to calculate the bandwidth value available within every obser-
vation interval: average value, minimum value or maximum value.
• Wait time before declaring Fading and starting the transmission of the BNM
messages.
• Transmission period between two successive BNM messages.

It is possible to create at most 8 MAB Monitor instances.
Create the MAB Sender instances. They must be associated to one MAB Monitor in-
stance and defined on one Ethernet port of the Switch (line side or Radio side - see
Tab.5).
When the instance is created (or later), it is necessary to define the following port pa-
rameters and forward parameters for the BNM messages:
• MAB Monitor instance which the MAB Sender instance must be associated to.
• Ethernet port on line side or towards the Radio which the MAB Sender instance
must be associated to.
For a correct operation of the instance, the port must be active.
A port belonging to LAG’s cannot be associated to a MAB instance (see LA Man-
ager).
• Administrative status of the instance: enable7disable the management of the
BNM messages at level of single MAB Sender instance.
• Value of Tag 802.1Q VLAN present in the BNM message.
• Priority 802.1p present in the BNM messages.
• Maintenance level of the OAM domain present in BNM messages.
• Standard which the transmitted BNM packets are in compliance with (MCM,
MAB extension or G.8013).
It is possible to create at most 8 MAB Sender instances. They can be associated to one
MAB Monitor instance (all or part of them).
See also
MAB (command)
MAB context

Radio Loop & Cmd
For the equipment with Radio Link in 1+0 configuration is present the Radio Loop & Cmd command. For
the equipment with Radio Link in 2+0 XPIC configuration or equipment in 2x(1+0) radio configuration are
present the Radio Loop & Cmd TRX A (transceiver A radio parameters) and Radio Loop & Cmd TRX B
(transceiver B radio parameters) commands.
The Radio Loop & Cmd command manages the loops, the transmitter operating status and the carrier
modulation.
Operations
Verify the digital loops status
Activate a digital loop
Deactivate a digital loop
Verify/modify the operation of the transmitter
Verify/modify the modulation status of the RF carrier
GUI
Radio Loop & Cmd context
Verify the digital loops status
1. Select Maintenance > Radio Loop & Cmd.

The Radio Loop & Cmd context displays the current status of the digital loops.
WARNING The activation of a digital loop affects the traffic.

The activation of the I/Q Loop (traffic not squelched) loop could cause the loss of supervision.
For equipment with Radio Link in configuration 2+0 XPIC:
• The activation of a loop disables the XPIC Fault Management Procedure (FMP) (see Xpic con-
text).
• The activation of a loop I/Q... switches the local transmitter off.
In order to verify the transit of the Ethernet traffic through the loop I/Q..., the loop must be activated on
both branches.
The activation of a loop for one transceiver involves the automatic activation of the same loop even for the
other transceiver.
Operation of maintenance (MAN. OP).
Before activating a loop, it is suggested to verify that the timeout of the manual operations is set. If the
timeout is not active, the loop will be active until its deactivation by the user, the switch-off/switch-on of
the equipment or the equipment reset.

2. In the Radio Loop area, select the option relevant to the loop that you want to activate.
It is not possible to preset more loops at the same time as the choice of a option automatically disables
the preceding one.

3. Press Apply.

The activation of a loop activates the MAN. OP alarm. If the equipment is turned off and then turned
on again, the loop results deactivated without taking into account the preceding setting.
WARNING The deactivation of a loop for one transceiver involves the automatic deactivation of the same
loop even for the other transceiver.
2. In the Radio Loop area, select the Loop OFF option.
WARNING Switching the transmitter off (option Off) is a maintenance operation (MAN. OP).
The permanent switch-off of the transmitter (option Permanent Off) is NOT a maintenance operation, so
the selection of this value is not subjected to the Timeout of MAN. OP and the setting is not lost after a
controller restart.
For equipment with Radio Link in configuration 2+0 XPIC, switching off the power supply disabled the XPIC
Fault Management Procedure (FMP) (see Xpic context).

The Tx Transmitter parameter indicates the operation of the transmitter:
• On. The transmitter is turned on.
• Off. The transmitter is turned off.
• Permanent Off. The transmitter is turned off in permanent mode.
3. Press Apply.
Only if you are switching off the transmitter (selection of the Off option) a message warns that you are
executing a forcing and displays the current setting of timeout.

The turning off of the transmitter activates the MAN. OP alarm. If the equipment is switched off and,
then, switched on, the transmitter is on, independently from the previous setting.
WARNING Deactivating the modulation (option On) is a maintenance operation (MAN. OP).
Before deactivating the modulation, configure the transmitter power to the minimum value.
For equipment with Radio Link in configuration 2+0 XPIC, switching off the modulation:
• Disables the XPIC Fault Management Procedure (FMP) (see Xpic context).
• Could cause interference in reception.

It is not advisable to perform the operation of Carrier Only on both transceivers. If it was however done,
it will be necessary to deactivate the operation for both the transceivers in rapid succession.

The Carrier Only parameter indicates the modulation status of the RF carrier:
• On. The carrier is not modulated.
• Off. The carrier is modulated.

3. Press Apply.
Only if you are deactivating the modulation (selection of the On option) a message warns that you are
executing a forcing and displays the current setting of timeout.

The modulation deactivation of the carrier activates the MAN. OP alarm. If the equipment is switched
off and, then, switched on, the modulation is active independently from the previous setting.

Radio Loop & Cmd context
For the equipment with Radio Link in 1+0 configuration the Radio Loop & Cmd command is available
which opens the Radio Loop & Cmd context.
For the equipment with Radio Link in configuration 2+0 XPIC configuration or equipment in 2x(1+0)radio
configuration there are the commands Radio Loop & Cmd TRX A (which opens the context area Radio
Loop & Cmd TRX A containing the radio parameters of transceiver A) and Radio Loop & Cmd TRX B
(which opens the context area Radio Loop & Cmd TRX B containing the radio parameters of transceiver B).
The context shows the current status of the loops, the transmitter operating status and the carrier modu-
lation.
Parameters
RADIO LOOP
Loop. Status of the loops:
• Loop OFF. No loop active.
• I/Q Loop (Traffic squelched). Digital loop executed before the modulation and
RF amplification block: traffic is not looped.
• I/Q Loop (Traffic not squelched). Digital loop executed before the modulation
and RF amplification block: traffic is looped.
Tx Transmitter. Operating status of the transmitter:

• Permanent Off. The transmitter is turned off in permanent mode.
Carrier Only. Modulation status of the RF carrier:

Buttons
See also
Radio Loop & Cmd (command)

Manual Operations
The Manual Operations command manages the available maintenance operations (MAN. OP) with the
exception of the BER measure.
Operations
Verify the manual operations status
Turn-off/turn-on the transmitter
Disable/enable the modulation of the RF carrier
Activate/deactivate a digital loop
Disable temporarily/restore the XPIC function
GUI
Manual Operations context
Verify the manual operations status
1. Select Maintenance > Manual Operations.

The Manual Operations context displays the current status of the available maintenance operations with
the exception of the BER measure.
For this operation see Verify the status and the configuration parameters of Radio BER measure.
WARNING Operation available only for equipment with at least one Radio Link defined.
Switching the transmitter off is a MAN. OP. Before executing the operation, verify the timeout setting (see
Verify/modify the manual operation timeout).
If the equipment is switched off and, then, switched on, the Tx is on, independently from the previous set-
ting.
The permanent turn-off of the transmitter is not a maintenance operation, so the operation is not available
in this context. To execute it see Verify/modify the operation of the transmitter.
For equipment with Radio Link in 2+0 XPIC configuration, turn off the transmitter disables the XPIC fault
management procedure (FMP) (see Xpic context).

The Tx Transmitter parameter indicates the operation of the transmitter:
2. To turn-off the transmitter select the Off option, press Apply and confirm.
3. To turn-on the transmitter select the On option, press Apply and confirm.

Deactivating the modulation of the RF carrier is a MAN. OP. Before executing the operation, verify the time-
out setting (see Verify/modify the manual operation timeout).
If the equipment is switched off and, then, switched on, the modulation is active independently from the
previous setting.
For equipment with Radio Link in configuration 2+0 XPIC, switching off the modulation:
• Disables the XPIC Fault Management Procedure (FMP) (see Xpic context).
• Could cause interference in reception.
It is not advisable to perform the operation of Carrier Only on both transceivers. If it was however done,
it will be necessary to deactivate the operation for both the transceivers in rapid succession.

The Carrier Only parameter indicates the modulation status of the RF carrier:
2. To disable the modulation of the RF carrier select the On value, press Apply and confirm.
3. To enable the modulation of the RF carrier select the Off value, press Apply and confirm.
The activation of a digital loop affects the traffic.
The activation of the I/Q Loop (traffic not squelched) loop could cause the loss of supervision.
For equipment with Radio Link in configuration 2+0 XPIC:
• The activation of a loop disables the XPIC Fault Management Procedure (FMP) (see Xpic con-
text).
• The activation of a loop I/Q... switches the local transmitter off.
In order to verify the transit of the Ethernet traffic through the loop I/Q..., the loop must be activated on
both branches.
The activation/deactivation of a loop for one transceiver involves the automatic activation/deactivation of
the same loop even for the other transceiver.
The activation of a loop is a MAN. OP. Before executing the operation, verify the timeout setting (see Verify/
modify the manual operation timeout).
If the equipment is switched off and, then, switched on, the loop is deactive independently from the pre-
vious setting.

The Radio Loop parameter indicates the status of the loops:
• I/Q Loop (Traffic squelched). Digital loop executed before the modulation and RF amplification
block: traffic is not looped.
• I/Q Loop (Traffic not squelched). Digital loop executed before the modulation and RF amplifica-
tion block: traffic is looped.
2. To activate a loop select the value relevant to the wished loop, press Apply and confirm
It is not possible to preset more loops at the same time as the choice of a option automatically disables
the preceding one.
3. To deactivate the loop select the Loop OFF value, press Apply and confirm.

WARNING Operation available only for equipment with Radio Link in 2+0 XPIC configuration.
Disabling temporarily the XPIC function is a MAN. OP. The activation of a loop is a MAN. OP. Before exe-
cuting the operation, verify the timeout setting (see Verify/modify the manual operation timeout).
If the equipment is switched off and, then, switched on, the XPIC function is active independently from the
previous setting.

The Xpic parameter indicates the status of the XPIC function:
• Disable. Function temporarily deactivated.
2. To disable temporarily the XPIC function, select Disable, press Apply and confirm.
3. To restore the XPIC function, select Enable, press Apply and confirm.
WARNING The activation of the forcing is a MAN. OP. Before executing the operation, verify the timeout
setting (see Verify/modify the manual operation timeout).
If the equipment is switched off and, then, switched on, the forcing results inactive, independently from
the previous setting.

The Status Control parameter indicates the status of T0 synchronism:
2. To force the status of the T0 synchronisation select the Free Running or Hold Over value, press Apply
and confirm.
3. To remove the forcing select the Locked option, press Apply and confirm.
WARNING The activation of the forcing is a MAN. OP. Before executing the operation, verify the timeout
setting (see Verify/modify the manual operation timeout).
If the equipment is switched off and, then, switched on, the forcing results inactive, independently from
the previous setting.

The Forced Switch parameter indicates the forced use of a synchronism source for the generation of
the T0 synchronism:
• Off. No source has been forced.
• <source name>. The use of the specific source is forced.
The list of the available sources is in Tab.9.
2. To force a source select the specific option, press Apply and confirm.
3. To remove the forcing select the Off option, press Apply and confirm.

Manual Operations context
The context shows the current status of the available maintenance operations (MAN. OP) with the excep-
tion of the BER measure.
Press to compress a group. Press to expand a group.
Parameters
TRX A AND TRX B
Areas available only for equipment with at least one Radio Link defined.
The following parameters are present in every area:
Tx Transmitter. Operating status of the transmitter:
Carrier Only. Modulation status of the RF carrier:
Radio Loop. Status of the digital loops:
• I/Q Loop (Traffic squelched). Digital loop executed before the modulation and
RF amplification block: traffic is not looped.
• I/Q Loop (Traffic not squelched). Digital loop executed before the modulation
and RF amplification block: traffic is looped.
Xpic. Activation of XPIC function:
• Disable. Function temporarily deactivated.
Parameter available only for equipment with Radio Link in 2+0 XPIC configuration.
SYNCHRONISATION
Status Control. Status of T0 synchronism:
• Free Running. The status of Free Running is forced (synchronism T0 is gener-
ated by the equipment internal reference - Internal Source).
Forced Switch. Forced use of a synchronism source for the generation of the T0 syn-
chronism:
• Off. No source has been forced.
• <source name>. The use of the specific source is forced.
The list of the available sources is in Tab.9.
Buttons
See also
Manual Operations (command)

RMON
Settings. It manages the count of the RMon statistics (group Statistics and History).
Ethernet Statistics. It displays the current values of RMon statistic counters (RMon instances per Port).
Ethernet Service Statistics. It displays the current values of RMon statistic counters (RMon instances
Port & Priority and Port & VLAN).
Ethernet History. It displays the history of the RMon statistics (RMon instances per Port).
Ethernet Service History. It displays the history of the RMon statistics (RMon instances Port & Priority
and Port & VLAN).

Settings
The Settings command manages the count of the RMon statistics (group Statistics and History).
Operations
Verify the count status of the RMon statistics
Activate the count of the RMon statistics
Deactivate the count of the RMon statistics
Reset the counters’ results of the RMon statistics
STATISTICS GROUP
Set a RMon instance per Port to the count of the RMon statistics
Delete a RMon instance per Port for the count of the RMon statistics
Set a RMon instance Port & Priority or Port & VLAN to the count of the RMon statistics
Delete a RMon instance Port & Priority or Port & VLAN for the count of the RMon statistics
HISTORY GROUP
Set a RMon instance per Port to the count of the RMON history
Delete a RMon instance per Port for the count of the RMON history
Set a RMon instance Port & Priority or Port & VLAN to the count of the RMON history
Delete a RMon instance Port & Priority or Port & VLAN for the count of the RMON history
GUI
Settings context
See also
RMon standard (info)
Verify the count status of the RMon statistics
1. Select Maintenance > RMON > Settings.

The parameter RMON Status shows the status of the count of the RMon statistics and the RMon history
for the all enabled instances:
• Enabled. The count is active.
• Disabled. The count is not active.
WARNING Operation meaningful only if at least one RMon instance has been set.
2. Set, in RMON Status box, the value Enabled and confirm.

The count of the RMon statistics is activated for the instances present in the Ethernet Statistics tab,
Ethernet History tab, Ethernet Service Statistics tab and Ethernet Service History tab.

WARNING The operation resets the current values of RMON statistic counters (see Ethernet Statistics and
Ethernet Service Statistics) and the RMon history (see Ethernet History and Ethernet Service History).
2. Set, in RMON Status box, the value Disabled and confirm.

The count of the RMon statistics is interrupted for the instances present in the Ethernet Statistics tab,
Ethernet History tab, Ethernet Service Statistics tab and Ethernet Service History tab.
Reset the counters’ results of the RMon statistics
2. Press Reset Counters and confirm.

All the counters of the instances present in the Ethernet Statistics tab and Ethernet Service Statistics
tab are set to zero.
Set a RMon instance per Port to the count of the RMon statistics
WARNING The recommended maximum number of RMon instances per Port is 10.
2. In the Ethernet Statistics tab, press Add.

3. Set, in Index box, a value which identifies in unique mode the instance in the database table of RMon
statistics (number between 1 and 65535).
It is not possible to set a value already present in list or in the tab Ethernet Service Statistics tab.
4. Set, in the Data source box, the Ethernet port or the LAG you wish to enable for the count of the RMon
statistics for the specific instance.
The Ethernet port identifier is a combination of slot number and the port number (slot number/port
number) followed by the port name (see Tab.5).
The label po<identification number> indicates a LAG (see LA Manager). If a LAG is selected, the specific
instance RMon per Port will allow monitoring all the traffic in input/output in/from the ports belonging
to the LAG.
The list will display only the ports/LAGs not associated yet to any RMon per Port instance.
5. Set, in Owner box, the information relevant to the user who is enabling the instance (alphanumeric
string of 30 characters at most).
Optional parameter. If the parameter is not set, as soon as the context is updated, the system will dis-
play the wording monitor.
6. Press Apply.
The instance is added to the list.
The instance will be enabled until when deleted by the user (see Delete a RMon instance per Port for
the count of the RMon statistics).

Delete a RMon instance per Port for the count of the RMon statistics
WARNING This operation involves the loss of the values of the counters for the specific instance.
2. In the Ethernet Statistics tab, select the instance you wish to delete.
An instance per Port cannot be deleted if an instance associated to the same Ethernet port is present
in the Ethernet History tab. To delete it, it is first necessary to remove the instance per Port present in
the tab Ethernet History.

The instance is deleted from the list.
Set a RMon instance Port & Priority or Port & VLAN to the count of the RMon statistics
WARNING The recommended maximum number of RMon instance for service (instances Port & Priority +
instances Port & VLAN) is 64. Within this limit, a maximum number of 40 instances Port & VLAN is foresee.
2. Select the Ethernet Service Statistics tab.
3. Press Add.
4. Set, in Index box, a value which identifies in unique mode the port in the database table of RMon sta-
tistics (number between 1 and 65535).
It is not possible to set a value already present in the list or in the Ethernet Statistics tab.
5. Set, in the box Data source, the Ethernet port or LAG you wish to enable to the count of RMon statistics
for the specific instance.
instance RMon Port & Priority or Port & VLAN will allow monitoring all the traffic in input/output in/from
the ports belonging to the LAG.
6. Set, in Owner box, the information relevant to the user who is enabling the port (alphanumeric string
of 30 characters at most).
7. Set, in the box Select Service, the criterion you wish to enable to filter the traffic:
• Priority. Priority value (C-PCP in Customer Bridge, S-PCP in Provider Bridge and Provider Edge
Bridge) which the packet in input/output must have to be counted by the RMon statistics (RMon
instance Port & Priority).
• SVID. S-VID (Service VLAN Identifier) which the packet in input/output must have to be counted
by the RMon statistics (RMon instance Port & VLAN).
Value available and meaningful when the Switch is in Provider Bridge or Provider Edge Bridge
modality.
• CVID. C-VID (Customer VLAN Identifier) which the packet in input/output must have to be
counted by the RMon statistics (RMon instance Port & VLAN).
Value available and meaningful when the Switch is in Customer Bridge modality.
8. Set, in the box Priority, the priority value which the packet in input/output from the port must have to
be counted by the RMon statistics.
Value available and meaningful only if the value Priority is present in the box Select Service.
9. Set, in the box SVID, the S-VID which the packet in input/output from the port must have to be counted
by the RMon statistics.

The set value must correspond to a VLAN ID present in the VLAN Table (see Static VLANs tab).
Parameter available and meaningful only if the value SVID is present in the box Select Service.
10.Set, in the box CVID, the C-VID which the packet in input/output from the port must have to be counted
by the RMon statistics.
Parameter available and meaningful only if the value CVID is present in the box Select Service.
11.Press Apply.
The instance will be enabled until when deleted by the user (see Delete a RMon instance Port & Priority
or Port & VLAN for the count of the RMon statistics).
Delete a RMon instance Port & Priority or Port & VLAN for the count of the RMon statistics
2. Select the Ethernet Service Statistics tab.

3. Select the instance you wish to delete.
An instance Port & Priority or Port & VLAN cannot be deleted if an instance associated to the same cri-
teria (Ethernet port and Priority or C-VID/S-VID) is present in the Ethernet Service History tab. In order
to delete it, it is first necessary to delete the corresponding instance Port & Priority or Port & VLAN pre-
sent in the tab Ethernet Service History.

Set a RMon instance per Port to the count of the RMON history
WARNING The total recommended maximum number of RMon instances for the count of the RMon history
is 74. The limit is for instances of 1 minute and 240 buckets.
2. Select the Ethernet History tab.
3. Press Add.
history (number between 1 and 65535).
It is not possible to set a value already present in the list or in the Ethernet Service History tab.
5. Set, in the box Data source, the Ethernet port or LAG you wish to enable for the count of the RMon
history for the specific instance.
instance RMon per Port will allow monitoring all the traffic in input/output in/from the ports belonging
to the LAG.
6. Set, in Owner box, the information relevant to the user who is enabling the RMon instance (alphanu-
meric string of 30 characters at most).
7. Set, in Buckets Requested, the total number of samples to collect (value between 1 and 240).

The equipment stores these data in a circular buffer, where the new information in input overwrites the
old one.
8. Set, in Persistence box, the status of automatic storing of RMon statistics on non-volatile memory:
• Disable. Automatic storing inactive.
• Enable. Automatic storing active.
9. Set, in the Interval (s) box, the sampling interval used to collect the data of the history.
If, in the previous step, the parameter Persistence has been set to:
• Disable, any value can be set, between 1 and 3600 seconds, as sampling interval.
• Enable, one of the following values can be set: 60, 300, 600, 900, 1200, 1800 or 3600 seconds.
The minimum recommended value is 60 seconds.
10.Press Apply.
The message Ethernet Statistics for <port name> are not present, they will be created automatically?
indicates that, for the Ethernet port selected at step 5, there is not an analogous instance in the Ether-
net Statistics tab. Press OK to continue the operation.
The instance will be enabled until when deleted by the user (see Delete a RMon instance per Port for
the count of the RMON history).
In the Ethernet Statistics tab, an instance per Port is automatically created with the following charac-
teristics:
• Index. First value Index free in the table of the current RMon statistics of the database.
• Data Source and Owner. Respectively Ethernet port and user of the instance per Port just cre-
ated for the count of the RMon statistics.
Delete a RMon instance per Port for the count of the RMON history
2. Select the Ethernet History tab.


Set a RMon instance Port & Priority or Port & VLAN to the count of the RMON history
WARNING The total recommended maximum number of RMon instances for the count of the RMon history
is 74. The limit is for instances of 1 minute and 240 buckets.
2. Select the Ethernet Service History tab.
3. Press Add.
history (number between 1 and 65535).
It is not possible to set a value already present in the list or in Ethernet History tab.
5. Set, in the box Data source, the Ethernet port or LAG you wish to enable for the count of the RMon
history for the specific instance.

instance RMon Port & Priority or Port & VLAN will allow monitoring all the traffic in input/output in/from
the ports belonging to the LAG.
6. Set, in Owner box, the information relevant to the user who is enabling the instance (alphanumeric
string of 30 characters at most).
7. Set, in Buckets Requested, the total number of samples to collect (value between 1 and 240).
The equipment stores these data in a circular buffer, where the new information in input overwrites the
old one.
The recommended maximum value of bucket for all the instances is 2400.
8. Set, in Persistence box, the status of automatic storing of RMon statistics on non-volatile memory:
9. Set, in the Interval (s) box, the sampling interval used to collect the data of the history.
If, in the previous step, the parameter Persistence has been set to:
• Disable, any value can be set, between 1 and 3600 seconds, as sampling interval.
• Enable, one of the following values can be set: 60, 300, 600, 900, 1200, 1800 or 3600 seconds.
The minimum recommended value is 60 seconds.
10.Set, in the box Select Service, the criterion you wish to use to filter the traffic:
• Priority. Priority value (C-PCP in Customer Bridge, S-PCP in Provider Bridge and Provider Edge
Bridge) which the packet in input/output from the port must have to be counted in the RMON
history (RMon instance Port & Priority).
• SVID. S-VID (Service VLAN Identifier) which the packet in input/output from the port must have
to be counted in the RMon history (RMon instance Port & VLAN).
Value available and meaningful when the Switch is in Provider Bridge or Provider Edge Bridge
modality.
• CVID. C-VID (Customer VLAN Identifier) which the packet in input/output from the port must
have to be counted in the RMon history (RMon instance Port & VLAN).
Value available and meaningful when the Switch is in Customer Bridge modality.
11.Set, in the box Priority, the priority value which the packet in input/output from the port must have to
be counted in the RMon history.
Value available and meaningful only if the value Priority is present in the box Select Service.
12.Set, in the box SVID, the S-VID which the packet in input/output from the port must have to be counted
in the RMon history.
Parameter available and meaningful only if the value SVID is present in the box Select Service.
13.Set, in the box CVID, the C-VID which the packet in input/output from the port must have to be counted
in the RMon history.
Parameter available and meaningful only if the value CVID is present in the box Select Service.
14.Press Apply.
The message Ethernet Service Statistics for <port name> with <priority or identifier> is not present,
will be created? indicates that, for the selected Ethernet port and priority or C-VID/S-VID there is not
an analogous instance in the Ethernet Service Statistics tab. Press OK to continue the operation.
The instance will be enabled until when deleted by the user (see Delete a RMon instance Port & Priority
or Port & VLAN for the count of the RMON history).
In the tab Ethernet Service Statistics, an instance is automatically created with the following charac-
teristics:
• Index. First value Index free in the table of the RMon history of the database.
• Data Source, Owner, Priority or C-VID/S-VID. Respectively Ethernet port, user, priority or VLAN
identifier of the instance just created for the count of the RMon history.

Delete a RMon instance Port & Priority or Port & VLAN for the count of the RMON history
2. Select the Ethernet Service History tab.


Settings context
This context shows the status and RMon instances enabled for the count of the RMon statistics (group Sta-
tistics and History).
Tab
Ethernet Statistics tab. RMon instances per Port (Statistics group).
Ethernet History tab. RMon instances per Port (History group).
Ethernet Service Statistics tab. RMon instances Port & Priority and Port & VLAN (Statistics
group).
Ethernet Service History tab. RMon instances Port & Priority and Port & VLAN (History group).
Parameters
RMON Status. Status of the count of the statistics and of the history of the statistics for all the
RMon instance set by the user:
• Enabled. The count is active.
• Disabled. The count is not active.
Buttons
Reset Counters. Reset the counters’ results of the RMon statistics
See also
Settings (command)
Ethernet Statistics tab
The tab shows the RMon instances per Port enabled for the count of the RMon statistics (group Statistics).
Table
Every row of the table corresponds to one instance for which are indicated:
Index. Value which identifies in unique mode the instance in the database table of the
RMon statistics.
Data source. Identifier of the Ethernet port or LAG enabled to the count of the RMon
The identifier is a combination of slot number and the port number (slot number/port
Owner. Information relevant to the user who has enabled the instance.
Sort Ascending. Sort in ascending order (from lowest to greatest value) the rows of the
table with respect to the value present in the specific column.
Command available only for Index column.
Sort Descending. Sort in descending order (from greatest to lowest value) the rows of
the table with respect to the value present in the specific column.

Buttons
Add. Set a RMon instance per Port to the count of the RMon statistics
Remove. Delete a RMon instance per Port for the count of the RMon statistics
Ethernet History tab
The tab shows the RMon instances per Port enabled for the count of the history of the RMon statistics
(group History).
Table
Index. Value which identifies in unique mode the RMon instance in the database table
of history of RMon statistics.
Data source. Identifier of the Ethernet port or LAG which the RMon instance enabled to
the count of the RMon statistics history is associated to.
Owner. Information relevant to the user who has created the instance.
Buckets Requested. Total number of samples to collect. The equipment stores these
data in a circular buffer, where the new information in input overwrites the old one.
Persistence. Status of automatic storing of RMon statistics on non-volatile memory:
Interval (s). Sampling interval (in seconds) used to collect the data of the statistics his-
tory.
Sort Ascending. Sort in ascending order (from lowest to greatest value) the rows of the
table with respect to the value present in the specific column.
Sort Descending. Sort in descending order (from greatest to lowest value) the rows of
the table with respect to the value present in the specific column.
Buttons
Add. Set a RMon instance per Port to the count of the RMON history
Remove. Delete a RMon instance per Port for the count of the RMON history
Ethernet Service Statistics tab
The tab shows the RMon instances Port & Priority and Port & VLAN enabled for the count of the RMon sta-
tistics (group Statistics).

Table
Index. Value which identifies in unique mode the instance in the database table of the
RMon statistics.
Data source. Identifier of the Ethernet port or LAG enabled to the count of the RMon
Owner. Information relevant to the user who has enabled the port.
Priority. Priority value (C-PCP in Customer Bridge, S-PCP in Provider Bridge and Provider
Edge Bridge) of the packet in input/output from the port.
Value meaningful for RMon instances Port & Priority.
SVID. S-VID (Service VLAN Identifier) of the packet in input/output from the port.
Value available and meaningful for RMon instances Port & VLAN when the Switch is in
Provider Bridge or Provider Edge Bridge modality.
CVID. C-VID (Customer VLAN Identifier) of the packet in input/output from the port.
Customer Bridge modality.
Buttons
Add. Set a RMon instance Port & Priority or Port & VLAN to the count of the RMon statistics
Remove. Delete a RMon instance Port & Priority or Port & VLAN for the count of the RMon sta-
tistics
Ethernet Service History tab
The tab shows the RMon instances Port & Priority and Port & VLAN enabled for the count of the history of
the RMon statistics (group History).
Table
Index. Value which identifies in unique mode the instance in the database table of his-
tory of RMon statistics.
Data source. Identifier of the Ethernet port or LAG enabled to the count of the history
of RMon statistics for the specific instance.
Owner. Information relevant to the user who has created the instance.
Buckets Requested. Total number of samples to collect. The equipment stores these
data in a circular buffer, where the new information in input overwrites the old one.
Persistence. Status of automatic storing of RMon statistics on non-volatile memory:
Interval (s). Sampling interval (in seconds) used to collect the data of the statistics his-
tory.
Edge Bridge) of the packet in input/output from the port.
SVID. S-VID (Service VLAN Identifier) of the packet in input/output from the port.

CVID. C-VID (Customer VLAN Identifier) of the packet in input/output from the port.
Buttons
Add. Set a RMon instance Port & Priority or Port & VLAN to the count of the RMON history
Remove. Delete a RMon instance Port & Priority or Port & VLAN for the count of the RMON his-
tory

RMon Standard
RMon (Remote Monitoring) is a standard whose function is providing a set of services of statistics
count, monitoring and alarm report with reference to the activity of a LAN network.
These services are defined in terms of MIB (Management Information Base) group described in
the document RFC2819 - Remote Network Monitoring Management Information Base, which
must be read for any further detail.
Outline on the operation

RMon standard is based on two components: an agent (RMon probe) and a client (remote man-
agement station).
The agent saves the data within its own RMon tables present on the network devices (equip-
ment, routers, etc.). The RMon probes can see only the traffic flowing through themselves.
The remote management station communicates with the RMon agent to obtain and correlate the
RMon data. Generally, the station is equipped with an interface (graphic or textual) which allows
the display and the analysis of the collected RMon data.
Management from WEB LCT

The RMon functionality available in WEB LCT allows monitoring the status of the Ethernet Switch
ports in compliance with the RMON standard.
With reference to what depicted in the previous paragraph, the RMon functionality acts as client
which, through the commands present in the GUI, allows the analysis and the management of
the data collected by the probes.
The probes are present at level of:
Port (line/radio) of the Ethernet Switch (RMon instance per Port). This instance allows
monitoring all the traffic in input/output to/from one port of the Ethernet Switch.
If one or more LAGs are defined (see LA Manager), an instance RMon per Port can be
defined at level of LAG. In this case, the instance allows monitoring all the traffic in input
to/output from the ports belonging to the LAG.
VLAN (RMon instance Port & VLAN). This instance allows monitoring only the traffic in
input/output to/from one Ethernet port with a given VLAN identifier (C-VID or S-VID ac-
cording to the Bridge operating modality).
If one or more LAGs are defined, an instance RMon Port & VLAN can be defined at level
of LAG. In this case, the instance allows monitoring all the traffic in input to/output from
the ports belonging to the LAG and having a specific VLAN identifier.
WARNING If the VLAN associated to the instance is removed and then restored, it is nec-
essary to delete and then re-create the specific instance in order to ensure a correct data
acquisition.
Priority (RMon instance Port & Priority). This instance allows monitoring only the traffic
in input/output to/from one Ethernet port with a given priority value (C-PCP in Customer
Bridge, S-PCP in Provider Bridge and Provider Edge Bridge).
If one or more LAGs are defined, an instance RMon Port & Priority can be defined at level
of LAG. In this case, the instance allows monitoring all the traffic in input to/output from
the ports belonging to the LAG and having a specific priority value.
The probes collect the statistic data, which are stored in the RMon table of the equipment.
Currently, the equipment implements the RMON MIB groups Statistics and History.
RMON MIB group: Statistics

RMon functionality can display to the user, through the GUI, the current statistics measured by
the RMon probes (see Display the values of the RMon statistic counters (RMon instances per
Port) and Display the values of the RMon statistic counters (RMon instances Port & Priority and
Port & VLAN).
To display the counters of an instance, it is necessary to enable the involved instance (see Set
a RMon instance per Port to the count of the RMon statistics and Set a RMon instance Port &
Priority or Port & VLAN to the count of the RMon statistics) and then activate the counting (see
Activate the count of the RMon statistics).

The count will be active for this instance until the user deactivates it (see Deactivate the count
of the RMon statistics) or deletes the instance (see Delete a RMon instance per Port for the count
of the RMon statistics and Delete a RMon instance Port & Priority or Port & VLAN for the count
of the RMon statistics.
In any moment the operator can Reset the counters’ results of the RMon statistics (Statistics
group).
RMON MIB group: History

RMon functionality can display to the user, through the GUI, the evolution in time (history) of
the statistics relevant to the counters in input/output of every monitored probes (see Display
the history of the RMon statistic (RMon instances per Port) and Display the history of the RMon
statistic (RMon instance Port & Priority and Port & VLAN).
At equipment level, the value of the counters of the RMon probes is stored in the statistics his-
tory every x seconds (sampling interval) for a total number of samples to take programmable
from 1 to 240. The equipment stores these data into a circular buffer where, when full, the new
information replaces the old one.
In order to memorize in the database and display the statistics history of one instance, it is nec-
essary to activate the instance (see Set a RMon instance per Port to the count of the RMON his-
tory and Set a RMon instance Port & Priority or Port & VLAN to the count of the RMON history)
and then activate the count (see Activate the count of the RMon statistics).
The count will be active for this instance until the user deactivates it (see Deactivate the count
of the RMon statistics) or deletes the instance (see Delete a RMon instance per Port for the count
of the RMON history and Delete a RMon instance Port & Priority or Port & VLAN for the count of
the RMON history).
When an instance is activated, the supervision system starts memorizing the data relevant to
the statistics and makes them available to the user, in table format, subdivided for single RMon
instance.
When an instance is created, it is possible to set if the data must be automatically stored or not
(parameter Persistence). The storing modes are described here below.
Automatic deletion of RMon statistics

The RMon statistics relevant to LAG are automatically deleted when the relevant LAG is removed
(see Delete a static LAG).
Automatic archive of RMon statistics

Statistic data collected by RMon probes can be stored on non-volatile support.
The following data types can be stored:
• Instances RMon per Port.
The counters RMon per port automatically stored in the persistence tables are: Drop
Events, Octets, Pkts, Broadcast Pkts, Multicast Pkts, Undersize Pkts, OversizePkts, Frag-
ments, CRC Align Errors, Utilization, Jabbers, Collisions.
The data of the counters are identified by the interface which they are collected from.
The counters refer to the reception direction of the data flow.
For the instances RMon per Port relevant to the LAGs, the stored counters will be the sum
of the counters of the ports belonging to the LAG.
The persistence tables contain the counters Jabbers and Collisions not present in the
Ethernet History tab.
• Instances RMon Port & VLAN and instances RMon Port & Priority.
The counters RMon per service automatically stored in the persistence tables are: Re-
ceived Pkts, Received Octets, Sent Pkts, Sent Octets.
The data of the counters are identified by the interface which they are collected from, by
VLAN ID or by the packet priority. The counters Octects and Pkts in the persistence da-
tabase are not separated between Unicast and Not Unicast as in Ethernet Service History
tab, but are summed. Moreover, the persistence tables contain the counter Drop Events,
which counts the sum of the counters Received Discard Pkts and Sent Discard Pkts.
For the instances RMon Port & VLAN and the instances RMon Port & Priority relevant to
the LAGs, the stored counters will be the sum of the counters of the instances RMon Port
& VLAN and Port & Priority of the ports belonging to the LAG.

The data archive on non volatile support must be activated during the creation of the instance
(option Persistence: Enable - see Set a RMon instance per Port to the count of the RMON history
and Set a RMon instance Port & Priority or Port & VLAN to the count of the RMON history).
Then, when the count is activated (see Activate the count of the RMon statistics), the data start
being stored in the persistence tables in the volatile memory of the controller.
The first interval is calculated in such a way that, at the end of the next hour, a measurement
interval is closed. Data are available to an external system (e.g. NMS) for the collection and the
archive as soon as the measurement interval is closed.
Every 15 minutes the data are copied to the non volatile memory of the controller.
Every persistence table stores a finite number of data. If, when the instance is created, a sam-
pling interval has been created (value Interval):
• Greater than or equal to 300 seconds, the relevant table will store the data relevant to
two days at most, independently from the set number of Buckets.
• Lower than 300 seconds, the table will store data corresponding, at most, to twice the
set number of Buckets.
In both the cases, when the limit is reached, the new data will overwrite the oldest ones.
The records in the persistence tables are created and deleted according to the operations exe-
cuted for the instances in the Ethernet History tab and in the Ethernet Service History tab.
Once the count is activated, the data will continue to be collected until the user deactivates the
count (see Deactivate the count of the RMon statistics) or deletes the instance (see Delete a
RMon instance per Port for the count of the RMON history and Delete a RMon instance Port &
Priority or Port & VLAN for the count of the RMON history). In this second case, the stored data
will be automatically deleted from the relevant persistence table.
In the persistence tables, the data relevant to an instance are deleted even when the count of
the statistics is re-activated after an interruption.
Limits
Tab.10 RMon instances recommended limits
STATISTICS (current counters)
Instances per Port & VLAN per Port & Priority per Port
Limit 74
Instances per Port & VLAN per Port & Priority
Limit 64
Instances per Port & VLAN
Limit 40
HISTORY (stored counters)
Instances per Port & VLAN per Port & Priority per Port
74
Limits min 1 minutes
max 240 bucket each
WARNING If the number of created instances is the recommended one or lower, but the pro-
cessing requires a time greater than that defined in one’s browser for the script processing, the
WEB LCT page displays a warning window.
The window contains the buttons to continue the script processing or to stop it (see the docu-
mentation relevant to one’s browser).
In this case, the use of CLI interface (application SM-OS) to display the counters or the enabling
of the Persistence function (automatic archive of RMon statistics non volatile memory) and the
export via FTP of the results on CSV file are suggested.
See also
Settings (command)
Ethernet Statistics (command)

Ethernet Service Statistics (command)
Ethernet History (command)
Ethernet Service History (command)

Ethernet Statistics
The command Ethernet Statistics displays the current values of the RMon statistic.
The traffic is analyzed subdivided per Ethernet port (RMon instances per Port).
Operations
Display the values of the RMon statistic counters (RMon instances per Port)
GUI
Ethernet Statistics context
See also
Display the values of the RMon statistic counters (RMon instances per Port)
WARNING Operation meaningful only if at least one Ethernet port is enabled for the count and if the count
of the RMon statistics is active (see Set a RMon instance per Port to the count of the RMon statistics and
Activate the count of the RMon statistics).
1. Select Maintenance > RMON > Ethernet Statistics.

The Ethernet Statistics context displays the value of the RMon counters for every RMon instance per
Port.

Ethernet Statistics context
The context displays the current values of the RMon statistic counters (RMon instances per Port).
Table
Counters. The first rows indicate the characteristics of the RMon instance:
• Index. Value which identifies in unique mode the instance in the database table of the
RMon statistics.
• Owner. User who has enabled the instance.
The remnant rows indicate the RMon counters (see Tab.11).
<Interface>. Identifier of the Ethernet port or LAG enabled to the count of RMon statistics for
the specific RMon instance per Port.
The Ethernet port identifier is a combination of slot number and the port number (slot number/
port number) followed by the port name (see Tab.5).
Every port/LAG (RMon instance) corresponds to a column where the results of the relevant RMon
counters are displayed.
Buttons
Help. Open the help on line.
Refresh. Update the table of counters.
See also
Ethernet Statistics (command)

Tab.11 RMon counters (Ethernet Statistics - RMon instance per Port)

Counter 64 octects (MTU value) octets (MTU value) octets FCS
Description (Undersize packet) (Oversize packet) (Good packet) *
Drop Events - - - - - - - - - OK
Number of dropped packets **
- - - - - - - - - KO
Octets x x x x x x x x x OK
Number of received octets
Pkts x x x x x x x x x OK
Number of received packets
BroadcastPkts - - - - - - - x - OK
Number of packets received directed to the broadcast ad-
dresses - - - - - - - - - KO
MulticastPkts - - - - - - - - x OK
Number of packets received directed to a multicast addresses
- - - - - - - - - KO
UndersizePkts x x x - - - - - - OK
Number of Undersize packets received
- - - - - - - - - KO
OversizePkts - - - x x x - - - OK
Number of Oversize packets received
- - - x x x - - - KO
Fragments - - - - - - - - - OK
x x x - - - - - - KO
CRC Align Errors - - - - - - - - - OK

Number of Good and Oversize packets received
- - - x x x x x x KO
Pkts 64 Octets - - - - - - x x x OK
Number of packets transmitted/received with 64 octets in
length - - - - - - x x x KO
Pkts 65 to 127 - - - - - - x x x OK
Number of packets transmitted/received with length between
65 and 127 octets - - - - - - x x x KO
Pkts 128 to 255 Octets - - - - - - x x x OK

128 and 255 octet) - - - - - - x x x KO

256 and 511 octets - - - - - - x x x KO

512 and 1023 octets - - - - - - x x x KO
Pkts > 1024 Octets - - - x x x x x x OK

Number of packets transmitted/received with length equal to
or greater than 1024 octets - - - x x x x x x KO
x Counter incremented. - Counter not incremented.

** Packets are discarded after the exhaustion of the local memory resources. This value is not necessarily
the absolute number of discarded packets, as it represents only the number of times that this condition
occurred after the exhaustion of the memory resources; the packets can be discarded also for other rea-
sons. This value does not include Output Dropped Frames.

Ethernet Service Statistics
The command Ethernet Service Statistics displays the current values of RMon statistic counters.
The analysed traffic is filtered according to the input/output port and the packet characteristics: value of
User Priority (RMon instances Port & Priority) or C-TAG identifier or S-TAG identifier (RMon instances Port
& VLAN).
Operations
Display the values of the RMon statistic counters (RMon instances Port & Priority and Port &
VLAN)
GUI
Ethernet Service Statistics context
See also
Display the values of the RMon statistic counters (RMon instances Port & Priority and Port &
VLAN)
WARNING Operation meaningful only if at least one RMon instance is enabled for the count and if the count
of the RMon statistics is active (see Set a RMon instance Port & Priority or Port & VLAN to the count of the
RMon statistics and Activate the count of the RMon statistics).
1. Select Maintenance > RMON > Ethernet Service Statistics.

The Ethernet Service Statistics context displays the value of RMon counters for every RMon instances
Port & Priority and Port & VLAN.

Ethernet Service Statistics context
The context displays the values of the RMon statistic counters (RMon instances Port & Priority and Port &
VLAN).
Table
Counters. The first rows indicate the characteristics of the RMon instance:
• Index. Value which identifies in unique mode the instance in the database table of the
RMon statistics.
• Owner. User who has enabled the RMon instance.
• Priority. Priority value (C-PCP in Customer Bridge, S-PCP in Provider Bridge and Pro-
vider Edge Bridge) which the packet in input/output from the port must have to be
counted in the RMon statistics.
• SVID. S-VID (Service VLAN Identifier) which the packet in input/output from the port
must have to be counted by the RMon statistics.
Value available and meaningful for RMon instances Port & VLAN when the Switch is
in Provider Bridge or Provider Edge Bridge modality.
• CVID. C-VID (Customer VLAN Identifier) which the packet in input/output from the
port must have to be counted by the RMon statistics.
Value available and meaningful for RMon instances Port & VLAN when the Switch is
in Customer Bridge modality.
<Interface>. Identifier of the Ethernet port or LAG enabled to the count of the RMon statistics
for the specific RMon instances.
The Ethernet port identifier is a combination of slot number and the port number (slot number/
port number) followed by the port name (see Tab.5).
Every RMon instance corresponds to one column where are indicated the characteristics of the
instance and the results of the relevant RMon counters.
Buttons
Refresh. Update the table of counters.
See also
Ethernet Service Statistics (command)

Tab.12 RMon counters (Ethernet Service Statistics and Ethernet Service History - RMon instanc-
es Port & Priority and Port & VLAN)
WARNING The counters per service (RMon instances Port & Priority and Port & VLAN) include even frames
received with wrong FCS or frames too long. The condition can be checked using the counters per port
(RMon instances per Port).
Packets (Tagged or Packet (Tagged or Packet (Tagged or

Untagged) with Untagged) with Untagged) with
length lower than length longer than n length between 64
Counter 64 octects (MTU value) octets and n (MTU value) oc- FCS *
Description (Undersize packet) (Oversize packet) tets (Good packet)

Received Pkts - - - x x x x x x OK
Total number of Good and Oversize packets received
Sent Pkts - - - - - - x x x OK
Total number of transmitted packets
- - - - - - - - - KO
Received Octects - - - x x x x x x OK
Total number of received octets
Sent Octects - - - - - - x x x OK
Total number of transmitted octets
- - - - - - - - - KO
Received Discard Pkts - - - x x x x x x OK
Total number of inbound packets which were discarded due
to forbidden forwarding or policing violation. - - - x x x x x x KO
Sent Discard Pkts - - - x x x x x x OK

Total number of outbound packets which were chosen to be
discarded even though no errors had been detected to pre-
vent their being transmitted. Possible reasons for discard- - - - - - - - - - KO
ing such a packet could buffer space lack due to output
shaping, rate limitation or egress MTU exceeded.
Received Unicast Pkts - - - x - - x - - OK
Total number of inbound Unicast packets
- - - x - - x - - KO
Sent Unicast Pkts - - - - - - x - - OK

Total number of outbound Unicast packets
- - - - - - - - - KO
Received Not Unicast Pkts - - - - x x - x x OK

Total number of inbound Non-Unicast packets
- - - - x x - x x KO
Sent Not Unicast Pkts - - - - - - - x x OK

Total number of outbound Non-Unicast packets
- - - - - - - - - KO


Ethernet History
The command Ethernet History displays the history of the RMon statistics.
The traffic is analyzed subdivided per Ethernet port (RMon instances per Port).
Operations
Display the history of the RMon statistic (RMon instances per Port)
Filter the history of RMon statistic (RMon instances per Port)
GUI
Ethernet History context
See also
Display the history of the RMon statistic (RMon instances per Port)
WARNING Operation meaningful only if at least one RMon instance is created and if the count of the RMon
statistics is active (see Set a RMon instance per Port to the count of the RMON history and Activate the
count of the RMon statistics).
1. Select Maintenance > RMON > Ethernet History.

The Ethernet History context shows the history of RMon statistics for all instances per Port.
In any moment it is possible to Filter the history of RMon statistic (RMon instances per Port).
Filter the history of RMon statistic (RMon instances per Port)
1. Select Maintenance > RMON > Ethernet History.
2. Set the criteria used to filter the records. The filter criteria works in AND logic:
• Index. Values which identify in unique mode the RMon instances in the database table of history
of RMon statistics (indexes) for which you wish to display the sampling intervals in table.
• Source. Ports of the Switch or LAG for which you wish to display the sampling intervals in table.
• Owner. Users who have enabled the RMON instances for which you wish to display the sampling
interval in table.
To activate an index, port/LAG or user, select the relevant box ( ), to deactivate it deactivate the rel-
evant box ( ).
It is possible to activate more indexes/ports-channels/users at the same time. By default, the table dis-
plays the records relevant to all the indexes/ports-channels/users.
3. Press Apply Filter.
4. To remove the filters and display in the table all the records relevant to all the indexes/ports-channels/
users, press Remove Filter.

Ethernet History context
The context displays the values of the RMon statistic counters (RMon instances per Port).
Table
Every line of the table corresponds to a sampling interval of an instance for which is indicated:
Time (Sample Start). Start instant (day/month/year, hour/minute/second) of every
sampling interval with which the statistics history data are collected.
Source. Identifier of the Ethernet port or LAG which the RMon instance enabled to the
count of the statistics history is associated to.
The Ethernet port identifier is a combination of slot number and the port number (slot
number/port number) followed by the port name (see Tab.5).
Owner. User who has enabled the instance.
Parameters
FILTERING
Criteria available to filter the sampling interval in the table. The filter criteria works in AND logic:
Index. Values which identify in unique mode the RMon instances in the database table
of history of RMon statistics).
Source. Ports of the Switch or LAGs.
Owner. Users who have enabled the RMON instances.
For every criterion, the active box ( ) indicates that the table contains sampling intervals
matching the specific criterion. The inactive box ( ) indicates that the table contains no sam-
pling interval matching the specific criterion.
Buttons
Apply Filter/Remove Filter. Filter the history of RMon statistic (RMon instances per Port)
See also
Ethernet History (command)

Tab.13 RMon counters (Ethernet History - RMon instance per Port)

Description
Drop Events - - - - - - - - - OK
Number of dropped packets **
- - - - - - - - - KO
Octets x x x x x x x x x OK
Number of received octets
Pkts x x x x x x x x x OK
Number of received packets
BroadcastPkts - - - - - - - x - OK
Number of packets received directed to the broadcast ad-
dresses - - - - - - - - - KO
MulticastPkts - - - - - - - - x OK
Number of packets received directed to a multicast ad-
dresses - - - - - - - - - KO
UndersizePkts x x x - - - - - - OK
- - - - - - - - - KO
OversizePkts - - - x x x - - - OK
Number of Oversize packets received
- - - x x x - - - KO
Fragments - - - - - - - - - OK
x x x - - - - - - KO
CRC Align Errors - - - - - - - - - OK

Number of Good and Oversize packets received
Utilization (%)
Estimate (expressed in percentage) of the average use of
the port during the sampling interval.
The percentage of use refers to the line rate of the associ- - - - - - - - - - -
ated porta.
The percentage of use of the radio port refers to the rate
of 2.5 Gbps

** Packets are discarded after the exhaustion of the local memory resources. This value is not necessarily
the absolute number of discarded packets, as it represents only the number of times that this condition
occurred after the exhaustion of the memory resources; the packets can be discarded also for other rea-
sons. This value does not include Output Dropped Frames.

Ethernet Service History
The command Ethernet Service History displays the history of the RMon statistics.
The analysed traffic is filtered according to the input/output port and to the characteristics of the packet:
value of User Priority (RMon instance Port & Priority) or C-TAG or S-TAG identifier (RMon instance Port &
VLAN).
Operations
Display the history of the RMon statistic (RMon instance Port & Priority and Port & VLAN)
Filter the history of RMon statistic (RMon instance Port & Priority and Port & VLAN)
GUI
Ethernet Service History context
See also
Display the history of the RMon statistic (RMon instance Port & Priority and Port & VLAN)
WARNING Operation meaningful only if at least one RMon instance is created and if the count of the RMon
statistics is active (see Set a RMon instance Port & Priority or Port & VLAN to the count of the RMON history
and Activate the count of the RMon statistics).
1. Select Maintenance > RMON > Ethernet Service History.

The Ethernet Service History context shows the history of RMon statistics for all Port & Priority and Port
& VLAN instances.
In any moment it is possible to Filter the history of RMon statistic (RMon instance Port & Priority and
Port & VLAN) according to different criteria.
Filter the history of RMon statistic (RMon instance Port & Priority and Port & VLAN)
1. Select Maintenance > RMON > Ethernet Service History.
2. Set the criteria used to filter the records. The filter criteria works in AND logic:
• Index. Values which identify in unique mode the RMon instances in the database table of history
of RMon statistics (indexes) for which you wish to display the sampling intervals in table.
• Source. Ports of the Switch or LAG for which you wish to display the sampling intervals in table.
• Owner. Users who have enabled the RMON instances for which you wish to display the sampling
interval in table.
To activate an index, port-channel or user, select the relevant box ( ), to deactivate it deactivate the
relevant box ( ).
It is possible to activate more indexes/ports-channels/users at the same time. By default, the table dis-
plays the records relevant to all the indexes/ports-channels/users.
3. Press Apply Filter.
4. To remove the filters and display in the table all the records relevant to all the indexes/ports-channels/
users, press Remove Filter.

Ethernet Service History context
The context displays the history of the RMon statistics (RMon instance Port & Priority and Port & VLAN).
Table
Every row of the table corresponds to one sampling interval of one instance for which is indicat-
ed:
Time (Sample Start). Start instant (day/month/year, hour/minute/second) of every
sampling interval with which the statistics history data are collected.
Source. Identifier of the Ethernet port or LAG which the RMon instance enabled to the
count of the statistics history is associated to.
The Ethernet port identifier is a combination of slot number and the port number (slot
number/port number) followed by the port name (see Tab.5).
Owner. User who has enabled the instance.
Edge Bridge) which the packet in input/output from the port must have to be counted by
the RMon statistics.
Value available and meaningful for RMon instances Port & Priority.
SVID. S-VID (Service VLAN Identifier) which the packet in input/output from the port
CVID. C-VID (Customer VLAN Identifier) which the packet in input/output from the port
Parameters
FILTERING
Criteria available to filter the sampling interval in the table. The filter criteria works in AND logic:
Index. Values which identify in unique mode the RMon instances in the database table
of history of RMon statistics).
Source. Ports of the Switch or LAG.
Owner. Users who have enabled the RMON instances.
For every criterion, the active box ( ) indicates that the table contains sampling intervals
matching the specific criterion. The inactive box ( ) indicates that the table contains no sam-
pling interval matching the specific criterion.
Buttons
Apply Filter/Remove Filter. Filter the history of RMon statistic (RMon instance Port & Priority
and Port & VLAN)
See also
Ethernet Service History (command)

ALARMS LIST
Tab.14 indicates the list of the alarms relevant to the equipment.

The alarms are not listed in alphabetical order but they are grouped according to the corresponding parts
of the equipment.
Equipment
COMMON
ETH LAN
OAM
P.M. ACM
P.M. G.828
P.M. Rx Power
P.M. Tx Power
Plug-in module
Queue Depth
RADIO
SETS
UNIT
For each alarm, the wording present in the Events area (see Equipment status area) of the GUI and the
wording present in the Alarm Severity Config. context are displayed.
Some alarms have some wordings in italic contained between the symbols < >. They, in the alarm dis-
played in the Events area, represent a variable.
The symbol “-“means that the alarm is not meaningful for the Alarm Severity Config. context.

Tab.14 Alarms list
Events area Alarm Severity Config. alarms
Equipment
Alarm Input <name> alarmInput
Equip. Alarm Synthesis Critical -
Equip. Alarm Synthesis Major -
Equip. Alarm Synthesis Minor -
Equip. Alarm Synthesis Warning -
COMMON
Equip Manual Operation equipManualOperation
NMS Wake Up Alarm equipManagerWakeUpAlarm
Radio Encryption Mismatch Alarm rdEncryptMismatchAlarm
ETH LAN
<LAN 1, LAN 2, LAN 3, LAN 4, MGNT, TRX> Loss of Signal Alarm ifextLosAlarm
OAM
Service OAM Domain <domain name> MA <MA name> MepId <MEP identifier> RDI Alarm defRdiCcmAlarm
Service OAM Domain <domain name> MA <MA name> MepId <MEP identifier> MAC Status defMacStatusAlarm
Alarm
Service OAM Domain <domain name> MA <MA name> MepId <MEP identifier> Remote CCM defRemoteCcmAlarm
Alarm
Service OAM Domain <domain name> MA <MA name> MepId <MEP identifier> Error CCM defErrorCcmAlarm
Alarm
Service OAM Domain <domain name> MA <MA name> MepId <MEP identifier> Xconn CCM defXconCcmAlarm
Alarm
P.M. ACM
P.M. ACM <Radio Link name> 15M counter <1=unavail., 2=downshift, 3=upshift, 6=4QAMS, acmsTpProfile15mAlarm
7=4QAM, 10=16QAMS, 11=16QAM, 13=32QAM, 15=64QAM, 17=128QAM, 19=256QAM,
21=512QAM, 23=1024QAM, 25=2048QAM, 27=4096QAM> threshold cross Alarm
P.M. ACM <Radio Link name> 24H counter <1=unavail., 2=downshift, 3=upshift, 6=4QAMS, acmsTpProfile24HAlarm
7=4QAM, 10=16QAMS, 11=16QAM, 13=32QAM, 15=64QAM, 17=128QAM, 19=256QAM,
21=512QAM, 23=1024QAM, 25=2048QAM, 27=4096QAM> threshold cross Alarm
P.M. G.828
P.M. G.828 <transceiver> 15M counter ES threshold cross Alarm pmG828-15MEsAlarm
P.M. G.828 <transceiver> 15M counter SEP threshold cross Alarm pmG828-15MSepAlarm
P.M. G.828 <transceiver> 15M counter SES threshold cross Alarm pmG828-15MSesAlarm
P.M. G.828 <transceiver> 24H counter ES threshold cross Alarm pmG828-24HEsAlarm
P.M. G.828 <transceiver> 24H counter SEP threshold cross Alarm pmG828-24HSepAlarm
P.M. G.828 <transceiver> 24H counter SES threshold cross Alarm pmG828-24HSesAlarm
P.M. G.828 <transceiver> UAS Alarm pmG828-UASAlarm

P.M. Rx Power
P.M. RxPower <transceiver> 15M counter Rlts1 threshold cross Alarm pmRxPwr-15MRltsAlarm
P.M. RxPower <transceiver> 15M counter Rlts2 threshold cross Alarm pmRxPwr-15MRlts2Alarm
P.M. RxPower <transceiver> 24H counter Rlts1 threshold cross Alarm pmRxPwr-24HRltsAlarm
P.M. RxPower <transceiver> 24H counter Rlts2 threshold cross Alarm pmRxPwr-24HRlts2Alarm
P.M. Tx Power
P.M. TxPower <transceiver> 15M counter Tlts1 threshold cross Alarm pmTxPwr-15MTltsAlarm
P.M. TxPower <transceiver> 15M counter Tlts2 threshold cross Alarm pmTxPwr-15MTlts2Alarm
P.M. TxPower <transceiver> 24H counter Tlts1 threshold cross Alarm pmTxPwr-24HTltsAlarm
P.M. TxPower <transceiver> 24H counter Tlts2 threshold cross Alarm pmTxPwr-24HTlts2Alarm
Plug-in module
<LAN 1, LAN 2> Plug-in module Fail Alarm plug-inModuleAlarm
Queue Depth
Queue Depth Profile Mismatch Alarm qdProfileMismatchAlarm
RADIO
<transceiver> Invalid Frequency Alarm radioInvalidFrequencyAlarm
<transceiver> Rx Power Low Alarm radioRxPowerLowAlarm
<transceiver> Tx Power Alarm radioTxPowerAlarm
<transceiver> Vco Fail Alarm radioRtVcoFail
<transceiver> Rx AGC Alarm radioRxAGCAlarm
<transceiver> Tx AGC Alarm radioTxAGCAlarm

<transceiver> IDU ODU Communication Alarm radioIduOduCommunicationAlarm
<transceiver> ODU IDU Communication Alarm radioOduIduCommunicationAlarm
<transceiver> Local alarm synthesis radioLocalOduAlarmSynthesis
<transceiver> Remote alarm synthesis radioRemoteOduAlarmSynthesis
<transceiver> Configuration parameter Mismatch Alarm radioConfigMismatch
<transceiver> Radio Rx Quality Low Alarm radioRxQualityLowAlarm
<transceiver> Radio Rx Quality Warning Alarm radioRxQualityWarningAlarm

<transceiver> Rx Active Status radioRxActiveStatus
<transceiver> Tx Active Status radioTxActiveStatus
Radio Link <Radio Link name> Telemetry Fail Alarm linkLinkTelemetryFailAlarm
Radio Link <Radio Link name> Adaptive Modulation Reduced Capacity Notification linkReducedCapacityAlarm
Radio Link <Radio Link name> ID Alarm linkIdAlarm
Radio Link <Radio Link name> Radio EOC Alarm linkRadioEocAlarm
Radio Link <Radio Link name> Setup Mismatch Alarm linkSetupMismatchAlarm
Radio Link <Radio Link name> Rescue Modulation Setup Alarm linkRescueSetupAlarm
Radio Link <Radio Link name> FMP: Xpic disable linkXpicProcedureBlockAlarm
Radio Link <Radio Link name> FMP: Tx Off Under Remote End Request linkXpicRemTxOffAlarm
Radio Link <Radio Link name> Remote Alarm Synthesis linkRemoteIduAlarmSynthesis
Radio Branches <transceiver> No Matching Radios Parameters linkNoMatchingRadiosAlarm
Radio Link <Radio Link name> Transmitter Switch on Remote Terminal BER linkTfcAlarm
Local Radio Alarm Synthesis linkLocalRadioAlarmSynthesis
L1 Aggregation Port <TRX> Fail Alarm aggrL1FailAlarm
L1 Aggregation Port <TRX> Degrade Alarm aggrL1DegradeAlarm
L1 Aggregation Port <TRX> Realignment Alarm aggrL1RealignmentAlarm
<LAN 1, LAN 2, LAN 3, LAN 4, MGNT, TRX> Link Loss Forwarding Alarm llfAlarm
<LAN 1, LAN 2, LAN 3, LAN 4, MGNT, TRX> Link BER Sync Loss Alarm linkBerSyncLossAlarm
<transceiver> Demodulator Fail Alarm radioDemodulatorFailAlarm
<transceiver> Remote Demodulator Fail Alarm radioRemDemodulatorFailAlarm
<transceiver> TxOfTx Calibration Failure radioModulatorFailAlarm
<transceiver> TxOfTx Calibration in progress linkConfigurationInProgress
SETS
BASE BAND Sets <synchronism signal name> Active Status timingSynkActiveStatus
BASE BAND Sets <synchronism signal name> Drift Alarm timingSynkDriftAlarm
BASE BAND Sets <synchronism signal name> LTI Alarm timingSynkLossAlarm
BASE BAND Sets Free Running Status timingGeneratorFreeRunningStatus
BASE BAND Sets Holdover Status timingGeneratorHoldoverStatus
BASE BAND Sets T0 Fail Alarm timingGeneratorT0FailAlarm

BASE BAND Sets T4 Squelch Alarm timingGeneratorT4SquelchAlarm
BASE BAND Sets Active Status timingGeneratorActiveStatus
UNIT
<unit name> Unit Fail Alarm unitFailAlarm
<unit name> Unit Missing Alarm unitMissingAlarm
<unit name> Unit Not Responding Alarm unitNotRespondingAlarm
<unit name> Unit Hw Mismatch Alarm unitHwMismatchAlarm
<unit name> Unit Sw Mismatch Alarm unitSwMismatchAlarm

OPERATIONS LIST
A
ACL
Add a rule to ACL ..............................................................................................................106
Modify a rule of ACL ...........................................................................................................107
Remove a rule from ACL .....................................................................................................107
Verify the rules used by the ACL ..........................................................................................106
Alarms
Change the severity of an alarm ........................................................................................... 75
Delete the log of the equipment alarms ................................................................................. 56
Enable/disable an alarm ...................................................................................................... 74
Enable/disable the forwarding of the trap of an alarm .............................................................. 74
Save the log of the equipment alarms ................................................................................... 55
Verify the severity and the enabling/forwarding status of the alarms ......................................... 74
ATPC
Verify/modify the functioning status .....................................................................................249
Verify/modify the intervention threshold ...............................................................................250
Verify/modify the maximum output power value at the transmitter ..........................................250
Verify/modify the range of the ATPC regulation .....................................................................250
B
Bridge Mode
Modify the Bridge mode of the Ethernet Switch ......................................................................143
Verify the Bridge mode of the Ethernet Switch .......................................................................143
C
Communication protocol
Enable/disable the administrative status of a communication protocol .......................................111
Verify the operating status of the communication protocols .....................................................111
D
Delete the log of the operations executed by the users ................................................................. 56
Digital loop
Activate ...........................................................................................................................266
Deactivate ........................................................................................................................267
Verify the status ................................................................................................................266
E
Enable a new equipment feature ............................................................................................... 37

Equipment configuration
Retrieve the equipment configuration automatically saved by the program before the last operation
of configuration restore (configuration revert) ........................................................................ 70
Save the whole equipment configuration (configuration backup) ............................................... 69
Transfer the equipment configuration previously saved (configuration restore) ........................... 70
Equipment firmware
Switch the memory benches ................................................................................................ 63
Equipment reference date/time, align to the PC date/time ............................................................ 37
Equipment software reset .................................................................................................... 36, 64
Equipment software/firmware
Update .............................................................................................................................. 62
Verify the version ............................................................................................................... 62
Ethernet ports
Activate the loop on line side of a port ..................................................................................146
Deactivate the loop on line side of a port ..............................................................................146
Modify the activation state of the autonegotiation for a port ....................................................146
Modify the Bridge Port Type for a port ..................................................................................148
Modify the enabling status of a port .....................................................................................145
Modify the inversion status of the Tx and Rx lines of a port .....................................................147
Modify the maximum dimension of the packet accepted by a ports ...........................................147
Modify the transmission speed of a port ................................................................................147
Modify the type of interface ................................................................................................145
Restart the auto negotiation procedure for a port ...................................................................147
Verify the Ethernet ports configuration ......................................................................... 145, 148
Verify the flow control configuration of the Ethernet ports .......................................................149
Verify the parameters for the Tunneling management ............................................................150
Verify the status of the ports as regards the Link Aggregation function .....................................150
Verify/modify the traffic class which a packet, in input from a port, is assigned to, depending
on its priority (User Priority) ...............................................................................................149
EtherType
Modify the EtherType values in the S-Tag field of a port/LAG ...................................................171
Verify the EtherType values in the S-Tag field of the Ethernet ports .........................................171
H
Header Compression
Enable/disable the functionality ...........................................................................................173
Verify the status of the functionality .....................................................................................173
Verify/modify the context depth to compress in the header of the Ethernet packets ....................173
Verify/modify the parsing mode applied to the header of the Ethernet packets ...........................174
HTTPS
Download the SSL certificate in an equipment .......................................................................114
Generate the Certificate Signing Request for an equipment .....................................................114
Modify the list of CipherSuite managed by the equipment .......................................................113
Verify the configuration of the SSL protocol ...........................................................................113
L
LAN

Modify the operating mode of line synchronism (role) of the LAN’s ...........................................237
Link Aggregation
Add/remove the ports to/from one LAG ................................................................................205
Create a static LAG ............................................................................................................202
Create a static LAG for protection (ELP) ................................................................................203
Define the ports members of one LAG ..................................................................................204
Delete a static LAG ............................................................................................................204
Modify the allocation of memory for the Link Aggregation function ...........................................201
Modify the configuration of a static LAG (Admin State, MTU and/or Max Ports) ...........................203
Modify the enabling of Link Aggregation function ...................................................................202
Modify the LACP settings for the ports member of a LAG (Activity and/or Timeout) .....................206
Remove all the ports from one LAG ......................................................................................205
Verify the LACP settings for the ports member of one LAG ......................................................206
Verify the ports member of one LAG ....................................................................................204
Verify the static LAGs .........................................................................................................202
Verify the status and configuration of Link Aggregation function ...............................................201
Verify/modify the policy for the distribution of the Ethernet traffic ............................................206
LLF
Configure a port for the management of LLF functionality .......................................................190
Configure the radio circuit for the forwarding of the LOS alarm present on LAN ..........................191
Enable/disable the forwarding of LLF alarm on the radio .........................................................192
Enable/disable the LLF functionality for a LAN ........................................................................192
Modify the forwarding of LOS alarm of a LAN to the radio .......................................................193
Modify the hysteresis value for the LLF functionality ...............................................................193
Modify the modality used to forward the alarm LOS on the radio circuit ....................................193
Modify the propagation modality of LLF alarm ........................................................................193
Remove a port of the switch from the management of LLF functionality ....................................191
Remove a radio circuit from the management of LLF functionality for a given LAN ......................192
Verify the status of the LLF functionality for the Ethernet ports ................................................190
M
MAB
Create a MAB Monitor instance ............................................................................................258
Create a MAB Sender instance .............................................................................................260
Delete one or more Monitor MAB instance .............................................................................259
Delete one or more Sender MAB instances ............................................................................261
Modify the configuration of a Sender MAB instance ................................................................260
Modify the configuration of the Monitor MAB Instance .............................................................259
Verify the existing MAB instances ........................................................................................258
MAN OP
Activate/deactivate a digital loop .........................................................................................271
Disable temporarily/restore the XPIC function .......................................................................272
Disable/enable the modulation of the RF carrier .....................................................................271
Force the status of the T0 synchronisation ............................................................................272
Force the use of a synchronism source .................................................................................272
Turn-off/turn-on the transmitter ..........................................................................................270
Verify the active manual operations ...................................................................................... 32
Verify the manual operations status .....................................................................................270
Verify/modify the manual operation timeout ........................................................................... 32

MNGT port
Enable/disable the Loss of Signal Alarm for the port ...............................................................226
Modify the 802.1p priority for the management VLAN .............................................................223
Modify the activation state of the autonegotiation for the port .................................................224
Modify the Bridge Port Type for the port ...............................................................................225
Modify the DSCP value for the management VLAN .................................................................224
Modify the enabling status of port ........................................................................................223
Modify the inversion status of the Tx and Rx lines of the port ..................................................224
Modify the IP Address used as Default Gateway .....................................................................223
Modify the IP Address/NetMask of the port ............................................................................222
Modify the transmission speed of the port .............................................................................224
Modify the VLAN reserved for the in-band management ..........................................................223
Modify the VLAN reserved for the management .....................................................................223
Restart the auto negotiation procedure for the port ................................................................225
Verify the configuration of the management port ...................................................................222
Modify the equipment identifier ................................................................................................. 36
Modify the IP address of the agent SNMP .................................................................................... 36
P
PB-VLAN
Verify the C-VID registration table (C-VID Registration) ..........................................................167
Verify the Provider Edge Port configuration table (PEP Configuration) .......................................167
PM
Activate one or more measures ............................................................................................ 43
Deactivate one or more measures ........................................................................................ 43
Reset the threshold exceeding alarms of one or more PM measures .......................................... 43
Reset the values of the records daily and primary of one or more PM measures .......................... 43
Set the thresholds of the control parameters and alarms of a PM measure ................................. 44
Verify the status, the results and the threshold exceeding alarms of a PM measure ..................... 42
Q
Queue Depth
Modify the policy for the management of the depth of the queues in output ..............................198
Verify the policy for the management of the depth of the queues in output ...............................198
R
Radio
Modify the lower threshold of the modulation ........................................................................131
Modify the operating status of the adaptive modulation ..........................................................131
Modify the reference band ..................................................................................................130
Modify the reference modulation ..........................................................................................131
Modify the upper threshold of the modulation ........................................................................131
Verify the operating status and the configuration parameters of the adaptive modulation ............130
Verify the reference band/modulation ...................................................................................130
Verify/modify the duplexer frequency ...................................................................................248

Verify/modify the modulation status of the RF carrier .............................................................267
Verify/modify the operation of the transmitter .......................................................................267
Verify/modify the radio Link label ........................................................................................134
Verify/modify the resolution of the received power (Prx) .........................................................249
Verify/modify the resolution of the transmitted power (Ptx) ....................................................249
Verify/modify the threshold level of the signal at reception ......................................................134
Verify/modify the transmission frequency .............................................................................248
Radio BER
Activate the measure .........................................................................................................256
Deactivate the measure .....................................................................................................256
Verify the configuration parameters of the measure ...............................................................256
Verify the status of the measure ..........................................................................................256
Radio configuration
Delete a Radio Link ............................................................................................................127
Modify a Radio Link ............................................................................................................126
Verify the Radio Link configuration .......................................................................................125
Radio Encryption
Modify the allocation of memory for Radio Encryption function .................................................116
Modify the data encryption algorithm ...................................................................................117
Modify the enabling of Radio Encryption function ...................................................................117
Modify the encryption key ...................................................................................................117
Verify the status and configuration of Radio Encryption function ...............................................116

Add a station ..................................................................................................................... 26
Add equipment .................................................................................................................. 27
Open the WEB page of equipment (Remote Link) .................................................................... 28
Remove a station ............................................................................................................... 26
Remove equipment ............................................................................................................. 27
Rename a station ............................................................................................................... 26
Reset ................................................................................................................................ 28
Restore Factory Default of the equipment ................................................................................... 64
RMon
Activate the count of the RMon statistics ...............................................................................275
Deactivate the count of the RMon statistics ...........................................................................276
Delete a RMon instance per Port for the count of the history of the RMON statistics ....................279
Delete a RMon instance per Port for the count of the RMon statistics ........................................277
Delete a RMon instance Port & Priority or Port & VLAN for the count of the RMON history ............281
Delete a RMon instance Port & Priority or Port & VLAN for the count of the RMon statistics ..........278
Display the history of the RMon statistic (RMon instance per Port & Priority and per Port & VLAN) 299
Display the history of the RMon statistic (RMon instances per Port) ..........................................296
Display the values of the RMon statistic counters (RMon instances per Port) ..............................290
Display the values of the RMon statistic counters (RMon instances Port & Priority and
Port & VLAN) ....................................................................................................................293
Filter the history of the RMon statistic (RMon instance Port & Priority and Port & VLAN) ...............299
Filter the history of the RMon statistic (RMon instances per Port) .............................................296
Reset the counters’ results of the RMon statistics ...................................................................276
Set a RMon instance per Port to the count of the RMon history ................................................278
Set a RMon instance per Port to the count of the RMon statistics ..............................................276
Set a RMon instance Port & Priority or Port & VLAN to the count of the history of the RMON
statistics ..........................................................................................................................279
Set a RMon instance Port & Priority or Port & VLAN to the count of the RMon statistics ................277
Verify the count status of the RMon statistics ........................................................................275

Routing Table
Add an element to the Routing Table ....................................................................................229
Remove one or more elements from the Routing Table ...........................................................230
Verify the Routing Table of the equipment ............................................................................229
RSTP
Enable/disable the use of STP/RSTP protocol for the equipment ...............................................177
Verify the information stored by every single Switch port ........................................................182
Verify/modify the allocation of memory for the STP/RSTP function ...........................................178
Verify/modify the cost of the a port ......................................................................................182
Verify/modify the dynamic path cost calculation function (STP/RSTP) .......................................179
Verify/modify the enabling of STP/RSTP function ...................................................................179
Verify/modify the interoperability of the equipment with other equipment .................................182
Verify/modify the maximum number of BPDU packets in transmission ......................................180
Verify/modify the parameters for the transmission of BPDU packets .........................................180
Verify/modify the ports set for the STP/RSTP function ............................................................178
Verify/modify the priority assigned to the Switch ...................................................................180
Verify/modify the priority of a port .......................................................................................181
Verify/modify the status of the STP/RSTP function of a port ....................................................181
Verify/modify the version of the protocol ..............................................................................180
S
S/N measure
Update the value ...............................................................................................................254
Verify the value .................................................................................................................254
Save the equipment configuration ............................................................................................. 57
Save the log of the operations executed by the users ................................................................... 56
Security
Enable/disable the FTP and/or SFTP protocol .........................................................................121
Modify the FTP access credentials ........................................................................................121
Modify the SFTP access credentials ......................................................................................122
Verify the operating status of the FTP and SFTP protocols .......................................................121
Statistics
Reset the counters’ results (Ethernet-like Statistics group) ......................................................216
Reset the counters’ results (Interfaces group) .......................................................................216
Verify the counters of the Ethernet interfaces (Ethernet-like Statistics group) ............................216
Verify the counters of the Ethernet interfaces (Interfaces group) .............................................216
Synchronisation
Enable/disable the use of a synchronism source ....................................................................234
Enable/disable the use of the source quality as criterion to select the synchronism .....................234
Force the quality level in input and/or output of a synchronism source ......................................236
Force the status of the T0 synchronisation ............................................................................232
Force the use of a synchronism source .................................................................................235
Modify the use priority of a synchronism source .....................................................................235
Restore the availability of a source for the selection of the T0 synchronism without waiting
for the expiry of Wait Time .................................................................................................236
Set a synchronism source as preferential ..............................................................................235
Set the Hold Off Time parameter .........................................................................................233
Set the threshold levels of the LTI alarm ..............................................................................233
Set the WTR Time parameter ..............................................................................................233

Verify the status and configuration of the synchronism sources ................................................234
Verify the status and configuration of the T0 synchronism .......................................................232
Verify/modify the management of SSM protocol for every single LAN ........................................237
Verify/modify the management of synchronisation .................................................................234
U
Users
Add a user ......................................................................................................................... 94
Add a user group ................................................................................................................ 79
Delete a user ..................................................................................................................... 96
Delete a user group ............................................................................................................ 81
Force the logout of a user ...................................................................................................103
Modify a user ..................................................................................................................... 95
Modify a user group ............................................................................................................ 80
Set/modify the IP address of Permanent Login ......................................................................101
Verify the IP address of Permanent Login ..............................................................................101
Verify the user groups ......................................................................................................... 79
Verify the users connected to the equipment .........................................................................103
Verify the users list ............................................................................................................. 94
V
Verify the basic configuration of the equipment ........................................................................... 36
Verify the equipment feature .................................................................................................... 37
Verify the equipment units (type, code, version and functional status) ............................................ 38
Verify/modify the link identification number ...............................................................................131

VLAN
Create one or more static VLANs .........................................................................................160
Delete one or more static VLANs ..........................................................................................162
Enable/disable the learning of the addresses in the MAC Table .................................................158
Modify the aging time of the addresses stored in the MAC Table ..............................................159
Modify the check modality (filtering) applied to the packets in input on a port/LAG .....................159
Modify the configuration of a static VLAN ..............................................................................161
received on the port/LAG ....................................................................................................160
Modify the default VLAN identifier of a port/LAG (Port VID) .....................................................160
Modify the limit of MAC unicast addresses managed by the Switch for the VLAN’s ......................159
Modify the type of packets accepted in input by a port/LAG .....................................................159
Verify the basic configuration of the VLAN management .........................................................158
Verify the existing static VLANs ...........................................................................................160
W
Wake Up functionality
Activate ............................................................................................................................ 59
Deactivate ......................................................................................................................... 59
Set the execution parameters .............................................................................................. 59

Verify the status ................................................................................................................. 59
WEB LCT page

Close the page ................................................................................................................... 19
Display the page of equipment (Remote Link) ........................................................................ 24
Open more pages ............................................................................................................... 19
Open the WEB LCT page ...................................................................................................... 18
X
Xpic
Disable temporarily the function XPIC for a single transceiver ..................................................136
Enable/disable XPIC fault management procedure (FMP) .........................................................137
Restore the function XPIC after a fault detection ....................................................................137
Restore the XPIC function of the single ODU ..........................................................................136
Verify the configuration parameters of the XPIC function ........................................................136

PARAMETERS LIST
A E
ACL Equipment Feature
Filter Action ........................................108 2+0 radio configuration ......................... 40
Index .................................................108 ETH transport ...................................... 40
Interfaces ...........................................108 Packet processing (1) ............................ 40
IP Address ..........................................108 Radio payload encryptions ..................... 40
Mask .................................................108 Security package .................................. 40
Priority ...............................................108 Sync Quality management ..................... 40
Upgrade up to 100Mbps ........................ 40
ACM Engine .............................................132
ACM Table Upgrade up to 300Mbps ........................ 40
Active Modulation ................................132
Ethernet Capacity ................................132
Global Capacity ...................................133 Upgrade up to 50Mbps .......................... 40
Agent IP Address .................................. 22, 39 XPIC ................................................... 40
Alarms ..................................................... 77 Equipment firmware

Group/Alarm ........................................ 76 Actual Release ..................................... 65
Severity .............................................. 76 Bench Status ....................................... 65
Trap Notification ................................... 76 Download Status .................................. 65
Release Bench 1 ................................... 66
ATPC
Release Bench 2 ................................... 66
ATPC Full Range ..................................252
Software ............................................. 65
ATPC Regulation ..................................252
Software Version .................................. 65
ATPC Thresholds on Local PRx ...............252
Unit .................................................... 65
Max Ptx ..............................................252
Tx Power Control .................................252 Equipment ID ...................................... 22, 39
Equipment Type ................................... 22, 39
Equipment unit
B Expected Type ..................................... 40
Bandwidth ...............................................132 HW Ver. .............................................. 40

Par Part Number ................................... 40
Bridge Mode ...................................... 22, 144
Part Number ........................................ 40
Real Type ............................................ 40
Serial Number ...................................... 41
C Unit Alarms ......................................... 41
Carrier Only ..................................... 269, 273 Ethernet Bridge Mode ................................ 39
EthType
Description .........................................172
Egress EtherType ................................172
D
Ingress EtherType ...............................172
Dplx Freq ................................................251 Port ...................................................172

F Load Balancing
Description ....................................211
Factory default .......................................... 66 Policy ............................................211
Firmware Version ...................................... 39 Port Channel ..................................211
Forced Switch ..........................................273 Link Label ...............................................135
FTP protocol ............................................. 16 LLF

Alarm to Circuit ...................................195
Circuit ................................................195
Delay Time .........................................195
H Descr .................................................195
Header Compression Link ID ...............................................195
Context Depth ....................................175 LLF Status ..........................................195
H.C. Status .........................................175 LOS Insertion Mode .............................195

Parsing Mode ......................................175 LOS to Circuit .....................................195
Port ...................................................175 Port ...................................................195

Protection Mode ..................................195
Help Web Server ....................................... 16
Signal Fail ..........................................195
Local Link ID ............................................133
I Lower Profile ............................................132
IP Address ................................................ 39
L MAB
Sender
LA Admin Status .................................262
General Settings OAM Maint Level .............................263
Admin State ...................................208 PDU Compliance .............................263
Bridge Port Type .............................208 Port index ......................................262
LA Status ......................................207 Sensor Index .................................262
Link Status ....................................207 User Priority ...................................263
Max Ports ......................................208 VLAN ID ........................................262
MTU ..............................................208 Sensor
Port Channel ID ..............................207 Admin Status .................................262
System Control ..............................207 BW Mode .......................................262
System ID .....................................207 Curr. BW (Mbps) ............................262
LACP Holdoff Time (s) .............................262
Activity .........................................210 Link ID ..........................................262
Description ....................................209 Nom. BW (Mbps) ............................262
Mode ............................................209 Observ. Time (s) ............................262
Port ..............................................209 ODU Index .....................................262
Port Channel State ..........................209 Sensor Index .................................262
Port State ......................................210
MAC Address ............................................ 39
Timeout ........................................210
LAG Manager IP Address 1 ...............................102
Aggregation Type ...........................208
Manager IP Address 2 ...............................102
Mode ............................................209
Port Channel ..................................208 Measurements Resolution
Ports .............................................208 Prx ....................................................251

Ptx ....................................................251 LA
Description ....................................155
MNGT port
Port ..............................................155
Admin State .......................................227
Port Channel ..................................156
Auto Neg ............................................227
Port Channel State ..........................155
Bridge Port Type .................................227
Optical
Default Gateway ..................................227 Description ....................................153
DSCP Priority ......................................227 Fail Alarm ......................................153
IP Address ..........................................227 Link Length 50um (m) .....................154
Link Status .........................................227 Link Length 62.5um (m) ..................154
MDI/MDIX ..........................................227 Link Length 9um (m) ......................153
Net Mask ............................................227 Nominal Bit Rate (Mbps) ..................153
PCP Priority ........................................227 Port ..............................................153
Port Alarm Report ................................227 Vendor Date ..................................153
Vendor Name .................................153
Speed ................................................227
Vendor PN .....................................153
VLAN ID .............................................227
Vendor SN .....................................153
Wave Length (nm) ..........................153
Physical
P Admin State ...................................151
Auto Neg .......................................152
PB-VLAN
Bridge Port Type .............................152
Acceptable Frame Types .......................169
Description ....................................151
COS Preservation ................................169 Duplex ..........................................152
C-VLAN ID ..........................................168 Link Status ....................................151
Default User Priority ............................169 MDI/MDIX .....................................152
Ingress Filtering ..................................169 Media ............................................151
Port ........................................... 168, 169 MTU ..............................................152
P-VID ................................................169 Port ..............................................151
S-VID ................................................169 Speed ...........................................152
S-VLAN ID ..........................................168 Tunneling
Untagged CEP .....................................168 BPDU Priority .................................156

Dot1x ...........................................156
Untagged PEP .....................................168
GMRP ............................................157
Port Manager GVRP .................................... 156, 157
802.1p IGMP ............................................157
Description ....................................155 LACP .............................................156
Port ..............................................155 LLDP ..................................... 156, 157
Priority 0 .......................................155 MMRP ................................... 156, 157
Priority 1 .......................................155 MVRP .................................... 156, 157
Priority 2 .......................................155 Port ..............................................156
Priority 3 .......................................155 STP ..............................................156
Priority 4 .......................................155
Priority 5 .......................................155
Priority 6 .......................................155
Priority 7 .......................................155 Q
Data Flow Queue Depth
Description ....................................154
Action ................................................199
Flow Control Admin Status ...............154
Profile ................................................199
Flow Control Oper Status .................154
Profile description ................................199
Port ..............................................154
GMRP ................................................156

R RSTP Status ...................................185
Port Status
Radio BER
Description ....................................186
BER ...................................................257 Designated Bridge ..........................187
Elapsed Time ......................................257 Designated Cost .............................187
Errors ................................................257 Designated Port ..............................187
Fail Alarms .........................................257 Designated Root .............................187
Sync Loss Alarm ..................................257 Port ..............................................186
Test Mode ..........................................257 Port Role .......................................186
Port State ......................................186
Radio Configurator
Type .............................................187
Link Name ..........................................128
Priority ...............................................184
Link Type ...........................................128
Status ................................................184
Link# .................................................128
System Control ...................................183
Radio .................................................128
Tx Hold Count .....................................184
Radio Ports .........................................128
Version ..............................................184
Radio Encryption
Rx Signal Level Alarm Threshold .................135
Admin State .......................................118
Encrypt Algo. ......................................118
System Control ...................................118
S
Radio Loop ..............................................273
S/N ........................................................255
Reference Modulation ...............................132
Service Name .................................. 115, 123
Remote Element Table ............................... 29
Service Status .........................................123
Remote equipment list ............................... 29
Services Status Config
RMon
Admin Status ......................................112
Statistics
Operative Status .................................112
RMON Status .................................282
Service Name .....................................112
Routing Table
Statistics
Destination .........................................231
Descr .................................................218
Distance .............................................231
Port ...................................................218
Gateway ............................................231
Interface ............................................231 Status Control ..........................................273
Protocol .............................................231
Status signal ............................................. 77
Subnet Mask .......................................231
Synchronisation
RSTP
1000Base-T Role
Dynamic Path Cost Calculation ..............183
Description ....................................242
Dynamic Path Cost Lag-Speed ...............184 Media ............................................242
Enable Ports .......................................183 Port ..............................................242
Forward Delay ....................................184 Role ..............................................242
Hello Time ..........................................184 Alarms ...............................................238
Max Age .............................................184 Forced Switch .....................................239
Port Settings General
802.1W Interop ..............................186 Current .........................................239
Description ....................................185 Status ...........................................239
Path Cost ......................................186 Hold Off Time ......................................238
Port ..............................................185 LAN SSM
Port Priority ...................................185 Description ....................................241
Port Role .......................................185

Media ............................................241 User ................................................... 97
Port ..............................................241
Rx Dropped Pkts .............................241
Rx Errored Pkts ..............................241
Rx Pkts .........................................241 V
SSM Enable ...................................241
VLAN
Tx Pkts .........................................241
Acceptable Frame Types .......................164
LTI Reset Time ....................................238
Default User Priority .............................165
LTI Set Time .......................................238
Description .........................................164
Name ................................................239
Ether Type ..........................................165
Preferential Switch ..............................239
Global MAC Learning Status ..................163
Priority ...............................................239
Ingress Filtering ..................................164
Status Control .....................................238
Learning Mode ....................................163
Sync Loss ...........................................240
MAC Add. Table Aging Time ..................163
T0
Max Supported VLAN ...........................164
Ovw Rx Qlty ..................................240
Max. VLAN ID .....................................163
Ovw Tx Qlty ...................................240
Member Ports .....................................165
Rx Quality .....................................240
Num of VLANs in the System .................164
Source ..........................................239
Port ...................................................164
Tx Quality ......................................240
WTR Time ..........................................238 PVID ..................................................165
Unicast MAC Learning Limit ...................163
System Date/Time ..................................... 39
Unicast MAC Limit ................................165
System Up Time ........................................ 39 Untagged Ports ...................................165
VLAN ID .............................................165
T
W
Tx Freq ...................................................251
Wake Up
Tx Transmitter ................................. 269, 273
NE Location ......................................... 60
NMS IP Address .................................... 60
Status ................................................. 60
U Timeout (Minutes) ................................ 60
Upper Profile ...........................................132 WEB LCT

Product Code ....................................... 39
Users
Auth ................................................... 97 Release ............................................... 11
Version ............................................... 39
Group ................................................. 97
Groups WEB LCT Console ...................................... 16
CLI ................................................ 82
FTP ................................................ 82
HTTP ............................................. 82
HTTPS ............................................ 82 X
Name ............................................. 82
Xpic ........................................................273
Profile ....................................... 82, 97
Fault Management Procedure ................138
SFTP .............................................. 82
TRX A ................................................138
SNMP ............................................. 82
TRX A FMP Tx Off Under Remote End
SSH ............................................... 82
Request .............................................138
Priv .................................................... 97
TRX A FMP Xpic Disable ........................138
Timeout .............................................. 97
TRX B ................................................138

TRX B FMP Xpic Disable ........................138
XPD
TRX A ...........................................138
TRX B ...........................................138

ASSISTANCE SERVICE
For more information, refer to the section relevant to the technical support on the Internet site of the com-
pany manufacturing the product.


Web Lct-Alfoplus2 1.1 Mn00351e 002

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Web Lct-Alfoplus2 1.1 Mn00351e 002

Uploaded by

Copyright:

Available Formats

WEB LCT

MANUAL CONTENT ................................................................................................................. 11

WEB LCT APPLICATION.......................................................................................................... 12

CHARACTERS SET .............................................................................................................. 15

WEB LOCAL CRAFT TERMINAL (WEB LCT) PAGE..................................................................... 17

OPEN/CLOSE THE WEB LCT PAGE ......................................................................................... 18

ELEMENTS OF THE WEB LCT PAGE ........................................................................................ 20

MESSAGES DISPLAYED IN THE WEB LCT PAGE ....................................................................... 33

WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 1

2 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 3

4 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

BASE BAND ......................................................................................................................141

WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 5

6 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 7

8 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 9

ALARMS LIST ....................................................................................................................... 301

OPERATIONS LIST ............................................................................................................... 305

PARAMETERS LIST ............................................................................................................... 313

ASSISTANCE SERVICE.......................................................................................................... 319

10 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

In this manual, to make the writing easier, the wording:

WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 11

* See MNGT Port Configuration)

12 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

Through WEB LCT application, it is possible to manage:

WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 13

Remote equipment list

WEB LCT Session

* CLI user. User of SM-OS (Siae Microelettronica - Operating System) application.

14 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 15

16 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

Open/close the WEB LCT page

WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 17

Open the WEB LCT page

Open the WEB LCT page

The opening of the WEB LCT page is supported with:

As help for the WEB LCT application in order to manage the:

2. In the address box type the IP Address of the equipment.

4. Type the password, in the Password box.

18 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

Close the WEB LCT page

Select the [Logout] parameter.

WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 19

1 - Equipment Menu area

Fig.2 shows an example of WEB LCT page on an ALFOplu2 equipment.

Fig.2 Elements of the WEB LCT page (ALFOplu2)

20 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002 21

This area shows the equipment general properties.

Equipment ID. Equipment identifier.

Agent IP. IP Address assigned to the agent SNMP of the equipment.

RIGHT TABLE. Channel/modulation and Ethernet radio traffic (Tx/Rx):

The parameters are subdivided by transceiver:

Press to force the Equipment Info area updating.

22 WEB LCT ALFOplus2 - Release 1.1 - MN.00351.E - 002

User Profile parameter

User Profile parameter

Read/Write. The user has Read/Write profile.

Maint. The user has Maintenance profile.

Read Only. The user has Read Only profile.