Escolar Documentos
Profissional Documentos
Cultura Documentos
MAIN FUNCTIONS.................................................................................................................25
MENU BAR AND MENUS .................................................................................................................. 25
GRAPHICAL AREA............................................................................................................................. 26
ALARM SUMMARY............................................................................................................................. 27
TOOL BAR........................................................................................................................................... 28
The Connection Status Indication .................................................................................................... 29
Exit Button......................................................................................................................................... 29
Operator Access Button ................................................................................................................... 29
Script Execution Button .................................................................................................................... 29
Script Upload Button......................................................................................................................... 30
Synchronisation Configuration Button (ADM) .................................................................................. 30
Cross-connection / Labels Operations Button (ADM) .................................................................... 30
Ethernet Line Protection Button (ADM-16) (ADM-64)...................................................................... 30
Alarm/Event Log Button.................................................................................................................... 30
339-1268/06
Navigation Page
Book Contents
Performance Button.......................................................................................................................... 30
Help Button ....................................................................................................................................... 30
ALARM AND EVENT MONITOR WINDOW ...................................................................................... 31
PROGRESS BAR................................................................................................................................ 31
339-1268/06
Navigation Page
Book Contents
339-1268/06
Navigation Page
Book Contents
339-1268/06
Navigation Page
Book Contents
SPECIFIC FUNCTIONS: CHANNELS - STM-16 FOR VC-4-4C/4V AND 16C/16V (ADM-64) (ADM16) ...................................................................................................................................................... 165
STM-16 for VC-4-4c/4v and 16c/16v Unit Performance Data ....................................................... 168
STM-16 for VC-4-4c/4v and 16c/16v Unit Alarm Management..................................................... 169
Delay setting ................................................................................................................................... 169
SPECIFIC FUNCTIONS: CHANNELS - GIGABIT ETHERNET UNITS (ADM-16) (ADM-64) ........ 169
Gigabit Ethernet Unit Performance Data........................................................................................ 176
Gigabit Ethernet Loopback Management ...................................................................................... 176
Gigabit Ethernet Alarm Management............................................................................................. 176
SPECIFIC FUNCTIONS: CHANNELS - AUXILIARY UNIT ............................................................. 177
EOW Channels............................................................................................................................... 177
Auxiliary Channels .......................................................................................................................... 181
DAM UNIT CONFIGURATION .........................................................................................................182
Input Collector................................................................................................................................. 182
Output Collector.............................................................................................................................. 184
8XFAST ETHERNET UNIT COMMISSIONING............................................................................... 185
8XFAST ETHERNET UNIT: UNIT CONFIGURATION.................................................................... 186
8xFast Ethernet Unit: Ethernet Ports Configuration folder............................................................. 186
8xFast Ethernet Unit: Groups Configuration folder........................................................................ 191
8xFast Etherent Unit: Bandwidth Allocation folder......................................................................... 195
8xFast Etherent Unit: Port folder .................................................................................................... 198
PERFORMANCE..................................................................................................................202
PERFORMANCE: ALL PERFORMANCES ..................................................................................... 202
PERFORMANCE MANAGEMENT: THRESHOLD PROFILES ...................................................... 211
LOCAL ETHERNET DATA PERFORMANCE ................................................................................. 214
REMOTE ETHERNET DATA PERFORMANCE.............................................................................. 217
QUEUE ETHERNET DATA PERFORMANCE ................................................................................ 220
CONFIGURATION FILES....................................................................................................222
OSI CONFIGURATION..................................................................................................................... 222
CHANGING THE OSI PROTOCOL PARAMETERS ....................................................................... 223
OSI.INI FILE FOR COMMUNICATION AND CONTROL UNIT TYPE C......................................... 223
OSID.INI FILE FOR COMMUNICATION AND CONTROL UNIT TYPE D...................................... 224
PARAMETERS OF OSI.INI FILE...................................................................................................... 226
Transport Layer .............................................................................................................................. 226
Network Layer................................................................................................................................. 228
Operative Indications ...................................................................................................................... 237
Examples ........................................................................................................................................ 239
DESCRIPTION OF AGENT.CNF FILE............................................................................................. 254
MAIN section................................................................................................................................... 255
CONFIG section ............................................................................................................................. 256
B_INTERFACE section .................................................................................................................. 257
LAMP section.................................................................................................................................. 257
339-1268/06
Navigation Page
Book Contents
339-1268/06
Navigation Page
Book Contents
OCH-LOM....................................................................................................................................... 277
OTU-TIM......................................................................................................................................... 277
OTU-BDI ......................................................................................................................................... 277
OTU-SSF ........................................................................................................................................ 278
ODU-AIS ......................................................................................................................................... 278
ODU-BDI......................................................................................................................................... 278
ODU-SSF........................................................................................................................................ 278
ODU-OCI ........................................................................................................................................ 279
ODU-TIM......................................................................................................................................... 279
ODU-PLM ....................................................................................................................................... 279
OH Bus Rx Fail ............................................................................................................................... 279
OH Bus Tx Fail ............................................................................................................................... 280
OR Batt ........................................................................................................................................... 280
Plug Module Missing ...................................................................................................................... 280
Protection State Unstable............................................................................................................... 280
Protection State Mismatch.............................................................................................................. 280
Power Fail ....................................................................................................................................... 281
QI/F Link Down ............................................................................................................................... 281
Received Power High Low ............................................................................................................. 281
RS OH: n Disp Fail ......................................................................................................................... 282
RS OW: n Disp Fail......................................................................................................................... 282
RS UC: n Disp Fail.......................................................................................................................... 283
RS: 1 DEG ...................................................................................................................................... 283
RS: 1 EXC....................................................................................................................................... 283
RS: n LOF ....................................................................................................................................... 284
RS: n TIM........................................................................................................................................ 284
Sync Fail ......................................................................................................................................... 284
T. PDH: n AIS ................................................................................................................................. 285
T. PDH: n DEG ............................................................................................................................... 285
T. PDH: n DEG (In Faw).............................................................................................................. 285
T. PDH: n DEG (In - CRC-4) .......................................................................................................... 286
T. PDH: n EXC................................................................................................................................ 286
T. PDH: n EXC (In Faw) .............................................................................................................. 287
T. PDH: n EXC (In - CRC-4)........................................................................................................... 287
T. PDH: n LOF ................................................................................................................................ 287
T. PDH: n LOF (In).......................................................................................................................... 288
T. PDH: n LOS................................................................................................................................ 288
T. PDH: n CRC-4 mismatch (In)..................................................................................................... 288
T. PDH: n RAI (In)........................................................................................................................... 288
T. PDH: n AIS (Out) ........................................................................................................................ 289
T. PDH: n DEG (Out - CRC-4) ....................................................................................................... 289
T. PDH: n EXC (Out - CRC-4)........................................................................................................ 289
T. PDH: n LOF (Out)....................................................................................................................... 290
T. PDH: n CRC-4 mismatch (Out).................................................................................................. 290
T. PDH: n Tx Fail ............................................................................................................................ 290
339-1268/06
Navigation Page
Book Contents
339-1268/06
Navigation Page
Book Contents
339-1268/06
Navigation Page
Book Contents
339-1268/06
Navigation Page
10
Book Contents
339-1268/06
Navigation Page
11
Book Contents
339-1268/06
Navigation Page
12
Book Contents
HOW TO................................................................................................................................331
PROCEDURE TO EXECUTE A DATABASE DOWNLOAD............................................................ 331
339-1268/06
Navigation Page
13
Book Contents
GENERAL INFORMATION
INTRODUCTION
The equipment is connected to the Control Application which allows its management for monitoring
and configuration operations.
The equipment control system functions are provided by the software resident in the
Communication and Control Unit fully supporting the Information model (*).
The Control Application can be:
n the Local Craft Terminal (LCT): it is a software application running on a personal computer
(based on MS Windows operating system) with a serial connection to the equipment.
n Plug-in: it is a software application, part of the Element Manager program, running on a HP
server (based on Unix operating system) able to offer a Graphical User Interface for
controlling the equipment.
339-1268/06
Navigation Page
Book Contents
SYSTEM ARCHITECTURE
Local Craft Terminal: Local Connection
It can control the equipment via a local connection.
The dialogue between the Control Application and the controlled Network Element (see Fig. 1) is
based on a F-Interface with transport protocol fully supporting the information model and based on
V.24 interface (RS232 link).
339-1268/06
Navigation Page
16
Book Contents
Control Application
PERSONAL
COMPUTER
LAN
Control Application
software
NE
F Interface
Q Interface
NE
DCC
DCC
NE
NE
DCC
DCC
NE
Fig. 2 Remote
Control
using
the
Control
Application (Ring Network example)
339-1268/06
Navigation Page
17
Book Contents
HP SERVER
CORE
EM-IMO
Plug-in
EM-11C
Plug-in
EM-xx
Plug-in
DCN
DXC
ADM
DXC
ADM
xx
NE
Fig. 3 Centralized
Manager
xx
NE
Control
using
the
Element
For information regarding the installation and process description refer to the Element Manager
manual.
Refer To:
ServiceOn Optical Element Manager Manual
339-1268/06
Navigation Page
18
Book Contents
SOFTWARE FEATURES
The following functions are performed by the Control Application.
Unit Management
Manages for each electronic Unit the following functions:
n Configuration Management;
n Active Alarm Report;
n Performance Management;
n Utilities.
Access Management
It manages the following functionality:
n Operator Access Rights [LC];
n Equipment Password Management [LC].
339-1268/06
Navigation Page
19
Book Contents
Network address management enables the management of network addresses (NSAP address)
used to control the SDH network via a NMC (Network Management Centre).
Date and time configuration sets the equipment date and time.
Maintenance Management
Groups together all sub-applications for the management of:
n Software Download [LC];
n Performance Monitoring;
n General Functions.
Software download downloads from the Control Application computer the new releases of unit
application software.
Performance Monitoring initiates a performance data collection on different monitored entities.
General Functions facility to obtain the Software Version or Inventory Data Information from each
unit.
Fault Management
Fault management functions:
n Event Reports Listing.
Event reports listing can display the content of the Equipment Alarm Log and Event Log databases.
SYSTEM COMPOSITION
The information regarding the Element Manager can be found in the relevant manual while those
regarding the LCT application are given in the following.
Refer To:
ServiceOn Optical Element Manager Manual
339-1268/06
Navigation Page
20
Book Contents
DCE
1
2
3
4
5
6
7
(*) 1
2
Rx
3
Tx
(*) 4
GND
5
(*) 6
(*) 7
(*) 8
(*) 9
(*)
Tx
Rx
(*)
GND
(*)
(*)
8 (*)
9 (*)
Equipment
1
2
3
4
5
6
7
8
9
PC
(*) not used
DTE
DCE
1
2
3
4
5
6
7
(*) 1
2
Tx
3
Rx
(*) 4
GND
5
(*) 6
(*) 7
(*) 8
(*) 9
(*)
Tx
Rx
(*)
GND
(*)
(*)
8 (*)
9 (*)
Equipment
(*)
Navigation Page
25
PC
339-1268/06
1
2
3
4
5
6
7
8
9
10
Book Contents
DTE
SOFTWARE INSTALLATION
Before starting the software installation ensure that the DOS Operating System has been correctly
installed together with the Microsoft Windows program (or check the correct installation of
Windows 95 Operating System). For more information refer to the relevant handbooks.
Follow the procedure clicking on the Next button. The procedure is self-explaining.
339-1268/06
Navigation Page
22
Book Contents
9600baud
F Interface
DCC
ADM-1
NE
STM-1
NE = ADM/REG-4/16/64
ADM-1 = MSH11 (old ADM equipment)
339-1268/06
Navigation Page
23
Book Contents
MAIN FUNCTIONS
There are seven main parts on the Control Application (CA) window: the Menu bar, the Title bar
(with the NSAP indication), the Tool bar, the Graphical area, the Alarm and Event monitor window,
the Progress bar and the Alarm Summary.
Menu Bar
Title Bar
Graphical Area
Tool Bar
Alarm Summary
To display a menu using a mouse, click the menu title on the menu bar. To close the menu, click
another part of the screen.
There are two ways to display a menu using the keyboard:
339-1268/06
Navigation Page
Book Contents
1.
Press <Alt> to activate the menu bar. Use the arrow keys to move to the menu title to
select and press <Enter>. To close a menu without selecting a command, press <Esc>.
2.
Press <Alt> plus the first letter of the menu title to display. Note that the first letter of
each menu title on the menu bar is underlined. Select the required command with the arrow
keys and press <Enter>. To close a menu without selecting a command, press <Esc>.
GRAPHICAL AREA
The graphical area is a representation of the equipment layout.
Note
(ADM-4) / (ADM-16)
If the equipment has been configured as regenerator the Tributary and Switch Unit are
not accessible (the relevant slots are displayed in light grey colour) furthermore several
command buttons (and the associated function) are not available.
The push buttons disabled are: Synchronisation Configuration, Cross Connection, MSP,
MS-SPRing Configuration and Card Protection.
All the units are displayed, the colour of the unit is the status indication:
Colour
Status
Red
Yellow
Failed
Maintenance
(only for Communication and Control Unit)
Dark grey
Configured
Light grey
Not Configured
A configured unit is displayed in dark grey, a fitted but not configured card is displayed in light grey.
339-1268/06
Navigation Page
26
Book Contents
If a wrong card is inserted according to the configured card, it is drawn in a red colour.
If a unit is configured and it is not inserted in the sub-rack, it is drawn outside the sub-rack.
On the top of each unit there is a LED that becomes red when one or more alarms are detected
inside the unit.
ALARM SUMMARY
The Alarm Summary allows to display the summarising alarms for the equipment.
The indications are:
339-1268/06
Navigation Page
27
Book Contents
(ADM-64)
For the ADM-64 instead of the MEM indication is present the MEM/PARK indication.
When after an alarm acknowledge operation the indication becomes MEM, when the
parking mode is activated the indication becomes PARK.
By clicking with the right mouse button, next to the Alarm Summary and Alarm and Event Monitor
Window area, the following commands will be available: Active Alarms, Acknowledge, Clear
Window Alarms, Realign Shelf.
The Active Alarms item allows to display a summary of the active alarms.
The Acknowledge can be used as the alarm memorisation push button present on the physical
EOS (End of Shelf Unit). By selecting this item the alarm conditions are acknowledged; all the active
alarm lamps are switched off and the MEM LED lights on.
The Clear Window Alarms can be used to erase the alarm/event displayed in the Alarm and Event
Monitor Window, to perform a general refresh select the Realign Shelf item.
The ABN (Abnormal) LED lights on when:
n an internal loopback is activated;
n a "lockout of protection" or "forced switch" is activated on the MSP;
n LOS at booster and preamplifier input interface;
n the optical protection function is disabled or the laser is forced off (*).
Note(*)
The ABN optical indication activated in case of optical protection function disabled or
laser forced off can be inhibited via software.
See Also:
Specific Functions: Laser Configuration
TOOL BAR
The Tool bar is a bar of command buttons for reaching in a faster way the main functionalities of the
Control Application software.
By stopping the mouse pointer on a command button for a few seconds, a pop-up menu will appear,
indicating the main functionality that can be activated by using the selected button (as shown in the
following example).
339-1268/06
Navigation Page
28
Book Contents
Note
Before the connection with the equipment this button allows the communication
parameters set up (i.e. serial port used)
Exit Button
Used to exit from the Control Application.
(as after the selection of File ->Exit from the main menu).
By clicking on the button, when the operator is not logged in, a Login window, with user name and
password request, will appear, to log in either the local or remote equipment.
By clicking on the button, when the operator is already logged in, you are logged out from the
connected equipment.
(as selecting File->Logout from the main menu).
339-1268/06
Navigation Page
29
Book Contents
Performance Button
This button is used to visualise the equipment performances.
Help Button
This button is used to accesses the Control Application help.
339-1268/06
Navigation Page
30
Book Contents
Note
The Port Label information is displayed only when this option is enabled otherwise
the Unit information will take place.
By clicking with the right mouse button, next to the Alarm Summary and Alarm and Event Monitor
Window area, the following commands will be available: Active Alarms, Acknowledge, Clear
Window Alarms, Realign Shelf.
The Clear Window Alarms item can be used to erase the alarm/event displayed in the Alarm and
Event Monitor window.
The Acknowledge item is used to store the active alarms.
Using the Active Alarms item only the active alarms will be displayed in the alarm and event
monitor window, to perform a general refresh select the Realign Shelf item
PROGRESS BAR
The progress bar is divided into three different areas from left to right:
n send/receive message counter indicating the number of messages sent to the equipment
and received from the equipment by the Control Application;
n procedure in progress indicating the string of the current procedure carried out by the
equipment;
n percentage of procedure completion indicating the percentage number of the current
procedure carried out by the equipment.
339-1268/06
Navigation Page
31
Book Contents
Local Access
To perform a local access:
* Select Local Access in the access mode.
* Select the user type and insert the password.
* Confirm by clicking the OK button.
Once the operator has confirmed his login operation, in case of a Write or Administrator user, the
access to the equipment is enabled and the light on the Operator Access button becomes green. In
case of a Read user the access is enabled but no modifications are allowed. Light on the Operator
Access button is yellow. In the case of a login failure the light will be red.
339-1268/06
Navigation Page
Book Contents
Remote Access
To perform a remote access:
* Select Remote Access in the Access mode.
* Select the remote node NSAP by using the Enter Remote NSAP scroll list.
* Select the user type and insert the password.
* Confirm by clicking on the OK button.
A node can be added by clicking on the Add Node button. Then in the Add Node window the
operator has to insert the NSAP address and an identifier of the node.
By clicking on the Delete Node button and selecting a node in the list, the operator can remove the
node.
The Edit Node button is used to change the name or the NSAP address of an existing node.
See Also:
Logout, Change Password
LOGOUT
Path (File -> Logout) [LC]
Selecting the Login item the user closes his connection to the equipment.
The light on the Operator Access button becomes red.
See Also:
Local Craft Terminal: Remote Login, Change Password
EXIT
Path (File -> Exit)
By selecting the Exit item the operator exits the Control Application software.
LC SETTINGS
Path (File -> LC settings)
By selecting the Lc Settings menu item (File main menu), the User Settings window will become
accessible.
General Settings
Path (File -> Lc Settings -> General)
This folder is used to enable the label operations and to configure the Control Application language.
General folder by clicking on the General button in the upper part of the User Settings window.
339-1268/06
Navigation Page
34
Book Contents
339-1268/06
Navigation Page
35
Book Contents
For changing the Control Application language, the proper file (containing all the local
controller strings in the required language) must be present in the local controller
directory.
See Also:
Label Operations Configuration (ADM), Termination Point Labels (ADM), Specific
Functions: Channels - STM-n Units/WDM STM-16/DWDM STM-16/METRO STM16/DWDM STM-64, Specific Functions: Channels - nx140/155Mbit/s Tributary Units
(ADM)
Alarm Settings
Path (File -> Lc Settings -> Alarm Settings)
This folder is used to enable or disable the notification of some alarm in real time monitor window.
* Select the Alarm Settings folder by clicking on the relevant button in the upper part of
the User Settings window.
* Enable the alarm notification function by checking the relevant check buttons.
* Confirm the settings by clicking on the Apply push button.
Alarm Colours
Path (File -> Lc Settings -> Alarm Colours)
This folder is used to change alarm message colour in real time monitor window.
* Select the Alarm Colours folder by clicking on the relevant button in the upper part of the
User Settings window.
339-1268/06
Navigation Page
36
Book Contents
Any alarm message can be displayed, in alarm and event monitor window, with a custom colour,
this in accordance to the alarm category.
The categories are:
n urgent alarm;
n not urgent alarm;
n indicative alarm;
n not defined alarm (indicated by ------);
n alarm status cleared.
339-1268/06
Navigation Page
37
Book Contents
CHANGE PASSWORD
Path (Security -> Change Password) [LC]
Selecting the Change Password item the Supervisor user can modify his password and the
password of the Write user, while the write user is only allowed to change his own password.
339-1268/06
Navigation Page
38
Book Contents
* Set the name of the equipment, by writing it into the System text field.
* Set any Additional information about the equipment (optional).
* Set the version of the equipment, by writing it into the Version text field (optional).
* When the path trace bytes (J0, J1 and C2) and any SOH bytes are not used, it is possible
to set their value to all 0 or all 1 by checking the relevant radio button Fixed to 0 value
or Fixed to 1 value.
* Set the system date and time, using the relevant spinners.
Two buttons are available for extracting the date and time from the computer (Set to
Computer time) or from the equipment (Request from shelf).
* Click on the Apply button to validate the new configuration parameters.
339-1268/06
Navigation Page
Book Contents
* Input the NSAP address, by writing it into the relevant text field (20 bytes in hexadecimal
code).
* Define whether the system is used as a Level 1 Intermediate System or as a Level 2
Intermediate System (for routing purposes), by checking the relevant radio button.
* Enable the use of Ethernet, by checking the relevant check box Enabled (this option is
used to enable the use of Q interface).
* Introduce the MAC address of the equipment, by writing it into the relevant text field (6
bytes in hexadecimal code).
* Define the size of packets (in bytes) used on the DCC link.
* Define the size of packets (in bytes) used on the ethernet link.
* Click on the Apply button to validate the new configuration parameters.
* Use the Restart button to force the start-up of the communication protocol.
339-1268/06
Navigation Page
41
Book Contents
This function is used to enable the use of DCC and to configure their parameters (DCC side and
status).
339-1268/06
Navigation Page
42
Book Contents
339-1268/06
Navigation Page
43
Book Contents
* Select the Files Upload folder by clicking on the Files button in the upper part of the NE
Installation window.
The Routing Tables are only available when the NE is equipped with a
Communication and Control Unit Type D.
* Select the Routing Tables folder by clicking on the Files button in the upper part of the
NE Installation window.
339-1268/06
Navigation Page
44
Book Contents
If the equipment is configured as Level 1 Intermediate System only the Level 1routing tables are
available, while if it is configured as Level 2 Intermediate System both Level 1 and Level 2 routing
tables are available.
* Press Read Local Routing Tables (level 1) to view the values for this level.
The fields for the Local Routing Tables (level 1) are listed in the following:
SystemID: it displays the NE identifier reachable from the route;
NextHopSysId: it displays the NE identifier of the next hop;
Port: it indicates the type of circuit used for the routing (DCC or Ethernet);
DccIdentifier: It indicates the slot number and the port that recognises the connection.
(This field will be empty if the circuit is Ethernet).
MacAddress: it contains the SNAP (Sub Network Point Attachment) in case of the connection is via
Ethernet, otherwise it is empty (via DCC);
Lev2Capability: it displays if the Network Element is able to perform a level 2 routing;
Entry: this field indicates if the next hop is manual, virtual, IS-IS (Intermediate System) or ES-IS
(End System);
Metric: this field contains the global cost of the route.
* Press Read Area Routing Tables (level 2) to view the values for this level.
The fields for the Local Routing Tables (level 2) are listed in the following:
Area Prefix Len: this field indicates the length of the area prefix;
Area Prefix: it indicates the value of the reachable areas prefixes:
NextHopSysId: it displays the NE identifier of the next hop;
339-1268/06
Navigation Page
45
Book Contents
Port: it indicates the type of circuit used for the routing (DCC or Ethernet);
CircuitID: it indicates the slot number and the port that recognises the connection.
(This field will be empty if the circuit is Ethernet).
MacAddress: it contains the SNAP (Sub Network Point Attachment) in case of the connection is via
Ethernet, otherwise it is empty (via DCC);
Entry: it indicates if the next hop is manual, virtual, IS-IS (Intermediate System) or ES-IS (End
System);
Metric:it contains the global cost of the route.
* Press Export to save the routing tables data on a file on the PC.
In the Cross Connection window there are two fields (From and To) with the currently selected
elements to be connected and the protection information field (Protection).
When a channel is selected the push buttons relevant to the possible options will appear under the
protection information field.
339-1268/06
Navigation Page
46
Book Contents
To refresh the Cross Connections status of a specific unit (either line or tributary), click on the Slot
button, allocated below each tributary channel list, to perform a global refresh click on the Request
push button.
See Also:
Cross Connections: Bidirectional, Cross Connections: Drop and Continue (ADM-4)
(ADM-16), Cross Connections: Concatenated, Cross Connections: Loopback, Cross
Connections: SNC Protection Configuration, Cross Connections: SNC Protection
Switch, Cross Connections: Unidirectional, How to Create a Cross connection, Cross
Connections: Path Info
When the MS-SPRing is active, the protected channels can be multiplied and if the
Extra Traffic option has been selected it is also possible to multiply the channels used
as protection.
To explode an AU-4, a TU-3 or a TU-2 into its lower order components (down to
TU-12 level):
* Select an AU-4, a TU-3 or a TU-2 in a STM-1 frame by double clicking on it.
* Click on the Mul. TU12 (Multiply TU12) push button to split the selected element into its
lower level components (TUG-3s, TUG-2s and TU-12s for the AU-4, TUG-2s and TU-12s
for the TU-3, TU-12s for the TU-2).
Note
To deselect a channel the operator can double click again on it or click on the Cancel
push button.
339-1268/06
Navigation Page
47
Book Contents
To explode an AU-4 or a TU-3 into its lower order components (down to TU-2
level):
* Select an AU-4 or a TU-3 in a STM-1 frame by double clicking on it.
* Click on the Mul. TU2 (Multiply TU2) button to split the selected element into its lower
level components (TU-3s and TU-2s for the AU-4, TU-2s for the TU-3).
339-1268/06
Navigation Page
48
Book Contents
See Also:
Cross Connections: Bidirectional, Cross Connections: Loopback Cross Connections:
Drop and Continue (ADM-4) (ADM-16), , Cross Connections: SNC Protection
Configuration, Cross Connections: SNC Protection Switch, Cross Connections:
Unidirectional, How to Create a Cross connection
339-1268/06
Navigation Page
49
Book Contents
339-1268/06
Navigation Page
50
Book Contents
* Select the first channel to cross connect (Master), by double clicking on it.
The selected channel will be displayed in a red colour, and the channel indication will
appear in the From box.
* Select the leg channels to cross connect, by double clicking on them.
The selected channels will be displayed in red colour, and the channel indication will
appear in the To box.
Note
After these operations the cross connected channels will be displayed in green and they will show
the symbol - to indicate that they are connected to another channel.
Modify push button is displayed when a broadcast cross connection is selected and allows to add
or disconnect leg channels.
339-1268/06
Navigation Page
51
Book Contents
339-1268/06
Navigation Page
52
Book Contents
In the example the protected channel is the slot 11 channel n. 1-2-1. In normal conditions, it
receives data from Slot 1 channel n. 1-3-4; in case of failure, it receives data from Slot 6 channel n.
1-1-5.
* Click the OK button and the Cancel button in the Set Protection Data for Drop &
Continue window.
In the Cross Connection window, the protection channel is displayed in a dark green and the
channels directly involved in the drop & continue cross connection, show the symbol ^.
339-1268/06
Navigation Page
53
Book Contents
339-1268/06
Navigation Page
54
Book Contents
Note
This must be set also into the intermediate node where the AU4 channel is cross connected in
passing-through mode.
The node identification number must be univocal, consecutive and defined following the East to
West directionality as shown in the figure below.
The Routing Path information is not managed yet.
E
W
1
W
2
5
E
W
3
E
Sequence
1
2
3
4
5
E
W
See Also:
Cross Connections: Bidirectional, Cross Connections: Unidirectional, How to Create
a Cross connection
339-1268/06
Navigation Page
55
Book Contents
* Create a bidirectional cross connection between the selected channels, by clicking on the
Bidir button. After these operations the cross connected channels will be displayed in
green and they will show the symbol - to indicate they are connected to another
channel.
To remove this cross connection double click on one of the two channels and click on the Yes
button in the confirmation window that will be displayed. To remove a cross-connections is also
possible to click on one of the channels, press the DEL CC button and confirm the operation by
pressing the Yes button in the confirmation window that will appear.
339-1268/06
Navigation Page
56
Book Contents
The protection units, in Equipment protection, are not accessible in the Cross Connection window
and are displayed with a proper indication.
The protection units, in MSP, are not accessible in the Cross Connection window and are displayed
with a proper indication.
If the Extra Traffic option is disabled, the protection units, in MS-SPRing, are not accessible in the
Cross Connection window and are displayed with a proper indication, while if the Extra Traffic is
active, the relevant channels can be cross connected; this condition is indicated by the letter E.
339-1268/06
Navigation Page
57
Book Contents
See Also:
Cross Connections: Bidirectional, Cross Connections: Loopback, Cross
Connections: Multiply SDH Frame (ADM-4), Cross Connections: SNC Protection
Configuration, Cross Connections: SNC Protection Switch, Cross Connections:
Unidirectional
339-1268/06
Navigation Page
58
Book Contents
* Select if the protection is revertive or not, by checking the relevant radio button.
* For a revertive protection, set also the Wait to Restore time (from 0.5 to 30.0 minutes),
using the relevant spinner.
This time is expressed in minutes and represents the time waited by the system before switching
back to the protected channel, once it returns available.
* Set the Holdoff time (from 0.0 to 20.0 seconds), which is the time waited by the system
before triggering the protection.
If the selected channel is an AU-4 it is also possible to set the parameters concerning the SNCP
Inherent or Not intrusive.
* Set Inherent or Not-intrusive SNC protection, by clicking on the relevant radio button.
* If the Not-intrusive selection is done, you can also enable the detection of EXC, TIM and
SD alarms as switching criteria by clicking on the corresponding check boxes.
Note
Note
A red cross indicates that both channels (protection and protected) are faulty; in this
case the Current State indicates the message: SF Switch Pend (Switch Pend due
a Signal Failure).
IMPORTANT The SNCP/N can be managed only if the involved AU-4 channels have
previously been set with the monitor enabled.
In the Cross Connections window the protecting channel will be displayed in a darker green.
After selecting a protected cross connection, the operator can modify the protection parameters, by
clicking on the Protection button. The Protection Setting window will be displayed.
339-1268/06
Navigation Page
59
Book Contents
For a Revertive SNC protection the Manual Switch to the Protected slot is not
available.
When the Protecting slot is not available, the right Manual switch button is not
accessible.
For a Revertive SNC protection the Forced Switch to the Protected slot is not
available.
Note
When the Protecting slot is not available, the right Forced switch button is not
accessible.
339-1268/06
Navigation Page
60
Book Contents
* Click on the Swap Ports button to invert the roles in the protection scheme. The
protection channel will become the protected one and vice versa.
* Define if the ACT is Generate, Terminate or Disabled using the Sauts scroll list.
* When the ACT is generated, define the sent value of path trace, on byte J1 (select it with
the pull down menu into the J1 Path Trace Send field).
* When the ACT is terminate, define the expected value of path trace, on byte J1 (select it
with the pull down menu into the J1 Path Trace Expected field).
339-1268/06
Navigation Page
61
Book Contents
For the expected and sent value of J1 path trace, five different configurations can be selected:
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters
E164 Hex View
The path trace is represented as a string of fifteen Hexadecimal characters
Blank Fill
The path trace is represented as a string of blanks
Zero Fill
The path trace is represented as a string of all zeros
Disable
The path trace management is not used
In the upper part of this window, in the Tp Label scroll list, the different tributary and line ports are
listed by using their labels. If no labels have been previously entered (by using the Channels item in
the Unit menus or the Tp Labels item in the Configuration menu), the ports will be displayed with
their default name. The klm scroll list indicates, in case of STM-n ports, the selectable channels by
using the SDH standard channel numbering.
The Details area provides additional information regarding the selected port. The Int Synch text
field indicates if the port is used or not as system synchronisation source, the Ext Synch text field
shows if the port is configured as external output synchronisation source and the DCC field is used
when a data communication channel of the selected STM-n port is unlocked.
In the rightmost part of the window, the Cross Connection area contains all fields and push buttons
for performing connections.
339-1268/06
Navigation Page
62
Book Contents
In the middle of the window, the Performances area contains the push buttons to activate and setup the collection of information quality data of the selected port.
The DCC management and the synchronisation sources configuration can be performed by using
the relevant push buttons present in the centre of the window, as described in the following.
When a channel is selected the push buttons relevant to the possible options will appear.
See Also:
Termination Point Labels (ADM)
NOTICE
Once an element of SDH frame is split into its lower elements, these are still available in some
eventual future access to the Cross Connection or to the Labels Operations windows.
See Also:
Cross Connections: Multiply SDH Frame (ADM-4)
339-1268/06
Navigation Page
63
Book Contents
* Click on the > button of the To field to confirm the selection. The selected channel will
be displayed in the relevant field.
* Create the cross connection by clicking on:
Unidir. push button
to create a unidirectional cross connection
Bidir. push button
to create a bidirectional cross connection
Broad. push button
to create a broadcast cross connection (with one leg channel)
If the operator want to create a broadcast cross connection with n leg channels, he will have to
repeat n times steps 3 and 4, before clicking on the Broad. push button.
See Also:
Cross Connections: Bidirectional, Cross Connections: Unidirectional, Cross
Connections: Broadcast
339-1268/06
Navigation Page
64
Book Contents
See Also:
Cross Connections: Broadcast, Cross Connections: Drop and Continue (ADM-4)
(ADM-16)
339-1268/06
Navigation Page
65
Book Contents
339-1268/06
Navigation Page
66
Book Contents
339-1268/06
Navigation Page
67
Book Contents
339-1268/06
Navigation Page
68
Book Contents
* Select the protection type, by checking the relevant radio button (1:N Protection or 1+1
Protection).
* Select the unit to act as working, by clicking on it in the relevant list.
* Click on the Worker button. The selected unit will be displayed in the Worker list.
* Define the worker channel Priority by means of the relevant scroll list (in case of 1:N
Protection only).
Note
Note
Note
The operator has to control that on the worker leg a Multiplex Section DCC is enabled
and that on the protection leg a Multiplex Section DCC can be enabled or is already
enabled.
* Define whether or not the protection is Bidirectional, by checking the relevant check box.
Two Undo buttons, one for Worker units and the other for Protection ones, can be used to cancel
the relevant selection operations.
If the use of extra traffic has been selected, also the protection line will be available in the Cross
Connection window. This allows the insertion of lower priority traffic (Extra Traffic) on the protection
line.
See Also:
MSP Switch Operations (ADM), Specific Functions: MSP Protection (ADM)
339-1268/06
Navigation Page
69
Book Contents
339-1268/06
Navigation Page
70
Book Contents
Worker: slot 1
Protection: slot 3
1:2
Protection: slot 3
1:3
Protection: slot 3
1:4
Protection: slot 3
1:1
Worker: slot 6
Protection: slot 8
1:2
Protection: slot 8
1:3
Protection: slot 8
1:4
Protection: slot 8
Group 2
339-1268/06
Navigation Page
71
Book Contents
By selecting this item, the Create New Equipment Protection window becomes accessible.
339-1268/06
Navigation Page
72
Book Contents
See Also:
Specific Functions: Equipment Protection (ADM)
If the equipment has been configured as regenerator this function is disabled and the
system works in through timing mode.
The main element of this window is a list of synchronisation sources used by the equipment, with
their quality level, their priority, their status and their bit error rate enable (Ena) /disable (Dis) /not
supported (---) status.
339-1268/06
Navigation Page
73
Book Contents
When the in use synchronisation source fails, the equipment will switch on the available source with
the highest priority. If the quality management is enabled, the highest quality source is always the in
use one (on two sources with the same quality the choice is done on the basis of their priority).
Note
(ADM-4) / (ADM-16)
The type of matrix used by the equipment limits the number of synchronisation sources configurable
for a card.
(ADM-4)
If the ADM-4 uses a Switch Unit Type A (XILINX matrix), only one synchronisation
source can be configured for each card. This source can be configured only on port n.1,
except for PDH cards and for the 2x140/155Mbit/s Tributary Unit (port n.1 or port n.2 can
be configured indifferently).
If the ADM-4 uses a Switch Unit Type B (TIMEX ASIC matrix), the operator can
configure up to two synchronisation sources for each card, except for the
2x140/155Mbit/s Tributary Unit. For this card only one synchronisation source can be
configured, choosing between port n.1 and port n.2.
(ADM-16)
If the ADM-16 uses a Switch Unit Type A (XILINX matrix), only one synchronisation
source can be configured for each card. This source can be configured only on port n.1,
except for the 2x140/155Mbit/s Tributary Unit (port n.1 or port n.2 can be configured
indifferently) and for 4x140/155Mbit/s Tributary Unit (port n.1 or port n.3 can be
configured indifferently). It is impossible to configure sources on slots n. 7, 9, and 10.
If the ADM-16 uses a Switch Unit Type B (TIMEX ASIC matrix), the operator can
configure up to two synchronisation sources for each card, except for the
2x140/155Mbit/s Tributary Unit. For this card only one synchronisation source can be
configured, choosing between port n.1 and port n.2. For the 4x140/155Mbit/s Tributary
Unit the operator can configure up to two synchronisation sources, choosing one source
between port n.1 and port n.3 and the other source between port n.2 and port n.4. It is
possible to configure sources on each slot.
339-1268/06
Navigation Page
74
Book Contents
* Select the unit (or external clock reference) to be used as a synchronisation source, by
clicking on it in the relevant list.
When an STM-n unit is selected as a synchronisation source, the quality information cannot be
defined, since the system uses only the content of S1 byte, but deselecting the Do not overwrite
box the quality can be changed by the user.
* Select the synchronisation source, by clicking on it in the relevant list.
* Select the quality level to be assigned to the synchronisation source, by clicking on it in
the Quality scroll list. The following quality levels can be selected:
G811 (PRC)
Primary Reference Clock
G812 Transit (SSUT)
Synchronisation Supply Clock Transit
G812 Local (SSUL)
Synchronisation Supply Clock Local
G813 (SEC)
SDH Equipment Clock
DNU
Do Not Use
This field is only available for external synchronisation sources or for synchronisation sources based
on signals received from systems which can not manage S1 byte or when the Do not overwrite
option has been deselected.
* Select the Priority of the synchronisation source, by using the relevant spinner.
* Check the EXC Enable, for enabling the change-over function in case of excessive bit
error rate detected on the synchronisation source.
This field is not available for the 2MHz and 2Mbit/s not CRC framed inputs and PDH
140Mbit/s sources.
* Confirm the settings by clicking on the OK button.
339-1268/06
Navigation Page
75
Book Contents
The quality information cannot be set on STM-n units if the Do not overwrite is selected.
* Select the new value for the quality level, by using the Quality scroll list.
* Select the new value for the priority, by using the Priority scroll list.
* Check the EXC Enable, for enabling the change-over function in case of excessive bit
error rate detected on the synchronisation source.
* Confirm the new settings, by clicking on the OK button.
339-1268/06
Navigation Page
76
Book Contents
339-1268/06
Navigation Page
77
Book Contents
These folders are used to manage the synchronisation sources sent as clock reference outputs by
the equipment.
IMPORTANT (ADM-4) / (ADM-16)
If the equipment uses a Switch Unit Type B (TIMEX ASIC matrix), both Ext out #1 and
Ext Out #2 can be set. If the equipment uses a Switch Unit Type A (XILINX matrix), only
Ext out #1 can be set.
By clicking on the Ext out button, on the top of the Synchronisation window, the Ext Out
Synchronisation folder becomes accessible.
The main element of this window is a list of synchronisation outputs supplied by the equipment, with
their quality level and their priority.
339-1268/06
Navigation Page
78
Book Contents
The output can be selected between the internal source or an external SDH source.
The type of matrix used by the equipment limits the number of synchronisation sources configurable
for a card (refer to System Synchronisation Sources).
For selecting the internal source click on the System button.
When the System mode is selected, the output will be locked to the internal clock used by the
equipment (the possible sources in the list are not used).
For selecting the external source click on the External button.
When the External mode is selected, the output will be locked to the best source available in the list
(the Internal Source is not used).
When the active synchronisation output fails, the equipment switches to the available output source
with the highest priority.
Note
In the Ext Out #1/ Ext Out #2, an indication about the current state of the
synchronisation output (squelched or not) is present. When the output is squelched a
red cross is displayed on the current state symbol.
Current State
Indication
This field is only available for external synchronisation sources or for synchronisation sources based
on signals received from units which can not manage S1 byte or when the Do not overwrite option
has been deselected.
* Select the priority of the synchronisation output, by using the Priority scroll list.
339-1268/06
Navigation Page
79
Book Contents
* Check the EXC Enable, for enabling the change-over function in case of excessive bit
error rate detected on the synchronisation source.
This field is not available for the 2MHz and 2Mbit/s not CRC framed inputs and PDH 140Mbit/s
sources.
* Confirm the settings by clicking on the OK button.
339-1268/06
Navigation Page
80
Book Contents
339-1268/06
Navigation Page
81
Book Contents
339-1268/06
Navigation Page
82
Book Contents
This folder is used to manage the synchronisation source quality sent as clock reference outputs by
the equipment.
By selecting the Output Quality folder, on the top of the Synchronisation window, the Output
Quality folder becomes accessible.
GROUND CONTACTS
Path (Configuration -> Ground Contacts)
When the Ground Contacts window is selected, different pictures can be displayed according to
the ground contact configuration and to the Connection Unit equipped.
The two possible configurations are able to manage either 32 single wire output ground contacts or
11 double wire output loop contacts.
Each contact can be configured associating parameters, such as the alarm which activate it or the
logical state.
The window also gives access to the parameters associated to 4 input ground contacts.
339-1268/06
Navigation Page
83
Book Contents
The Location name shows the number of the pin used on the physical connector by default, for the
selected ground contact, but can be also customised by the user.
* Define the Severity of the alarm, by checking the relevant radio button (Urgent, Noturgent, etc.).
* Select the Alarm causes necessary to activate the output contact, by selecting them in
the relevant scroll list.
339-1268/06
Navigation Page
84
Book Contents
* Select from the relevant scroll list the Alarm sources, to which the output contact will be
associated.
* Define the Alarm kind, by checking the relevant radio button (INT, EXT, etc.).
* Define whether the output contact is active when connected to ground (active high) or not
(active low), by checking the relevant Polarity radio button.
* Confirm the settings by clicking the OK button.
Note
When check box Disable is active, no indication of alarm will be given by means of
the selected ground contacts. The disable ground contacts will be displayed in the
Ground Contacts window with a dark grey.
Acting on the Current State can modify the current state of the alarm.
Note
When in the Location name the output contact is followed by the indication HardWired, its settings cannot be modified.
339-1268/06
Navigation Page
85
Book Contents
The Location name shows the number of the pin used on the physical connector by default, for the
selected ground contact, but can be also customised by the user.
* Set the Additional information about the generated alarm, by writing into the relevant
text field.
* Set the type of Generated alarm, by using the relevant scroll list.
The alarm names present in the Generated alarm scroll list are the same configured in
the Ground Contact Alarm Name.
* Define whether the input contact is active when connected to ground (active high) or not
(active low), by checking the relevant Polarity radio button.
The Current state of the alarm, in this case, is read only.
These ground contact inputs are used to monitor environmental parameters (such as temperature,
humidity, etc.).
NOTICE
When some of the causes selected for a ground contact are active, the relevant
button in the Ground Contacts window will display a red colour, instead of the
default blue one. Further the contact will be shown as an opened or closed
switch according respectively to Active high or Active low Polarity selection.
See Also:
Specific Functions: Ground Contacts
MS-SPRING (ADM)
Path (Configuration -> MS-SPring)
By clicking on the MS-SPring item in the Configuration menu, the MS-SPRing Configuration
window becomes accessible.
This window gives access to Multiplex Section Shared Protection ring configuration functions.
Note
This protection requires the SS bits equal to Sdh (these bits can be set in the Port
Configuration window).
339-1268/06
Navigation Page
86
Book Contents
See Also:
MS-SPRing Configuration, MS-SPRing Cross Connection, Specific Functions: MSSPRing (ADM), Specific Functions: Channels - STM-n Units/WDM STM-16/DWDM
STM-16/METRO STM-16/DWDM STM-64, Specific Functions: Channels nx140/155Mbit/s Tributary Units (ADM)
MS-SPRing Configuration
Path (Configuration -> MS-SPRing -> Ring Config)
This folder is used to manage the MS-SPRing Protection. By clicking on the Ring Config. folder,
the ring configuration window becomes accessible.
* Define the MS-SPRing type: Two Fibres, Four Fibres,Two Fibre NUT or Four Fibres
NUT, by selcting it in the Protection Type scroll list.
* Define the local node identification number to be associated to the equipment by clicking
in the Node Id scroll list (every equipment involved in the MS-SPRing must have a node
identification number).
After this operation the local node number will be automatically displayed next to the Node Id field
and also included in the Ring Map.
Note
These numbers must be univocal but they can be chosen in a casual order.
* Define the Ring Map by inserting the node identification number of the neighbouring
nodes, for each node select the node number by clicking in the Ring List.
339-1268/06
Navigation Page
87
Book Contents
IMPORTANT The node identification numbers must be univocal, consecutive, and inserted in
the map list following a clockwise path. In other words, the last node number
inserted in the map list must be the first network element number in an
anticlockwise path.
For example, suppose that the network configuration is the following (W = west, E = east):
In the equipment with node number 1, the ring map list will be 1, 2, 3, 4, 5; in the equipment with
node number 2, the ring map list will be 2, 3, 4, 5, 1.
If a mistake occurs, select the node identification number in the ring map list and delete it using <<
Undo command button.
* Define whether the protection channel will be used to carry low priority traffic in MSSPRing (1:1 Protection) or not, by checking the relevant Extra Traffic check box.
Note
This time is expressed in minutes and represents the time waited by the system before switching
back to the original working path, once it returns available.
In case of 2 Fibres MS-SPRing:
* Select from the Line West field, the line card connected with the first node identification
number located in anticlockwise direction (West).
* Confirm it clicking on West Work/Prot>> command button.
* Select from the Line East field, the line card connected with the first node identification
number located in clockwise direction (East).
* Confirm it clicking on East Work/Prot>> command button.
If some mistake occurs, remove the MS-SPRing configuration using <<Undo Work/Prot command
button.
* Click on Apply button to enable the MS-SPRing configuration.
In case of 4 Fibres MS-SPRing:
* Select from the Line West field, the line card to act as worker connected with the first
node identification number located in anticlockwise direction (West).
339-1268/06
Navigation Page
88
Book Contents
To delete a MS-SPRing
* Click on a unit involved in the MS-SPRing, using the right button of the mouse.
* Select the MS-SPRing protection item in the unit menu, the MS-SPRing Configuration
window becomes accessible.
* Click on the Delete button.
See Also:
Cross Connections: Path Info, MS-SPRing Cross Connection, MS-SPRing NUT,
Specific Functions: MS-SPRing (ADM)
This folder displays for a selected AU-4 channel the Source and the Destination Node identification
numbers. Selecting the Cross Conn. folder, the Cross Connection window becomes accessible.
339-1268/06
Navigation Page
89
Book Contents
* Select an AU4 channel and its path information, if defined, are shown in Source Node
and Destin. Node fields.
The time slot interchange (TSI) information are not managed yet.
By using the Request button, the Cross Conn. window will be updated.
See Also:
Cross Connections: Path Info, MS-SPRing Configuration, MS-SPRing NUT, Specific
Functions: MS-SPRing (ADM)
MS-SPRing NUT
Path (Configuration -> MS-SPRing ->NUT)
This folder is used to manage the NUT and becomes accessible only if it has been configured a
MS-SPRing NUT type. Selecting the NUT folder, the NUT window becomes accessible.
339-1268/06
Navigation Page
90
Book Contents
* Click on the Create Nut button to configure the type of NUT and the Create NUT
window will be displayed.
* Select the NUT type in the scroll list and than click on the Apply button to confirm or the
Cancel button
After having configured the NUT type the Port NUT Info button becomes accessible.
* Select an AU-4 channel.
* Click on the Port NUT Info button and the Port NUT Info window will be displayed.
* Define the AU4 channel type, by clicking on it in the scroll list. The following channel
types can be selected:
339-1268/06
Navigation Page
91
Book Contents
Absent
The channel works normally
NUT Ring
The Ring Switchs are disabled on this channel while the Span Switchs are still enabled
NUT
The Ring and Span Switchs are disabled on this channel.
SOFTWARE INVENTORY
Path ( Inventory -> Shelf Inventory -> Inventory Data (SW))
This function is used to display the software versions loaded on both memory FLASH banks and the
software boot version loaded on the EPROM of the units present in the equipment.
For each unit the relevant slot is specified.
* Select the Inventory Data (SW) folder by clicking on the Inventory Data (SW) button in
the upper part of the Inventory window.
The Inventory Data (SW) window becomes accessible.
In Inventory window, information about the SW present in each slot are available.
Next to the software version present on the FLASH banks there is also an indication of the active
bank (*). To save the software inventory data on a file on the PC, click on Export button.
See Also:
339-1268/06
Navigation Page
92
Book Contents
Hardware Inventory
HARDWARE INVENTORY
Path (Inventory -> Shelf Inventory -> Inventory Data (HW))
This function is used to display the hardware versions of the units present in the equipment.
For each unit the relevant slot is specified.
* Select the Inventory Data (HW) folder by clicking on the Inventory Data (HW) button in
the upper part of the Inventory window.
The Inventory Data (HW) window becomes accessible.
In Inventory window, information about the HW present in each slot are available. To save the
hardware inventory data on a file on the PC, click on Export button.
See Also:
SoftwaRe Inventory
339-1268/06
Navigation Page
93
Book Contents
In this folder the units, with the relevant channels, are displayed. The fields can show that the
relevant unit channel is monitored (Mon), is using the HO Supervisory Unequipped (Hosu), is
involved in a Tandem Connection (Tandem), has a loopback (Loop), etc.
339-1268/06
Navigation Page
94
Book Contents
In this folder the units involved in a Tandem Connection are displayed. The Source field displays
the particular unit channel; the Matrix Side and Line Side display how the Tandem Connection has
been configured.
In this folder the units involved in a Equipment Protection are displayed. The window displays in
which slot there is the protected unit (Workers) and in which slot there is the protection unit (Prot.).
339-1268/06
Navigation Page
95
Book Contents
339-1268/06
Navigation Page
96
Book Contents
The Tp Labels (termination point labels) of the configured units can be added, modified or deleted
by using this window. The Resume button can be used whenever an update of the window is not
automatically performed.
339-1268/06
Navigation Page
97
Book Contents
TEST MODE
Path (Maintenance -> Maintenance / Service State)
By clicking on the Maintenance item, the Communication and Control Unit will be off-line. This
command will affect the Communication and Control Unit database and will not be forwarded to the
peripheral units.
When the Communication and Control Unit is in maintenance mode the yellow LED on its front
panel lights on and its graphical representation on the Control Application main window is yellow
highlighted.
To exit the Maintenance mode, select the Service option on the Communication and Control Unit
menu.
When the Service option is selected all the units will be reconfigured according to the new
configuration database (if any).
NOTICE
It is only allowed to add new configuration data to the existing database when
the Communication and Control Unit is in Maintenance mode. In the new
configuration you can add new data, but you can not neither delete the existing
ones nor replace them with other ones. The new configuration must be a
superset (or at least equal) of the previous one. In order to force a different
configuration it is necessary to perform a System Restart after the Service
mode (that will affect the traffic).
See Also:
Specific Functions: Maintenance/Service
SOFTWARE DOWNLOAD
Path (Maintenance -> Software Download) [LC]
This item is used to download the application software on the units (via local or remote login).
339-1268/06
Navigation Page
Book Contents
The Communication and Control Unit software is contained in a file bigger than 1.4Mbyte; for this
reason this file is split into two or three diskettes.
where X4xxxxxx.C3D is the destination file in which the source files will be merged.
IMPORTANT The destination file name must be the same of the Communication and Control
Unit one in the download.ini file.
* Remove the temporary files:
del X4xxxxxx.001
del X4xxxxxx.002
del *.EXE
* Move the program files from the temporary directory to the Control Applications
installation directory.
* Copy the download.ini file from the Control Applications installation disk, to the Control
Applications installation directory.
* Select the Software Download item in the Maintenance menu.
339-1268/06
Navigation Page
100
Book Contents
* Select the unit types to upgrade, by checking them in the available list.
* Start the download operation by clicking on the Start button.
Click on the Hide button to have the download operation performed in background mode (other
operations can be performed on the equipment while the software download takes place).
See Also:
Bank Switch, Common Functions: Bank Switch, Common Functions: Software
Commit, Software Commit
BANK SWITCH
Path (Maintenance -> Bank Switch)
This item is used to perform a bank switch, after a software download operation from the
Maintenance menu (a confirmation is required to the operator).
This operation, performed on all the upgraded units, consists in a change of the active FLASH
banks (the software download operation is performed on the inactive FLASH banks). A switch on
the old software version can not be performed using this item.
IMPORTANT After the completion of bank switch procedure on the Communication and
Control Unit, remember to exit Control Application and connect with new Control
Applications software.
See Also:
Common Functions: Bank Switch, Common Functions: Software Commit, Software
Download, Software Commit, Software Download
SOFTWARE COMMIT
Path (Maintenance -> Software Commit)
This item is used to validate a new software version, after a bank switch operation from the
Maintenance menu (a confirmation is required to the operator).
A FLASH bank with new loaded application software should be validated by means of this
operation, to confirm the new software version. If the software commit isn't executed, the new
software version can be used until an equipment switch off, a unit extraction, a unit reset or a
system restart happens; after these events the unit will switch on the old FLASH bank. A software
commit on the old software version can not be performed using this item.
See Also:
Bank Switch, Common Functions: Bank Switch, Common Functions: Software
Commit, Software Download
MIB RESET
Path (Maintenance -> MIB Reset)
By selecting the MIB Reset item in Maintenance menu, the equipment configuration database is
erased (after confirmation).
MIB UPLOAD
Path (Maintenance -> MIB Upload) [LC]
339-1268/06
Navigation Page
101
Book Contents
Before performing a cdl upload please check that all protections are in No
Request State. This means that no active alarms must be present on the NE.
SCRIPT EXECUTION
Path (Maintenance -> Execution of Scripts) [LC]
This item is used to execute CDL scripts, with predefined configuration sequences.
By selecting this item in the Maintenance menu, the CDL Interpreter window becomes accessible.
339-1268/06
Navigation Page
102
Book Contents
REALIGN SHELF
Path (Maintenance -> Realign Shelf)
With this menu, the operator can perform a refresh of all the equipment functions.
339-1268/06
Navigation Page
103
Book Contents
the Control Application behaviour: e.g. no unit extraction or alarm is detected in real time.
LOG SETUP
Path (Fault Management-> Alarm Log/Reporting -> Log Setup)
This option is used to enable the alarm/event report into a log file and to set the Log Full alarm
threshold. The alarm log file can contain a maximum number of 200 events and/or alarms. Using
the Log Full alarm threshold, the operator can set a threshold for the number of detected
events/alarms: when this threshold is exceeded, a Log Full alarm indication will be displayed.
339-1268/06
Navigation Page
104
Book Contents
This window contains all the settings for the log file implemented on the equipment.
LOG RECORDS
Path (Fault Management -> Alarm Log/Reporting -> Log Records)
339-1268/06
Navigation Page
105
Book Contents
Using this function the operator can view all the alarms/events stored by equipment in the log file.
IMPORTANT This will be available only if the Log Setup window in (Fault -> Alarm
Log/Reporting -> Log Setup) the Locked check box is not checked.
ALARM REPORTING
Path (Fault Management -> Alarm Log/Reporting -> Alarm Reporting)
Using this function the operator can view all the alarms which parameters has been modified and
can restore the default settings.
339-1268/06
Navigation Page
106
Book Contents
The alarm parameters relevant to a selected unit can be modified using the Alarm Severity common
function.
ALARM SEVERITY
Path (Fault Management -> Alarm Log/Reporting -> Alarm Severity)
Using this function the operator can view all the alarms which severity parameter has been modified
by the operator and can restore the default settings.
339-1268/06
Navigation Page
107
Book Contents
The alarm parameters relevant to a selected unit can be modified using the Alarm Severity common
function.
ACTIVE ALARMS
Path (Fault Management -> Active Alarms)
With this menu, the operator can delete all the inactive alarms/events present in the Alarm and
Event Monitoring window; on this window only the active alarms/events remain
339-1268/06
Navigation Page
108
Book Contents
UNIT FUNCTIONS
The unit functions are accessible by clicking on the units in the main window. Some functions are
common for every type of unit, some other are specific.
This function is present on every type of unit, except on the Communication and
Control Unit and on the End Of Shelf Unit.
If a unit is not configured it can be created by clicking on the unit itself, on the main window, and
selecting the item Create in the scroll menu.
339-1268/06
Navigation Page
Book Contents
All the available traffic interfaces that can be created are written in the following list:
ADM-64
STM-64 Opt
ADM-16
ADM-4
REG-64
STM-16 Opt
REG-4/16
STM-16
FOR X
Integrated WDM
STM-4 Opt
STM-1 Opt
STM-1 El
2xSTM-1 Opt
4xSTM-1 Opt
1x140/155Mbit/s
(VC-12) El
2x140/155Mbit/s
(VC-4) El
2x140/155Mbit/s
(VC-12) El
4x140/155Mbit/s
(VC-4) El
X
X
3x34/45Mbit/s
32x1,5/2Mbit/s
63x1,5/2Mbit/s
Booster +17
Preamplifier
2 Channel Bidir. X
WDM
339-1268/06
Navigation Page
110
Book Contents
ADM-64
ADM-16
Mux
Demux
for X
Integrated WDM
Splitter
Combiner
OSC X
Metro Filter
Gigabit Ethernet
Pre
&
EXT/INS
ADM-4
REG-64
REG-4/16
See Also:
Common Functions: Delete
339-1268/06
Navigation Page
111
Book Contents
In this window the operator can see the active alarms on the unit. The Refresh button can be used
whenever an update of the active alarms is not automatically performed.
See Also:
Alarm Log Reporting, Log Records, Log Setup
339-1268/06
Navigation Page
112
Book Contents
This function is present on every type of unit, except on the Communication and
Control Unit and on the End Of Shelf Unit.
When a unit is configured it can be deleted by clicking on the unit itself and selecting the Delete item
in the scroll menu.
To delete a unit:
* Click on the selected unit, using the right button of the mouse.
* Select the Delete item, in the unit menu.
See Also:
Common Functions: Create
339-1268/06
Navigation Page
113
Book Contents
In this window information about the HW (equipment code and serial number) and about the SW
(SW versions present in the boot EPROM and in the FLASH banks) are available.
Next to the SW version present on the FLASH banks there is also an indication of the in-use bank (it
is indicated with a check mark).
339-1268/06
Navigation Page
114
Book Contents
By clicking on the Communication and Control Unit on the main window and selecting the MIB
Upload item in the scroll menu, the equipment configuration database can be saved in a CDL file.
NOTICE
Before performing a cdl upload please check that all protections are in No
Request State. This means that no active alarms must be present on the NE.
339-1268/06
Navigation Page
115
Book Contents
339-1268/06
Navigation Page
116
Book Contents
* Deselect the Do not overwrite box and set the new quality in the relevant list.
* Confirm the new settings, by clicking on the Apply button.
See Also:
Synchronisation Output Quality (ADM)
Before performing any laser configuration please refer to the Safety Rules
handbook.
339-1268/06
Navigation Page
117
Book Contents
Aut. Rest. (2 sec after 300 sec) (Automatic Restart 300 seconds)
the laser is automatically re-activated for two seconds every 300 seconds
Laser on ABN on
the laser is forced on, the ABN led is switched on
Laser off ABN on
the laser is forced off, the ABN led is switched on
Laser off - ABN off
the laser is forced off, but no abnormal condition is displayed (the yellow LEDs on the optical unit
and the EOS remain OFF)
Laser on - ABN off
the laser is forced on, but no abnormal condition is displayed (the yellow LEDs on the optical unit
and the EOS remain OFF)
* If the selected optical unit is a NxSTM-1 Optical/Mux Unit, N folders (Laser1 to LaserN)
will be accessible in the Laser Configuration window.
* Click on the Apply button to confirm the latest configurations.
339-1268/06
Navigation Page
118
Book Contents
A list of the units belonging to the MSP Protection group is displayed in the upper part of the folder,
together with information relevant to their port identifier (MS#), the Protection Status (Local SF
Switch Pend, Auto Switch (SF), No Request, etc.), the State (Service or Stand-by) and the Priority
(it can be set for 1:N Protection).
* Change, if necessary, the protection settings in the relevant area (Revertive, Not
revertive, Bidirectional; Unidirectional protection is a default setting).
* If a Revertive protection was set, the operator can modify the Wait to Restore time,
using the relevant scroll list.
* Click the Apply button to confirm the latest configurations.
339-1268/06
Navigation Page
119
Book Contents
A list of the units belonging to the Equipment Protection group is displayed in the upper part of the
window, together with information relevant to the Protection Status (Local SF Switch Pend, Auto
Switch (SF), No Request, etc.) and the State (Service or Stand by).
339-1268/06
Navigation Page
120
Book Contents
339-1268/06
Navigation Page
121
Book Contents
Different commands are available for the two sides of the ring (West and East).
339-1268/06
Navigation Page
122
Book Contents
339-1268/06
Navigation Page
123
Book Contents
339-1268/06
Navigation Page
124
Book Contents
To delete a MS-SPRing:
* Click on the Delete command button to remove the MS-SPRing scheme.
See Also:
MS-SPRing Configuration, MS-SPRing Cross Connection, Section Status Info, MSSPRing NUT, West/East Info
West/East Info
In these fields are reported information concerning the local node section status.
If the local node status is Idle the card status west Working/Protection, east Working/Protection are
in No request status.
If the local node status is Bridged-Switched, Full pass-through or K Bytes pass-through in the
West/East Info area are reported information about the local node status causes:
n local or remote failure;
339-1268/06
Navigation Page
125
Book Contents
* Select an AU4 channel and its path information, if defined, are shown in Source Node
and Destin. Node fields.
The time slot interchange (TSI) information are not managed yet.
By using the Request button, the Cross Conn. window will be updated.
See Also:
Cross Connections: Path Info, MS-SPRing Configuration, Specific Functions: MSSPRing Manual Command/BSHR Status
339-1268/06
Navigation Page
126
Book Contents
* Click on the Create Nut button to configure the type of NUT and the Create NUT
window will be displayed.
* Select the NUT type in the scroll list and than click on the Apply button to confirm or the
Cancel button
After having configured the NUT type the Port NUT Info button becomes accessible.
* Select an AU-4 channel.
* Click on the Port NUT Info button and the Port NUT Info window will be displayed.
* Define the AU4 channel type, by clicking on it in the scroll list. The following channel
types can be selected:
Absent
The channel works normally
339-1268/06
Navigation Page
127
Book Contents
NUT Ring
The Ring Switchs are disabled on this channel while the Span Switchs are still enabled
NUT
The Ring and Span Switchs are disabled on this channel.
339-1268/06
Navigation Page
128
Book Contents
* For each port select the traffic type. When the port is used for Cross-Connections,
Synchronisation, DCC, etc., it is not possible to change its traffic type. In the relevant Port
field the radio buttons are shown in a grey colour and a string is shown to indicate the
current state of the port.
* Press OK to confirm.
See Also:
Common Functions: Create
LOOPBACK
Loopback connections are diagnostic tools used by the equipment to locate the fault on a specific
part of the network. By means of these loopbacks, after the detection of an alarm on a traffic unit,
the source of a fault can be isolated.
If the operator performs a loopback on an STM-N unit, he performs the loopback on all the N AU-4
of the STM-N unit. In this case the operator has to click on the relevant unit and select the
Channels item; in the General folder the Loopback button is available.
If the operator performs a loopback on a PDH unit he has to choose the port on which the loopback
will be performed. In this case the operator has to click on the relevant unit and select the Channels
item; in the resulting window the Loopback button is available and is related to the selected port.
Clicking on the Loopback push button, the Loopback window will be displayed.
339-1268/06
Navigation Page
129
Book Contents
FET
BET
FENT
BENT
UNIT
FET
BET
FENT
BENT
339-1268/06
Navigation Page
130
Book Contents
339-1268/06
Navigation Page
131
Book Contents
* Decide if the TC will be opened on matrix side or on line side and decide the role of the
selected channel.
The possible configurations are:
Disabled
the selected channel is not used for the Tandem Connection
Generate
the selected channel generates the Tandem Connection
Terminate
the selected channel terminates the Tandem Connection
Gen. + Term.
the selected channel generates and the terminates the Tandem Connection
Bidirectional
if the user want to create a Bidirectional Tandem Connection
Monitor
if the user want to create a monitor Tandem Connection
NOTICE
Not all the units, which manage the Tandem Connection, support the functionality on both sides. In
the following a detailed table is given:
UNIT
Term./gen.
Term./gen.
Matrix side
line side
Stm-16
Stm-4
339-1268/06
Navigation Page
132
Book Contents
1x140/155Mbit/s Electrical
1-2-4xStm-1 Optical
4x140/155Mbit/s
Check the relevant check boxes to enable one of these evaluation models.
* Define the expected, received and sent value of the TC access point identifier (the
operator can select it with the pool down menu into the Expected, Received and Send
field in the Identifier area).
For the expected, received and sent value of TC access point identifier, five different
configurations can be selected:
E164 Ascii View
the access point identifier is represented as a string of fifteen ASCII characters
E164 Hex View
the access point identifier is represented as a string of fifteen Hexadecimal characters
Blank Fill
the access point identifier is represented as a string of blanks
Zero Fill
the access point identifier is represented as a string of all zeros
Disabled
the access point identifier management is not used
339-1268/06
Navigation Page
133
Book Contents
The Optical folder shows read only information about the unit: the Optical Reach and the laser
Wave Freq Length. If the selected STM-n unit is an electric STM-1, the Optical Reach and the
Wave Freq Length fields are empty and the Optical Measure push button is not displayed.
The following options are only available for the STM-64 G.709:
* Configure the wavelength using the Wave Length Freq scroll list.
* Set the bit rate 9,9Gb/Sec or 10,7Gb/Sec using the relevant radio button.
339-1268/06
Navigation Page
134
Book Contents
Note
The 10,7Gb/Sec bit rate must be set to use the OOB FEC and the Digital Wrapper
functions.
* Select the Pilot Tone check box to enable the Pilot Tone.
This option can be used when the STM-64 is working in a WDM link with amplifiers which
use the pilot tones to recognise the number of the channels.
* Select the OOB FEC check box to enable the Out Of Band Forward Error Correction.
* Select the Digital Wrapper check box to enable this function.
When the Digital Wrapper is enabled the Optical Channel Transport and the Optical Channel
Data parameters become accessible.
* Define the expected value of SAPI (Source Access Point Identifier) for the OTU (Optical
channel Transport Unit), by the Sapi Expected pull down menu into the Opt. Channel
Transport field.
* Define the sent value of SAPI (Source Access Point Identifier) for the OTU (Optical
Transmission Unit), by the Sapi Sent pull down menu into the Opt. Channel Transport
field.
* Define the expected value of SAPI (Source Access Point Identifier) for the ODU (Optical
channel Data Unit), by the Sapi Expected pull down menu into the Opt. Channel Data
field.
* Define the sent value of SAPI (Source Access Point Identifier) for the ODU (Optical Data
Unit), by the Sapi Sent pull down menu into the Opt. Channel Data field.
For the expected and sent value of SAPI, five different configurations can be selected:
339-1268/06
Navigation Page
135
Book Contents
Disabled
The path trace management is not used
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters
E164 Hex View
The path trace is represented as a string of fifteen HEX characters
Blank Fill
The path trace is represented as a string of blanks
Zero Fill
The path trace is represented as a string of all zeros
* Set the threshold of errors corrected in one second by the FEC overt that the pre-FEC
Degrade alarm will be risen, by using the Error Trh scroll list.
In the Error Statistic field is displayed the number of errors corrected in one second by the FEC.
* Insert the Port Label in the Tp Label (Termination Point Label) field (optional).
The Current State filed displays the unit state.
* Set the Port Mode functionality, this functionality is used to monitor the LOS, the
following options are available:
Mon (Monitored)
In case of LOS the equipment displays the relevant alarm
Nmon (Not monitored)
In case of LOS the equipment does not display the relevant alarm
339-1268/06
Navigation Page
136
Book Contents
Auto
The LOS alarm is not displayed if the port is not connected to the traffic. The LOS alarm is displayed
only when the port loses its traffic. When the first LOS is cleared the Porte Mode status pass from
Auto to Mon
Note
The FEC (Tx) and FEC (Rx) fields are present only on the STM-64 Units
* Set the Forward Error Correction for the transmission side (select it with the pull down
menu into the FEC (Tx) field).
* Set the Forward Error Correction for the receiving side (select it with the pull down menu
into the FEC (Rx) field).
Enabled
The FEC is enabled
Inhibited
The FEC is disabled
* Set the MS Signal Degrade threshold in the SD Threshold area (MS area). (ADM)
The MS signal degrade threshold can be set using two different evaluation models:
ITUT
values from 10-5 to 10-9
ETSI
from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the
Bad threshold is exceeded, the MS signal degrade alarm will be activated; if the calculated value is
under the configured Good threshold, the alarm will expire
Check the relevant radio button to enable one of these evaluation models.
* Define the expected value of RS path trace, on J0 byte (select it with the pull down menu
into the J0 Path Trace Expected field).
* Define the sent value of RS path trace, on J0 byte (select it with the pull down menu into
the J0 Path Trace Send field).
For the expected and sent value of RS path trace, five different configurations can be selected:
Disabled
The path trace management is not used
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters
E164 Hex View
The path trace is represented as a string of fifteen HEX characters
Blank Fill
The path trace is represented as a string of blanks
Zero Fill
The path trace is represented as a string of all zeros
* Define the RS LOF Step (expressed in seconds), which is the duration of a loss of frame
alignment state necessary to emit a RS LOF alarm, by using the relevant scroll list.
* Click on the Apply button to validate the new configuration parameters. The Refresh
button can be used whenever an update of the window is not automatically performed.
339-1268/06
Navigation Page
137
Book Contents
* Select the Port folder, by clicking on the relevant button at the windows top.
The Port Configuration window becomes accessible. (ADM)
339-1268/06
Navigation Page
138
Book Contents
If the AU-4 is not multiplied and not connected the following window will appear.
If the AU-4 is not multiplied and connected the following window will appear.
Different parameters will be available depending on the type of channel selected (the type of
available channels depends on the demultiplexing level chosen in the Cross connection window,
for the unit to be configured).
339-1268/06
Navigation Page
139
Book Contents
* Define the expected value of path trace, on byte J1 (select it with the pull down menu into
the J1 Path Trace Expected field).
* Define the sent value of path trace, on byte J1 (select it with the pull down menu into the
J1 Path Trace Send field).
For the expected and sent value of J1 path trace, five different configurations can be selected:
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters
E164 Hex View
The path trace is represented as a string of fifteen Hexadecimal characters
Blank Fill
The path trace is represented as a string of blanks
Zero Fill
The path trace is represented as a string of all zeros
Disable
The path trace management is not used
Note
If the received J1 path trace value cant be read, the J1 Path Trace Received field
will contain a string of fixed byte, represented by the string Fixed Byte.
339-1268/06
Navigation Page
140
Book Contents
Check the relevant check boxes to enable one of these evaluation models.
* Define the SS Bit format for both sides (Tx and Rx).
* Confirm the new settings by clicking on the Apply button.
339-1268/06
Navigation Page
141
Book Contents
339-1268/06
Navigation Page
142
Book Contents
339-1268/06
Navigation Page
143
Book Contents
Zero Fill
The path trace is represented as a string of all zeros
Note
If the received J1 path trace value cant be read, the J1 Path Trace Received field
will contain a string of fixed byte, represented by the string Fixed Byte.
* Set the SDH SD Threshold (Signal Degrade Threshold) to be used.
Check the relevant radio button to enable one of these evaluation models.
* Define whether the PDH signal is framed or unframed, by using the PDH Framed check
box.
* For testing purpose by checking PRBS 23 Inject box, the PDH unit generates 223-1
(140Mbit/s) Pseudo Random Bit Sequence and sends it towards the Switch Unit. In the
selected channel the payload is replaced by the PRBS.
* For testing purpose by checking PRBS 23 Verify, the PDH unit checks the received
PRBS.
* Click on the Apply button to validate the new configuration parameters. The Refresh
button can be used whenever an update of the window is not automatically performed.
339-1268/06
Navigation Page
144
Book Contents
Check the relevant radio button to enable one of these evaluation models.
* Define the expected value of RS path trace, on byte J0 (select it with the pull down menu
into the J0 Path Trace Expected field).
* Define the sent value of RS path trace, on byte J0 (select it with the pull down menu into
the J0 Path Trace Send field).
For the expected and sent value of RS path trace, five different configurations can be selected:
Disabled
The path trace management is not used
339-1268/06
Navigation Page
145
Book Contents
* Define the LOF Step (expressed in seconds), which is the duration of a loss of frame
alignment state, necessary to emit a RS LOF alarm.
* Click on the Apply button to validate the new configuration parameters. The Refresh
button can be used whenever an update of the window is not automatically performed.
* Define the expected value of path trace, on byte J1 (select it with the pull down menu into
the J1 Path Trace Expected field).
* Define the sent value of path trace, on byte J1 (select it with the pull down menu into the
J1 Path Trace Send field).
For the expected and sent value of J1 path trace, five different configurations can be selected:
339-1268/06
Navigation Page
146
Book Contents
Disabled
The path trace management is not used
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters
E164 Hex View
The path trace is represented as a string of fifteen HEX characters
Blank Fill
The path trace is represented as a string of blanks
Zero Fill
The path trace is represented as a string of all zeros
Note
If the received J1 path trace value cant be read, the J1 Path Trace Received field
will contain a string of fixed byte, represented by the string Fixed Byte.
* Set the SDH SD Threshold (Signal Degrade Threshold) to be used.
Check the relevant radio button to enable one of these evaluation models.
* Define the SS Bit format for both sides (Tx and Rx).
* Confirm the new settings by clicking on the Apply button. The Refresh button can be
used whenever an update of the window is not automatically performed.
If the not connected AU-4 is multiplied: (ADM-4)
339-1268/06
Navigation Page
147
Book Contents
NOTICE
This window can be displayed whether the unit can perform VC-12 handling
only.
* Define the expected value of path trace, on byte J1 (select it with the pull down menu into
the J1 Path Trace Expected field).
* Define the sent value of path trace, on byte J1 (select it with the pull down menu into the
J1 Path Trace Send field).
For the expected and sent value of J1 path trace, five different configurations can be
selected:
Disabled
The path trace management is not used
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters
E164 Hex View
The path trace is represented as a string of fifteen HEX characters
Blank Fill
The path trace is represented as a string of blanks
Zero Fill
The path trace is represented as a string of all zeros
Note
If the received J1 path trace value cant be read, the J1 Path Trace Received field
will contain a string of fixed byte, represented by the string Fixed Byte.
* Set the SDH SD Threshold (Signal Degrade Threshold) to be used.
339-1268/06
Navigation Page
148
Book Contents
ETSI
from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the
Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is
under the configured Good threshold, the alarm will expire
Check the relevant radio button to enable one of these evaluation models.
* Define the SS Bit format for both sides (Tx and Rx).
* Confirm the new settings by clicking on the Apply button. The Refresh button can be
used whenever an update of the window is not automatically performed.
339-1268/06
Navigation Page
149
Book Contents
For the expected value of J1 path trace, five different configurations can be selected:
Disabled
The path trace management is not used
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters
E164 Hex View
The path trace is represented as a string of fifteen HEX characters
Blank Fill
The path trace is represented as a string of blanks
Zero Fill
The path trace is represented as a string of all zeros
Note
If the received J1 path trace value cant be read, the J1 Path Trace Received field
will contain a string of fixed byte, represented by the string Fixed Byte.
* Set the SDH SD Threshold (Signal Degrade Threshold) to be used.
Check the relevant check boxes to enable one of these evaluation models.
* Define the SS Bit format for both sides (Tx and Rx).
* Confirm the new settings by clicking on the Apply button. The Refresh button can be
used whenever an update of the window is not automatically performed.
If the connected AU-4 is multiplied: (ADM-4)
NOTICE
This functionality is available whether the unit can perform VC-12 handling.
339-1268/06
Navigation Page
150
Book Contents
* Define the expected value of path trace, on byte J1 (select it with the pull down menu into
the J1 Path Trace Expected field).
* Define the sent value of path trace, on byte J1 (select it with the pull down menu into the
J1 Path Trace Send field).
For the expected and sent value of J1 path trace, five different configurations can be
selected:
Disabled
The path trace management is not used
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters
E164 Hex View
The path trace is represented as a string of fifteen HEX characters
Blank Fill
The path trace is represented as a string of blanks
Zero Fill
The path trace is represented as a string of all zeros
Note
If the received J1 path trace value cant be read, the J1 Path Trace Received field
will contain a string of fixed byte, represented by the string Fixed Byte.
339-1268/06
Navigation Page
151
Book Contents
Check the relevant check boxes to enable one of these evaluation models.
* Confirm the new settings by clicking on the Apply button. The Refresh button can be
used whenever an update of the window is not automatically performed.
339-1268/06
Navigation Page
152
Book Contents
Note
If the received J1 path trace value cant be read, the J1 Path Trace Received field
will contain a string of fixed byte, represented by the string Fixed Byte.
IMPORTANT The J1 Path Trace area (lower order monitoring) is displayed only if the unit is
equipped with TUREG-B ASIC.
* Set the SDH SD Threshold (Signal Degrade Threshold) to be used.
The threshold can be set using two different evaluation models:
339-1268/06
Navigation Page
153
Book Contents
ITUT
values from 10-5 to 10-9
ETSI
from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the
Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is
under the configured Good threshold, the alarm will expire
Check the relevant check boxes to enable one of these evaluation models.
* Confirm the new settings by clicking on the Apply button. The Refresh button can be
used whenever an update of the window is not automatically performed.
* Define the expected value of path trace, on byte J2 (select it with the pull down menu into
the J2 Path Trace Expected field).
* Define the sent value of path trace, on byte J2 (select it with the pull down menu into the
J2 Path Trace Send field).
For the expected and sent value of J2 path trace, five different configurations can be
selected:
Disabled
The path trace management is not used
339-1268/06
Navigation Page
154
Book Contents
Note
If the received J1 path trace value cant be read, the J2 Path Trace Received field
will contain a string of fixed byte, represented by the string Fixed Byte.
* Set the SDH SD Threshold (Signal Degrade Threshold) to be used.
Check the relevant check boxes to enable one of these evaluation models.
* Confirm the new settings by clicking on the Apply button. The Refresh button can be
used whenever an update of the window is not automatically performed.
339-1268/06
Navigation Page
155
Book Contents
IMPORTANT The J2 Path Trace area (lower order monitoring) is displayed only if the unit is
equipped with TUREG-B ASIC.
* Set the SDH SD Threshold (Signal Degrade Threshold) to be used.
The threshold can be set using two different evaluation models:
339-1268/06
Navigation Page
156
Book Contents
ITUT
values from 10-5 to 10-9
ETSI
from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the
Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is
under the configured Good threshold, the alarm will expire
Check the relevant check boxes to enable one of these evaluation models.
* Confirm the new settings by clicking on the Apply button. The Refresh button can be
used whenever an update of the window is not automatically performed
339-1268/06
Navigation Page
157
Book Contents
339-1268/06
Navigation Page
158
Book Contents
NOTICE
If the received J1 path trace value cant be read, the J1 Path Trace Received
field will contain a string of fixed byte, represented by the string Fixed Byte.
* Set the expected and the send value for the signal label, by means of byte C2 (for byte
C2 there is an additional field with the received value).
* Set the values of signal degrade thresholds.
The threshold can be set using two different evaluation models:
ITUT
values from 10-5 to 10-9
ETSI
from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the
339-1268/06
Navigation Page
159
Book Contents
Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is
under the configured Good threshold, the alarm will expire
Check the relevant check boxes to enable one of these evaluation models.
* Set the status of RDI (former FERF) on received tributary signal (bit 8 in byte V5), using
the FERF State scroll list.
For the FERF State these different configurations can be selected:
Auto
The RDI signal is generated only when there is a remote defect indication
Forced ON
The RDI signal will always be generated; this option is used for testing
Forced OFF
The RDI signal will never be generated
* Confirm the new settings by clicking on the Apply button. The Refresh button can be
used whenever an update of the window is not automatically performed.
339-1268/06
Navigation Page
160
Book Contents
The Refresh button can be used whenever an update of the window is not automatically performed.
* Select the port to be configured, clicking on it in the scroll list.
* Define the port as: 2Mbit/s Unframed, 2Mbit/s Framed, 2Mbit/s Multiramed, 1.5Mbit/s AMI
code or 1.5Mbit/s B8ZS code.
* Set the Port Mode functionality, this functionality is used to monitor the LOS, the
following options are available:
Mon (Monitored)
In case of LOS the equipment displays the relevant alarm
Nmon (Not monitored)
In case of LOS the equipment does not display the relevant alarm
Auto
The LOS alarm is not displayed if the port is not connected to the traffic. The LOS alarm is displayed
only when the port loses its traffic. When the first LOS is cleared the Porte Mode status pass from
Auto to Mon
* Insert the Port Label in the Tp Label (Termination Point Label) field (optional).
* Define the expected value of path trace, on byte J2 (select it with the pull down menu into
the J2 Path Trace Expected field).
* Define the sent value of path trace, on byte J2 (select it with the pull down menu into the
J2 Path Trace Send field).
For the expected value of J2 path trace, five different configurations can be selected:
Disabled
The path trace management is not used
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters
E164 Hex View
The path trace is represented as a string of fifteen HEX characters
339-1268/06
Navigation Page
161
Book Contents
Blank Fill
The path trace is represented as a string of blanks
Zero Fill
The path trace is represented as a string of all zeros
* Set the expected and the send value for the signal label, by means of byte V5 (for byte
V5 there are two additional fields with the received and send values).
* Set the values of signal degrade thresholds by means of the relevant scroll lists in the SD
Threshold area.
The threshold can be set using two different evaluation models:
ITUT
values from 10-5 to 10-9
ETSI
from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the
Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is
under the configured Good threshold, the alarm will expire
Check the relevant check boxes to enable one of these evaluation models.
* Set the status of RDI (former FERF) on received tributary signal (bit 8 in byte V5), using
the FERF State scroll list.
For the FERF State these different configurations can be selected:
Auto
The RDI signal is generated only when there is a remote defect indication
Forced ON
The RDI signal will always be generated; this option is used for testing
Forced OFF
The RDI signal will never be generated
* Confirm the new settings by clicking on the Apply button. The Refresh button can be
used whenever an update of the window is not automatically performed.
339-1268/06
Navigation Page
162
Book Contents
339-1268/06
Navigation Page
163
Book Contents
In this window there are some read only information about the unit Current State, the Optical
Reach and the laser Wave Length. The operator can write additional information in the relevant
field.
* Set the Port Mode functionality, this functionality is used to monitor the LOS, the
following options are available:
Mon (Monitored)
In case of LOS the equipment displays the relevant alarm
Nmon (Not monitored)
In case of LOS the equipment does not display the relevant alarm
Auto
The LOS alarm is not displayed if the port is not connected to the traffic. The LOS alarm is displayed
only when the port loses its traffic. When the first LOS is cleared the Porte Mode status pass from
Auto to Mon
339-1268/06
Navigation Page
164
Book Contents
The SDH Termination window shows read only information about the unit Current State, the
Optical Reach and the laser Wave Freq Length.
* Insert the Port Label in the Tp Label (Termination Point Label) field (optional).
* Set the MS Signal Degrade threshold in the SD Threshold area (MS area).
The MS signal degrade threshold can be set using two different evaluation models:
ITUT
values from 10-5 to 10-9
ETSI
from 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If the
Bad threshold is exceeded, the MS signal degrade alarm will be activated; if the calculated value is
under the configured Good threshold, the alarm will expire
Check the relevant radio button to enable one of these evaluation models.
* Define the expected value of RS path trace, on J0 byte (select it with the pull down menu
into the J0 Path Trace Expected field).
339-1268/06
Navigation Page
165
Book Contents
* Define the sent value of RS path trace, on J0 byte (select it with the pull down menu into
the J0 Path Trace Send field).
For the expected and sent value of RS path trace, five different configurations can be selected:
Disabled
The path trace management is not used
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters
E164 Hex View
The path trace is represented as a string of fifteen HEX characters
Blank Fill
The path trace is represented as a string of blanks
Zero Fill
The path trace is represented as a string of all zeros
* Define the RS LOF Step (expressed in seconds), which is the duration of a loss of frame
alignment state necessary to emit a RS LOF alarm, by using the relevant scroll list.
* Set the Port Mode functionality, this functionality is used to monitor the LOS, the
following options are available:
Mon (Monitored)
In case of LOS the equipment displays the relevant alarm
Nmon (Not monitored)
In case of LOS the equipment does not display the relevant alarm
Auto
The LOS alarm is not displayed if the port is not connected to the traffic. The LOS alarm is displayed
only when the port loses its traffic. When the first LOS is cleared the Porte Mode status pass from
Auto to Mon
339-1268/06
Navigation Page
166
Book Contents
* Click on the Apply button to validate the new configuration parameters. The Refresh
button can be used whenever an update of the window is not automatically performed.
* Select the Port folder, by clicking on the relevant button at the windows top.
The Termination Point window becomes accessible.
* Define the expected value of path trace, on byte J1 (select it with the pull down menu into
the J1 Line field).
* Define the sent value of path trace, on byte J1 (select it with the pull down menu into the
J1 Line field).
For the expected and sent value of J1 path trace, five different configurations can be selected:
Disabled
The path trace management is not used
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters
E164 Hex View
The path trace is represented as a string of fifteen HEX characters
Blank Fill
The path trace is represented as a string of blanks
Zero Fill
The path trace is represented as a string of all zeros
Note
If the received J1 path trace value cant be read, the J1 Path Trace Received field
will contain a string of fixed byte, represented by the string Fixed Byte.
339-1268/06
Navigation Page
167
Book Contents
Check the relevant radio button to enable one of these evaluation models.
339-1268/06
Navigation Page
168
Book Contents
Delay setting
To set the delay time
* Select the Channels item in the unit menu and click on the Port folder.
* Select the first VC4V ( for the VC-4-4c/4v application select the first VC4V of each group)
and click on the Delay setting button, the Conversion Delay window will be displayed.
There are two possible ways to configure the delay time: Auto Adaptive or Max Delay.
* Check the Auto Adaptive button, the unit automatically sets the right delay time value.
* Use the Max Delay spinner to set the desired delay time value, the configuration range
for the delay time is between 125 microsec and 128msec with step of 125 microsec.
* There are two ways to perform the configured delay time:
Delayed/hitless
The delay time is not configured immediately but this operation it is hitless
Immediate/noising
The delay time is configured immediately but this operation it is not hitless
339-1268/06
Navigation Page
169
Book Contents
* Select either Eth#1 or Eth#2 folders to modify the Ethernet parameters for the port one
or two .
The Optical Interface shows read only information about the unit: the Optical Reach and the laser
Wave Freq Length.
* Insert the Port Label in the Tp Label (Termination Point Label) field (optional).
* Enable or disable the Auto Negotiation process by checking the relevant check box.
IMPORTANT For the Gigabit Ethernet line protection the Auto Negotiation must be set
enabled.
* Check the Port Enable field to start the transmission of the data traffic.
* Set the Max Ethernet Size by the M.t.u. (Max transmitted unit) spinner (from 64 to 1600
bytes).
In the Bit Rate field is displayed the line rate value (1000Mbit/s) and in the Duplex field is displayed
the duplex status of the interface (full duplex).
* Enable or disable the Shaper function by checking the relevant check box.
This option is used to define the traffic data rate desired by using the Rate spinner (from
10 to 1000Mb/s)
By clicking on the Mapper Performances button the Ethernet Statistic window will be displayed
339-1268/06
Navigation Page
170
Book Contents
The parameters relevant to the data incoming/outgoing into/from the Ethernet interface are
displayed in the Input/Output field, the meaning of them is explained in the following:
Allignement
The number of octets in valid MAC frames received on this interface, including the MAC header
and FCS. This does include the number of octets in valid MAC Control frames received on this
interface.
Unicast
The total number of unicast packets without errors. Note that this does not include MAC Control
frames, since MAC Control frames are consumed by the interface layer and are not passed to any
higher layer protocol.
Multicast
The total number of good packets that were directed to a multicast address. Note that this number
does not include packets directed to the broadcast. Note that this does not include MAC Control
frames, since MAC Control frames are consumed by the interface layer and are not passed to any
higher layer protocol.
339-1268/06
Navigation Page
171
Book Contents
Broadcast
The total number of good packets that were directed to the broadcast address. Note that this does
not include multicast packets. Note that this does not include MAC Control frames, since MAC
Control frames are consumed by the interface layer and are not passed to any higher layer
protocol.
Discarded
The number of inbound packets discarded even though no errors had been detected to prevent
their being delivered. Includes RxFIFO overflow count.
The parameters relevant to the Ethernet errors are displayed in the Errors Summary field, the
meaning of them is explained in the following:
Allignement
Count of frames received with a length between 64 bytes and the maximum packet size, a nonintegral byte count and a CRC error.
UnderSized
The total number of packets received that were less than 64 octets long (excluding framing bits, but
including FCS octets) and were otherwise well formed.
fcs
Count of frames received with a length between 64 bytes and the maximum packet size, an integral
byte count and a CRC error.
FrmTooLong
The total number of packets received that were longer than the configured Max Ethernet Size
(excluding framing bits, but including FCS octets) and were otherwise well formed.
Int.MAC rx
A count of frames for which reception fails due to an internal MAC sublayer receive error.
Int.MAC tx
A count of frames for which transmission fails due to an internal MAC sublayer receive error
By means of Request push button, a query on the status of the current register can be performed.
By selecting Continuous check box, the status of the current register is displayed every n seconds
(n stands for the number configured by the Refresh interval spinner).
By means of Disable push button, the performance data collection is stopped.
By means of Cnt. Reset push button, the counters value in the current aggregation period is reset.
339-1268/06
Navigation Page
172
Book Contents
By clicking on the Queue Performances button the Queue Performances window will be displayed.
The parameters relevant to the queue function are displayed in the Current Data field, the meaning
of them is explained in the following:
DisPackts
The number of inbound packets discarded even though no errors had been detected to prevent
their being delivered. Includes RxFIFO overflow count.
DiscBytes
The number of bytes discarded even though no errors had been detected to prevent their being
delivered.
By means of Request push button, a query on the status of the current register can be performed.
By selecting Continuous check box, the status of the current register is displayed every n seconds
(n stands for the number configured by the Refresh interval spinner).
By means of Disable push button, the performance data collection is stopped.
By means of Cnt. Reset push button, the counters value in the current aggregation period is reset.
339-1268/06
Navigation Page
173
Book Contents
* Select the Mapping folder, by clicking on the relevant button at the windows top.
* For the port one and port two define the mapping mode using the relevant scroll lists.
For the mapping different configurations can be selected:
VC-4
The data incoming from the Ethernet interface are mapped in a single VC-4
VC-4-4C
The data incoming from the Ethernet interface are mapped in a contiguous concatenation of four
VC-4
VC-4-4-nV
The data incoming from the Ethernet interface are mapped in a virtual concatenation of n VC-4, n
from 2 to 8
For the virtual VC-4 concatenation mapping see the following steps:
* Number of the virtual VC-4 make part of the concatenation using the VC-4-nV channels
spinner
* Check the Auto Adaptive button, the unit automatically sets the right delay time value.
* Use the Max Delay spinner to set the desired delay time value, the configuration range
for the delay time is between 125 microsec and 128msec with step of 125 microsec.
* There are two ways to perform the configured delay time:
339-1268/06
Navigation Page
174
Book Contents
Delayed/hitless
The delay time is not configured immediately but this operation it is hitless
Immediate/noising
The delay time is configured immediately but this operation it is not hitless
* Define the dLOM Threshold (expressed in milliseconds) by using the relevant scroll list,
this parameter indicates the duration of the loss of multiframe state necessary to emit a
dLOm alarm,
* Define the dSQM Thresholdby using the relevant scroll list., it is the number of
multiframes with wrong sequence necessary to emit an alarm of dSQM.
* Define the dSQM Recovery by using the relevant scroll list., it is the number of
multiframes with right sequence necessary to remove an alarm of dSQM.
* Confirm the new settings by clicking on the Change Map Settings button.
* Select the Port folder, by clicking on the relevant button at the windows top.
The Termination Point window becomes accessible.
* Define the expected value of path trace, on byte J1 (select it with the pull down menu into
the J1 Line field).
* Define the sent value of path trace, on byte J1 (select it with the pull down menu into the
J1 Line field).
For the expected and sent value of J1 path trace, five different configurations can be selected:
Disabled
The path trace management is not used
339-1268/06
Navigation Page
175
Book Contents
Note
If the received J1 path trace value cant be read, the J1 Path Trace Received field
will contain a string of fixed byte, represented by the string Fixed Byte.
* Define the expected value of signal label, on byte C2.
* Set the SDH SD Threshold (Signal Degrade Threshold) to be used.
Check the relevant radio button to enable one of these evaluation models.
339-1268/06
Navigation Page
176
Book Contents
EOW Channels
To configure the EOW Areas:
* Select either EW1 or EW2 folders (depending on the EOW Area to be configured).
339-1268/06
Navigation Page
177
Book Contents
* Select the connection type to be configured, by using the Type scroll list. The available
connection types are Direct, Bypass Line, and Ring.
339-1268/06
Navigation Page
178
Book Contents
339-1268/06
Navigation Page
179
Book Contents
339-1268/06
Navigation Page
180
Book Contents
Auxiliary Channels
To configure the G.703 64kbit/s auxiliary channels:
* Select G703 folder.
* Select the line or tributary interface to be used for carrying the auxiliary channel by double
clicking on it in the list.
* Select a spare SOH byte to be used to carry the auxiliary channel.
The RSOH and MSOH bytes are displayed as MS: x-y, where x is the number of the row
and y the number of the column.
* Use the Add button to confirm the creation of the auxiliary channel.
339-1268/06
Navigation Page
181
Book Contents
* Select the line or tributary interface to be used for carrying the auxiliary channel by double
clicking on it in the list.
* Select a spare SOH byte to be used to carry the auxiliary channel.
The RSOH and MSOH bytes are displayed as MS:x-y, where x is the number of the row
and y the number of the column.
* Use the Add button to confirm the creation of the auxiliary channel.
See Also:
Specific Functions: Channels - Auxiliary Unit
Input Collector
To configure the unit as Input Collector:
* Select the Input Collector, in this case the summary alarms (external) are collected from
the input (B interface) and sent to the DAM configured as Output Collector.
339-1268/06
Navigation Page
182
Book Contents
* Select the number of ground contacts to send in the In contacts number scroll list (the
maximum number of available contacts depends on the configured Dam address).
* Select the correct Dam address, this one must be unique and consecutive in the
network.
* Confirm the new settings by clicking on the APPLY button.
To configure the DAM connections to the lines:
* Click on the Connection folder.
339-1268/06
Navigation Page
183
Book Contents
* Select an available unit in the list and define if it is used for the East or West connection
by clicking on the East Line or West Line button.
* Repeat the previously step for the other connection (the configured units will be displayed
in the Line West and Line East fields).
* Confirm the settings by clicking on the APPLY button.
Output Collector
To configure the unit as Output Collector:
* Select the Output Collector, in this case the summary alarms are collected from the
remote Network Elements and returned on the DAM subrack connector (B interface).
339-1268/06
Navigation Page
184
Book Contents
339-1268/06
Navigation Page
185
Book Contents
* Under the column called Connector it is possible set the port as electrical (RJ45) or
optical.
* Click on the OK button to confirm and exit from this window.
Note
In order to create the 8xFast Ethernet Unit it is mandatory enabled one or more
Ethernet port.
Note
See Also:
8xFast Ethernet Unit: Ethernet Ports Configuration folder
339-1268/06
Navigation Page
186
Book Contents
339-1268/06
Navigation Page
187
Book Contents
Please refer to the t.b.d. paragraph in the t.b.d. chapter within of this handbook for
the description of the Loopback features.
See Also:
8xFast Ethernet Unit: Ethernet Ports Configuration folder, Fault Detection Procedure,
Alarm Reporting
Only the ports previously equipped can be available for the Ethernet parameters
Configuration.
When the Auto Negotiation function is enabled, the Local Config. Capabilities field will
be available (see the following picture) and simultaneously the only read Remote
Capabilities (if enabled) field will be shown.
339-1268/06
Navigation Page
188
Book Contents
Note
Note
When two or more Auto Negotiation parameters are simultaneously enabled, the
equipment will select the best signal available on the link.
Note
* Set the bit rate by using the relative radio buttons. Two option are available:
10Mb/s bit rate
The bit rate is set to 10Mb/s
100Mb/s bit rate
The bit rate is set to 100Mb/s
* Set the Half duplex or Full duplex function by using the relative radio buttons.
* Enable or disable the Asymmetrical pause function by using the relevant scroll list.
Note
For the optical interface the bit rate is permanent set as 100Mb/s and the duplex is
permanent set as Half duplex.
In order to summarize the current state of Ethernet parameter configuration of both the local and
remote ports, are shown several read only parameters under the label Used Setting and Remote
Status respectively as listed in the following:
n
Auto Neg.
Bit Rate
Duplex
Pause
339-1268/06
Navigation Page
189
Book Contents
See Also:
8xFast Ethernet Unit: Ethernet Ports Configuration folder
339-1268/06
Navigation Page
190
Book Contents
* Click on the Eth Queue Statistics button in order to show the Eth Queue Statistics
window.
* Click on the Apply button to confirm the choice.
See Also:
8xFast Ethernet Unit: Ethernet Ports Configuration folder, Local Ethernet Data
Performance, Remote Ethernet Data Performance, Queue Ethernet Data Performance
Some parameters described in the following will be displayed on the VCH Par. Config
window only if the LCAS function is enabled as shown in the following picture.
339-1268/06
Navigation Page
191
Book Contents
Note
manual
Manually insertion of both the expected and sent values for each VC in the VCG.
Note
For manual configuration, the value of SQ must be unique within the VCG. Moreover
the SQ number must be consecutive.
339-1268/06
Navigation Page
192
Book Contents
Note
If the Delayed hitless option is set, it is possible enable or not the Auto Adaptive
function by clicking on the relevant check box.
339-1268/06
Navigation Page
193
Book Contents
* Define the PathFail Holdoff [sec] by using the relevant scroll list (the range of this value
is between from 0s to 20s, 0.1s step). This parameter indicates the waiting time before
raising a LOPC/LOTC (loss of partial capacity, loss of total capacity) alarm.
* Define the PathFail WTR [min] by using the relevant scroll list (the range of this value is
between from 0m to 20m, 1m step. This parameter indicates the waiting time before
cleaning a LOPC/LOTC (loss of partial capacity, loss of total capacity) alarm.
* Set the TFS Criteria to be enabled by checking the relevant check boxes. In the TSF
Criteria field it is possible to select the alarm criteria to have the relevant VC-4 /Vc-3/VC12 disabled. In the following are described the TFS Criteria options available to be
enabled.
n Deg
n Lom
n Tim
n Plm
n Exc
n Loa
n Unequipped
n Ais
n Lop
339-1268/06
Navigation Page
194
Book Contents
The VC-n can be a VC-12,VC-3 and VC-4 for MSH41C only, while the VC-n is always
a VC-4 for MSH51C/64C.
339-1268/06
Navigation Page
195
Book Contents
The following picture shows the case of the first VC-3 (VC-3 obtained from VC-4 as described
above) exploded into 21 VC-12 . In order to visualize all channels under the Free Channels column,
using the relevant scroll list.
339-1268/06
Navigation Page
196
Book Contents
* Repeat the steps from n.1 to n.5 in order to insert another Virtual Container Group,
otherwise jump to the next step.
* When the Bandwidth allocation procedure is ended, click on the OK button to confirm last
action and close this window, while click on the Close button to reject the last action and
close this window.
It is mandatory always enable either the Source Allocation or the Sink Allocation. It
is also possible to enable both the functions simultaneously.
* Click on the Apply button in order to insert the VC-n channel into the VCG.
* Repeat the steps from n. 2 to n.5 in order to insert another VC-n channel into the
selected Virtual Container Group, otherwise jump to the next step.
* Repeat the steps from n.1 to n.6 in order to insert another Virtual Container Group,
otherwise jump to the next step.
* When the Bandwidth allocation procedure is ended, click on the OK button to confirm last
action and close this window, while click on the Close button to reject the last action and
close this window.
339-1268/06
Navigation Page
197
Book Contents
Description of the icon text channel shown under the column Assigned Channels
within of the Bandwidth Allocation folder
Generally the icon text representative the VC-n channel allocate into a VCG could be different,
because different are the situations where the channel could be involved (the Vc-n channel could be
allocate into a VCG where a LCAS mapping is enabled and only the Source Allocation is active or
the VC-n channel could be allocate into a VCG where a nV mapping is enabled and consequently
both the Source and the Sink Allocation function are active, and so on.). In all cases a arrow icon,
site near on the right side of the icon text representative of the VC-n channel will be shown. This
arrow can be shown in three different mode as described in the following:
n Left arrow ->
On the generic VC-n channel is active only the Sink Allocation function (only for LCAS
enabled);
n Right arrow <-
On the generic VC-n channel is active only the Source Allocation function (only for LCAS
enabled);
n Bidirectional arrow <->
On the generic VC-n channel are active both the Sink and the Source Allocation function.
See Also:
8xFast Ethernet Unit: Unit Configuration
339-1268/06
Navigation Page
198
Book Contents
Note
The picture shown above is only an example and it is displayed when a VC-4 or VC-3
channel is selected. If a VC-12 is selected the J2 Path Trace and V5 Signal label
fields will be shown instead of the J1 Path Trace and C2 Signal label ones
respectively.
In this folder it is possible to set the SDH parameter of the VC-n channel previously allocated into
the VCGs.
Define the expected value of path trace, on byte J1 by using the relevant scroll list as shown in the
following picture.
For the expected and sent value of J1 path trace, five different configurations can be selected:
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters;
E164 Hex View
The path trace is represented as a string of fifteen Hexadecimal characters;
Disable
The path trace management is not used;
Blank Fill
The path trace is represented as a string of blanks;
Zero Fill
The path trace is represented as a string of all zeros.
Note
If the received J1 path trace value cant be read, the J1 Path Trace Received field will
contain a string of fixed byte, represented by the string Fixed Byte.
* Define the expected value of path trace, on byte C2 by using the relevant arrow button.
Several options are available as listed in the following:
n Not spec.
n GFP encap
339-1268/06
Navigation Page
199
Book Contents
* Set the SDH SD Threshold (Signal Degrade Threshold) to be used by clicking on the
relevant radio buttons. Two options are alternatively available:
ITUT
Values from 10-9 to 10-5
ETSI
From 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If
the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is
under the configured Good threshold, the alarm will expire.
The VC-12 channels are not available for the MSH51C/64 equipments.
* Select the VC-12 to be configured in the Port scroll list.
* Define the expected value of path trace, on byte J2 by using the relevant scroll list as
shown in the following picture.
* Define the expected value of path trace, on byte J2 by using the relevant scroll list as
shown in the following picture.
For the expected and sent value of J2 path trace, five different configurations can be selected:
E164 Ascii View
The path trace is represented as a string of fifteen ASCII characters;
E164 Hex View
The path trace is represented as a string of fifteen Hexadecimal characters;
Disable
The path trace management is not used;
Blank Fill
The path trace is represented as a string of blanks;
Zero Fill
The path trace is represented as a string of all zeros.
Note
If the received J2 path trace value cant be read, the J2 Path Trace Received field will
contain a string of fixed byte, represented by the string Fixed Byte.
* Define the expected value of path trace, on byte V5 by using the relevant arrow button.
Several options are available as listed in the following:
339-1268/06
Navigation Page
200
Book Contents
n Not spec.
n GFP encap
* Set the SDH SD Threshold (Signal Degrade Threshold) to be used by clicking on the
relevant radio buttons. Two options are alternatively available:
ITUT
Values from 10-9 to 10-5
ETSI
From 0 to 100 % of errored frames, calculated in a configurable period (from 2 to 10 seconds). If
the Bad threshold is exceeded, the signal degrade alarm will be activated; if the calculated value is
under the configured Good threshold, the alarm will expire.
* Click on the Path Term Data button in order to show the relevant window.
* Click on the Alarm Management button in order to show the Alarm Severity window for
the VC-n channels.
* Click on the Apply button to confirm the actions.
* Click on the Refresh button to update the window.
See Also:
8xFast Ethernet Unit: Unit Configuration, Fault Detection Procedure, Alarm Reporting
339-1268/06
Navigation Page
201
Book Contents
PERFORMANCE
PERFORMANCE: ALL PERFORMANCES
Path (Performance -> All Perf)
This item is used to start and set-up the collection of the information quality data.
339-1268/06
Navigation Page
Book Contents
* Clicking on the Select button the Item Search and Selection window will appear. Within
this window several options relevant to string selection and searching are available.
Select
the Select push button allows to select all the items containing the searched string inserted String
to search field
Search
the Search push button allows to search all the items containing the searched string inserted
String to search field
Unselect
the Unselect push button allows to select all the items selected using the Select push button
Cancel
This button allows to exit the window
Both the 15 minutes and the 24 hours registers are available in order to store the performance data
in 15 minutes periods (15 Min. folder) or in 24 hours periods (24 Hrs. folder). In order to enable the
data collection:
* Choose the register in which the performance data collection will be enabled, by clicking
on the 15 Min. or 24 Hrs. folder.
* Set the exception threshold set by means of Perf Trh pull down menu.
* Set the CSES Threshold using the relevant scroll list.
When this threshold is exceeded, the number of the detected CSES and the period in
which they are detected are shown in the window placed on the right side in the upper
part of the folder.
* Enable the performance data collection by clicking on the Enable button.
339-1268/06
Navigation Page
203
Book Contents
In the History Data window the performance samples are displayed with the information relevant to
the monitored performance parameters (BBE, ES, SES, UAS and OFS). If no protection event
happens during the aggregation period (parameters equal to zero during 15 minutes or 24 hours),
the relevant sample will not be displayed in the History Data window and the # Suppressed field
will be incremented. By means of the Delete push button, the samples present in the History Data
window
are
deleted.
By means of Request push button, a query on the status of the current register can be performed.
By selecting Continuous check box, the status of the current register is displayed every second.
By means of Suspend and Resume push buttons, the operator can suspend and restart the
performance data collection. By means of Disable push button, the performance data collection is
stopped.
By means of Cnt. Reset push button, the counters value in the current aggregation period is reset.
See Also:
STM-n Units Performance Data, nx140/155Mbit/s Units Performance Data
MS Data and Path Termination Data VC-3/VC-2/VC-12
Four registers are available in order to store the performance data with attention to the duration of
the collection periods (15 minutes periods or 24 hours periods) and to the location of the termination
point where the performance is calculated (Near End = Local; Far End = Remote). In order to
enable the data collection:
* Choose the register in which the performance data collection will be enabled, by clicking
on the Near End 15 Min., Near End 24 Hrs., Far End 15 Min. or Far End 24 Hrs. folder.
* Select the exception threshold set by means of Perf Trh pull down menu.
* Set the CSES Threshold using the relevant scroll list.
When this threshold is exceeded, the number of the detected CSES and the period in
which they are detected are shown in the window placed on the right side in the upper
part of the folder.
339-1268/06
Navigation Page
204
Book Contents
339-1268/06
Navigation Page
205
Book Contents
Optical Measure
By means of this option the following parameters, related to the laser of the STM-N optical unit, are
monitored:
- TxPw (dB): transmitted optical power expressed in dBm;
- RxPw (dB): received optical power expressed in dBm;
- Bias (mA): laser pump bias current expressed in mA;
- Temp (C): laser pump temperature expressed in Celsius degrees.
In order to enable the data collection:
* Use the Enable button to start a measure (an existing measure can be stopped or
disabled).
By means of Request push button, a query on the status of the current register can be performed.
By selecting Continuous check box, the status of the current register is displayed every second.
By means of Suspend and Resume push buttons, the operator can suspend and restart the
performance data collection. By means of Disable push button, the performance data collection is
stopped.
See Also:
STM-n Units Performance Data, Booster and Preamplifier Units Performance Data
339-1268/06
Navigation Page
206
Book Contents
MS Adapt. Data
Both the 15 minutes and the 24 hours registers are available in order to store the performance data
in 15 minutes periods (15 Min. folder) or in 24 hours periods (24 Hrs. folder). In order to enable the
data collection:
* Choose the register in which the performance data collection will be enabled, by clicking
on the 15 Min. or 24 Hrs. folder.
* Set the exception threshold set by means of Perf Trh pull down menu.
* Enable the performance data collection by clicking on the Enable button.
In the History Data window the performance samples are displayed with the information relevant to
the monitored performance parameters (pJC+ and pJC-). If no protection event happens during the
aggregation period (parameters equal to zero during 15 minutes or 24 hours), the relevant sample
will not be displayed in the History Data window and the # Suppressed field will be incremented.
By means of the Delete push button, the samples present in the History Data window are deleted.
By means of Request push button, a query on the status of the current register can be performed.
By selecting Continuous check box, the status of the current register is displayed every second.
By means of Suspend and Resume push buttons, the operator can suspend and restart the
performance data collection. By means of Disable push button, the performance data collection is
stopped.
By means of Cnt. Reset push button, the counters value in the current aggregation period is reset.
See Also:
STM-n Units Performance Data, nx140/155Mbit/s Units Performance Data
339-1268/06
Navigation Page
207
Book Contents
Protection Data
Both the 15 minutes and the 24 hours registers are available in order to store the performance data
in 15 minutes periods (15 Min. folder) or in 24 hours periods (24 Hrs. folder). In order to enable the
data collection:
* Choose the register in which the performance data collection will be enabled, by clicking
on the 15 Min. or 24 Hrs. folder.
* Select the exception threshold set by means of the Perf Trh pull down menu.
* Enable the performance data collection by clicking the Enable push button.
In the History Data window the performance samples are displayed with the information relevant to
the monitored performance parameters (PSC and PSD). If no protection event happens during the
aggregation period (parameters equal to zero during 15 minutes or 24 hours), the relevant sample
will not be displayed in the History Data window and the # Suppressed field will be incremented.
By means of the Delete push button, the samples present in the History Data window are deleted.
By means of Request push button, a query on the status of the current register can be performed.
By selecting Continuous check box, the status of the current register is displayed every second.
By means of Suspend and Resume push buttons, the operator can suspend and restart the
performance data collection. By means of Disable push button, the performance data collection is
stopped.
By means of Cnt. Reset push button, the counters value in the current aggregation period is reset.
See Also:
Specific Functions: MSP Protection (ADM)
339-1268/06
Navigation Page
208
Book Contents
Both the 15 minutes and the 24 hours registers are available in order to store the performance data
in 15 minutes periods (15 Min. folder) or in 24 hours periods (24 Hrs. folder). In order to enable the
data collection:
* Choose the register in which the performance data collection will be enabled, by clicking
on the 15 Min. or 24 Hrs. folder.
* Set the exception threshold set by means of Perf Trh pull down menu.
* Enable the performance data collection by clicking on the Enable button.
In the History Data window the performance samples are displayed with the information relevant to
the monitored performance parameters (BBE, ES, SES, UAS and OFS). If no protection event
happens during the aggregation period (parameters equal to zero during 15 minutes or 24 hours),
the relevant sample will not be displayed in the History Data window and the # Suppressed field
will be incremented. By means of the Delete push button, the samples present in the History Data
window are deleted.
By means of Request push button, a query on the status of the current register can be performed.
By selecting Continuous check box, the status of the current register is displayed every second.
By means of Suspend and Resume push buttons, the operator can suspend and restart the
performance data collection. By means of Disable push button, the performance data collection is
stopped.
By means of Cnt. Reset push button, the counters value in the current aggregation period is reset.
See Also:
nx140/155Mbit/s Units Performance Data, 2Mbit/s Units Performance Data
339-1268/06
Navigation Page
209
Book Contents
Four registers are available in order to store the performance data with attention to the duration of
the collection periods (15 minutes periods or 24 hours periods) and to the location of the termination
point where the performance is calculated (Near End = Local; Far End = Remote). In order to
enable the data collection:
* Choose the register in which the performance data collection will be enabled, by clicking
on the Near End 15 Min., Near End 24 Hrs., Far End 15 Min. or Far End 24 Hrs. folder.
* Select the exception threshold set by means of Perf Trh pull down menu.
* Set the CSES Threshold using the relevant scroll list.
When this threshold is exceeded, the number of the detected CSES and the period in
which they are detected are shown in the window placed on the right side in the upper
part of the folder.
* Enable the performance data collection by clicking on the Enable button.
In the History Data window the performance samples are displayed with the information relevant to
the monitored performance parameters (BBE, ES, SES, UAS and OFS). If no protection event
happens during the aggregation period (parameters equal to zero during 15 minutes or 24 hours),
the relevant sample will not be displayed in the History Data window and the # Suppressed field
will be incremented. By means of the Delete push button, the samples present in the History Data
window are deleted.
By means of Request push button, a query on the status of the current register can be performed.
By selecting Continuous check box, the status of the current register is displayed every second.
By means of Suspend and Resume push buttons, the operator can suspend and restart the
performance data collection. By means of Disable push button, the performance data collection is
stopped.
By means of Cnt. Reset push button, the counters value in the current aggregation period is reset.
See Also:
8xFast Ethernet Unit: Unit Configuration, Local Ethernet Data Performance, Remote
Ethernet Data Performance
339-1268/06
Navigation Page
210
Book Contents
The pull down menu at the top of the window contains the entity types on which the operator can
enable a performance exception threshold. These entity types are listed in the following:
Path Term. Data for VC2, VC12 15min
(ADM-4)
Performance data related to a VC-2, VC-12 stored in a Near End 15 minutes register and in a Far
End 15 minutes register
Path Term. Data for VC-2, VC12 24h
(ADM-4)
Performance data related to a VC-2, VC-12 stored in a Near End 24 hours register and in a Far
End 24 hours register
Path Term. Data for VC4, VC3 15min
(ADM-4)
Performance data related to a VC-4, VC-3 stored in a Near End 15 minutes register and in a Far
End 15 minutes register
Path Term. Data for VC4, VC3 24h
(ADM-4)
Performance data related to a VC-4, VC-3 stored in a Near End 24 hours register and in a Far End
24 hours register
Path Term. Data for AU4-VC4 15min
(ADM-16) (ADM-64)
Performance data related to an AU-4, VC-4 stored in a Near End 15 minutes register and in a Far
End 15 minutes register for ADM-16, only in a Near End 15 minutes register for ADM-64
339-1268/06
Navigation Page
211
Book Contents
339-1268/06
Navigation Page
212
Book Contents
For each entity type the operator can set different exception threshold related to different
performance parameters.
For the Path Term. Data for VC-2, VC-12 15min, Path Term. Data for VC-2, VC-12 24h, Path
Term. Data for VC-4, VC-3 15min, Path Term. Data for VC-4, VC-3 24h, Path Term. Data for
AU-4-VC-4 15min, Path Term. Data for AU-4-VC-4 24h, MS Data 15min, MS Data 24h, TC Path
Term Data for VC2-VC12 15m, TC Path Term Data for VC2-VC12 24h, TC Path Term Data for
VC4-VC3 15m, TC Path Term Data for VC4-VC3 24h, TC Path Term Data for VC4 15m, TC Path
Term Data for VC4 24h entity types, the following performance parameters appear:
n BBE (Background Block Error)
n ES (Errored Second)
n SES (Severely Errored Second)
n CSES (Consecutive SES)
For the RS Data 15min and RS Data 24h entity types, the following performance parameters
appear:
n BBE
n ES
n SES
n CSES
n OFS (Out of Frame Second)
For the MS/TU Adapt. Data 15min and MS/TU Adapt. Data 24h entity types, the following
performance parameters appear:
n PJC+ (Pointer Justification Counter +): indicates the number of increments in the pointer
value
n PJC- (Pointer Justification Counter -): indicates the number of decrements in the pointer
value
For the Protection Data 15min and Protection Data 24h entity types, the following performance
parameters appear:
n PSC (Protection Switching Counter): indicates the number of protection switching
n PSD (Protection switching Duration): indicates the protection duration in seconds
To set the exception thresholds for an entity:
* Select the entity type with its aggregation period by mean of the pull down menu.
* Use the arrow buttons to set the eight exception threshold sets. Each set has two
configurable values:
Max
when the number of the monitored events exceeds this value, a reporting message appears in the
Alarm and Event Monitor Window
Min
when the number of the monitored events does not exceed this value during all the related
aggregation period, the reporting message disappears from the Alarm and Event Monitor Window
339-1268/06
Navigation Page
213
Book Contents
* Use Request to access the value of the current entity type and its associated
aggregation period.
* Click on Default and then confirm by pressing the Apply button to restore the default
values.
See Also:
Performance: All Performances
* Define whether the Data Collection counters are enabled or disabled by clicking on the
relevant button (step n.5).
339-1268/06
Navigation Page
214
Book Contents
Perform the step n.8, only if the Continuous check box is enabled, otherwise jump
to the step n.9 .
* Set the refresh time of the current register status using the relevant scroll list (The range
of these value is between from 1s to 3600s, 1s step) (step n.8).
* Click on the Apply button to confirm the choices (step n.9).
* Finally, by means of Request button, a query on the status of the current register can be
performed (step n.10).
The following table describers all snapshots shown in the local Performance Monitoring
Management folder shown above.
Local Ethernet Data Performance Snapshot Counters
Counter name
Direction
Description
Notes
In
Out
---
Note1
Note2, Note3
Note4, Note5
Note6
Unicast Fr.
Multicast Fr.
Broadcast Fr.
Pause Fr.
InErrors
---
---
OutErrors
---
---
---
Note7
---
Note8
CRC error.
FrmTooLong
MauJabEntry
CarrierSense
339-1268/06
Navigation Page
215
Book Contents
Discarded Fr.
Note9
Note10
collision.
A count of successfully transmitted frames on a particular
MultiColl Fr.
LateColl Fr.
ExcColl Fr.
Note11,
Note12
Note13
Note14
The following notes are referred to the Local Ethernet Data Performance Snapshot Counters table
show above.
Note 1
The Unicast Frame value does not include MAC Control frames, since MAC Control
frames are consumed by the interface layer and are not passed to any higher layer
protocol.
Note 2
The Multicast Frame value does not include packets directed to the broadcast.
Note 3
The Multicast Frame value does not include MAC Control frames, since MAC Control
frames are consumed by the interface layer and are not passed to any higher layer
protocol.
Note 4
Note 5
The Broadcast Frame value does not include MAC Control frames, since MAC Control
frames are consumed by the interface layer and are not passed to any higher layer
protocol.
Note 6
Note 7
The Frame To Long counter is only applicable to 10Mb/s interfaces. This counter will
always indicate 0 for MAUs above 10Mb/s.
Note 8
The Carrier sense counter is not applicable for full-duplex operation mode.
Note 9
The Single Collision Frame counter is not applicable for full-duplex operation mode.
Note 10 The Multiple Collision Frame counter is not applicable for full-duplex operation mode.
Note 11 The Deferred Transmissions count does not include frames involved in collisions.
Note 12 The Deferred Transmissions counter is not applicable for full-duplex operation mode.
Note 13 The Late Collision counter is not applicable for full-duplex operation mode.
Note 14 The Excessive Collisions counter is not applicable for full-duplex operation mode
339-1268/06
Navigation Page
216
Book Contents
See Also:
Queue Ethernet Data Performance, Remote Ethernet Data Performance, 8xFast
Ethernet Unit: Ethernet Ports Configuration folder
* Define whether the Data Collection counters are Enabled or Disabled by clicking on the
relevant buttons (step n.5)
339-1268/06
Navigation Page
217
Book Contents
Perform the step n.8, only if the Continuous check box is enabled, otherwise jump
to the step n.9 .
* Set the refresh time of the current register status using the relevant scroll list (The range
of these value is between from 1s to 3600s, 1s step) (step n.8).
* Click on the Apply button to confirm the choices (step n.9))
* Finally, by means of Request button, a query on the status of the current register can be
performed (step n.10).
The following table describers all snapshots shown in the remote Performance Monitoring
Management folder shown above.
Remote Ethernet data Performance Snapshot Counters
Counter name
Direction
Description
Notes
In
Out
---
---
---
---
---
Packets
MulticastPackets
BroadcastPackets
Note15,
Note16
Note17,
Note18
OversizePkt
CrcAlignErrors
339-1268/06
Navigation Page
218
Book Contents
Note19,
Note21
---
---
---
---
---
---
Note20
Error).
Fr.64bit
Fr.65-127bit
Fr.128-255bit
Fr,256-511bit
Fr.512-1032bit
Fr.1024-1518
The following notes are referred to the Remote Ethernet Data Performance Snapshot Counters
table show above.
Note 15 The MulticastPackets value does not include packets directed to the broadcast.
Note 16 The MulticastPackets value does not include MAC Control frames, since MAC Control
frames are consumed by the interface layer and are not passed to any higher layer
protocol.
Note 17 The BroadcastPackets value does not include multicast packets.
Note 18 The BroadcastPackets value does not include MAC Control frames, since MAC Control
frames are consumed by the interface layer and are not passed to any higher layer
protocol.
339-1268/06
Navigation Page
219
Book Contents
Note 19 The Fragments counter computes both runts (which are normal occurrences due to
collisions) and noise hits.
Note 20 The Fragments counter in not available for full duplex interfaces
Note 21 The jabber definition in this handbook is different than the definition in IEEE-802.3
section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These handbook define
jabber as the condition where any packet exceeds 20 ms. The allowed range to detect
jabber is between 20 ms and 150 ms.
See Also:
Queue Ethernet Data Performance, Local Ethernet Data Performance, 8xFast Ethernet
Unit: Ethernet Ports Configuration folder, Queue Ethernet Data Performance
* Define whether the Data Collection counters are enabled or disabled by clicking on the
relevant buttons.
* Define whether the Automatic counters reset function is enabled or disabled by checking
or not the relevant check box respectively.
339-1268/06
Navigation Page
220
Book Contents
* Define whether the Automatic refresh function of the current register status is enabled or
disabled by checking or not the Continuous check box respectively.
Note
Perform the step n.8, only if the Continuous check box is enabled, otherwise jump
to the step n.9 .
* Set the refresh time of the current register status using the relevant scroll list (The range
of these value is between from 1s to 3600s, 1s step).
* Click on the Apply button to confirm the choices.
* Finally, by means of Request push button, a query on the status of the current register
can be performed.
339-1268/06
Navigation Page
221
Book Contents
CONFIGURATION FILES
In this chapter are described the configuration files that can be downloaded to the equipment.
The configuration files are text files that may be edited by the user and loaded via the control
application into the equipment in order to change some of the equipment default values.
Configuration files distributed with the equipment Software Kit are normally meant as template files
that should be saved before any changes are introduced.
OSI CONFIGURATION
An ASCII configuration file with the parameters of second, third and fourth layers of OSI protocol
stack, used for the communication with the Network Management Centre (both on the Ethernet and
on the DCCs), can be sent to the Communication and Control Unit.
The SDH equipment implement the protocols specified by the following recommendations.
On layer 2:
n On Ethernet:
ISO 8802-3 (CSMA/CD)
ISO 8802-2 (LLC)
n On DCC:
CCITT Q.920/921 (LAPD)
On layer 3:
n ISO 8473 (CLNP)
n ISO 9542 (ESIS)
n ISO 10589 (ISIS)
On layer 4:
n ISO 8073 (OSI Transport)
The information contained in this document, and related to the second, third and fourth OSI layers,
may be used for a first check of the interoperability at the DCN level between our SDH equipment
and equipment by another manufacturer. Such interoperability may be desirable both on ethernet Qinterface (QB3) and on QECC.
Note that, with few exceptions (such as the System Id length which should be the same for two
systems within the same ISIS domain, or the LAPD frame size which, together with its header and
its footer, should be equal or smaller than the Maximum Data packet Size on the other side of the
STM-1 connection), it is not necessary that the parameters are configured exactly in the same way.
This capability allows interoperability between systems by different manufacturers. However, big
discrepancies in the values of some parameters, such as the LAPD, ESIS and ISIS timers, may
prevent the communication from working properly.
The information related to layer 4 profiling may be useful to try and improve the performance of the
communication between a Network Element and its Element Manager.
339-1268/06
Navigation Page
Book Contents
339-1268/06
Navigation Page
223
Book Contents
ISIS_RA_PREFIX_2
ISIS_RA_PREFIX_3
ISIS_RA_PREFIX_4
ISIS_RA_PREFIX_5
ISIS_RA_PREFIX_6
ISIS_RA_PREFIX_7
ISIS_RA_PREFIX_8
ISIS_RA_PREFIX_9
CLNS_PARAM = 0 ,
Note(*)
=
=
=
=
=
=
=
=
0
0,0,6,490102,20,000205111111;
0,0,6,490102,20,000205111111;
0,0,6,490102,20,000205111111;
0,0,6,490102,20,000205111111;
0,0,6,490102,20,000205111111;
0,0,6,490102,20,000205111111;
0,0,6,490102,20,000205111111;
0,0,6,490102,20,000205111111;
, 1 ;
ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,10,1800,30,600,3;
MAC_ADDR = 020511111106 ;
DCC_PROFILE_0 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_1 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_2 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_3 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_CONFIG_0 = 0 , 0 , 0 ;
DCC_CONFIG_1 = 0 , 0 , 0 ;
DCC_CONFIG_2 = 0 , 0 , 0 ;
DCC_CONFIG_3 = 0 , 0 , 0 ;
DCC_CONFIG_4 = 0 , 0 , 0 ;
DCC_CONFIG_5 = 0 , 0 , 0 ;
DCC_CONFIG_6 = 0 , 0 , 0 ;
DCC_CONFIG_7 = 0 , 0 , 0 ;
SOH_SLOT_0 = 1,4,5,6,13,11,9,10;
SLOT_PORT_0
SLOT_PORT_1
SLOT_PORT_2
SLOT_PORT_3
SLOT_PORT_4
SLOT_PORT_5
SLOT_PORT_6
SLOT_PORT_7
=
=
=
=
=
=
=
=
0
0
0
0
0
0
0
0
,
,
,
,
,
,
,
,
0
0
0
0
0
0
0
0
,
,
,
,
,
,
,
,
0
0
0
0
0
0
0
0
;
;
;
;
;
;
;
;
#
~
Note(*)
The ETH_CONFIG values shown in the row are the default values for the ADM-4,
ADM-16 and REG-4/16. The ETH_CONFIG default values for the ADM-64 and REG64 are shown in the following:
ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3;
339-1268/06
Navigation Page
224
Book Contents
ISIS_NUM_RA_PREFIXES = 0 ;
ISIS_RA_PREFIX_0 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111;
CLNS_PARAM = 0 , 0 , 1 ;
Note(*)
ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,10,1800,30,600,3;
MAC_ADDR = 020511111106 ;
DCC_PROFILE_0 =
1513,1492,1,7,20,20,0,0,1,3,10,20,150,10,7,10,30,3;
DCC_PROFILE_1 =
1513,1492,1,7,20,20,0,0,0,3,10,20,150,10,7,10,30,3;
DCC_PROFILE_2 =
1513,1492,1,7,20,20,0,0,1,3,10,20,150,10,7,10,30,3;
DCC_PROFILE_3 =
1513,1492,1,7,20,20,0,0,0,3,10,20,150,10,7,10,30,3;
DCC_CONFIG_0 = 0 , 0 , 0 ;
DCC_CONFIG_1 = 0 , 0 , 0 ;
DCC_CONFIG_2 = 0 , 0 , 0 ;
DCC_CONFIG_3 = 0 , 0 , 0 ;
DCC_CONFIG_4 = 0 , 0 , 0 ;
DCC_CONFIG_5 = 0 , 0 , 0 ;
DCC_CONFIG_6 = 0 , 0 , 0 ;
DCC_CONFIG_7 = 0 , 0 , 0 ;
DCC_CONFIG_8 = 0,0,0;
DCC_CONFIG_9 = 0,0,0;
DCC_CONFIG_10 = 0,0,0;
DCC_CONFIG_11 = 0,0,0;
DCC_CONFIG_12 = 0,0,0;
DCC_CONFIG_13 = 0,0,0;
DCC_CONFIG_14 = 0,0,0;
DCC_CONFIG_15 = 0,0,0;
DCC_CONFIG_16 = 0,0,0;
DCC_CONFIG_17 = 0,0,0;
DCC_CONFIG_18 = 0,0,0;
DCC_CONFIG_19 = 0,0,0;
DCC_CONFIG_20 = 0,0,0;
DCC_CONFIG_21 = 0,0,0;
DCC_CONFIG_22 = 0,0,0;
DCC_CONFIG_23 = 0,0,0;
DCC_CONFIG_24 = 0,0,0;
DCC_CONFIG_25 = 0,0,0;
DCC_CONFIG_26 = 0,0,0;
DCC_CONFIG_27 = 0,0,0;
SLOT_PORT_0 = 0,0,0;
SLOT_PORT_1 = 0,0,0;
SLOT_PORT_2 = 0,0,0;
SLOT_PORT_3 = 0,0,0 ;
SLOT_PORT_4 = 0,0,0 ;
SLOT_PORT_5 = 0,0,0 ;
SLOT_PORT_6 = 0,0,0 ;
SLOT_PORT_7 = 0,0,0 ;
SLOT_PORT_8 = 0,0,0;
SLOT_PORT_9 = 0,0,0;
SLOT_PORT_10 = 0,0,0;
SLOT_PORT_11 = 0,0,0;
SLOT_PORT_12 = 0,0,0;
SLOT_PORT_13 = 0,0,0;
SLOT_PORT_14 = 0,0,0;
SLOT_PORT_15 = 0,0,0;
SLOT_PORT_16 = 0,0,0;
339-1268/06
Navigation Page
225
Book Contents
SLOT_PORT_17 = 0,0,0;
SLOT_PORT_18 = 0,0,0;
SLOT_PORT_19 = 0,0,0;
SLOT_PORT_20 = 0,0,0;
SLOT_PORT_21 = 0,0,0;
SLOT_PORT_22 = 0,0,0;
SLOT_PORT_23 = 0,0,0;
SLOT_PORT_24 = 0,0,0;
SLOT_PORT_25 = 0,0,0;
SLOT_PORT_26 = 0,0,0;
SLOT_PORT_27 = 0,0,0;
#Note(*) The ETH_CONFIG values shown in the row are the default values for the ADM-4,
ADM-16 and REG-4/16. The ETH_CONFIG default values for the ADM-64 and REG-
339-1268/06
Navigation Page
226
Book Contents
339-1268/06
Navigation Page
227
Book Contents
n window_tmr: Window timer. The period of inactivity that can occur before Transport sends a
hello packet to the peer entity with which a connection is established (in tenths of second).
Must be bigger than the Local Acknowledgement delay (note that the Local
Acknowledgement delay is expressed in milliseconds).
Range is [1-65535].
Default: 750 (75 seconds).
n local_ack: Local acknowledgement delay. The maximum amount of time Transport can
delay acknowledging a TPDU it receives (in milliseconds). Must be lower than the Window
timer (note that the Window timer is expressed in tenths of seconds).
Range is [1-65535].
Default: 1 (0.001 seconds).
n local_flow_ctrl: Local flow control. Available resources check interval (in milliseconds). If
Transport has no receive credit available, it checks the available resources each time the
interval specified by this parameter has passed, until credit becomes available.
Range is [1-65535].
Default: 100 (0.1 seconds).
n retrans_cnt: Number of retransmission. Maximum number of times which the local transport
entity will continue to transmit a TPDU that requires acknowledgement.
Range is [1-255].
Default: 8.
TRANSPORT = 2,8,3,3000,120,20,120,750,1,100,8;
Network Layer
NSAP: parameters associated to this entry are:
n nsap_len: length of NSAP address, expressed in bytes.
n nsap_addr[20]: field containing the NSAP (Network Service Access Point) identifier or
network address of the equipment.
NSAP = 20, 4901020304050607080900004402051111110601 ;
339-1268/06
Navigation Page
228
Book Contents
339-1268/06
Navigation Page
229
Book Contents
Range is [1-65535].
Default: 2.
n ES_poll_rate: ES polling rate. Default End System Hello rate.
Range is [1-65535].
Default: 50.
n wait_time: Default Waiting Time.
Range is [1-65535].
Default: 60.
n max_virt_adjs: Maximum Number of Virtual Adjacencies. Default maximum number of
virtual adjacencies (virtual adjacencies are used for Partition Repair).
Range is [0-31].
Default: 2.
NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2;
339-1268/06
Navigation Page
230
Book Contents
n RAP_id: An integer value which uniquely identifies the Reachable Address Prefix within the
Network Element. Value 0 is used when the RAP with this identifier is not defined.
Default: 0 (prefix undefined).
n RAP_type: Type of the RAP. 0 (BDC, for Broadcast RAP), 1 (PP, for Point to Point RAP), 2
(BDC_MA, for Broadcast MESA), (PP_MSA, for Point to Point MESA) (MESA, Manual End
System Adjacencies).
n RAP_len: Prefix length. If Prefix Type is 0 or 1, range is [0-40]. Note that the value 0 is
allowed, and allows to redirect on a given interface all the packets which may not be routed
otherwise. If Prefix Type is 2 or 3, the range is [-(20/SystemIdLength)], identifying the
number of End Systems manually connected on the selected unit.
n RAP_addr[20]: RAP data. If Prefix Type is 0 or 1, this field contains the Reachable Address
Prefix. If Prefix Type is 2 or 3, this field contains prefix_length System Identifier of the End
Systems which may be reached through this adjacency. Note that only the first prefix_length
semioctets, if Prefix Type is 0 or 1, or the first prefix_length*SystemIdLength bytes, if Prefix
Type is 2 or 3, they are meaningful.
n RAP_metric: Prefix default metric. Default metric value for the reachable address prefix, or
the Manual End System Adjacency. This value is used for the computation of the shortest
path.
Range is [1-128].
Default: 20.
n RAP_cid[6]:
If the prefix type is PP, or PP_MA, this field will contain the DCC channel id of the DCC
channel carrying the point to point circuit to which the RAP, or MESA, is associated, on two
bytes, and the remaining four bytes will be meaningless. If the prefix type is BDC, or
BCD_MA, this field will contain the Ethernet MAC address, on 6 bytes, to which the packets
addressed to the configured prefix, or Manual End Systems must be delivered.
ISIS_RA_PREFIX_0 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111;
339-1268/06
Navigation Page
231
Book Contents
339-1268/06
Navigation Page
232
Book Contents
n ETH_max_size: Max Data Packet Size. Maximum size of the data packet output on this
circuit.
Range is [500-1500].
Default: 1492.
n ETH_lev1metric: Default level 1 circuit metric. Value of the default metric on this circuit, for
level 1 routing.
Range is [1-63].
Default: 20.
n ETH_lev2metric: Default level 2 circuit metric. Value of the default metric on this circuit, for
level 2 routing.
Range is [1-63].
Default: 20.
n ETH_lev1pri: Default level 1 priority. Priority to become the level 1 designated router. The
highest the priority, the highest the chances of this system to become the designated router.
Range is [1-127].
Default: 64.
n ETH_lev2pri: Default level 2 priority. Priority to become the level 1 designated router. The
highest the priority, the highest the chances of this system to become the designated router.
Range is [1-127].
Default: 64.
n ISIS_hello_tmr: ISIS Hello Timer default. Timer defining the default interval of generation of
the ISIS Hello PDUs, in seconds.
Range is [1-65535].
Default: 10. (ADM-4), (ADM-16), (REG-4/16)
Default: 3. (ADM-64), (REG-64)
n ISO9542_redirect_tmr: ISO 9542 redirect timer. Default ISO 9542 redirect timer, in
seconds.
Range is [1-65535].
Default: 1800.
n ISO9542_IS_conf_tmr: IS configuration timer. Default ISO 9542 IS configuration timer, in
seconds.
Range is [1-21845].
Default: 30. (ADM-4), (ADM-16), (REG-4/16)
Default: 10. (ADM-64), (REG-64)
339-1268/06
Navigation Page
233
Book Contents
339-1268/06
Navigation Page
234
Book Contents
n ext_domain: External domain flag. Flag saying whether the external domain attribute is set
for this DCC channel.
Range is [TRUE, FALSE].
Default: FALSE.
n dcc_r_m: DCCR/DCCM selector. A flag saying whether DCCR or DCCM should be used for
this profile.
Range is [0(DCCR),1(DCCM)].
n retrans_cnt: Retransmission count. Limit is MAX_CNTR (1024).
Default: 3.
n cong_tmr: Congestion Timer. Limit is MAX_TIMER (1024).
Default: 10 tenths of second, that is, one second.
n retrans_tmr: Retransmit Timer. LAPD T200 timer; the value is expressed in tenths of
second. The maximum allowed value for this timer is MAX_TIMER (1024); it must be smaller
than T203 timer.
Default: 20.
n idle_tmr: Idle Timer. LAPD T203 timer; the value is expressed in tenths of second. The
maximum allowed value for this timer is MAX_TIMER (1024); it must be bigger than T200
timer.
Default: 200 tenths of second, that is 20 seconds.
n isis_hello_tmr: ISIS Hello Timer default, in seconds.
Range is [1-65535].
Default: 15.
n ISO_9542_opts: ISO 9542 (ESIS) functions supported.
bit 1 = configuration
bit 2 = redirect
bit 3 = notification
bit 4 = checksum
Default: configuration | redirect | notification.
n ish_tmr: IS configuration timer. Default ISO 9542 IS configuration timer, in seconds.
Range is [1-21845].
Default: 300.
n esc_tmr: ES configuration timer. Default ISO 9542 Suggested ES configuration timer, in
seconds.
Range is [1-65535].
Default is 600.
339-1268/06
Navigation Page
235
Book Contents
n Hold: Holding time multiplier. Default ISO 9542 Holding time multiplier.
n Range is [2-63].
n Default: 3.
DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_1 = 1513,1492,1,7,20,20,0,0,0,3,10,20, 200,15,7,300,600,3;
DCC_PROFILE_2 = 1513,1492,1,7,20,20,0,0,1,3,10,20, 200,15,7,300,600,3;
DCC_PROFILE_3 = 1513,1492,1,7,20,20,0,0,1,3,10,20, 200,15,7,300,600,3;
339-1268/06
Navigation Page
236
Book Contents
Operative Indications
How to modify NSAP
* Look for the row identified by the entry NSAP.
* Modify nsap_length and nsap_value.
|
NSAP = 20,4901020304050607080900004402051111110601 ;
Ethernet is enabled.
339-1268/06
Navigation Page
237
Book Contents
339-1268/06
Navigation Page
238
Book Contents
Examples
Management of Static Routing Information
Static Routing information may be of two different types, as described by the IS-IS protocol (ISO
10589): RAP:s (Reachable Address Prefixes) and MESA:s (Manual End System Adjacencies).
Note that Manual End System Adjacencies are not supported by all the equipment and releases
supporting OSI management.
Reachable address prefixes may be used, on an equipment which is configured as a level 2 router,
to set up static routes, both on point to point and on broadcast circuits, based on a prefix of the
destination NSAP contained in each data packet.
Note that the systems reachable by means of a RAP must be in a different area from any other area
in the network, where an area is a fully connected partition of the network, in which the area address
part of the NSAP is the same for all the systems, and different from the area address of any system
in the network outside such partition.
339-1268/06
Navigation Page
239
Book Contents
Manual End System Adjacencies may be used to set-up a static route from a SDH NE (which is
always an Intermediate System) to up to [20/SystemIdLength] (3, if SystemIdLength is 6, as usual)
End Systems belonging to the same area, for which it is not possible (or desirable) to establish a
dynamic adjacency by means of ES-IS protocol (ISO 9542). For example, it may be that such End
Systems dont implement IS-IS on the considered circuit. Manual End System Adjacencies have the
advantage that it is not necessary to use a different area for each configured route.
On the other hand, they have the disadvantage that each route may give access to
[20/SystemIdLength] (typically 3) End Systems, at most, while a single RAP may give access to a
virtual unlimited number of systems. For examples. If there were a STM-N ring containing 20
elements, it would be possible to reach all the elements from the gateway by configuring just one
rap, but 7 MESA:s would be needed.
In the following some examples of stating routing configuration necessary for the communication
between two equipment are given.
Eqt. A
DCC
Eqt. B
339-1268/06
Navigation Page
240
Book Contents
OSIA.ini
**********************************
@OSI.ini@
[OSI_CONFIG]
PSAP = not_used ;
PRESENTATION = not_used ;
SSAP = not_used ;
SESSION = not_used ;
TSAP = not_used ;
TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8;
NSAP = 20, 4901020304050607080900004402052179710601 ;
NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2;
ISIS_SYS_ID = 6 , 020521797106 ;
ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ;
ISIS_MAN_AREA_ADDR_1 = 0 , ;
ISIS_MAN_AREA_ADDR_2 = 0 , ;
ISIS_NUM_RA_PREFIXES = 1 ;
ISIS_RA_PREFIX_0 = 1,1,20,49555555555555555555,20,000600000000;
ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111;
CLNS_PARAM = 0 , 0 , 3 ;
ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3;
MAC_ADDR = 020521797106 ;
DCC_PROFILE_0 =
1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_1 =
1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_2 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_3 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_CONFIG_0 = 0 , 0 , 0 ;
DCC_CONFIG_1 = 0 , 0 , 0 ;
DCC_CONFIG_2 = 0 , 0 , 0 ;
DCC_CONFIG_3 = 0 , 0 , 0 ;
DCC_CONFIG_4 = 0 , 0 , 0 ;
DCC_CONFIG_5 = 0 , 0 , 0 ;
DCC_CONFIG_6 = 0 , 1 , 1 ;
DCC_CONFIG_7 = 0 , 0 , 0 ;
#
~
**********************************
339-1268/06
Navigation Page
241
Book Contents
File notes
NSAP = 20, 4901020304050607080900004402052179710601
ISIS_NUM_RA_PREFIXES = 1 (number of configured prefixes)
ISIS_RA_PREFIX_0:
field RAP_id=1
field RAP_type=1 (point to point circuit)
field RAP_len=20
field RAP_addr=49555555555555555555
field RAP_metric=20
field RAP_cid=00060000000 (seventh DCC)
this prefix supplies to equipment A the information necessary to connect to equipment B (equipment
B NSAP is
NSAP = 20, 4955555555555555555555555502051010100601)
CLNS_PARAM: field router_type=3 (area router)
DCC_PROFILE_0 = 1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3
(eighth field ext_domain=1)
DCC_CONFIG_6 = 0,1,1 (seventh DCC, profile 0, network, enable)
339-1268/06
Navigation Page
242
Book Contents
OSIB.ini
**********************************
@OSI.ini@
[OSI_CONFIG]
PSAP = not_used ;
PRESENTATION = not_used ;
SSAP = not_used ;
SESSION = not_used ;
TSAP = not_used ;
TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8;
NSAP = 20, 4955555555555555555555555502051010100601 ;
NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2;
ISIS_SYS_ID = 6 , 020510101006 ;
ISIS_MAN_AREA_ADDR_0 = 13 , 49555555555555555555555555 ;
ISIS_MAN_AREA_ADDR_1 = 0 , ;
ISIS_MAN_AREA_ADDR_2 = 0 , ;
ISIS_NUM_RA_PREFIXES = 1 ;
ISIS_RA_PREFIX_0 = 1,1,20,49010203040506070809,20,000400000000;
ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111;
CLNS_PARAM = 0 , 0 , 3 ;
ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3;
MAC_ADDR = 020510101006 ;
DCC_PROFILE_0 =
1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_1 =
1513,1492,1,7,20,20,0,0,0,3,10,20,150,15,7,300,600,3;
DCC_PROFILE_2 =
1513,1492,1,7,20,20,0,0,1,3,10,20,150,15,7,300,600,3;
DCC_PROFILE_3 =
1513,1492,1,7,20,20,0,0,1,3,10,20,150,15,7,300,600,3;
DCC_CONFIG_0 = 0 , 0 , 0 ;
DCC_CONFIG_1 = 0 , 0 , 0 ;
DCC_CONFIG_2 = 0 , 0 , 0 ;
DCC_CONFIG_3 = 0 , 0 , 0 ;
DCC_CONFIG_4 = 0 , 0 , 1 ;
DCC_CONFIG_5 = 0 , 0 , 0 ;
DCC_CONFIG_6 = 0 , 0 , 0 ;
DCC_CONFIG_7 = 0 , 0 , 0 ;
#
~
**********************************
339-1268/06
Navigation Page
243
Book Contents
File notes
NSAP = 20, 4955555555555555555555555502051010100601
ISIS_NUM_RA_PREFIXES = 1 (number of configured prefixes)
ISIS_RA_PREFIX_0:
field RAP_id=1
field RAP_type=1 (point to point circuit)
field RAP_len=20
field RAP_addr=49010203040506070809
field RAP_metric=20
field RAP_cid=000400000000 (fifth DCC)
this prefix supplies to the equipment B the information necessary to connect to the equipment A (the
equipment A NSAP is: NSAP = 20, 4901020304050607080900004402052179710601)
CLNS_PARAM: field router_type=3 (area router)
DCC_PROFILE_0
(eighth field ext_domain=1)
1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3
ADM-64
ADM-64
339-1268/06
Navigation Page
244
Book Contents
OSIAMEt.ini
**********************************
@OSI.ini@
[OSI_CONFIG]
PSAP = not_used ;
PRESENTATION = not_used ;
SSAP = not_used ;
SESSION = not_used ;
TSAP = not_used ;
TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8;
NSAP = 20, 4901020304050607080900004402052179710601 ;
NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2;
ISIS_SYS_ID = 6 , 020521797106 ;
ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ;
ISIS_MAN_AREA_ADDR_1 = 0 , ;
ISIS_MAN_AREA_ADDR_2 = 0 , ;
ISIS_NUM_RA_PREFIXES = 1 ;
ISIS_RA_PREFIX_0 = 1,0,20,49555555555555555555,20,020510101006;
ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111;
CLNS_PARAM = 0 , 0 , 3 ;
ETH_CONFIG = 7,1,0,1,1492,20,20,64,64,3,1800,10,600,3;
MAC_ADDR = 020521797106 ;
DCC_PROFILE_0 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_1 =
1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_2 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_3 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_CONFIG_0 = 0 , 0 , 0 ;
DCC_CONFIG_1 = 0 , 0 , 0 ;
DCC_CONFIG_2 = 0 , 0 , 0 ;
DCC_CONFIG_3 = 0 , 0 , 0 ;
DCC_CONFIG_4 = 0 , 0 , 0 ;
DCC_CONFIG_5 = 0 , 0 , 0 ;
DCC_CONFIG_6 = 0 , 0 , 0 ;
DCC_CONFIG_7 = 0 , 0 , 0 ;
#
~**********************************
File notes
339-1268/06
Navigation Page
245
Book Contents
339-1268/06
Navigation Page
246
Book Contents
OSIBMEt.ini
**********************************
@OSI.ini@
[OSI_CONFIG]
PSAP = not_used ;
PRESENTATION = not_used ;
SSAP = not_used ;
SESSION = not_used ;
TSAP = not_used ;
TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8;
NSAP = 20, 4955555555555555555555555502051010100601 ;
NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2;
ISIS_SYS_ID = 6 , 020510101006 ;
ISIS_MAN_AREA_ADDR_0 = 13 , 49555555555555555555555555 ;
ISIS_MAN_AREA_ADDR_1 = 0 , ;
ISIS_MAN_AREA_ADDR_2 = 0 , ;
ISIS_NUM_RA_PREFIXES = 1 ;
ISIS_RA_PREFIX_0 = 1,0,20,49010203040506070809,20,020521797106;
ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111;
CLNS_PARAM = 0 , 0 , 3 ;
ETH_CONFIG = 7,1,0,1,1492,20,20,64,64,3,1800,10,600,3;
MAC_ADDR = 020510101006 ;
DCC_PROFILE_0 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_1 =
1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_2 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_3 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_CONFIG_0 = 0 , 0 , 0 ;
DCC_CONFIG_1 = 0 , 0 , 0 ;
DCC_CONFIG_2 = 0 , 0 , 0 ;
DCC_CONFIG_3 = 0 , 0 , 0 ;
DCC_CONFIG_4 = 0 , 0 , 0 ;
DCC_CONFIG_5 = 0 , 0 , 0 ;
DCC_CONFIG_6 = 0 , 0 , 0 ;
DCC_CONFIG_7 = 0 , 0 , 0 ;
#
~**********************************
File notes
339-1268/06
Navigation Page
247
Book Contents
339-1268/06
Navigation Page
248
Book Contents
OSIAM.ini
**********************************
@OSI.ini@
[OSI_CONFIG]
PSAP = not_used ;
PRESENTATION = not_used ;
SSAP = not_used ;
SESSION = not_used ;
TSAP = not_used ;
TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8;
NSAP = 20, 4901020304050607080900004402052179710601 ;
NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2;
ISIS_SYS_ID = 6 , 020521797106 ;
ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ;
ISIS_MAN_AREA_ADDR_1 = 0 , ;
ISIS_MAN_AREA_ADDR_2 = 0 , ;
ISIS_NUM_RA_PREFIXES = 1 ;
ISIS_RA_PREFIX_0 = 1, 3, 1, 020544444406, 20, 000600000000;
ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111;
CLNS_PARAM = 0 , 0 , 1 ;
ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3;
MAC_ADDR = 020521797106 ;
DCC_PROFILE_0 =
1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_1 =
1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_2 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_3 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_CONFIG_0 = 0 , 0 , 0 ;
DCC_CONFIG_1 = 0 , 0 , 0 ;
DCC_CONFIG_2 = 0 , 0 , 0 ;
DCC_CONFIG_3 = 0 , 0 , 0 ;
DCC_CONFIG_4 = 0 , 0 , 0 ;
DCC_CONFIG_5 = 0 , 0 , 0 ;
DCC_CONFIG_6 = 0 , 0 , 0 ;
DCC_CONFIG_7 = 0 , 0 , 0 ;
#
~**********************************
File notes
339-1268/06
Navigation Page
249
Book Contents
339-1268/06
Navigation Page
250
Book Contents
OSIBM.ini
**********************************
@OSI.ini@
[OSI_CONFIG]
PSAP = not_used ;
PRESENTATION = not_used ;
SSAP = not_used ;
SESSION = not_used ;
TSAP = not_used ;
TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8;
NSAP = 20, 4901020304050607080900004402054444440601 ;
NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2;
ISIS_SYS_ID = 6 , 020544444406 ;
ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ;
ISIS_MAN_AREA_ADDR_1 = 0 , ;
ISIS_MAN_AREA_ADDR_2 = 0 , ;
ISIS_NUM_RA_PREFIXES = 1 ;
ISIS_RA_PREFIX_0 = 1,3,1,020521797106,20,000400000000;
ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111;
CLNS_PARAM = 0 , 0 , 1 ;
ETH_CONFIG = 7,0,0,0,1492,20,20,64,64,3,1800,10,600,3;
MAC_ADDR = 020544444406 ;
DCC_PROFILE_0 =
1513,1492,1,7,20,20,0,1,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_1 =
1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_2 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_3 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_CONFIG_0 = 0 , 0 , 0 ;
DCC_CONFIG_1 = 0 , 0 , 0 ;
DCC_CONFIG_2 = 0 , 0 , 0 ;
DCC_CONFIG_3 = 0 , 0 , 0 ;
DCC_CONFIG_4 = 0 , 0 , 0 ;
DCC_CONFIG_5 = 0 , 0 , 0 ;
DCC_CONFIG_6 = 0 , 0 , 0 ;
DCC_CONFIG_7 = 0 , 0 , 0 ;
#
~**********************************
File notes
339-1268/06
Navigation Page
251
Book Contents
339-1268/06
Navigation Page
252
Book Contents
OSIAMEt.ini
**********************************
@OSI.ini@
[OSI_CONFIG]
PSAP = not_used ;
PRESENTATION = not_used ;
SSAP = not_used ;
SESSION = not_used ;
TSAP = not_used ;
TRANSPORT = 2,8,3,3000,120,120,120,750,1,100,8;
NSAP = 20, 4901020304050607080900004402052179710601 ;
NETWORK = 1492,1492,1,0,64,2,3,5,900,30,33,10,2,50,60,2;
ISIS_SYS_ID = 6 , 020521797106 ;
ISIS_MAN_AREA_ADDR_0 = 13 , 49010203040506070809000044 ;
ISIS_MAN_AREA_ADDR_1 = 0 , ;
ISIS_MAN_AREA_ADDR_2 = 0 , ;
ISIS_NUM_RA_PREFIXES = 1 ;
ISIS_RA_PREFIX_0 = 1, 2, 1, 020544444406, 20, 020544444406;
ISIS_RA_PREFIX_1 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_2 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_3 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_4 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_5 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_6 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_7 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_8 = 0,0,6,490102,20,000205111111;
ISIS_RA_PREFIX_9 = 0,0,6,490102,20,000205111111;
CLNS_PARAM = 0 , 0 , 1 ;
ETH_CONFIG = 7,1,0,1,1492,20,20,64,64,3,1800,10,600,3;
MAC_ADDR = 020521797106 ;
DCC_PROFILE_0 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_1 =
1513,1492,1,7,20,20,0,0,0,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_2 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_PROFILE_3 =
1513,1492,1,7,20,20,0,0,1,3,10,20,200,15,7,300,600,3;
DCC_CONFIG_0 = 0 , 0 , 0 ;
DCC_CONFIG_1 = 0 , 0 , 0 ;
DCC_CONFIG_2 = 0 , 0 , 0 ;
DCC_CONFIG_3 = 0 , 0 , 0 ;
DCC_CONFIG_4 = 0 , 0 , 0 ;
DCC_CONFIG_5 = 0 , 0 , 0 ;
DCC_CONFIG_6 = 0 , 0 , 0 ;
DCC_CONFIG_7 = 0 , 0 , 0 ;
#
~**********************************
File notes
339-1268/06
Navigation Page
253
Book Contents
Note
Note
Note
N_SHELF = 1
N_EXT_OUT = 32
N_EXT_IN = 4
N_LAMP = 11
GC_CONF = ONE_WIRE
ALARM_SHOW = YES
[B_INTERFACE]
OUT_1 = *,URG,*,*
339-1268/06
Navigation Page
254
Book Contents
OUT_2
OUT_3
OUT_4
OUT_5
OUT_6
OUT_7
OUT_8
OUT_9
OUT_10
OUT_11
OUT_12
OUT_13
OUT_14
OUT_15
OUT_16
OUT_17
OUT_18
OUT_23
OUT_24
OUT_28
[LAMP]
LAMP_1
LAMP_2
LAMP_3
LAMP_4
LAMP_5
LAMP_6
LAMP_7
LAMP_8
Note
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
*,NURG,*,*
*,IND,*,000001101000000000001
EXT,*,*,000001101000000000001
INT,*,*,000001101000000000001
*,IND,*,000000000111100000000
EXT,*,*,000000000111100000000
INT,*,*,000000000111100000000
*,IND,*,000000000000000001110
EXT,*,*,000000000000000001110
INT,*,*,000000000000000001110
*,IND,*,011000000000000000000
EXT,*,*,011000000000000000000
INT,*,*,011000000000000000000
*,IND,*,000110000000000000000
EXT,*,*,000110000000000000000
INT,*,*,000110000000000000000
*,*,30,*
*,*,29,*
*,URG,*,000000000000000100000
*,URG,*,000000000000011110000
=
=
=
=
=
=
=
=
*,*,*,*
MEM,*,*,*
*,URG,*,*
*,NURG,*,*
INT,*,*,*
EXT,*,*,*
*,IND,*,*
ABN,*,*,*
In the following table are listed the default values for the fields:
EQ_TYPE, N_SLOT
EQ_NAME
EQ_TYPE
N_SLOT
ADM-4
MSH41C
ADM
16
ADM_16
MSH51C
ADM
26
ADM-64
MSH64
ADM
15
MSH53C
REG
MSH63
REG
REG-4/16
REG-64
EQ_NAME,
NOTICE
If a field is empty or not present, the equipment uses the default value.
MAIN section
n INST_TYPE: distinguish Name Type; the value is GLOBAL or LOCAL (default is LOCAL).
With MV36 the value LOCAL must be used;
n HIDDEN: if the value is 1 then the attributes in Information Model added in the equipment
are hidden to Manager : in this way the Q interface is fully standard; if 0 the attributes are
not hidden (default is 0). With MV36 the value 0 must be used;
339-1268/06
Navigation Page
255
Book Contents
n F4TIME: it is the integration time in seconds for F4 filter, that is the time an alarm must stay
on or off in order to be reported or cleared by the controller unit. It may vary from 1 second
to 20 seconds (default is 3 seconds);
n DELAY: Delay time to wait after a message is send to the management (in milliseconds).
Default value is 0, that is there is no wait; using a value different from 0 slows down the
equipment management (such behaviour may be useful with some management centre too
slow: this is not the case for MV36);
n DEBUG: if this option is ON the debugging mode is enabled. Default is OFF. The use of this
option is reserved to lab personnel.
CONFIG section
n EQ_NAME: Equipment Name (for the default value see Tab. -1);
n EQ_TYPE: Equipment Type. For the ADM-4 and ADM-16 the value may be ADM or REG
(default is ADM). If ADM is selected the equipment acts as an Add Drop Multiplexer allowing
cross connections and the use of matrix unit. If REG is selected, the equipment acts as a
Regenerator. For the ADM-64 the value is always ADM and for the REG-4/16 and REG-64
is always REG.
n N_SHELF: Managed shelf number (for the default value see Tab. -1);
n N_SLOT: Slot number in the shelf (for the default value see Tab. -1);
n N_EXT_OUT: Number of outgoing Ground Contacts; default is 32 for One Wire Ground
Contacts; in Two Wire case, the number is 11;
n N_EXT_IN: Number of incoming Ground Contacts (default is 4);
n N_LAMP: Number of lamps in End Of Shelf card, managed by the equipment (default is 8);
n GC_CONF: Type of outgoing Ground Contacts; there are two cases: ONE_WIRE and
TWO_WIRE (default is ONE_WIRE). In case of TWO_WIRE contacts, the number
N_EXT_OUT must be 11;
n ALARM_SHOW: this option offers the possibility to enable/disable the LED indication by
means of EOS LEDs in case of acknowledged alarm. The value may be YES or NOT;
n RACK_LAMP: The RAU, fitted with three LEDs, can be set according to three
configurations:
339-1268/06
Navigation Page
256
Book Contents
Configur
ation
A
LEFT LED
LED Colour
Meaning
Red
Urgent
MIDDLE LED
LED Colour
Yellow or
Meaning
Not Urgent
Green
B
Red
Red
RIGHT LED
LED Colour
Green or
Meaning
(*)
Yellow
Any active
Green or
EOW call
alarm
Red
received
Urgent or
Yellow
Indicative
Yellow
Green
(*)
(*)
Not
Urgent
Note(*)
B_INTERFACE section
n OUT_N: it describes the characteristic of the N-Th Ground Contact, that is the conditions
affecting the status of the ground contact. There are 4 comma-separated fields, which
mean: alarm type (EXT, INT, ABN, MEM), alarm severity (URG, NURG, IND); alarm
probable cause numeric code; bit mask defining the cards involved; if a field has "*" value,
then it means DONT_CARE (any value are possible).
LAMP section
n LAMP_N: See description for B_INTERFACE section.
339-1268/06
Navigation Page
257
Book Contents
N (Ports)
N (AU)
ADM-64
ADM-16
ADM-4
STM-64 Opt
1 to 64
STM-16 Opt
1 to 16
STM-4 Opt
1 to 4
STM-1 Opt
STM-1 El
1x140/155Mbit/s
(VC-12) El
2xSTM-1 Opt
1 to 2
2x140/155Mbit/s
(VC-4) El
1 to 2
2x140/155Mbit/s
(VC-12) El
1 to 2
4xSTM-1 Opt
1 to 4
4x140/155M
1 to 4
3x34/45Mbit/s
1 to 3
32x1,5/2Mbit/s
1 to 32
63x1,5/2Mbit/s
1 to 63
Booster +17
Preamplifier
REG-64
REG-16
X
X
bit/s (VC-4) El
339-1268/06
Navigation Page
Book Contents
2 Channel
WDM
Gigabit
Unit
Bidir.
Ethernet
1 to 2
X
X
The alarms can refer to the Regenerator or Multiplex Section which letter x can be:
n x = R: Regenerator Section
n x = M: Multiplex Section
In case of ADM 4 the alarms can refer to the TU, which multiplex level y can be:
n y = 12, 2, or 3 for the STM-4 Optical/Mux Unit, STM-1 Optical/Mux Unit, STM-1
Electrical/Mux Unit, 2xSTM-1 Optical/Mux Unit, 2x140/155Mbit/s (VC-12) Tributary Unit and
1x140/155Mbit/s (VC-12) Tributary Unit (when the last two units are set as SDH interfaces).
In case of ADM 4, the alarms can refer to the VC, which multiplex level y can be:
n y = 4 for the 2x140/155Mbit/s (VC-4) Tributary Unit, 2x140/155Mbit/s (VC-12) Tributary Unit
and 1x140/155Mbit/s (VC-12) Tributary Unit (when these units are set as PDH interfaces);
n y = 4 when the alarmed AU-4 is demultiplexed at lower levels for the STM-4 Optical/Mux
Unit, STM-1 Optical/Mux Unit, STM-1 Electrical/Mux Unit, 2xSTM-1 Optical/Mux Unit,
2x140/155Mbit/s (VC-12) Tributary Unit and 1x140/155Mbit/s (VC-12) Tributary Unit (when
the last two units are set as SDH interfaces);
n y = 3 for the 3x34Mbit/s Tributary Unit and 3x45Mbit/s Tributary Unit;
n y = 12 for the (16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit and
63x1.5/2Mbit/s Tributary Unit.
NOTICE
ADM 64 and ADM 16 are able to manage VC-4 level only then, relevant to these
equipment, this field is meaningless because it always has the value 4.
The alarms can refer to the LTU (Line Termination Unit) which number w can be:
n w =1 for the STM-1 Electrical/Mux Unit, 2x140/155Mbit/s (VC-4) Tributary Unit,
2x140/155Mbit/s (VC-12) Tributary Unit, 1x140/155Mbit/s (VC-12) Tributary Unit, 3x34Mbit/s
Tributary Unit and 3x45Mbit/s Tributary Unit;
n w =4 for the (16+16)x1.5/2Mbit/s Tributary Unit and 32x1.5/2Mbit/s Tributary Unit;
n w =8 for the 63x1.5/2Mbit/s Tributary Unit.
339-1268/06
Navigation Page
259
Book Contents
The alarms are detected by functional blocks on the units shown in the following diagram.
LINE
Rx
RS
RS
Rx
Rx
RS
MS
Rx
Rx
MATRIX
AU4/VC4
Rx
TRIBUTARY SDH
RS
TUy
TUy
Tx
Rx
Rx
RS
MS
RS
AU4
Rx
Tx
RS
RS
RS
MS
Tx
Tx
Rx
Rx
RS
Tx
Rx
LT
U
(*)
INT
INT
Tx
RS
Tx
Rx
Tx
AU4
Tx
RS
TUy
TUy
Rx
Rx
Tx
AU4/VC4
Rx
RS
Rx
MS
Rx
RS
Rx
Rx
TRIBUTARY PDH
2, 34, 45Mb/s
PDH
Tx
VCy
Tx
LT
U
(*)
INT
VCy
Rx
TRIBUTARY PDH
nx140Mb/s
AU4
Tx
VC4
Tx
LT
U
(*)
INT
VC4
Rx
PDH
Tx
PDH
Rx
ALARM TYPES
In the following all the alarms detected are reported.
AU4: n AIS
Severity: INDICATIVE
Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
Detected on the AU4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as
PDH interface).
This is an Administrative Unit Alarm Indication Signal received from the remote equipment; AU-AIS
defect is detected when all "1" in the entire AU including AU pointer are observed (for three frames).
In case of PDH unit:
339-1268/06
Navigation Page
260
Book Contents
Problem:
1.
Consequence of the following alarms: LOS, LOF, MS-EXC, MS-AIS, RS-TIM detected
on the STM-N unit which is providing the incoming VC4 to the PDH unit
2.
3.
Failure on the STM-N unit which is providing the incoming VC4 to the PDH unit
Action:
1.
2.
Perform a forced switch to the protecting switch unit. If the alarm goes off, problem on
the switch unit and follow:
Unit Internal Fault Trouble-Shooting Procedure
3.
Check the status of the STM-N unit which is providing the incoming VC4 to the PDH unit
1.
AU4: n DEG
Severity: NOT URGENT
Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
Detected on the AU4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as
PDH interface).
This is an indication of a bit error rate from e10-5 to e10-9 (threshold pre-settable via Software) on
the received high level payload (check on B3 byte) on port n.
This alarm can be detected when the relevant AU-4 is under monitor (AU-4 monitor enabled via
Software).
Problem:
1.
2.
1.
Check if the same alarm is detected at the termination of the path. If the alarm is
DETECTED, follow:
Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG)
2.
Check if the same alarm is detected at the termination of the path. If the alarm is NOT
DETECTED, follow:
Unit Internal Fault Trouble-Shooting Procedure
339-1268/06
Navigation Page
261
Book Contents
AU4: n EXC
Severity: URGENT
Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
This is an indication of a bit error rate e10-3 on the received high level payload (check on B3 byte)
on port n or AU-4 n.
This alarm can be detected when the relevant AU-4 is under monitor (AU-4 monitor enabled via
Software).
Problem:
1.
2.
339-1268/06
Navigation Page
262
Book Contents
Action:
1.
Check if the same alarm is detected at the termination of the path. If the alarm is
DETECTED, follow:
Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG)
2.
Check if the same alarm is detected at the termination of the path. If the alarm is NOT
DETECTED, follow:
Unit Internal Fault Trouble-Shooting Procedure
AU4: n LOP
Severity: URGENT
Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
This alarm is an indication of a Loss Of Administrative Unit Pointer on port n or AU-4 n.
Problem:
1.
Transmitter of the far-end equipment is configured for a different multiplexing path
(AU3/AU4) or for a different standard (SONET/SDH)
2.
1.
2.
Use the Software to check the local configuration, check the remote configuration
Proceed as described in:
SDH LOS Fault Trouble-Shooting Procedure
AU4: n RDI
Severity: INDICATIVE
Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
This is a High Order Remote Defect Indication on port n or AU-4 n received from the remote
multiplexer.
This alarm can be detected when the relevant AU-4 is under monitor (AU-4 monitor enabled via
Software).
It indicates that the far-end port has detected some problems into the received stream.
Problem:
1.
339-1268/06
Navigation Page
263
Book Contents
Action:
1.
Check the status of the far-end port and follow the Fault Detection Procedure for the
detected alarm.
AU4: n TIM
Severity: URGENT
Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
This is an indication of a mismatch between the received and expected J1 Trace Identifier on port n
or AU-4 n.
This alarm can be detected when the relevant AU-4 is under monitor (AU-4 monitor enabled via
Software).
Problem:
1.
1.
Check, using the Software facilities, the local and destination J1 equipment configuration
and the status of the intermediate Digital Cross-connector Equipment
AU4: n UNEQ
Severity: URGENT
Detected on the AU4 Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
The UNEQUIPPED indicates that in the far-end equipment the AU-4 on port n or AU-4 n is not
connected. The unexpected reception of AU-4 unequipped indicates that a connection error has
occurred on the path.
This alarm can be detected when the relevant AU-4 is under monitor (AU-4 monitor enabled via
Software).
Action:
1.
Buffer Overflow
Severity: URGENT
Detected on the VC-4 Rx block of the following units: Gigabit Ethernet Units and .STM-16 for VC4-4c/4v and 16c/16v Units
This alarm indicates that one or more channels are missing in a group of virtual VC-4 connection.
Problem:
1. Wrong Virtual VC-4 configuration or problem in the Virtual VC-4
Action:
1. Check the Virtual VC-4 configuration and the status of the Virtual VC-4
339-1268/06
Navigation Page
264
Book Contents
DC/DC 1 Fault
Severity: URGENT
Detected on: Communication and Control Unit
Action:
1.
DC/DC 2 Fault
Severity: INDICATIVE
Detected on: Communication and Control Unit
Action:
1.
2.
3.
1.
Using the Software check the local and remote LAPD configuration for the STM-N
interfaces (NETWORK must be connected to USER and vice-versa)
2.
3.
Disparity Fail
Severity: NOT URGENT
Detected on the MS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
There is a problem of communication with the Auxiliary Unit concerning auxiliary channels on port n.
Problem:
1.
339-1268/06
Navigation Page
265
Book Contents
Missing Unit
Unit Fail
2.
1.
2.
Fan Fail
Severity: NOT URGENT
Detected on: Communication and Control Unit.
This alarm indicates a failure in the Environmental Control Unit.
Problem:
1.
Both the two Power Supply for Environmental Control Units are faulty or switched off
2.
3.
339-1268/06
Navigation Page
266
Book Contents
1.
Check that the Power Supply for Environmental Control Units are working properly
2.
3.
Replace the faulty Environmental Control Unit(s) with the spare one(s)
FEC_DEGRADE
Severity: NOT URGENT
Detected on the Rx block of the STM-64 G.709 Units.
This is an indication of the number of corrected errors in one second exceeds the threshold of X
errors, X is presettable via Software in the range from 10-5 to 10 6 equivalent to BER of e10-15 to
e10-4.
Problem:
1.
2.
1.
High Temperature
Severity: URGENT
Detected on: Communication and Control Unit.
Action:
1.
339-1268/06
Navigation Page
267
Book Contents
Action:
1.
1.
1.
1.
339-1268/06
Navigation Page
268
Book Contents
This alarm indicates that the laser transmission power has been configured, via Software, too low
(less than -12dBm).
Problem:
1.
1.
Loss of Sequencing
Severity: URGENT
Detected on the VC-4 Rx block of the following units: Gigabit Ethernet Units and .STM-16 for VC4-4c/4v and 16c/16v Units
Loss of Sequence defect is detected if the accepted sequence number does not match the
expected sequence number. The received sequence number is recovered from the H4 byte, bits 14 in multiframe 14 and 15.
Problem:
1. The number of received multiframes with not correct sequence number has exceeded the
threshold set.
Action:
1. Check the far-end equipment where the VC-4s come from and their paths.
LTU w Fail
Severity: URGENT
Detected on the Rx block of the following units: STM-1 Electrical/Mux Unit, Nx140/155Mbit/s
Tributary Unit, 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary Unit, (16+16)x1.5/2Mbit/s Tributary
Unit, 32x1.5/2Mbit/s Tributary Unit and 63x1.5/2Mbit/s Tributary Unit..
This is an indication of Line Terminal Unit malfunction.
The Line Terminal Unit, according to the connected traffic unit, can be:
339-1268/06
Navigation Page
269
Book Contents
n 140/155Mbit/s Connection Unit for the STM-1 Electrical/Mux Unit and for 1x140/155Mbit/s
(VC-12) Tributary Unit;
n 2x140/155Mbit/s Connection Unit for the 2x140/155Mbit/s (VC-4) Tributary Unit and
2x140/155Mbit/s (VC-12) Tributary Unit;
n 4x34/45Mbit/s Connection Unit for the 3x34Mbit/s Tributary Unit and 3x45Mbit/s Tributary
Unit;
n Tx 16x2Mbit/s Connection Unit and Rx 16x2Mbit/s Connection Unit for the
(16+16)x1.5/2Mbit/s Tributary Unit, 32x1.5/2Mbit/s Tributary Unit and 63x1.5/2Mbit/s
Tributary Unit.
Problem:
1.
2.
3.
1.
2.
Check whether all pins of the male subrack connector corresponding to the alarmed
connection unit are straight
3.
The numbering of the Line Terminal Units will follow the physical position into the subrack according
to the figure shown below.
L L L L
L L
T T T T
U U U U
T T
U U
2 4 6 8
2 4
T
1
L L L L
L L
T T T T
T T
U U U U
U U
1 x 140/155Mbit/s
1 3 5 7
1 3
2 x 140/155Mbit/s
1 x 155Mbit/s
3 x 34Mbit/s
63 x 1.5/2Mbit/s
32 x 1.5/2Mbit/s
3 x 45Mbit/s
339-1268/06
Navigation Page
270
Book Contents
L L L L L L L L L L L L
T T T T T T T T T T T T
U U U U U U U U U U U U
1 2 3 4 5 6 7 8 9 10 11 12
4x140/155Mbit/s
9 10
For ADM-64 the LTU numbering does not follow any particular rule because the equipment
managed only one unit that needs the connectors interface: the 4x140/155Mbit/s electrical unit.
Missing Unit
Severity: NOT URGENT
Detected on: all the units excepted for the Communication and Control Unit.
This alarm indicates that a unit, configured into the database, it is not inserted.
Problem:
1.
2.
1.
2.
Check whether all pins of the male subrack connector corresponding to the alarmed unit
are straight
1.
339-1268/06
Navigation Page
271
Book Contents
2.
339-1268/06
Navigation Page
272
Book Contents
Action:
1.
2.
MS: n AIS
Severity: INDICATIVE
Detected on the MS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
This is an Alarm Indication Signal, on Multiplex Section port, received from a remote regenerator
equipment on the port n (the pattern 111 is observed in bits 6,7 and 8 of K2 byte in at least 3
consecutive frames).
Problem:
1.
Fault on the reception side of the far-end regenerator or the far-end regenerator has
detected some problems into the received stream
Action:
1.
MS: DAC
Severity: URGENT
Default APS Code, it is risen when the default value of APS Code (k1 and k2 are equal zero ) for
three consecutive frames.
Problem:
1. Internal failure on the local or far-end protection Line Unit
Action:
1. Proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
MS: n DEG
Severity: NOT URGENT
Detected on the MS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
This is an indication of a bit error rate from e10-5 to e10-9 (threshold presettable via Software) on
the Multiplex Section port n. in the received signal (check on B2 byte).
Problem:
1.
2.
339-1268/06
Navigation Page
273
Book Contents
Action:
1.
2.
MS: n EXC
Severity: URGENT
Detected on the MS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
This is an indication of a bit error rate e10-3 on the Multiplex Section port n in the received signal
(check on B2 byte).
Problem:
1.
2.
1.
2.
MS: IAC
Severity: URGENT
Improper APS Code, it is risen when the received APS value is wrong for three consecutive
frames.
Problem:
1. Internal failure on the local or far-end protection Line Unit
Action:
1. Proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
MS: INV
Severity: URGENT
Invalid APS (Automatic Protection Switch) protocol (MSP). Mismatch between the expected value of
the received K2 (bits 1 to 5 of byte K2) and sent K1 byte. MSP bytes is accepted as valid only when
identical bytes are received in three consecutive frames
339-1268/06
Navigation Page
274
Book Contents
Note
MS: NIM
Severity: URGENT
Node Id Mismatch, it is raised when the fields relevant to the source and destination node id in the
byte k1 and k2 are mismatching for three consecutive frames.
Problem:
1. Internal failure on the local or far-end protection Line Unit
Action:
1. Proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
MS: PAM
Severity: URGENT
Multiplex Section Protection Architecture Mismatch. Mismatch between the MSP (multiplexing
section protection) architecture configuration (1+1, 1:N or 1+N)
Problem:
1. Wrong MSP configuration
Action:
1. Check with the Control Application the local MSP configuration
Check the far-end MSP configuration
MS: n RDI
Severity: INDICATIVE
Detected on the MS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
This is a Remote Defect Indication on the Multiplex Section port, received from the remote
multiplexer on the port n (the pattern 110 is observed in bits 6,7 and 8 of K2 byte in at least 3
consecutive frames).
339-1268/06
Navigation Page
275
Book Contents
It indicates that the far-end multiplexer equipment has detected some problems into the received
stream.
Problem:
1.
1.
Check the alarm status of the far-end multiplexer equipment and follow the trouble
shooting procedure for the detected alarm
Note(*)
The MS: n RDI alarm can be detected in case of LOS only if the Automatic Laser
Shutdown is not enabled or in case of electrical interface.
MS: SCM
Severity: URGENT
Selector Control Mismatch, it is risen when the far-end equipment sends a signalling of executed
bridge for a different channel from the request one. It must persist over more 50ms.
Problem:
1. Internal failure on the local or far-end protection Line Unit
Action:
1. Proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
MS: TMOUT
Severity: URGENT
It is risen when the tail-end does not get the answer from the head-end (the Reverse Request) by
50ms
Problem:
1. Internal failure on the local or far-end protection Line Unit
Action:
1. Proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
OCH-AIS
Severity: INDICATIVE
Detected on the Rx block of the STM-64 G.709 Units.
339-1268/06
Navigation Page
276
Book Contents
This is an Alarm Indication Signal on the Optical Channel layer received from the remote equipment.
Problem:
1.
Fault on the reception side of the far-end equipment or the far-end equipment has
detected some problems into the received stream
Action:
1.
OCH-LOF
Severity: URGENT
Detected on the Rx block of the STM-64 G.709 Units.
This is a Loss of Frame alarm detected at the Optical Channel layer.
Action:
1.
OCH-LOM
Severity: URGENT
Detected on the Rx block of the STM-64 G.709 Units.
This is a Loss of Multi-frame alarm detected at the Optical Channel layer.
Action:
1.
OTU-TIM
Severity: URGENT
Detected on the Rx block of the STM-64 G.709 Units.
This is an indication of a Source Access Point Identifier Mismatch.
Problem:
1.
Transmitter on the far-end equipment configured with a different path trace identifier
from the expected one
Action:
1.
Check, using the Software, that the remote transmitted SAPI is configured as the local
expected one
OTU-BDI
Severity: INDICATIVE
Detected on the Rx block of the STM-64 G.709 Units.
This is a Backward Defect Indication received from the remote equipment.
Problem:
339-1268/06
Navigation Page
277
Book Contents
1. The far-end equipment has detected some problems into the received stream
Action:
1.
Check the alarm status of the far-end equipment and follow the trouble shooting
procedure for the detected alarm
OTU-SSF
Severity: INDICATIVE
Detected on the Rx block of the STM-64 G.709 Units.
This is an indication of Server Signal Failure at the Optical channel Transport Unit layer.
Problem:
1. Problem on the Optical Physical Section in the trail termination
Action:
1. Check the status of the Optical Physical Section in the trail termination
ODU-AIS
Severity: INDICATIVE
Detected on the Rx block of the STM-64 G.709 Units.
This is an Alarm Indication Signal at the Optical Channel Data Unit layer.
Problem:
1.
1.
ODU-BDI
Severity: INDICATIVE
Detected on the Rx block of the STM-64 G.709 Units.
This is a Backward Defect Indication received from the remote equipment.
Problem:
1. The far-end equipment has detected some problems into the received stream
Action:
1.
Check the alarm status of the far-end equipment and follow the trouble shooting
procedure for the detected alarm
ODU-SSF
Severity: INDICATIVE
Detected on the Rx block of the STM-64 G.709 Units.
This is an indication of Server Signal Failure at the Optical channel Data Unit layer, this alarm is
generated when the OTU-TIM is detected.
Action:
339-1268/06
Navigation Page
278
Book Contents
ODU-OCI
Severity: URGENT
Detected on the Rx block of the STM-64 G.709 Units.
This is an Open Connection Indication and indicates that the connection in an upstream element is
open.
Action:
1.
ODU-TIM
Severity: URGENT
Detected on the Rx block of the STM-64 G.709 Units.
This is an indication of a Source Access Point Identifier Mismatch.
Problem:
1.
Transmitter on the far-end equipment configured with a different path trace identifier
from the expected one
Action:
1.
Check, using the Software, that the remote transmitted SAPI is configured as the local
expected one
ODU-PLM
Severity: URGENT
Detected on the Rx block of the STM-64 G.709 Units.
This is an indication of a Source Access Point Identifier Mismatch.
Problem:
1.
Transmitter on the far-end equipment configured with a different path trace identifier
from the expected one
Action:
1.
Check, using the Software, that the remote transmitted SAPI is configured as the local
expected one
OH Bus Rx Fail
Severity: INDICATIVE
Detected on the INT block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH
interfaces).
This is an indication of mismatch during the parity check on the Rx overhead bus.
Problem:
1.
339-1268/06
Navigation Page
279
Book Contents
Action:
1.
OH Bus Tx Fail
Severity: INDICATIVE
Detected on the INT block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as SDH
interfaces).
This is an indication of mismatch during the parity check on the Tx overhead bus.
Problem:
1.
Unit internal failure
Action:
1.
Proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
OR Batt
Severity: NOT URGENT
Detected on: Communication and Control Unit.
This is an indication of loss of power supply from one of the two batteries.
1.
1.
Problem:
Power supply cable disconnected or loss of power supply
Action:
Plug the power supply cable; check fuses, breakers and battery
1.
Problem:
Plug module not fitted
Problems with the insertion of the module
Action:
Insert the missing plug module
2.
1.
2.
339-1268/06
Navigation Page
280
Book Contents
Due to the crossing of the protection switches threshold, it is possible that the Control Application
does not report the current data of the unit protection status.
1.
Action:
Restart the Control and Communication Unit to realign the reports
Power Fail
Detected on the INT block of the following units: all the unit of the equipment excepted for the
Communication and Control Unit.
This is an indication of on board DC/DC converter faulty.
Problem:
1.
1.
2.
1.
2.
Problem:
Wrong transmission power configuration of far-end equipment
2.
3.
4.
339-1268/06
Navigation Page
281
Book Contents
1.
2.
3.
4.
2.
1.
2.
2.
1.
2.
339-1268/06
Navigation Page
282
Book Contents
2.
1.
2.
RS: 1 DEG
Severity: NOT URGENT
Detected on the RS Rx block of the STM-4 and STM-16 Optical/Mux Unit, when the equipment is
configured as regenerator only and on the RS Rx block of the STM-64 in the REG-64.
This is an indication of a bit error rate e from 10-5 to 10-9 (threshold presettable via software) on the
Regenerator Section port 1, in the received signal (check on B1 byte).
Problem:
1.
1.
RS: 1 EXC
Severity: URGENT
Detected on the RS Rx block of the STM-4 and STM-16 Optical/Mux Unit, when the equipment is
configured as regenerator only and on the RS Rx block of the STM-64 in the REG-64.
This is an indication of a bit error rate e10-3 on the Regenerator Section port 1 in the received signal
(check on B1 byte).
339-1268/06
Navigation Page
283
Book Contents
Problem:
1.
1.
RS: n LOF
Severity: URGENT
Detected on the RS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
This is a Loss of Frame alarm detected at the incoming Regenerator Section of port n.
Action:
1.
RS: n TIM
Severity: URGENT
Detected on the RS Rx block of the STM-N and NxSTM-1 units (or Nx140/155Mbit/s units set as
SDH interfaces).
This is an indication of a J0 Trace Identifier Mismatch on Regenerator Section port n.
Problem:
1.
Transmitter on the far-end equipment configured with a different path trace identifier
from the expected one
Action:
1.
Check, using the Software, that the remote transmitted J0 is configured as the local
expected one
Sync Fail
Severity: NOT URGENT
Detected on: Communication and Control Unit.
The clock signal extracted from the Rx interface of one port or one 2MHz/2Mbit/s external
synchronisation source input is missing.
Problem:
1.
2.
3.
339-1268/06
Navigation Page
284
Book Contents
4.
1.
2.
3.
4.
Check the external synchronisation source input cable and the external clock generator.
T. PDH: n AIS
Severity: INDICATIVE
Detected on the PDH Rx block of the following unit: (16+16)x1.5/2Mbit/s Tributary Unit,
32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s G.703/G.704 CRC-4
Tributary Unit, 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary Unit and Nx140/155Mbit/s Tributary
Unit (when set as PDH interface).
This is a Termination PDH - Alarm Indication Signal on port n, received from the connected PDH
equipment.
Action:
1.
Check the alarm status of the PDH equipment connected to the local Tributary Unit
T. PDH: n DEG
Severity: NOT URGENT
Detected on the PDH Rx block of the following unit: 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary
Unit and Nx140/155Mbit/s Tributary Unit (when set as PDH interface).
This is an indication of a bit error rate from e10-5 to e10-9 (threshold presettable via Software) on
the received PDH stream port n.
Problem:
1.
1.
339-1268/06
Navigation Page
285
Book Contents
Problem:
1.
1.
1.
Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG and MS EXC/DEG)
T. PDH: n EXC
Severity: URGENT
Detected on the PDH Rx block of the following unit: 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary
Unit and Nx140/155Mbit/s Tributary Unit (when set as PDH interface).
This is an indication of a bit error Rate e10-3 on the received PDH stream on port n.
Problem:
1.
1.
339-1268/06
Navigation Page
286
Book Contents
Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG and MS
EXC/DEG)
1.
1.
Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG and MS EXC/DEG)
T. PDH: n LOF
Severity: URGENT
Detected on the PDH Rx block of the following unit: 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary
Unit and Nx140/155Mbit/s Tributary Unit (when set as framed PDH interface).
This is a Loss of Frame alarm detected at the incoming circuit level over a PDH framed signal in
accordance ITU G751 on port n.
Action:
339-1268/06
Navigation Page
287
Book Contents
1.
T. PDH: n LOS
Severity: URGENT
Detected on the PDH Rx block of the following unit: (16+16)x1.5/2Mbit/s Tributary Unit,
32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s G.703/G.704 CRC-4
Tributary Unit, 3x34Mbit/s Tributary Unit, 3x45Mbit/s Tributary Unit and Nx140/155Mbit/s Tributary
Unit (when set as PDH interface).
This is a Loss of Signal alarm detected at the incoming circuit level over a PDH signal on port n.
Action:
1.
339-1268/06
Navigation Page
288
Book Contents
Problem:
1. Excessive bit error rate or failures along the line which connects the local tributary output and
the remote PDH equipment
Action:
1. Check the line and the PDH equipment status
1.
Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG and MS EXC/DEG)
339-1268/06
Navigation Page
289
Book Contents
This is an indication of a bit error Rate e10-3 on the received PDH stream, from the matrix side,
connected to the port n.
Problem:
1.
1.
Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG and MS EXC/DEG)
T. PDH: n Tx Fail
Severity: URGENT
Detected on the PDH Tx block of the following unit: (16+16)x1.5/2Mbit/s Tributary Unit,
32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit, 3x45Mbit/s
Tributary Unit and Nx140/155Mbit/s Tributary Unit (when set as PDH interface).
339-1268/06
Navigation Page
290
Book Contents
This alarm indicates that the Tx output circuit of the port n is not working properly.
Problem:
1.
1.
T. SDH: n LOS
Severity: URGENT
Detected on the SDH Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH
interfaces), Preamplifier and Booster Unit.
This is a Loss of Signal alarm detected at the incoming circuit level over a SDH signal on port n.
Action:
1.
If the involved unit is a 4x140/155Mbit/s Tributary Unit or a STM-N Optical/Mux Unit,
proceed as indicated in:
SDH LOS Fault Trouble-Shooting Procedure
1.
If the involved unit is a Preamplifier Unit or Booster Unit, proceed as indicated in:
Preamplifier and Booster LOS Fault Trouble-Shooting Procedure
TC: n DEG
Severity: NOT URGENT
Detected on the VC-4 Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH
interfaces).
This is an indication of a bit error rate e from 10-5 to 10-9 (threshold presettable via software) on the
received high level payload on port n or VC-4 n, between the end points of the Tandem Connection.
Problem:
1.
2.
1.
Check if the same alarm is detected at the termination of the path. If the alarm is
DETECTED, follow:
Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG)
2.
Check if the same alarm is detected at the termination of the path. If the alarm is NOT
DETECTED, follow:
Unit Internal Fault Trouble-Shooting Procedure
TC: n EXC
Severity: URGENT
339-1268/06
Navigation Page
291
Book Contents
Detected on the VC-4 Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH
interfaces).
This is an indication of a bit error rate e10-3 on the received high level payload on port n or VC-4 n,
between the end points of the Tandem Connection.
Problem:
1.
2.
1.
Check if the same alarm is detected at the termination of the path. If the alarm is
DETECTED, follow:
Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG)
2.
Check if the same alarm is detected at the termination of the path. If the alarm is NOT
DETECTED, follow:
Unit Internal Fault Trouble-Shooting Procedure
TC: n IncAIS
Severity: URGENT
Detected on the VC-4 Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH
interfaces).
This alarm indicates that a defect is present on the VC before the input end point of the Tandem
Connection. It indicates that there are not defects on the Tandem Connection path.
Problem:
1.
Failure in the far-end equipment before the input end point of the Tandem Connection
Action:
1.
Check the status of the far-end equipment before the input end point of the Tandem
Connection
TC: n UNEQ
Severity: URGENT
Detected on the VC-4 Rx block of the STM-N, NxSTM-1 units (or Nx140/155Mbit/s units set as SDH
interfaces).
The UNEQUIPPED indicates that the VC-4 on port n or VC-4 n is not connected, via switching
matrix, to any source point. The unexpected reception of VC unequipped indicates that a connection
error has occurred on the Tandem Connection path or indicates that the TC receive side
(termination point) has been enabled while the TC transmit side is disabled (generation point).
Action:
1.
339-1268/06
Navigation Page
292
Book Contents
339-1268/06
Navigation Page
293
Book Contents
2.
Check if the same alarm is detected at the termination of the path. If the ALARM NOT
DETECTED, proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
2.
Tx Fail
Severity: URGENT
Detected on the Tx block of the STM-N and NxSTM-1 Optical units, Preamplifier and Booster Unit.
This alarm indicates failure of the laser module.
Problem:
1.
1.
Unit Fail
Severity: URGENT
Detected on the INT block of all the units excepted for the Communication and Control Unit.
This alarm indicates an unit internal failure.
Problem:
1.
1.
339-1268/06
Navigation Page
294
Book Contents
This alarm indicates mismatch between the database unit type commission and the unit inserted.
Problem:
1.
1.
Check the configuration and the inserted unit, replace the unit or change the database
according to the required configuration
VC4: n DEG
Severity: NOT URGENT
Detected on the VC-4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as
PDH interface).
This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as
SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active.
This is an indication of a bit error rate from e10-5 to e10-9 (threshold presettable via Software) on
the received high level payload (check performed by BIP-8 on B3 byte) on port n or VC-4 n.
Problem:
1.
2.
1.
Check if the same alarm is detected at the termination of the path. If the alarm is
DETECTED, follow:
Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG)
2.
Check if the same alarm is detected at the termination of the path. If the alarm is NOT
DETECTED, follow:
Unit Internal Fault Trouble-Shooting Procedure
VC4: n EXC
Severity: URGENT
Detected on the VC-4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as
PDH interface).
This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as
SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active.
This is an indication of a bit error rate e10-3 on the received high or low level payload (check on B3
byte) on port n or VC-4 n.
Problem:
1.
339-1268/06
Navigation Page
295
Book Contents
1.
Check if the same alarm is detected at the termination of the path. If the alarm is
DETECTED, follow:
Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG)
2.
Check if the same alarm is detected at the termination of the path. If the alarm is NOT
DETECTED, follow:
Unit Internal Fault Trouble-Shooting Procedure
VC4: n LOM
Severity: URGENT
Detected on the VC-4 Rx block of the following units: STM-4 Optical/Mux Unit, 2xSTM-1
Optical/Mux Unit, STM-1 Optical/Mux Unit, STM-1 Electrical/Mux Unit, 2x140/155Mbit/s (VC-12)
Tributary Unit, and 1x140/155Mbit/s (VC-12) Tributary Unit (when the last two units are set as SDH
interfaces).
Detected on the VC-4 Tx block of the following units: 2x140/155Mbit/s (VC-4) Tributary Unit,
2x140/155Mbit/s (VC-12) Tributary Unit, and 1x140/155Mbit/s (VC-12) Tributary Unit (when the last
three units are set as PDH interfaces).
This alarm indicates the Loss Of Multi-frame (byte H4) of the TU-2 and TU-12 levels on port n or
VC-4 n.
This alarm can be detected by the STM-4 Optical/Mux Unit, 2xSTM-1 Optical/Mux Unit, STM-1
Optical/Mux Unit and STM-1 Electrical/Mux Unit, 2x140/155Mbit/s (VC-12) Tributary Unit, and
1x140/155Mbit/s (VC-12) Tributary Unit (when the last two units are set as SDH interfaces) when
the AU-4 is demultiplexed at TU-2 and TU-12 levels and the monitoring is active.
Action:
1.
VC4: n PLM
Severity: URGENT
Detected on the VC-4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as
PDH interface).
This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as
SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active.
This is an indication of a mismatch between the received and expected Payload Label value (C2
byte) on port n.
Problem:
1.
Local and destination equipment has been configured with a different Payload Label
Action:
339-1268/06
Navigation Page
296
Book Contents
1.
Check the local and destination C2 byte configuration and the status of the intermediate
Digital Cross-connector Equipment
VC4: n RDI
Severity: INDICATIVE
Detected on the VC4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as
PDH interface).
This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as
SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active.
This is a High Order Remote Defect Indication on port n received from the remote multiplexer.
It indicates that the far-end port has detected some problems into the received stream.
Problem:
1.
1.
Check the status of the far-end port and follow the trouble-shooting procedure for the
detected alarm
VC4: n TIM
Severity: URGENT
Detected on the VC4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as
PDH interface).
This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as
SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active.
This is an indication of a mismatch between the received and expected J1 Trace Identifier on port n.
Problem:
1.
Transmitter on the far-end equipment configure with a different path trace identifier from
the expected one
Action:
1.
Check, using the Software, that the remote transmitted J1 is configured as the local
expected one
VC4: n UNEQ
Severity: URGENT
Detected on the VC4 Tx block of the following unit: Nx140/155Mbit/s Tributary Unit (when set as
PDH interface).
339-1268/06
Navigation Page
297
Book Contents
This alarm can be detected by the STM-N Unit, NxSTM-1 units and Nx140/155Mbit/s units set as
SDH interfaces when the AU-4 is demultiplexed at lower levels and the monitoring is active.
The UNEQUIPPED indicates that in the far-end equipment the VC4 on port n is not connected. The
unexpected reception of VC4 unequipped indicates that a connection error has occurred on the
path.
Action:
1.
VCy: n DEG
Severity: NOT URGENT
Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit,
32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and
3x45Mbit/s Tributary Unit.
This is an indication of a bit error rate from e10-5 to e10-9 (threshold presettable via software) on
the received high or low level payload (check performed by BIP-8 on B3 byte for the VC-3 or by BIP2 on V5 byte for the VC-12) on port n.
Problem:
1.
2.
1.
Check if the same alarm is detected at the termination of the path. If ALARM
DETECTED, proceed as indicated in:
Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG)
2.
Check if the same alarm is detected at the termination of the path. If ALARM NOT
DETECTED, proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
VCy: n EXC
Severity: URGENT
Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit,
32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and
3x45Mbit/s Tributary Unit.
This is an indication of a bit error rate e10-3 on the received high or low level payload (check
performed by BIP-8 on B3 byte for the VC-3 or by BIP-2 on V5 byte for the VC-12) on port n.
Problem:
1.
339-1268/06
Navigation Page
298
Book Contents
2.
1.
Check if the same alarm is detected at the termination of the path. If ALARM
DETECTED, proceed as indicated in:
Bit Error Rate on the LP/HP payload (Vcy-Tuy/AU4-VC4 EXC/DEG)
2.
Check if the same alarm is detected at the termination of the path. If ALARM NOT
DETECTED, proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
VCy: n PLM
Severity: URGENT
Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit,
32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and
3x45Mbit/s Tributary Unit.
This is an indication of a mismatch between the received and expected Payload Label Message (C2
byte for the VC-3 or bit 5, 6 and 7 of V5 byte for the VC-12) on port n.
Problem:
1.
Local and destination equipment has been configured with a different Payload Label
Action:
1.
Check the local and destination C2 or V5 byte configuration and the status of the
intermediate Digital Cross connector Equipment
VCy: n RDI
Severity: INDICATIVE
Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit,
32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and
3x45Mbit/s Tributary Unit.
This is a High or Low Order Remote Defect Indication (bit n. 5 in G1 byte for the VC-3 or bit n.8 in
V5 byte for the VC-12) on port n received from the remote multiplexer.
It indicates that the far-end port has detected some problems into the received stream.
Problem:
1.
339-1268/06
Navigation Page
299
Book Contents
1.
Check the status of the far-end port and follow the trouble-shooting procedure for the
detected alarm
VCy: n TIM
Severity: URGENT
Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit,
32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and
3x45Mbit/s Tributary Unit.
This is an indication of a mismatch between the received and expected Trace Identifier (byte J1 for
the VC-3 or J2 for the VC-12) on port n.
Problem:
1.
Transmitter of the far-end equipment configured with a different path trace identifier from
the expected one
Action:
1.
Check, using the Control Application, that the remote transmitted J1 or J2 is configured
as the local expected one
VCy: n UNEQ
Severity: URGENT
Detected on the VCy Tx block for the following units: (16+16)x1.5/2Mbit/s Tributary Unit,
32x1.5/2Mbit/s Tributary Unit, 63x1.5/2Mbit/s Tributary Unit, 3x34Mbit/s Tributary Unit and
3x45Mbit/s Tributary Unit.
The UNEQUIPPED indicates that the virtual container on port n is not connected, via switching
matrix, to any source point. The unexpected reception of VC unequipped indicates that a connection
error has occurred on the path.
Action:
1.
Wavelength drift
Severity: URGENT
Detected on Tx block of the STM-16 WDM Optical/Mux Unit.
The wavelength stabilisation loop is out of control.
Action:
1.
Follow:
Unit Internal Fault Trouble-Shooting Procedure
Wavelengthmis_LaserOff
Severity: INDICATIVE
Detected on the INT block of the STM-64 G.709 Units.
339-1268/06
Navigation Page
300
Book Contents
This alarm indicates the wavelength configured in the database is not present in the set of
configurable wavelengths for the unit inserted. The unit will not be configured and the laser will
remain OFF.
Problem:
1. Wrong unit fitted or wrong database configuration
Action:
1. Check the kind of unit fitted or check if the kind of unit configured in the database is right
COMMON PROCEDURES
Unit Internal Fault Trouble-Shooting Procedure
When a unit internal fault condition is detected proceed in the following way:
1.
Using the Software select from the main menu the option Unit Reset and perform a
Software reset for the relevant unit.
If the alarm condition remains active:
2.
Perform a unit hardware reset (pull out and re-insert the faulty unit).
2.
3.
If the alarm goes OFF, the problem is a consequence of far-end equipment transmitter
failure; check the status of the far-end equipment.
4.
If the alarm is still ON, the problem is an unit internal failure; proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
If the alarm is ON, the problem is due to an unit internal failure; proceed as indicated in:
339-1268/06
Navigation Page
301
Book Contents
2.
3.
Restart the laser on the optical STM-N unit by pressing the front panel push-button or via
Software procedure (this procedure is not necessary if the Automatic Laser Shutdown is
permanently disabled).
4.
In case of Preamplifier:
5.
6.
If the received power is less than -48dBm: problem on the line or remote equipment.
If the received power is greater than -48dBm; proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
In case of Booster:
5.
If the received power is less than -15dBm: problem on the optical connection path cord
on the local STM-N transmitter.
6.
Check the status of the optical path cord and the STM-N Optical Mux/Unit.
7.
If the received power is greater than -15dBm: Booster internal failure; proceed as
indicated in:
Unit Internal Fault Trouble-Shooting Procedure
Bit Error Rate on the STM-N Optical Signal (MS-EXC/DEG and RSEXC/DEG)
IMPORTANT The following procedure will set out of service the line traffic.
Proceed therefore only if it is actually necessary or if the traffic is protected.
1.
Disconnect the Tx and Rx connectors, loop output with input using an optical fibre patchcord (set an optical attenuator with a proper dB value, when the Tx power overtakes the
minimum overload of the Rx side as reported in the Optical Performances Chapter in the
Technical Specifications Section of the Equipment Manual.
2.
Restart the laser by pressing the front panel push-button or via Software procedure (this
procedure is not necessary if the Automatic Laser Shutdown is permanently disabled).
3.
4.
5.
6.
In the remote equipment disconnect the Tx and Rx connectors and loop the line towards
the local equipment. Restart the local laser.
7.
If the alarm goes OFF, the problem is due to a fault in the far-end equipment.
8.
9.
10.
Using an optical fibre patch-cord connect the Tx side of the STM-n Optical/Mux Unit to
the Rx side of an optical adjustable attenuator.
339-1268/06
Navigation Page
302
Book Contents
11.
Force the laser on (Manual Restart for Test) by pressing the front panel push-button for
12 seconds or via Software procedure (this procedure is not necessary if the Automatic Laser
Shutdown is permanently disabled).
12.
Set the attenuator to measure on its Tx side an optical power according to the tables
reported in the Optical Performances Chapter in the Technical Specifications Section of the
Equipment Manual.
13.
Using a proper optical cable connect the Tx side of the attenuator with the Rx side of the
STM-N Optical/Mux Unit.
14.
Restart the laser by pressing the front panel push-button or via Software procedure (this
procedure is not necessary if the Automatic Laser Shutdown is permanently disabled).
15.
16.
If the alarm goes OFF, the problem is caused by an excessive degradation of the optical
fibre or by a failure of the far-end transmitter; proceed with the next step.
17.
Check if the received optical power is between the values according to the tables
reported in the Optical Performances Chapter in the Technical Specifications Section of the
Equipment Manual
For measuring the received optical power, the Automatic Laser Shutdown in the remote equipment
must be disabled.
18.
19.
If the measured value is out of the range, proceed with the next step.
20.
Check if the measured value is below the minimum sensitivity or above the minimum
overload of the tables.
21.
If the measured value is below the Minimum Sensitivity, probable signal attenuation is
due to poor connector coupling or to the optical fibre line or faulty far-end equipment.
22.
If the measured value is above the Minimum Overload, optical power transmitted from
the far-end equipment is higher than the acceptable one or faulty optical output power
regulation loop on the far-end transmitter
Bit Error Rate on the PDH and STM-1 Electrical Signal (PDH EXC/DEG
and MS EXC/DEG)
IMPORTANT The following procedure will set the line traffic out of service.
Proceed therefore only if it is actually necessary or if the traffic is protected.
1.
2.
Disconnect the Tx and Rx connectors, loop output with input using a proper cable.
If the alarm stays ON, proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
3.
4.
5.
In the remote equipment disconnect the Tx and Rx connectors and loop the line towards
the local equipment.
6.
If the alarm goes OFF, the problem is due to a failure in the far-end equipment.
339-1268/06
Navigation Page
303
Book Contents
7.
If the alarm stays ON, the problem is on the connectors or on the coaxial cable.
If the alarm goes OFF, the problem is due to a failure in the far-end equipment.
3.
IMPORTANT The following procedure will put the line traffic out of service.
Proceed therefore only if it is actually necessary or if the traffic is protected.
4.
Disconnect the Tx and Rx connectors, loop output with input using a proper cable (set
an optical attenuator, with a proper dB value, when the Tx power overtakes the minimum
overload of the Rx side as reported in the Optical Performances Chapter in the Technical
Specifications Section of the Equipment Manual) and restart the laser (this procedure is not
necessary if the Automatic Laser Shutdown is permanently disabled).
If the unit is electrical:
5.
7.
If the alarm goes OFF, the problem is due to a degradation of the optical/electrical
power, problems in connectors coupling or failure in transit equipment; check the connections
and the status of the transit equipment.
339-1268/06
Navigation Page
304
Book Contents
EQUIPMENT EVENTS
This paragraph describes the format of the protection switch report messages in the CA Alarm and
Management window.
The Control Application manages the switch report of the following types of protections:
n Internal Synchronism Protection (Int Sync)
n External Synchronism Protection (Ext Sync)
n Equipment Protection (Equip)
n MS Protection (MSP)
n MS SPRING Protection (Bshr)
The operator can start the report using a configuration window and can configure the colours used
to show the report.
Messages Format:
The information reported in the alarms list are the following:
n Date: date;
n Time: event time;
n Slot: position of the involved unit;
n Source: entity which causes the event;
n Unit: unit type and involved port;
n Severity: event category;
n Alarm Cause: event cause.
339-1268/06
Navigation Page
305
Book Contents
The involved fields are Source, that indicates the involved port or the source, Unit, that indicates
the involved unit type and Alarm Cause. This field gives three different information:
* The protection source status, that can be:
"No request"
Available, not active
"Auto switch"
Active synchronism source
"Manual switch"
Active, selected with manual switch
"Forced switch"
Active, selected with forced switch
"Lockout
Not included in protection
"Failed"
Signal not present or not suitable for synchronism
"WTR"
Input signal waiting for restoration
"OOF"
Input signal out of frequency limits
"Forced & Failed"
Selected with forced switch with failed input
"Forced & OOF"
Selected with forced switch with out of frequency signal
"Forced & WTR"
Selected with forced switch waiting for restoration
339-1268/06
Navigation Page
306
Book Contents
(Ext Sync(T42))
Second Group External Synchronism (new type switch)
The involved fields are Unit, that indicates the involved unit type and Alarm Cause. This field gives
three different information:
* The Protection status, that can be:
"No request"
Normal Status of the not switched protection
"Auto switch"
The protection has switched
"Do not revert"
Switched without restoration
"Auto switch pending"
Failed switching
"Manual switch"
Manual switch
"Forced switch
Forced switch
"Lockout"
Card not included in protection
"Wait to restore"
Waiting for restoration
339-1268/06
Navigation Page
307
Book Contents
The involved fields are Source, that indicates the involved port (MS), Unit, that indicates the
involved unit type and Alarm Cause. This field gives three different information:
* The Protection status, that can be:
"No request"
Normal Status of the not switched protection
"Auto Switch (SF)"
Switched for failure of protected line
"Auto Switch (DEG)"
Switched for degrade of protected line
"Do not revert"
Switched without restoration
"SF Switch Pend"
Failed switch with signal loss
"DEG Switch Pend"
Failed switch with signal degrade
"Manual switch
Manual Switch
"Forced switch"
Forced Switch
"Failed"
Failed Protection
"Lockout"
Card not included in protection
"Wait to restore"
Waiting for restoration
339-1268/06
Navigation Page
308
Book Contents
The involved fields are Unit, that indicates the involved unit type and Alarm Cause. This field gives
two different information: the Protection Status and the Protection Type. Besides the switches of
the two protection sub-parts are reported:
(Bshr Sc) Protection Status
(Bshr Ring) Ring side
The reported status are the following:
* Protection Status (Bshr Sc):
Idle"
Normal condition; actual protection not active
"Full Passthrough"
There is a protection ring switch in other nodes of the ring; the traffic switches on protection
channels
K bytes Passthrough"
There was a span switch on the ring or a failed protection; this node doesnt switch and doesnt
squelch extra-traffic
"Bridged-Switched"
Node switch and traffic on protection (different if the type is span or ring)
"Isolated Node"
Double fault on the two ring group and loss of communication with the other parts of the ring. If the
node is passing-through there is no traffic loss
"Rule S4B"
Not switched protection because of a the presence of ring fault of the same priority on the ring
nodes (ES: double ring SD or double MANUAL RING); this situation doesnt allow to restore the
faults on not adjacent nodes
"Drop Br Sw"
Protection failure; in case of failure on protected cards the traffic will be lost
339-1268/06
Navigation Page
309
Book Contents
Los
(Ethernet Port)
Severity: URGENT
Loss of signal relevant to the Rx side of the port.
Problem:
1. Consequence of a line loopback.
2. Consequence of far-end equipment transmitter failure or line interruption
3. Unit Internal Failure
Action:
1. Remove, if necessary, the line loopback
2. Disconnect the Tx and Rx connectors and loop output to input using a test patch cord. If the
alarm goes OFF, check the status of the far-end equipment and the line.
3. Disconnect the Tx and Rx connectors and loop output to input using a test patch cord. If the
alarm stays ON, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure
TxFail
(Ethernet Port)
Severity: URGENT
Failure of the transmission section.
Problem:
1. Unit internal failure.
Action:
1. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure
339-1268/06
Navigation Page
310
Book Contents
EthernetLink Down
(Ethernet Port)
Severity: URGENT
Ethernet Link Down: This alarm indicates that the unit has not received idle signal for 200ms.
Problem:
1. Possible problem in the auto-negotiation process
2. Failure on the far-end transmitter or problem in the line
3. Internal failure on the local or far-end protection Line Unit
Action:
1. Disable the auto-negotiation process, if the alarm does not go off check the causes
2. Check the status of the far-end transmitter and the line
3. Proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure
PlugModuleMissing
(Ethernet Port)
Severity: URGENT
Module Missing: This alarm indicates that a pluggable module of the 8XFast Ethernet
Unit, configured into the database, it is not inserted.
Problem:
1. Plug Module not fitted
2. Problems with the insertion of the module
Action:
1. Insert the missing pluggable module.
2. Check if the module is right fitted in the unit.
wrongPortConfiguration
(Ethernet Port)
Severity: URGENT
This alarm indicates mismatch between the port type configured via software and the port fitted on
the unit.
Problem:
1. An electrical port is configured instead of an optical one or vice versa.
Action:
1. Check the configuration and the inserted unit, replace the unit or change the database
according to the required configuration.
VCG Alarms
In the following all the alarms relevant to the VCG (Virtual Container Group) are reported.
R-LOA
(VCG)
Severity: URGENT
Recoverable - Loss of Alignment: It is detected if the alignment process cannot perform the
alignment of the individual VC-nv to a common Multiframe start. The alignment process is
performed by means of a signal buffering that allows the accommodation of a Xms differential delay
between the VC-n of reference and any other VC-n-v in the same Multiframe.
339-1268/06
Navigation Page
311
Book Contents
Problem:
1. The value set with manual method is inadequate to recover the
differential delay but the buffer overflow is recoverable with the
auto-adaptive method.
Action:
1. Try to set the Adaptive option in the delay value configuration.
RS-ACKPending
(VCG)
Severity: INDICATIVE
Problem:
1. In a virtual connection on or more VC12s or VC3s has been inserted in a wrong position and
consequently it are not received into the expected position.
Action:
1. Check the cross connections.
GIDMismatch
(VCG)
Severity: URGENT
Problem:
1. This alarm indicates that the received GID of a VCG member is not equal to the GID of the
first VCG member.
Action:
1. Check the cross-connection configuration on the near-end and far end equipment.
VC-n Alarms
In the following all the alarms relevant to the VC-n channels are reported.
DEG
(VC-n)
Severity:NOT URGENT
This is an indication of a bit error rate from e10-9 to e10-5 (threshold configurable via Software) on
the received high level payload (check performed by BIP-8 on B3 byte or by BIP-2 on B2 byte) on
port n.
Problem:
1. Excessive degradation of the optical fibre
Coupling attenuation
Failure on the far-end transmitter
Unit internal failure
Action:
1. Check if the same alarm is detected at the termination of the path. If the alarm is NOT
DETECTED, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure
RDI
(VC-n)
Severity:INDICATION
Remote Defect Indication
339-1268/06
Navigation Page
312
Book Contents
Problem:
1. Consequence of the following alarms detected on the receive side of the far-end multiplexer:
AU-AIS
VCn EBER
VCn: x PLM
VCn TIM
VCn Unequipped
Action:
1. Check the status of the far-end port and follow the trouble shooting procedure for the detected
alarm
PLM
(VC-n)
Severity:URGENT
Payload Label Mismatch
Problem:
1. Local and far-end equipments has been configured with a different Payload Label
Action:
1. Check the local and destination C2 byte configuration and the status of the intermediate
Digital Cross-Connect equipment.
EXC
(VC-n)
Severity:URGENT
This is an indication of a bit error rate e10-3 on the received high or low level payload (check on
B3/B8 byte) on port n.
Problem:
1. Excessive degradation of the optical fibre
Coupling attenuation
Failure on the far-end transmitter
Unit internal failure
Action:
1. Check if the same alarm is detected at the termination of the path. If the alarm is NOT
DETECTED, proceed as indicated in: Unit Internal Fault Trouble-Shooting Procedure
TIM
(VC-n)
Severity: URGENT
Trace Identifier Mismatch: This is an indication of a mismatch between the received and
expected J1/J2 Trace Identifier for VC-4/(VC-3 and VC-12) on port n.
Problem:
1. Transmitter on the far-end Equipment is configured with a different path trace identifier from
the expected one.
Action:
339-1268/06
Navigation Page
313
Book Contents
1. Check, using the Software, that the remote transmitted J1/J2 is configured as the local
expected one.
dLossOfMultiframe
(VC-n)
Severity: URGENT
Problem:
1. This alarm indicates a loss of multiframe alignment word detected on port n.
Action:
1. Check the status of the far-end transmitter and the line
excCRCErrors
(VC-n)
Severity: URGENT
Excessive CRC ErrorS: This alarm indicates an excessive consecutive detection of the number of
CRC errors. This value is settable via LCT.
Problem:
1. Excessive degradation of the optical link
2. Coupling attenuation
3. Failure on the far-end transmitter
4. Unit internal failure
Action:
1. Check the fibre status
2. Check the presence of optical attenuator
3. Check the far-end transmitter
4. Proceed as indicated in:
Unit Internal Fault Trouble-Shooting Procedure
UNEQ
(VC-n)
Severity: URGENT
The UNEQUIPPED indicates that in the far-end Equipment the VC-n is not connected.
Problem:
1. The unexpected reception of VC-n unequipped indicates that a connection error has occurred
on the path.
Action:
1. Check the local and destination C2 for VC-4 and V5 byte for VC-3/VC-12 configuration and
the status of the intermediate Digital Cross-Connect Equipment.
339-1268/06
Navigation Page
314
Book Contents
ERROR MESSAGES
These messages are managed by the Control Application and are displayed on the user interface
by means of dialogue boxes.
WRONG IDM
Unrecognised Message Identification. Protocol error: unknown command or missing message.
INVALID FILE
Invalid format or name of download.ini or of files related to it.
339-1268/06
Navigation Page
Book Contents
WRONG SERVER!
Control Application version or type mismatch.
COMMIT FAILED!
A commit operation failed.
DEMULTIPLEXING UNAVAILABLE!
It is impossible to demultiplex the selected stream. Check the unit type or the unit setting.
339-1268/06
Navigation Page
317
Book Contents
WRONG DATA
The inserted data are wrong or out of range.
TIME OUT
The time necessary to complete the operation is expired.
INSUFFICIENT PRIVILEGE
A superior privilege is needed (i.e.: a read only user can not modify the configuration).
UNDEFINED ERROR
The error type is not present in the archive.
NOT LOGGED IN
The Control Application is not connected.
OPERATION FAILURE
The Communication and Control Unit tells the operator that an operation mismatch occurred.
OPERATION ABORTED
The operation has been interrupted.
339-1268/06
Navigation Page
318
Book Contents
NOT IMPLEMENTED
The feature isnt yet available.
TIMEOUT EXPIRED
The time spent for the operation is too long.
PROTOCOL ERROR
The used protocol isnt suitable with the operation (i.e.: channels involved in SNCP/N - Not Intrusive
switching criteria - are not monitored).
NO PRIVILEGE
The operator has no privileges for the current operation.
OUT OF SEQUENCE
There was a problem in data sequence.
INVALID OPERATION
The operation isnt permitted.
339-1268/06
Navigation Page
319
Book Contents
WRONG PASSWORD
The operator must insert the correct password.
339-1268/06
Navigation Page
320
Book Contents
INVALID NODE
The operator has set an incorrect node address value during a MS-SPRing configuration.
339-1268/06
Navigation Page
321
Book Contents
ALREADY LOGGED-IN
It is one possible message in the error message of CDL file. It indicates that the operator has
attempted two consecutive connections.
INVALID TP TYPE
It is one possible message in the error message of CDL file. It indicates that the Termination Point
type isnt present in the archive.
339-1268/06
Navigation Page
322
Book Contents
INVALID KIND
It is one possible message in the error message of CDL file. It indicates that the attribute kind isnt
suitable for the operation.
339-1268/06
Navigation Page
323
Book Contents
INVALID EQUIPMENT
It is one possible message in the error message of CDL file. It indicates that the equipment is not
suitable for the network.
INVALID TP(S)
It is one possible message in the error message of CDL file. It indicates that the TP(s) is incorrect.
INVALID TO TP(S)
It is one possible message in the error message of CDL file. It indicates that the TO TP(s) is
incorrect.
TP NOT CONNECTED
It is one possible message in the error message of CDL file. It indicates that there are problems in
TP connection or in the network.
INVALID INSTANCE
It is one possible message in the error message of CDL file. It indicates that the instance is
incorrect.
339-1268/06
Navigation Page
324
Book Contents
INVALID LEVEL
It is one possible message in the error message of CDL file. It indicates that the multiplexing level
is incorrect.
339-1268/06
Navigation Page
325
Book Contents
339-1268/06
Navigation Page
326
Book Contents
UNEXPECTED TOKEN
It is one possible message in the error message of CDL file. It indicates that the keyword in the
code isnt recognised.
INVALID SS BYTE
It is one possible message in the error message of CDL file. It indicates that the SS byte must be
configured as SDH or SONET.
339-1268/06
Navigation Page
327
Book Contents
339-1268/06
Navigation Page
328
Book Contents
DOWNLOAD ABORTED
The unit software download is failed.
DOWNLOAD RUNNING
The unit software download is in progress.
DOWNLOAD COMPLETED
The unit software download has been completed.
339-1268/06
Navigation Page
329
Book Contents
339-1268/06
Navigation Page
330
Book Contents
HOW TO
This chapter describes how to perform the operations that require the execution of a proper
sequence of commands in the Control Application software.
339-1268/06
Navigation Page
Book Contents