Eda2530r421 PDF

1/1553-HSC901 003/2 Uen B
Operating Guide
EDA2530 Access Hub Release 4.21
Operating InstDRAFT01s
Copyright
© Ericsson AB, 2008. All Rights Reserved
Disclaimer
All rights reserved. The information in this document is the property of

Ericsson. Except as specifically authorized in writing by Ericsson, the
receiver of this document shall keep the information contained herein
confidential and shall protect the same in whole or in part from disclosure
and dissemination to third parties. Disclosure and disseminations to the
receiver's employees shall only be made on a strict need to know basis.
Trademark List
Microsoft Microsoft MS and MS-DOS are registered

MS and MS-DOS trademarks of the Microsoft Corporation in the
United States of America and other countries.
Windows Windows is a trademark of the Microsoft

Corporation in the United States of America
and other countries.
Adobe Reader Adobe and Reader are either registered

trademarks or trademarks of Adobe Systems
Incorporated in the United States and/or other
countries.
HP-UX HP-UX is a registered trademark of Hewlett-

Packard Company. (HP-UX®) in the United
States and/or other countries.
JAVA JRE JAVA is a trademark or registered trademark

of Sun Microsystems, Inc. in the United States
and other countries.
Linux Linux is a registered trademark of Linus

Torvalds. (Linux®).
AdventNet AdventNet is a trademark of AdventNet, Inc.

EDA2530 - Operating Guide
Preliminary Information
Revision History
The guide is valid for EDA 2530 R4.21. Other product versions, with functions
not described in this guide, may be available.
Actual Version (Version B)

Editorial Revision.
Version A
First Issue.
1/1553-HSC901 003/2 Uen B 3

Contents
Contents
1 Preliminary Information 7
1.1 Conventions Used In Handbook 8
1.2 Hardware and Software Requirements 8
1.3 Application Software Installation 9
1.4 Connecting the Personal Computer to the Equipment 13
2 Operating Instructions 14
2.1 Introduction 15
2.2 Application Software Activation 16
2.3 Main Window Description 18
2.4 Main Menu 21
2.4.1 File Menu 21
2.4.1.1 Refresh Equipment View 21
2.4.1.2 Log off 21
2.4.1.3 Exit 21
2.4.2 Application Options Menu 21
2.4.3 Alarm Browsers Menu 24
2.4.3.1 Active Alarms 24
2.4.3.2 Historical Alarms 25
2.4.4 Trace 27
2.4.5 Configuration menu 27
2.4.6 Card/Port Protection 28
2.4.7 Alarms 29
2.4.7.1 Alarms and Event Notifications 29
2.4.7.2 Configuring the Traps Target Table 30
2.4.7.3 Configuring the Traps LT Table 30
2.4.7.4 Configuring the Traps EM Table 31
2.4.7.5 Input Alarms Table 32
2.4.8 SHDSL Profiles and Setup 33
2.4.9 xDSL Profiles 39
2.4.9.1 xDSL Line Profile Application 39
2.4.9.2 xDSL Alarm Profile application 43
2.4.9.3 ADSL PSD Profile application 45
2.4.9.4 VDSL PSD Profile application 49
2.4.10 Line Bonding Management 51
2.4.11 xDSL Line Activation 52
2.4.12 PSTN National Mapping 53
2.4.13 POTS/ISDN Profiles 57
2.4.14 IP and Ethernet Management 60
2.4.14.1 Browse & Configure xDSL Bridge 60
2.4.14.2 xDSL Bridge Survey 85
2.4.14.3 IP-CP Static Forwarding Database 89
2.4.14.4 IP-CP Static VLAN 91
2.4.14.5 Current Forwarding Database Surveillance 94
2.4.14.6 RSTP/MSTP Configuration 95
2.4.14.7 Ethernet Link Aggregation 102
2.4.14.8 Bridging Parameters 104
IV 1/1553-HSC901 003/2 Uen B

Contents
2.4.14.9 VLAN SubInterface Configuration 105

2.4.14.10 Management Interface Setting 106
2.4.14.11 IP Interface Configuration (Network Interface Config) 107
2.4.14.12 Static Routing Table 109
2.4.14.13 ARP Table Configuration 110
2.4.14.14 Ping Request Parameters 111
2.4.15 L3 DHCP Relay Agent Management 112
2.4.15.1 L3 DHCP Profile Management 113
2.4.15.2 L3 DHCP Server Profile Management 114
2.4.15.3 L3 DHCP VLAN Management 115
2.4.15.4 L3 DHCP Interface Management 116
2.4.16 Video Multicast Management 116
2.4.17 IP-CP Multicast Configuration 117
2.4.17.1 Multicast VLANs 117
2.4.17.2 IGMP Interfaces 119
2.4.17.3 Static Multicast 121
2.4.18 IP-CP Multicast Survey 122
2.4.18.1 Multicast Group Surveillance 124
2.4.19 Voice over IP Management 125
2.4.19.1 VoIP Global Parameters 125
2.4.19.2 VoIP DNS Servers 125
2.4.19.3 Voice over IP Inventory/Provisioning 126
2.4.20 System Info 144
2.4.21 Equipment Date and Time Configuration 145
2.4.22 SCTS - Centralized Timing Source Configuration 147
2.4.23 Connection Modules 152
2.4.24 Line Test 153
2.4.24.1 Equipment Level Configuration 153
2.4.24.2 Line Test Input Profiles 154
2.4.24.3 Line Interface Test 155
2.4.24.4 ADSL2 Diagnostic (DELT) 160
2.4.24.5 xDSL SELT 164
2.4.25 IP / Ethernet Statistics 168
2.4.26 ADSL Statistics Counters 173
2.4.27 Performance Monitoring 175
2.4.27.1 Running Performance Tool 177
2.4.27.2 Utilities 181
2.4.28 Equipment Alarm Status 182
2.4.29 Maintenance Menu 183
2.4.30 Help Menu 183
2.5 Graphical Area 184
2.5.1 Unit Creation 185
2.5.2 Unit Deletion 186
2.6 Unit Configuration 187
2.6.1 General 187
2.6.1.1 About 187
2.6.1.2 Show Actual 187
2.6.1.3 Hw/Sw Inventory 188
2.6.1.4 Refresh 188
2.6.1.5 Delete 188
2.6.1.6 Reset Board 189
1/1553-HSC901 003/2 Uen B V

Contents
2.6.2 CP-IP Unit 189

2.6.2.1 SFP Provisioning 189
2.6.2.2 CP-IP On Board Element Manager 193
2.6.2.3 Ethernet Lines 194
2.6.2.4 Frontal Ethernet Line 201
2.6.2.5 Link Aggregator Lines 203
2.6.3 ADSL Unit Configuration 205
2.6.4 VDSL Unit Configuration 212
2.6.5 SHDSL Unit Configuration 219
2.6.6 POTS Unit Configuration 225
2.6.7 ISDN Unit Configuration 230
2.6.7.1 ISDN Lines Configuration 230
2.6.7.2 ISDN Performances 235
2.7 Maintenance Functions 239
2.7.1 Display LT Software Version and User Guide 239
2.7.2 Check connection to Equipment 239
2.7.3 Displaying Hardware and Software Inventories 240
2.7.4 Equipment Software Download 241
2.7.5 Equipment Reboot 245
2.7.6 Configuration Backup/Restore 246
VI 1/1553-HSC901 003/2 Uen B

1 Preliminary Information
This Section provides the basic elements for the use of the control application.
The following topics are dealt:
• Conventions used in the Handbook;
• Hardware and Software Requirements;
• Application Software Installation;
• Connecting the Personal Computer to the Equipment.
SAFETY No particular actions are required on the equipment after a manual switch
off. The standard switch on operation restores the current configuration.
1/1553-HSC901 003/2 Uen B 7

1.1 Conventions Used In Handbook

This manual describes the control application, which allows the Operator to
interact with the equipment, to program the configuration, to check the alarms, to
activate some operations and perform the maintenance procedures.
This manual is divided in two sections.
The first session provides preliminary information about:
• Control application structure;
• Hardware and Software requirements;
• Installation of the Software;
• Connection of the computer with the equipment.
The second section “Operating Instructions” describes how to run the control
application, the meaning of the program’s main window and the use of the
relevant menus. These descriptions may refer to other parts of this manual, or to
other manuals that will supply the detailed description of the equipment's
functionality.
1.2 Hardware and Software Requirements

This Chapter describes the basic requirements of the personal computer,
Operating System and the connection cables needed to run and use the Local
Controller application.
Hardware Requirements
The basic requirements for the personal computer are:
• Microprocessor: Intel Pentium III - 750MHz, or higher;
• RAM Memory: 512MByte recommended or more;
• Hard disk: 200Mbyte of free space on disk, required for installation;
• Graphic interface: SVGA supporting at least 1024x768 resolution with at
least 256 colors;
• Mouse: Two or three buttons;
• External interface: Ethernet 10 Base T;
• Display:15” or more for desktop PC, 14'' display or more for portable PC;
• CD-ROM Driver.
NOTICE Electrical Safety: equipment must be compliant with EN60950.
Software Requirements
The minimum software requirements are:
• Microsoft Windows 2000®, Windows XP® and Windows Vista®;
• Java® 2 Runtime Environment standard Edition v1.5 (JRE 1.4.0) or
higher;
• ITCL/ITK (Ericsson distribution);
• Adobe Reader 6.0 or higher.
8 1/1553-HSC901 003/2 Uen B

1.3 Application Software Installation

This chapter provides information about the software set-up, which includes the
Local Craft Terminal, the ADD-ON Package, Java, Itcl/Tk and Adobe Reader
software packages installation. All these software packages are supplied on a
CD ROM. CD ROMs are product release specific and may be customer specific.
If not otherwise specified, the term "Windows Operating System" will be used to
indicate the Microsoft Windows 2000®, Windows XP® and Windows Vista®
Operating Systems.
NOTICE All the programs (Java, ITCL, Adobe Reader and Local Terminal) must be
installed from a user with Administrator privileges.
Before installing the Local Terminal software package, any previous version of
this software must be removed. After the removal, the personal computer has to
be restarted, in order to update the Windows Operating System registry.
Before starting the set-up installation, it is suggested to close any other running
application.
Java Installation Procedure
Java Runtime Environment provided with the release of Local Terminal software,
can be also downloaded from the http://java.sun.com Internet site. In this handbook,
there is a brief explanation of the Java Runtime Environment set-up procedure,
supplying the minimum information needed in order to install the program. For a
detailed description and troubleshooting procedures, please refer to the product's
official documentation, available from the indicated Internet site. The following
procedure describes the installation of the software delivered with the
equipment.
Inside most of the windows that will be described, the BACK pushbutton will be
used to return to the previous window, and the CANCEL to abort the set-up.
1. Start the JRE software installation from the CD ROM.
2. The welcome screen is then shown, carefully read its content and press YES.
3. The subsequent window allows the selection of the folder where to store the
Java software. Press NEXT to continue.
4. It is suggested to confirm the default selection of the following windows by
clicking the NEXT button, to continue the set-up without changing any
parameter.
5. The software download to the PC will start. Successfully completion of the
download process is indicated on the screen, stating that the Java download is
completed. Press the FINISH button to terminate the operation.
6. It is suggested to delete the installation file from the desktop.
NOTICE DE-INSTALLATION NOTES

To remove the software package installed by this set-up procedure, use the
"Add/Remove Program" utilities from the Windows Control Panel.
ITCL Installation Procedure

The installation procedure can be performed using the installation software
provided inside the software CD shipped with the equipment.
1/1553-HSC901 003/2 Uen B 9

Also in this case, from most of the windows that will be described, the BACK
pushbutton will be used to return to the previous window, and the CANCEL to
abort the set-up.
1. Locate the Setup.exe program contained by the ITCL inside the software CD.
2. Select the Setup.exe file and then press the OPEN button.
3. The welcome screen is then shown, carefully read its content and press NEXT.
4. Subsequent window allows the selection of the folder containing the ITCL software.
This software package MUST be installed under the default directory c:\itcl3.3.
5. The subsequent window will summarize the previous selections. If all the data
are correct, press NEXT to start the file installation.

Adobe Reader Installation Procedure

The Adobe Reader software provided with the Local Terminal software can be
also downloaded from the http://www.adobe.com Internet site. In this handbook,
there is a brief explanation of the Adobe Reader software set-up procedure,
supplying the minimum information needed in order to install the program. For
detailed description and troubleshooting procedures, please refer to the official
documentation for the product, available in the indicated Internet site.
The following procedure, refers to the installation performed from the software
delivered with the equipment and may slightly differ when using a newer or
different version of the program.
During the installation, from most of the windows that will be described, the
BACK pushbutton will be used to return to the previous window, and the
CANCEL to abort the set-up.
1. Start the Adobe Reader software installation from the CD ROM.
2. The welcome screen is then shown, carefully read its content and press NEXT.
3. The subsequent window allows the selection of the folder where to insert the
Adobe Reader software. Accept the default value and press NEXT to continue.
4. It is suggested to confirm the default selection of the following windows by clicking
the NEXT button, to continue the set-up without changing any parameter.
are correct, press NEXT to start file installation.
6. The software download to the PC will start. Successfully completion of the
download process is indicated on the screen, stating that the Adobe Reader
download is completed. Press the FINISH button to terminate the operation.
7. It is suggested to delete the installation file from the desktop.

Local Terminal Installation Procedure

The installation procedure can be performed using the installation software,
provided inside the software CD delivered with the equipment.
10 1/1553-HSC901 003/2 Uen B

1. Locate the Setup.exe program contained inside the software CD.

2. Select the Setup.exe file and press the OPEN button.
3. The welcome screen is then shown, carefully read its contents and press NEXT.
4. The subsequent window allows the selection of the folder that will contain the
mv36blt software. We suggest performing the installation of the software
package under the default directory c:\MV36BLT. Press NEXT to continue.
5. The next window box, allows the selection of the folder where the Local
Terminal software will be installed. User is allowed to choose a new or an
already existing folder. After the selection, press NEXT button to continue.
are correct, press NEXT to start the installation.
7. If the installation will be successfully terminated, the “Set-Up Complete” box will
be displayed. Press FINISH button to exit set-up.
8. One shortcut icon to the Local Terminal software will be available on the
desktop. The procedure adds the program folder (selected during the set-up)
under the Programs group folder. This folder contains the shortcut icon
necessary to start the Local Terminal software. In the same folder, the Port
Server Program will also be available.

"Add/Remove Program" utilities in the Window Control Panel.
SNMP Trap_LCT for Windows XP

It is suggested to verify the below procedure in order to ensure the proper
execution of the received trap in the Local Craft Terminal installed in a Windows
XP® Operating Systems.
1. Launch the start menu, by clicking on the taskbar or pressing the Start button
2. According to the menu configured (classic start menu or start menu) follow the
procedure:
Classic Start menu:
a) click on the taskbar by means of the right key of the mouse;
b) press Properties from the floating menu;
c) select Start Menu folder;
d) press Customize button;
e) check the Display Administrative Tools item.
Start menu:
a) click on the taskbar by means of the right key of the mouse;
b) press Properties from the floating menu;
c) select Start Menu folder;
d) press Customize button;
e) select Advanced folder;
f) check the Display on the all Programs menu in the System
Administrative tools section.
3. From the menu just enabled launch "Programs->Administrative Tools-
>Services" and in the SNMP Trap service make a Stop command and set
"manual.
1/1553-HSC901 003/2 Uen B 11

ADD-ON Installation Procedure

The installation procedure can be performed using the installation software,
provided inside the software CD delivered with the equipment.
NOTICE The Add-On Package contains a few plug-in applications used by LCT to
fully manage Equipments. It is mandatory to install the Add-On package for
this Local Craft Terminal version, to support the IP/Ethernet Management
features and other functionalities.
1. Locate the Setup.exe program contained by the LCT directory labeled as

"ADDONPKG" inside the software CD.
2. Select the Setup.exe file and press the OPEN button.
3. On return screen, push the OK button.
4. The welcome screen is then shown, carefully read its contents and press NEXT.
5. A window allows the Operator to choice EasyOn Lct_AddOn_BMS, the
component to install.
6. Press NEXT to continue.
7. The subsequent window allows the selection of the folder that will contain the
ADD-ON software. We suggest installing the software package under the
default directory c:\usr\local\lib. Press NEXT to continue.
8. If the installation will be successfully terminated, the “Set-Up Complete” box will
be displayed. Press FINISH button to exit the set-up.
9. Restart the system to apply the modifications.

To remove the ADD-ON software package installed by this setup procedure,
use the "Add/Remove Program" utility in the Control Panel and select the
"BMS" software.
12 1/1553-HSC901 003/2 Uen B

1.4 Connecting the Personal Computer to the Equipment

This Chapter describes how to connect locally the Personal Computer to the
Equipment. The Personal Computer where the Local Terminal software is
installed could be connected to the equipment using an Ethernet connection
over a LAN.
How to connect the PC to the Equipment
1. Connect the PC to the LAN using an Ethernet Hub, by means of its Ethernet
interface (usually 10BaseT) and a straight twisted pair cable mated with RJ45
connectors.
2. Connect the equipment Ethernet interface to the LAN through an Ethernet Hub,
by means of a straight twisted pair Ethernet cable mated with RJ45 connectors.
3. Configure the Personal Computer IP address and the Net mask value, in order
the have them in the same IP network.
The Personal Computer is now connected to the Equipment, and the Operator,
after the login is able to use the Equipment. If an Ethernet Hub is not available, it
is possible to connect the PC directly to the equipment Ethernet interface
through a cross-over (MDI-X) Ethernet cable.
1/1553-HSC901 003/2 Uen B 13

Operating Instructions
2 Operating Instructions
This Section gives detailed instructions on how to use the Local Craft Terminal
(LCT) application. The following topics are dealt:
• Introduction;
• Application Software Activation;
• Main Window Description;
• Main Menu;
• Graphical Area;
• Unit Configuration;
• Maintenance Functions.
14 1/1553-HSC901 003/2 Uen B

2.1 Introduction
The control software application is the operator’s interface towards the
equipment and permits interaction with the firmware installed on the units.
This section gives step-by-step operating instructions to run the control
application, understanding the meaning of the elements present in the main and
in the additional windows and using the various menu items.
1/1553-HSC901 003/2 Uen B 15

2.2 Application Software Activation

In the Windows Start->Programs menu-> AXH-EDA Local Terminal X.y.z start
menu bar (where X.y.z indicates the number of AXH-EDA software release), the
following menus are present:
• AXH-EDA Local Terminal. It is used to activate the local operator;
• Backup & Restore procedure. It is used to perform a backup and restore
of the equipment configuration data, using the TFTP server process;
• Custom setup. Not used;
• Port server. It is used to activate the port server, which is needed to
manage the equipment;
• TFTP server. It is used to activate the TFTP server.
Before running the control application software, the Operator must verify:
• Ethernet interfaces fitted in the equipment must be properly connected;
• The Personal Computer must be connected to the equipment;
• The Windows O.S. must be running;
• The "Port Server" program must be running. When it is running, a DOS
window is present in the task bar of the Windows O.S. By default the
"Port Server" program is started automatically when the Windows O.S. is
running.
The control application software may be launched in two ways:
• By clicking on AXH-EDA Local Terminal icon on Windows O.S. desktop;
• By selecting Start->Programs menu->AXH-EDA Local Terminal item,
from the Windows O.S task bar.
The following window will be displayed.
16 1/1553-HSC901 003/2 Uen B

1. Insert the Equipment Address (IP address) or the Equipment Name in the
relevant text field. By clicking on the scroll bar buttons, the history of the last
eight inserted IP address (or Equipment names) will appear.
2. Click on the Logon button, or hit the return key while the input cursor is over the
Equipment Address field (or Equipment name), to start the working session.
3. Check the Connect in READ ONLY mode box to entry in read only mode.
4. In order to change the SNMP parameters, press the arrow on the right.
The following window is shown:
5. After these operations, the sub rack structure will be displayed.

Detailed instructions about how to use the control application are given in the
next chapter.
1/1553-HSC901 003/2 Uen B 17

2.3 Main Window Description

When the control application is active, the main window is always displayed.
b
c
d
It can be divided in the following functional parts:

a. Title Bar;
b. Main Menu Bar;
c. Error Messages Display;
d. Toolbar;
e. Equipment parameters;
f. Graphical Area;
g. Menu Display.
Secondary windows can appear above the main window, to request the
insertion of data or to display additional information.
Title Bar (a)
The Title Bar is a standard element inside the windows that contains the window
title with the buttons to minimize and maximize it. Using the Windows O.S., the
crossed button could be used to exit the program. However the correct method
to halt the AXH-EDA Local Terminal software is by selecting File -> Exit from
the main menu bar. For additional details about the Title Bar, consult the
Windows O.S. documentation.
Main Menu Bar (b)
This bar contains the main menu items of the control application. Each item can
be expanded by opening the relevant pull down menu, which allows displaying
the secondary items. The meaning of the selected item from the pull down menu
is shown in the Menu Display area. To expand the menu, click once over the
relevant item (e.g. File, Add Options…).
18 1/1553-HSC901 003/2 Uen B

The items of the main menu bar, and the pertinent secondary items, are
described in a dedicated Chapter within this section. The items displayed with
light grey color cannot be selected. This color indicates that the item is not
applicable in the selected context.
Error Messages Display (c)
This part of the window is used by the program to display the last error message
occurred. Using the C button, located on the left side, it is possible to cancel the
displayed message.
Toolbar (d)
The toolbar contains shortcut buttons for the direct access to the most common
functions. When the cursor is positioned above the buttons, a short help string
will be displayed. Some buttons are only shortcut of pop-up menu options, while
some other buttons are available only from the toolbar.
Protection button: it displays access to the protection management facility.
Synchronization button: this button is used to manage the equipment

synchronization.
Alarm Browser button: it gives access to the Alarm table management facility.
Equipment Parameters (e)

This part of the window is used to display the equipment IP Address and the
equipment's name.
By clicking on the string with the right button of the mouse, it is possible to
display the equipment properties.
1/1553-HSC901 003/2 Uen B 19

Graphical Area Section (f)

The main window displays a synoptic view of the equipment. In this area, the
user is allowed to perform all the operations related to equipment configuration
and maintenance. The area is composed of different slots that correspond to the
physical unit positions. When a unit is configured, it is displayed with its own
name on the front panel, while a not equipped unit is displayed as an empty slot.
Menu Display (g)
This Menu shows a brief description of the derived item, when the user selects a
menu from the main menu and move the cursor above a secondary item.
20 1/1553-HSC901 003/2 Uen B

2.4 Main Menu

2.4.1 File Menu
This paragraph describes the File item, and the relevant secondary items,
selectable from the main menu.
The File menu is used for:
• Update the equipment view (Refresh Equipment View);
• Close to the control application active session (Logoff);
• Exit and Close the control application.
2.4.1.1 Refresh Equipment View
PATH: (File Æ Refresh Equipment View)

This command interrogates and performs a new scan of the equipment, in order
to realign the control application to the physical status of the equipment. To be
used only if the software could be unaligned with the equipment.
2.4.1.2 Log off
PATH: (File Æ Logoff)

It closes current session of the NE. When this item is selected, a confirmation
window will be displayed. After confirmation, the Login window appears.
2.4.1.3 Exit
PATH: (File Æ Exit)

By clicking on the Exit item from the File menu, the Local Craft Terminal will be
closed.
2.4.2 Application Options Menu

This paragraph describes the use of the Application Options item, and
relevant secondary items, selectable from the main menu.
General Application Configuration
PATH: (App Options Æ General App Conf)
This option is used to change the software application. The function is also
available through the shortcut button from the Logon window, by clicking using
the right button of the mouse.
Then select the menu Application Conf to display the relevant window.
1/1553-HSC901 003/2 Uen B 21

By this command it is possible to:

• Modify the setting relevant to the message windows;
• Display and modify IP parameters of the control application software;
• Configure the timeout for the backup / restore of the equipment.
Modify the settings relevant to message windows

1. Select the Configuration folder.
2. Enable the displaying of messages as Pop up windows, by selecting Pop up
message windows check box. When this option is disabled, the messages are
displayed only in the message field of the main window.
Display and modify the IP parameters

2. Check the radio button labeled: Automatically get Host Name and IP
Address. This is the default option. During the control application boot up, the
program reads the PC address and sends it to the Equipment. The Equipment
needs the IP address in order to communicate with the control application.
3. When it is necessary to manually specify the IP address and the name of the
PC, check the radio button named Specify Host Name and IP address and
change the data in the fields: Host IP Addr and Host Name. The address
configured in these fields is set-up during the installation procedure.
This configuration is needed only when PC has multiple IP addresses assigned.
Modify the timeout for the Backup & Restore operations

22 1/1553-HSC901 003/2 Uen B

2. Set the Backup Timeout. This parameter is used in the Backup procedure that
is run by the command: Start Æ Programs- Æ AXH-EDA Local Terminal Æ
Backup & Restore procedure. Configure the timeout for the phase of creation
of the DBM backup file in the equipment's memory. This value, in minutes, is not
comprehensive of the time of transfer of the backup file on the user's disk.
Default value is 20 minutes. Increase this value if the operation of backup's
equipment fails.
3. Set the Restore Timeout. This parameter is used in the Restore procedure that
it is run by the command Start->Programs-> AXH-EDA Local Terminal->
Backup & Restore procedure. Configure the timeout for the restore of the
DBM backup file on the equipment. This value, in minutes, is comprehensive of
the time of transfer of the backup file from the user's disk to equipment's
memory, but it is not comprehensive of the time of the reboot of the equipment.
Default value is 40 minutes. Increase this value if the operation of restore's
equipment fails.
4. Press SAVE button to store the new configuration, LOAD to refresh the window
and DONE to close it.
Some features in the SNMP
ALERT We suggest NOT modifying these parameters.
1. The Snmp folder displays this window:
2. The MA SNMP port text field is used for the Management Application
3. The SNMP Time Out (sec.) value defines in seconds, the maximum waiting
time for the Equipment answer messages.
4. The SNMP Retry stated the number of tentative that may be performed within
the SNMP Time Out.
1/1553-HSC901 003/2 Uen B 23

Change the LED Colors configuration

By means the LED Colors configuration folder it is possible to associate a
specific color (red, orange, yellow, blue and green) to an alarm in the Main
Equipment Window.
1. Select the LED Colors folder in order to display this window.
2. Choose by means of the relevant scroll list the color to be associated to an alarm.
4. Press File->Refresh Equipment view and the alarm view of the equipment will
be automatically updated.
2.4.3 Alarm Browsers Menu

This paragraph describes the Alarms Browser item and the relevant secondary
items. Using this item from the main menu, it is possible to display the active
and historical alarms windows.
2.4.3.1 Active Alarms
PATH: (Alarm Browser -> Active Alarms)

As alternative option, Operator can select the relevant shortcut button from Toolbar.
The Alarm table and Last Alarm Received windows will be displayed.
24 1/1553-HSC901 003/2 Uen B

The last received item is emphasized using a different background color and it is
positioned at the bottom of the list. Using the scroll bar on the right, it is possible
to scroll the window and display all the lines.
The Last Alarm Received window, displays only the most recent alarm or
event, received from the equipment. The above-mentioned windows provide
information about.
• Alarm type: It may be Alarm ON or Alarm OFF;
• Alarm severity;
• Alarm cause;
• Physical position of the alarm source and event parameters;
• Alarm source Identification;
• Alarm date;
• Alarm time.
Enabling alarm reception from all the units:

1. Select Receive from all cards (default).
Enabling alarm reception from a specific unit only:

1. Check the box Receive from specific card.
2. Press Apply Setting… button to confirm the choice.
In Current filter field the choice about the reception of the alarm is shown.
3. Use the Refresh button, to update the Alarm table window.
How to save the alarms log

1. Click on the button Save to File to copy currently displayed alarms info to a text
file on disk (may be useful to analyze alarms later).
2.4.3.2 Historical Alarms
PATH: (Alarms Browser -> Historical Alarms)

This tool is used to display the historical alarms/events traps in the Equipment.
1/1553-HSC901 003/2 Uen B 25

In the following the meaning of the columns:

• Physical Location: the slot/port where the trap arises.
• Data and Time: the data and time when the alarm occurred.
• Notification ID: name of the alarm trap.
• Severity: it specifies the level of severity of the alarm (critical, major,
minor, warning or cleared).
• Probable Cause: it specifies the probable cause of the alarm.
According to the operation to perform it is possible to choose among these
buttons:
• Start: it runs the trap collection.
• Pause: it suspends the trap collection.
• Stop: it terminates the trap collection.
• Details >>: it opens a Property Details window with further information
about the alarm:
26 1/1553-HSC901 003/2 Uen B

2.4.4 Trace
This item is reserved for factory use only.
2.4.5 Configuration menu

This paragraph describes the Configuration item and the relevant secondary
items. The items available are:
• Card/Port Protection: it manages the Common Part Unit protection;
• Alarms: it manages the consequent actions related to equipment
alarm(s) detection;
• SHDSL Profiles and Setup: it manages all SHDSL profiles;
• xDSL Profiles: it manages all ADSL/VDSL profiles;
• xDSL Line Bonding Configuration: it manages the aggregation by
bonding more physical lines into one channel;
• xDSL Line Activation: it manages the activation/deactivation of the
xDSL lines per slot basis (all subrack at the same time is possible);
• PSTN National Mapping: it is used to manage the National Mapping
configuration, tuning the parameters, in order to match the specific
national mapping;
• POTS/ISDN Profiles: It manages profiles to assign to POTS/ISDN lines;
• IP / Ethernet Management: it manages IP / Ethernet Management,
Bridging, IP and Ethernet Features;
• L3 DHCP Relay Agent Management: it allows configuring L3 DHCP
Relay Agent interfaces, servers, VLANs;
• Video/Multicast Management: it manages the Video/Multicast features;
• VoIP Management: it manages the Voice Over IP Features;
• System Info: it manages some information relevant to the system;
• Equipment Date/Time: it manages the equipment Date/Time for the
NTP service;
• SCTS Service: this option is used to display the synchronization
sources by means of the SCTS (Simplified Centralized Timing Source);
• Connection Modules: it allows to manage and configure the connection
modules in the equipment;
• Line Test: it allows to configure/execute Line tests (e.g. SELT, DELT
etc) over the subscriber interfaces (both narrowband and broadband);
• IP/Ethernet Statistics: it displays IP/Ethernet Statistics counters;
• ADSL Statistics Counters: it displays the ADSL Statistics counters;
• Performance Monitoring: it allows the performance management in the
equipment;
• Equipment Alarm Status: it displays status of the equipment alarms.
1/1553-HSC901 003/2 Uen B 27

2.4.6 Card/Port Protection

PATH: (Configuration -> Card/Port Protection)
The function is also available through the shortcut button indicated below:
After selecting this option, the following window will be displayed:
This window is used to manage the card protection (1:1 scheme) for the
Common Part Unit (CP-IP). For the line protection (RSTP, LAG etc) please
refer to the relevant paragraphs.
List of PROTECTING Cards area shows if the protection unit is available
indicating the Subrack, Slot and Protecting Card. If the protection unit is
available it is displayed as in the window above.
Protection Group CARD Entry area shows administrative and operational
status of the protection scheme. AdminStatus is always enabled while
OperStatus could be enabled or disabled. If it is disabled, protection scheme is
not working and the reason why it is displayed in CARD Protection Units area.
CARD Protection Units area shows the status of the protected card and the
protecting one via the following parameters:
• Subrack: it identifies the subrack number (always 1)
• Slot: it is the position of the unit inside the subrack (1 or 22)
• Role: it is the role of the protection unit (protected, unit is configured as
a worker unit; protecting, unit is configured as backup or standby unit).
• Admin: indicates administrative status of the unit. It is always enabled.
• Protection Status: indicates the state of the unit. The field can assume
different values in depending on the unit's role:
28 1/1553-HSC901 003/2 Uen B

- Alarm. A defect condition has been detected (unit internal problem);

- switchedAutomatically. The unit traffic is switched to the other unit
after an automatic switch command;
- switchedManually. The unit traffic is switched to the other unit after a
manual switch command;
- AutomaticSwitchPending. The unit has a pending automatic request
of traffic switch to the other unit;
- unitUnavailable. The unit is unavailable. This could be caused by unit
problems or when the unit has been extracted from the subrack;
- notActive. The module is ready and no traffic switch is pending.
• Summary: This label summarizes the information about the protected
unit status.
NOTICE The Activate and Deactivate button of this window are not used.
Press the Refresh button to update the information of this window and Close to
exit from the window.
How to perform a Manual Switch:

1. From the CARD Protection Units folder select the protected unit to be
switched.
2. Press the Manual Switch button to switch the traffic to the protecting unit.
To switch back the protection manually:
3. From the CARD Protection Units folder, select the protecting unit involved in
the switch.
4. Press the Manual Release button in order to switch back the traffic to the
protected unit.
2.4.7 Alarms
PATH: (Configuration -> Alarms)
This item contains some services to manage the consequent actions related to
Equipment alarm(s) and event(s) detection.
2.4.7.1 Alarms and Event Notifications
PATH: (Configuration -> Alarms ->Trap Target table or Trap LT table/Trap EM table)
The Operator can configure the messages notification towards the Managers,
towards the Local Terminal and towards the Element Manager using different
kinds of tables:
• Trap Target table: it is used to enable or disable the alarm and event
traps reporting towards the Manager.
• Trap LT table: it is used to enable or disable the alarm and event
reporting towards the Local Terminal.
• Trap EM table: it is used to enable or disable the alarm and event
reporting towards the Element Manager.
1/1553-HSC901 003/2 Uen B 29

2.4.7.2 Configuring the Traps Target Table
PATH: (Configuration -> Alarms ->Trap Target table)

This item is used to manage the transmission of the Alarms and Events traps
toward the Manager.
There are three sections in the table:

• The section called "Entry Name Identifier” is used to add a name of a
Manager (AXH-EDA Local Terminal or Element Manager) to a list saved
on the Equipment. When the Name Identifier of a Manager is inside the
list, it will be considered by the equipment as a destination where to
send the notifications (event or alarms).
• The section called "Manager IP address" is used to add the IP address
of the Manager identified as alarm destination.
• The section called "UDP Port Number" is used to add the UDP Port
Number.
Insert a new entry in the Traps Target table:

1. Insert an alpha-numeric string in the Entry Name Identifier field.
2. Insert an IP address in the Manager IP address field.
3. Insert a numeric string in the UDP Port Number field.
4. Use the Add button, to insert additional entry.
5. Use the Refresh button to update the window.
Delete an entry in the Traps Target table:

1. Select an existing entry in the table.
2. Use the Delete button to delete the entry from the table.
2.4.7.3 Configuring the Traps LT Table
PATH: (Configuration -> Alarms ->Trap LT table)

This item is used to manage the transmission of the Equipment Alarms and
Events towards the AXH-EDA Local Terminal.
30 1/1553-HSC901 003/2 Uen B

The section on the left of the table is used to add or remove IP addresses to a
list saved on the Equipment. When the IP address of an AXH-EDA Local
Terminal is inside the list, it will be considered by the NE as destinations where
to send the notifications (events or alarms).
The section on the middle of the table is used to display the equipment IP
address identified as alarm source. The section on the right of the table is used
to globally enable or disable the sending of alarm or event notifications.
2.4.7.4 Configuring the Traps EM Table
PATH: (Configuration -> Alarms ->Trap EM table)

This item is used to manage the transmission of the Equipment Alarms and
Events towards the Element Manager.
The section on the left of the table is used to add or remove IP addresses to a
list saved on the Equipment. When the IP address of an Element Manager is
inside the list, it will be considered by the NE as destinations where to send the
notifications (event or alarms).
The section on the middle of the table is used to display the equipment IP
address as alarm source. The section on the right of the table is used to globally
enable or disable the sending of alarm or event notifications.
1/1553-HSC901 003/2 Uen B 31

Configuring the Alarm/Event reporting (for Trap LT/EM tables):

1. Select the alarm/event destination, using the relevant check boxes.
2. Use Apply to confirm the settings.
3. Use the Add button, to insert additional address of LT (in the LT table) or EM (in
the EM table).
4. Use the Del button to delete an address from the table.
5. Use the Close button to close the window.
Usually, it is not necessary to add and remove the IP addresses from the list
shown inside the window, since both the AXH-EDA Local Terminal and the EM,
manage the contents automatically. Manual operation may be required only for
test or debugging purpose.
2.4.7.5 Input Alarms Table
PATH: (Configuration -> Alarms -> Input Alarms Table)

This window allows configuring the 31 Input Ground Contacts. According to the
hardware the Input Ground Contacts can be available or not in the Equipment.
For each available Input Ground Contact (its identifier is displayed in the read-
only column “Input Contact Number”) it is possible to associate the following
operations:
• insert a short description in the “Associated Alarm Description” column;
• enable or disable the relevant alarm in the column “Enabling Status”; the
possible values are disable, enableHigh, enableLow.
If the Input Contact Number is displayed in grey color, it is not available on the
Equipment.
The Read from FILE button allows importing a new Input Ground Contacts
configuration from a file, instead of entering it manually from keyboard. The file
must be an ASCII text, one line for each input contact and each line must have
the following format: <input contact number>#<status>#<description>
example: 8#enableHigh#cabinet High temperature
Use the Apply button to confirm the choices, Refresh button to update the
window and Close button to exit from the window.
32 1/1553-HSC901 003/2 Uen B

2.4.8 SHDSL Profiles and Setup

PATH: (Configuration -> SHDSL Profiles and Setup)
This tool is used to configure all the SHDSL profiles. To simplify the task of
configuring lines, different profiles can be defined and assigned to one or more
lines instead of configuring each line with all parameters. The tool is divided in
different application, and it allows the network operator to create, delete, and
modify SHDSL Line Profiles. The tool is composed by the following
applications, as shown in the figure below:
• Conf Profiles;
• Alarm Profiles;
• Stack Profiles;
• Bonding.
Each application is an all-in-one editor/browser/writer tool that may have one or

more folders. Each folder contains an editable spreadsheet-like table for a
consistent set of parameters. The data displayed in each row of the subsequent
tables are always related to the equipment. Some fields may be of read-only
type: such fields are displayed when reading from equipment but not used when
configuring this service on it.
Conf Profiles
This application supports the definition of configuration profiles for SHDSL lines.
Each entry corresponds to a single configuration profiles. Each profile contains a set
of configuration parameters. The fields that you will find in this application are:
• Ne Name: IP Address of the equipment.
• Profile Name: name of the SHDSL line profile. It must be an
alphanumeric string with a maximum of 32 chars.
1/1553-HSC901 003/2 Uen B 33

• Wire Interface: this field defines if the SHDSL line profile is composed
by two, four, six or eight wires.
• Min Line Rate bps (0..4294967295): this field configures the minimum
transmission rate for the associated SHDSL Line in bits-per-second (bps).
• Max Line Rate bps (0..4294967295): this field configures the maximum
transmission rate for the associated SHDSL Line in bits-per-second (bps).
• PSD Type: this read-only field displays the use of the PSD (Power Spectral
Density) Mask for the associated SHDSL Line.
• Tx Mode this read-only field displays regional setting.
• Remote Manage Enabling: this read-only field displays the possibility to
have the support for remote management of the units in a SHDSL line
from STU-R.
• Power Feeding: this read-only field displays the power feeding present in
the line.
• DownstCurrCond SNRMargin(dB): this field specifies the downstream
current condition target SNR margin for a SHDSL line. SNR margin is
the difference between the desired SNR and the actual SNR. Possible
values are in the range from -10 to 21.
• DownstWorstCase SNRMargin(dB): this field represents the SNR
margin between the desired SNR and the actual one in downstream
direction in worst condition. Possible values are in the range from -10 to 21.
• UpstCurrCond SNRMargin (dB): this field specifies the upstream
current condition target SNR margin for a SHDSL line. SNR margin is
the difference between the desired SNR and the actual SNR. Possible
• UpstWorstCase SNRMargin (dB): this field specifies the upstream
worst-case target SNR margin for a SHDSL line. SNR margin is the
difference between the desired SNR and the actual SNR. Possible
• Used SNR Target Margins: this field indicates whether a target SNR
margin is enabled or disabled. This field can assume one or more of the
following values:
currCondDown: current condition downstream target SNR margin enabled.
worstCaseDown: worst case downstream target SNR margin enabled.
currCondUp: current condition upstream target SNR margin enabled.
worstCaseUp: worst case upstream target SNR margin enabled.
In order to set the value double click in the field, the window Used Target
Margins will be displayed in which you will be able to check or to uncheck
the single values.
• Reference Clock: this field represents the reference clock used by the
STU-C interface. The values are the following:
localClk: Mode-1 per G991.2.
networkClk: Mode-2 per G991.2.
dataOrNetworkClk: Mode-3 per G991.2.
34 1/1553-HSC901 003/2 Uen B

• Line Probe Enabling: this read-only field displays if the interface performs
line probing to find the best line rate.
• Date & Time: Date & Time when the Command is launched. This is
read-only field.
• Ip Address: IP Address that launches the command. This is read-only field.
• Command: possible commands are:
- Create: it creates a new configuration profile for SHDSL lines on the
equipment.
- Modify: it modifies an existing configuration profile for SHDSL lines on the
equipment
- Delete: it deletes an existing configuration profile.
- Skip: it skips the current line and it does not execute any commands on the
equipment.
• Result: this field displays the result of the command that can be OK or
ERROR. It is read-only field
• Error Message: Error description, the error type. This is read-only field.
• Annotations: it is used to write some note about the operation. This is
read-only field.
Alarm Profiles
This application supports the definition of alarm configuration profiles for SHDSL
lines. Each individual row in the table defines a single alarm profile that it is
identified by the field "Profile Name". The configuration parameters in a profile
are applied to those lines referencing that profile. The parameters that you will
find in this application are:
• Profile Name (max 32 chars): name of the SHDSL alarm profile.
It must be an alphanumeric string with a maximum of 32 chars.
• LoopAttenuation (dB -127..128): this field represents the threshold
used to rise up an alarm in case of loop attenuation worst than this
threshold.
• SNR Margin (dB, -127..128): this field represents the threshold used to
rise up an alarm in case of SNR Margin worst than this threshold.
• ES Thresh. (secs, 0..900): this field represents the minimum time
required to rise up an alarm in case of Errored Seconds condition.
• SES Thresh. (secs, 0..900): this field represents the minimum time
required to rise up an alarm in case of Severely Errored Seconds
condition.
• CRC Anomalies: this field configures the threshold for the number of
CRC anomalies.
• LOSWS Thresh. (secs, 0..900): this field represents the minimum time
required to rise up an alarm in case of Loss of Synchronization Word
condition.
• UAS Threshold (secs, 0..900): this field represents the minimum time
required to rise up an alarm in case of Unavailable Seconds condition.
1/1553-HSC901 003/2 Uen B 35

read-only field.
Create: it creates a new configuration profile for SHDSL lines on the
equipment
Modify: it modifies an existing configuration profile for SHDSL lines on
the equipment
Delete: it deletes an existing configuration profile
Skip: it skips the current line and it does not execute any commands on the
equipment
• Error Message: Error description, the error type. This is read-only field.
read-only field.
Stack Profiles
This application manages the protocol stack profiles for SHDSL line.
Each individual row in the table defines a protocol stack profile that it is identified
by the field "Profile Name". Each defined protocol is intended to be associated to
one or more lines by a dedicated application, other than this one.
The parameters that you will find in this application are:
• Profile Name: Name of the profile; it must an alphanumeric string.
• Profile Service: this field defines the SHDSL working method and possible
values are the following: ipdslamAtmShdsl, ipdslamEthernetShdsl.
• Profile E1: this field is grey colored because it is not used.
• SHDSL TC layer: this field defines the Transmission Convergence layer
over SHDSL frame. This must be configured congruently with the protocol
stack profile service. Possible values are the following: atmByteAligned and
efm6465.
• ATM TC alfa: this field is grey colored because it is not used.
• ATM TC beta: this field is grey colored because it is not used.
• ATM TC Cell Scrambling: this field is grey colored because it is not used.
• ATM TC HEC correction: this field is grey colored because it is not used.
read-only field.
- create: it creates a new configuration profile for SHDSL lines on the
equipment.
- modify: it modifies an existing configuration profile for SHDSL lines on the
equipment.
- delete: it deletes an existing configuration profile.
36 1/1553-HSC901 003/2 Uen B

- skip: it skips the current line and it does not execute any commands on the
equipment.
• Error Message: Error description, the type of the error. This is read-only field.
read-only field.
Bonding
This application allows aggregating a higher bandwidth for an end user by
bonding more physical lines together into one channel. The xDSL line
configuration must be done per line and the traffic configuration must be done
on the main line only. The bonding specific parameters apply to the line index
(User Port <subrack>/<slot>/line) for the line, that is denoted main line within
specific group. The individual line configuration is independent from the bonding
service configuration.
The GUI is an all-in-one editor/browser/writer tool, with more than one folder.
Each tabbed card contains an editable spreadsheet-like table for a consistent
set of parameters. The tables are strictly related to one another, and they can be
seen as sections of a one big table. Each table's row has its continuation in the
tables located at its right or left hand. The data displayed in each row of the
subsequent tables are always related to the equipment referred to. Some fields
may be of read-only type: such fields are displayed when reading from
equipment but not used when configuring this service on it.
The application is composed by the following folders:
• xDSL Bonding Configuration;
• IMA-specific Bonding;
• Application Control.
xDSL Bonding Configuration folder:
• NE Name: IP Address of the equipment.
• Card Type: this field shows the unit type. This is read-only field.
• User Port (sh/sl/ln): this field defines which user port (indicated with
subrack/slot/line notation) is included in the bonding configuration.
• Group Admin Status: this field defines the desired status of the
bonding group. The possible values are: up and down.
• Max Ds Rate bps: this field defines the maximum downstream rate for
the bonding group. This field is not available yet, for future use.
• Min Ds Rate bps: this field defines the minimum downstream rate for
the bonding group. This field is not available yet, for future use.
• Max Us Rate bps this field defines the maximum upstream rate for the
bonding group. This field is not available yet, for future use.
• Min Us Rate bps: this field defines the minimum upstream rate for the
bonding group. This field is not available yet, for future use.
• Atuc Qual. Threshold bps: this field specifies the line quality alarm
threshold for the bonding group. This field is not available yet, for future use.
1/1553-HSC901 003/2 Uen B 37

• Atur Qual. Threshold bps: this field specifies the line quality alarm
threshold for the bonding group. This field is not available yet, for future use.
• Atur No Wait: this field controls bonding mode behavior. Possible
values are: true and false. If set to true allows the bonding group to be
active as soon as least on line is in Showtime. This field is not available
yet, for future use.
• Group Members: this field indicates which lines should be bonded in
this bonding group. Include main line and ordinary member lines to be
bonded. The following rules must be respected:
Min number of lines >=2 or none.
Max number of lines <=8.
The lines are adjacent to each other.
In order to set the field the operator must:
- double click in the field and the window Group Members will be displayed.
- select the lines and after click on Close button.
• Bonding Protocol: this field defines bonding protocol user. Possible
values are atmBonding, efmPaf, atmIma.
The subsequently fields are read-only fields and they display the Line Bonding
Status.
• OperStatus: This field displays the operational state of the bonding
group. When operational state is down, no data traffic can be passed. If
the total group rate does not match the minimum value configured for
the group, OperStatus will be down even though the Group Admin
Status is up. Note that when all lines in the group have been down,
OperStatus will not change to up until all lines in the group are up.
• DsActualRate: this field displays the actual downstream rate for the
bonding group.
• UsActualRate: this field displays the actual upstream rate for the
bonding group.
IMA Specific Bonding folder
This folder is not available for this release; for this reason it is grey colored.
Application Control folder
This folder provides the fields to control the application itself that are:
• Command: this field specifies the configuration operation to perform.
The possible commands are: create, modify, setadmin.
• Result: In this field is displayed the result of the command that can be:
OK or ERROR.
• Error Message: Error description, the type of the error.
• Date&Time: Date & Time when the Command is launched.
• IP address: IP Address that launches the command.
• Annotations: it is used to write some note about the operation.
38 1/1553-HSC901 003/2 Uen B

2.4.9 xDSL Profiles

PATH: (Configuration -> xDSL Profiles)
This tool is used to configure all the xDSL profiles. To simplify the task of
configuring lines, different profiles can be defined and assigned to one or more
lines instead of configuring each line with all parameters. This tool is composed
by different applications (as shown in the figure below) and it allows the network
operator to create, delete, and modify different kind of ADSL and VDSL Profiles.
The GUI is an all-in-one editor/browser/writer tool, with more than one tabbed
card. Each tabbed card contains an editable spreadsheet-like table for a
consistent set of parameters. The tables are strictly related to one another, and
they can be seen as sections of a one big table. Each table's row has its
continuation in the tables located at its right or left hand. The data displayed in
each row of the subsequent tables are always related to the equipment referred
to. Some fields may be of read-only type: such fields are displayed when
reading from equipment but not used when configuring this service on it.
2.4.9.1 xDSL Line Profile Application
This application allows the network operator to create, delete and modify ADSL
and VDSL Line Profiles. It is composed by the following folders:
• Channel;
• Line Spectrum;
• Power Management;
• Action.
Channel folder
This folder is composed by the following fields:
• NE Name: the NE IP address.
1/1553-HSC901 003/2 Uen B 39

• Profile Identifier: this field specifies the name of the profile. It can be
an alphanumeric string the which length cannot exceed 32 chars.
• XTU-C/XTU-R Min/Max Rate: The data rate in each direction is set by
the Minimum Data Rate and Maximum Data Rate parameters. The
range for the downstream parameters is 32 kbps (32000bps) to 8128
kbps (8128000bps). The range for the upstream parameters is 32 kbps
to 4096 kbps.
• XTU-C/XTU-R Max Int. Delay: The Data rate has also relations to
Maximum Interleave Delay and Impulse Noise Protection settings. The
Maximum Interleaved Delay improves the error correction capabilities of
the ADSL connection. The Interleaved delay determines the
improvement of the error correction: long delay improves more than
short delay. For real time application, set the Interleave delay to zero.
The Interleaved delay value is the maximum permitted value. The exact
value that will be used is determined automatically during line
initialization. The higher the data rate, the lower is the interleaved delay.
The interleave delay settings have relations to the Maximum Achievable
Data Rate and the Impulse Noise protection settings. This value must be
expressed in ms.
• XTU-C/XTU-R Min Imp. Noise Prot: The Impulse Noise Protection
(INP) is the ability of the ADSL transmission to withstand corruption of
data due to noise impulses. This parameter sets a requirement to the
transmission, and it is related to the data rate and the interleave delay
parameters. The minimum value for INP is DMT symbols, which is
equivalent to 250 uS in ADSL, ADSL2 and ADSL2+. Setting INP min to
½ DMT will cause the transmission to withstand (correct errors due to) a
noise pulse with 125 uS duration, one DMT will withstand a pulse of 250.
Possible values are: noINP, halfDmtSymbolINP, oneDmtSymbolINP,
twoDmtSymbolINP, fourDmtSymbolINP, eightDmtSymbolINP,
sixteenDmtSymbolINP.
Line Spectrum folder
• Transmit PSD (Power Spectral Density) defines in which way the
Equipment will use the transmit power capabilities. When the line is
initialized during training, the IP DSLAM can be configured for 2
optimization modes: fixed transmit PSD, re-initialize PSD level. The IP
DSLAM will use the configured priority as a guideline during the training.
Note that the Transmit PSD will not change during Showtime.
• PSD Optim Config scroll list controls the selected PSD optimization
modes. Possible values are: noOptimisation,
optimizeForPsdMaskFilling, optimizeShapeForPerformance.
• PRM Protection, this field is used for 12/16 kHz Private Metering (PRM)
support for DSL line. Possible values are:
disablePrmProtect (Default) - it disables the PRM pulse signaling for the
DSL line.
enablel2kHzPrmProtect - it enables 12 kHz PRM signaling for the DSL line.
40 1/1553-HSC901 003/2 Uen B

enable16kHzPrmProtect - it enables 16 kHz PRM signaling for the DSL line.

• PRM Power Level sets the power level of the PRM signal. This
parameter can be set only when the line is disabled. Valid range is from
0 to 2E32-1.
• Nitro option is used to enable and disable BCM Nitro feature. Possible
values are: enableNitro, disableNitro.
• xTU-C/R Rx Target Noise Margin (tenths of DB) is the signal to noise
ratio (SNR) margin, which always must be achieved for successful
training. The SNR is measured continuously to ensure a bit error rate of
10-7 or better (e.g. 6 dB is the recommended value. Insert, for example,
60 as value in this LCT field).
• xTU-C/R Rx Min Noise Margin (tenths of DB) is the minimum SNR
margin. If the actual SNR falls below the minimum SNR margin, the
output power will be increased. The minimum SNR margin must be
equal to or less than the target SNR margin.
• xTU-C/R Rx Max Noise Margin (tenths of DB) is the actual SNR rises above
the maximum SNR margin, output power will be reduced. The maximum SNR
margin must be equal to or greater than the target SNR margin.
• xTU-C/R Rate Adaptation Mode defines the type of transmit mode to
be configured in the modem. Possible values :
- Fixed: no rate adaptation
- adaptAtStartup: perform rate adaptation only at initialization;
- adaptAtRuntime: perform rate adaptation at any time.
• xTU-C/R Rate downshift SNR (tenths of DB) allows configuring the
signal/noise for rate downshift. If the actual SNR falls below the
threshold, the CPE must decrease the transmit rate. This option is valid
only if rate adaptation is enabled.
• xTU-C/R Min Time for Rate downshift allows to configure the minimum
time that the current margin is above the downshift SNR before the line
rate will be decreased.
• xTU-C/R Rate upshift SNR (tenths of DB) allows configuring the
signal/noise for rate upshift. If the actual SNR falls above the threshold,
the CPE must increase the transmit rate. This option is valid only if rate
adaptation is enabled.
• xTU-C/R Min Time for Rate upshift allows configuring the minimum
time that the current margin is above the upshift SNR before the line rate
will be increased.
• xTU-C/R Bit Rate Threshold. The IP DSLAM can be setup to send an
alarm if the actual data rate of the line drops below the predefined value.
Different threshold values can be set for upstream and downstream
traffic. The bit rate threshold is specified for both upstream and
downstream traffic respectively. Alarms for both upstream and
downstream traffic can be disabled by specifying a threshold value that
is lower than Minimum data rate for the direction. Threshold values
equal to or higher than the minimum data rate will enable the alarm.
1/1553-HSC901 003/2 Uen B 41

The range for each direction is between zero and the specified
Maximum data rate.
• xTU-C/R Bitswap. Bitswap, if enabled, allows the IP DSLAM to
dynamically change the bit allocation per carrier during showtime. The
general effect of this function is a more stable line that is resistant to
temporary interference. However, this function can be disabled (by un-
checking the checkboxes) if interoperability problems with the CPE are
encountered. Possible values are: enableDownstreamBitswaps,
disableDownstreamBitswaps.
• Downshift DMT Carrier Mask, DMT Carrier Mask Downstream: defines
which carries (tones) can be used in the downstream direction.The Mask
is represented as a list of 64 bytes (512 bits), where each bit represents
a tone. The first byte represents carrier 0-7, the second byte represents
carriers 8-15, etc. The last byte represents carriers 504-511.
• Upshift DMT Carrier Mask, DMT Carrier Mask Upstream: defines which
carries (tones) can be used in the upstream direction. The Mask is
represented as a list of 8 bytes (64 bits), where each bit represents a
tone. The first byte represents carrier 0-7, the second byte represents
carriers 8-15, etc. The last byte represents carriers 56-63.
Power Management folder
This mode only affects ADSL2 and ADSL2+, and the parameters are ignored if
the line is VDSL2. While in L2 power mode the IP DSLAM continues to lower
the power in steps (power trims) as long as the target SNR and minimum L2 bit
rate can be maintained. The following parameters can be configured:
• Power Management State Enabling: The ADSL line has 2 possible
power management states: disableL2AndL3 - Synchronized, this Line
state (L0) is when the Line has full transmission (i.e. showtime).
enableL2 - Power down data transmission, this line state (L2) is when
there is transmission on the line but the net data rate is reduced (e.g.
only for OAM and higher layer connection and session control).
• Minimum L2 bit rate is the minimum bit rate when the line is in L2
mode. This value is also used as entry criterion for L2 power mode. This
value must be less than the maximum L2 bit rate (4000 Kbps). The
default value of Minimum L2 bit rate is 2000 Kbps. The range is 0 to the
configured downstream minimum data rate (at L0).
• Mintime in L0 is the minimum interval between exit from L2 power and
the next entry to L2 power mode. The default value is 10 s. The range is
0 to 65535s.
• Mintime in L2 is the minimum interval between entry to L2 power mode
and the first L2 power trim, as well as between consecutive power trims.
The default value is 10 s. The range is 0 to 65535s.
• xTU-C L0 to L2 threshold time, the time interval for L2 entry.
• Max ATPR. Aggregate Transmit Power Reduction per power trim. Defined
the maximum allowed reduction of power per power trim. The range is 0 to
Maximum L2 ATPRT, in 1 dB units. The default value is 3 dB.
42 1/1553-HSC901 003/2 Uen B

• Max ATPRT. Total Aggregate Transmit Power Reduction. When the power
reduction reaches this value no further power trims will be performed.
The range is 0 to 31 dB, in 1 dB units. The default value is 12 dB.
The following figure illustrates the Power and Time L2 Parameters.
Action folder
This folder provides the fields to control the application itself. By means of the
To Do scroll list is possible to create, modify, and delete the configured xDSL
line profile. Result and Error fields give a feedback of the configuration.
2.4.9.2 xDSL Alarm Profile application
This application allows the network operator to create, delete and modify ADSL
and VDSL Alarm Profiles.
General folder
In this folder is possible to enable/disable the trap relevant to different alarms,
choose a name for the profile and assign the NE IP address.
1/1553-HSC901 003/2 Uen B 43

• NE Name: NE logical name or the explicit IP Address (i.e.: x.y.z.w).

• Profile Identifier: This field specifies the name of the profile. It can be
an alphanumeric string the which length cannot exceed 32 chars.
• Init Failure Trap Enable: this field enables or disables the
InitFailureTrap.
• xTU-C Lof Enable: This field is used to enable and disable the
adslAtucXLofFailureTrap and adslAtucXLofFailureCeasingTrap.
The possible values are:
- enable, adslAtucXLofFailureTrap and adslAtucXLofFailureCeasingTrap
will be sent to the trap receiver.
- disable,adslAtucXLofFailureTrap and adslAtucXLofFailureCeasingTrap will
not be sent to the trap receiver.
• xTU-R Lof Enable: This field is used to enable and disable the
adslAturXLofFailureTrap and adslAturXLofFailureCeasingTrap.
- enable, adslAturXLofFailureTrap and adslAturXLofFailureCeasingTrap will
be sent to the trap receiver.
- disable, adslAturXLofFailureTrap and adslAturXLofFailureCeasingTrap will
not be sent to the trap receiver.
• xTU-C LosEnable: This field is used to enable and disable the
adslAtucXLosFailureTrap and adslAtucXLosFailureCeasingTrap.
- enable, adslAtucXLosFailureTrap and adslAtucXLosFailureCeasingTrap
- disable, adslAtucXLosFailureTrap and adslAtucXLosFailureCeasingTrap
will not be sent to the trap receiver.
• xTU-R Los Enable: This field is used to enable and disable the
adslAturxLosFailureTrap and adslAturXLosFailureCeasingTrap.
- enable, adslAturXLosFailureTrap and adslAturXLosFailureCeasingTrap
- disable, adslAturXLosFailureTrap and adslAturXLosFailureCeasingTrap
• xTU-R Lop Enable: This field is used to enable and disable the
dslAturxLopFailureTrap and adslAturXLopFailureCeasingTrap.
- enable, adslAturXLopFailureTrap and adslAturXLopFailureCeasingTrap
- disable, adslAturXLopFailureTrap and adslAturXLopFailureCeasingTrap
15 min / 24 hour Threshold folders:
The thresholds can be set for both upstream and downstream direction. There
are two intervals: 15 minutes and 24 hours. The 15 minutes always start at 0,
15, 30, 45 minutes after the hour (start time is line initialization). The 24 hours
interval start at line initialization, and is synchronized with the 15 minutes
44 1/1553-HSC901 003/2 Uen B

interval. Setting a threshold value to 0 (zero) disables the alarm. The range for
15 Minutes interval is 0 – 900. The range for 24 Hours interval is 0 - 86.400.
These data establish the limits which cause the SNMP agent of the equipment
to send the relative trap. The possible configurable thresholds are:
SES: The number of Severely Errored Seconds encountered by an xDSL
interface within of the data collection period.
UAS: The number of Unavailable Seconds encountered by an xDSL interface
within of the data collection period.
ES: The number of Errored Seconds encountered by an xDSL interface
LOS: The number of Loss of Signal Seconds encountered by an xDSL interface
LOF: The number of Loss of Frame Seconds encountered by an xDSL interface
LOL: The number of Loss of Link Seconds encountered by an xDSL interface
LOP: The number of Loss of Power Defects encountered by an xDSL interface
Action folder
This folder provides fields to control the application itself. By means of the To Do
scroll list is possible to create, modify, and delete the configured xDSL line
profile. Result and Error fields give a feedback of the configuration.
2.4.9.3 ADSL PSD Profile application
This application allows creating, deleting and modifying ADSL Power Spectral
Density profile.
1/1553-HSC901 003/2 Uen B 45

It is composed by the following folders:

• General Setting;
• TSSI Shape Configuration;
• Downstream Power Back Off;
• Action.
General Setting folder
This folder provides the following fields:
• Profile Identifier: this field specifies the name of the profile. It can be an
alphanumeric string the which length cannot exceed 32 chars.
• Downstream Max. Tx Power: it defines the maximum allowed
transmitted power used in the downstream direction. The range is from -
5 to 20 dBm expressed in 0.1 dBm.
• Upstream Max. Tx Power: it defines the maximum allowed transmitted
power used in the upstream direction. The range is from -13 to 20 dBm,
expressed in 0.1 dBm.
• Upstream Max. Rx Power: defines the maximum received power at the
ATU-C. The ATUC will request an Upstream Power Cutback such that
the power received at the ATUC does not exceed Max. Rx Power
Upstream. This parameter applies to ADSL2 and ADSL2+ only. The
range is from -5 to 20 dBm, expressed in 0.1 dBm
TSSI Shape Configuration folder
• Downstream ADSL Plus Tx Filter: The parameter enables an extra,
proprietary, high pass filter, for ADSL2+ cabinet deployment. It can be
used to cut down the lower frequencies in the transmission. This
additional filter is used to suppress side lobes for tones under the
defined cutoff tone. It should be used together with the downstream
carrier mask where all downstream tones under the defined cutoff tone
must be disabled. The range is 0 to 15. Exchange need value 0. Cabinet
need value in the range 1...15.
• Protocol Type: defines on which ADSL modes the PSD shape will be
applied. Annex A/B/M (for G.992.3), Annex A/B/M (for G.992.5),
Annex L (for G.992.3).
Possible values are: ADSL2, ADSL2+, ADSL2+ AND ADSL2, ADSL2 L,
46 1/1553-HSC901 003/2 Uen B

ADSL2 AND ADSL2 L, ADSL2+ AND ADSL2 L, ADSL2+ AND ADSL2

AND ADSL2 L.
• Tone: a separate window will be displayed by double clicking in this
field. In the Tone Index (from 0 to 511)and Resulting PSD [dB/Hz]
(from 38.3 to 100.8) it is possible to create PSD (Power Spectral
Density) shaping using breakpoints. The PSD hexadecimal string
defines the breakpoints.
• PSD Mask Upstream: The selected upstream PSD mask.
• A43/B43/A43C/B43C (dBm/Hz): it defines the PSD level of the ADSL
handshakes. PSD level can be defined for the following G.994.1 carrier
set designations in the range from -128 to - 32 and 0. The unit is
dBm/Hz: A43 (mainly for Annex A), B43 (mainly for Annex B) and
A43C/B43C (mainly for cabinet deployment).
Downstream Power Back-Off folder
• RFI Notching: This configuration parameter defines the subset of
downstream PSD mask breakpoints that shall be used to notch an RFI
band. This subset consists of couples of consecutive subcarrier indices
belonging to breakpoints: [ti; ti + 1], corresponding to the low level of the
notch. The specific interpolation around these points is defined in the
relevant Recommendations (e.g., ITU-T Rec. G.992.5). For ITU-T Rec.
G.993.2 (VDSL2), this configuration parameter defines the bands where
the PSD shall be reduced as specified in #7.2.1.2/G.993.2. Each band
shall be represented by a start and stop subcarrier indices with a
subcarrier spacing of 4.3125 kHz. Up to 16 bands may be specified. This
parameter defines the RFI bands for both upstream and downstream
directions. The value can be a sequence of couples separated by %%,
i.e. 0-1%%2-6%%.
• ESEL (dB): This configuration parameter defines the assumed electrical
length of cables (E-side cables) connecting exchange based DSL
services to a remote flexibility point (cabinet), that hosts the xTU-C that
is subject to spectrally shaped downstream power back-off depending
on this length. For this parameter the electrical length is defined as the
loss (in dB) of an equivalent length of hypothetical cable at a reference
frequency defined by the network operator or in spectrum management
regulations. DPBOESEL shall be coded as an unsigned integer
representing an electrical length from 0 dB to 255.5 dB in steps of 0.5
dB. All values in the range are valid. If DPBOESEL is set to zero, the
DPBO in this section shall be disabled.
• ESCMA: This configuration parameter is used to define a cable model in
terms of three scalars DPBOESCMA, DPBOESCMB and DPBOESCMC
that shall be used to describe the frequency dependent loss of E-side
cables. Parameters DPBOESCMA, DPBOESCMB, DPBOESCMC shall
be coded as unsigned integers representing a scalar value from -1 to 1.5
in steps of 1/256. All values in the range are valid.
• ESCMB (1/sqr(Hz)): See ESCMA.
1/1553-HSC901 003/2 Uen B 47

• ESCMC (1/Hz): See ESCMA.

• FMIN (kHz): it defines minimum frequency from which the DPBO shall
be applied. It ranges from 0 kHz to 8832 kHz in steps of 4.3125 kHz.
• FMAX (kHz): it defines the maximum frequency at which DPBO may be
applied. It ranges from 138 kHz to 29997.75 kHz in steps of 4.3125 kHz.
• MUS (dBm/Hz): it defines the assumed Minimum Usable receive PSD
mask (in dBm/Hz) for exchange based services, used to modify parameter
DPBOFMAX. It shall be coded as an integer representing a PSD mask level
from -127.5 dBm/Hz to 0 dBm/Hz in steps of 0.5 dB. All values in the range
are valid. The PSD mask level is 3.5 dB above the signal PSD level.
• Nonstandard DPBO: it enables an alternative downstream Power Back-
Off, which differs from the standard G.997.1 PBO calculation.
• ESELMIN (dB): this configuration parameter defines the minimum value
of all trunk line losses of the cable distributors served (including the KVz
at the DSLAM site). This parameter is not G.997.1 compliant and has
only effect when adslLineConfPhysAdslPboPsdDnAdvanced is enabled.
• MIB Mask Ds: The configuration parameter defines the PSD mask that
is assumed to be permitted at the exchange. This parameter shall have
up to 16 breakpoints. Each breakpoint occupies 3 octets: The first two
octets hold the index of the sub-carrier associated with the breakpoint.
The third octet holds the PSD reduction at the breakpoint from 0.
48 1/1553-HSC901 003/2 Uen B

Action folder
2.4.9.4 VDSL PSD Profile application
This application allows creating, deleting and modifying VDSL Power Spectral
Density profiles.
It is composed by the following folders:

• General Setting;
• VDSL PSD Shaping;
• Action.
General Setting folder

• Profile Identifier: this field specifies the name of the profile. It can be an
alphanumeric string the which length cannot exceed 32 chars.
• Profile Enabling: VDSL2 profiles to be allowed by the near-end xTU on
this line. It is coded in a bit map representation. In order to set the value
double click on the field, the window "VDSL Profile Enabling will be
displayed (unchecked means not allowed, checked means allowed).
• Maximum power ds. This is the maximum total power of the
transmission. It can be used to further reduce the transmission power.
1/1553-HSC901 003/2 Uen B 49

Note that this parameter should be equal to or less than the power
defined in the standard for the selected profile.
• Limit Mask that will be used. The limit masks define band plan and PSD
shape. The following limit masks are supported:
Standard masks (G.993.2 annexes and amendments):
• In the Disabled Carrier section up to 8 bands can be defined. The

carriers in a defined band will be disabled, Note that this applies to both
upstream and downstream. Use the same index number in both start
and stop to disable only one carrier. The range is 0-4095. In order to set
the value the operator must execute the following steps:
- Double click on the field "Disabled Carrier", the window "NOTCHES" will be
displayed.
- Compile the columns and after click on the button "Confirm & Close".
The value can be a sequence of couple separated by characters "%%", i.e.
0-1%%2-6%%.
VDSL PSD Shaping folder
• If Downstream Power Back-Off (DPBO) function is desired, check the
Enable DPBO checkbox. In this case, all the following line configuration
parameters must be set to generate a modified downstream PSD mask
for Downstream Power Back-Up.
• Forced e-length – Set the electrical length that will be used for the
calculation of the UPBO PSD mask. The electrical length is the
attenuation of the signal at 1MHz from the CPE to the cabinet. The
range is 0 - 127 dB (0.1 dB steps). Set the value to -1 in order to use the
value measured during training.
• US1, US2, US3 A and B fields are used to define 2 parameters, A and B
for each of the three upstream bands. These parameters are used in the
mathematical description of the desired PSD mask of the signal when it
reaches the cabinet. The ranges are:
A: 0, -80.96 to -40.0 dBm/Hz in steps of 0.01 dBm/Hz. Zero disables the
UPBO in the band. Note that this parameter has a negative value.
B: -40.0 to 0.0 dBm/ Hz in steps of 0.01 dBm/ Hz . Note that this
parameter has a negative value.
• Nonstandard UPBO: it enables an alternative UPBOMASK calculation,
which differs from the standard G.997.1 PBO mask calculation.
• In the MIB Mask Downstream section and the MIB Mask Upstream
section a custom PSD mask can be defined. Each breakpoint is defined
50 1/1553-HSC901 003/2 Uen B

by a Carrier Index (range 0 to 4095) and a PSD level (range from 0 to

-96 dBm/Hz). MIB Mask will be combined with all other defined masks.
Action folder
2.4.10 Line Bonding Management

PATH: (Configuration -> xDSL Line Bonding Configuration)
This application allows the network operator to aggregate a higher bandwidth for
an end user by bonding more physical lines together into one channel.
The ADSL line configuration must be done per line and the traffic configuration
must be done on the main line only.
The bonding specific parameters apply to the line index for the line that is
denoted main line within the bonding group.
The individual line configuration is independent from the bonding service
configuration.
The GUI is an all-in-one editor/browser/writer tool, with more than one folder.
Each tabbed card contains an editable spreadsheet-like table for a consistent
set of parameters. The tables are strictly related to one another, and they can be
seen as sections of a one big table. Each table's row has its continuation in the
tables located at its right or left hand. The data displayed in each row of the
subsequent tables are always related to the equipment referred to. Some fields
may be of read-only type: such fields are displayed when reading from
equipment but not used when configuring this service on it. The application is
composed by the following folders:
• Line Bonding Configuration;
1/1553-HSC901 003/2 Uen B 51

• Line Bonding Status;

• Application Control.
Line Bonding Configuration
• NE Name: the name or IP address.
• Line Id: the end-user's physical line in the following format
subrack>/<slot>/<port> (e.g. 1/13/1).
• Group Admin Status: the desired state of the bonding group.
• Max Ds Group Rate: the configured maximum downstream group rate.
• Min Ds Group Rate: the configured minimum downstream group rate.
• Max Us Group Rate: the configured maximum upstream group rate.
• Min Us Group Rate: the configured minimum upstream group rate.
• Atuc Quality Threshold: line quality alarm threshold for the bonding group.
• Atur Quality Threshold: line quality alarm threshold for the bonding group.
• Atur No Wait: it controls bonding mode behavior.
• Group Members: the lines (channels) that should be bonded in this
bonding group. Include main line and ordinary member lines to be
bonded (Min number of lines >= 2 or none, Max number of lines <= 8).
Line Bonding Status
• Group Oper Status: the operational state of the bonding group (down:
no data traffic can be passed).
• Actual Ds Rate: the actual downstream rate for the bonding group.
• Actual Us Rate: the actual upstream rate for the bonding group.
Application Control
This folder provides fields to control the application itself.
• Command: the configuration operation to perform, create, delete,
modify setAdmin.
• Result: the response for the operations executed.
• Error Message: Error description, the type of the error.
• Date&Time: the timestamp (time that is printed to a file or other location
to help keep track of when data is added, removed, sent, received)
referred to the inventory operation.
• Ip Address: IP address of the Equipment.
• Annotations column is used to write some note about the operation.
2.4.11 xDSL Line Activation
PATH: (Configuration -> xDSL Line Activation)

This option is used to change the administrative status of the xDSL Lines. In
particular this feature allows the Operator to enable or disable all the lines
belong to the same card at the same moment. It possible to check the lines
status, getting a report too.
52 1/1553-HSC901 003/2 Uen B

To perform a Line’s Admin Status change:

1. Select the relevant radio button according to the operation to be executed
(Enable, Disable, and Check).
2. By means of the relevant spinner, choose the Slot to enable/disable/check.
If the item All is chosen all xDSL lines are selected.
The Waiting for... bar shows the progress of the operation, while the Message
Area (highlighted in yellow); will give you a response of the operation requested.
3. Press Go to perform the Enable/Disable/Check operation.
4. View error log button gives a response in case of operation failure.
2.4.12 PSTN National Mapping

PATH: (Configuration ->PSTN National Mapping)
The National Mapping consists in a large number of parameters (timers,
cadences, voltages, frequencies etc.) that must be predefined. The purpose of
these information elements is to allow the Local Exchange national PSTN/ISDN
protocol to control adequately the operation and the responses of the line
circuits over a common based signaling channel. These information elements
may be used within different messages at different times depending upon time
constraints imposed by the national PSTN/ISDN protocols and the state of the
signaling path.
The National Mapping Download is an application useful to manage and tune
the parameters of the POTS/ISDN lines in order to match the specific national
mapping. By means of this application is possible to:
• add to your local catalogue a National Mapping created by another user
(the imported National Mapping is available in Read mode);
• read the National Mapping configuration actually present on the
equipment (VoIP line cards);
• read the National Mapping configuration expected for the equipment
(VoIP line cards);
• configure download of the National Mapping files to the voice line cards.
1/1553-HSC901 003/2 Uen B 53

EDA National Mapping Download

With this application it is possible to download the National Mapping
configuration. You can easily access this tool by clicking the NM Download
button on the EDA National Mapping Editor mask:
The National Mapping Download allows managing different National Mapping

SW and it is structured in two different tab panels:
• Actual Configuration panel used to read the actual configuration for
each slot.
• Expected Configuration panel used to read the expected configuration
of each slot and to configure the desiderated configuration.
NOTICE Do not forget to open a TFTP Server session on the PC before running the
application. TFTP features are required.
54 1/1553-HSC901 003/2 Uen B

Each National Mapping code consists of a single compressed file containing all
the files needed to the VoIP line cards to implement the National Mapping.
Two different mechanisms are possible in the Equipment to download the
National Mapping files to the voice line cards:
• A manual download directly controlled and triggered by management.
• An automatic download to update those VoIP line cards that have a
National Mapping mismatching with the desired one.
In order to manually download to the line cards the National Mapping
information the following steps are needed from the management interface:
• Configuration of the desired National Mapping with the file to be
downloaded for each slot position (applicable only if in that slot position
a voice line card is hosted).
• Configuring the URL containing the TFTP/FTP server IP address and
directory path where the National Mapping files are stored.
Export DB
With this application it is possible to export the local DB configurations. You can
easily access this tool by clicking the Export DB button on the EDA National
Mapping Editor mask.
• Export Dir: it is used to specify the destination directory.

• DB Name: it is used to specify the DB name.
• Press Apply to start the exporting database (.zip file will be created).
1/1553-HSC901 003/2 Uen B 55

Import DB
With this application it is possible to import the local DB configurations. You can
easily access this tool by clicking the Import DB button on the EDA National
Mapping Editor mask.
• Full DB Name: it is used to specify the DB name (full path).

• Import Type: it is used to specify the import type. Possible values are:
No merge: the local repository is cleaned before importing a configuration.
Merge overwrite: local repository is merged (existing files overwritten).
Merge no overwrite: local repository is merged (existing files no overwritten).
• Press Apply to start the import.
Managing of Pull Down Menus:

The following paragraphs describe the File, Tools, Edit, Option, NatMap, Call
Control, Line Card menus available in PSTN National Mapping application.
56 1/1553-HSC901 003/2 Uen B

File Menu (NM)

NM BROWSE = it browses the directory containing the NM file in order to open
it and load the parameters in the Edit panel of the National Mapping Editor.
EXIT = it closes the application.
Tools Menu (NM)
NM REPOSITORY REGISTRY: it opens the default repository address. In the
Repository URL of the NM Repository Registry it is possible to add or delete
a new repository location. The directory must be present on local PC in order to
be created. The possible URL can be in the local PC or in a FTP/TFTP Server.
In the following the syntax accepted for this operation:
file:C:/Temp (in this case Temp has been chosen ad local repository location).
ftp://hpiv114/disk2/usr/test/.
Option Menu (NM)
ENABLE EDIT MODE = it allows to enable the possibility to modify/create a
National Mapping. This feature is protected and only certified Ericsson personnel
can use it.
STOP ON ERROR = it allows to stop applying configuration sheet at the first error.
ENABLE REPORT = it allows to produce a report file containing all I/O data
(including result codes and error descriptions), at the end of each configuration run.
NatMap Menu (NM)
NATMAP BROWSE = it browses a NM file already present.
HOWLER TONE IMPORT = it allows to import a Howler Tone file.
NATMAP IMPORT = it allows to import a NM file.
CallControl Menu (NM)
CC BROWSE = it browses a CallControl file already present.
CC IMPORT = it allows to import a CallControl file.
LineCard Menu (NM)
LC BROWSE = it browses a LC file already present.
LC IMPORT = it allows to import a LC file.
2.4.13 POTS/ISDN Profiles

PATH: (Configuration -> POTS/ISDN Profiles)
This menu is used to create the RTP Profile and TOIP Profile used for the VoIP
application. The two profiles have to be applied to the POTS and ISDN units.
The profiles for POTS and ISDN units have the same parameters.
In the following every application will be described.
1/1553-HSC901 003/2 Uen B 57

POTS RTP Profile/ISDN RTP Profile

The RTP Profile Application provides the Profile for RTP (Transport Protocol for
Real-Time Application) with RTP parameters for a line. The characteristics
include VLAN ID, VLAN priority, layer 3 IP ToS field, local RTP IP address and
default gateway address. Each profile is designed for specific requirements of
different markets segments and standards. This application is composed by
following folders:
• RTP Profiles;
• Action.
RTP Profile folder
RTP Profile defines Transport Protocol for Real-Time Applications parameters
for a line. The characteristics include VLAN ID, VLAN priority, layer 3 IP ToS
field, local RTP IP address and default gateway address. Each Profile is
designed for specific requirements of different market segments and standards.
• Ne Name: IP address of the equipment.
• Profile Number: identifying number. It must be a unique value, greater
than zero.
• Description: a name used to identify the profile.
• ID: VLAN ID used in layer 2 VLAN Tag header for RTP Ethernet packets.
Two IDs are available: Outer VLAN ID (S-VLAN ID) and Inner VLAN ID (C
VLAN ID).Outer will be always applied but Inner VLAN is optional.
• Priority: priority used in the layer 2 VLAN Tag header for RTP Ethernet
packets. Two Priorities are available: Outer VLAN priority (priority for S-
VLAN ID) and Inner VLAN priority (priority for C VLAN ID). The possible
values are in the range from 0 to 7. 0 is the lowest priority.
• Tag Type: defines the VLAN tag type applied on downstream (Outer
VLAN Tag Type) or upstream (Inner VLAN Tag Type) traffic interface.
Two Tag Types are available: Outer VLAN Tag Type (TP ID for the S-
VLAN ID) and Inner VLAN ID Tag Type (TPID for the C VLAN ID).
Possible values are:
- qtag: Q/QinQ VLAN tagging (Ethernet Type 0x8100);
- vmantag: VMAN VLAN tagging (Ethernet Type 0x88A8);
- extremevmantag: Extreme VMAN VLAN tagging (Ethernet Type 0x9100).
• VLAN Operation: type of VLAN Operation. Possible values are:
addonetag means single tag (only Outer VLAN is used);
addtwotags means stacked tag (both Outer and inner Tag are used).
• DSCP Field: it is the value to set in DSCP (Differentiated Services
CodePoint bits) for RTP packets.
• Subnet Mask Prefix Length: it denotes the length of a generic Internet
network address prefix. A value of n corresponds to an IP address mask
which has n contiguous 1-bits from the most significant bit (MSB) and all other
bits set to 0.the imum significant value is 32 for the 'ipv4'. Specifies number of
bits to use in the parameter RTP Local IP Address in the window of
Configuration for the POTS and ISDN units (Lines -> Configuration).
58 1/1553-HSC901 003/2 Uen B

• Default Gw IP Addr: IP address of the first router connected to the

equipment that receives RTP traffic.
• Disallow Local Switching: it establishes the policy action for U-turn of
user traffic, i.e. for packet forwarding between two lines on the same
equipment/card. Possible values are true and false. False means that
RTP streams between two lines on the same equipment/card is not
allowed to be looped internally. Thus in order to establish RTP streams
between lines on the same equipment the streams has to be looped by
an external gateway.
Action folder
• ToDo: This field allows to create/modify/delete a profile via the
corresponding commands.
• Result: Display the result of the executed command.
• Error: This read only field shows the type of the error.
POTS TOIP Profile/ISDN TOIP Profile
The TOIP Profile Application defines the Profile for Telephony over IP, ToIP
parameters for a line. The characteristics include echo cancellation, audio
codec, packet size and jitter buffer configuration. Each profile is designed for
specific requirements of different market segments and standards.
ToIP Profile folder
• Profile Number: identifying number. It must be a unique value, greater
than zero.
• Description, a name used to identify the profile.
• Jitter Buffer Type, a Jitter buffer is used where the RTP stream is terminated
to eliminate delay variations (known as jitter) in the IP network. The main task
for the jitter buffer is to compensate for the jitter introduced by the network. It
operates on the downstream RTP packets which are stored in this buffer. The
jitter buffer will introduce delay on the downstream traffic based on the
configured and actual size. Possible values are:
- None: jitter buffer is disabled. This is not recommended normal operation,
voice packets may be dropped due to jitter. The delay introduced is
approximately 10 ms.
- Fixed: A fixed jitter buffer is the simplest form of jitter buffer. This buffer
eliminates delay variations by using a constant buffer size. This constant buffer
size introduces a constant delay. Jitter buffer has a fixed size and fixed delay.
- adaptive: The adaptive jitter buffer adapts to network delay variations and tries
to keep the buffer as short as possible to avoid the (long) constant delay.
• Jitter Buffer Size min (ms): minimum dimension of the jitter buffer.
This value should be always less than or equal to Initial value.
• Jitter Buffer Size max (ms): maximum dimension of the jitter buffer.
This value should be always greater than or equal to Initial value.
1/1553-HSC901 003/2 Uen B 59

• Jitter Buffer Size initial (ms): this field specifies the JitterBufferSize
initial value. Initial value indicates how much payload data should be
there in jitter buffer to start parsing. It is the initial fill level before starting
the play-out.
Action folder
• ToDo: This field allows to create/modify/delete a profile via the
corresponding commands.
• Result: Display the result of the executed command.
2.4.14 IP and Ethernet Management

This application groups together the applications that configure the Bridging on
xDSL board side and Common Part side.
2.4.14.1 Browse & Configure xDSL Bridge
PATH: (Configuration -> IP / Ethernet Management -> Browse and Configure xDSL Bridge)
This application allows configuring the bridge features in the Equipment. It is
composed by several applications and each one contains several folders as
shown in the window below:
PVC Management application

The application supports the configuration of the IP-DSLAM bridge functionality.
The IP-DSLAM bridges data from the end-users ATM side to the Ethernet-
based network and vice-versa. Data flowing through the IP-DSLAM will be
60 1/1553-HSC901 003/2 Uen B

validated to identify the correct recipient and to disallow data flow to end-users
for which the data is not intended. The bridge filtering of the IP-DSLAM is
configurable per end-user and per-PVC for a specific end-user. A PVC
(Permanent Virtual Circuit) has a pair of ATM VCL identifiers VPI, VCI
associated to it. On the base of the class of service and other parameters, the
data is classified and bridged in different paths. Each classification is considered
as a distinct flow.
To obtain a full configuration of the PVC set, at least two more applications,
respectively intended for configuration of downstream and upstream flows, have
to be used, and they can indeed be run from within this one. Besides, one more
application has to be used to configure the set of user lines and even more
applications should be run to complete the configuration of an EDA object with
ACLs (Access Control Lists ), Multicast Filters and Subscriber IP Filters.
This application provides a number of folders that all together make up one big
logical table for PVC configuration:
• CONTROL;
• Bridge PVC;
• QUEUES&ATM;
• PROTOCOLS;
• GATEWAY;
• DHCP, PPPoX, AGENTS;
• FILTERS.
Therefore, the rows having the same row index in each folder, all together,
make up one logical big entry for specific PVC, and each entry is indexed by:
• Line Path <sh>/<sl>/<ln>
• PVC Index
Control folder
This application is composed by following folders:
• Access Node: the IP address of the Equipment.
• Line Path: indication (subrack/slot/line) of the line involved in the PVC.
• PVC Index: the index for the Permanent Virtual Circuit.
• PVC Status Summary: the status of the PVC. The following statuses
are possible: Failed, createFailed, notUsed, success, testDisabled,
testing, ok, failedF5etoe, lineDown, awaitCreation.
• Command: the command to be performed.
- enable: bring the PVC to visibility;
- modify: change some properties for an exposed PVC;
- bdlCkdEnable: enable PVC only after a successful bundling
consistency check;
- bdlCkdModify: modify PVC only after a successful bundling
consistency check;
1/1553-HSC901 003/2 Uen B 61

-
- disable: makes a PVC unavailable;
- setmacfilter: special command to set the Subscriber MAC Filter value;
('modify' has no effect on it);
- skip: does nothing with this row (enable, disable, modify, skip).
- restorePvcDefault: restore default values for the specified PVC. When
the restorePvcDefault command is issued, the Logical Channel is
automatically disabled by setting peakCellRate = 0, then all its
parameters are restored to default values so that a subsequent 'enable'
will re-create it with default values.
• Result column shows response for the operations executed (OK, NOK).
• Error Message column shows the type of the error.
Bridge PVC folder
• Access Method: This field determines how the end-user device
interacts with the IPDSLAM, it will therefore take the following into
account:
- If and how the end user device obtains an IP address.
- How authentication of the customer's IP address is achieved.
- How the address of the default IP gateway is specified.
- The underlying encapsulation protocol to be used.
• dhcp: when DHCP is selected, the DHCP protocol is used to
authenticate, assign and renew the end-user's IP address. The address
of the IP gateway is also provided by means of the DHCP protocol. The
encapsulation protocol is IP over Bridged Ethernet.
• staticIp: when Static IP is selected, the IP address of the end-user as
well as the default gateway must manually be specified. This information
is furthermore used to authenticate traffic from the end user device. The
encapsulation protocol is IP over Bridged Ethernet.
• transparentLan: all traffic from the end-user device passes transparently
to the network. No IP address is provided by the IPDSLAM itself. No
authentication is performed and furthermore no gateway is specified.
When this option has been activated, all filtering of end-user packets is
disabled. The encapsulation protocol is Bridged Ethernet.
• pppoe: when PPPoE is selected, the PPP protocol is used to setup PPP
sessions. Once a session has been setup, all traffic is encapsulated
within PPP packets, until the session is torn down. Once a session is
established, an IP address is assigned to the end-user, which is also
used to authenticate the end-user's traffic. The address of the IP
gateway is also provided as the start of the PPP session.
• pppoa: when PPPoA is selected, the encapsulation of all traffic between
the IPDSLAM and the end user device is Routed PPP over AAL5
frames. These so-called PPP over ATM packets are converted to
PPPoE before being passed to the access network.
62 1/1553-HSC901 003/2 Uen B

• pppox: when this option is selected, auto-detection is used to determine

whether the customer device is using PPPoE or PPPoA.
• staticIpoa: when this mode is selected, the behavior is much alike that
described in staticIp. The principle difference is the use of Routed IP
over AAL5 frames as the encapsulation protocol instead of IP over
Bridged Ethernet. The use of ATM is exclusively used between the
IPDSLAM and the customer device. This functionality is converted to IP
over Bridged Ethernet before being passed to the access network.
• dhcpIpoa: when this mode is selected, the behavior is much alike that
described in dhcp. The principle difference is the use of Routed IP over
AAL5 frames as the encapsulation protocol instead of IP over Bridged
Ethernet. The use of ATM is exclusively used between the IPDSLAM
and the customer device. This functionality is converted to DHCP over
Bridged Ethernet before being passed to the access network.
• transparentIpoa: when this mode is selected, the behavior is much alike
that described in staticIp. The principle difference is the use of Routed
AAL5 frames as the encapsulation protocol instead of Bridged Ethernet.
The use of ATM is exclusively used between the IP DSLAM and the
customer device.
• Vpi: this field represents the Virtual Path Identifier (VPI) for the specified
PVC of an end-user line. The VPI and VCI (Virtual Channel Identifier)
identifies the PVC (Permanent Virtual Circuit). The value can be
between 0 and 15.the VPI involved in the PVC.
• Vci: This field represents the Virtual Channel Identifier for the specified
PVC of an end-user line. The VCI and VPI identify the PVC (Permanent
Virtual Circuit).The value can be between 0 and 255.
• Bundling: if this field is enabled (pvcBundlingEnabled), the PVC will
be bundled with other PVCs that have the same service (S) and
customer (C) vlan on a line and a single logical port can be created.
• S/C VLAN Operation: This field defines the VLAN operation for the
specific PVC. The possible values are:
* addonetag: the IP-DSLAM will add one VLAN tag. It will be added on
top of the end-users tags if any. A maximum of five tags are supported
included the one added by the IP-DSLAM.
*addtwotags: the IP-DSLAM will add two VLAN tag. They will be added
on top of the end-users tags if any. A maximum of five tags are
supported included the two added by the IP-DSLAM.
• End User Q-VLAN Op: this field decides how the end-users VLAN tags
should be handled. The possible values are:
* endUserVLanForward: End-user VLANs are filtered according to the
VLAN ID ACL and then forwarded. If the VLAN ID ACL is not defined all
VLAN IDs will be allowed.
* endUserVLanFilterRemove: End-user VLANs are filtered and then
removed/added. Upstream traffic is first filtered according to the
upstream VLAN ID ACL and then the VLAN is removed. On downstream
traffic the VLAN is added to the frame before sending it to the end-user.
1/1553-HSC901 003/2 Uen B 63

The VLAN that is added is the first VLAN in the first range specified in
the downstream VLAN ID ACL.
• S-VLAN Id: (outer): This field specifies the VLANID to be used for the
Ethernet traffic (accordingly to 802.1Q) from and to the specified PVC.
The value can be between 0 and 4095.
• S-Priority (outer): This field specifies the priority value to be used when
VLAN Operation is set to addonetag/addtwotags. This field specifies the
priority (accordingly to 802.1Q) that should be used for the Ethernet
frames to and from the specified PVC. It is only used when VLAN
Operation" field is set to "addonetags" or "addtwotags". The value can
be between 0 and 7 (where 7 is the highest priority).
• S-VLAN Tag: (outer): This field defines the VLAN tag type applied on
upstream traffic. In case of two VLAN tags applied then this VLAN tag
type is applied to the outer VLAN tag. The possible values are:
* qtag: Q/QinQ VLAN tagging. (Ethernet Type 0x8100)
* vmantag: VMAN VLAN tagging. (Ethernet Type 0x88A8)
* extremevmantag: Extreme VMAN VLAN tagging. (Ethernet Type 0x9100).
• C-VLAN Id: (inner): This field represents the VLAN identifier that is to
be used if vlan Operation field is configured to "addtwotags". This is the
inner Vlan used on traffic from and to the specified PVC. The value can
be between 0 and 4095. 65535 is a nil-value indicating that inner VLAN
is not in use the outer-tag VLANID used for the Ethernet frames to and
from the specified PVC.
• C-Priority (inner): This field represents the VLAN priority that is to be
used if vlan Operation field is configured to "addtwotags". This priority is
associated with "C-VLAN Id (inner)" accordingly to 802.1Q. The value
can be between 0 and 7 (where 7 is the highest priority). 255 is a nil
-value indicating that inner VLAN is not in use.
• C-VLAN Tag: (inner): this field defines the inner VLAN tag type applied
on upstream traffic. The possible values are:
- qtag: Q/QinQ VLAN tagging. (Ethernet Type 0x8100)
- vmantag: VMAN VLAN tagging. (Ethernet Type 0x88A8)
- extremevmantag: Extreme VMAN VLAN tagging. (Ethernet Type 0x9100).
• VLAN filterBits: This field defines the types of VLAN tagging a user is
allowed to use on upstream traffic. The upstream traffic passes a VLAN
filter and if the outermost VLAN tag in the received packet is not allowed
the packet is discarded. The possible values are:
- untag: it allows untagged traffic.
- qtag: it allows Q-tagged traffic
- vmantag: it allows VMAN-tagged traffic.
- extremevmantag: it allows Extreme VMAN-tagged traffic.
By activating multiple bit positions, multiple ethertypes will be accepted. By
activating no bit positions, no ethertypes will be accepted.
• L2CP Tunneling: this field is used to enable Layer 2 Protocol
Tunneling. The Layer 2 Control Protocol tunneling feature is only
available when Access Method field is "transparentLan". The possible bit
64 1/1553-HSC901 003/2 Uen B

positions are:
- stp: when set Layer 2 Control Protocol tunneling is enabled for
Spanning Tree Protocol (destination MAC = 01:80:c2:00:00:00)
- pvst: when set Layer 2 Control Protocol tunneling is enabled for Per
VLAN Spanning Tree Protocol, a Cisco specified extension to STP
(destination MAC = 01:00:0c:cc:cc:cd).
- cdp: when set Layer 2 Control Protocol tunneling is enabled for Cisco
Discovery Protocol (destination MAC = 01:00:0c:cc:cc:cc)
- vtp: when set Layer 2 Control Protocol tunneling is enabled for Virtual
Trunking Protocol (destination MAC = 01:00:0c:cc:cc:cc). The default
setting is 0 for all bits.
Queues & ATM folder
• ATM Service Category: this field determines which atm service
category to use for the PVC. The possible values are:
- ubr: Unspecified bit rate. This is typically used for data applications
- vbrNrt: Variable bit rate - non real-time. (such as VBR RT, except that
CDV (cell delay variance) is not taken into account)
- vbrRt: Variable bit rate - real-time. This is typically used for multimedia
applications.
- cbr: Constant bit rate. This is typically used for telephony applications.
• Schedule Scheme: this field specifies how packets on the ATM PVC
should be scheduled from the queues (strictPriority, deficitRoundRobin,
modifiedDeficitRoundRobin, none)
• Schedule Scheme B1: this field specifies how packets on the ATM PVC
should be scheduled from the queues for downstreamFlows 5 - 8
(strictPriority deficitRoundRobin, modifiedDeficitRoundRobin, none).
• Downstream PCR: This field represents the peak downstream PVC
rate. It specifies in bits per second the peak rate at which bits are to be
sent on this PVC.
• Downstream SCR: this field represents the average downstream PVC
rate. It specifies in Kbits per second the average rate at which bits are to
be sent on this PVC. SCR means Sustainable Cell Rate.
• Downstream MBS: This field represents the maximum number of cells
in a burst in the downstream direction.
Protocols folder:
• Local Switch: This field controls the local switching of the ethernet
packets on the IP DSLAM. The possible values are:
* enabled: it enables local switching on this connection.
* disabled: it disables local switching on this connection.
• Allow Broadcast: this field specifies how broadcast traffic towards the
end-user should be handled. The possible values are:
* true: to forward broadcast traffic to the end-user.
* false: to drop all broadcast traffic.
• ICMP Security: This field is used to allow the IPDSLAM to drop certain
ICMP messages coming on this PVC in the upstream direction. The
purpose of this is to avoid denial of service attacks from the end-users.
1/1553-HSC901 003/2 Uen B 65


* True: all ICMP destination unreachable and ICMP redirect messages
will be dropped;
* False: all ICMP destination unreachable and ICMP redirect messages
will be allowed.
• Arp Proxy Config: This field decides the behavior of the ArpProxy in the
IP-DSLAM. It is only valid when forced forwarding is enabled. The
possible values are:
* proxyAllArpRequests: All ARP Requests from the end-user will always
be replied with the MAC address of the default gateway configured for
the end-user, except gratuitous ARP Requests which will be dropped.
This setting should be used when broadcast traffic should be kept to a
minimum, for instance when running large L2 networks.
* proxyNonGwArpRequests: All ARP Requests from the end-user to the
default gateway are forwarded to the network. Gratuitous ARP Requests
are also forwarded to the network. Any request to a non gateway IP will
be replied the default gateway MAC address. This setting is needed
when running 'Passive ARP Learning' in VRRP enabled routers or other
technologies where ARP from the end-users is needed.
*proxyNonGratuitousArpRequests: All ARP Requests from the end-user
will be replied with the MAC address of the default gateway configured
for the end-user. Except gratuitous ARP Requests which are forwarded
to the network. This setting should be used when broadcast traffic
should be kept to a minimum, but the ARP cache timeout in the router is
too long to detect end-user MAC replacement.
• IGMP Snooping: this field is used to activate IGMP snooping on the
specified PVC. The possible values are:
* true: IGMP snooping will be enabled. The end-user will be able to use
IGMP (v1, v2 and v3) to join multicast groups.
* false: All IGMP packets from the end-user will be discarded, and no
IGMP packets from the network will be forwarded to the end-user.
• User Mcast Max (0,1-16): this field represents the upper limit on the
number of Multicast Groups an end-user can join simultaneously. When
exceeded, the end-user will be denied the membership to any new
group. The possible values are
* 0: Limiting disabled.
* 1-16: The upper limit to be imposed.
• Upstream Mcast: when set to True enables the end-user to send IGMP
queries and multicast streams in the VLAN associated with the PVC.
• Flood Multicast range: IP Since not all multicast is based on IGMP;
there exist certain cases where multicast traffic needs to be detected.
The only possible way to do this is snoop the traffic based on the
multicast address if the address falls within a pre-defined range then the
traffic is treated as multicast and flooded on all PVCs and LAN. The
"Flood Multicast Range" is a string of octets which can be configured as:
* Empty: All multicast packets are handled as video streaming packets.
* A range: If the range is configured as >=224.0.0.1 and <=224.0.0.40 on
66 1/1553-HSC901 003/2 Uen B

PVC1 and PVC2, then all multicast packets received from PVC1 with a
destination address in this range are flooded on PVC2.
• Anonymous McastSubscriber: This field determines whether MAC and
IP address validation is performed when an end-user sends multicast
frames upstream in the network. The possible values are:
* true: end-user source IP and MAC addresses are not validated.
* false: end-user source IP and MAC addresses are validated.
• Virtual MAC: This field is used to activate the function that exchanges
the MAC addresses in the frames that pass, so that only virtual MAC
addresses, chosen by the access network are used within the access
network. The possible values are:
* mat-1-1: 1:1 (one-to-one) MAC address translation
* disabled: Original MAC addresses are used within the access network
(the use of virtual MAC addresses is disabled)
* mat-N-1: N:1 (many-to-one) MAC address translation
* mat-N-1-withLB: Like above but extra virtual MAC addresses may be
used to provide better load balancing for the Ethernet switches in the
aggregation network.
• PVC max MACs: limit for the number of MAC addresses concurrently in use.
• Downst. Flooding: Frames received from the aggregation network will
be forwarded on this PVC if the destination MAC address is unknown to
the DSLAM. The frame must be received in the same VLAN as
associated with the PVC. The possible values are:
* true: this PVC will receive ethernet frame if destination MAC is unknown.
* false: this PVC will not receive ethernet frame if destination MAC is unknown.
Gateway folder:
• Gtw MAC Filter direction: This field specifies on which traffic the
Gateway Mac filtering needs to be done. The possible values are:
* upstream: filter the gateway MAC in the upstream direction only.
* upDownstream: filter the gateway MAC in both the upstream and
downstream direction.
• Gtw Fixed Forwarding: This field specifies on which traffic the Gateway
Mac filtering needs to be done. The possible values are:
* upstream: Filter the gateway MAC in the upstream direction only.
* upDownstream: Filter the gateway MAC in both the upstream and
downstream direction.
• Gtw IP address: the ip address of the gateway.
DHCP, PPPoX, Agents folder
• PPPoE Behaviour on Link Failure: This field decides how the PPPoE
behavior should be when DSL line state changes. This field is only valid
if the "Access Method" field is set to PPPoE or PPPoX and if PPPoE is
used on uplink. Possible values are in the following range: 0...255:
* 0: PPPoE session termination message will be sent immediately.
* 255: PPPoE session termination message will never be sent.
* For any other value in the range a timer with duration of the value per
10 seconds will be started.
1/1553-HSC901 003/2 Uen B 67

• PPPoA Max Payload Option: When the end-to-end connectivity

between the BRAS and the end user is a combination of PPPoA and
PPPoE, large packet fragmentation results due to a mismatch between
the largest payloads possible by the two different types of protocols.
PPPoA supports a payload of minimum 1500 octets whereas PPPoE
supports maximum 1492 octets thus resulting in fragmentation of
packets. When this option is enabled, the IPDSLAM inserts the PPP-
Max-Payload tag (with a value of 1500) in the PADI and PADR frames
for a PPP session when a conversion from PPPoA (user end) to PPPoE
(BRAS) takes place. This facilitates both the end user and BRAS to send
packets with a payload of 1500 octets thereby minimizing/eliminating
fragmentation. This parameter is disabled by default.
• PPP MRU Subst (0..1530): using this field it is possible to 'trick' the CPE
modem to think the BRAS uses a MRU (Maximum Receive Unit) of for
instance 1500 bytes (Which it usually can).This can be used to get CPE
modems, that discards packets that exceed the standard MRU of 1492,
to forward the packets anyway. Setting this value to zero (0) disables the
function. This field is only valid if the access method is set to PPPoA.
• Dhcp Server MAC Address: It is used to convert DHCP Discover or a
Request from broadcast to unicast.
• MAC in Dhcp option (0,128-255): it represents the DHCP option code used
inserting the end-user MAC address to DHCP messages from end-user.
• Relay Agent Circuit ID Configuration: This field is used to determine
which Relay Agent configuration to use (DHCP or PPPoE). DHCP: The
relay agent adds DHCP option 82 to upstream DHCP requests, and
removes the option 82 from downstream DHCP replies. See also RFC
3046. PPPoE: The relay agent adds a vendor specific option
(AtmForum=353) to upstream PADR frames. The information is encoded
similar to the suboptions in DHCP option 82. No standard currently
exists (Juniper/BRAS interworking). Possible values are:
* notUsed: no relay-agent information will be added or removed from
the frames.
* remoteIdString: A specified string will be inserted as 'Agent Remote ID'
(sub-option 2). The parameter relayAgentString has to be set with the
string before using this configuration.
* remoteIdCisco: The 'Agent Remote ID' (sub-option 2), is encoded as
'Routed Bridge Encapsulation' specified by Cisco.
* remoteIdCustomer: The customer Id will be inserted as a string in sub-
option 2, Agent Remote ID, in the option 82 field. The parameter
DelayAgentString has to be set with the correct customer Id before using
this configuration.
* circuitIdString: Same as remoteIdString except that it will be encoded
in 'Agent Circuit ID' (sub-option 1). Example: '172.30.38.83 atm
0/1:100.33' (relay-agent=172.30.38.83, slot=0, port=1, vpi=100, vci=33)
*circuitIdCustomer: Same as remoteIdCustomer except that it will be
encoded in 'Agent Circuit ID' (sub-option 1).
* remoteIdEda: EDA specified coding of the relay agent information
68 1/1553-HSC901 003/2 Uen B

(sub-option 2). The parameters relayAgentEdaIp and

relayAgentEdaNodeId have to be set before using this option when the
IP-DSLAM is running in managed mode.
* circuitIdEda: EDA specified coding of the relay agent information (sub-
option 1). The parameters relayAgentEdaIp and relayAgentEdaNodeId
have to be set before using this option when the IP-DSLAM is running in
managed mode.
* circuitIdTR101: The standard TR-101 Access Loop Identification
Syntax will be inserted as 'Agent Circuit ID' (sub-option 1).
* circuitIfIfAlias: a specified string will be inserted as Agent Circuit ID.
The parameter Subscriber Identifier (that it is defined in the xDSL Lines
Configuration window) has to be set with the string before using this
configuration.
• Agent Circuit String input: ASCII | OCTETS: this field allows
specifying a string for the entire Agent Circuit ID.
• Agent Vendor Specific Option Mask: this field is used to specify if and
what DSL line characteristics are sent in the vendor-specific sub-option
(for DHCP this corresponds to sub-option code 9). The field allows
flexibility where none, some or all access characteristics can be selected
and sent in the Vendor Specific sub-option. If the field is set with all zero
(no entry selected) the Vendor Specific sub-option will be omitted.
By clicking on the field the window "Vendor Specific Options" will be
displayed. The operator can select/deselect the following entries:
actualDataRateUpstream - Actual Data Rate Upstream in kbps.
Type Code: 0x81; Length of field: 4 bytes
actualDataRateDownstream - Actual Data Rate Downstream in kbps.
Type Code: 0x82; Length of field: 4 bytes.
minimumDataRateUpstream - Minimum Data Rate Upstream in kbps.
minimumDataRateDownstream - Minimum Data Rate Downstream in kbps.
attainableDataRateUpstream - Attainable Data Rate Upstream in kbps.
Type Code: 0x85; Length of field: 4 bytes
attainableDataRateDownstream - Attainable Data Rate Downstream in
kbps. Type Code: 0x86; Length of field: 4 bytes.
maximumDataRateUpstream - Maximum Data Rate Upstream in kbps.
maximumDataRateDownstream - Maximum Data Rate Downstream in
kbps. Type Code: 0x88; Length of field: 4 bytes.
minDataRateLowPowerStateUpstream - Minimum Data Rate Upstream in
low power state in kbps. Type Code: 0x89; Length of field: 4 bytes.
minDataRateLowPowerStateDownstream - Minimum Data Rate Downstream
in low power state in kbps. Type Code: 0x8a; Length of field: 4 bytes.
maxInterleavingDelayUpstream - Maximum Interleaving Delay Upstream in
millisec. Type Code: 0x8b; Length of field: 4 bytes.
1/1553-HSC901 003/2 Uen B 69

actualInterleavingDelayUpstream - Actual Interleaving Delay Upstream in

millisec. Type Code: 0x8c; Length of field: 4 bytes.
maxInterleavingDelayDownstream - Maximum Interleaving Delay
Downstream in millisec. Type Code: 0x8d; Length of field: 4 bytes.
actualInterleavingDelayDownstream - Actual Interleaving Delay Downstream
in millisec. Type Code: 0x8e; Length of field: 4 bytes.
accessLoopEncapsulation - Access-Loop-Encapsulation. Type Code: 0x90;
Length of field: 3 bytes.
adslTransmissionSystem - ADSL Transmission System. Type Code: 0x91;
Length of field: 4 bytes.
• Relay Agent Remote ID Configuration: Used to determine which
Relay Agent configuration to use (DHCP or PPPoE).
DHCP: The relay agent adds DHCP option 82 to upstream DHCP
requests,and removes the option 82 from downstream DHCP replies.
See also RFC 3046.
PPPoE: The relay agent adds a vendor specific option (AtmForum=353)
to upstream PADR frames. The information is encoded similar to the
suboptions in DHCP option 82. No standard currently exists
(Juniper/BRAS interworking).
- remoteIdNotUsed, no relay-agent information will be added or removed
from the frames.
- remoteIdString, a specified string will be inserted as 'Agent Remote ID'
(sub-option 2). The parameter relayAgentString has to be set with the
string before using this configuration.
- remoteIdCustomer, the customer Id will be inserted as a string in sub-
option 2, Agent Remote ID, in the option 82 field. The parameter
relayAgentString has to be set with the correct customer Id before using
this configuration.
- remoteIdEda, EDA specified coding of the relay agent information
(sub-option 2). The parameters relayAgentEdaIp and
relayAgentEdaNodeId have to be set before using this option when the
IP-DSLAM is running in managed mode.
- remoteIdCisco, the 'Agent Remote ID' (sub-option 2), is encoded as
'Routed Bridge Encapsulation' specified by Cisco.
- remoteIdIfAlias, a specified string will be inserted as 'Agent Circuit ID'
(sub-option 1). The parameter adslIfAlias has to be set with the string
before using this configuration. If multiple services on the same line is
configured with this option, then those services will insert the same relay
agent information.
• Agent Remote String input: ASCII | OCTETS: this field allows a string
to be specified for the entire Agent Remote ID.
Filters folder
• Upstream Flow Ident: When packets arrive on a DSL line, the DSLAM
needs to determine which flow the packet belongs to. This can be done
in one of four ways. The possible values are:
* classic: PVC, (Only one flow may be associated with the PVC.)
* pbit: Pbit flow classification. The pbit value is part of the VLAN header.
70 1/1553-HSC901 003/2 Uen B

Pbit flow classification is a layer-2 classification method.

* dscp: DSCP flow classification. The DSCP field is part of the TOS field
of the IP-header. Dscp flow classification is a layer-3 classification
method.
• Upstream Flow list: This field represents a list and the priority S in
upstream flows, which are contained in/use this PVC. Each octet is a
number of a flow that exists (is active).
• Downstream Flow Ident: When packets arrive on the uplink, the
DSLAM needs to determine which flow the packet belongs to. This can
be done in one of three ways. The possible values are:
* classic: VLAN and destination MAC address
* pbit: Pbit flow classification. The pbit value is part of the VLAN header.
Pbit flow classification is a layer-2 classification method. The p-bit is
always taken from the outermost customer VLAN. If 3 customer VLAN
tags are provided, p-bit information from the 2 inner VLAN tags is
ignored.
Downstream Flow list: it is the list of upstream flows that are contained
in/use this PVC.
• ACL Enabling: This field determines if the ACL is enabled or not.
• Upstream VLAN ACL: This field is not used, for this reason it is grey colored.
• Upstream Ethertype ACL: Ether Type ACL to be used for upstream
direction. Zero means that no upstream Ether Type ACL is used for this PVC.
• Upstream IP ACL: the IP ACL for upstream direction. Zero means no
upstream IP ACL is used for this PVC.
• Downstream VLAN ACL: it specifies the VLAN ID ACL for downstream
direction.
• Downstream Ethertype ACL: it specifies the Ether Type ACL to be
used for downstream direction. Zero means that no downstream Ether
Type ACL is used for this PVC.
• Downstream IP ACL: it specifies the IP ACL for downstream direction.
Zero means no downstream IP ACL is used for this PVC.
• Subscriber MAC Filter: when the filter type is none, all packets with the MAC
addresses which are parts of the filter entries are allowed by the filter.
Downstream Flows
The Downstream Flows Configuration section includes parameters to specify
which packets are to be put in this flow and control details of policing and
scheduling this direction of flow. This application provides only one folder:
Downstream Flows. Fields relevant in a provisioning operation in each table's
row are described below.
Downstream Flows folder
• Ne Name: The name of the equipment.
• User Port: <shelf>/<slot>/<line> (<slot> is always 1).
• PVC Index: An index for the PVC.
• Flow Index: index of the flow.
1/1553-HSC901 003/2 Uen B 71

• Identifying Values (Octets): according to the flow identification criteria

selected for the PVC, (e.g. a list of p-bit (CoS) or DSCP values in the
incoming packets), the value of this field is given as a string of octets
separated by spaces. Each octet represents a matching value, that is, a
packet that contains at least one of these values is classified as
belonging to the referred flow.
• Policing: Specifies whether this flow should be policed or not (not to be
confused the ATM-level policing of cells). When done, the policing is
based upon the value of the subsequent fields.
• Sustainable Data Rate (Kbps): To carry telephone over IP, at least 192
Kbps are needed and the DSL line must be configured to at least 192
Kbps (192000 bps). Value range: 0 or 32...196608 (Kbps).
• Max Burst: the maximum allowed number of bytes in a burst. A
minimum of 250 bytes are needed to allow a complete telephony over IP
packet in one burst.
• Bytes PerRound: Number of bytes, converted to number of ATM/PTM
cells that can be transmitted from this queue for each turn (rounded to
nearest integer).The Scheduler may start transmission of a frame even
when the current credit for a queue is either negative or less than the
frame size.
• Max Queue Buffers: Max number of packet buffers allowed to be
placed in one downstream flow queue.
• Preemp Flow Enable: an option for Packet Transfer Mode (PTM).
Packets from flows marked as pre-emptive flows can pre-empt packets
from not-marked ones (i.e. normal flows). This parameter is ignored for
an ATM PVC.
• Policing Bundles (0..1): This field is used for bundling multiple flows for
policing purposes. The bundle can be made to include the selected flows
for the same line. Thus, all flows marked with the same Policing Bundle
Number will be sharing the rate in the Sustainable Data Rate and the
flows will be policed accordingly. The flows marked with the same
Policing Bundle Number must be configured with identical values for
Sustainable Data Rate and MaxBurst. Setting this parameter to '0' will
disable the policing bundling feature. This is also the default behavior.
Note that this field does not have any effect unless dfcPolicingEnable is
enabled for the flow. Flows in a PTM entry cannot be bundled with flows
in an ATM entry.
• Date & Time: Date & Time when the Command is launched.
• Ip Address: IP Address that launches the command.
• Command: possible commands are: check&modify, modify and skip.
• Result: OK | ERROR.
• Error Message: it is an error explanation, if the result was ERROR.
When the error log is a multi-line text, this field shows the last line of it.
72 1/1553-HSC901 003/2 Uen B

WRED
The WRED Application contains the main configuration parameters for a
downstream flow WRED for one VLAN priority and one end-user connection.
Each individual entry is made of User Port, PVC Index, Priority Index, Buffer
Limit and Drop Probability fields. The IP-DSLAM flow implementation allows
multiple VLAN priorities to be mapped to the same downstream flow queue
(downstream flows are configured with Downstream Flow Config Application).
Parameters in the Downstream Flow Wred Application are used to configure the
discard probability of packets with different VLAN priority in the same
downstream flow. The mechanisms Weighted Random Early Discard (WRED)
is implemented to allow configuration of discard probability of packet with
different VLAN priority. The WRED mechanism works as an extension to the
other flow mechanisms in the IP-DSLAM.
• Ne Name: the name of the equipment.
• User Port: the physical line which is mapped to the end-user line.
• PVC Index: It is the logical channel index.
• Down Flow Index: this field represents the index of the traffic queues
(from 1 to 4).
• VPI: this field represents the Virtual Path Identifier (VPI) for the specified
PVC of an end-user line. The VPI and VCI (Virtual Channel Identifier)
identifies the PVC (Permanent Virtual Circuit). The value can be
between 0 and 15; the VPI involved in the PVC.
• VCI: This field represents the Virtual Channel Identifier for the specified
PVC of an end-user line. The VCI and VPI identify the PVC (Permanent
Virtual Circuit).The value can be between 0 and 255.
• S-VLAN: This field specifies the VLAN ID to be used for the Ethernet
traffic (accordingly to 802.1Q) from and to the specified PVC. The value
can be between 0 and 4095.
• Identifying Values: the value of this field is given as a string of octets
• Priorities: This value can be between 0 and 7 (where 7 is the highest
priority). It is applicable for the amber and green thresholds.
• Buffer Limit: drop limit is specified as a percentage of the total
queue length (dfcMaxQueueBuffers) for the flow. For example, if the
flow queue can contain 100 packets and wredBufferLimit is set to
70%, then the IPDSLAM's WRED mechanism will start dropping
packets with the specific VLAN priority when more than 70 buffers from
the queue is in use. It is applicable for the amber and green thresholds.
• Drop Probability: This is used to specify the probability that a packet
with a specific VLAN priority will be dropped if the Buffer Limit has been
exceeded.The attribute itself is configured as a percentage of all packets
received with the VLAN priority. For example, if 80% drop probability has
been specified, 4 out of 5 packets with this VLAN priority will be dropped
1/1553-HSC901 003/2 Uen B 73

when Buffer Limit has been exceeded. This parameter is applicable for
the amber and green thresholds.
• Command: possible commands are: modify / skip.
• Press Apply Selected Rows to confirm the choices to the rows involved
in the command.
• Press Apply Selection to confirm the choices to the rows involved in the
command.
• Press Exit to close.
The application displays a button Check WRED Table that does a check of the
data shown in table without reading the Equipment. So, to check the
consistency of the WRED data already configured into an Equipment, first do a
Read network and then do Check WRED Table.
Upstream Flows
The Upstream Flow Configuration section includes parameters to specify which
packets are to be put in this flow and control details of policing and scheduling in
this direction of flow. This application provides only one folder: Upstream Flows
management. Fields relevant in a provisioning operation in each table's row are
described below.
Upstream Flows Management folder
• PVC Index: An index for the PVC.
• Flow Index: index of the flow.
• Identifying Values (Octets): according to the flow identification criteria
selected for the PVC, (e.g. a list of p-bit (CoS) or DSCP values in the
incoming packets), the value of this field is given as a string of octets
• Policing: Specifies whether this flow should be policed or not (not to be
confused the ATM-level policing of cells). When done, the policing is
based upon the value of the subsequent fields.
• Sustainable Data Rate (Kbps): To carry telephone over IP, at least 192
Kbps are needed and the DSL line must be configured to at least 192
Kbps (192000 bps). Value range: 0 or 32..196608 (Kbps).
• Max Burst: the maximum allowed number of bytes in a burst. A
minimum of 250 bytes are needed to allow a complete telephony over IP
packet in one burst. Value range: 64...16777215.
74 1/1553-HSC901 003/2 Uen B

• Peak Rate Kbps: This field represents the maximum allowed Peak data
rate for the flow in question. When 2 Rate 3 Color Limiter functionality is
enabled the value of this field should be greater than the value specified
in Sustainable Data Rate. The rate must be lower than or equal to the
configured line rate and needs to be configured in steps of 32000 bps. A
value of zero for this object is valid only when ufcRemarkingPbit is set to
-1, this means that 2 Rate 3 Color Limiter is disabled and remarking will
not be done. If ufcRemarkingPbit is set to a value other than -1 then
ufcPeakDataRate value should be greater than ufcSustainableDataRate
otherwise the flow configuration is considered to be an invalid
configuration.
• Peak Burst bytes: This field represents the maximum allowed number
of bytes in a peak burst. When 2 Rate 3 Color Limiter functionality is
enabled the value of this object should be greater than the value
specified in Max Burst.
• Remark Pbit: For 2 Rate 3 Color Rate Limiter, this fields specifies the
VLAN priority that will be written in the upstream traffic forwarded by this
flow, whose data rate is greater than Sustainable Data Rate and less
than Peak Data Rate. Allowed values are:
-1: 2 Rate 3 Color Limiter functionality is disabled and traffic with data
rate greater than ufcSustainableDataRate is dropped.
0-7: VLAN priority in the redirecting traffic is overwritten with the value
specified. Note that Remarking Pbit can not be set to the same value as
the flow Index of the current flow.
• Command: modify, skip.
• Error Message: An error explanation, if the result is ERROR.
Lines
The Lines application contains the main configuration parameters for a downlink
line. Each individual entry in line Entry is indexed with User Port: the end-user's
physical line. This application provides only one folder: Lines management.
Lines Management folder:
• Broadcast Storm Control (BSC): A broadcast storm means that your
network is flooded with constant broadcast or multicast traffic. Broadcast
storms can eventually lead to a complete loss of network connectivity as
the packets proliferate. This field allows enabling the BSC
(limitToThreshold) or disabling it.
• Broadcast Storm Control Threshold: It a numeric value in the range
1...500 expressed in broadcast packets/sec. When this value is passed
1/1553-HSC901 003/2 Uen B 75

and the field ""Broadcast Storm Control" is enabled, all broadcast traffic
is limited to this value Broadcast traffic above is dropped.
• Multicast Storm Control: This field is the Multicast Storm Control
(MSC) function. The possible values are:
disable: MSC is disabled.
limitToThreshold: MSC is enabled that is multicast is limited to Multicast
Storm Control Threshold field
• Multicast Storm Control Threshold: It a numeric value in the range
1..500 expressed in multicast packets/sec. When this value is passed
and "MultiCast Storm Control" field is enabled, all multicast traffic is
limited to this value. Multicast traffic this value is dropped.
• ATM Traffic Separator Only: this field is used to enable a QoS (Quality
of Service) model where ATM is only used as a separation for the traffic
opposed to the ordinary ATM functionality where also QoS is handled.
The Possible values are:
false: The standard ATM QoS model is used.
true: ATM QoS is disabled and ATM is only used for traffic separation.
This model is used where multiple PVCs are used towards a CPE and
an Ethernet scheduling mechanism is desired. This field can only be
changed if all PVCs on this line are disabled.
• Command: modify
• Error Message: An error explanation, if the result was ERROR. When
the error log is a multi-line text, this field shows the last line of it.
Multicast Filters
The Multicast Filter Application contains multicast filter information for PVC.
Each entry describes a range of consecutive multicast group addresses which
are allowed or disallowed, depending on the value of Filter Type, to be
forwarded on the PVC. Each individual entry is made of User Port, PVC Index,
the First Address of a multicast group Internet address range, the Last Address
of the multicast group and VLAN ID and VLAN Priority fields. This application
provides only one folder: Multicast Filters.
Multicast Filters folder:
• PVC Index: index of the logical channel that the traffic in question is
coming from. The logical channel contains service-specific settings such
as the type of access method to support and multicast settings.
• Filter Type: This field specifies whether the multicast filter is positive or
negative. If this field is positive, the managed device is allowed to
forward multicast group Internet addresses. If this field is negative, the
76 1/1553-HSC901 003/2 Uen B

managed device is allowed to forward all multicast group Internet

addresses except the ones specified in the table.
• First Address: This field represents the first address in the multicast
group Internet address range.
• Last Address: This field represents the last address in the multicast
group Internet address range. The value for this field must be an equal
to or higher than the value of the field "First Address" before the settings
are into operation.
• VLAN ID: This field represents the Vlan ID to be used for the multicast
traffic on a multicast group Internet address range, from and to the
specified PVC. The value -1 is a nil-value indicating that the outer
service VLAN ID is used for the multicast traffic.
• VLAN Priority: This field represents the priority (accordingly to 802.1Q)
that should be used for the multicast frames to and from the specified
PVC. The value can be between 0 and 7 (where 7 is the highest
priority).The value -1 is a nil-value indicating that the outer service VLAN
priority is used for the multicast traffic.
• Command: negativeFilter, positiveFilter, addAddressRange,
deleteAddressRange.
• Annotations column is used to write some note.
Subscriber IP Filters
The Subscriber IP Filter Application contains Subscriber IP filter information for
PVC. Each entry describes a range of consecutive Subscriber IP addresses
which are allowed to forward traffic on the PVC. Each individual entry is made of
User Port, PVC Index, the first address "First IP Address" of a range and the
"Last IP Address" of the range. This application provides only one folder:
Subscriber IP Filters.
Subscriber IP Filters folder:
• Ne Name: The name that the equipment to be accessed has in the
Management environment.
• PVC Index: index of the logical channel that the traffic in question is
coming from. The logical channel contains service-specific settings such
as the type of access method to support and multicast settings.
• Filter Type: this field specifies whether the subscriber IP filter is positive
or disabled. If the filter is positive, the managed device is allowed to
forward traffic from/to end-users if their IP address is specified. If the
subscriber IP filter is disabled, the managed device will make no filtering
on end-user IP. Whether the subscriber IP filter is positive or disabled is
specified per PVC.
1/1553-HSC901 003/2 Uen B 77

• First IP Address: This field represents the first address in the end-user
Internet address range.
• Last IP Address: This field represents the last address in the end-user
Internet address range. This value must be a equal to or higher than of
the value of the field "First IP Address
• Ne Ip Address: IP Address that launches the command.
• Command: enableSubsIpFilter, disableSubsIpFilter, addAddressRange,
deleteAddressRange
VLAN ACL
Access Control Lists (ACLs) provides a mechanism to support enhanced and
flexible filtering criteria on a per flow basis (PVC). Each ACL is made up of a list
of ACL rules which contains multiple parameters to be matched against the
packet contents.
The VLAN ACL (VACL) is an ACL that specifies traffic parameters based on
Layer 3 and above information that is applied to a Layer 2 VLAN or in some
instances a Layer 2 interface. These lists offer a benefit over traditional router
access lists of being applied in hardware and therefore being faster than
traditional ACLs. They also add the capability to filter traffic within an IP subnet
and beyond the IP subnet.
The possible actions currently defined are forward or drop the packet. If no rule
matching the packet is found within the ACL the packet is discarded.
Each row in the application's table is a Rule of an ACL. This application shows
both ACLs with rules attached to them and ACLs without any attached rule. The
latter case may be that of an ACL from which all attached Rules have been
removed. Removing all the Rules attached to an ACL does not automatically
remove the ACL. This application provides only one folder: VLAN ACL.
VLAN ACLs folder
• Subrack/Slot: subrack/slot of the XDSL card where the specific Vlan
Access Control List is applied.
• ACL id: index of this Access Control List. Value provided by user.
• Rule id: The index of the Rule in ACL that specifies the position. The
order of the rules is very important. The rules are processed in a top
down order. Once a match is found, no further rules are processed. If no
match is found, the packet is dropped.
• Match Action: Only “permit” filtering is allowed.
• Vlan IdMin: This field is used to set the VLAN ID to be permitted.
• Vlan IdMax: This field is not used.
78 1/1553-HSC901 003/2 Uen B


• Command: The possible commands are: createAcl / destroyAcl /
addRule / deleteRule / modify
• Result: OK | ERROR
• Error Message: An error explanation, if the result is ERROR.
IP ACL:
flexible filtering criteria on a per flow basis (PVC). Each ACL is made up of a list of
ACL rules which contains multiple parameters to be matched against the packet
contents. When a packet is received in a PVC, the ACL is evaluated and
compared to the content of the packet. If a match is found the action associated
with the rule is executed. ACL rules in an ACL are evaluated in order, so that the
first rule matching the packet determines the action to be done on the packet. The
possible actions currently defined are forward or drop the packet. If no rule
matching the packet is found within the ACL the packet is discarded. The IP ACL
application is used to browse, create, destroy and modify IP Access Control List.
remove the ACL. This application provides only one folder: IP ACLs.
IP ACLs folder
• Ne Name: name of the equipment.
• Subrack/Slot: subrack/slot.
• ACL id: index of this Access Control List. It must be provided by user.
• Rule id: the Rule in ACL that specifies the position. The order of the
rules is very important. The rules are processed in a top down order.
Once a match is found, no further rules are processed. If no match is
found, the packet is dropped. This value must be provided by user and is
in the range 1..64.
• Match Action: Action to be performed when a packet matches any of
the specified rules. The possible values are permit and deny.
• Ip Protocol: the layer above IP to which the IP packet data should be
passed (icmp-1, ignp-2, tcp 6, udp 17, any-1)
• Source Ip Addr Min: the first element of the intended IP source address
range. IP packets from hosts in that range will be filtered, depending on
the value of the action field.
• Source Ip Addr Max: the last element of the intended IP source
address range. IP packets from hosts in that range will be filtered,
depending on the value of the action field.
• Source Ip Actual Range: the actual element of the intended IP source
1/1553-HSC901 003/2 Uen B 79

The filtering is not indicated by the values Source Ip Addr Min and Source Ip
Addr Max, but from the range indicated in Source Ip Actual Range field. This
value is evaluated automatically from LCT.
• Destination Ip Addr Min: The first elements of the intended IP source
• Destination Ip Addr Max: the last element of the intended IP source
addresses range. IP packets from hosts in that range will be filtered,
• Destination Ip Actual Range: the actual element of the intended IP
source address range. IP packets from hosts in that range will be
filtered, depending on the value of the action field.
• Source Port Operator: how a packet's source TCP/UDP port number is
to be compared. The possible values are:
noOperator: no comparison is to be made with source TCP/UDP port number.
equal: equal to comparison.
range: range-based comparison.
• Source Port: the source port number of the TCP or UDP protocol, the
starting port number of the port range.
• Source Port Range: the closing source port number of TCP or UDP protocol.
• Destination Port Operator: how a packet's destination TCP/UDP port
number is to be compared. The possible values are:
- noOperator: no comparison is to be made with destination TCP/UDP port number.
- equal: equal to comparison.
- range: range-based comparison.
• Destination Port: the destination port number of TCP or UDP protocol.
• Destination Port Range: the closing destination port number of the
TCP or UDP protocol.
• Tcp Flags: the value of the TCP Control code/flags. The various bit
positions are:
1 - F, FIN End of data flag.
2 - S, SYN Synchronize sequence numbers flag.
3 - R, RST Reset connection flag.
4 - P, PSH Push flag.
5 - A, ACK Acknowledgment number valid flag.
6 - U, URG Urgent pointer valid flag.
• Tcp Flags Mask: This object represents value of the TCP Control
code/flags mask. The Tcp Flags Mask specifies which of the TCP
Control flags specified in Tcp Flags to match.
The various bit positions are:
1 - F,FIN End of data flag.
2 - S,SYN Synchronize sequence numbers flag.
3 - R,RST Reset connection flag.
4 - P,PSH Push flag.
5 - A,ACK Acknowledgment number valid flag.
80 1/1553-HSC901 003/2 Uen B

6 - U,URG Urgent pointer valid flag.

The Tcp Flags Masks used in combination with Tcp Flags and Tcp Flags
Match Method.
• Tcp Flags Match Method: This field specifies whether all (matchAll) or
just one or more (matchAny) TCP flags must be correct to have a match
in the TCP flags part of the rule.
• Icmp Type: value of ICMP type. ICMP type defines the ICMP message
that is being passed.
• Icmp Code: value of ICMP code. ICMP type may have several sub
messages. A sub message is called an ICMP code.
• Igmp Type: value of IGMP type. IGMP type defines the IGMP message
that is being passed.
• Command: createAcl / destroyAcl / addRule / deleteRule / modify
Ether Type ACL:
flexible filtering criteria on a per flow basis (PVC). Each ACL is made up of a list
of ACL rules which contains multiple parameters to be matched against the
packet contents. When a packet is received in a PVC, the ACL is evaluated and
compared to the content of the packet. If a match is found the action associated
with the rule is executed. ACL rules in an ACL are evaluated in order, so that the
first rule matching the packet determines the action to be done on the packet.
The possible actions currently defined are forward or drop the packet. If no rule
matching the packet is found within the ACL the packet is discarded.
The Ether Type ACL application is used to browse, create, destroy and modify
Ether Type Access Control List.
remove the ACL. This application provides only one folder: Ether Type ACLs.
Ether Type ACLs folder:
• Subrack/Slot: subrack/slot of the XDSL card where the specific Vlan
Access Control List is applied.
• ACL Id: index of this Access Control List. Value provided by user.
• Rule id: The index of the Rule in ACL that specifies the position. The
order of the rules is very important. The rules are processed in a top
down order. Once a match is found, no further rules are processed. If no
1/1553-HSC901 003/2 Uen B 81

match is found, the packet is dropped. This value must be provided by

user.
• Match Action: Action to be performed when a packet matches any of
the specified rules.
• Ether Type (Hex): This number indicates the Ethernet type to match.
Zero means any Ethernet type will match the rule. A list of standardized
Ethernet type numbers is maintained by IANA (Internet Assigned
Numbers Authority).
• Command: createAcl / destroyAcl / addRule / deleteRule / modify
Bridge Line Card:
This Bridge Global Application contains the main configuration parameters for a
single xDSL Card. Parameters that can be written are: Max Ethernet Frame
Size, MAC, and Filter aged time. Other parameters are read only. This
application provides only one folder: Bridge Line Card Parameters
Management.
Bridge Line Card Parameters Management folder:
• User Subrack/Slot: subrack/slot.
• Max Ethernet Frame Size: This field specifies the maximum frame size
that the IP DSLAM will send up-stream in the access network. Longer
frames will be discarded. The specified size covers the whole frame,
including Ethernet header, VLAN-tag(s) and 4 bytes of CRC.
• MAC Filter Aged Time (sec): This field specifies in seconds the
maximum age of inactive MAC address entries in the end-user MAC
filter for access methods PPPoE and TLS.
• Domain: This field specifies 6 of the 8 bits in the first byte in the virtual
Mac address. (The remaining two bits are the multicast bit and the
globally/locally administrated bits which equals 01 to identify the locally
administrated unicast address known as the virtual Mac address)
• Node Id Ex: this field specifies the virtual Mac address 'Node ID
Extended' in the virtual Mac address. With the Node ID Extended, it is
possible to identify the origin of an ethernet frame, even when the IP
DSLAM has been exchanged with a new IP DSLAM, with a new Mac
address.
• Network Element ID: This field represents an identifier for this network
element of the Domain. The Virtual MAC Domain defines a virtual MAC
addressing scheme of three identifiers:
* Node Id Ex, Slot, and Port Offset. Supported access methods are
dhcp, staticIp and pppoe. virtualMacEnable must be set to 1:1 MAC
82 1/1553-HSC901 003/2 Uen B

address translation. Virtual MAC Domain 60 must be selected by

virtualMacAddressDomain. macAddressCountLimit must be set to a limit
equal or lower than 64.
• Slot: This field identifies a group of IPDSLAM's aggregated below e.g. a switch.
• Port Offset: The port offset value enables each IPDSLAM within a slot
to uniquely identify every line.
• Node Id: This field is the virtual Mac address Node ID; it specifies the
last 3 bytes in the virtual Mac address. With the Node ID, it is possible to
identify the origin of an ethernet frame, even when the IPDSLAM has
been exchanged with a new IP DSLAM, with a new Mac address.
• Relay Agent EDA Ip: This field specifies the IP address inserted in the
relay agent information when remoteIdEda is used (see 'Relay Agent
Configuration' description). Zero must be used when the IP-DSLAM is
running standalone; in this case the IP-DSLAM will insert its own IP
address into the relay agent information. If the IP-DSLAM is not running
standalone the IP address of the controlling node (e.g. EAN or MSAN)
must be specified in this field.
• Relay Agent EDA Node Id: This field specifies the NodeId inserted in
the relay agent information when remoteEdaId is used (see 'Relay Agent
Configuration' description). The layout of the NodeId field is dependant
on the IPDSLAM configuration.
• Access Node Identifier String: This parameter specifies the string to be
used as the Access-Node-Identifier in the Agent Circuit ID. This is only valid
if "Relay Agent Configuration" is set to "circuitIdTR101". The standard TR-
101 Access Loop Identification Syntax will be inserted as Agent Circuit ID
(sub option 1) in upstream DHCP and PPPoE messages.
• Command: modify
Bridge Common
The Bridge Common application contains the configuration parameters that
apply to all xDSL cards. Editable parameters are: Virtual MAC Domain, Domain
62 Node Id, Domain 60 Network Element Id, Relay Agent EDA IP, Access Node
identifier string. This application provides only one folder: Bridge Common
Parameters Management.
Bridge Common Parameters Management folder:
• Domain: This field specifies 6 of the 8 bits in the first byte in the virtual
Mac address. (The remaining two bits are the multicast bit and the
1/1553-HSC901 003/2 Uen B 83

globally/locally administrated bits which equals 01 to identify the locally

administrated unicast address known as the virtual Mac address)
• Node Id: This field is the virtual Mac address Node ID; it specifies the
last 3 bytes in the virtual Mac address. With the Node ID, it is possible to
identify the origin of an ethernet frame, even when the IPDSLAM has
been exchanged with a new IP DSLAM, with a new Mac address.
• Mng. Suggested Node Id: This is a read only field and it may be empty
or filled with None.
• Network Element ID: This field represents an identifier for this network
element of the Domain. The Virtual MAC Domain defines a virtual MAC
addressing scheme of three identifiers:
* Node Id Ex, Slot, and Port Offset. Supported access methods are
dhcp, staticIp and pppoe. virtualMacEnable must be set to 1:1 MAC
address translation. Virtual MAC Domain 60 must be selected by
virtualMacAddressDomain. macAddressCountLimit must be set to a limit
equal or lower than 64.
• Relay Agent EDA Ip: This field specifies the IP address inserted in the
relay agent information when remoteIdEda is used (see 'Relay Agent
Configuration' description). Zero must be used when the IP-DSLAM is
running standalone; in this case the IP-DSLAM will insert its own IP
address into the relay agent information. If the IP-DSLAM is not running
standalone the IP address of the controlling node (e.g. EAN or MSAN)
must be specified in this field.
• Access Node Identifier String: This parameter specifies the string to
be used as the Access-Node-Identifier in the Agent Circuit ID. This is
only valid if "Relay Agent Configuration" is set to "circuitIdTR101". The
standard TR-101 Access Loop Identification Syntax will be inserted as
'Agent Circuit ID'(sub option 1) in upstream DHCP and PPPoE
messages.
• Command: modify
xDSL Bridge Management buttons:
This paragraph describes the buttons:
You must press Read Network to find connections on each NE in the list. The
property data of each found entry are transparently stored into the local
persistent cache. If you instead press the Read Local Info button, the same
information is taken from the local cache.
Search Criteria
None: No selection criteria applied. All PVCs will be retrieved with their
properties.
84 1/1553-HSC901 003/2 Uen B

Manual: Search criteria will be specified by hand, entering input by means of

provided spinner fields. Search will be based on: shelf, slot (range: 1-21), port
(1-64, all), pvc (1-8, all).
Forced: Search will be based on a list of value pairs {{line pvc} {line pvc} ...}. If
any, provided by an external launcher application as a command-line option:
-indexes {{line pvc} {line pvc} ...} If this option is selected in a context where no
such option exists, no data will be obtained.
2.4.14.2 xDSL Bridge Survey
PATH: (Configuration -> IP / Ethernet Management -> XDSL Bridge Survey)

This tool allows checking the bridge features in the Equipment. It is composed
by the following applications and each one contains one folder as shown in the
window below:
• PVC Status Survey;
• MAC History Survey;
• Mcast Group Survey;
• Subscriber Info Survey.
PVC Status Survey

This application is used to have a look at the read-only state variables in the
PVC table. Each entry is indexed with user port and PVC Index.
• User Port: end-user's physical line, which is mapped to the end-user line.
• PVC Status: This field shows the result of the latest 'ATM PVC Test' and
the general status of the PVC. The possible values are:
* notUsed: either missing PVC configuration (at least Peak Cell Rate has
to be specified) or line is not using this entry since a different transfer
mode is currently used (i.e. ATM vs. PTM).
1/1553-HSC901 003/2 Uen B 85

* lineDown: line is down.

* testDisabled: the line is ready to start an ATM PVC Test session.
* testing: an ATM PVC Test is in running.
* failedF5etoe: no reply received on for the ATM PVC test cell.
* ok: either test succeeded for this PVC (ATM) or service configured
correctly (PTM).
* createFailed: due to configuration- or resource failure.
Please note that even when failedF5etoe the PVC could still be usable because
the test might not be supported by all CPEs.
Note that testDisabled, testing and failedF5etoe are only used with ATM.
• Down FrameCount: this field contains the total number of unicast
packets received from the network and sent to the end user on the
specified PVC.
• Upst FrameCount: This field contains the total number of unicast
packets received from end-user on specified PVC and sent to network.
• Down ByteCount: This field contains the total number of unicast bytes
forwarded to the end-user on the specified logical channel.
• Upst ByteCount: This field contains the total number of unicast bytes
received from the end-user on the specified logical channel.
• Encaps Protocol: it specifies the encapsulation protocol used on top of
the AAL5, according to RFC2684. The possible values are:
* llc: Logical Link Control, it allows multiple protocols to run over one
virtual circuit with a reasonable amount of overhead.
* vcmux: Virtual Circuit Multiplexer, it allows only one protocol to run per
virtual circuit and uses less overhead than LLC. The value is auto-
detected based on the packets received from the CPE modem.
• PPP Variant: The actual PPP variant chosen based on the packets
received from the CPE modem. The value is only valid if "access
Method" is set to "pppox".
• DHCP Status: This field indicates the result of testing availability of
DHCP Server support within connection. The value is updated only
during IP connectivity Test.
• GTW Status: This field indicates the result of testing availability of
default gateway for connection. The value is updated only during an IP
Connectivity Test.
• Down Frame/sec: This field contains the total number of unicast
packets per second forwarded to end-user on specified logical channel.
• Upst Frame/sec: This field contains the total number of unicast packets
per second received from the end-user on the specified logical channel.
• Down Bit/sec: This field contains the total number of unicast bits per
second forwarded to the end-user on the specified logical channel.
• Upst Bit/sec: This field contains the total number of unicast bits per
second received from the end-user on the specified logical channel.
• Access Node Ip Address: IP Address of the equipment
86 1/1553-HSC901 003/2 Uen B

MAC History Survey

This application is used to have a look at the end-user MAC addresses table.
Each individual entry is indexed with User Port, PVC Index, and MAC Address.
• User Port: the end-user's physical line, which is mapped to the end-user line.
• MAC address: the MAC address of the end-user.
• Last Seen: the timestamp which indicates the time when the end-user
MAC address was last seen.
• Status: The value can be either Active or Inactive. If Active indicates
that the end-user is currently connected and Inactive shows the MAC of
a disconnected end-user.
• Access Node Ip Address: IP Address of the equipment
Mcast Group Survey
This application will show the IGMP membership information for each Multicast
Group Address learned by IGMP snooping on a certain xDSL card.
Each individual entry in the table will show:
• The end-user line.
• PVC index (logical channel that the traffic in question is going to.
The logical channel contains service-specific settings such as the type of access
method to support and multicast settings).
The (McastGroup) VlanId represents the VLAN ID on which the multicast group
was discovered. The (McastGroup) Address represents the IP address on which
the multicast group was discovered. The (McastGroup) Host MAC Address
represents the MAC address of a host that is a member of the multicast group.
The (McastGroup) Source Filter IP Address represents an explicit source IP
address from where multicast traffic is to be received. Each entry in this
application's table contains IGMP membership information for each Multicast
Group Address learnt by IGMP Snooping. With IGMP Snooping enabled, the IP
DSLAM can 'listen in' on the IGMP conversation between IP Multicast Hosts and
Routers, to learn the group memberships. When it hears an IGMP Join/Report
from a host for a given multicast group, the IP DSLAM adds the host's MAC
address to the Source MAC Address List for that group. And, when the IP
DSLAM hears an IGMP Leave, it removes the host's MAC address entry. Thus
multicast traffic of a group is forwarded only to the members of that group,
thereby reducing the network traffic. The Mcast Group Information entry is
created for each multicast group learnt on PVC, when any end-user joins the
multicast group.
• User Port: end-user's physical line, which is mapped to the end-user line
• PVC Index: It is the logical channel index
• Vlan Id: the VLAN in which the multicast group is learned.
• Address: the IP address of the multicast group learned.
1/1553-HSC901 003/2 Uen B 87

• Host MAC Address: the MAC address of the host which is a member of
the Multicast Group.
• Source Filter IP Address: IGMP Version 3 (IGMPv3) adds support for
'source filtering', which enables a multicast receiver host to explicitly signal
sources from which they want to receive traffic. This field is specified in the
IGMPv3 Membership Reports and indicates the source address from which
traffic is expected. Groups for which IGMPv1/v2 Membership Reports are
received are considered to have a this field of 0.0.0.0.
• IGMP Msg Type: the type of IGMP messages that are transmitted and
received for the Multicast Group.
• IGMP Msg Up Time: the time elapsed since the "IGMP Msg Type" was
first received/transmitted.
• Access Node Ip Address: IP Address of the equipment.
Subscriber Info Survey
This application is used to have a look at the Subscriber's Info table. Each line
contains a list of end-user information that the IP-DSLAM has dynamically
learnt. From the list it is possible to get the relationship between end-user MAC
and IP addresses.
• User Port: the end-user's physical line, which is mapped to the end-user line.
• MAC address: MAC address of the end user learnt by the IPDSLAM.
• IP address: For StaticIP, DHCP and DHCPIP over ATM access
methods, relationship between MAC address of the end-user and IP
address of the end-user is maintained in the IP-DSLAM. For these three
access methods, this field will contain the IP address of the end-user.
For other access methods, this field will contain 0.0.0.0 value.
• Virtual Mac: virtual MAC address of end-user generated by IP-DSLAM.
• DHCP Lease Time: it represents the IP address lease time for the
subscriber when DHCP is used as access method.
• GTW Fixed Forwarding: it indicates whether the PVC is configured to
use Fixed Forwarding. There are two possible values:
true: fixed forwarding is enabled.
false: fixed forwarding is disabled.
• Gateway Ip: IP address of the gateway used by the end-user.
• Gateway MAC: MAC address of the gateway used by the end-user
which is learned by the IP-DSLAM.
• Access Node Ip Address: IP Address of the equipment.
88 1/1553-HSC901 003/2 Uen B

2.4.14.3 IP-CP Static Forwarding Database
PATH: (Configuration->IP / Ethernet Management->IP-CP Static Forwarding DB)

This is a tool to find out and/or change the bridge forwarding setup (also known
as VLAN FILTERING setup) on an EDA class device. The local cache can then
be searched for data matching a pattern (in the syntax defined by Structured
Query Language), and data can be extracted in a sorted form or selected
depending on the result of a comparison. Data can be stored either in an internal
format, or as Comma Separated Value, Excel (TM_-compatible files). Data
obtained from SNMP are anyway collected in a local persistent memory,
grouped by inspected equipment names, so that they can be reviewed from
inside the application at a later time. The tool is composed by the following 2
folders: FDB Unicast Setting, FDB Multicast Setting.
In the FDB Unicast Setting folder, the following fields are present:
1. Insert in the Ne Name the name or the IP address of the Equipment.
2. Insert in the Fdb Id (VLAN) an identifier for the database.
3. Insert in the Static Unicast Address an address in hexadecimal format. (e.g.
0A:0B:0C:0D:0E:0F).
4. Insert in the Receive Port Interface Name a name for the unicast address.
5. Insert in the Allowed to go to Interface Names a name for each bridge port, In
order to fill this field the following table must be compiled by clicking in the
"Allowed to Go to Interface Names.
1/1553-HSC901 003/2 Uen B 89

In order to import the data click on Read NE button select the desired ports and
click on Accept selected entries button.
6. Insert in the Static Unicast Status the type of connection. (permanent,
deleteOnReset, deleteOnTimeout, invalid)
7. Data&Time column displays the data and time.
8. IP Address displays the IP address of the Equipment.
9. Result and Error Message columns are used to have a feedback about the
configuration.
10. In order to apply the modifications select the line with the right mouse button and
select Apply.
In the FDB Multicast Setting the following fields are present:
1. Insert in the Ne Name the name or the IP address of the Equipment.

2. Insert in the Fdb Id (VLAN) an identifier for the database.
3. Insert in the Static Multicast Address an address in hexadecimal format.
(e.g. 0A:0B:0C:0D:0E:0F)
4. Insert in the Receive Port Interface Name an Interface name for the multicast port.
5. Insert in the Allowed to go to Interface Names an Interface name for each
bridge port. In order to fill this field the following table must be compiled by
clicking in the Allowed to go to Interface Names cell.
90 1/1553-HSC901 003/2 Uen B

In order to import the data click on Read NE button, detect the ports that you do
not want select, delete them and click on Accept selected entries to confirm, or
Close to exit. Other buttons are present to clear /read information.
6. Insert in the Forbidden Ports Interface Names a name for each bridge port,
not yet configured. In order to fill this field the following table must be compiled
by clicking in the Forbidden Ports Interface Names cell.
In order to import the data click on Read NE button select the desired ports and
click on Accept selected entries button.
7. Desired Status displays the type of connection. (Permanent, deleteOnReset,
deleteOnTimeout, invalid).
9. Display in the IP Address the IP address of the Equipment.
configuration.
11. In order to apply the modifications select the line with the right mouse button and
select Apply.
2.4.14.4 IP-CP Static VLAN
PATH: (Configuration->IP / Ethernet Management-> IP-CP Static VLAN)

This is a tool to read/create/destroy the bridge static VLANs on a EDA class
device, at the same time defining the attached policies, by means of policy
profile names, and the required flag to enable/disable learning. VLANs on the
EDA class device have to be configured by management.
1/1553-HSC901 003/2 Uen B 91

Static VLAN’s application
1. Insert in the Ne Name column the name or the IP address of the Equipment.
2. Insert in the S-VLAN Id column an identifier for the VLAN.
3. Insert in the S-VLAN Name column the name of the VLAN.
4. Choose in the Learn scroll list if the Equipment learns the MAC address.
Possible values are 'true' and 'false'.
5. Select in the Command column field the action to be executed. The possible
actions are: create, destroy, set learning and none.
6. Data&Time column displays the data and time when a retrieve operation has
been performed.
7. Display in the IP Address column the IP address of the Equipment.
8. The Result and Error Message columns are used to have a feedback about
the configuration.
9. The Annotations column is used to write some note about the operation.
10. Press Apply Selected Rows to confirm the choices.
11. Press Exit to close.
Ports application
This is a tool to find out an/or change the static VLAN port membership setup on
a EDA class device
92 1/1553-HSC901 003/2 Uen B

1. Insert in the Ne Name column the name or the IP address of the Equipment.
2. Insert in the S-VLAN Id field, the VLAN-ID of the VLAN attached to the egress
port displayed in the User Port Interface Name column.
3. Insert in the S-VLAN Name column the name of the VLAN.
4. Insert in the User Port Interface Name column a port which is permanently
assigned to the egress list for this VLAN by management. Every port in this list
is an existent bridge port. In order to fill this field, the following table must be
compiled by clicking in the User Ports Interface Names cell.
In order to import the data click on Read NE button, select the port and then
click on Accept selected entries button to confirm, press Close to exit from this
application and coming to the VLAN user port membership.
5. In the Tagging field is possible to specify if the referred port should transmit
egress packet for this VLAN as untagged. Possible values are yes or no.
6. Insert in the Command column field the action to be executed. (addPort, delete
Port, setTagging).
8. Display in the IP Address column the IP address of the Equipment.
1/1553-HSC901 003/2 Uen B 93

configuration.
10. Annotations column is used to write some note about the operation.
11. Press Apply selected lines to confirm the choices.
Static VLANs Management buttons
In the upper window three buttons are displayed:
Read Network Info: the VLAN's data are obtained by the Equipment
Read Local Info: the same data are taken from the local cache.
Look VLANs: it allows you to select which VLANs to read from beforehand.
2.4.14.5 Current Forwarding Database Surveillance
PATH: (Configuration-> IP/Ethernet Management ->IP-CP Current Forwarding DB Survey)

The Current Forwarding Database view retrieves stores and displays VLAN
forwarding setup on the Equipment.
The folder Current FDB is composed by the following fields:

1. Ne Name: the name of the Equipment or the IP address of the Equipment.
2. FDB Id: The identity of this Filtering Database.
3. FDB Address: a unicast MAC address for which the device has forwarding
and/or filtering information.
4. FDB Status: this column can assume several values, according to the status of
this filtering/forwarding database.
• other (1) - none of the following. This may include the case where some
other MIB object (not the corresponding instance of Fdb Port, or an entry
in the Static Unicast Table) is being used to determine if and how frames
addressed to the value of the corresponding instance of
dot1qTpFdbAddress are being forwarded.
94 1/1553-HSC901 003/2 Uen B

• invalid (2) - this entry is no longer valid (e.g., it was learned but has
since aged out), but has not yet been flushed from the table.
• learned (3) - the value of the corresponding instance of Fdb Port was
learned and is being used.
• self (4) - the value of the corresponding instance of Fdb Mac Address
represents one of the device's addresses. The corresponding instance of
Fdb Port indicates which of the device's ports has this address.
• mgmt (5) - the value of the corresponding instance of Fdb Mac Address
is also the value of an existing instance of dot1qStaticAddress.
5. Port: the port number of the port on which a frame having a source address
equal to the value of the corresponding instance of MAC Address has been
seen. A value of 0 indicates that the port number has not been learned but that
the device does have some forwarding/filtering information about this address.
6. Data and Time: the data and the time obtained from the Inventory.
7. IP Address: the IP address of the Equipment.
9. Press Exit to close the application.
10. Read Network: the data are obtained by the Equipment
11. Read Local Info: the data are taken from the local cache.
2.4.14.6 RSTP/MSTP Configuration
PATH: (Configuration -> IP/Ethernet Management -> RSTP/MSTP Configuration)

The Multiple Spanning Tree Protocol (MSTP) has been developed to provide an
efficient means of supporting the multiple instances of Spanning Tree Protocol
(STP) required for deploying numerous VLANs in a switched Ethernet LAN.
Instead of a separate instance of STP for each VLAN (as PVSTP does), MSTP
provides for a grouping of VLANs to share a common instance of STP.
So, several VLANs can be mapped to a small number of STP instances.
This mainly allows the MSTP to provide a traffic load balancing depending on
the VLANs the traffic belongs to. Moreover it assures, as the RSTP does, the
path reliability.
Its behavior is almost the same of that foreseen by the RSTP with the following
difference:
MST allows the user to map multiple VLANs to the same MST instance, but a
VLAN can be mapped to one and only one MST instance.
This management application allows the network operator to view and modify
the configuration and status for Multiple Spanning Tree Protocol running in each
bridge group.
RSTP Bridge
RSTP Bridge is an application useful to manage RSTP Protocol Bridge
parameters on the NE.
1/1553-HSC901 003/2 Uen B 95

• NE: name or IP address.

• Bridge Index: index that uniquely identifies the bridge.
• Protocol Specification: An indication of what version of the Spanning
Tree Protocol is being run.
• Bridge Id: Bridge Group Id.
• Priority: this field can assume value (multiple of 4096) between 0 and
65525 and 4000.
• Designated Root: bridge identifier of the root of the spanning tree as
determined by the Spanning Tree Protocol as executed by this node.
• Root Cost: The cost of the path to the root as seen from this bridge.
• Root Port: The port number of the port which offers the lowest cost path
from this bridge to the root bridge.
• Max Age: Maximum number of seconds a bridge waits without receiving any
spanning tree configuration messages before attempting reconfiguration.
• Hello Time: The amount of time between transmission of Configuration
Bridge PDUs, if this bridge group acts as the root of the tree
• Hold Time: This time value determines the interval length during which no
more than two Configuration bridge PDUs shall be transmitted by this node.
• Forward Delay: The amount of time a bridge interface stays in
listening/learning state before moving to forwarding state.
• Admin Status: it specifies if the procedures are enabled or disabled on
a particular bridge group.
• Bridge Max Age (600-4000): The value that all bridges use for MaxAge
when this bridge is acting as the root.
96 1/1553-HSC901 003/2 Uen B
• Bridge Hello Time (100-1000): The value that all bridges use for Hello
Time when this bridge is acting as the root.
• Bridge Forward Delay (400-3000): The value that all bridges use for
Forward Delay when this bridge is acting as the root.
• Version: version of Spanning Tree Protocol, the bridge is currently running.
• Command: possible commands are: modify / none.
RSTP Ports
RSTP Bridge is an application useful to manage RSTP Protocol Bridge
parameters on the NE.
• Bridge Index: Bridge Group Id.
• Port Name: the type of interface (for example ethG//1/1/1).
• Port Id: The port number of the port for which this entry contains
Spanning Tree Protocol management.
• Priority: The cost of the path to the root as seen from this bridge.
• Port State: The port's current state as defined by application of the
Spanning Tree Protocol. This state controls what action a port takes on
reception of a frame.
• Port Role: Operational role of the interface, as calculated by STP/RSTP
procedures.
• Port Enabling: The enabled/disabled status of the port.
• Designated RootBridge: The unique Bridge Identifier of the Bridge
recorded as the Root in the Configuration BPDUs transmitted by the
Designated Bridge for the segment to which the port is attached.
• Designated Port Path cost: The contribution of this port to the path
cost of paths towards the spanning tree root which include this port.
• Designated Bridge: Bridge Identifier of the bridge which this port
considers to be the Designated Bridge for this port's segment.
• Designated Port: The Port Identifier of the port on the Designated
Bridge for this port's segment.
• Forward Transitions: The number of times this port has transitioned
from the Learning state to the Forwarding state.
• Admin Edge Port: The administrative value of the Edge Port parameter.
A value of YES (1) indicates that this port should be assumed as an
edge-port and a value of NO (2) indicates that this port should be
assumed as a non-edge-port.
1/1553-HSC901 003/2 Uen B 97

• Oper Edge Port: The operational value of the Edge Port parameter. The
object is initialized to the value of foreStpPortAdminEdgePort and is set
NO on reception of a BPDU.
• Admin p2p Port: The administrative point-to-point status of the LAN
segment attached to this port. A value of yes (1) indicates that this port
should always be treated as if it is connected to a point-to-point link. A
value of no (2) indicates that this port should be treated as having a
shared media connection. Comment: A value of auto (3) is not
supported in this release.
• Oper p2p Port: The operational point-to-point status of the LAN
segment attached to this port. It indicates whether a port is considered
to have a point-to-point connection or not
• Admin Path Cost: The administratively assigned value for the
contribution of this port to the path cost of paths towards the spanning
tree root.
MSTP Configuration
NOTICE This feature is not implemented yet
The Multiple Spanning Tree Protocol (MSTP) has been developed to provide an
efficient means of supporting the multiple instances of Spanning Tree Protocol
(STP) required for deploying numerous VLANs in a switched Ethernet LAN.
Instead of a separate instance of STP for each VLAN (as PVSTP does), MSTP
provides for a grouping of VLANs to share a common instance of STP. So,
several VLANs can be mapped to a small number of STP instances. This mainly
allows the MSTP to provide a traffic load balancing depending on the VLANs the
traffic belongs to. Moreover it assures, as the RSTP does, the path reliability. Its
behavior is almost the same of that foreseen by the RSTP with the following
difference: MST allows the user to map multiple VLANs to the same MST
instance, but a VLAN can be mapped to one and only one MST instance. This
management application allows the network operator to view and modify the
configuration and status for Multiple Spanning Tree Protocol running in each
bridge group.
• Forced Version: the Spanning Tree Protocol which runs on the bridge group.
• Admin Status: it specifies if MSTP procedures are enabled or disabled
on a particular bridge group.
98 1/1553-HSC901 003/2 Uen B

• Configuration Name: it specifies an administratively assigned name for

the configuration.
• Configuration Version: it specifies an administratively assigned
revision number for the current MSTP configuration.
• Regional Root: MSTP Regional Root.
• External Root Cost: The cost of path from this bridge to the root bridge,
as calculated by this MST Instance.
• Configuration Signature: it indicates the signature of the VLAN to
Instance Mapping.
• Hello Time: The amount of time between transmission of Configuration
Bridge PDUs, if this bridge group acts as the root of the tree.
• Root Hello Time: The amount of time between transmissions of
Configuration Bridge PDUs.
• Forward Delay: the amount of time a bridge interface stays in
listening/learning state before moving to forwarding state.
• Root Forward Delay: The amount of time a bridge interface stays in
listening/learning state before moving to forwarding state. This is the
operational forward delay.
• Max Age: Maximum number of seconds a bridge waits without receiving
any spanning tree configuration messages before attempting
reconfiguration.
• Root Max Age: Maximum number of seconds a bridge waits without
receiving any spanning tree configuration messages before attempting
reconfiguration. This is the operational MaxAge.
• Max Hop Count: Maximum hop count for a BPDU.
• Pending Changes: This variable indicates if there are pending VLAN to
MSTI assignments in this bridge group. Pending assignments become
operational after the MSTP restarts.
• Tx Hold: it indicates the tx hold count parameter for MSTP.
MSTP Instances
This application allows viewing and modifying the configuration and status for
Multiple Spanning Tree Protocol instances running on a particular Bridge Group.
It is composed by the following folders: MSTP inst and Vlan Mapping.
1/1553-HSC901 003/2 Uen B 99

MSTP inst
• MSTP Index: STP Instance ID.
• Bridge Priority: Bridge Priority for this particular instance.
• Designated Root: The bridge identifier for the root of the spanning tree
calculated by this MST Instance.
• Root Cost: The cost of path from this bridge to the root bridge.
• SNMP bridge Index: SNMP Index for the bridge interface which has
been designated as root port for this particular instance.
• Number of topology changes: Number of topology changes on this
MST Instance, since the last start of MSTI.
• Number of mapped VLANs: Number of VLANs which have been
mapped to this instance of MSTI.
• Command: possible commands are: create / modify / delete / none.
VLAN Mapping
• MSTP Inst: An integer with values ranging from 0 to 64 that identify a
the CIST/MSTI instance to which this VLAN is mapped.
• VLAN Id: The VlanId for which this entry contains the instance mapped.
• Command: possible commands are: create / modify / delete / none.
MSTP Ports
This application allows viewing and modifying the configuration and status for
each bridge interface within in particular Bridge Group. Interfaces may have
different configuration and states for different instances of MST.
100 1/1553-HSC901 003/2 Uen B


• MSTP Instance: An integer with values ranging from 0 to 64 that identify
the CIST/MSTI instance to which this VLAN is mapped.
• Port Number: Bridge Interface SNMP index.
• Layer-2 Interface: The bridge identifier for the root of the spanning tree
• Bridge Priority: it specifies the Priority of a particular interface for a
particular MstpInst Instance.
• Port Hello Time: Amount of time between transmissions of
Configuration Bridge PDUs, if this bridge group acts as root of the tree.
• Path Cost: Link cost for a particular MSTI.
• Is Edge Link: Administratively declare an interface as an edge port.
Such designation applies to all instances in MSTP.
• Oper Edge Port: Operational edge port mode.
• Admin Edge Port: Auto edge port mode.
• Oper Version: Operational running mode for a particular interface.
• Port Role: Operational running mode for a particular interface.
• Port State: Forwarding state of the interface, for a particular MST
Instance, as calculated by MSTP/RSTP procedures.
• Is Border Interface: forwarding state of the interface, for a particular
MST Instance, as calculated by MSTP/RSTP procedures.
• Admin status: Enable MAC services on this interface.
• Oper Status: Operational value of services on this interface.
• Is point to point: Administratively designate this interface as a point to
point interface for RSTP functions.
• Oper p2p Port: Operational value of services on this interface.
• Forward Transitions: it reflects 'mcheck' - 'Force BPDU Migration
Check' management operation, which is executes, when this object is
being set to true (1). The value false (2) in SET operation has to be
ignored. The operation GET must always return value false (2).
• Designated Root: it indicates the Designated Root for this interface.
• Designated Bridge: it indicates the Designated Bridge for this interface.
• Designated cost: The cost of path from this bridge to the root bridge, as
• Designated Port prio: it indicates the Designated Interface Priority for
this interface.
• Designated Port: it indicates Designated Interface Priority for this interface.
1/1553-HSC901 003/2 Uen B 101


2.4.14.7 Ethernet Link Aggregation
PATH: (Configuration -> IP/Ethernet Management -> Ethernet Link Aggregation)

This tool allows creating and managing the Link Aggregation Group (LAG)
entities. This tool is structured in two tabs:
• Link Aggregator in order to specify aggregator parameters.
• Link Aggregator Ports in order to manage Port assigned to a specified
aggregator.
In order to complete the configuration, the Operator must also configure these
level 2 parameters:
• Line Identifier;
• Ingress Filter;
• Num Traffic Classes;
• Priority Traffic Class.
This operation must be performed by means of the Link Aggregator Lines in
the CP-IP board menu.
By clicking Read Network – Active Page you can retrieve information from
equipment depending on selected tabbed panel.
By clicking Read Network –All Pages you can retrieve information from all
tabbed panels.
Link Aggregator folder
This folder is composed by the following columns:
The fields shown in grey (e.g. MAC Address) are not editable.
102 1/1553-HSC901 003/2 Uen B

1. Select the NE by means of the relevant scroll list. Logical Name is relevant only
if the Operator use a Network Management System.
2. Display the value in the MAC Address Selection Mode (auto or manual).
MAC address, MAC Address Selection Mode and Interface Name fields are
not editable.
3. Define the aggregator priority in the Actor System Priority.
Actor System ID represents an identifier for the System that contains this
Aggregator. This field is not editable.
4. LAC Enable field specifies, if the protocol is supported (true) or not (false).
5. Actor Admin Key identifies in a univocal way the Link Aggregation Group entry.
It is used to separate the ports of the switch into separate groups (LAG) of
aggregated ports.
6. Actor Oper Key field is the current operational value of the Key for the
Aggregation Port.
7. Partner System Id is the identifier for the current protocol Partner of this
Aggregator. This field is not editable.
8. Partner System Priority indicates the priority value for the partner system.
9. Partner Oper Key identifies which ports may be aggregated together.
Actor Oper Key, Partner System Id, Partner System Priority, Partner Oper
Key are not editable fields.
10. Status and Error Descr help the Operator to have more information about the
operation executed
Link Aggregator Port folder
1. Select the NE by means of the relevant scroll list.
The Logical Name is relevant only if the Operator use a Network Management
System.
Interface Name field is the interface name of the port and can assume the
values: none, browse.
2. Command field allows executing the action. Possible values are:
* create
* modify
* delete
3. Actor Admin Key field is the current administrative value of the Key for the
Aggregator. The administrative Key value may differ from the operational Key
value.
4. Actor Oper Key field is the current operational value of the Key for the
Aggregation Port.
Actor Oper Key field is not editable.
5. Actor Admin State is used to define the administrative value of priority
associated with the Partner's System ID. This parameter can assume the
following values: none or update
If you choose Update a new window will appear and you can select one or more
of the following values: LACP_Activity, LACP_Timeout, Aggregation,
Synchronization, Collecting, Distributing, Defaulted, Expired.
6. Actor Oper State is the current operational values of Actor_State as transmitted
by the Actor in LACPDUs.
1/1553-HSC901 003/2 Uen B 103

Actor Oper State field is not editable.

7. Actor Port Priority is the priority value assigned to this Aggregation Port.
8. Actor Port is the port number locally assigned to the Aggregation Port.
The port number is communicated in LACPDUs as the Actor_Port.
9. Port Attached Aggregator ID is the identifier value of the Aggregator that this
Aggregation Port is currently attached to. Zero indicates that the Aggregation
Port is not currently attached to an Aggregator.
10. Partner Oper System ID representing the current value of the Aggregation
Port's protocol Partner's System ID.
11. Partner Oper System Priority indicating the operational value of priority
associated with the Partner's System ID.
12. Partner Oper Key is the current operational value of the Key for the Aggregator.
13. Partner Oper State is a string of 8 bits, corresponding to current values of
Actor_State in the most recently received LACPDU transmitted by protocol Partner.
14. Partner Oper Port Priority is the current administrative value of the port priority
for the protocol Partner.
15. Partner Oper Port is the operational port number assigned to this Aggregation
Port by the Aggregation Port's protocol Partner.
Actor Port, Port Attached Aggregator ID, Partner Oper System ID, Partner
Oper System Priority, Partner Oper Key, Partner Oper State, Partner Oper
Port Priority, Partner Oper Port field are not editable fields.
16. Status and Error Descr help the Operator to have more information about the
operation executed.
17. Press Apply Active Page or Apply All Pages to confirm the choices.
2.4.14.8 Bridging Parameters
PATH: (Configuration -> IP/Ethernet Management -> Bridging Parameters)

This tool allows configuring the bridging parameters at the Equipment level.
1. Configure by means of the Forwarding DB Aging Time (sec), the timeout

(expressed in seconds, maximum 600sec) period for aging out learnt forwarding
information.
2. Insert in the Bridge Ethertype S, the value used to assign an Ethertype value
for the S-VLAN tagged frames (hexadecimal string, default value 0x88A8).
3. Press Refresh to update, Apply to confirm, and Cancel to close the window.
104 1/1553-HSC901 003/2 Uen B

2.4.14.9 VLAN SubInterface Configuration
PATH: (Configuration -> IP/Ethernet Management -> VLAN SubInterface Configuration)

This window allows display/create the VLAN SubInterface.
1. Lower Interface Name column specifies the textual name of the interface.
2. SubInterface Name column specifies the name of the subinterface. The
Subinterface is automatically created from the equipment
3. C-VID column specifies the C-VLAN id for this VLAN subinterface. This value
must be set by the operator.
4. S-VID column specifies the S-VLAN Id for this VLAN sub interface. This value
must be set by the operator.
5. SubInterface Number column specifies the index for the VLAN Sub interface. It
can be set by the operator or it can be chosen by the equipment automatically.
To create/modify a new VLAN SubInterface

1. Click on Details >> button
A Property Details window will be displayed
1/1553-HSC901 003/2 Uen B 105

2. Specify in the field Lower Interf Name the type of interface (BVI)
3. In the C-VLAN ID selects a number that specifies the C-VLAN id for this VLAN
subinterface. A value in the range 1...4094 indicates a specific C-VLAN id to be
configured for this subinterface. A value of 0 indicates the no C-VLAN, i.e. this
VLAN carries traffic with S-VLAN tag only.
4. S-VLAN ID specifies the S-VLAN Id for this VLAN subinterface. The C-VLAN
and S-VLAN values must be unique among subinterfaces configured.
5. In the SubInterface Number write a number that specifies the index of the
VLAN-SubInterface. If the operator does not fill this field an index will be created
automatically by the equipment.
The fields SubInterface If-Index and Table Indexes report internal tables and
they have debugging purpose.
6. Click on Create button in order to create a new VLAN subinterface.
7. Click on Refresh button in order to update the "Property Details" window.
8. Click on Close Details button in order to exit.
2.4.14.10 Management Interface Setting
PATH: (Configuration -> IP/Ethernet Management -> Management Interface Setting)

This tool is used to configure the value of the DSCP (Differentiated Services
Code Point bits) field for the IP packets on the SNMP protocol used for the
equipment management. The DSCP value is between 0 and 63.
After the insertion of the DSCP value:

1. Click on Apply button to confirm the choice.
106 1/1553-HSC901 003/2 Uen B

2. Click on Refresh button to update the window.

3. Click on Close button to exit.
2.4.14.11 IP Interface Configuration (Network Interface Config)
PATH: (Configuration->IP / Ethernet Management->IP Interface Configuration)

This tools permits to manage the Layer 3 Interfaces [Routing I/F (RIF)].
How to create a RIF interface

1. Click on Details>> button. A Property Details window will be displayed.
1/1553-HSC901 003/2 Uen B 107

2. Specify in the field L2 Interface Name the type of interface [vlanCVID-SVID

(e.g. vlan4094-4094)].
3. Insert an IP Address.
4. Insert a Mask Length. The possible values are from 0 to 32
5. Insert a short description in the Description field
6. Set the parameter “Local In-Band Mng" if you want that this IP Router interface
is used for In-Band Management of this equipment.
7. Insert a MTU Size the size of the largest packet which can be sent/received on
the interface, specified in octets. Insert 1500 as value.
8. Insert the PTOP neighbor IP address in the Neighbor Address field (default
value "0.0.0.0").
9. Click on Create button
The fields "Row Status" and "IP Oper Status" are read-only fields that display
the status of the in-band management. Possible values for Oper Status field are
up, testing and down.
Possible values for Row Status field are active and not in service
The fields IP If-Index, L2 If-Index and Index are indices of internal tables, they
have debugging purpose.
How to modify a RIF interface

1. Select in the Network Interface Configuration window the IP interface that you
want modify.
2. Click on Details>> button.
3. Modify the fields above specified.
4. Click on Modify button.
108 1/1553-HSC901 003/2 Uen B

How to delete a RIF interface

1. Select in the IP Interface Configuration window the interface that you want
delete.
2. Click on the Delete button.
2.4.14.12 Static Routing Table
PATH: (Configuration->IP / Ethernet Management-> Static Routing Table)

This tool allows displaying and configuring the Static Routing Table.
How to create a Static Route Entry:

1. Click on the Details >> button in order to add the Routing Data folder in the
Property Details section.
2. Insert in the Route Dest field the Route Destination IP address.
1/1553-HSC901 003/2 Uen B 109

3. Insert in the Route mask field the Route Mask for the IP address inserted.
4. Insert in the Route Gateway field the Route gateway address.
5. Oper Status shows the actual state of the Route.
6. Press Create to insert the data before configured in the table.
How to delete a Static Route Entry

1. Select in the static Routing window the item that you want delete.
2. Click on the Delete button.
2.4.14.13 ARP Table Configuration
PATH: (Configuration Æ IP/Ethernet Management Æ ARP Table Configuration)

This tool allows configuring the ARP table in the Equipment. ARP converts an
Internet Protocol (IP) address to its corresponding physical network address.
How to add an entry in the table

1. Press the Details >> button.
110 1/1553-HSC901 003/2 Uen B

2. Insert the IP Interface Name by selecting it in the list. You can refresh the list of
available IP interfaces by clicking on the round button.
3. In the IP Address field is possible to read the interface IP address.
4. IP If-Index: an index automatically associated to the IP address.
5. Display in the field L2 Interface Name the type of interface.
6. L2 If-Index is the index of lower interface of which PPPoE client interface is bound.
7. In the Target IP address insert the IP address of the target system.
8. Insert the Target Phys Address insert the MAC address of the target system.
9. Specify the Mapping Type. The type mapping that can be:
- static: it indicates that the mapping is statically configured.
- dynamic: it indicates that the IP address to physical addresses mapping has
been dynamically resolved.
- invalid: it has the effect of invalidating the corresponding entry.
- other.
10. The field Table Indexes reports internal tables and they have debugging purpose.
11. Click on Create button in order to create a new entry.
12. Click on Modify button in order to modify the entry.
13. Click on Refresh button in order to update the entry.
2.4.14.14 Ping Request Parameters
PATH: (Configuration -> IP/Ethernet Management -> Ping Request/Response)

By means of this window is possible to configure and activate the ping request.
On this Equipment is possible to ping a selectable IP address triggered, in an
‘on-demand’ manner, by the management interface on the management VLAN.
In order to do that, the following operation MUST be performed via management
interface:
1/1553-HSC901 003/2 Uen B 111

1. Creation of a static entry in the ARP Cache Table, in order to associate a MAC
address to the specific IP address to be pinged. This operation must be
executed by the Configuration->IP/Ethernet Management-> ARP Table
configuration window. This operation is not mandatory; if you do not execute it
the ping operation automatically will execute it.
2. Start the Ping request and read the Ping results.
3. In the Owner Name scroll list is possible to insert the user involved in the test.
4. In the Test Name scroll list is possible to insert the name of the test.
5. In the Target IP Address field is possible to insert the IP address of the
Equipment involved in the test.
6. Min RTT (msec) gives a response about minimum ping round trip time received.
7. Max RTT (msec) gives a response about maximum ping round trip time received.
8. Average RTT (msec) gives a response about the current average ping round
trip time received.
9. Probe Responses gives a response about the number of ping received.
10. Probe Sent gives a response about the number of ping sent.
11. Last Good Probe gives a response about the data and time of the last ping.
12. Press Refresh Ping Table in order to update the ping table.
13. Press Refresh Current entry to update the entries.
14. Press Send Ping to start the operation.
15. Press Delete Current entry to cancel the entries.
16. Press Cancel to exit.
2.4.15 L3 DHCP Relay Agent Management

PATH: (Configuration -> L3 DHCP Relay Agent Management)
DHCP is a commonly used protocol to dynamically configure IP layer on hosts
located in IP network. Mainly IP host needs information regarding its IP
address/subnet mask and its default gateway. Moreover it can require DNS
configuration, basic routing information and other information. After obtaining
parameters via DHCP, a DHCP client should be able to exchange packets with
any other host in the Internet.
112 1/1553-HSC901 003/2 Uen B

In many cases, DHCP clients and server(s) are not belonging to the same IP
sub-network. This occurs especially in Access Network in which users are
directly connected to access DSLAM, while the DHCP servers are located in the
core IP network, behind the users’ IP default gateway, far away (from IP point of
view) from the users themselves.
In such cases, a DHCP Relay Agent device is required to transfer DHCP
messages between clients and servers.
The tool is composed by 4 applications, according to the L3 DHCP part of
configuration to be performed.
2.4.15.1 L3 DHCP Profile Management
The L3 DHCP Profile Application provides the parameters for the configuration
of L3 DHCP Relay Agent. One entry in this table reflects a profile defined by a
manager which can be used to configure the L3 DHCP Relay Agent. It is
composed by the following folders:
• L3 DHCP profiles;
• Action.
L3 DHCP profiles folder

1. Ne Name: equipment name or IP address.
2. Profile Id: L3 DHCP Relay Agent profile identifier.
3. IP Address: the IP address that the L3 DHCP Relay Agent shall use as Gigabit
Address (Giaddr) in the DHCP messages and as Source IP address in IP packet.
1/1553-HSC901 003/2 Uen B 113

4. Subnet Mask: the subnet mask associated with the IP address specified in IP
Address field. The value of the mask is an IP address with all the network bits
set to 1 and all the hosts bits set to 0.
5. Default Gateway: the IP address of the default gateway to be used.
6. Dscp: this field defines the DSCP (Differentiated Services CodePoint) for DHCP
messages.
7. Priority Tag: the Ethernet Priority tag to be used for DHCP messages.
8. Server Policy: this field is used to define the policy followed by the DHCP Relay
Agent to select the DHCP servers. Possible values are:
- byPriority: the DHCP Relay Agent sends a unicast message to highest priority
DHCP Server and if it does not respond within a fixed timeout it tries with DHCP
Server having priority 2 (if existing) and so on.
- allListedServers: the DHCP Relay Agent sends a unicast message to each
DHCP Server listed in the table at the same time.
Action folder:
1. To Do: the command to be applied: create, modify, delete.
2. Result: result of command (OK, ERROR).
3. Error: in case of error a description of it.
2.4.15.2 L3 DHCP Server Profile Management
The L3 DHCP Server Profile Application provides the list of DHCP Servers that
are relayed by the L3 DHCP Relay Agent.
L3 DHCP Server profiles folder

This application is composed by the following L3 DHCP Server Profiles folder.
2. Profile Id: L3 DHCP Relay Agent profile identifier.
114 1/1553-HSC901 003/2 Uen B

3. DHCP Server IP Address: the IP address of the DHCP Server.

4. DHCP Server Priority: the priority indicating the order that the DHCP Relay
Agent shall follow in contacting the DHCP Servers.
Priority 1 is the highest priority (the first DHCP Server to be contacted), while
priority 8 means the lowest priority (the last DHCP Server to be contacted).
Entries in table must all have different priorities. At least one entry must have
priority set to 1.
5. To Do: command to be applied to current row: create , modify, delete.
6. Result: result of command: OK or ERROR.
7. Error: In case of error a description of it.
2.4.15.3 L3 DHCP VLAN Management
The L3 DHCP VLAN Application provides the parameters for the configuration
of L3 DHCP Relay Agent per VLAN.
This application is composed by the L3 DHCP VLANs folder.This folder is

composed by the following fields:
2. DHCP C VLAN Id: the VLAN identifier representing the inner VLAN, i.e. C-
VLAN. When this field is set to 0, it means not meaningful field.
3. DHCP S VLAN Id: the VLAN identifier representing the outer VLAN, i.e. S-VLAN.
4. DHCP Conf Profile: the row in L3 DHCP Profile Id which applies to current VLAN.
5. DHCP Conf Server Profile: the row in the L3 DHCP Server Profile which
applies to current VLAN.
6. To Do: command to be applied to current row (create, modify, delete).
7. Result: result of command (OK or ERROR).
1/1553-HSC901 003/2 Uen B 115

2.4.15.4 L3 DHCP Interface Management
L3 DHCP Interface lists the interfaces on which L3 DHCP Relay Agent is enabled
for specifics S-VLAN. To enable a certain interface on more than one VLAN, add
additional entries using the same interfaces (or port) and different VLANs.
This application is composed by the L3 DHCP Interface Management folder.

1. Ne Name: Equipment Name or IP Address.
2. DHCP Interface name: the interface name or the interface where L3 DHCP
Relay Agent is enabled. (ethG//1/1/<port number>, lag//1/<logical port number>,
intLag//1/<Line Card Slot>).
3. S-VLAN: the VLAN identifier representing the outer VLAN, i.e. S-VLAN, for
which L3 DHCP Relay Agent is enabled on current interface.
4. To Do: command to be applied (create or delete).
5. Result: result of command (OK or ERROR).
2.4.16 Video Multicast Management

This tool allows configuring and managing the Video and the Multicast
functionality in the Equipment.
116 1/1553-HSC901 003/2 Uen B

2.4.17 IP-CP Multicast Configuration

PATH: (Configuration-> Video/Multicast management -> IP-CP Multicast Configuration)
This tool allows configuring the services relevant to the Video and the Multicast
on CP card. The application is composed of three sub-application, to configure
the Multicast VLAN, the IGMP and the Static Multicast.
2.4.17.1 Multicast VLANs
Multicast VLANs Management is an application that allows configuring and

browsing multicast VLANs used to transport multicast services from the DSLAM
to the user. IGMP protocol will be enabled and configured for the selected
VLAN. This application is provided of 2 folders: Mcast VLANs, Application
Control.
Multicast VLANs folder

This folder is used to define parameters for the IGMP protocol. The following
parameters are defined:
1. Insert the IP address of the Equipment in the Ne Name.
2. Insert the identifier for the VLAN in VLAN Id.
3. IGMP Mode: the type of IGMP processing configured for the interface:
querier: the router cache is populated from received IGMP reports and leaves.
The router participates in querier election and sends queries. This is the normal
router-side processing.
snooper: this is the same as router mode, but the router does not participate in
querier elections, nor sends any queries, nor responds to leave message.
proxy: the host cache is a summary of router caches of all interfaces on system.
4. IGMP version: the version of IGMP which is running on this interface. Value 1
applies to IGMPv1 routers only. Value 2 applies to IGMPv2 routers and value 3
applies to IGMPv3 routers.
1/1553-HSC901 003/2 Uen B 117

5. IP address: The source IP address of all IGMP packets generated by the

equipment, both network-side (i.e. proxy Host and query solicitation for proxy
and snooper configuration) and user-side (i.e. Querier for the entire
configuration). Default value is 0.0.0.0. IP Address is a mandatory field.
6. Flood Mcast Address Min / Max: Since not all multicast is based on IGMP,
there exist certain cases where multicast traffic needs to be detected. The only
possible way to do this is to snoop the traffic based on the multicast address - if
the address falls within a pre-defined range then the traffic is treated as multicast
and flooded on current VLAN. The two parameters define the range.
7. Query Interval (sec) the frequencies at which the packets are transmitted.
8. Query MaxResponse Time (1/10 sec) the maximum time allowed to the host
to reply to the query.
9. Robustness (1..255) the variable that allows tuning for the expected packet
loss on a subnet. If a subnet is expected to be lost, the Interface Robustness
variable may be increased.
10. Last Memb Query Intvl parameter displays the Max Response Time inserted
into Group-Specific Queries sent in response to Leave Group messages, and is
also the amount of time between Group-Specific Query messages.
11. By means of the Unsolicited interval (sec) field is possible to configure the
frequency at which unsolicited IGMP packets are transmitted.
12. Priority Tag (0..7): Ethernet Priority tag applied.
13. Dscp (0..63): This field defines the DSCP (Differentiated Services CodePoint)
parameter for IP packets.
14. Up Time: the time elapsed since this entry was created.

This folder provides the fields to control the application and to display the
situation
118 1/1553-HSC901 003/2 Uen B

1. Admin Status: the administrative status of the interface. It can assume the
values enabled or disabled.
2. Oper Status: The operational status of the interface. It can assume the values
up or down.
3. Command: it specifies the configuration operation to perform:
- create: it provisions the parameters to the equipment.
- delete: it removes the gateway information.
- modify: it changes the configuration parameters
- setAdmin: it set the admin status.
4. Result: it shows the response for the operations executed (OK, ERROR).
5. Error: This read only field shows the type of the error.
6. Date&Time: the timestamp (time that is printed to a file or other location to help
keep track of when data is added, removed, sent, received) referred to the
inventory operation.
7. Ip Address: IP address of the Equipment.
8. Annotations: it is used to write some note about the operation.
2.4.17.2 IGMP Interfaces
IGMP User Multicast Channels Management is an application that allows

configuring and browsing igmp multicast channels used to transport video
streams and additional services from the DSLAM to the user. After running the
application, you will be presented a single window with a tabbed notebook and
one table named "IGMP Interface.
IGMP Interface
This folder is used for enabling/disabling the IGMP Protocol. The following
parameters are defined:
1/1553-HSC901 003/2 Uen B 119

2. Interface Name is the interface used in the Equipment (EthG, lag, ipoE)
4. Admin Status: the administrative status of the interface. It can assume the
values enabled or disabled.
6. Interface Type is the type of interface used in the Equipment.
7. Oper Status: The operational status of the interface. It can assume the values
up or down.
8. Querier IP address: The address of the IGMP Querier on the IP subnet to
which this interface is attached. Read only field.
9. Querier Up Time: The time since Querier IP address was last changed, in time
ticks i.e. hundredth of seconds. Read only field.
10. Querier Expiry Time: The amount of time remaining, in time ticks i.e. hundredth
of seconds, before the Other Querier Present Timer expires. If the local system
is the querier, the value of this object is zero. Read only field.
11. Wrong Version Queries: The number of queries received whose IGMP version
does not match the equivalent IGMP version parameter. Both IGMP requires
that all routers on a LAN be configured to run the same version, thus, if any
queries are received with the wrong version, this indicates a configuration error.
Read only field.
12. Joins: The number of times a group membership has been added on this
interface; that is, the number of times an entry for this interface has been added
to the cache table. This parameter gives an indication of the amount of IGMP
activity. Read only field.
13. Groups: The current number of entries for this interface in the router cache
table. Read only field.
14. V1 Querier Timer: The time remaining, in time ticks i.e. hundredth of seconds,
until the host assumes that there are no IGMPv1 routers present on the
interface. While this is non-zero, the host will reply to all queries with version 1
membership reports. This variable applies to IGMPv2 or 3 hosts that are forced
to run in v1 for compatibility with v1 hosts or routers present on the interface.
Read only field.
15. V2 Querier Timer: The time remaining, in time ticks i.e. hundredth of seconds,
until the host assumes that there are no IGMPv2 routers present on the
interface. While this is non-zero, the host will reply to all queries with version 1 or
2 membership reports. This variable applies to IGMPv3 hosts that are forced to
run in v2 for compatibility with v2 hosts or routers present on the interface. Read
only field.
16. Result column shows the response for the operations executed (OK, ERROR).
17. Error Message column shows the type of the error.
19. IP Address: the IP address of the Equipment
120 1/1553-HSC901 003/2 Uen B

2.4.17.3 Static Multicast
The purpose of this application is that of configuring the source IP addresses

(one or many) for the IP multicast group of one or many IGMP interfaces. Each
addressed IGMP interfaces are identified by its associated L2 interface and an
IP multicast group address. The tool has an editable row for each source IP
address of each IGMP interface, that is, each IGMP interface will show up in the
table as many times as there are source IP addresses for it.
Static Multicast
2. Interface Name: This is the textual name of the interface on which configuring
the static multicast address. The following possibilities are available:
- intLag//1/slot (e.g. intLag//1/5);
- ethG//1/slot/port (e.g. ethG//1/1/3);
- lag//slot/group (e.g. lag//1/2);
- ipoEnumber (e.g. ipoE2).
4. Multicast IP Address: the value of the multicast destination address coming
from the network.
-setAdmin: it set the admin status.
1/1553-HSC901 003/2 Uen B 121

6. Result column shows the response for the operations executed (OK, ERROR).
7. Error Message column shows the type of the error.
9. IP Address: the IP address of the Equipment.
2.4.18 IP-CP Multicast Survey

PATH: (Configuration-> Video/Multicast management -> IP-CP Multicast Survey)
This tool allows getting info about the IGMP features in the Equipment. It is
composed by the following applications and each one contains one folder as
shown in the window below:
• Router Cache;
• Host Cache.
Mcast Router Cache

This tool is useful to find out info about the IGMP Router cache table contents.
To get data from live equipments you must be sure that the IP address is
inserted into the "NE addr" field. Then, press Read Network to find data on the
NE. The result of the search is displayed in "MCast Router Cache Table". The
following parameters are defined:
1. Ne Name: This is the IP address of the equipment.
2. VLAN Id: identifier for the VLAN.
3. Multicast IP Address: the value of the multicast destination address coming
from the network.
4. Interface Name: the interface for which this entry contains information for an IP
multicast group address. (EthG, lag, ipoE).
122 1/1553-HSC901 003/2 Uen B

5. Last Reporter: the IP address of the source of the last membership report
received for this IP multicast group address on this interface. If no membership
report has been received, this object has the value 0.0.0.0.The Output format is
decimal dotted notation (x.y.z.t)
7. Expiry Time: The minimum amount of the time remaining before this entry will
be declared expired.
8. Version 1 Host Timer: The time remaining until the local router will assume that
there are no longer any IGMP version 1 members on the IP subnet attached to
this interface.
9. Version 2 Host Timer: The time remaining until the local router will assume that
there are no longer any IGMP version 2 members on the IP subnet attached to
this interface.
10. Data&Time column shows data and time when this information has been taken.
11. Ne IP Address column shows the IP address of the Equipment.
Mcast Host Cache
This is a tool to get info about the IGMP Host Cache table contents. To get data
from live equipments you must be sure that the IP address is inserted into the
"NE addr" field. Then, press [Read Network] to find data on the NE. The result of
the search is displayed in "MCast Host Cache Table".
1. Ne Name: This is the IP address of the equipment.
3. Multicast IP Address: IP multicast group address for which this entry contains
information. Output format: decimal dotted notation (x.y.z.t).
4. Interface Name: the interface for which this entry contains information for an IP
multicast group address (EthG, lag, ipoE).
5. Last Reporter: the IP address of the source of the last membership report
received for this IP multicast group address on this interface. If no membership
report has been received, this object has the value 0.0.0.0.The Output format is
decimal dotted notation (x.y.z.t).
7. Data&Time column shows data and time when this information has been taken.
8. IP Address column shows the IP address of the Equipment.
1/1553-HSC901 003/2 Uen B 123

2.4.18.1 Multicast Group Surveillance
PATH: (Configuration -> Video/Multicast management ->Multicast Group Surveillance)

This tool retrieves stores and displays multiple Group Registration Databases.
They contain filtering information for VLANs configured into multiple bridge
devices by the management, or learnt dynamically, and specify the set of ports
to which frames received on a VLAN for each FDB (and containing a specific
Group destination address) are allowed to be forwarded.
To get data from live equipments you must be sure that the IP address is inserted
into the "NE addr" field. Then, press [Read Network] to find data on the NE.
The result of the search is displayed in "Group Registration Table". The push-button
labeled "Look in VLANs" allow you to select which VLANs to read from beforehand.
The wanted VLANs have to be selected by means of their VLAN Ids. You are not
limited to one VLAN ID, as the input dialog form accepts also a list of comma-
separated ids (e.g. 1, 3, and 5) or of ids ranges (e.g. 1-3, 256, 512-768).
The folder Group Registration is composed by the following fields:

1. Ne Name: the name of the Equipment or the IP address of the Equipment.
2. Bridge: name of the bridge assigned by the system.
4. The Group Address shows the destination Group MAC Address in a frame
which this entry's filtering information is applied.
5. The Egress Port shows the complete set of ports (one per row), in this VLAN,
to which frames designated for the associated Group MAC address are
currently explicitly forwarded. This does not include ports for which this address
in only implicitly forwarded.
6. Learnt: A flag telling the port indicated in the previous field has been learnt by
GMRP or some other dynamic mechanism, in this database.
124 1/1553-HSC901 003/2 Uen B

7. Data&Time column shows the data and time when this information has been
taken from each device.
8. IP Address column shows the actual IP address used to access each device.
2.4.19 Voice over IP Management

This tool is used to configure and manage the Voice over IP functionalities in the
Equipment.
2.4.19.1 VoIP Global Parameters
PATH: (Configuration->VoIP Management->VoIP Global Parameters)

This menu allows configuring the type of Call Control (distributed or centralized)
for each type of VoIP signaling protocol managed by the equipment.
By using the relevant scroll lists, choose which equipment behavior you want for
VoIP application. This selection is possible for H248 and SIP protocol.
2.4.19.2 VoIP DNS Servers
PATH: (Configuration->VoIP Management->VoIP DNS Servers)

This menu allows configuring the DNS Servers for this kind of service.
1/1553-HSC901 003/2 Uen B 125

1. Press Refresh to refresh the collection.

2. Press Delete to erase an item in the collection table.
How to add a DNS Server Priority:

1. Press the Details >> button to add a new DNS Server.
2. Insert the IP Address.
3. Insert the priority [Server Priority]. Possible values are from 1 or 2. Priority 1
means the highest priority, while priority 2 means the lowest priority.
4. Press Create button.
2.4.19.3 Voice over IP Inventory/Provisioning
PATH: (Configuration->VoIP Management->VoIP Inventory/Provisioning)

This tool allows the configuration (and the reading) of all VoIP parameters. Once
a time the application is launched, the VoIP Management window appears:
The upper part of the window contains some icons that allow opening the
relative application (H248 Virtual Gateways, H248 Terminations, etc...) with an
amount number of folder associated to it. The graphic is an all-in-one
editor/browser/writer tool, with more than one folder. Each folder contains an
editable spreadsheet-like table for a consistent set of parameters. The folders
are strictly related to one another, and they can be seen as sections of a one big
table. Each table's row has its continuation in the folders located at its right or left
hand. The equipment’s or IP address is the first field that you come across in the
first folder. The data displayed in each row of the subsequent folders are always
related to the equipment referred to. Some fields may be of read-only type: such
fields are displayed when reading from equipment but not used when
configuring this service on it. Cells related to such parameters are yellow
126 1/1553-HSC901 003/2 Uen B

colored. Cells related to mandatory parameters are ivory colored and cells
related to parameters not yet supported by the equipment are grey colored.
H248 Virtual Gateways
This application is composed of several folders and allows to read or configure
(create and delete too) a Virtual Gateways with their parameters for H248
protocol. In the following there is the description of every folder.
Gateway1 folder
• NE Name: the IP address of the Network Element.
• Identifier: It is an integer value that univocally identifies the Virtual Gateway.
• Domain Name: It is the domain name associated with The Virtual Gateway;
the domain name of each Virtual Gateway is unique inside equipment.
• IP Address: local IP address used by Virtual Gateway for H.248 messages.
• UDP Port: The local UDP port number used by the Virtual Gateway for
H.248 messages.
• Subnet Mask: It is the subnet mask associated with the IP address
specified in "Signaling Gateway Default GW" parameter; the value of the
mask is an IP address with all the network bits set to "1" and all the
hosts’ bits set to "0".
• Default GW: IP address of the default gateway for the Virtual Gateway.
• Outer Ether Type: It is the value of Ether Type field (i.e. Tag Protocol
Identifier) for tagged frames. Possible values are 8100, 9100 and 88a8.
• Outer VLAN Id Tag (-1..4094); this field defines the Ethernet VLAN Id
tag for signaling data on current Virtual Gateway. If this value is 0, no
VLAN is assigned. If this value is -1 no tagging is performed, Outer
VLAN will always be applied.
• Outer Prior. Tag (0..7): This field defines the Ethernet Priority tag for
signaling data on current Virtual Gateway. This field is only meaningful
when the "Signaling Gateway Outer VLAN Id Tag" parameter is different
from -1.
• Inner Ether Type: The value of the Ether Type field i.e. Tag Protocol
Identifier, for tagged frames, this VLAN tag type is applied to the inner
VLAN tag. Possible values are 8100, 9100 and 88a8.
• Inner VLAN Id Tag (-1..4094): This defines Vlan Id tag used in the layer
2 VLAN Tag header for signaling data on current Virtual Gateway. If this
value is 0, no Inner Vlan Id tag is assigned. If this value is -1, no tagging
is performed. InnerVlan is optional.
• Inner Prior. Tag (0..7): This field defines the Ethernet Priority tag in the
layer 2 VLAN Tag header for signaling data on current Virtual Gateway.
This field is only meaningful when “Signaling Gateway Inner VLAN Id
Tag “parameter is different from -1.
• Signalling Dscp (0..63): This field defines DSCP field (Differentiated Services
Code Point) for IP packets of signaling data on current Virtual Gateway.
• Termin Address Format Options: the addressing format method for
the Terminations in the Virtual Gateway (etsiWithPhysicalLocation,
1/1553-HSC901 003/2 Uen B 127

etsiWithSlotPort, etsiWithoutPhysicalLocation, msfWithPhysicalLocation,

msfWithSlotPort, msfWithoutPhysicalLocation).
• Max Concurrent Active Calls: Maximum number of calls (incoming or
outcoming) that may be active at the same time for a given VoIP card. It
may be inserted to reduce the Maximum Number of Concurrent Active Calls
in order to limit the overall power consumption for the Network Element.
• CPU Onset Threshold: CPU occupancy threshold, expressed as a
percentage number between 0 and 99, at which a CPU is defined to be
overloaded. The onset and abatement thresholds shall be set
consistently (i.e. either both shall be not applicable or have appropriate
values, onset higher or equal to the abatement).
• CPU Abatement Threshold: This field specifies the CPU occupancy
threshold, expressed as a percentage number between 0 and 99, at
which a CPU overload is defined to abate.
The onset and abatement thresholds shall be set consistently (i.e. either
both shall be not applicable or have appropriate values, onset higher or
equal to the abatement).
Gateway2 folder
The list of the fields below is displayed in the second folder for each Virtual
Gateway entry found on each investigated Network Element
• PrettyPrint Format: this value allows reading the enabling/disabling of
the pretty print format of the H.248 notation.
• Longhand Format: this value allows reading the enabling/disabling of
the longhand format of the H.248 notation. When set to 'true' the format
is longhand. When set to 'false' the format is shorthand. In case of SIP:
When set to 'true' the format is generic one; when set to 'false' the
format is 'compact form.
• Addressing Type: addressing to be used for this Virtual Gateway. This
field t is used to specify which type of addressing has to be used for this
Virtual Gateway. Possible values are ipAddress and domain Name
• Andisp Data Tas Def: control of the provisioned default for the terminal
alerting signal for on or off hook generic FSK data signaling in the
absence of an explicit tas parameter (dualTone, ringPulse,
lineRevDualTone, noTas).
• Dial Map: dial map that establishes the expected numbers and pattern
of digits for telephone numbers. Patterns are separated by '|' sign.
• Dial Map Emergency: a dial map that establishes the expected
numbers and pattern of digits for emergency telephone numbers.
Patterns are separated by '|' sign.
• Preferred Protocol Version: preferred H.248 Protocol Version Number
with which Virtual Gateway starts H.248 version negotiation, at registration.
• H248 Profile Config: control of the H.248 profile that the Virtual
Gateway advertises at Start-Up and enforces when operational.
• H248 protocol profile index: index for this H248 profile.
128 1/1553-HSC901 003/2 Uen B

• Def Phys Term Event Detection: style of event priming present in the
default events descriptor for an analogue termination, which can be no
event detection (empty) or one of various combinations of hook state
events (on, of) which can be detected either on the basis of an actual
state transition (Exct) or additionally when the hook state indicates that
that transition has previously already occurred (Stat). The default events
descriptor is applied when the line is initially unblocked, and when the
line is placed back into the NULL context by a H.248 Subtract command.
• Def Phys Term Event Reporting: style of event reporting that the
gateway uses when the default events descriptor matches a hook event.
• Call Type Discriminator Timer: the value of the Call Type Discriminator
Timer (expressed in milliseconds). The timer is used to discriminate the
call type (event calldisres for package ctyp).
• Emergency Digit Map Name: the Emergency Digit Map name.
• Default digit Map Name: the Default Digit Map name.
Gateway3 folder
The list of the fields below is displayed in the third folder for each Virtual
Gateway entry found on each investigated Network Element.
• Identifier: index of the signaling gateway.
• Normal Calls Threshold: This field is used to set the threshold of the
normal calls ETSI-NR package). The value is in the range: 0-65536.
• Emergency Calls Threshold: This field is used to set the threshold of
the emergency calls (ETSI-NR package).The value is in the following
range: 0-65536.
• Rate Increment Period: This field is used to set the Rate Increment
Period (ETSI-NR package). The value, in the range 0-1000, is
expressed in milliseconds.
• Max Leak Rate: This field represents the Max Leak Rate (ETSI-NR)
package. The value is in the range: 0-100.
• Leak Rate Growth: This field represents the Leak Rate Growth Factor
(ETSI-NR) package. The value in the range: 0-100.
• Long Timer (10ms): Long digit map timer (interdigit timeout).
• Short Timer (10ms): Short digit map timer (multiple pattern match timeout).
• Start Timer (10ms): Start digit map timer (digit map activation timeout).
• Long Threshold (10ms): Time threshold for Long digit detection.
• Ringing Tones (10ms): Provisioned default timeout for ringing.
• Dial Tone (10ms): Provisioned default timeout for dial tone.
• Ring Tone (10ms): Provisioned default timeout for ring tone.
• Busy Tone (10ms): Provisioned default timeout for ringing.
• Equipment Engaged Tone (10ms): control of the provisioned default
timeout for equipment engaged tone.
1/1553-HSC901 003/2 Uen B 129

• Number Unobtainable Tone (10ms): control of the provisioned default

timeout for number unobtainable tone.
• Special Dial Tone (10ms): control of the provisioned default timeout for
special (stutter) dial tone
• Message Waiting Dial Tone (10ms): control of the provisioned default
timeout for message waiting dial tone
• Howler Tone (10ms): control of the provisioned default timeout for
howler tone.
MGCs Folder
The list of the fields below is displayed in the fourth folder for each Virtual
• Domain Name: the gateway domain name associated with the Media
Gateway Controller. This parameters is available both for the primary
and secondary Media Gateway Controller.
• IP Address: the IP address of the Media Gateway Controller. This
parameters is available both for the primary and secondary Media
Gateway Controller.
• UDP Port: UDP port of the Media Gateway Controller. This parameters is
available both for the primary and secondary Media Gateway Controller.
• Request TO(1..100ms): this is the timing of retry attempts from the
virtual gateway in units 100ms. This parameters is available both for the
primary and secondary Media Gateway Controller.
• Request Retries (1..10): this value represents the number of retry
attempts performed by the virtual gateway. This parameters is available
both for the primary and secondary Media Gateway Controller.
• Recent Rsp TO (1..30s): the duration in units of 1 sec that recent
responses are held by the virtual gateway before being deleted. This
parameters is available both for the primary and secondary Media
Gateway Controller.
• Restart Avalanche Prot. Max Random Delay: control of the maximum
time of the random delay that virtual gateway waits before registering
with the Media Gateway Controller after the card has been restarted.
• Reattempt Unans Min Delay: control of the minimum delay between
successive reattempts (after Application Level Framing retries) for
gateway transactions, when those transactions are unanswered.
• Reattempt Unans Max Rand TmOffset: control of the maximum time
offset to be added to the minimum delay between successive reattempts
(after Application Level Framing retries) for gateway transactions, when
those transactions are unanswered.
• Reattempt Neg Ack Min Delay (10 ms): This field controls the
minimum delay between reattempts (with distinct Ids) for gateway
130 1/1553-HSC901 003/2 Uen B

transactions, when those transactions are negatively acknowledged.

Value is measured in 1/100 second units.
• Reattempt Neg Ack Max Rand TmOffset (10 ms): This field controls
delay controls the maximum time offset to be added to the minimum
delay between successive reattempts (with distinct Ids) for gateway
transactions, when those transactions are negatively acknowledged.
Value is measured in 1/100 second units.
• Forced Context Clean Timeout: control of the provisioned default
timeout for the Media Gateway Controller to clean-up context after a
forced out-of-service.
• Normal MG Exec Time: interval within which the MGC expects a
response to any transaction from the MG (exclusive of network delay).
• Normal MGC Exec Time: interval within which the MG should expects a
response to any transaction from the MGC (exclusive of network delay).
• MG Originated Pending Limit: number of TransactionPendings that
can be received from the MG.
• MGC Originated Pending Limit: number of TransactionPendings that
can be received from the MGC.
• MG Provisional Response Timer: time within which the MGC should
expect a Pending Response from the MG if a Transaction cannot be
completed.
• MGC Provisional Response Timer: time within which MG should expect a
Pending Response from the MGC if a Transaction cannot be completed.
• Transaction Response Ack: This field is used to enable (true) or disable
(false) the transmission of Transaction Response Ack parameter.
• Transaction pending: This field is used to enable (true) or disable
(false) the Transaction Pending feature.
• Provisional Response Timer Percentage: This field represents the
Provisional Response Timer Percentage used to update the Long
Provisional Response Timer.
• SC Graceful: This field enable (true) or disable (false) SC Graceful feature.
EDA4.11 Only folder
The parameters that are listed in this folder are valid only for EDA 2530 4.11
equipments for this reason they happens grey colored.
• Binding Card <shelf>/<slot>: the shelf, slot where the card is lodged.
• Media Local IP Address: This is the local IP address used by the
Virtual Gateway for media. If this is left empty (0.0.0.0) then the same
local IP address is used for Media and Signaling and it is the one
specified in "Virtual Gw Ip Address" field.
• Media Subnet Mask: the subnet mask associated with the Media
Default Gateway.
1/1553-HSC901 003/2 Uen B 131

• Media Default Gateway: the IP address of the primary default gateway

used for media of current Virtual Gateway.
• Media Dscp (0..63): this field defines the DSCP (Differentiated Services
Code Point) parameter for IP packets of media data on the current
Virtual Gateway.
• Media VLANId Tag (-1..4094): This field defines the Ethernet Vlan Id
tag for media data on current Virtual Gateway. If this value is 0, no Vlan
Id tag is assigned. If this value is -1, no tagging is performed.
• Media Priority Tag (0..7): This field defines the Ethernet Priority tag for
media data on current Virtual Gateway.
• Fixed Forwarding: This parameter enables/disables forwarding traffic
between users, through users Default Gateway. In case it is enabled the
traffic is sent from a user to another through sending users Default
Gateway. Otherwise (disabled) the traffic is sent from a user to another
following the standard IP/Ethernet rules. The possible values are:
- enabled: it enables sending traffic to the sending users Default
Gateway.
- disabled: it - uses standard IP/Ethernet forwarding rules.
App. Control
• Admin Status: the administrative state of the Virtual Gateway.
(OutOfService: out-of-service state, ForcedOutOfService: immediate
transition to the out of service state, InService: set the virtual gateway in
to the in service state).
• Oper Status: this value allows reading the operational status of the
virtual gateway. Possible values are notConfigured, inService,
outOfService, disconnected and restarting.
• Command: it specifies the configuration operation to perform:
• Result: it shows the response for operations executed (OK, ERROR).
• Annotations: it is used to write some notes about the operation.
H248 Terminations
(create and delete too) the physical terminations in a Virtual Gateways with their
132 1/1553-HSC901 003/2 Uen B

parameters for H248 protocol. In the following there is the description of every
folder.
Termination folder
The list of the fields below is displayed in the Termination folder.
• User Port: info relevant to the physical port. This string must is
displayed in the following way: subrack (sr) / slot (sl) / module (mod) /
port number (port).
• Virtual GW Index: This field is the identifier of the Virtual Gateway to
which current physical port belongs.
• Virtual GW Name: This field is the gateway domain name associated
with the virtual gateway.
• Media Local IP Address (4.21 only): This field is the local IP address
used by the termination for media.
• Admin Status: The operator sets this parameter to command the
block/unblock of the termination. Possible values:
- forcedBlock: The user port is taken out of service immediately, even if
busy.
- block: The user port is taken out of service only if it is not busy.
- unblock: The user port is brought into service.
• Termination Name (4.11 only): The complete descriptive name that
describes this termination and its use. This is a unique identifier that is
assigned to the termination and it is used in the protocol messages that
are sent from the gateway.
• Status: It represents the operational status of the termination
• Busy Status: the status of the application use of the termination (null,
idle, busy).
• Active Channels: the number of media channels that are currently

active on the termination.
Application Control folder:
1/1553-HSC901 003/2 Uen B 133

H248 Virtual Gateways Survey

This application allows reading the status of the H248 Virtual Gateways. It is
composed by the H248 Gateway folder.
H248 Gateway folder
• Ne Name: the IP address of the Network Element.
• VG Identifier: index of the Virtual Gateway.
• Domain Name: identifier for the Virtual Gateway. This field is the
gateway domain name associated with the virtual gateway.
virtual gateway. Possible values are notConfigured, inService,
outOfService, disconnected and restarting.
• VG Status: bitmap of status dependencies for current Virtual Gateway
(operational, terminationConfigurationMismatch,
applicationConfigurationMismatch, dependentApplicationUnavailable,
dependentApplicationError).
• Supported Codecs: this value represents bitmap of supported codec.
• Profile: H.248 Profile name used by the Virtual Gateway.
• Profile Version: this field represents the H.248 Profile Version Number
used by the Virtual Gateway.
• Context Num: this value represents the number of contexts supported
by the Virtual Gateway.
• Context Term Num: this value represents the number of terminations
per context supported by the Virtual Gateway.
• Termin Address Format: This parameter shows the full termination
syntax. The format is determined by the virtual gateway type and the
format option.
• Active Media Gateway Controller: Media Gateway Controller
connection (notAvailable, primaryMGC, secondaryMGC).
• MGC Oper Status: operative status of the primary Media Gateway
Controller (notAvailable, commsUp, commsDown).
• InUse MGC IP Address: the UDP port of the primary Media Gateway
Controller currently used by the Virtual Gateway.
• InUse MGC UDP Port: This is the UDP port of the primary Media
Gateway Controller currently used by the Virtual Gateway.
• Secondary MGC Oper Status: operative status of the secondary Media
Gateway Controller (notAvailable, commsUp, commsDown).
• Secondary MGC IP Address: IP address of the secondary Media
Gateway Controller related to the Virtual Gateway.
• Secondary MGC UDP Port: UDP port of the secondary Media Gateway
Controller related to the Virtual Gateway.
134 1/1553-HSC901 003/2 Uen B

• CPU Overload Status: Card’s CPU Overload Status.

• Cpu Overload Rejected Cmd: A rollover count of the H.248 commands
that have been rejected due to a CPU Overload condition.
• Primary CPU Occupancy: Current CPU occupancy (expressed as a
percentage from 0 to 99) of the card’s CPU.
• Date & Time: the timestamp (time that is printed to a file or other
location to help keep track of when data is added, removed, sent,
received) referred to the inventory operation.
SIP Virtual Gateways
(create and delete too) a Virtual Gateways with their parameters for SIP
protocol. In the following there is the description of every folder.
Gateways folder
• Identifier: Value that univocally identifies the virtual gateway
• Domain Name: This is the gateway domain name associated wit the
Virtual Gateway. The domain name of each Virtual Gateway is unique
inside EDA equipment.
• IP Address: local IP address used by the Virtual Gateway for SIP messages.
• UDP Port: The local UDP port number used by the Virtual Gateway for
SIP messages.
• Subnet Mask: This is the subnet mask associated with the IP address
specified in “Virtual Gateway Default GW” parameter. The value of the
mask is an IP address with all the network bits set to 1 and all the hosts
bits set to 0.
• Default GW: IP address of the default gateway for the Virtual Gateway.
• Outer EtherType: The value of the Ether Type field, i.e. Tag Protocol
Identifier, for tagged frames (81:00, 88:A8 and 91:00).
• Outer VLAN Id Tag: This defines the Ethernet Vlan Id tag for signaling
data on current Virtual Gateway. If this value is 0, no Vlan Id tag is
assigned. If this value is -1, no tagging is performed. This field will be
always applied. Possible values are in range fro -1 to 4094.
• Outer Prior. Tag: This defines the Ethernet Priority tag for signaling
data on current Virtual Gateway. This object is only meaningful when
“Virtual Gateway Outer VLAN Id Tag” parameter is different from -1.
• Inner EtherType: The value of the Ether Type field i.e. Tag Protocol
Identifier, for tagged frames, this VLAN tag type is applied to the inner
VLAN tag (81:00 , 88:A8 and 91:00).
• Inner VLAN Id Tag: This defines Vlan Id tag used in the layer 2 VLAN Tag
header for signaling data on current Virtual Gateway. If this value is 0, no
Inner Vlan Id tag is assigned. If this value is -1, no tagging is performed.
InnerVlan is optional. Possible values are in range from -1 to 4094.
1/1553-HSC901 003/2 Uen B 135

• Inner Prior. Tag: This object defines the Ethernet Priority tag in the
layer 2 VLAN Tag header for signaling data on current Virtual Gateway.
This object is only meaningful when “Signaling Gateway Inner VLAN Id
Tag “parameter is different from -1.
• Signalling Dscp: This object defines the DSCP field (Differentiated Services
Code Point) for IP packets of signaling data on current Virtual Gateway.
• Max Concurrent Active Calls: The maximum number of calls (incoming or
outcoming) that may be active at the same time for a given VoIP card. It
may be inserted to reduce the Maximum Number of Concurrent Active Calls
in order to limit the overall power consumption for the Network Element.
• Longhand Format: this value allows reading the enabling/disabling of
the longhand format of the H.248 notation. When set to 'true' the format
is longhand. When set to 'false' the format is shorthand. In case of SIP:
When set to 'true' the format is generic one; when set to 'false' the
format is 'compact form
• Dial Map: dial map that establishes the expected numbers and pattern
of digits for telephone numbers. Patterns are separated by '|' sign.
• Dial Map Emergency: a dial map that establishes the expected
numbers and pattern of digits for emergency telephone numbers.
Patterns are separated by '|' sign.
• Local Transport Protocol: This field represents the preferred local
Transport Protocol used by the Virtual Gateway for SIP messages.
Possible values: udp, tcp.
• Protocol Profile Index: This field describes the protocol profile chosen
in the configurable download mapping file.
• Service Profile Index: This field describes the service profile chosen in
the configurable download mapping file.
• Supported Codecs: this value represents the bitmap of supported
codec. The possible values are:
unknown
g71164kAlaw Æ G.711 64 kbit/s A-law
g71164kmulaw Æ G.711 64 kbit/s mu-law
g71156kAlaw Æ G.711 56 kbit/s A-law
g71156kmulaw Æ G.711 56 kbit/s mu-law
g722 Æ G.722 (SB-ADPCM)
g7231 Æ G.723.1
g7231AnnexA Æ G.723.1 Annex A (silence suppression)
g726 Æ G.726 (ADPCM)
g727 Æ G.727 (Embedded ADPCM)
g728 Æ G.728
g729 Æ G.729 (CS-ACELP)
g729AnnexB Æ G.729 Annex B (silence suppression)
136 1/1553-HSC901 003/2 Uen B

• SIP Protocol Version: This is the version of SIP protocol. It follows the
same format as SIP version information contained in the SIP messages
generated by this SIP entity.
Registrars/Proxies folder
The list of properties below is displayed in the second table for each Virtual
• Identifier: value that univocally identifies the virtual gateway.
• Registrar IP Address: this is the IP address of Registrar server.
• Registrar Port: this is the port of Registrar server.
• Registrar KeepAlive Timer: Timer for checking Registrar availability.
0 means checking is disabled. Timer is expressed in seconds.
• Registrar Expires (secs): this is the time indicating how long the
registration is valid. The value is expressed in seconds (default: 3600).
• Backup Registrar IP Address: IP address of backup registrar server.
• Backup Registrar Port: backup registrar port.
• OutBound Proxy Domain Name: name of the Out Bound Proxy server.
• Outbound Proxy IP Address: this is the IP address of Out Bound
Proxy server.
• Outbound Proxy Port: this is port used by Out Bound Proxy server.
• OutBound Proxy Keepalive Timer: Timer for checking Outband proxy
availability.
• Bck OutBound Proxy IP Address: IP address of backup Outband proxy server.
• Bck OutBound Proxy Port: Port used by backup Outband proxy server.
• Interdigit Timer: If no DialMap defined, INVITE is sent after timer
expiration during dialing (seconds).
Timers folder
The list of properties below is displayed in the third table for each virtual gateway
entry found on each investigated Network Element.
• Identifier: value that univocally identifies the virtual gateway.
• TimerA (100..1000): this object reflects the initial value for the retransmit
timer for the INVITE method. The retransmit timer doubles after each
retransmission, ensuring exponential back offing network traffic. This
object represents the initial time a SIP entity will wait to receive a
provisional response to an INVITE before resending the INVITE request.
• TimerB (32000..300000): This object reflects the maximum time a SIP
entity will wait to receive a final response to an INVITE. The timer is
started upon transmission of the initial INVITE request.
• TimerC (180000..300000): This object reflects the maximum time a SIP
Proxy Server will wait to receive a provisional response to an INVITE.
The timer C MUST be set for each client transaction when an INVITE
request is proxied
1/1553-HSC901 003/2 Uen B 137

• TimerD (0..300000): This object reflects the amount of time that the
server transaction can remain in the 'Completed' state when unreliable
transports are used. The default value MUST be greater than 32000 for
UDP transport and its value MUST be 0 for TCP/SCTP transport
• TimerE (100..1000): This object reflects the initial value for the
retransmit timer for a non-INVITE method while in 'Trying State'. The
retransmit timer doubles after each retransmission until it reaches T2 to
ensure an exponential back off in network traffic. This object represents
the initial time a SIP entity will wait to receive a provisional response to
the request before resending the non-INVITE request.
• TimerF (32000..300000): This object reflects the maximum time a SIP
entity will wait to receive a final response to a non-INVITE request. The
timer is started upon transmission of the initial request.
• TimerG (0..1000): This object reflects the initial value for the retransmit
timer for final responses to INVITE requests. If timer G fires, the
response is passed to the transport layer once more for transmission,
and timer G is set to fire in MIN(2*T1, T2) seconds.
From then on, when timer G fires, the response is passed to the
transport again for transmission, and timer G is reset with a value that
doubles, unless that value exceeds T2, in which case it is reset with the
value of T2. The default value MUST be T1 for UDP transport and its
value MUST be 0 for reliable transport like TCP/SCTP.
• TimerH (32000..300000): This object reflects the maximum time a
server will wait to receive an ACK before it abandons retransmitting the
response. The timer is started upon entering the 'Completed' state
• TimerI (0..10000): This object reflects the maximum time a SIP entity
will wait to receive additional ACK message retransmissions. The timer
is started upon entering the 'Confirmed' state. The default value MUST
be T4 for UDP transport and its value MUST be 0 for reliable transport
like TCP/SCTP.
• TimerJ (32000..300000): This object reflects the maximum time a SIP
server will wait to receive retransmissions of non-INVITE request. The
timer is started upon entering the 'Completed' state for non-INVITE
transactions. When timer J fires, the server MUST transition to the
'Terminated' state.
• TimerK (0..10000): This object reflects the maximum time a SIP client
will wait to receive retransmissions of responses to non-INVITE
requests. The timer is started upon entering the 'Completed' state for
non-INVITE transactions. When timer K fires, the server MUST transition
to the 'Terminated' state. The default value MUST be T4 for UDP
transport and its value MUST be 0 for reliable transport like TCP/SCTP.
• TimerT1 (200..10000): This object reflects the T1 timer for a SIP entity.
T1 is an estimate of the round-trip time (RTT) between the client and
server transactions.
T2 is the maximum retransmit interval for non-INVITE requests and
138 1/1553-HSC901 003/2 Uen B

INVITE responses. It's used in various parts of the protocol to reset other
Timer* objects to this value.
T4 is the maximum duration a message will remain in the network. It
represents the amount of time the network will take to clear messages
between client and server transactions. It's used in various parts of the
protocol to reset other Timer objects to this value.
EDA4.11 Only folder
This folder is contains fields that are valid only for EDA 2530 R4.11.
• Identifier: Value that univocally identifies the virtual gateway.
• Binding Card <shelf>/<slot>: This parameter is used to associate a
virtual gateway to a specific hardware. It is necessary to specify the shelf
and the slot where the card is lodged. The 'none' value with the 'modify'
command is used to unbind the virtual gateway from the card.
• Media Local IP Address: This is the local IP address used by the
Virtual Gateway for media. If this is left empty (0.0.0.0) then the same
local IP address is used for Media and Signaling and it is the one
specified in "Virtual Gw Ip Address" field of the folder “Gateways”.
• Media Subnet Mask: This is the subnet mask associated with the Media
Default Gateway specified in “Media Default GW” parameter. The value
of the mask is an IP address with all the network bits set to 1 and all the
hosts bits set to 0.
• Media Default GW: This is the IP address of the primary default
gateway used for media of current Virtual Gateway. If this is left empty
(0.0.0.0) then the same Default Gateway is used for Media and
Signaling and it is the one specified in “Signaling Gateway Default GW”
parameter.
• Media Dscp: this field defines the DSCP (Differentiated Services Code
Point) parameter for IP packets of media data on the current Virtual
Gateway.
• Media VLANId Tag: This field defines the Ethernet Vlan Id tag for media
data on current Virtual Gateway. If this value is 0, no Vlan Id tag is
assigned. If this value is -1, no tagging is performed.
• Media Priority Tag: This field defines the Ethernet Priority tag for media
data on current Virtual Gateway. This object is only meaningful when
“Media VLAN Id Tag” parameter is different from -1.
• Fixed Forwarding: This parameter enables/disables forwarding traffic
between users, through users Default Gateway. In case it is enabled the
traffic is sent from a user to another through sending users Default
Gateway. Otherwise (disabled) the traffic is sent from a user to another
following the standard IP/Ethernet rules. The possible values are:
* enabled: it enables sending traffic to the sending users Default Gateway.
* disabled: it - uses standard IP/Ethernet forwarding rules.
App.Control folder
1/1553-HSC901 003/2 Uen B 139

virtual gateway. Possible values are: notConfigured, inService,
outOfService, disconnected, restarting.
SIP Terminations
This application allows setting up a user service by creating from scratch,
deleting and modifying VOICE over IP Terminations tied to Virtual Gateways. It
is composed by the following folders:
• Termination
• Application Control
Termination folder
• User Port: info relevant to the physical port. This string must is
displayed in the following way: subrack (sr) / slot (sl) / module (mod) /
port number (port).
• Termination index: This is an incremental index to be assigned to each
sub-termination attached to the same physical line.
• Virtual GW Index: This field is the identifier of the Virtual Gateway to
which current physical port belongs.
• Virtual GW Name: identifier for the Virtual Gateway.
• Media Local IP Address (4.21 only): This is the local IP address used
by the termination for media.
• Phone Number: the phone number on the port. The phone number can
start with '+' and contains only numeric characters. This field is
mandatory for SIP terminations.
• UserName: the username associated to the phone number.
140 1/1553-HSC901 003/2 Uen B

• Password: the password associated to the username.

• Supported Services: bitmask representing the set of services
supported by current termination. (callHold, consultationHold,
callWaiting, threePTYConference, explicitCallTransfer, clip, hotLine,
callDeflection). To display the services enabled, click on the
hexadecimal value.
• Admin Status: The operator sets this parameter to command the
block/unblock of the termination. Possible values:
* forcedBlock: User port is taken out of service immediately, even if busy.
* block: User port is taken out of service only if it is not busy.
* unblock: User port is brought into service.
• Oper Status: It represents the operational status of the termination.
• Termination Name (4.11 only): The complete descriptive name that
describes this termination and its use. This is a unique identifier that is
assigned to the termination and it is used in the protocol messages that
are sent from the gateway.
• Status: It represents the operational status of the termination
• Busy Status (4.11 only): the status of the application use of the
termination (null, idle, busy).
• Active Channels: the number of media channels that are currently

active on the termination.
virtual gateway. Possible values are: notConfigured, inService,
outOfService, disconnected, restarting.
• Result: it shows response for the operations executed (OK, ERROR).
1/1553-HSC901 003/2 Uen B 141

Handling of the VoIP pull-down menu, buttons and other features

This paragraph shows the meaning of the pull-down menu in the VoIP
Management tool.
According to the application chosen (H248 Virtual Gateways, H248
Terminations, etc.) some of the buttons below explained can be omitted or
appear in different mode.
From the File menu, the following menus are listed:
• Open: To open a configuration saved in the PC hard disk.
• Save: To save the configuration.
• SaveAs: To save the configuration in PC hard disk in several formats.
• Print active table: To print only the active table.
• Print all tables: To print all the tables.
• List Cached Ne: it shows a list of all Network Elements whose data are
currently held in the application persistent storage area (usually referred
as the application's data cache). From the list window, each found NE
name may be copied to the main view's NE list box, to be used for
extracting cache's data or refreshing them from the network.
• Exit: this menu allows the Operator to exit from VoIP Inventory window.
• Forced exit: this menu allows to user to exit in a forced way because
the application doesn’t permit simply exit.
From the Edit menu, the following menus are listed:
• Undo (on Active view): to return to previous action
• Copy: To copy a cell, a row or a column from the table.
• Cut cells: To cut a cell, a row or a column from the table.
• Paste: To paste a cell or a row or a column from the table.
• Delete rows: To delete a row (or rows if these are selected).
• Insert empty row: To insert a new empty row.
• Paste & spread: To spread a pasted cell of the table, in a certain
number of selected cells, either horizontal or vertical.
• Paste & spread & increment: To spread and increment the value of a
pasted cell of the table, in a certain number of selected cells, either
horizontal or vertical.
• Concat & spread: to concatenate the new string to the old rather than
replacing it.
• Merge cells: To merge many cells or rows of the table.
• Split merged: To split the cells before merged.
• Protect Selection: To protect a cell. It will not be possible to write into
this cell.
• Unprotect Selection: To unprotect a cell. It will be possible to write into
a cell, before protected.
• Replace/Insert substring: To perform editing modifies in the strings.
From the Table menu, the following menus are listed:
142 1/1553-HSC901 003/2 Uen B

• Clear Views: this option allows canceling the data containing in the
tables.
• Open Form for Advanced Query: this option allows finding some data
using a SQL query form.
It is possible to use this tool only if a Read Network operation has been made.
The Exact match check button allows performing a search in the specified field.
The Replace button inserts the data of the search in the table erasing the old
value. The Add button allows viewing the result of the old search and the new
data.
Clear cache, this option allows canceling data containing in the cache tables.
From the View menu, the following menus are listed:
• Restore default colors: to restore the normal table's colors, removing
any color tag that may have been put there to flag the success or failure
of an operation.
• Collapse column: this menu allows Operator to collapse the column selected.
• Expand column: this menu allows the Operator to expand the column
before collapsed.
• Show NE address line: this menu shows the address line to the Operator.
• Show format toolbar: this menu allows the Operator to displays some
useful toolbars for the data formatting (e.g. to change a field to normal to
bold, to change its font…). Moreover it allows displaying the Rows
spinner in order to add the rows.
• Flat buttons look: to display the button in flat mode (no borders
highlighted)
• Set columns visibility: only for UNIX systems.
• Draw stripes: this menu improves the visibility, filling (in violet) odd lines.
• Clear stripes: this menu allows clearing before filling by means of the
Draw stripes menu.
From the Options menu, the following items are listed:
• Stop on Error: to stop applying the configuration sheet at the first error
• Enable Report mode: to produce a report file containing all the I/O data
(including result codes and error descriptions), at the end of each
configuration run.
Termination Search Criteria, this option allows to find the desired voice
terminations. Reading terminations from network can be restricted to a subset
based on a selection of values for:
• shelf (1..4);
• slot (1..21,all);
• or for particular termination name (physical indication in term of
shelf/slot/port).
H248 Gateway Search Criteria, this option allows to find the desired virtual
gateways. Reading from network can be restricted to a single Network
Element's gateway. To do so, check the "By Identifier" radio-button from the
Gateway Search Criteria frame.
1/1553-HSC901 003/2 Uen B 143

• Searching by Identifier;
• Requires exactly typing the Identifier of a Virtual Gateway.
2.4.20 System Info

PATH: (Configuration -> System Info)
This window resumes some information relevant to the equipment.
The equipment is able to store the following information:

• System Name: to store a name for the equipment;
• Administrator: to indicate the system administrator's name;
• Location: to indicate the name of the location where the equipment is
installed;
• System Description: to read a textual description of the system;
• SNMP SysObjectID: to read the vendor's authoritative identification of
the network management subsystem which contain the equipment;
• Services: to read the set of services that this entity potentially offers;
• Start Up Time: to read the last time that the network management
portion of the system was re-initialized.
144 1/1553-HSC901 003/2 Uen B

2.4.21 Equipment Date and Time Configuration

PATH: (Configuration -> Equipment Date/Time)
This item is used to set the date and time of the equipment and to add or
remove the Network IP addresses of the NTP Service.
The following sections compose the window:

Equipment Date and Time
The section allows set the equipment date and time.
1. Set the equipment local time in the Time field using the format: hh:mm:ss.
2. Chose the Time Zone by clicking on the arrow.
3. Select the Date by clicking on the "calendar" icon button using the format:
mm:dd:yyyy.
4. Click on the blue left arrow to select the next month.

5. Click on the blue right arrow to select the previous month.
6. Select the day. The red line box represents the day selected.
7. Press Apply to confirm the selection.
1/1553-HSC901 003/2 Uen B 145

8. Select Refresh to update the window.

NTP Service Status
The section allows enabling or disabling the NTP Service, by clicking on the
relative check box, and pressing Apply.
Frequency NTP Engine sub-section is composed by:
• Frequency NTP Engine scroll list: enable/disable the NTP engine;
• Outgoing DSCP value spinner: to assign a level of traffic service,
transmitted by this Equipment;
• Frequency NTP Engine status: the status of the Frequency NTP
Engine;
• Current NTP Server IP Address: the IP address of the NTP Server;
• Successful Time Server reselections: number of successful
reselections.
NTP Peers Table
The section allows adding or modifying a Network IP address of NTP Service.
The meanings of the columns are:
• Peer IP Address, IP address of an NTP Peer. New NTP Peers may be
added by using the Add Peer button;
• Controller Mode, this item is set to client.
• Stratum, indicates the stratum of the clock. The stratum defines the
accuracy of a timeserver. Higher is the stratum value and lower is the
accuracy [0, unspecified; 1, primary reference (e.g, calibrated atomic
clock, radio clock); 2-255, secondary reference (via NTP)].
• Reachable, indicates if the NTP Peer is accessible from the Controller;
• Delay (sec), the estimated round-trip delay of the peer clock from the
local clock over the network path, expressed in second. This variable
can assume a positive or negative value, depending on the clock
accuracies and the skew-error accumulation;
• Offset (sec), the estimated offset of the peer clock from the local clock,
expressed in seconds;
• Dispersion (sec), maximum error in seconds of the peer clock relative
to the local clock over the network path, expressed in second. Only
positive values greater than zero are possible.
• Recv Pkts, total number of received NTP packets.
• 1% delay, 1 percent of the received NTP packets with delay in addition
to the minimum delay (in ms).
• 10% delay, 10 percent of the received NTP packets with delay in
addition to the minimum delay (in ms).
• 50% delay, 50 percent of the received NTP packets with delay in
addition to the minimum delay (in ms).
Add/Remove Network IP Addresses of NTP Service
146 1/1553-HSC901 003/2 Uen B

1. Select Add Peer to display the link ADD NTP Peer window.
2. Insert the new address on the NTP Peer IP Address field.
3. Select Apply to confirm and Close to exit the window.
2.4.22 SCTS - Centralized Timing Source Configuration

PATH: (Configuration -> SCTS Service)
This item is available through the shortcut showed in main window below:
The SCTS has the purpose to extract a Network Timing Reference (NTR) from
the line symbol timing of any traffic interface able to carry a NTR and to
distribute it to all the interface cards to make all the outgoing traffic streams
synchronous with such NTR.
This function is used to manage the SCTS (Simplified Centralized Timing
Source), to select different timing sources options (up to eight sources) to be
used by the centralized equipment synchronization.
The SCTS module will use automatically the synchronization source configured
with the highest priority if the parameter “Quality Level Mode” is disabled or if
this parameter is enabled it will use the source with the better quality level and
highest priority.
Inside the "Configure SCTS Service" window, two sections are shown:
1. Synchronization Parameters section: This section allows viewing or modifying
the parameters that the synchronization process uses, to determine the Master
Line. There are two different methods:
1/1553-HSC901 003/2 Uen B 147

Non Revertive Mode

when a timing source is recovered, the "source process selection"
checks if the source should be used as master. If the response to the
check is affirmative, then the source will be set as master when the
source current used will fail;
Revertive Mode
when a timing source is recovered, the "source process selection"
checks if the source should be used as master. If the response to the
check is affirmative then the source is immediately set as master.
In the Quality Level Mode scroll list it is possible to choose if the System will
operate in Quality mode in added to the priority.
In the Minimum Quality Level scroll list it is possible to assign the
synchronization quality level of a signal. The number in the brackets is an
association between the quality and its use (the lower the number the higher the
quality priority, the value = 99 means source do not to be used in any case).
The possible values in case of E1 or STM-1 Interface in ETSI standard are:
• PRC: the source transports a timing generated by a Primary Reference
Clock (G.811), quality priority=10.
• SSUA: the source transports a timing generated by a G.812 type I or V
clock, quality priority=20.
• SSUB: the source transports a timing generated by a G.812 type VI
clock, quality priority=30.
• SEC: the source transports a timing generated by an SDH Equipment
Clock (SEC) fulfilling G.813 option 1, quality priority=40.
• DNU: the source should not be used for synchronization (Do Not Use),
quality priority=99.
The possible values in case of E3 Interface in ETSI standard are:
• PRC: the source transports a timing generated by a Primary Reference
Clock (G.811), quality priority=10.
• DNU: the source should not be used for synchronization (Do Not Use),
The possible values in case of DS1Interface in ANSI standard are:
• PRS: the source transports a timing generated by a Primary Reference
Source (G.811), quality priority=10.
• STU: the source transports a timing generated by a source with
Synchronized Traceability Unknown, quality priority=20.
• ST2: the source transports a timing generated by a Stratum 2 Clock
(G.812 type II), quality priority=30.
• TNC: the source transports a timing generated by a Transit Node Clock
(G.812 type V), quality priority=40.
• ST3E: the source transports a timing generated by a Stratum 3E clock
(G.812 type III), quality priority=50.
• ST3: the source transports a timing generated by a Stratum 3 clock
(G.812 type IV), quality priority=60.
148 1/1553-HSC901 003/2 Uen B

• SMC: the source transports a timing generated by a SONET clock

fulfilling G.813 Option 2, quality priority=70.
• ST4: the source transports a timing generated by a Stratum 4 clock,
• PROV: the Quality Level settable by the Network Operator in the range
1..99.
• DUS: the source should not be used for synchronization (Do not Use for
Synchronization), quality priority=99.
The following values are valid either in ETSI or in ANSI mode if anything is
transmitted outside the equipment over an interface:
• Failed: the source is in a failure condition, or the relevant card is not
inserted or the card is failed or the equipment controller is not able to
communicate with the card, quality priority =99.
• NotSupp: the source is not able to carry SSM/TM messages (i.e. 2MHz
and DS3, DS1 can be set to carry or not) or the SSM/TM monitoring for
this source has not been enabled, quality priority =99.
• Invalid: the SSM/TM monitoring is enabled on the source but no valid
SSM/TM code has been received and accepted, quality priority =99.
Choose Apply to confirm or Refresh to update the section.
2. Synchronisation Nominated Source section: This section displays the list of
the Source Interface (up to eight) candidates to become the reference clock for
the equipment. The following information can be found:
• Index: this number represents the row, to identify a synchronism source
with a unique number.
• Source Interface: this column represents the synchronism source
physical position inside the subrack.
• Clock Degrade: the column represents an Alarm indication. When the
synchronism source is affected with an EFO-Excessive Frequency
Offset (and so it is not available any more as clock reference) an alarm
indication is shown under this column and the button "Reset Clock
Degrade" becomes available, to allow the clear of this alarm condition.
• WTR (min.): the column represents the time (from 0 to 12 minutes in 1
minute step) while a synchronism source that has been declared
unavailable can be considered for the selection process again. It
represents a waiting time to avoid intermittent switches of the
synchronism source;
• WTR Status: the column shows if the synchronism source is under WTR
(Wait to Restore) condition. It is not possible to manually exit the source
from this status;
• Priority: the column represents the priority level of the synchronism
source nominated to become the clock reference. The value "1"
represents the highest priority, the value "8" represents the lowest one,
while the value “Not Nominated" represents a null value and the source
selection process will not consider the sources with this value.
1/1553-HSC901 003/2 Uen B 149

• Locked Out: the column states that the source has been locked-out by
an operator command.
• Rx Quality Level: the column represents the quality level received from
this synchronization source.
• Rx QL Override: the value in this column is used to overwrite the quality
level of each synchronization source.
• Tx Quality Level: the value in this column provides the SSM/TM
message.
• Available: this column shows if the synchronism source is candidate for
a possible nomination to become the clock reference. If the source is in
WTR status or if the interface is faulty, the synchronism source will not
be available. When the synchronism source is used as Synchronization
Master, the index "YES-MASTER" will be shown.
SETG Compliance field shows the characteristics of the Synchronous
Equipment Timing Generator (G.813 Option 1, G.813 Option 2, Stratum 3, and
Stratum 4).
SETG Status (Synchronous Equipment Timing Generator) field indicates the
synchronization status of the Equipment (locked-free running).
Synchronisation Master field indicates which synchronization source listed in
the table is Master. If the Equipment is not locked to a synchronization source
this field has none value, instead if the Equipment is locked and then
synchronized this field has the Index of the synchronization source.
Reset Clock Degrade button is active when a condition of alarm is present in a
synchronization source (Clock Degrade field in alarmed state). By pressing this
button is possible to delete the alarm.
To add a synchronization source to the table

1. Press the Add Entry button in Configure SCTS Service window to add a new
source by means of the Add Synchronisation Source window.
150 1/1553-HSC901 003/2 Uen B

Index: this number represents the row, to identify a synchronism source with a
unique number.
1. In the Interface Type NTP Engine scroll list is possible to choose between:
Line, the Synchronization Source is a card inserted in the Equipment.
Station, the Synchronization Source is an external line (2Mbit or 2MHz).
NTP Engine, the Synchronization Source is an external NTP service.
2. The Station Interface ID field represents the address of the Station Interface
(external line).
This parameter is shown only when the Interface Type is configured as
Station.
3. The Station Interface Type indicates the type of stream used (2MHz, E1
Structured, and E1 Unstructured).
4. The Station Interface Sa Bits Config allows configuring which Sa bit of the E1
frame is used to convey the SSM message.
This parameter is applicable only if the Interface Type is Station and when the
Station Interface Type is E1 Structured or E1 Unstructured.
5. Insert in the Slot field the physical slot position where the unit is lodged.
6. Insert in the Port field the number of the port.
The parameters Slot and Port are meaningful only when the Interface Type is
configured as Line.
7. By means of the relevant spinners insert the Wait to Restore (WTR) Time
(min.). This value represents the time (from 0 to 12 minutes in 1 minute step)
while a synchronism source that has been declared unavailable can be
considered for the selection process again. It represents a waiting time to avoid
intermittent switches of the synchronism source
8. By means of the relevant spinners insert the Priority Level. This value
represents the priority level of the synchronism source nominated to become the
clock reference. The value "1" represents the highest priority; the value "8"
represents the lowest one.
9. In the Locked Out field is possible to lock a nominated source.
10. The Overriding Rx SSM/TM field is used to enable/disable the overwriting of
the synchronization source quality level.
11. The SSM/TM override value field is used to overwrite the quality level of each
synchronization source.
12. Press Apply to confirm.
To modify a synchronization source:

1. Select in the Configure SCTS Service table, the row containing the source to
be modified.
2. Click on the Modify Entry button inside the "Configure SCTS Service” window
to change the parameters of a pre-existent synchronism source.
1/1553-HSC901 003/2 Uen B 151

3. Modify the Wait to Restore (WTR) by means of the relevant spinner.

4. Modify the Priority Level to the synchronization to be modified.
5. Modify the Locked-Out field.
6. Modify the Overriding Rx SSM/TM field.
7. Modify the SSM/TM override value field.
8. Press Apply to confirm.
Delete a synchronization source:

1. Select in the Configure SCTS Service table, the row containing the source to
be deleted.
2. Click on the Delete Entry button inside the "Configure SCTS Service” window to
delete the selected synchronism source from the table.
A pop-up to confirm the operation will appear.
2.4.23 Connection Modules

PATH: (Configuration -> Connection Modules)
This application is used to edit/modify the connection modules inserted in the
Equipment. According to the type of Connection Module, they may be
automatically detected and auto configured when physically inserted in the
Equipment.
152 1/1553-HSC901 003/2 Uen B

How to configure the Connection Modules

1. Select the row related to the module to be configured.
2. Press View/Modify selected Connection Module button.
The following window will appear:
1. Insert in the Connection Module Type scroll list the type of Connection Module
used.
2. Press Apply to confirm this operation.
3. By means of the 60 check boxes, is possible to choose which line will be
associated to an external device. The Operator must check only the line to be
connected as external device.
4. Press Apply to confirm this operation.
The section relevant to the check boxes is valid only for cm-adslpotsx60-PPB
connection module type.
5. Press Refresh to update or Close to exit.
2.4.24 Line Test

PATH: (Configuration -> Line Test)
This menu collects a series of applications that execute the management of
different type of tests on user lines. This menu is common to different types of
lines (POTS, ISDN SHDSL).
2.4.24.1 Equipment Level Configuration
PATH: (Configuration ->Line Test -> Equipment Level Configuration)

This window allows the Operator to configure the Equipment parameters for the
line and interface test.
1/1553-HSC901 003/2 Uen B 153

1. Insert the Relay’s switch-back timeout (secs) by means of the relevant

spinner. This value represents the time to wait before the relays are
automatically switched back in order to re-establish traffic. The possible values
are zero or a range from 60 to 1800. Value 0 means that there is no timeout, i.e.
relays are not released automatically.
2. Insert the Delayed Test expiration time (mins) by means of the relevant
spinner.
3. Insert the Voice Automatic Test interval (mins) by means of the relevant
spinner. This is the period between two consecutive starts of the automatic test
process. The possible values are in a range from 720 to 1440.
2.4.24.2 Line Test Input Profiles
PATH: (Configuration-> Line Test -> POTS/ISDN Line Test Input Profiles)
This application allows the operator to create, delete, and modify VCP Test
Profiles. The GUI is an all-in-one editor/browser/writer tool, with one folder. This
folder contains an editable spreadsheet-like table for a consistent set of
parameters. The equipment name (or IP address) is the first field. The data
displayed in each row are always related to the equipment referred to. The fields
"Result" and "Error" are of read-only type: such fields are displayed when
reading from equipment. A default profile, named DEFVAL, is furnished by the
equipment.
• NE Name: the IP address of the Equipment.

• Profile Name: the name of a profile associated to the test.
• Filter: the type of filter applied to the received signal during the Active
and Passive Noise with filter test. The following filter types are defined:
154 1/1553-HSC901 003/2 Uen B

none : no filter
filter3KHz : 3 KHz Filter
filterCMSG : C-Message Filter
filter15KHz : 15 KHz Filter
filter3dot4KHz : 3.4 KHz Filter
filterD : D-Filter
• Test Type: the REN measurement technique used and it can have the
following values:
regularPhone: regular phone REN test.
electronicPhone: electronic phone REN test
• Threshold Power: the minimum signal power (in tenths of dBm0) that
must be observed for at least 178 ms for this test to return a meaningful
result. If no signal is seen meeting this requirement within 8 seconds,
then the test times-out and returns a zero-power result.
• Break Percent: the length of the break (open-circuit) period for a single
pulse and is specified as a percentage of the pulse (make plus break)
period. The make period is therefore 100% minus break Percent of the
pulse period. This input must be greater than 20% and less than 80%.
The actual break period may be further limited by the switching
characteristics of the test circuit.
• Pulse Per Second: the duration of each pulse (make plus break) period
and is specified as a pulse rate (pulses per second). This input must be
greater than 7 and less than 13. The maximum pulse rate may be further
limited by the switching characteristics of the test circuit.
• Dtmf Digit: the expected value of the decoded DTMF digit. Possible
values from digit0 to digit9.
• Tone Frequency: the frequency (specified in Hertz) of the tone
generated during the Trans Hybrid Loss test. Possible values:
hz200(0) : 200 Hz
hz400(1) : 400 Hz
hz1020(2): 1020 Hz
hz3500(3): 3500 Hz
• Tone Power Level: the tone generated during the Trans Hybrid Loss
test. The tone power level is specified in tenths of dBm referenced to the
zero transmission level point, or dBm0.
• Signal Power: 1010 Hz signal output during Signal to Noise Ratio Test.
• Command: the operation to perform: create, delete, modify
2.4.24.3 Line Interface Test
PATH: (Configuration Æ Line Test -> POTS/ISDN/SHDSL Line and Interface Test)
This option allows the Operator to perform line test on the POTS/ISDN/SHDSL
cards.
1/1553-HSC901 003/2 Uen B 155

The tests performed over each line are configurable by means of the Test
Mask, Test Extension Mask and Tone Profile fields. The extension tests (that
are configurable by the column Test Extension Mask) require setting a Test
Profile also. The management of the Test Profiles is executed in an external
application (Configuration Æ Line Test Æ POTS/ISDN Line Test Input Profiles).
The extension tests are only in manual mode.
The application is divided in two different folders: Tests, which set the line test
parameters and Result to display the result of the test.
How to perform a test line
1. Select a row from the table, and then double click to write in the table.
2. Insert a name for the line test.
3. Select the NE from the relevant scroll list. For the AXH/EDA-LCT, only one NE
will be accessible.
4. Choose the type of test:
Automatic, this test is available only for the POTS cards.
Manual, test performed port by port. Operator must choose the port to test.
5. If the test is manual, specify the Subrack, slot and port.
Only the slot with an inserted card will be shown. The Card field is automatically
filled with the type of the card relevant to the slot number inserted by the
Operator.
6. In the Test Mask field the Operator is able to choose:
All,all the tests are chosen and enabled.
Update, it allows to enable some items among a set of test already enabled
by default.
New, it allows enabling a set of line tests to perform among all the possible
tests, in order to create a new profile that can be saved.
156 1/1553-HSC901 003/2 Uen B

Delete, it allows to delete a customized Test Mask profile.

7. In the Test Extension Mask field the Operator is able to choose
All, all the tests are chosen and enabled.
Update, it allows to enable some items among a set of test already enabled
by default.
New, it allows enabling a set of line tests to perform among all the possible
tests, in order to create a new profile that can be saved.
Delete, it allows to delete a customized Test Mask profile.
8. In the Test Profile field the operator can insert a test input profile name. If any
test input profile has been configured, "DEFVAL" must be set. The management
is executed in an external application (Configuration -> Line Test -> POTS/ISDN
Line Test Input Profiles).
9. In the Command field (CMD) the Operator has to specify the action to perform:
Start, to start the tests collection.
Stop, to stop the tests collection.
Force, to force starting collection when the resource is busy (only for manual test).
Delay, to wait starting collection when the resource is busy (only for manual test).
check test result, to verify the result of the test even if the resource is busy.
It is used to read the actual state of the resource (test in progress, test
in pause, test completed).
automatic test status
to verify if there are automatic tests in progress. It is used to read the
actual state of the resource (test in progress or test completed).
Status field shows the state of the line.
Error field notices the Operator about the response of the test.
Error Descr field gives to the operator a brief description of the error (in case of
error).
When the Operator enable a Test Mask the following mask will appear:
Test Mask field is used to assign a name to a profile, the Select All button
enables the selection of the entire test while Reset erases the entire test before
checked.
1/1553-HSC901 003/2 Uen B 157

Set As Default check box allows the Operator to configure that profile as
default.
OK button applies the modifications, Close allows to exit without changing the
parameters.
The possible basic tests to be started are:
• DC Voltage A to B, this test measures the Continuous Voltage between
A and B
• DC Voltage A to Gnd, this test measures the Continuous Voltage
between A and ground
• DC Voltage B to Gnd, this test measures the Continuous Voltage
between B and ground
• AC Voltage A to B, this test measures Alternate Voltage between A and B
• AC Voltage A to Gnd, this test measures the Alternate Voltage A and
ground
• AC Voltage B to Gnd, this test measures the Alternate Voltage between
B and ground
• Resistance A to B, this test measures the Resistance between A and B
• Resistance A to Gnd, this test measures the Resistance between A and
ground
• Resistance B to Gnd, this test measures the Resistance between B and
ground
• Capacitance A to B, this test measures the Capacitance between A and B,
i.e. Continuity Loop
• Capacitance A to Gnd, this test measures the Capacitance between A
and ground
• Capacitance B to Gnd, this test measures the Capacitance between B
and ground
• Battery Feed Voltage, this test measures the Battery Feed Voltage
• Loop Current, this test measures the Loop Current
• Reverse Polarity Resistance A to B, this test measures the Reverse
Polarity Resistance A and B
• Ring Voltage – loaded, this test measures the Ring Voltage with load
• Off-Hook Detection, this test measures the Off-Hook Detection
• Dial-Tone Test, this test measures the Dial Tone Test
When the Operator enable a Test Extension Mask the following mask will
appear.
158 1/1553-HSC901 003/2 Uen B

The Test Extension Mask field is used to assign a name to a profile, the Select
All button enables the selection of the entire test while Reset erases the entire
test before checked.
The Set as Default check box allows the Operator to configure that profile as
default.
The OK button applies the modifications, Close allows to exit without changing
the parameters. Possible extension tests are:
• Resistance A to B with offset, this test measures Resistance A to B with
offset
• Resistance A to battery, this test measures the Resistance A and battery
• Resistance B to battery, this test measures the Resistance B and battery
• Active Noise, this test measures the sum of the line circuit active noise
and the subscriber loop noise using one of selected weighing filters
• Distance To Open, this test diagnoses a line to locate a cable cut
• Passive Noise, this test measure the sum of the line circuit passive noise and
the subscriber loop noise using one of the selected weighing filters
• Ringer Equivalency Number Test, this test calculates the Ringer
Equivalency Number for the telephone attached to the line
• Arbitrary Single Tone Measurement, this test measures the frequency
and power of a single arbitrary tone between 0 and 4000 Hz
• DC Feed Self Test, this test verifies the capability of the SLIC to drive
currents into a load and to measure the voltage developed across it
(using dummy load)
• On/Off Hook Self Test, this test verifies the capability of the line card
circuitry to detect a simulated on-hook and off-hook event
• Ringing Self Test, this test verifies the capability of the line card circuitry
to generate a ringing voltage at reduced amplitude and to perform ring
trip upon a simulated off-hook event
• Metering Self Test, this test verifies the capability of the line card
circuitry to generate a metering pulse at reduced amplitude
1/1553-HSC901 003/2 Uen B 159

• Dialing Self Test, this test verifies the capability of the line card circuitry
to detect pulse dialing and DTMF dialing; tones and pulses are
generated by the interface itself.
• Transmission Test, this test verifies that the line card can pass signals
in the digital to analog and analog to digital direction; it measures trans-
hybrid loss open-circuit and a load impedance applied to the line; these
trans-hybrid loss results are checked against expected values to
generate a pass/fail result
• Trans Hybrid Loss, this test measures the Trans Hybrid Loss of the line
circuit by generating a tone and measuring the reflected signal (the
subscriber loop is always connected)
• Signal to Noise Ratio, this test measures the signal to noise ratio
due to circuit noise and quantization distortion while applying a 1000 Hz
test tone to the loop
• ISDN Pattern Injection Test with Loopback 1, this test executes a pattern
injection test with loopback in LT towards the ET (i.e. local loop).
Injected pattern is a fixed one and cannot be chosen and also the test is
fixed. Only for ISDN boards. It has not effect on other kind of boards.
• ISDN Pattern Injection Test with Loopback 2, this test executes a pattern
injection test with loopback in NT (i.e. remote loop). Injected pattern is a
fixed one and cannot be chosen and also the test is fixed. Only for ISDN
boards. It has not effect on other kind of boards.
Results folder is used to read the results of the test.
2.4.24.4 ADSL2 Diagnostic (DELT)
PATH: (Configuration Æ Line Test ->ADSL2 Diagnostic (DELT))

The purpose of the ADSL2 Diagnostics test is to measure the ADSL2 line
quality from the IP DSLAM to the customer’s ADSL modem. ADSL2 Diagnostics
is an ADSL2 function (ITU G992.3) that uses the IP DSLAM together with the
CPE modem to estimate the line quality. ADSL2 Diagnostics test is part of, and
defined by the ADSL2 standard G.992.3, and the ADSL Management standard
G.997.1. The test is an active two-way test that requires a CPE modem that
supports ADSL2 or ADSL2+. Further more, the test requires that the line must
be deactivated, which means that the End user cannot use the line (the test will
however not influence any POTS connection). Contrary to the SELT, which is a
one-way test that estimates the line properties by the reflection of the signal,
ADSL2 Diagnostics is a two-way test where one transceiver sends a signal,
which is measured by the receiving transceiver. Through different
measurements the line properties are determined. For a more detailed technical
description of the test, please refer to the ITU G.992.3 and G.997.1 standards.
ADSL2 Diagnostics test can only be executed when the line is deactivated. Any
End user sessions will therefore be interrupted if an ADSL2 diagnostics session
is executed. ADSL2 diagnostics can be executed either from AXH/EDA-LCT or
from the command line. In AXH/EDA-LCT the results are presented as values
for parameters that apply for the line, values and graph for parameters that
apply for sub carriers. The results can also be exported to separated text file.
160 1/1553-HSC901 003/2 Uen B

Each parameter has values for downstream, and values for upstream. The
following parameters are included in the Loop diagnostics:
Line parameters
• Loop attenuation: defined in G.997.1 as Line Attenuation (LATN).
Defined as difference between the total transmitted power and total
received power (dB). All sub carriers are used in the calculation.
• Signal attenuation: defined in G.997.1 as Signal Attenuation (SATN).
Defined as difference between the total transmitted power and total
received power (dB). Only sub carriers that are used as bearer are part
of the calculation.
• Signal to noise ratio: defined in G.997.1 as Signal-to-Noise-Ration-
Margin (SNRM). This parameter gives the maximum noise that can be
induced on the line while still meeting the targeted Bit Error Rate (BER)
on all sub carriers (dB).
• Attainable net data rate: defined in G.997.1 as Maximum Attainable Data
Rate (ATTNDR). This parameter gives the maximum attainable net data
rate (without ADSL coding) that can be achieved, while still meeting
targeted SNR and BER, and accounting for available coding and
latency. The unit for this exported parameter is bps (bits per second).
• Transmit power: defined in G.997.1 as Actual Aggregated Transmit
Power (ACTATP). This parameter gives the total amount of transmit
power (dBm).
Sub-carrier parameters
• Transfer function: This parameter is not directly defined in the standard.
G.992.3 defines CCF-ps as the Channel Characteristic Function H (f)
per sub carrier as a complex transfer function per sub carrier.
• Attenuation (log): defined in G.997.1 as the logarithmic representation of
the transfer function in dB (HLOGps). This parameter contains only the
real part of the complex transfer function value.
• Quiet Noise: Quiet Line Noise PSD per sub carrier is defined in G.992.3
as the noise present in a particular sub carrier when no signal is present
(QLN-ps). The unit of this parameter is dBm/Hz.
• SNR margin: Signal-to-Noise-Ratio per sub carrier (SNRps) is defined in
G.992.3 as the ration between the received signal and the received
noise for a particular sub carrier (dB).
Most parameters have a special value (defined in the standard) indicating out of
range or not measurable. These values are exported as “Out of range” text.
WARNING After a test session the line will remain disabled.
1/1553-HSC901 003/2 Uen B 161

How to perform a test line
1. Select Tests folder.

2. Select a row from the table, and then double click to fill the table.
3. Insert a Name for the line test. This field is not mandatory.
4. Select the NE from the relevant scroll list.
For the EDA-LCT, only one NE will be accessible from the scroll list.
5. Specify the Subrack.
6. Specify the Slot.
Only the slot equipped with an appropriate card will be shown.
The Card field is automatically filled with the type of the card relevant to the
slot number inserted by the Operator.
7. In the Command field (CMD) the Operator has to specify the action to perform:
Start, to run an ADSL2 Diagnostic session.
check test result, to retrieve the results of the last ADSL2 Diagnostic test
session.
8. Status field shows the state of the test.
9. Error field notices the Operator about the possible error in the test.
10. Error Descr field gives to the operator a brief description of the error (in case of
error). The test of diagnostic employs about 2 minutes for each line.
11. Press the button "Apply" to start the selected command ("start" or "check test
result").
ADSL2 Diagnostic Utilities
There are two available utilities to save, load and see precompiled lines:
• Save.
162 1/1553-HSC901 003/2 Uen B

• Load.
Save utility (File -> Save) saves precompiled lines (and results) to file in CSV
format (and automatically in .raw format). In a second while you can import them
with Load option (from CSV and raw format) and execute them again. These
lines are saved in CSV format file so you can also import and modify them with
an ASCII editor (VI, notepad) or with Excel application (setting separator char=’;’
in Control Panel -> Regional Setting -> Number -> List Separator).
• Cancel: it allows breaking the command on a line and the session test
continues on the subsequently line.
• Abort: it allows to break the whole session test.
• Exit: it allows to close this application.
How to see the results

You can see in the General folder the results for the following counters:
DS stands for downstream, US stands for upstream.
• Attainable net data rate DS
• Attainable net data rate US
• Loop Attenuation DS
• Loop Attenuation US
• Signal Attenuation DS
• Signal Attenuation US
• Signal to noise ratio DS
• Signal to noise ratio US
• Transmit power DS
• Transmit power US
The others folders (for example "Transfer function (real)-DS") show the results
of the test by tones.
You can see the results of these last counters in graphical mode also.
In order to see the graphic for these counters execute the following instructions:
1. In the "Tests" folder select the line where the Status field is set to "completed"
and then click.
2. Select the command "Export Tests to Graph".
3. Select "Yes" button when the following question is displayed: "Export Tests to
file in graph format?"
4. Fill the field "Nome file" (for default the file is stored in
C:\usr\local\lib\data\Graph\LoopDiag directory)
5. Click on "Save" button.
6. In the "Tests" folder select the line where the Status field is set to "completed"
and then click.
7. Select the command "Graph Tests" in order to display, tone by tone the ADSL2
graph as shown below.
1/1553-HSC901 003/2 Uen B 163

2.4.24.5 xDSL SELT
PATH: (Configuration Æ Line Test ->xDSL SELT)

The Single Ended Line Test (SELT) is an application that is used to test the
physical line (loop) in order to evaluate and maintain the ADSL service to the
customer. Using advanced frequency and time domain analysis, this function
can be used for estimating both the length of the local loop and which ADSL
services it is possible to deliver through the local loop. The SELT function is
entirely software based, enabling subscriber line tests to be performed without
dedicated test HW. A test is initiated from AXH/EDA LCT without requiring any
cable type knowledge input. The SELT function enables the operator to test the
physical line (loop) in order to give guidance for ADSL service deployment and
maintenance. The SELT consists of sending and analyzing a wide-band test
signal combined with measuring the noise present on the line. The line noise is
measured in the upstream band and estimated for the downstream band.
The following single value parameters are estimated or measured by the
AXH/EDA LCT:
• Downstream Capacity (bps): Estimated downstream bandwidth in bps.
Estimating the capacity may vary due to environmental differences.
Estimations should therefore be used as guidelines only.
• Upstream Capacity (bps): Estimated upstream bandwidth in bps.
Estimating the capacity may vary due to environmental differences.
Estimations should therefore be used as guidelines only.
• CPE presence Indicator shows the type of powered-on CPE modem
connected to the line. Indications are:
* open
* short
* matched
* cpePowerOnAnnexA
* cpePowerOnAnnexB
* cpePowerOnAnnexC
164 1/1553-HSC901 003/2 Uen B

* unknown
The CPE presence can be detected without training the line. If the line is
configured for Annex B, only CPE modem of Annex B type can be
detected.
• Reliability: it specifies the reliability of the results. Possible values are :
* reliable
* modReliable
* notReliable
* newMeasReq
* unsupportedHw
* shortLineReliable
* cpeDetected
The test results will be always displayed also when the results are unreliable (for
example if the line is too long).
• Estimated Length (m): Estimated line length in meters between the IP
DSLAM and the subscriber termination point.
• Loop Attenuation @ 300kHz (dB): Estimated loop attenuation at
300kHz expressed in dB.
• Attenuation @ 300kHz (dB): it specifies the maximum
measurable/reliable attenuation at 300 KHz expressed in dB.
• Mean Upstream Noise Level (dBm/Hz): Average value of noise power
spectrum density in upstream direction.
• Mean Downstream Noise Level (dBm/Hz): Average value of noise
power spectrum density n downstream direction.
• ADSL deployment: Indicator intended as guidance for ADSL service
deployment. Indications: Possible, Uncertain or Not Possible. This result
is based on the estimated length and attenuation @ 300 KHz.
The following parameters are measured by the application.
The descriptions below describe the parameters of the test results, which can be
seen graphically or exported as raw data text files from AXH/EDA LCT (export
file and data collection tool):
• TDR: Time Domain Reflectometry (TDR) impulse diagram equivalent in
decibel. Each value is spaced 1/ (1024*4312.5) seconds in time. The
value spacing can be interpreted in a length unit equal to (x meter),
where x = 0.5*velocity of propagation*10000*1/ (1024*4312.5)
corresponding to one-way physical length fraction, that is, the physical
length from CO to customer/breakpoint. The "Velocity of propagation"
value can be specified from the folder "Tests" in the appropriate column.
Velocity of propagation is the speed at which an electric signal passes
through a cable.
• Echo Frequency Response: Magnitude (absolute value) of the Echo
Frequency Response of the line per sub carrier in decibel.
• Input Impedance: Estimated Input Impedance of the line including far-
end termination per sub carrier in Ohm.
1/1553-HSC901 003/2 Uen B 165

• Insertion Loss: Line Insertion Loss (attenuation) of the line per sub
carrier in decibel.
• Noise Ne: The measured near-end line noise per sub carrier in the
upstream band in unit dBm/Hz.
• Noise Fe: The estimated far-end line noise per sub carrier in the
downstream band in unit dBm/Hz.
• SNR Ne: Signal to Noise Ratio per sub carrier in the upstream band.
The SNR is calculated based on: maximum allowed transmit power,
insertion loss of the line and the line noise.
• SNR Fe: Signal to Noise Ratio per sub carrier in the downstream band.
The SNR is calculated based on: maximum allowed transmit power,
insertion loss of the line and the line noise.
• Bitloading NE: Estimation of the maximum attainable load of bits per
sub carrier in Upstream band. The Bit loading is calculated based on the
SNR with an assumed SNR margin of 6 dB.
• Bitloading FE: Estimation of the maximum attainable load of bits per
sub carrier in downstream band. The Bit loading is calculated based on
the SNR with an assumed SNR margin of 6 dB.
The SELT test range and reliability depend on the type of cable characteristics
such as attenuation, and line termination. In addition, any DSL CPE modem
connected to the line under test must be turned off (if test results other than CPE
Modem presence are desired).
WARNING After a SELT session the line will remain disabled.
The SELT Test Window is structured in two panels:

• Tests used to enter the input parameters.
• Basic Output Table that summarizes the results obtained (Reliability,
Estimated length, Loop Attenuation @ 300 KHz, Attenuation @300 KHz,
166 1/1553-HSC901 003/2 Uen B

Downstream Capacity, Upstream Capacity, Mean Downstream noise

level, Mean Upstream noise level, ADSL deployment, CPE presence)
To activate a new test

1. Select Tests folder.
2. Select a row.
3. Double click right mouse button, to edit.
4. Select Ne from a menu list (or LogicalName if you prefers).
5. Subrack from a menu list.
6. Slot from a menu list.
7. Port from a menu list.
Card field is automatically filled when you specify Subrack and Slot fields.
8. Specify CMD field from menu list. Possible values are:
• start: to run a SELT Test session.
• check test result: to check test result after a previous test started.
If you set “start” in the “CMD” field the following additional input parameters must
be selected:
• Splitter Type: it specifies the external splitter filter type. This parameter
is used to inform the SELT software about any installed external splitter
filter. SELT performance is affected by this parameter. Possible values
are noneOrPOTS, edf110i, kroneIsdn, kronePots, pots02HAT00218AAW
• Velocity of propagation: It is the speed at which an electric signal
passes through a cable. It is expressed in unit of 10 km/s. The default
value is 19000.
• Tone Profile: Transmission mode identification for the intended DSL
connection splitter filter. The SELT performance is affected by this
parameter. Possible values are ANSI T1.413, ETSI TS 101 388, ITU-T
ADSL Not Overlapped, G992.1 Annex A, ITU-T ADSL over ISDN,
G992.1 Annex B, ITU-T ADSL Lite over POTS, G992.2 Annex A, ITU-T
ADSL2 over POTS, G992.3 Annex A, ITU-T ADSL2 over ISDN, G992.3
Annex B, ITU-T ADSL2, G992.3 Annex M, ITU-T RE-ADSL2 over POTS,
G992.3 Annex A, ITU-T RE-Narrow PSD ADSL2 over POTS
G.992.3,ITU-T ADSL2+ over POTS, G992.5 Annex A,ITU-T ADSL2+
over ISDN, G.992.5 Annex B, ITU-T ADSL2+, G992.5 Annex M, ITU-T
VDSL2, G993.2
So you can apply (Apply button) or stop (Abort button) your compiled line (all
selected line will be applied too).
How to see a graph

In order to display the graph for each array value the user must execute the
following steps:
1. Select the folder (Echo Frequency Response, Insertion Loss, Noise FE/NE,
SNR FE/NE, Bit Loading FE/NE, TDR, and Input Impedance).
2. Select the row;
3. By double click on the right mouse button, select the command Graph Tests.
1/1553-HSC901 003/2 Uen B 167

A new window will be displayed with the graph. It is possible to save the graph
to a file. In order to execute this operation the user must execute the following
steps:
1. To select the folder (Echo Frequency Response, Insertion Loss, Noise FE/NE,
SNR FE/NE, Bit Loading FE/NE, TDR, Input Impedance)
2. Select the row;
3. Double Click right mouse button;
4. To select the command Export Tests To Graph.
5. Select the Yes button when the following question is displayed Export Tests to
file in graph format?
6. Fill the File Name field (for default the file is stored in
<installDir>\data\Graph\EdaSelt directory).
7. Click on Save button.
2.4.25 IP / Ethernet Statistics

PATH: (Configuration -> IP/ Ethernet Statistics Counters)
This tool is used to have statistic about the applications of the Equipment. In
particular, several kinds of reports about RSTP, Ethernet, VoIP, ICMP (Internet
Control Message Protocol), IGMP are shown.
This application is read only and the tables are filled by pressing either Read
Network - Active Page or Read Network – All Pages.
This application is structured in several folders in order to collect different

counter types:
• RSTP Bridge Stats
• RSTP Port Stats
• Ethe MAC Stats
• IP Stats
168 1/1553-HSC901 003/2 Uen B

• ICMP Stats
• ICMP MSG Stats
• VOIP Stats
• MSTP Bridge Stats
• MSTP Instance Stats
• MSTP Port Stats
• MCAST IGMP Instance Stats
• MCAST IGMP Port stats
• MCAST Content Stats
• DHCP L3 Counters
RSTP – Bridge Stats
This window reports the following information:
• Conf BPDUs Transmitted
• Conf BPDUs Received
• Conf TCN BPDUs Transmitted
• Conf TCN BPDUs Received
• Expired BPDUs
• Topology Change Num
• Last Topology Change Time [centisec]
• Tot Topology Change Num
RSTP – Port Stats
• Expired BPDUs
• Last Topology Change Time
• Ongoing Topology Change Num
Ethe MAC Stats
• NE
• Logical Name
• Record Time
• Interface Name
• Incoming Octets
• Incoming Frames
• Incoming Discarded Frames
• Incoming Errored Packets
• Outgoing Octets
1/1553-HSC901 003/2 Uen B 169

• Outgoing Frames
• Outgoing Discarded Frames
• Outgoing Errored Packets
• Incoming Multicast Packets
• Incoming Broadcast Packets
• Outgoing Multicast Packets
• Outgoing Broadcast Packets
IP Stats
• NE
• Logical Name
• Record Time
• IP Version
• Total Incoming IP Datagrams
• Discard Incoming IP Datagrams
• Discarded Incoming IP Datagrams (Unknown Protocol)
• To be Forwarded Incoming IP Datagrams
• Incoming IP Fragments
• Reassembled IP Fragments
• NotReassembled IP Fragments
• Discarded Incoming IP Datagrams (Invalid Address)
• Discarded Incoming IP Datagrams
• Successfully Delivered Incoming IP Datagrams
• Outgoing Request IP Datagrams
• Discarded Outgoing IP Datagrams
• Successfully Delivered Outgoing IP Datagrams
• Failed Fragmented Outgoing IP Datagrams
• Outgoing Generated Datagram Fragments
ICMP Stats
• NE
• Logical Name
• Record Time
• IP Version
• Total Incoming ICMP Messages
• Discarded Incoming ICMP Messages
• Total Outgoing ICMP Messages
• Discarded Outgoing ICMP Messages
ICMP MSG Stats
170 1/1553-HSC901 003/2 Uen B

• NE
• Logical Name
• Record Time
• IP Version
• Type
• Incoming Per-Type ICMP Messages
• Outgoing Per-Type ICMP Messages
VOIP Stats
• NE
• Logical Name
• Record Time
• Virtual Gateway Id
• Successful Controller Commands
• Failed Controller Commands
• Successful Gateway Commands
• Failed Gateway Commands
• Retransmitted Commands
• Active Terminations Number
• Active Contexts Number
• Ephemeral Terminations Number
• Total Incoming SIP Request Messages
• Total Incoming SIP Response Messages
• Total Outgoing SIP Request Messages
• Total Outgoing SIP Response Messages
• Total Retransmitted SIP Request Messages
• Total Retransmitted SIP Response Messages
• IUADUA Layer 3 traffic messages from the Gateway to the MGC
• IUADUA Layer 3 traffic messages from the MGC to the Gateway
MSTP-Bridge Stats
This panel allows user to collect MSTP counters (bridge/group level) and reports
the following information:
• Topology Change BPDUs Transmitted
• Topology Change BPDUs Received
• Received Errored Packets
MSTP-Instance Stats
This panel allows user to collect MSTP counters (instance level) and reports the
following information:
1/1553-HSC901 003/2 Uen B 171


• Conf TCN BPDUs Transmitted
• Conf TCN BPDUs Received
• Expired BPDUs
MSTP-Ports Stats
This panel allows user to collect MSTP counters (port level) and reports the
• Forward Transitions Num
• Expired BPDUs
• Ongoing Topology Change Num
MCAST IGMP Instance Stats
This panel allows user to collect MCAST IGMP counters (instance level) and
reports the following information:
• Active Groups
• Joins To Router
• Joins From Host
• Successful Joins From Host
• Leaves Messages To Router
• Leaves Messages From Host
• Queries To Host
• Queries From Router
• Invalid Messages
MCAST IGMP Port Stats
This panel allows user to collect MCAST IGMP counters (port level) and reports
the following information:
• Leaves Messages
• Queries To Host
• Invalid Messages
• Joins
• Version2 Querier Timer [centisec]
MCAST Content Stats
This panel allows user to collect MCAST Content counters and reports the
• Active Hosts
172 1/1553-HSC901 003/2 Uen B

DHCP L3 Counters
• Upstream DHCP Discovery Packets(toward DHCP servers).
• Upstream DHCP Request Packets (toward DHCP servers).
• Received DHCP Packets encapsulated on Ethernet V2 frames.
• Received DHCP Packets encapsulated on Ethernet 802.3 frames.
• Received Unknown DHCP Packets.
• Received DHCP Discovery Packets.
• Received DHCP Offer Packets.
• Received DHCP Broadcast Request Packets.
• Received DHCP Ack Packets.
• Received DHCP Unicast Request Packets.
• Received DHCP Release Packets.
2.4.26 ADSL Statistics Counters

PATH: (Configuration -> ADSL Statistics Counters)
This tool is used to have statistic about the ADSL counters. In particular, several
kind of reports about ADSL LINE (ATU-C and ATU-R side) and ADSL TC
(Transmission Convergence) Stats (ATU-C and ATU-R side) are shown.
This application is read only and the tables are filled by pressing either Read
Network - Active Page or Read Network – All Pages, after the inserting of the
Slot and Port in the Network Search Criteria section.
This application is structured in several folders in order to collect different

counter types:
• ADSL Line ATUC Stats
1/1553-HSC901 003/2 Uen B 173

• ADSL Line ATUR Stats

• ADSL TC ATUC Stats
• ADSL TC ATUR Stats
• PVC Counters
It’s suggested to read the Alarm Description manual, for further information
about the alarms below reported (e.g. LOFS, LOSS, and LOLS).
ADSL LINE ATUC Stats:
This panel allows user to collect the following counters at line level:
• Loss of Frame Seconds (LOFS).
• Errored Seconds (ES). A cumulative count indicating the number of
seconds during which block errors have been detected.
• Full Inits.
• Failed Full Inits.
• Forward Error Correction seconds (FEC).
• Severely Errored Seconds (SES). A cumulative count indicating the
number of seconds of a performance data period during which the
preset threshold has been exceeded for a performance entity.
• Unavailable Seconds (UAS). A cumulative count indicating the
unavailability of the related entity. It means that the SUE threshold has
been exceeded.
ADSL LINE ATUR Stats:
This panel allows user to collect the following counters at line level:
• Loss of Frame Seconds (LOFS)
• Loss of Power Seconds (LPRS)
• Errored Seconds (ES)
• Forward Error Correction seconds (FEC)
• Severely Errored Seconds (SES)
• Unavailable Seconds (UAS)
ADSL TC ATUC Stats:
This panel allows user to collect the following counters at TC level:
• Corrected blocks
• Uncorrect blocks
• Total Cells In [24h]
• User Cells In [24h]
ADSL TC ATUR Stats:
This panel allows user to collect the following counters at TC level:
• Corrected blocks
• Uncorrect blocks
• Total Cells In [24h]
• User Cells In [24h]
PVC Counters:
This panel allows user to collect the following counters at PVC level:
174 1/1553-HSC901 003/2 Uen B

• Downstream Forwarded Unicast Frame

• Downstream Forwarded Unicast Bytes
• Downstream Forwarded Unicast Frame per Seconds
• Downstream Forwarded Unicast Bits per Seconds
• Upstream Received Unicast Frame
• Upstream Received Unicast Bytes
• Upstream Received Unicast Frame per Seconds
• Upstream Received Unicast Bits per Seconds
To start a collection:
• Insert the Slot and the Port to be monitored.
• Press Read Network - Active Page or Read Network – All Pages
according to the measurement.
You can also collect counters continuously using Read Mode panel:
1. Select Continuous checkbox.
2. Specify Polling Time [sec] (e.g. 10).
3. Select Scrolling checkbox to scroll automatically to the latest collected values.
To graph a collection
When you enable continuous collection, you can graph collected values
selecting a line and clicking Right mouse button -> Graph.
With Save/Load utility you can save and import old collected values and graph
them offline (clicking Right mouse button -> Graph Offline).
2.4.27 Performance Monitoring
PATH: (Configuration -> Performance Monitoring)

This item is used to start and show performance and raw data collections on
NE. Possible data collected are about performance counters:
ADSL Line - ATU-C Side - 15 minutes
Loss of Frame Seconds (adslAtucIntervalLofs)
Loss of Signal Seconds (adslAtucIntervalLoss)
Loss of Link Seconds (adslAtucIntervalLols)
Errored Seconds (adslAtucIntervalESs)
Full Inits (adslAtucIntervalInits)
Valid Data flag (adslAtucIntervalValidData)
Forward Error Correction seconds (adslAtucIntervalXEcs)
Fast Retrains (adslAtucIntervalFastR)
Failed Fast Retrains (adslAtucIntervalFailedFastR)
Severely Errored Seconds (adslAtucIntervalSesL)
Unavailable Seconds (adslAtucIntervalUasL)
ADSL Line - ATU-R Side - 15 minutes
Loss of Frame Seconds (adslAturIntervalLofs)
Loss of Signal Seconds (adslAturIntervalLoss)
1/1553-HSC901 003/2 Uen B 175

Loss of Power Seconds (adslAturIntervalLprs)

Errored Seconds (adslAturIntervalESs)
Valid Data flag (adslAturIntervalValidData)
Forward Error Correction seconds (adslAturIntervalXEcs)
Severely Errored Seconds (adslAturIntervalSesL)
Unavailable Seconds (adslAturIntervalUasL)
ADSL TC Level - ATU-C Side - 15 minutes
Rx Blocks (adslAtucChanIntervalReceivedBlks)
Tx Blocks (adslAtucChanIntervalTransmittedBlks)
Corrected blocks (adslAtucChanIntervalCorrectedBlks)
Uncorrect blocks (adslAtucChanIntervalUncorrectBlks)
Valid Data flag (adslAtucChanIntervalValidData)
Header Error Correction Violations (adslAtucChanIntervalXHecv)
Total Cells In (adslAtucChanIntervalXTotalCells)
Valid Cells In (adslAtucChanIntervalXTotalUserCells)
Idle Cells (adslAtucChanIntervalXIdleCells)
Idle Cell Bit Errors (adslAtucChanIntervalXIdleCellBitErrors)
Overflow Cells (adslAtucChanIntervalXOverFlowCells)
ADSL TC Level - ATU-R Side - 15 minutes
Rx Blocks (adslAturChanIntervalReceivedBlks)
Tx Blocks (adslAturChanIntervalTransmittedBlks)
Corrected blocks (adslAturChanIntervalCorrectedBlks)
Uncorrect blocks (adslAturChanIntervalUncorrectBlks)
Valid Data flag (adslAturChanIntervalValidData)
Header Error Correction Violations (adslAturChanIntervalXHecv)
Total Cells In (adslAturChanIntervalXTotalCells)
Total User Cells (adslAturChanIntervalXTotalUserCells)
Idle Cell Bit Errors (adslAturChanIntervalXIdleCellBitErrors)
VDSL Line - VTU-C Side - 15 minutes
PTM Coding Violations Non-Preemptive (vdslVtucChanIntervalXPtmCv)
PTM Coding Violations Preemptive (vdslVtucChanIntervalXPtmCvP)
ISDN Line - Near End - 15 minutes
Errored Seconds (marconiIsdnIntervalESs)
Severely Errored Seconds (marconiIsdnIntervalSESs)
Unavailable Seconds (marconiIsdnIntervalUASs)
Background Block Errors (marconiIsdnIntervalBBEs)
ISDN Line - Far End - 15 minutes
Errored Seconds (marconiIsdnFarEndIntervalESs)
Severely Errored Seconds (marconiIsdnFarEndIntervalSESs)
Unavailable Seconds (marconiIsdnFarEndIntervalUASs)
Background Block Errors (marconiIsdnFarEndIntervalBBEs)
176 1/1553-HSC901 003/2 Uen B

2.4.27.1 Running Performance Tool
This tool allows starting performance and raw data collection on the NE and
seeing the collected results. The tool is structured in two folders:
• Sink Jobs where you can specify collection parameters (a Job entry).
• Reports where you can see the collected results.
To compile a new Job entry it is necessary to click right mouse button and select
New Job item or select Edit menu and New Job item.
A new row is inserted in Job Table and compiles every cell double clicking on it.
Select the NE address from a menu list (or LogicalName).
Select Primary and Secondary Url where data collected (.gz files) are moved via
tftp protocol. Possible syntax is “tftp://xxx.yyy.hhh.zzz/PerfSink/” where
xxx.yyy.hhh.zzz= tftp server ip address.
1/1553-HSC901 003/2 Uen B 177

NOTICE TFTP Server must be in running. If you have any problems of transfer file
please check the following conditions:
- TFTP server is running;
- home directory of the TFTP Server is set correctly. You can verify in the
windows Tftpd32 that the field Current Directory is set as the field Base
Directory in the Tftpd32:Settings window;
- access's permissions (you can verify in the Tftpd32:Settings window that
the Read Only field us not checked.
If you modify the TFTP configuration in order to apply the new settings you
will have to close and to restart the TFTP protocol and this tool
Specify a Transfer Delay (in seconds from 0 to 600) to specify a minimal delay
before NE will send data via tftp (so it is useful to avoid network congestion
balancing tftp transfers). A special value Random (obtained specifying “” in
Transfer Delay field) is useful to choose a random value from 0 to 600.
Start the performance Job (start a collection and a transfer operation on NE) so
that every 15 minutes (plus the specified Transfer Delay ) a .gz file is sent by
NE to tftp server machine
NOTICE The performance collection can be started only if an NTP (Network Time
Protocol) server is active on the network. If such requirement is not fulfilled
the counters on the equipment cannot be started.
When the number of performance collections is enough stop the job. If needed
check the job status to see the current transfer state.
After a transfer operation is completed successfully it is possible to Load in the
Report tab the collected records contained in .gz file/files.
178 1/1553-HSC901 003/2 Uen B

It is possible to browse the collected records and save them in new file with
different format [.csv (ascii), .html, .perfo].
1/1553-HSC901 003/2 Uen B 179

With these new file format you can:

• Graph these collected record (loading from .csv format)
• Export To Performance DB (loading from .perfo format)
180 1/1553-HSC901 003/2 Uen B

2.4.27.2 Utilities
There are to available utilities to save, load and see precompiled Job lines
• Save Job Order
• Load Job Order
1/1553-HSC901 003/2 Uen B 181

2.4.28 Equipment Alarm Status

PATH: (Configuration -> Equipment Alarm Status)
This item is used to display the Status of the Equipment Alarms the Input and
the Output Ground Contact active Alarms.
The window has two sections:
182 1/1553-HSC901 003/2 Uen B

Equipment Alarm Status section shows the following type of alarms for each
Subrack:
• Subrack Connection: it indicates alarms in the connection among the
subracks.
• Power Supply: it indicates a fault in the power supply subrack.
• Temperature: The temperature has risen above normal operative range.
• Cooling Fans: There is a fault inside a least one cooling fan. Clicking on
the Details button for more information.
• CTS Timing: it indicates SCTS alarms in one of the Subracks. Click on
the Details to have a report of the alarms.
Active Input Contacts section shows the Input Ground Contacts (if this feature
is available). In order to display details about the Input Contact status click on
Details button.
2.4.29 Maintenance Menu

This paragraph describes the Maintenance item, selectable from the main
menu. The items available are:
• Equipment Reboot: this item permits to restart the equipment unit and
the controller unit in different modalities;
• Software Download: this item permits to manage the software
download;
• Check Connection to Equipment: this item permits to verify if a given
equipment's IP Address is ready for management;
• Subrack Hw Inventory: this item permits to resume the hardware
inventory information about the subrack.
2.4.30 Help Menu

This paragraph describes the Help item, selectable from the main menu.
This item of the main menu permits:

• To display the software version;
• To display the software guide.
1/1553-HSC901 003/2 Uen B 183

2.5 Graphical Area

This area displays a synoptic view of the equipment. The window shows a
Subrack composed by twenty-two slots, each correspond to a unit position. The
first and twenty-second slots are reserved for the Common Part unit (CP IP).
In this area the operator can activate a pop up menu by clicking on any slot. The
cursor is displayed with a hand, the "finger" icon indicates which mouse button
must be clicked to display the slot menu. The menu permits accessing the unit
configuration functions.
When a unit is configured, its name is displayed on the front panel while an
empty slot indicates a not equipped unit. When the unit inserted is different from
the one configured, the front panel is drawn outside the Sub Rack.
The unit border of an empty slot is displayed in grey color. When the unit
inserted is different from one configured, the unit border is displayed in red color.
On the top of the area there is a string, which identifies the Sub Rack and on the
top of each slot there is a LED, indicating the alarm status:
• Red: One or more alarms are detected inside the unit (or the color
specified in Application General Configuration/LED Colors window);
• Green: There are no alarms (or the color that it has been specified in the
Application General Configuration/LED Colors window);
• Grey: The slot is empty.
Under each slot is indicated the relevant position number. There are three
different colors of background field:
• Grey: when the relevant unit is not involved in any active protection scheme;
• Red: when the relevant unit is involved in an Automatic Protection switch;
• Blue: when the relevant unit is involved in a Manual Protection switch.
184 1/1553-HSC901 003/2 Uen B

2.5.1 Unit Creation

The equipment has an auto sense facility and will automatically recognize when
a new unit is plugged inside the Subrack. The AXH-EDA Local Terminal will
show the new situation in the graphical area.
Even not necessary to create a new unit, follow this procedure:
1. Select the empty slot where the unit will be inserted.
2. From the floating menu, select Create to display the choice list.
3. Select the unit type, by clicking on the relevant item in the scroll list.
emptySlot
displays a reserved slot;
cp-2530-4xGbEth
Common Part Card with on board up to 4 Gigabit Ethernet interfaces;
cp-2530-4xGbEth-NTP
Common Part Card with on board up to 4 Gigabit Ethernet interfaces
and NTP Synchronization feature;
adslx64-NP
ADSL card with 64 lines over POTS (Not Protectable);
adsl-isdnx64-NP
ADSL card with 64 lines over ISDN (Not Protectable);
vdslx32-NP
VDSL card with 32 lines (Not Protectable);
shdslx32-MultiServices
SHDSL card with 32 lines;
potsx60-NP
POTS card with 60 lines (Not Protectable);
potsx64-NP
POTS card with 64 lines (Not Protectable);
1/1553-HSC901 003/2 Uen B 185

isdnx32-SIP-4B3T-NP
32xISDN (4B3T line code) for VoIP SIP unit (Not Protectable);
isdnx32-SIP-2B1Q-NP (not used)
32xISDN (2B1Q line code) for VoIP SIP unit (Not Protectable);
Pressing an alphabetical key, a "Quick Search" popup window is displayed,
which allows to enter a pattern-matching string to help searching the wished unit
name in the list.
NOTICE For the unit code number, see the chapter "Composition" of the System
Description handbook.
According to the configured units and to the allowed equipment
configurations, some selections for the selected position are not allowed and
error messages will be notified.
4. Click over the OK button to confirm the operation.

If the unit is not present inside the Subrack, a message window will report the
slot error status.
2.5.2 Unit Deletion

This item is used to delete a unit. It is available for each type of unit, except for
the Matrix unit inserted in the first slot.
Proceed as follows:
1. Move the cursor over the slot corresponding to the unit to be removed and
display the floating menu by a right click of the mouse.
2. Select the Delete item to display the confirmation window.
3. Click the YES button to confirm, or click the NO button if you refuse the
operation.
NOTICE A warning window will show up if the unit to be deleted is involved in a cross-
connection or there are active lines present. In this case the delete
command will be refused.
186 1/1553-HSC901 003/2 Uen B

2.6 Unit Configuration

2.6.1 General
This function involves the peculiar settings of each unit, and it is managed using
different methods for the different types of unit.
The following paragraphs will describe the menu that appears when the right
button of the mouse is clicked above the graphical representation of each unit.
In this chapter, each unit is described separately.
2.6.1.1 About
The About item shows a window text that contains a brief description about the
interfaces lodged on board of the equipment.
2.6.1.2 Show Actual
This item shows a text window, indicating the type of unit inserted, its alarm
status and the alarm severity associated to the slot.
1/1553-HSC901 003/2 Uen B 187

2.6.1.3 Hw/Sw Inventory
This item displays the hardware and software information about the unit.
Through this window, the operator can check the active memory bank, the
software and the hardware release of each unit.
There are two sections inside the window, the Software and the Hardware
Inventory.
The Software Inventory window provides information about:
• Boot memory;
• Bank1 memory;
• Bank2 memory;
• Monitor.
The fields above are described with the following labels:
Code, this label shows the Software Code;
Release, this label shows the Software Release;
Date, the label shows the update date;
Valid, this label shows the downloaded software status:
Yes: The downloaded software does not have any problem;
No: equipment detected some problem in the software downloaded.
Running, this label shows the software running status:
Yes: The equipment software is running;
No: The equipment software is not active.
The Hardware Inventory window provides information about the Base Board
with the following fields:
Card Type, this field shows the code number of the unit;
Serial, this field shows the Factory Unit Serial Number;
Use the Refresh button to update and Close button to exit the window.
2.6.1.4 Refresh
This item updates the information relevant to the selected slot.
2.6.1.5 Delete
This item permits to delete the unit from the selected slot.
188 1/1553-HSC901 003/2 Uen B

2.6.1.6 Reset Board
This item permits to perform the software and hardware reset or reset to factory
default of the unit.
Reset to Factory Default choice is available for all units except the Common
Part Unit.
How to reset a unit

1. Click the Software Reset radio button or the Hardware Reset radio button to
enable the software unit reset or the hardware unit reset.
2. Click over Reset Board to confirm the choice.
DANGER ! The unit reset procedure could cause the traffic interruption. A warning
window will ask to confirm the operation.
2.6.2 CP-IP Unit

In the following will be described the CP-IP entries.
2.6.2.1 SFP Provisioning
This window allows to display/to configure the SFP module on a CP-IP card.
The SFP (Small Form factor Pluggable transceivers) technology essentially
allows to choose the characteristics of the transceiver of a port of a card already
in service (“hot-pluggability”), by simply inserting (or removing) the SFP
transceiver directly from the front panel of the housing motherboard, then
optimizing card application flexibility and CAPEX cost. The SFP types basically
fall in two categories:
• SFP able to provide the hosting card processor with useful information
about its inventory data, contained in an EEPROM; usually such devices
are named SFP without digital monitoring interface;
• SFP able to provide the hosting card processor with both useful
information about its inventory data (such information are contained in
an EEPROM) and digital monitoring functions; usually such devices are
named SFP with digital monitoring interface; the digital monitoring
functions are the capability to provide the following real time measures:
- Internal SFP temperature;
- SFP Supply Voltage;
- SFP Bias Current;
1/1553-HSC901 003/2 Uen B 189

- Transmitted optical power;

- Received optical power.
To be noted that for SFP, equipment performs auto configuration. When a SFP
is inserted in a not yet configured SFP slot,equipment automatically configures
the characteristics of the relevant SFP according to the inserted SFP type. One
SFP may be inserted/configured on each Gigabit Ethernet physical port.
The "CP-IP SFP/Port Provisioning" window displays a table in which is possible

to find the configuration of the CP-IP board. The following information is present:
• Module ID column displays the HW module type on which are connected
the ports. The first module, cp, does not contain physical ports.
• Port column specifies physical port i.e. subrack/slot /module/port information.
• Provisioning Status column displays configuration status of the port. It
can be provisioned/unprovisioned. If it is 'unprovisioned' it is unusable.
• SFP tag column displays the tag type of SFP that it has been configured
in the Configure SFP window (in the "Configured" column) and the type
of SFP currently installed in the slot (in the "Actual" column).
The possible cases of SFP tag types are:
• SFPs of type approved by Marconi (containing the ‘MONI’ tag in the
EEPROM) and able to perform digital monitoring functions;
• SFPs of type approved by Marconi (containing the ‘MONI’ tag in the
EEPROM) but not able to perform digital monitoring functions;
• SFPs of type not approved by Marconi (then they are not ‘MONI’
tagged).
WARNING The pluggable optical module approved by Ericsson for use with Ericsson
equipment have been certified and labeled appropriately by their respective
manufacturers then verified for use in Ericsson products. The use of any
pluggable optical module not approved by Ericsson invalidates the
compliance certification of this equipment, including, but not limiting to,
safety, EMC and functional performances characteristics. If this is done
Ericsson accepts no liability or responsibility for such action, and the person
or organization performing such action is deemed to have accepted full
responsibility for the system.
• SFP Frame type column displays the type of SDH or Ethernet frame that
it has been configured in the "Configure SFP" window (in the
190 1/1553-HSC901 003/2 Uen B

"Configured" column) and the type of SDH or Ethernet frame actually

provisioned on the SFP.
• SFP medium type column displays the characteristics of the
transmission medium that is has been configured in the "Configure SFP"
window (in the "configured" column) and the transmission medium
actually provisioned on the SFP ("Actual" column).
• Wave Length: this field indicates the operating wavelength supported by
the SFP actually provisioned into the relevant SFP slot.
• Y-Coupler connected displays "true" if the SFP is connected towards the
Y-coupler and this SFP is coupled with the peer-SFP of the peer card, or
it will display false if this SFP is not connected towards a Y-coupler.
• In the SFP Alarm Status is displayed the possible alarm condition.
How to modify a SFP configuration:

1. Select a physical port.
2. Click on the "View Details/Modify selected SFP configuration" button.
The Configure SFP window will be displayed:
The window is divided in 2 sections. In the upper section you can modify the
configuration of the "SFP module" for the selected port.
3. Set "the SFP MONI-tagged required" parameter (false => a not MONI tagged
SFP is allowed to be provisioned in the relevant SFP slot; true => only "MONI'
tagged SFP are allowed to be used).
4. Set the "SFP Frame Type" parameter that specifies the frame type (SDH or
Ethernet) with the SFP will be provisioned (stm1, stm4, stm16, eth10, eth100,
eth1000).
1/1553-HSC901 003/2 Uen B 191

5. Set the "SFP Medium Type" parameter that specifies the characteristics of the
transmission medium with the SFP will be provisioned (electrical, dualFibre,
undefined).
6. Set the "SFP Laser Wave Length" parameter that specifies the wavelength of
the SFP expected to be provisioned into the relevant SFP slot.
7. Set the "SFP connected to Y-Coupler" parameter that specifies if the SFP is
connected towards the Y-coupler (true), or if this SFP is not connected towards
a Y-coupler (false).
8. Click on the Apply button.
How to see the details of a SFP configuration:

1. Select a physical port.
2. Click on the View Details/Modify selected SFP configuration button.
The "Configure SFP" window will be displayed:
The "Configure SFP" window is divided in 2 sections. In the "Current SFP
status" section you can see the actual configuration of the "SFP module" for the
selected port.
In this section the following information are displayed:
• Actual Tag Type specifies the tag type of the SPF. Possible values are:
- unequipped => the SFP has not been actually equipped yet,
consequently, all the other information takes a not significant value.
- moniNotTagged => the equipped SFP is not of type approved by
Marconi.
- moniTagged => the provisioned SFP contains the 'MONI' tag.
• Marconi Saleable Entity Code specifies the Marconi Saleable Entity
code the SFP actually provisioned into the relevant SFP slot. When the
SFP is not yet actually provisioned or the SFP is of type not approved by
Marconi, a null string will be displayed.
• Supported SDH Frame states the SDH frame supported by the SFP
actually provisioned (STM-1; STM-4; STM-16).
• Supported SDH Application states the SDH Application supported by the
SFP actually provisioned.
• Supported Data Frame Type. It states the Ethernet frames types
supported by the SFP actually provisioned (Ethernet 10 Mbit/s; Ethernet
100 Mbits; Ethernet 1 Gbits/s).
• Supported Data Application. It states the data application supported by
the SFP actually provisioned.
• Medium Type. It states the characteristics of transmission medium
supported by SFP actually provisioned (electrical; dualFibre; singleFibre).
The value "undefined" means either SFP not yet actually provisioned or not
applicable, which is an SFP of type not approved by Marconi.
• Operating Wavelength. It states the operating wavelength supported by
the SFP actually provisioned
• Alarm Status: possible alarm conditions.
192 1/1553-HSC901 003/2 Uen B

• Internal Temperature (Celsius), internally measured transceiver

temperature in degrees Celsius.
• Supply Voltage (volts), internally measured transceiver supply voltage in
Volts.
• Tx Bias Current (mAmp), measured transmitter bias current in mA.
• Tx Optical Power (mWatt), measured output power in mWatt. Data is not
valid when the transmitter is disabled.
• Rx Optical Power (mWatt) received optical power measured in mWatt.
• Out of Range Measures: possible alarm conditions.
3. Click on the Refresh button in order to update the window.
4. Click on the Close button in order to exit.
2.6.2.2 CP-IP On Board Element Manager
This feature allows connecting the Equipment to On Board Element Manager.
How to access to On Board Element Manager:

1. Select On Board Element Manager item to display the HTTP Browser window
as displayed in the picture below:
2. Click on Login button to confirm the action. The following picture will be
displayed.
1/1553-HSC901 003/2 Uen B 193

2.6.2.3 Ethernet Lines
This item allows configuring the Giga Ethernet lines.
Proceed as follows:
1. In the graphical area, select the CP IP unit slot and click over it with the right
button to display the floating menu.
2. Select the Ethernet Lines item.
3. Select Configure button, to display all the line parameters. It displays the
Configuration folder page where the Line parameters can be configured.
4. In the Line Identifier field is possible to insert an alphanumeric string (ASCII

characters) to identify the line.
5. Use the Refresh button to update the field.
6. Use the Apply button to confirm the action.
7. Check the Local In-Band Mng field in order to enable this line to be used as local
in band management.
8. The Bridge Port field is used to read the port associated to the bridge if this is a
L2 bridged interface. If the value is 0, a bridge port isn't associated with this
bridged L2 interface.
9. By means of the MTU Size (bytes) field, it is possible to display the largest
packet which can be sent/received on this interface.
10. Promiscuous Mode parameter is set to the value false if this interface only
accepts packet/frames that are addressed to this station, while it displays the
value true when the station accepts all packet/frames transmitted on the media.
194 1/1553-HSC901 003/2 Uen B

11. By means of Accept. Frame field is possible to display if the untagged or

Priority Tagged frames received on this port, are discarded or not. Only value
accepted AdmitAll.
12. Insert the Num Traff Classes, the number of egress traffic classes supported
on this port.
13. Ingress Filter scroll list. When this parameter is set to true the device will
discard incoming frames for VLAN which do not include this port in its member
set; when it is set to false the port will accept all incoming frames scroll list is
possible to discard or not the untagged incoming frames. False option is not
supported.
14. Insert the P-VID, the VLAN ID assigned to untagged frames or Priority –Tagged
received on this port.
15. Set the priority by means of Def User Priority spinner. This parameter is the
default ingress User priority for this port. This only has effect on media, such as
Ethernet, that do not support native User Priority.
16. Pause Admin Mode: This parameter is used to configure the default
administrative PAUSE mode for this interface.
17. Pause Oper Mode: This parameter reflects the PAUSE mode currently in use
on this interface, as determined by either (1) result of auto-negotiation function
or (2) if auto-negotiation is not enabled or is not implemented for the active MAU
attached to this interface, by the value of parameter "Pause Admin Mode".
18. In Pause Frames: A count of MAC Control frames received on this interface
with an opcode indicating the PAUSE operation. This counter does not
increment when the interface is operating in half-duplex mode. Discontinuities in
the value of this counter can occur at re-initialization of the management system.
19. Out Pause Frames: A count of MAC Control frames transmitted on this
interface with an opcode indicating the PAUSE operation. This counter does not
increment when the interface is operating in half-duplex mode. Discontinuities in
the value of this counter can occur at re-initialization of the management system.
20. Press Apply button to confirm or Refresh to update the window.
CP-IP Ethernet Lines Status
This item allows to display and to manage the state of Ethernet lines.
1. Select the Status folder, to display lines status window.
1/1553-HSC901 003/2 Uen B 195

2. In Line Oper Status field it is possible to see the status of the line.
3. Y-Coupler field indicates if the SFP is connected towards the Y Coupler (true)
or not (false).
4. Physical Address field displays the interface’s address (e.g. MAC address).
5. Speed (bit/s) field displays the interface’s current bandwidth.
6. Connector present field specifies if there is the presence of a connector or not.
7. Link Aggregator field shows if the Ethernet line belongs to a Link Aggregator
and its Admin Key
8. Press Refresh to update the window.
Ethernet MAU Parameters
This item allows displaying the CP-IP Ethernet MAU parameters.
1. The MAU folder displays the status of MAU parameters. This folder is divided in
two different sections: MAU Status (it displays the status of the MAU
parameters) and MAU Auto Negotiation (it is used to set the auto negotiation
parameters)
196 1/1553-HSC901 003/2 Uen B

2. In the MAU Default Type field the default administrative baseband of the
interface is displayed.
3. In the MAU Type field the type of the interface is displayed.
4. In the MAU Media Available field the media available (fiber type, coax etc...) is
displayed.
5. By means of the relevant scroll list, in the MAU Status, is possible to configure
the current status of the MAU, among these possible values: Operational,
Standby, Shutdown, Reset.
6. In the MAU Jabber State the proper value for the Jabber State is displayed.
Possible values are: Unknown, NoJabber, Jabbering, Other.
7. MAU Auto Neg Supp field indicates whether or not auto-negotiation is
supported on this MAU.
The following parameters can be set in the MAU Auto Negotiation section.
8. Set in the Admin Status scroll list, if the auto negotiation is enabled or not.
9. Set in the Restart scroll list, the possibility to force auto negotiation to begin link
renegotiation (restart).
10. By means of the Config it is possible to read the status of auto negotiation process.
11. In the Capability Bits it is possible to read the set of capabilities of the local
auto negotiation.
12. In the Cap. Advertised Bits it is possible to identify the set of capabilities
advertised by the local auto negotiation.
13. By pressing of Details button, it is possible to change the bits association
between Advertised Capability Bits corresponding to check Cap Bits. In order to
perform the changes, check your choice press OK in this window and then
Apply in the MAU folder (Ethernet lines).
1/1553-HSC901 003/2 Uen B 197

14. Remote Fault Advertised is a value that identifies any local fault indications
that this MAU has detected and will advertise at the next auto-negotiation
interaction.
15. In the Remote Fault Received it is possible to read any fault indication received
from a far end of a link by the local auto negotiation.
16. Press Refresh to update the window, press Apply to set a new auto
negotiation.
198 1/1553-HSC901 003/2 Uen B

Ethernet Statistics Parameters

1. Select the Statistics folder, to display a window showing the current values of
statistical counters.
2. In the Incoming Octets field, the total number of the octets received on the
interface is displayed.
3. In the Incoming Frames field, the number of the packets delivered from a sub
layer to a higher one including frames characters is displayed.
4. In the Incoming Discarded Frames, the number of inbound packets which
were chosen to be discarded even through no errors had been detected to
prevent their being deliverable to a higher layer protocol. One possible reason
for discarding such a packet could be free up buffer space.
5. In the Incoming Errored Frames, the number of inbound packets that
contained errors preventing them from being deliverable to a higher protocol.
6. In the Incoming Multicast Pkts field, the number of the packets delivered from
a sub layer to a higher one (for multicast packets) is displayed.
7. In the Incoming Broadcast Pkts field, the number of the packets delivered
from a sub layer to a higher one (for broadcast packets) is displayed
8. In the Outgoing Octets field, the total number of the octets transmitted out of
the interface is displayed.
9. In the Outgoing Frames field, the number of packets requested to be
transmitted is displayed.
1/1553-HSC901 003/2 Uen B 199

10. In the Outcoming Discarded Frames, the number of outbound packets which
were chosen to be discarded even through no errors had been detected to
prevent their being transmitted. One possible reason for discarding such a
packet could be free up buffer space.
11. In the Outcoming Errored Frames, the number of outbound packets that could
not been transmitted because of errors.
12. In the Outgoing Multicast Pkts field, the number of packets requested to be
transmitted. (for multicast packets) is displayed
13. In the Outgoing Broadcast Pkts field, the number of packets requested to be
transmitted. (for broadcast packets) is displayed.
14. Press Refresh to update the window.
Priority Traffic Class
1. Select the Priority Traffic Class folder.
2. Assign, for each priority assigned, a type for a Traffic Class, choosing among
the values stored in the relevant spinners.
200 1/1553-HSC901 003/2 Uen B

2.6.2.4 Frontal Ethernet Line
This item allows configuring the Frontal Ethernet lines over the CP card.
Proceed as follows:
2. Select the Frontal Ethernet Line item.
3. Select the Configure button, to display all the line parameters. The program
displays the Configuration / Status folder page where the following parameters
can be configured:
4. In the Line Identifier field is possible to insert an alphanumeric string (ASCII

characters) to identify the line.
5. Use the Refresh button to update the field.
6. Use the Apply button to confirm the action.
7. Line Admin Status and Line Oper Status fields show the status of the line.
8. By means of the MTU Size (bytes) field, it is possible to display the largest
packet which can be sent/received on this interface.
9. The field Physical Address displays interface’s address (e.g. MAC address).
10. The field Connector present specifies if there is the presence of a connector or not.
11. In Line Oper Status field, the Operator is able to see the current operational
status of the interface (the value will be up or down).
12. Promiscuous Mode parameter displays the value false if this interface only
accepts packet/frames that are addressed to this station, while it displays the
value true when the station accepts all packet/frames transmitted on the media.
13. Speed (bit/s) field displays the interface’s current bandwidth.
1/1553-HSC901 003/2 Uen B 201


MAU folder
1. Press MAU folder in order to display the following parameters configured:
2. In the MAU Admin Status is possible to set the current status of the MAU
3. In the MAU Type field the type of the interface is displayed.
4. In the MAU Media Available field the media available (fiber type, coax etc.) is
displayed.
5. MAU Auto Neg Supp field indicates whether or not auto-negotiation is
supported on this MAU.
6. In the MAU Jabber State the proper value for the Jabber State is displayed.
Possible values are: Unknown, NoJabber, Jabbering, Other.
The following parameters can be displayed in the MAU Auto Negotiation
section.
7. In the Default Type field is possible to set the default administrative baseband
of the interface.
8. Set in the Admin Status scroll list, if the auto negotiation is enabled or not.
9. In the Capability Bits it is possible to read the set of capabilities of the local
auto negotiation.
10. In the Cap. Advertised Bits it is possible to identify the set of capabilities
advertised by the local auto negotiation.
11. Set in the Restart scroll list, the possibility to force auto negotiation to begin link
renegotiation (restart).
12. By means of the Config it is possible to read the status of the auto negotiation
process.
13. Remote Fault Advertised is a value that identifies any local fault indications
that this MAU has detected and will advertise at the next auto-negotiation
interaction.
202 1/1553-HSC901 003/2 Uen B

14. In the Remote Fault Received it is possible to read any fault indication received
from a far end of a link by the local auto negotiation.
15. Press Refresh to update the window, press Apply to set a new auto
negotiation.
2.6.2.5 Link Aggregator Lines
This tool allows managing the parameters of L2 layers of a Link Aggregator

Group (LAG). The configuration is executed by the application Ethernet Link
Aggregation (Configuration -> IP/Ethernet Management -> Ethernet Link
Aggregation). Refer to the relevant paragraph for further information.
Proceed as follows:
2. Select the Link Aggregator Lines item.
3. Select the Configure button, to display all the line parameters. The program
displays the Configuration folder page where the Line parameters can be
configured.
4. Set the Line identifier (if desired). In the Line Identifier field is possible to insert
an alphanumeric string (ASCII characters) to identify the line. Use the Refresh
button to update the field and Apply button to confirm the action.
5. The Admin Key parameter is the current administrative value of the key for the
Aggregator.
6. By means of Accept. Frame field is possible to display if the untagged or
Priority Tagged frames received on this port, are discarded or not. Only value
accepted is AdmitAll.
7. Ingress Filter scroll list. When this parameter is set to "true" the device will
discard incoming frames for VLAN which do not include this port in its member
set; when it is set to "false" the port will accept all incoming frames scroll list is
possible to discard or not the untagged incoming frames. False option is not
supported.
1/1553-HSC901 003/2 Uen B 203

8. Insert the Num Traff Classes, the number of egress traffic classes supported
on this port.
9. The Bridge Port field is used to read the port associated to the bridge if this is a
L2 bridged interface. If the value is 0, a bridge port isn't associated with this
bridged L2 interface.
10. Insert the PVID, the VLAN ID assigned to untagged frames or Priority –Tagged
received on this port.
11. Set the priority by means of Def User Priority spinner. This parameter is the
default ingress User priority for this port. This only has effect on media, such as
Ethernet, that do not support native User Priority.
12. Ports in LAG shows the interface name of Ethernet ports inserted in this Link
Aggregation Group (LAG)). If the list is empty it means that no Ethernet ports
are assigned to this group
13. Press Apply button to confirm or Refresh to update the window.
Priority Traffic Class (LAG)
This window allows mapping, for the selected line, a Traffic Class Priority to a
Traffic Class.
1. Select Priority Traffic Class folder.
2. Assign, for each priority assigned, a type for a Traffic Class, choosing among
the values stored in the relevant spinners.
204 1/1553-HSC901 003/2 Uen B

2.6.3 ADSL Unit Configuration

In the following paragraphs the Lines items will be described.
Proceed as follows
1. Select the slot of the 64xADSL unit to be configured and click over it using the
right mouse button, to display the floating menu.
2. Select the Lines item, to display the 64xADSL configuration window.
An icon represents each traffic line, displaying the actual operating status as
follows:
- Grey, indicates that the line is not configured;
- Yellow, indicates that the line is configured, but the line's status is not active
because the carrier is missing;
- Green, indicates that the line is configured and the line's status is active. The
carrier is present.
3. Press Refresh All Lines button to update the operating status of the lines.
ADSL Lines Configuration
This item allows configuring the ADSL lines of the 64xADSL Unit.
1. Select the icon of the line (from 1 to 64) to be configured.
2. Select the Configure button to display all the line parameters. It is also possible
to select or deselect multiple lines by pressing SHIFT and CONTROL (read the
procedure below). Multiple lines selection is relevant only for the
Configuration folder, and may be used to apply an identical configuration to
a set of ADSL lines.
How to select a range of consecutive lines

1. Select the first line of the range.
2. Select the last line of the range while holding down the SHIFT key.
How to select a range of not consecutive lines

1. Select each line to be configured, while holding down the CTRL key.
1/1553-HSC901 003/2 Uen B 205

How to configure the ADSL parameters

1. Inside the Subscriber Identifier field, it is possible to insert an alphanumeric
(ASCII characters) string to identify the subscriber to which the line is assigned.
2. The Line Configuration Profile scroll list is used to show, set and modify the
value of this field identifies the row in the ADSL Line Configuration Profile Table
(Configuration -> xDSL Profile -> xDSL Line Profile) which applies for this ADSL
line, and channels if applicable.
3. Use the clockwise arrow icon to update the list of ADSL Configuration Profile.
4. By pushing View/Change Configuration Profile it is possible to gain access to
the xDSL Line profile Management window.
5. The Alarm Profile scroll list is used to identify the row in the ADSL Line Alarm
Configuration Profile Table, which applies to this ADSL line, and channels if
applicable.
6. Use the clockwise arrow icon to update the list of ADSL Alarm Profile.
7. By pushing View/Change Alarm Profile it is possible to gain access to the
xDSL Alarm Profiles Management window.
8. PSD Profile scroll list is used to show, set and modify the PSD Spectrum
profiles configured for the selected line(s).
9. By pushing View/Change PSD Spectrum Profile it is possible to gain access
to ADSL PSD Profiles Management window.
10. By means of the LinkUp/LinkDown Trap radio button, is possible to
enable/disable the generation of these traps on this interface.
11. In the Transmission Mode Type section, is possible to choose the actual
transmission mode with which the line will be activated.
12. Select Refresh to read current line configuration, Apply to confirm the choices.
206 1/1553-HSC901 003/2 Uen B

64xADSL Lines Status

This item allows to display and to manage the state of ADSL lines.
2. Use the Enable or the Disable button, to enable or disable the ADSL link. If the
start-up procedure will be successfully completed, the Carrier on message will
be displayed; conversely the Carrier off indication will not change.
CAUTION The Enable and Disable button's status depends on the line status.
In the Line Status Section the following information can be detected:

Note If the value cannot be detected the label "unknown" or "Not Available" will be
displayed.
Actual Transmission Mode
The actual transmission mode of the ATU-C. During ADSL line
initialization, the ADSL ATU-R will determine the mode used for this
link.
Actual Line State
ADSL line state.
(ATU-C) Alarms
The current state of the local ADSL interface by clicking over Details
button, the alarm details will be displayed.
(ATU-R) Alarms
The current state of the remote ADSL interface by clicking over Details
1/1553-HSC901 003/2 Uen B 207

In the Downstream and Upstream direction, the following information can be

detected:
(ATU-C) Actual Channel Rate (kbps
This parameter displays the actual bit rate [kbit/s] of the Downstream
path over the line.
(ATU-R) Actual Channel Rate (kbps
This parameter displays the actual bit rate [kbit/s] of the Upstream path
over the line.
(ATU-C) Previous Channel Rate (kbps
This parameter displays the bit rate [kbit/s] of the Downstream path
over the line. Previous transmit rate on this channel, i.e. the transmit
rate before the last activation of the line.
(ATU-R) Previous Channel Rate (kbps
This parameter displays the bit rate [kbit/s] of the Upstream path over
the line. Previous transmit rate on this channel, i.e. the transmit rate
before the last activation of the line.
(ATU-C) Attainable Rate (kbps
This parameter indicates the maximum transmit net data rate currently
attainable for the Downstream path.
(ATU-R) Attainable Rate (kbps)
attainable for the Upstream path.
(ATU-C) Interleav. Delay (msec)
This parameter displays the value of the buffer-delay over the
Downstream path.
(ATU-R) Interleav. Delay (msec)
This parameter displays the value of the buffer-delay over the Upstream
path.
(ATU-C) SNR Margin (dB)
This parameter displays the noise margin measured at the ATU-C side
of a SNR (Signal to Noise Ratio) with a BER higher then 1x10-7.
(ATU-R) SNR Margin (dB)
This parameter displays the noise margin measured at the ATU-R side
(ATU-C) Previous SNR Margin (dB)
The previous SNR for ATU-C.
(ATU-R) Previous SNR Margin (dB)
The previous SNR for ATU-R.
(ATU-C) Attenuation (dB)
This parameter is the measured difference, in dB, in the total power
transmitted by the ATU-R and the total power received by the ATU-C
measured at initialization time.
(ATU-R) Attenuation (dB)
transmitted by the ATU-C and the total power received by the ATU-R
208 1/1553-HSC901 003/2 Uen B

(ATU-C) Signal Attenuation (dB)

during the showtime.
(ATU-R) Signal Attenuation (dB)
(ATU-C) Output Power (dBm)
This parameter displays the output power transmitted by ATU-C.
(ATU-R) Output Power (dBm)
This parameter displays the output power transmitted by ATU-R.
(ATU-C) Previous Output Power (dBm)
This parameter displays the previous output power transmitted by ATU-C.
(ATU-R) Previous Output Power (dBm)
This parameter displays the previous output power transmitted by ATU-R.
64xADSL Maintenance
This item allows to display and to manage the launch operations of maintenance
of ADSL lines.
1. Select the Maintenance folder, to display lines maintenance window.
1. In the Current Relay position field is possible to display the current status of
the TAM (Test Access Matrix) status for the line chosen.
1/1553-HSC901 003/2 Uen B 209

How to run a test via Splitter Bypass Connection Module:

1. By means of the relevant radio buttons the Operator can choose the kind of line
test to apply to this card. The possible choices in the frame are:
• Normal operation: no test is activating over this line.
• Central Office: Line testing is performed by direct twisted pair access.
The test consists in switching the relay on the splitter in order to bypass
it. The measurements are performed by external test equipment.
(Splitter Bypass, Central Office side).
2. Press Apply to launch the test or Refresh to update the section.
How to run a test via TAM Connection Module:

The TAM (Test Access Matrix) is a smart entity in the connection module area.
The TAM replace the function provided by the LTA card, because they allow to
select a subscriber line switching to the test bus and therefore to connect a test
instrument to it. The TAM occupies 2 slots and it is used in conjunction with
64xPOTS and 64xADSL cards.
1. By means of the relevant radio buttons the operator can choose the kind of line
tests to apply. The possible choices are:
• Line monitoring: switching the relays on the TAM Connection Module in
order to monitor the line without affecting the traffic.
• Inward Test: switching the relays on the TAM Connection Module in
order to test the interface (xDSL/POTS).
• Outward Test: switching the relays on the TAM Connection Module in
order to test the line.
64xADSL NT Inventory Status
This item allows displaying the Inventory information of the NT device.
1. Select the NT Inventory folder.
210 1/1553-HSC901 003/2 Uen B

This window displays the Vendor Information Inventory identification. The

following information is available:
Vendor ID, according to the modem used, this parameter can be codified
following the ITU-T G.994.1 or ANSI T1.413 specifications. If the
Vendor ID is codified as ANSI T1.413 the field "Vendor Name" is
displayed otherwise a "Not available" text string will be displayed
Version number, vendor assigned number. The field describes the NT
associated to ADSL Line;
Vendor Name, name of the manufacturer that owns the ID shown in the
Vendor ID field of the folder (only for modems that follow the ANSI
T1.413 specifications).
3. Use the Close button to exit the window.
ADSLx64 Connectivity Test
End-to-end connectivity tests are used for verify that the path between the
CPE modem, IPDSLAM is OK.
End-to-end connectivity test is split in two independent tests: ATM PVC TEST
and PPP over Ethernet Test.
End-to-end connectivity test can be executed only on lines that have been
enabled.
In the ATM PVC test a number of "ATM OAM F5 end-to-end loopback' cells are
sent on each PVC created on the subscriber line. The CPE modem must return
a reply within 5 seconds.
In order to run the test the user must press the button Start Test. The result of
the test is displayed in the column RESULT.
1/1553-HSC901 003/2 Uen B 211

PPP over Ethernet Test is executed on each PVCs with the Access Method
set to PPPoE. The test is a PADI packet broadcasted on the Ethernet through
the Bridge/Filter for this line). The test succeeds when at least one "Access
Concentrator" server replies with a PADO socket.
In order to run the test the user must press the button Start Test.
The result of the test is displayed in the column RESULT.
2.6.4 VDSL Unit Configuration

Proceed as follows
1. Select the slot of the 32xVDSL unit to be configured and click over it using the
2. Select the Lines item, to display the 32xVDSL configuration window.
follows:
carrier is present.
VDSL Lines Configuration
This item allows configuring the VDSL lines of the 32xVDSL Unit.
a set of ADSL lines.


1. Select each line that is to be added to the set, while holding down the CTRL key.
212 1/1553-HSC901 003/2 Uen B

How to configure the VDSL parameters:

2. The Line Configuration Profile scroll list is used to identify the row in the xDSL
Line Configuration Profile Table (Configuration -> xDSL Profile -> xDSL Line
Profile) which applies for this VDSL line, and channels if applicable.
3. Use the clockwise arrow icon to update the list of xDSL Configuration Profile.
the xDSL Line profile Management window.
5. Alarm Profile scroll list is used to identify the row in the VDSL Line Alarm
Configuration Profile Table, which applies to this VDSL line, and channels if
applicable.
6. Use the clockwise arrow icon to update the list of ADSL Alarm Profile.
xDSL Alarm Profiles window.
8. PSD Spectrum Profile scroll list is used to show, set and modify the PSD
Spectrum profiles configured for the selected line(s).
9. By pushing View/Change PSD Spectrum Profile it is possible to gain access
to the ADSL PSD Profile Management window.
10. VDSL PSD Profile scroll list is used to show, set and modify the PSD Spectrum
profiles configured for the selected line(s).
11. By pushing View/Change VDSL PSD Profile it is possible to gain access to the
VDSL PSD Profiles window.
1/1553-HSC901 003/2 Uen B 213

13. In the Transmission Mode Type section, is possible choose the actual
transmission mode with which the line was activated.
14. Select Refresh to re-read the current line configuration, Apply to confirm the
choices.
VDSL Lines Status
This item allows to display and to manage the state of VDSL lines.
2. Use the Enable or the Disable button, to enable or disable the VDSL link. If the
start-up procedure will be successfully completed, the Carrier on message will
be displayed; conversely the Carrier off indication will not change.

If the value cannot be detected the label "unknown" or "Not Available" will be
displayed.
Actual Transmission Mode
The actual transmission mode of the ATU-C. During VDSL line
initialization, the VDSL ATU-R will determine the mode used for this
link.
Actual Line State
ADSL line state.
(ATU-C) Alarms
The current state of the local ADSL interface by clicking over Details
214 1/1553-HSC901 003/2 Uen B

(ATU-R) Alarms
The current state of the remote ADSL interface by clicking over Details
In the Downstream and Upstream direction, the following information can be
detected:
(ATU-C) Actual Channel Rate (kbps)
This parameter displays the actual bit rate [kbit/s] of the Downstream
path over the line.
(ATU-R) Actual Channel Rate (kbps)
This parameter displays the actual bit rate [kbit/s] of the Upstream path
over the line.
(ATU-C) Previous Channel Rate (kbps)
This parameter displays the bit rate [kbit/s] of the Downstream path
over the line. Previous transmit rate on this channel, i.e. the transmit
rate before the last activation of the line.
(ATU-R) Previous Channel Rate (kbps)
This parameter displays the bit rate [kbit/s] of the Upstream path over
the line. Previous transmit rate on this channel, i.e. the transmit rate
before the last activation of the line.
(ATU-C) Attainable Rate (kbps)
attainable for the Downstream path.
(ATU-R) Attainable Rate (kbps)
attainable for the Upstream path.
(ATU-C) Interleav. Delay (msec)
This parameter displays the value of the buffer-delay over the
Downstream path.
(ATU-R) Interleav. Delay (msec)
This parameter displays the value of the buffer-delay over the Upstream
path.
(ATU-C) SNR Margin (dB)
This parameter displays the noise margin measured at the ATU-C side
(ATU-R) SNR Margin (dB)
This parameter displays the noise margin measured at the ATU-R side
(ATU-C) Previous SNR Margin (dB)
The previous SNR for ATU-C.
(ATU-R) Previous SNR Margin (dB)
The previous SNR for ATU-R.
(ATU-C) Attenuation (dB)
1/1553-HSC901 003/2 Uen B 215

(ATU-R) Attenuation (dB)

(ATU-C) Signal Attenuation (dB)
(ATU-R) Signal Attenuation (dB)
(ATU-C) Output Power (dBm)
This parameter displays the output power transmitted by ATU-C.
(ATU-R) Output Power (dBm)
This parameter displays the output power transmitted by ATU-R.
(ATU-C) Previous Output Power (dBm)
This parameter displays the previous output power transmitted by ATU-C.
(ATU-R) Previous Output Power (dBm)
This parameter displays the previous output power transmitted by ATU-R.
VDSL Maintenance
of VDSL lines.
Current relays position: This field is used to indicate the TAM status for the
current line.
216 1/1553-HSC901 003/2 Uen B

How to run a test via Splitter Bypass Connection Module

How to run a test via TAM Connection Module

The TAM replace the function provided by the LTA card, because they allow to
select a subscriber line switching to the test bus and therefore to connect a test
instrument to it. The TAM occupies 2 slots and it is used in conjunction with
64xPOTS, 64xADSL cards or 32xVDSL.
• Line monitoring: switching the relays on the TAM Connection Module
in order to monitor the line without affecting the traffic.
VDSL NT Inventory Status
1/1553-HSC901 003/2 Uen B 217


Vendor ID
According to the modem used, this parameter can be codified following the ITU-
T G.994.1 or ANSI T1.413 specifications. If the Vendor ID is codified as ANSI
T1.413 the field "Vendor Name" is displayed otherwise a "Not available" text
string will be displayed
Version number
Vendor assigned number. The field describes the NT associated to ADSL Line;
Vendor Name
Name of the manufacturer that owns the ID shown in the Vendor ID field of the
folder (only for modems that follow the ANSI T1.413 specifications).
VDSL Connectivity Test
The End-to-end connectivity test is split in two independent tests: ATM PVC
TEST and PPP over Ethernet Test.
enabled.
218 1/1553-HSC901 003/2 Uen B

2.6.5 SHDSL Unit Configuration

Proceed as follows:
1. Select the slot of the 32xSHDSL unit to be configured and click over it using the
2. Select the Lines item, to display the 32xSHDSL configuration window.
follows:
carrier is present.
SHDSL Lines Configuration
This item allows configuring the SHDSL lines of the 32xSHDSL Unit.
a set of SHDSL lines.


1. Select each line to be configured, while holding down the CTRL key.
1/1553-HSC901 003/2 Uen B 219

How to configure the SHDSL parameters

2. The Line Configuration Profile scroll list is used to show, set and modify the
value of this field identifies the row in the SHDSL Line Configuration Profile
Table (Configuration -> SHDSL Profiles and Setup) which applies for this
SHDSL line. Use the clockwise arrow icon to update the list of SHDSL
Configuration Profile.
the SHDSL Line profile Management window.
4. Alarm Profile scroll list is used to identify the row in the SHDSL Line Alarm
Configuration Profile Table, which applies to this SHDSL line. Use the clockwise
arrow icon to update the list of SHDSL Alarm Profile.
SHDSL Alarm Profiles Management window.
6. The Protocol Stack Profile scroll list is used to show, set and modify the
SHDSL Protocol Stack Profile configured for the selected line(s).Use the
clockwise arrow icon to update the list of SHDSL Alarm Profile.
7. By pushing View/Change Protocol Stack Profile it is possible to gain access
to SHDSL Protocol Stack Profile Management window.
9. Check the Wire Interface configuration via the relevant field. This field displays
the wire configuration for SHDSL line that can be: two wires, four wires, six wires
and eight wires.
220 1/1553-HSC901 003/2 Uen B

choices.
32xSHDSL Lines Status
This item allows to display and to manage the state of SHDSL lines.
2. Use the Enable or the Disable button, to enable or disable the Protocol Stack
Admin Status and the Line Admin Status. If the start-up procedure will be
successfully completed, the Carrier on/up message (Line Oper Status and Prot
Oper Status) will be displayed; conversely the Carrier off/down indication (Line
Oper Status and Prot Oper Status) will not change.

If the value cannot be detected the label "unknown" or "Not Available" will be
displayed.
Actual Line Rate (bps)
This parameter displays the actual bit rate [bit/s] of the physical line (gross
bandwidth).
Max Attainable Line Rate (bps)
This parameter displays the maximum bit rate [bit/s] attainable by the physical
line (gross bandwidth).
Regional Setting Max
This parameter displays the regional setting, in the SHDSL unit is Region2
Actual Payload Rate (bps)
1/1553-HSC901 003/2 Uen B 221

This parameter displays the actual payload bit rate [bit/s] transmittable over the
SHDSL frame (net bandwidth).
Attainable Payload Rate (bps)
This parameter displays the maximum payload bit rate [bit/s] transmittable over
the SHDSL frame (net bandwidth).
STU-C/R Unit Status
This parameter displays the status of the status of the STU-C/R devices
(alarmed or not)
STU-C/R Attenuation (db)
This parameter displays the line attenuation (db) measured in STU-C/R side.
STU-C/R SNR Margin (db)
This parameter displays the Signal-noise ratio of the line (db) measured in STU-
C/R side.
32xSHDSL Maintenance
of 32xSHDSL lines.
2. In the Current Relay position field is possible to display the current status of
the TAM (Test Access Matrix) status for the line chosen.
How to run a test via Splitter Bypass Connection Module:

222 1/1553-HSC901 003/2 Uen B

How to run a test via TAM Connection Module:

The TAM allows to select a subscriber line switching to the test bus and
therefore to connect a test instrument to it.
• Line monitoring: switching the relays on the TAM Connection Module in
order to monitor the line without affecting the traffic.
How to run the Search Tone test:

In the Search Tone Test section the operator is able to control the
activation/deactivation of the search tone. After the choice (Enable/Disable)
press the Send Cmd button to apply the action. This test is traffic affecting and
the NE shall disrupt the communication, blocking the line if it is busy. A Warning
will be displayed before activating the Search Tone test. After a fixed time the
NE shall automatically deactivate the search tone test.
32xSHDSL NT Inventory Status

1/1553-HSC901 003/2 Uen B 223

Vendor ID
According to the modem used, this parameter can be codified following the ITU-
T G.994.1 or ANSI T1.413 specifications. If the Vendor ID is codified as ANSI
T1.413 the field "Vendor Name" is displayed otherwise a "Not available" text
string will be displayed.
EOC Version
This field displays the version of the Embedded Operation Channel
Version number
Vendor assigned number. The field describes the NT associated to ADSL Line.
SHDSL standard
This field displays the SHDSL standard implemented by the STU-C/R device.
Supported Regional Settings
This field displays the SHDSL regional setting implemented by the STU-C/R
device.
32xSHDSL Connectivity Test
The End-to-end connectivity test is split in two independent tests: ATM PVC
TEST and PPP over Ethernet Test.
enabled.
224 1/1553-HSC901 003/2 Uen B

2.6.6 POTS Unit Configuration

Two different POTS unit types are available: 60xPOTS and 64xPOTS.In the
following paragraphs the configuration of the POTS Lines item will be described
independently from the unit type. In fact the configuration parameters are the
same.
Proceed as follows
1. Select the slot of the POTS unit to be configured and click over it using the right
mouse button, in order to display the floating menu.
2. Select the POTS Lines item, to display the POTS Lines Configuration
window.
follows:
carrier is present.
POTS Lines Configuration
This item allows configuring the POTS lines of the POTS Unit.
1/1553-HSC901 003/2 Uen B 225

1. Select the icon representing the line (1 to 60/64) to be configured.

to select and deselect multiple lines at the same time using the SHIFT and
CONTROL keys (read below the procedure). Multiple lines selection is used to
apply an identical configuration to a set of POTS lines.


1. Select each line to be configured while holding down the CTRL key.
How to configure a line

226 1/1553-HSC901 003/2 Uen B

2. Choose the desired AC Profile, DC Profile, Metering Profile and CLI (Calling
Line Identification) Profile via using the relevant scroll lists. The parameters
available are taken from the national mapping files downloaded into the
equipment. A brief explanation of the profiles is given in the following:
AC Profile defines the transmission characteristics, e.g. voice termination gain
block and filter block commands and data. Each AC Profile is designed for
specific requirements of different market segments and standards. The profile is
also specific to the actual HW.
DC Profile defines feed characteristics, e.g.: constant current, resistive feed and
loop supervision. Each DC Profile is designed for specific requirements of
different market segments and standards. The profile is also specific to the
actual HW.
Metering Profile defines the metering characteristics, e.g. signal frequency,
cadence and level. Each Metering Profile is designed for specific requirements
of different market segments, standards and/or subscriber metering device.
The profile is also specific to the actual HW.
CLI Profile defines the Calling Line Identification characteristics, e.g. signal
frequency, cadence and level. Each CLI Profile is designed for specific
requirements of different market segments and/or standards. The profile is also
specific to the actual HW.
3. Choose the desired ToIP profile and RTP profile. Use the clockwise arrow
icons to update the list of profiles. By pushing View/Change ToIP Profile and
View/Change ToIP Profile it is possible to gain access to the relevant profiles
manager windows. A brief explanation of the profiles is given in the following:
ToIP Profile defines the Telephony over IP parameters for a line. The
characteristics include echo cancellation, audio codec, packet size and jitter
buffer configuration. Each Profile is designed for specific requirements of
different market segments and standards.
RTP Profile defines the Transport Protocol for Real-Time Applications
parameters for a line. The characteristics include VLAN ID, VLAN priority, layer
3 IP ToS field, local RTP IP address and default gateway address. Each Profile
is designed for specific requirements of different market segments and
standards.
4. Insert the line parameters to adapt the line characteristic to the customer
requirements. The parameters are the following:
Automatic Gain Control: This parameter is used to enable or disable the
Automatic Gain Control (AGC) of a POTS line. Possible values are enabled and
disabled.
Howler Tone: This parameter is used to enable or disable the Howler Tone
for a POTS line. Possible values are enabled and disabled.
Line Type: This parameter is used to configure the behavior of the physical line,
supervisory and control signals for current entry. Possible values:
- Simplex: normal POTS line
- Loop Calling PABX: loop calling Private Automatic Branch Exchange
- Earth Calling PABX: earth calling Private Automatic Branch Exchange
RTP Local IP Address: This parameter is the Local RTP IP Address for the line
termination. This address must be coherent with the field "Default Gw IP Addr"
that it is have been defined in the RTP POTS Profiles. When configuring a VoIP
1/1553-HSC901 003/2 Uen B 227

Termination on this line, the Termination Media Local IP Address must be

configured the same as the RTP Local IP Address.
Ground Key Detection: This parameter allows enabling ground start
functionality. Possible values are enabled and disabled.
Metering level (mV): This parameter defines the Voltage level of a metering
pulse in millivolt RMS in 200 Ohm. The loop resistance should be considered
when this value is defined. Setting this value for the line will overrule the general
defined voltage level for the metering on this line alone. Possible values are zero
or a value in the range from 200 to 2200.Value 0 means use default value from
basic configuration.
Tx level (dBr). The Transmit Level parameter indicates the relative level
between the analogue line and the digital side. Possible values are in the range
from -8..6 dBr in 0.5 dBr steps or "Default". The default value can be read via
"Default Tx Level" parameter.
Rx level (dBr): The Receive level parameter indicates the level between the
digital side and analogue line set via basic configuration. Possible values are in
the range from -11..1 dBr in 0.5 dBr steps or "Default". The default value can be
read via "Default Rx Level" parameter.
choices.
POTS Lines Status / Maintenance
This item allows to display and to manage the status and the maintenance of the
POTS lines.
Select the Status / Maintenance folder.
In the upper section is possible enabling or disabling one or a set of lines POTS
by pressing the buttons.
228 1/1553-HSC901 003/2 Uen B

In Line Oper Status field, the Operator is able to see the current operational
status of the interface (the value will be enabled or disabled).
In Line Status area, there is the possibility to have an indication of the real
status of the physical line via the following fields:
• Additional Status Info: This parameter displays additional info on the
operational status of the line. This parameter can assume the following
values:
no add info: no additional information
Testing: line is in testing mode
Foreign Voltage: Foreign voltage detected on line
Disabled by management: Disabled by management system
Thermal fault: Disabled due to high temperature
Battery fault: Battery failure on card
DC Fault: DC fault detected on line
AC Fault: AC fault detected on line
Ground Key Fault: Ground Key Fault detected on line.
• Last Change: This parameter indicates hour and date when the
associated user port entered in its current operational status. If the
current status was entered prior to the last re-initialization of the local
network management subsystem, then this object contains a zero value.
• Call Status information: This parameter indicates the call related status
information for the POTS line. This state information is intended for
testing and error tracking purpose. It is state information collected on the
POTS line side i.e. it is not reflecting states in the call control. This
parameter can assume the following values :
Idle: Line is not in use - loop is open (On hook)
Dialing: Line is in use and dialing is possible
Ringing: Cadenced ringing is applied to the line
Busy: Line is in active call - speech path established
On hold: Line is busy, but speech path is put on hold
Failure: Line is not in service. Call attempt will be rejected.
T.38: Line is busy in T.38 operation mode.
Modem: Line is busy with modem call detected
Parked: Line is in reduced battery feeding mode
N.A: State information not available
• Battery Level: This parameter allows the manager to read the current
selected battery level. This parameter can assume the following values:
High
Low
Medium
N.A. (not available)
• Tx Power Level: This parameter indicates the Current transmit nominal
voice level set on line when the Automatic Gain Control (AGC) is
enabled. The value is in the range from -8 to 6, it is expressed in dBr
1/1553-HSC901 003/2 Uen B 229

• Rx Power Level: This parameter indicates the Current receive nominal

voice level set on line when the Automatic Gain Control (AGC) is
enabled. The value is in the range from -11 to 1; it is expressed in dBr.
How to enable/disable physical line(s)

Be aware to enable the physical interface you want to use. It is possible to
enable/disable multiple lines. In this case select more than one line (using CTRL
or SHIFT) and then enable selected lines or disable selected lines depending
which operation you want to perform.
How to run the Search Tone test

In the Search Tone Test section the operator is able to control the
activation/deactivation of the search tone. After the choice (Enable/Disable)
press the Send Cmd button to apply the action. This test is traffic affecting and
the NE shall disrupt the communication, blocking the line if it is busy. A Warning
will be displayed before activating the Search Tone test. After a fixed time the
NE shall automatically deactivate the search tone test.
2.6.7 ISDN Unit Configuration

In the following paragraphs the configuration of the ISDN Lines item will be
described independently from the unit type.
Proceed as follows
1. Select the slot of the ISDN unit to be configured and click over it using the right
mouse button, in order to display the floating menu.
2. Select the ISDN Lines item, to display the ISDN Lines Configuration window.
follows:
carrier is present.
2.6.7.1 ISDN Lines Configuration
This item allows configuring the ISDN lines.
1. Select the icon representing the line (1 to 32) to be configured.
230 1/1553-HSC901 003/2 Uen B

to select and deselect multiple lines at the same time using the SHIFT and
CONTROL keys (read below the procedure). Multiple lines selection is used to
apply an identical configuration to a set of ISDN lines.


Select each line to be configured while holding down the CTRL key.
How to configure a line

2. Choose the desired ToIP profile and RTP profile. Use the clockwise arrow
icons to update the list of profiles. By pushing View/Change ToIP Profile and
View/Change ToIP Profile it is possible to gain access to the relevant profiles
manager windows. A brief explanation of the profiles is given in the following:
ToIP Profile: This parameter defines the Profile for Telephony over IP, ToIP
parameters for a line. The characteristics include echo cancellation, audio
codec, packet size and jitter buffer configuration. Each Profile is designed for
specific requirements of different market segments and standards.
RTP Profile: This parameter defines the Profile for RTP (Transport Protocol for
Real-Time Applications), RTP parameters for a line. The characteristics include
VLAN ID, VLAN priority, layer 3 IP ToS field, local RTP IP address and default
1/1553-HSC901 003/2 Uen B 231

gateway address. Each Profile is designed for specific requirements of different

market segments and standards.
3. Set the RTP Local IP Address, this parameter defines the Local RTP IP
Address for the line termination. This address must be coherent with the field
Default Gw IP Addr that it is have been defined in the RTP ISDN Profiles.
When configuring a VoIP Termination on this line, the Termination Media Local
IP Address must be configured the same as the RTP Local IP Address.
4. Enable or Disable the Remote Power Feeding of the line via the relevant scroll list.
This parameter is used to configure the remote power feeding as switched on
(Actived) or switched off (Deactived).
5. Set the Q.921 Termination Configuration section (if desired) via the following
parameters:
Data Link mode: This parameter specifies the type of access; it can assume the
following values Point To Point and Point To Multipoint. Only Point To Point is
allowed on ISDN-PRA terminations.
Activation Mode: It specifies the activation / deactivation policy for Point To
Multipoint access. Possible values are On Demand and Permanent. Activation
mode can only be set to On Demand if the Data Link Mode parameter is Point
To Multipoint.
Disconnected Mode Options: It specifies whether establish requests are rejected
with the standard DM message or not. This feature is applicable to Point To
Point and Point To Multipoint access modes.
Network Orientation: It specifies whether the interface is acting as the network or
the user side. The option only applies when access mode is Point To Point. In
the Point To Multipoint access mode only network is allowed.
Deactivation Timer (secs): It specifies the Layer 2 inactivity deactivation timeout
in units of 1 second. When Activation Mode is set to On Demand, this value
must be non zero while the Activation Mode is set to permanent, this value must
be zero.
6. Set the Alarms Configuration section (if desired) via the following parameters:
EXC BER Threshold Timer: It represents the threshold of CRC errored frame
blocks used to detect the EXC Alarm, which is notified when for each 10
consecutive sec the threshold is exceeded. The consequence action is service
unavailable and access disable. (BER = 10exp-3 corresponds to specified
number of CRC errored frame blocks, DeltaT = 1 sec).
DEG BER Threshold Timer: It represents the threshold of CRC errored frame
blocks used to detect DEG Alarm, which is notified when the threshold is
exceeded. The consequence action is access is still available and an indication
of the faulty line has to be sent. (BER = 10exp-6 corresponds to specified
number of CRC errored frame blocks, DeltaT = 60 sec).
7. Select Apply to confirm the choices and Refresh to re-read the current line
configuration.
232 1/1553-HSC901 003/2 Uen B

ISDN Lines Status

This item is used to display the status of the ISDN Lines.
This window displays the status of the ISDN line. In the upper section of the
window it is possible to enable/disable the single line or enable/disable all
selected lines by pressing the corresponding buttons.
If the start-up procedure will be successfully completed, the Enabled message
will be displayed; conversely the Disabled indication will not change.
In the lower part of the window it is possible to display the following parameters:
Line Status
Line code: it shows the line code of the ISDN line. Possible values:
• 2B1Q line code (2 binary,1 quaternary)
• 4B3T line coding (code mapping 4 bits into 3 ternary symbols, also
known as MMS 43).
Remote Power Feeding Status: It shows the status of the remote power feeding
of the line. Possible values are Activated and Deactivated.
Alarm status: it shows the alarms present in the ISDN line
Manual Line Activation Status: It shows if the line has been manually activated
or deactivated
Loopback status: it shows if some loopbacks are present on the ISDN line
(noLoop, Loopback1, Loopback2)
ISDN Q921 Terminations Status
Status: It shows the overall status of the datalink and the dependency for
failures.
Related IDIdentity: it shows the IUA interface associated to this ISDN interface
1/1553-HSC901 003/2 Uen B 233

MGC Link Man Status: it shows whatever the Media Gateway Controller has
blocked the data link
Data Link Status: it shows the data link status. This information is only applicable
when the access mode is point To Point. The possible status is:
• N.A.: means the data link cannot be returned to service.
• Established: means the operational state is enabled.
• Remote Related: means the other end-user has disconnected the data
link (i.e. a 'Disconnect' frame has been received).
• Protocol Error: means the data link internal behavior has resulted in a
data link disconnection.
• Released: means that 'Release other' has been received from the MGC.
• Establishing: means that the Gateway is in the process of trying to
establish the data link.
Automatic TEI Count: It shows the number of dynamic TEIs assigned on this
termination. This information is only applicable when the access mode is point
To Multipoint. Zero will always be returned for the point To Point case.
Estab. Data link Count: It shows the number of established Data Links on this
termination.
ISDN Maintenance
This item is used to manage the maintenance of the ISDN Lines.
The maintenance window allows applying the following actions:

• Remote Power Feeding Activation/Deactivation.
• Manual Activation/Deactivation.
• Search Tone Test Enabled/Disabled.
• Loopback (no Loopback, Loopback 1 and Loopback 2).
234 1/1553-HSC901 003/2 Uen B

• Pattern Injection Test (with Loopback 1, Loopback 2 and with Loopback 1+2).
In order to perform these operations, check with the left mouse button the
operation to apply and then press the button Send Cmd.
In case of Pattern Injection Test, choose the type of test and then press Send
Pattern. Afterwards press Get results to display the results of the test.
It is important to remember that Loopback 1 is applied in the local interface and
the traffic is looped locally while Loopback 2 is applied in the Network
termination connected to the interface. This loopback forward back the traffic to
the ISDN interface of the equipment.
2.6.7.2 ISDN Performances
ISDN Performance Configuration

The graphical area provides the access to the Performance configuration
window. The following performances are possible in near and far end:
• Errored Seconds;
• Severely Errored Seconds;
• Unavailable Seconds;
• Background Block Errors.
In order to configure the monitoring follow the procedure listed below.
1. Inside the graphical area, move the cursor on the unit to perform the monitoring
and click on it with the right mouse button to display the unit menu
2. Select the Performance option to display the Performance window.
Two folders are available inside the ISDN Performance Management window;
the first is used for the Performance configuration and the latter one for the
Performance Data retrieving.
1/1553-HSC901 003/2 Uen B 235

To configure ISDN Performance Monitoring

1. Select the relevant folder.
2. Select the Port you where to configure the performance monitoring from the top
part of the window.
3. Select the Monitoring Admin State field and then click on the button Enable
Monitoring.
4. The label above the relevant field will change from "Disabled" to "Enabled" .
To disable a Performance Monitoring

1. Select the Monitoring Admin State field and then click on the button Disable
Monitoring.
2. A warning pop-up window will appear in order to prevent user from accidentally
deletion of a Performance entity.
3. The label above the relevant field will change from "Enabled" to "Disabled”. .
To reset all the old and the actual Performance monitoring counters of the
selected rows, click on the Reset Counters button.
ISDN Performance Data
ISDN Performance Data can be read by selecting the ISDN Performance Data
folder.
The graphical area provides the access to the Performance configuration

window. In order to configure the monitoring follow the procedure listed below.
1. Inside the graphical area, move the cursor on the unit where to perform the
monitoring and click on it with the right mouse button to display the unit menu.
2. Select the Performance option to display the Performance Monitoring window.
To retrieve ISDN Performance Data
236 1/1553-HSC901 003/2 Uen B

1. Select the relevant folder.

2. Select the Port where to read the Performance data from the top part of the
window.
3. Select the field DataType and select a value. Allowed values are showed in the
picture below:
4. Select the field Historical, if available, and choose a value from the list.
5. To read performance data it is provided a scrollbar for each monitored field .
6. The first two fields inside the performance data area, are always Time Elapsed
and Suspect Data.
Time Elapsed value indicates the time (in seconds) elapsed from the activation
of the performance monitoring. When historical data are requested, this field
shows when the performance monitoring was activated.
Suspect Data value gives information relevant to the validity of the retrieved
data. This field can show the following values:
Valid, the data has been correctly collected.
Invalid, the data collected are not correct. There are few reasons why it was
not possible to collect data:
- Reset (rst), the data collection was reset;
- Time, there was a clock adjustment during the data collection;
- Near, there was a problem about the collection of the data.
To select Data Type and Historical parameters

The Local Craft Terminal can retrieve the data collected and different time
intervals can be chosen. The main types of intervals are:
Current, time interval starting from the current time;
Previous, time interval starting in a specific moment, selectable from the
Historical field.
A label is used to select the time interval where the "M" symbol indicates the
minutes and the "Day" word indicates a full 24 hours day.
To enable the Historical field, you have to select a "Previous" option in the Data
Type field.
1/1553-HSC901 003/2 Uen B 237

Using the Historical field you can select how many previous time intervals you
want to start the data retrieving: the time interval dimension is selected using
"Previous" option from the Data Type field.
238 1/1553-HSC901 003/2 Uen B

2.7 Maintenance Functions

This group of functions includes the procedures to perform the maintenance
operation such as displaying hardware and software inventories, software
download and the procedures to reboot the equipment.
2.7.1 Display LT Software Version and User Guide
PATH: (Help ->About)

Trough this option, it is possible to display the software version of the local
operator and the software version of AXH-EDA ADD-ON package. The shortcut
button is selectable from the Logon window by clicking on it with the right mouse
button or selecting About from the main menu.
Moreover from the About menu is possible to display the Third Party License
Agreements manual, by clicking the relevant button. This document contains
the license agreements for all third-party products software used in EDA.
PATH: (Help ->User Guide)
This selection will start the Acrobat Reader software in order to open the on Line
User Guide of the AXH-EDA Local Terminal software.
2.7.2 Check connection to Equipment

PATH: (Maintenance -> Check connection to Equipment)
This window may be used to verify if a given equipments is reachable and
available for the management.
The following checks are done:
• verify the reply to "ping" command
• verify if SNMP agent responds
This window may be acceded from the Logon window by clicking with the
mouse's right-button on the telephone image and then selecting "Check
connection to Equipment" or selecting the entry "Check connection to
equipment" from the "Maintenance" menu.
1/1553-HSC901 003/2 Uen B 239

1. Insert or select in the Equipment IP Address field the IP address of the

equipment that you wish to check
2. Press the Check connection status button
In the middle section the operator can see the results of the operation.
• PING IP Address field displays the result of the ping command. It can
be "SUCCESS" or "FAILED".
• Verify SNMP access field displays if the equipment has an active
SNMP agent.
• Equipment status field displays if the equipment is ready for the
management.
• Equipment Description field displays the type of the equipment.
2.7.3 Displaying Hardware and Software Inventories

The program includes some functions to verify the hardware and software
releases of the AXH/EDA Local Terminal, the Equipment and the Network
Terminations.
Subrack Hardware Inventory
PATH: (Maintenance ->Subrack Hw Inventory)
This item permits to show the HW Inventory of the subrack. Select the item "Hw
Inventory" in the Maintenance menu in order to display the following picture.
The Subrack Hardware Inventory window provides information about the

equipment subrack with the following fields:
Subrack Type, this field shows the code number of the subrack;
Serial Number, this field shows the Factory Unit Serial Number.
Unit Software and Hardware Inventory
It is possible to open a single window, which resumes all the software and
hardware inventory information.
1. Select the slot where is located the unit to display the hardware and software
inventory codes
2. Click on the graphical representation of the unit, using the right button and a
menu will appear
3. Select the Hw/Sw Inventory item.
4. A window will arise, displaying the relevant information.
240 1/1553-HSC901 003/2 Uen B

5. Use the Refresh button to update the information

6. From Software and Hardware Inventory Data window, it is possible to check
which software banks are valid and the version of running application software.
2.7.4 Equipment Software Download

PATH: (Maintenance ->Software Download)
When it is necessary to download an updated version of the software running
within the equipment, a specific command can be used. To perform this
operation, it is necessary to access a TFTP/SFTP Server where the equipment
software has to be saved.
1. In the Automatic Software Download is possible enable/disable the auto

download feature, so when a new board is plugged into the slot, the software
download will automatically update the board according to the Software
download configuration list table.
2. Retry Period, expressed in minutes, after which the Equipment shall retry to
start the automatic software download.
1/1553-HSC901 003/2 Uen B 241

3. Fill the TFTP Server Identification fields, indicating a proper IP address and
the path where the software is stored.
4. Insert in File Transfer Protocol the type of ftp used.
5. Insert in FTP User the ftp user account.
6. Insert in FTP password the ftp password.
7. Load a new configuration using the Software Table Management facility: click
on New Conf button to load a new configuration file. A new window will pop up.
8. Inside the new window, browse your hard disk in order to indicate the new
configuration file location and press the OK button. Use the Filter button to filter
the files with a different extension than the default one (*.sdc): it is necessary to
modify the extension in the Filter field before using the Filter button.
The .sdc configuration file is used to simplify the download of the new software
in the equipment. To create a configuration file use a text file editor and insert a
single line for each downloadable software file, as illustrated in the example
below:
The first field indicates the unit involved in the software download. The second
field indicates the software serial code and the software version. The last field is
the file name.
242 1/1553-HSC901 003/2 Uen B

ALERT If the new software downloaded in the equipment uses a different type of
database version than the existing one, a forced switch must be performed.
In this case the configuration database will be erased with the consequent
loss of the equipment configuration.
9. After the selection of a new configuration file, it is possible to start the download
process with a click on the download button. A warning window will ask for
confirmation.
10. Click on the YES button to proceed with the software download
The System Software Download in progress window will pop up.
During the connection to the TFTP server the Idle label will be displayed and
during the download process the Downloading… label will be visible.
11. If the download process has been successfully completed, the label displayed
inside the System Software Download in progress window changes to
Download successful and two new buttons will be visible: the Switch
Software Bank and the Close button.
NOTICE Scratch DB checkbox must be not checked. This feature is not used in the
EDA2530 release 4.21. It must be checked only if required by the Ericsson
support.
1/1553-HSC901 003/2 Uen B 243

12. Press the Close button to complete the software download and not to switch to
the new software.
Press Switch Software Bank and follow the Switch Software Bank procedure
(later described in this chapter) to perform the bank switch software.
In case of errors, the Download Failed label will be visible. The System Software
Download Status window will resume the problems encountered during the
software download. Close the windows and go back to the System Software
Download.
13. After the download, an automatic check of the new software is performed, to
verify the compatibility between the database used for the current software
version and the one used for the previous software version. If they are
incompatible, the label Download successful but incompatible databases
will warn the operator
14. By pressing the Close button, the window goes back to the System Software
Download. By pressing the Switch Forced Software Bank button, a new
window will warn the user about the loss of the equipment configuration
244 1/1553-HSC901 003/2 Uen B

Switch Software Bank procedure

1. After successful software download, the Switch Software Bank button will be
available inside the System Software Download in progress window. Press
the Switch Software Bank button to start the software bank switch.
NOTICE Scratch DB checkbox must be not checked. This feature is not used in the
EDA2530 release 4.21. It must be checked only if required by the Ericsson
support.
2. A message will offer the last possibility to abort the operation
3. At the end of the switch process, the Switching label changes to Switch
successful. Press the Close button
After the software download it is not required to perform immediately a software
bank switch and the operation could be performed later.
By accessing the Software Download facility, the equipment is able to recognize
the presence of newer software inside the inactive software bank and a pop up
window will asks the operator to switch to the newer version.
Note Software download on 20 ADSL cards, 2 IP CP could take a lot of time. The
units with the same card type can be downloaded, in group of 5 units at
once.
2.7.5 Equipment Reboot
PATH: (Maintenance -> Equipment Reboot)

This option is used to restart the equipment unit or the controller unit.
1/1553-HSC901 003/2 Uen B 245

The window shows three types of reboot methods:

• Warm Reboot is used to reboot all the equipment units at software
level. This operation affects temporary the traffic transmission.
The equipment’s configuration is not lost;
• Hardware Reset is used to reset all the equipment units at hardware
level. This operation affects temporary the traffic transmission.
The equipment’s configuration is not lost;
• Restore Factory Default is used to clear the equipment configuration
and to restore the default configuration. The traffic will be permanently
lost. Out of Band Management is not lost and keeps the parameter
stored in the Backplane Eeprom. In Band Management instead could be
lost if the SFP are not MONI Tagged and if the Gigabit Ethernet uplinks
(with the relevant protection schemes) are not properly configured.
How to perform a Reboot

1. Select the Maintenance menu from the main menu bar
2. The window for selection of the reboot method information will appear
3. Press the Dismiss button to abort the operation and leave the window
4. Select the reboot you desire: Warm Reboot, Hardware Reset or Restore Factory
Default,
5. Press the Reboot button, to reboot the equipment using the selected method
6. Because this operation implies the loss of user traffic, a warning window will ask
to confirm the restart of the equipment
7. If the reboot is confirmed, a window will appear to notify that the EDA Local
Terminal will be disconnect before the equipment reboot
2.7.6 Configuration Backup/Restore

PATH: (Windows menu bar -> Start -> Programs -> AXH-EDA Local terminal x.y.z. ->
Backup & Restore Procedure)
This function is used to:
• backup the active equipment configuration, saving it on a file located in
the operator's computer hard disk.
• restore a previously saved equipment configuration.
The function is available via the Windows Start menu. Selecting Backup &
Restore procedure, the following window will be displayed:
246 1/1553-HSC901 003/2 Uen B

The configuration backup/restore operation is performed using Trivial File

Transfer Protocol (TFTP) and requires a running TFTP Server. If you use the
TFTP Server released by AXH-EDA LCT you can configure the timeout of the
"TFTP Server" by means the button "Settings". The default value is 3 seconds.
How to backup equipment configuration

1. Insert the equipment IP address
2. Click the Backup button to save the equipment configuration from the equipment
to a file on the operator's hard disk. After the application succeeds in
establishing a connection with the equipment, the following window is displayed:
Enter the name of the file that will contain the equipment configuration (Warning:
if the file exists, it will be overwritten) and click the Backup button.
The file transfer from the equipment to the local system may take few minutes.
The creation of the backup file in the equipment's memory is controlled by the
parameter "Backup Timeout". This parameter is configurable in "Application
General Configuration" window. The default is 20 minutes. Increase this value if
the backup fails.
How to restore equipment configuration
1/1553-HSC901 003/2 Uen B 247

ALERT This operation will overwrite the active configuration with the configuration
stored in the file saved on the computer's hard disk. Any configuration
change performed after the last configuration backup will be lost. The
operation may take few minutes. A reboot will be automatically done by the
equipment after the restore completion.
1. Insert the equipment IP address

2. Click on the Restore button, to download the equipment configuration. After the
application succeeds in establishing a connection with the equipment, the
following window is displayed:
The configuration restore operation is performed using the Trivial File Transfer
Protocol (TFTP) and requires a running TFTP Server. If you use the TFTP
Server released by this AXH-EDA LCT you can configure the timeout of the
"TFTP Server" by means the button "Settings". The default value is 3 seconds.
3. Browse your hard disk to find the new configuration file and press the
RESTORE button
When all tasks are completed, the label Continue will appear on the button. The
restore of the backup file in the equipment's memory is controlled by the
parameter "Restore Timeout". This parameter is configurable in "Application
General Configuration" window. The default is 40 minutes. Increase this value if
the restore fails.
.
248 1/1553-HSC901 003/2 Uen B

Eda2530r421 PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Eda2530r421 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

1/1553-HSC901 003/2 Uen B

© Ericsson AB, 2008. All Rights Reserved

All rights reserved. The information in this document is the property of

Microsoft Microsoft MS and MS-DOS are registered

Windows Windows is a trademark of the Microsoft

Adobe Reader Adobe and Reader are either registered

HP-UX HP-UX is a registered trademark of Hewlett-

JAVA JRE JAVA is a trademark or registered trademark

Linux Linux is a registered trademark of Linus

AdventNet AdventNet is a trademark of AdventNet, Inc.

Actual Version (Version B)

1/1553-HSC901 003/2 Uen B 3

IV 1/1553-HSC901 003/2 Uen B

2.4.14.9 VLAN SubInterface Configuration 105

1/1553-HSC901 003/2 Uen B V

2.6.2 CP-IP Unit 189

VI 1/1553-HSC901 003/2 Uen B

1/1553-HSC901 003/2 Uen B 7

1.1 Conventions Used In Handbook

1.2 Hardware and Software Requirements

NOTICE Electrical Safety: equipment must be compliant with EN60950.

8 1/1553-HSC901 003/2 Uen B

1.3 Application Software Installation

NOTICE DE-INSTALLATION NOTES

ITCL Installation Procedure

1/1553-HSC901 003/2 Uen B 9

NOTICE DE-INSTALLATION NOTES

Adobe Reader Installation Procedure

NOTICE DE-INSTALLATION NOTES

Local Terminal Installation Procedure

10 1/1553-HSC901 003/2 Uen B

1. Locate the Setup.exe program contained inside the software CD.

NOTICE DE-INSTALLATION NOTES

SNMP Trap_LCT for Windows XP

1/1553-HSC901 003/2 Uen B 11

ADD-ON Installation Procedure

1. Locate the Setup.exe program contained by the LCT directory labeled as

NOTICE DE-INSTALLATION NOTES

12 1/1553-HSC901 003/2 Uen B

1.4 Connecting the Personal Computer to the Equipment

1/1553-HSC901 003/2 Uen B 13

14 1/1553-HSC901 003/2 Uen B

1/1553-HSC901 003/2 Uen B 15

2.2 Application Software Activation

16 1/1553-HSC901 003/2 Uen B

5. After these operations, the sub rack structure will be displayed.

1/1553-HSC901 003/2 Uen B 17

2.3 Main Window Description

It can be divided in the following functional parts:

18 1/1553-HSC901 003/2 Uen B

Synchronization button: this button is used to manage the equipment

Equipment Parameters (e)

1/1553-HSC901 003/2 Uen B 19

Graphical Area Section (f)

20 1/1553-HSC901 003/2 Uen B

2.4 Main Menu

2.4.1.1 Refresh Equipment View

PATH: (File Æ Refresh Equipment View)

2.4.1.2 Log off

PATH: (File Æ Logoff)

PATH: (File Æ Exit)

2.4.2 Application Options Menu

1/1553-HSC901 003/2 Uen B 21