ADX 201 Installing - Addx PDF

Open Multimedia Gateway, Rel. Ui5.
Installing Active DDF Device
DN0973532
Issue 1-3
Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products
and services. We would like to encourage you as our customers and users to join us in working towards a
cleaner, safer environment. Please recycle product packaging and follow the recommendations for power
use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia Siemens Networks for additional information.
DN0973532 © Nokia Siemens Networks 1 (94)

Issue 1-3
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for
the use of Nokia Siemens Networks customers only for the purposes of the agreement under
which the document is submitted, and no part of it may be used, reproduced, modified or
transmitted in any form or means without the prior written permission of Nokia Siemens
Networks. The documentation has been prepared to be used by professional and properly
trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens
Networks welcomes customer comments as part of the process of continuous development
and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given “as is” and all
liability arising in connection with such hardware or software products shall be defined
conclusively and finally in a separate agreement between Nokia Siemens Networks and the
customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that
the instructions contained in the document are adequate and free of material errors and
omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks,
explain issues which may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO
SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,
SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE
USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2012. All rights reserved.
2 (94) © Nokia Siemens Networks DN0973532

Issue 1-3
Contents
Contents
Summary of changes ........................................................................................... 6
1 Product overview ................................................................................. 8
2 Hardware description .......................................................................... 9

2.1 Active Digital Cross-Connect ADX201 ................................................... 9
2.1.1 Interface card for external E1/T1 interfaces .......................................... 10
2.1.2 Specifications of external E1/T1 interfaces........................................... 11
2.2 Power distribution unit .......................................................................... 13
3 ADDF HW configuration with Open MGW ........................................ 15
4 Hardware installation ......................................................................... 19

4.1 Installing PDU ...................................................................................... 19
4.2 Installing ADX201 ................................................................................ 20
4.3 Connecting the grounding, power supply and power output
cables .................................................................................................. 22
4.3.1 Connecting the grounding cables ......................................................... 22
4.3.2 Connecting the site power supply cables ............................................. 23
4.3.3 Connecting the power output cables .................................................... 24
4.3.4 Installing the protective cover ............................................................... 24
4.4 Connecting internal & external interface cables.................................... 25
5 HW sales items................................................................................... 28
5.1 ADX201 with dual RJ-45 interface cards, 63xE1 .................................. 28
5.2 ADX201 with mini-coaxial interface cards, 63xE1 ................................ 28
5.3 ADX201 with dual RJ-45 interface cards, 63xT1 .................................. 29
5.4 Power distribution unit .......................................................................... 29
5.5 Cable set 1, Optical SM and PWR cables ............................................ 29
5.6 Cable set 2, Optical SM and PWR cables ............................................ 30
5.7 Single mode SFP module, SFPS1L ..................................................... 30
6 Software description.......................................................................... 31
7 Configuring O&M connections.......................................................... 32

7.1 Configuring O&M connection via LAN cable ......................................... 33
8 Installing software ............................................................................. 35

8.1 Getting the correct firmware version..................................................... 35
8.2 Install the firmware from PC ................................................................. 36
9 Provisioning of the ADDF without Open MGW ................................ 37

9.1 Introduction to ADDF provisioning ........................................................ 37
9.2 Configuring system details ................................................................... 38

Issue 1-3
9.3 Configuring pluggable items ................................................................. 40

9.3.1 Selecting an interface card ................................................................... 41
9.3.2 Replacing an IFC ................................................................................. 43
9.3.3 Selecting a small form pluggable (SFP) ............................................... 43
9.3.4 Replacing and accepting an SFP ......................................................... 45
9.3.5 Single Fibre SFPs ................................................................................ 45
9.4 Configuring XConnects ........................................................................ 45
9.5 Configuring Termination Points ............................................................ 46
9.6 Configuring MSP .................................................................................. 47
9.7 Configuring Timing Sources ................................................................. 47
9.8 Configuring system software and software upgrade ............................. 48
9.8.1 Installing software ................................................................................ 49
9.8.2 Selecting an inactive ISD ..................................................................... 51
10 Commissioning ADDF ....................................................................... 53
11 Integrating ADDF................................................................................ 54
12 Performance monitoring.................................................................... 55
12.1 PM overview ........................................................................................ 55
12.2 Add/Delete PM points .......................................................................... 56
12.3 PM Threshold....................................................................................... 57
12.4 PM Current Data View/Reset/Refresh .................................................. 58
12.5 PM History data View ........................................................................... 59
12.6 PM UAP Log ........................................................................................ 60
12.7 Configure System Performance Monitoring .......................................... 61
12.8 System PM Current Data View/Reset/Refresh ..................................... 62
12.9 System PM History Data View/Refresh ................................................ 62
13 ADDF alarms ...................................................................................... 64

13.1 Alarming ............................................................................................... 64
13.1.1 Most recent alarm bar .......................................................................... 64
13.2 LED indicators...................................................................................... 65
13.3 System alarms ..................................................................................... 66
13.4 Pluggable items ................................................................................... 67
13.5 Synchronization alarms ........................................................................ 69
13.6 Port alarms........................................................................................... 70
13.7 Termination point alarms ...................................................................... 72
13.8 Performance monitoring alarms ........................................................... 79
13.9 Digital input alarms............................................................................... 83
14 Troubleshooting ADDF ...................................................................... 84
Appendix 1 Configuring the system time ......................................................... 85
Appendix 2: Managing system recovery .......................................................... 86

Issue 1-3
Contents
Appendix 3 Configuring system database ....................................................... 87
Appendix 4 Configuring log files ...................................................................... 92
Appendix 5 Transmission terms and definitions ............................................. 94

Issue 1-3
Summary of changes
Changes between document issues are cumulative. Therefore, the latest

document issue contains all changes made to previous issues.
Changes between issue 1-3 and issue 1-2

The following changes have been made:
 Chapter Provisioning of the ADDF without Open MGW is updated:
- The supported interface card (IFC) types are updated for
subchapter Selecting an interface card.
 Chapter Performance monitoring is updated:
- Section Power Fail-counter and Timing Link Switch-counter are
added to subchapter PM Overview.
- Subchapter Configure System Performance Monitoring,
System PM Current Data View/Reset/Refresh, and System PM
History Data View/Refresh are added.
 Subchapter ADDF alarms has been updated as follows:
- E1cLOS is replaced with E12cLOS or DS1cLOS for subchapter
LED indicators.
- Two more alarms are added to subchapter Port Alarms.
- Bin is replaced with NE bin for subchapter Performance
monitoring alarms.
The following changes have been made:
 Co-location content has been added in Chapter ADDF HW
configuration with Open MGW.
 Chapter Performance monitoring has been added.
 Chapter ADDF alarms has been updated as follows:
- Subchapters Alarming and LED indicators have been added.
- Subchapter SDH alarms has been removed;
- Subchapter System alarms and Pluggable items have been
updated;
- Subchapters Synchronization alarms, Port alarms, Termination
point alarms, Performance monitoring alarms, and Digital input
alarms have been added.
 Positions of Chapters ADDF alarms and Troubleshooting ADDF
have been exchanged.

Issue 1-3
Summary of changes
 Editorial updates.
Note in Subchapter 9.1 Introduction to ADDF provisioning has been
updated.

Issue 1-3
1 Product overview
The Active Digital Distribution Frame (ADDF) is a multiplexer device which
provides PDH E1/T1 connectivity. It can be installed as part of an Open
MGW, or as part of an existing DDF to minimize cabling.
The following diagram shows logical drawing of ADDF in MGW:
Figure 1 Open MGW architecture with ADDF
ADDF consists of HW and SW module. For HW module, see Chapter 2 to

Chapter 5. For SW module, see Chapter 6 to Chapter 13.
For more detailed information, you can see ADX100, ADX200, ADX201
User Guide and Traditional GTM Series Fuse Panel User Manual on the
manufacturer’s website.

Issue 1-3
Hardware description
2 Hardware description
2.1 Active Digital Cross-Connect ADX201

The Active Digital Cross-Connect ADX201 is an external cabinet-mountable
transmission device, through which the MGW is connected to TDM PDH
E1/T1 networks. It is also referred to as Active Digital Distribution Frame
(ADDF). The ADDF can be connected via redundant STM-1/OC-3 links to
TDM SDH STM-1/OC-3 interfaces of the MGW for connecting the MGW to
the E1/T1 transmission network. It can have up to 63 E1 or 64 T1 interfaces
using eight Interface Cards.
Figure 2 Active Digital Distribution Frame ADX201

Issue 1-3
Dimensions: 88 x 450 x 171 mm (HxWxD)
Weight: 3.1 kg (with interface cards)

2.5 kg (without interface cards)
Interfaces:  Up to 8 interface cards of one type
 Up to 63 E1 with RJ45 interfaces
 Up to 64 T1 RJ45 interfaces
 Up to 63 E1 with mini coaxial interfaces
 Test port
 Digital input
 Serial console port
 SFPs, STM-1 interfaces
Power consumption  6.5W per ADX201 unit excluding interface cards
 13W per ADX201 unit including interface cards and SFP modules
Table 1 ADX201 technical data
2.1.1 Interface card for external E1/T1 interfaces
The ADX201 supports following interface cards:

 E1/RJ-45 (with 4 x 2 E1 interfaces)
 E1/mini-coaxial (with 8 x E1 interfaces)
 T1/RJ-45 (with 4 x T1 interfaces)
Figure 3 E1/T1 RJ-45 interface card

Issue 1-3
Figure 4 E1/mini-coaxial interface card
2.1.2 Specifications of external E1/T1 interfaces
PDH TDM interfaces

Interface type PDH (ITU-T G.703)
E1
Impedance Balanced 120 Ω Unbalanced 75Ω
Connectors RJ45 mini coax (DIN1.0-2.3)
Bit rate 2048kbit/s
Framing structure G.704
According to ITU-T rec. I.432.3
Mapping G.804
OAM F3 I.432.3 / G.704
OAM F2 Not used
OAM F1 I.432.3 / G.704
Table 2.TDM E1 interface specifications
Interface type PDH (ITU-T G.703)

T1
Impedance 100 Ω
Connectors RJ45
Bit rate 1544kbit/s

Issue 1-3
Framing structure G.704

According to ITU-T rec. I.432.3
Mapping G.804
OAM F3 I.432.3 / G.704
OAM F2 Not used
OAM F1 I.432.3 / G.704
Table 3 TDM T1 interface specifications
E1 and T1 balanced cable

Cable:
 Multi-cable (4 or more) bundled assembly
 Nominal impedance: 120 ± 15 Ω for E1 and 100 ± 15 Ω for T1
 E1 data transmission protocol specifies 6 dB as maximum attenuation
 AWG 26 or AWG 24 conductors
 Continuous pair twisting
 VW-1 materials
 Flammability: IEC 332-1 or IEC 332-3
 Operating temperature from 0° C to 70° C
Connector:
 RJ-45 connector
 Shielded construction
 Gold plating on the contacts (0.76 µm)
 UL94 V-0 materials
Connector pins for RJ-45
Position Signal, generic names Wire pair
1 Receive - (Rx-) 2
2 Receive + (Rx+) 2
3 Receive - (Rx-) 3
4 Transmit – (Tx-) 1
5 Transmit + (Tx+) 1

Issue 1-3
6 Receive + (Rx+) 3
7 Transmit – (Tx-) 4
8 Transmit + (Tx+) 4
Table 4 RJ-45 connector pinouts
E1 unbalanced (coaxial) cable

 Impedance 75 ± 3 Ω
 Single or multicoaxial cable
 E1 data transmission protocol specifies 6dB as maximum attenuation
 VW-1 material
 Flammability: IEC 332-1 or IEC 332-3
 Operating temperature from 0° C to 70° C
Tx Rx
Interface card 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Table 5 Mini coax connector pinouts
2.2 Power distribution unit

The PDU is cabinet-mountable device, which receives power from an
external source, passes the power through an array of fuses and distributes
the power to the connected ADX201 devices. Each dual PDU power feed
unit supplies up to 18 ADX201 devices. Technical data for PDU, you can
see in Chapter Specifications and Dimensions in Traditional GTM Series
Fuse Panel User Manual.

Issue 1-3
Figure 5 Front and rear view of PDU

Issue 1-3
ADDF HW configuration with Open MGW
3 ADDF HW configuration with Open MGW

Up to 36 ADX201 devices can be equipped in the network element, where
maximum number of ADX201 devices per cabinet is 18. ADX201 and its
power distribution unit (PDU) can be equipped in the same cabinet with
Open MGW or in a separate ATCA cabinet. In case the separate cabinet is
reserved for ADX201 devices, Open MGW and ADX201 cabinets must be
located side by side with no pillars between them. ADX201 can also be co-
located in ATCA cabinet with any ATCA-based NE, such as Open MSS or
ATCA-based DX HLR.
One PDU and six ADX201 devices can be mounted in the space of one
shelf, three from the front and three from the back of the cabinet. The order
in which the ADX201 devices should be equipped has been indicated in the
triangles in Figure Two different cabinets’ configurations of ADX201
devices. Generally, the order is from bottom to top, from front to back. The
PDUs are always mounted in the lowest shelf space on the front side of the
ATCA cabinet.
Vertical mounting coordinates are marked on the cabinet mounting rails at
front and rear sides. They increase from top downwards. See following
figure for more information, such as 08, 15 in rectangles.
ADX201 can also be installed in 19” cabinet, but this kind of installation is
not in the scope of this document.

Issue 1-3
Figure 6 Two different cabinets’ configurations of ADX201 devices

Issue 1-3
ADDF HW configuration with Open MGW
Two sets of interconnection cables can be used between Open MGW and
ADX201. Cable sets include the fiber between SCNAM-A and ADX201, and
power cables between ADX201 and PDU.
 ADX201 in the same cabinet with Open MGW, cable set 1
(3GNAB1008)
 ADX201 in the adjacent cabinet of Open MGW, cable set 2
(3GNAB1009)
In case longer cables are needed, they are provided by Services.
The following table shows generic connections between TDM AMCs and
ADX201 devices. In principle, it is possible to connect any pair of redundant
SFP ports on TDMNIP to any ADX201 device, so cable labels must be
printed without index (for example, ADXHW_) and must not be wrapped
around cable in factory. Then the customer can print the appropriate
indexes according to the chosen connection.
CABLE FROM CABLE TO

Cabinet
Cabinet
Equip. Node Position HW Position Type Use Note

No module
xx.07F/B y SFP z Active

ADXHW_ 1 TDMNIP x 1 ADX201 x xx.01F/R SFP 1 CMMUX026 TDM/ STM-1
xx.10F/B y SFP z Redundant


Issue 1-3
CABLE FROM CABLE TO

Cabinet
Cabinet
Equip. Node Position HW Position Type Use Note
No module
How to read the table:

- Column Node: x = 0... 47 index of TDM module to be connected to ADX201
- Column From Position: xx = 27, 52 or 77 if TDMNIP is equipped in top, middle or bottom shelf respectively
y = 1... 4 index of AMC bay in which TDMNIP is equipped (1=top)
z = 1... 4 index of SFP module used for connection (1=top)
- Column HW module: x = 0... 35 index of ADX201
- Column To Position: xx = mounting coordinate of ADX201
F/R = according if ADX201 is mounted on front (F) or rear (R) side
Table 6 Connections between TDM AMCs and ADX201
The following table shows generic connections between ADC-PDU and

ADX201 devices.
CABLE FROM CABLE TO

Cabinet
Cabinet
Equip. Node Position HW module Position Type Use Note

No
74.01F Batt. A, output
ADXHW_ 1 ADC-PDU 1 ADX201 x xx.01F/R SFP 1 CVKADX025 Power
terminal x
74.01F Batt. B, output
ADXHW_ 1 ADC-PDU 1 ADX201 x xx.01F/R SFP 1 CVKADX025 Power
terminal x
How to read the table:
- Column From position: x = 0... 18. For first ADX cabinet: same as ADX201 index.
For second ADX cabinet: x = 0 for ADX201 18, x=1 for ADX201 19, and so on.
- Column HW module: x = 0 .. 35 index of ADX201
- Column To Position: xx = mounting coordinate of ADX201
F/R = according if ADX201 is mounted on front (F) or rear (R) side
Table 7 Connections between ADC-PDU and ADX201

Issue 1-3
Hardware installation
4 Hardware installation
4.1 Installing PDU

The PDU can be mounted only in the front side of ATCA cabinet. The
following picture shows PDU mounting brackets. Long side of the brackets
is mounted to the PDU; short side is mounted to ATCA cabinet rails.
Figure 7 PDU installation

Issue 1-3
Steps:
1. Install the cable management bar, as shown in the figure above.
2. Mount the PDU brackets.
3. Mount PDU in the required position in ATCA cabinet. For mounting
positions, see Chapter ADDF HW configuration with Open MGW.
Please note that PDU can be mounted only in the front side of the
cabinet. Fasten brackets to ATCA cabinet rails as shown in the
picture.
4.2 Installing ADX201

General instructions for installation of ADX201, you can see in Chapter
Installation guide in ADX100, ADX200, ADX201 User Guide.
Electrostatic discharge (ESD) may damage hardware components. To

avoid ESD damage:
– Before handling hardware units, check that the site is an ESD-protected
area (EPA). If the area is not ESD-protected, create a temporary EPA.
– When handling hardware units, wear an ESD wrist strap or use a
corresponding protection method, and do not touch the connector
surfaces.
Figure 8 ADX201 installation

Issue 1-3
Steps:
1. Undo M4 screws from the mounting brackets.
2. Mount brackets in the required position.
a. For mounting the ADX201 on the front side of the ATCA
cabinet, long side of brackets must be mounted to the side of
ADX201, as shown in the following picture:
b. For mounting the ADX201 on the rear side of the ATCA cabinet,
short side of brackets must be mounted to the side of ADX201,
as shown in the following picture:

Issue 1-3
3. Mount ADX201 in the required position in ATCA cabinet. For the

mounting positions, see Chapter ADDF HW configuration with Open
MGW.
4. Insert SFP modules in ports Line1 and Line2.
4.3 Connecting the grounding, power supply and power

output cables
4.3.1 Connecting the grounding cables

Steps:
1. Measure and cut a 6 mm2 cable for connecting PDU grounding to the
cabinet grounding rail.
2. Crimp the provided lugs to each end of the cable.
3. Connect the grounding lug of the cable to the grounding studs
marked as CGND at the rear side of the PDU.
Figure 9 Grounding the PDU

Issue 1-3
4. Secure the lugs with nuts with captive star washers.

5. Tighten the nuts to 2.6 Nm.
6. Connect the other end of PDU grounding cables to the left cabinet
grounding rail. The screws and nuts are already attached to the
grounding rail. Tighten the nuts with a 10 mm socket wrench to 5.1
Nm.
4.3.2 Connecting the site power supply cables
Input power connector is implemented with 2-hole compression lugs. Two 6

mm2 cables are required. For more information, see chapter Connecting
Power Input in Traditional GTM Series Fuse Panel User Manual. Ensure
visually that the polarity of the supply lines is correct: in each supply line,
the input cable must be connected to the terminal marked with BATT and
the return cable must be connected to the terminal marked with RTN.
Figure 10 Site power supply cables

Issue 1-3
4.3.3 Connecting the power output cables
Connect power cable CVKADX205 to PDU output power connector. Then

route these cables through cable management bar (Bus A goes to the right
side, Bus B goes to the left side), and connect to power input connectors in
ADX201, B1 and B2.
Figure 11 Power output cables
Power output cables should go firstly to one side which is relatively closer
to B1 and B2, and then to ADX201 from one side only. Redundancy in DC
power feed is implemented by B1 and B2. Thus each ADX201 is connected
to both inputs of PDU device. For more information, see Chapter
Connecting Power output in Traditional GTM Series Fuse Panel User
Manual.
4.3.4 Installing the protective cover
After all the PDU connections are made, the protective cover should be
attached.

Issue 1-3
4.4 Connecting internal & external interface cables

Steps:
1. Connect optical cables to ADX201 SFP connectors.
2. Route the internal cables
a. Front side cables, route the cables to the right side of ATCA
cabinet and then towards the top of the cabinet. See yellow
cables in Figure Interface cabling in front side.
b. Rear side cables, route the cables to the left side of ATCA
cabinet through the cable opening to the rear side, and then
connect to ADX201. See yellow cables in Figure Interface
cabling in rear side.
3. If ATCA shelf with TDM AMCs is located in a different cabinet, cables
are routed through the top openings of the cabinet.
4. Connect TDM cables to interface cards.
5. Route TDM cables to the left side of ATCA cabinet and then towards
the top openings of the cabinet. See grey cables in Figure Interface
cabling in front side.

Issue 1-3
Figure 12 Interface cabling in front side

Issue 1-3
Figure 13 Interface cabling in rear side

Issue 1-3
5 HW sales items
This section lists the HW sales items that are available for ADX201 device.
Each sales item includes hardware products identified by the ID and Name.
5.1 ADX201 with dual RJ-45 interface cards, 63xE1

Sales item code: 3GNADX201RE1
Functional set C-code: C112547
Name Quantity (pcs)
ADX201, including 19" brackets 1

E1/dual RJ-45 interface cards 8
Mounting kit for ETSI cabinet 1
5.2 ADX201 with mini-coaxial interface cards, 63xE1

Sales item code: 3GNADX201CE1
Name Quantity (pcs)

Mini-coaxial interface cards 8

Issue 1-3
HW sales items
5.3 ADX201 with dual RJ-45 interface cards, 63xT1

Sales item code: 3GNADX201RT1
Name Quantity (pcs)

T1/dual RJ-45 interface cards 8
5.4 Power distribution unit

Sales item code: 3GNADXPDU
Name Quantity (pcs)
Dual feed ADC-PDU, including 19" 1

brackets
1A fuses – GMT-1A 40
Cable tray 1
5.5 Cable set 1, Optical SM and PWR cables

Sales item code: 3GNAB1008
ID Name Quantity (pcs)
C111275 CMMUX026 cable 2

C112527 CVKADX025 cable 2

Issue 1-3
5.6 Cable set 2, Optical SM and PWR cables

Sales item code: 3GNAB1009
C110212 CMMUX048 cable 2

C112527 CVKADX025 cable 2
5.7 Single mode SFP module, SFPS1L

Sales item code: OPENHW5006
P02032 SFPS1L 1

Issue 1-3
Software description
6 Software description
The ADX software supports all products of the ADX family (ADX201, 200
and 100). The ADX has two memory banks containing the active and
possibly an inactive software version. The software is stored in non volatile
(flash) memory.
Remote and local software uploads are supported. Software upgrades are
non service affecting. They also do not affect data communication settings.
The System supports the installation of new software via FTP.

Issue 1-3
7 Configuring O&M connections

ADDF provides two different management interfaces.
Local 192.168.2.1/32
Remote 192.168.1.2/32 No OSPF 10.12.0.2/24
Allow remote IP IP forwarding
Auto: 192.168.1.2/32 disabled
No OSPF
Depending on Open MGW

Local routing entries¨ SDH PC
to reach ADDF Open MGW protected link ADDF
No OSPF 10.12.0.100/24
Allow remote IP Default route:
Local 192.168.1.1/32 Auto: 192.168.1.2/32 10.12.0.2
Remote 192.168.1.2/32
Figure 14 ADDF management interfaces

The ADDF can be managed either
 Locally via the 10/100BASE-T Ethernet LAN interface
 Remotely by a PPP connection via STM1/DCC channel, that is, the
protected SDH link between Open MGW and ADDF. The multiplex
section communication channel (MS-DCC) offering higher bandwidth
is used for remote management.
Open MGW doesn’t support seamless integration via a DCC channel
in Ui5.0 release. The LAN connection is used for configuration and
troubleshooting purposes.
Seamless integration using the DCC channel is provided in later
releases.

Issue 1-3
Configuring O&M connections
To allow seamless management of the ADDF from Nokia Siemens

Networks network management via the Open MGW itself, the MS-DCC
channel is the only feasible communication path.
During normal Open MGW operation, the ADDF is fully managed via the
PPP connection. The local LAN interface is used only during initial onsite
installation, and for troubleshooting purposes.
Following protocol stacks are used for different management interfaces:
File Web GUI MIB
transfer
Telnet FTP HTTP SNMP NTP

TCP UDP
IP v4
Ethernet PPP/LCP
LAN HDLC
10/100 DCC
FE MS/RS
SDH DCC channel
MS/RS section
[pt-pt HDLC/PPP link]
Local 10/100Base-T
connector
[LAN]
Figure 15 ADDF O&M interface protocol stacks
7.1 Configuring O&M connection via LAN cable

You can also create the O&M connection via LAN cable. This connectivity
alternative is used for maintenance and troubleshooting purposes.
ADDF has one LAN 10/100 BASE-T full/half duplex MDI interface. Cross
wire (MDX) detection is not supported. If the PC does not support
MDI/MDX switching, a PC cross-cable is required for a direct connection.
ADDF can be managed via the 10/100BASE-T Ethernet LAN interface only
if the ADDF is not connected to the Open MGW. Otherwise the
management interface operates in read-only mode. The ADDF must have a
valid (known) IP address, within the subnet range of the LAN it is

Issue 1-3
connected to, to access the management interface. When setting up a

connection with the web browser for the first time, use a direct LAN
connection between the PC and the ADDF.
The default address of the ADDF on the Ethernet LAN interface is
10.127.127.1/8. Depending on the use of a DHCP server in your network,
you can provision the LAN port settings.
Note
For the local LAN of ADDF, you must use a LAN IP address that does
not fit in the LAN network of Open MGW, for example, 10.127.127.1/30.
If IP address 10.127.127.1/30 is used, the IP subnet addresses are as
follows:
 10.127.127.0
 10.127.127.1
 10.127.127.2
 10.127.127.3.
The first one is usually not allowed, and the last one is a broadcast
address. So these addresses cannot be used as host addresses.
The ADDF has an integrated web server. You should not use a router
between the ADDF and PC.
The default address of the ADDF is 10.127.127.1/8. Depending on the use
of a DHCP server in your network, you can provision the LAN port settings.
The subnet mask notation /8 equals to 255.0.0.0 (RFC950).
Note
Do not perform LAN port provisioning via Web browser. By default,
DHCP is enabled, and the ADDF immediately attempts to obtain the
LAN IP details (IP address, mask, and gateway) from a DHCP server. If
this fails, the default values are used.
DHCP needs to be disabled if:

 No connection can be established towards the ADDF;
 A direct cross-over cable is used from a PC/laptop.
In this case, you should configure LAN IP settings according to your real
needs.
For more information on this connectivity type, see the User Guide
ADX100, ADX200, ADX201.

Issue 1-3
Installing software
8 Installing software
As a basic rule, the ADDF device-related software is installed during the
Open MGW installation. Only in case the ADDF device is added to the
Open MGW after the initial installation should there be a need to install the
software as described in the following sub-chapters.
Especially in Ui5.0, the ADDF firmware is managed with an O&M
connection via a LAN cable (for more information, see chapter Configuring
O&M connection via LAN cable). Nokia Siemens Networks delivers the
latest firmware version with the ADDF, but once a new version is released,
operators should at least consider installing the new software version. For
instructions, see chapters below.
8.1 Getting the correct firmware version

The operator receives the notification of a new firmware version in a
Technical Note. Once a new firmware version is available, the operator
should update the firmware version as described below.
Follow the steps below to check and update (if needed) the firmware
version of the ADDF.
1. Check the matching ADDF firmware version from the Release note.
2. If the firmware version does not match, update it. The firmware is
distributed via Nokia Siemens Networks online service (NOLS). Find
the new released firmware from the same place in NOLS where
delivery software for Open MGW is located.
3. Download the firmware from NOLS to a local PC storage.

Issue 1-3
8.2 Install the firmware from PC

If the current firmware does not match the required firmware, install the new
firmware version.
Once you have downloaded the firmware from NOLS to a local PC storage,
install the firmware using an O&M connection via a LAN cable. For more
information, see chapter System software and software upgrade in this
document.

Issue 1-3
Provisioning of the ADDF without Open MGW
9 Provisioning of the ADDF without Open

MGW
9.1 Introduction to ADDF provisioning

You can provision the ADDF with a Web browser and a local LAN
connection. When a login as admin is required, this is explicitly mentioned.
The default password for the admin user is adm123.
For more information on the available user groups and passwords, see the
User Guide ADX100, ADX200, ADX201 document.
You can check the actual configuration of the ADDF for troubleshooting
purposes via the LAN and Web browser interface at any time, even if the
ADDF is already connected to the Open MGW and managed by the Open
MGW.
The minimum ADX release that supports the Open MGW is release 3.0.
Bare minimum configuration tasks:
- set ADX system name for unique logs and debugging purposes
- set System mode to E1
- uncheck “VC12 Unequipped”
- set “Disable IP Forwarding”
- configure the system time
Note
You cannot modify any configuration via LAN and Web browser interface
if the ADDF is connected to the Open MGW. In this kind of situation,
modification is supported only when ADDF is seamlessly integrated into
the Open MGW in later releases.

Issue 1-3
For more information on O&M connection via LAN cable, see chapter O&M
connectivity via LAN cable.
9.2 Configuring system details

1. Select MENU: SYSTEM | DETAILS
This opens the System – Details dialog, which displays the
ADDF name and location, hardware specific details, and the
system mode that is used.
Figure 16 System - Details
2. Provision the name and location of the ADDF, if needed. Also

check any of the check boxes, if needed.
3. Click Apply to verify the changes.
4. If you need to update the system mode, select the needed
alternative from the System Mode drop-down menu and click
Change System Mode. For Open MGW Ui5 release, E1 is
supported; and for Open MGW Ui5 EP1 release, T1 (DS1) is
supported.
System name
A name of 30 characters can be entered.
System Location

Issue 1-3
A location of 30 characters can be entered, allowed characters are:

 [A-Z][a-z][0-9]+_-./| : ;#%~@&*{}[]()><!?^$.
Evaluation of these characters takes place after you press Apply. If
you entered invalid characters, a warning is displayed and the input is
not accepted.
Note
When minimizing the browser, the ADDF name and location are shown.
Note
The current ADDF location and name are shown on the top bar of the
browser.
VC12 Unequipped
Check this box to insert a VC12 Unequipped signal for all VC12 in the
VC12 upstream direction, when a loss of signal (E1 2cLOS) alarm is
detected on the related E1 port.
Note
This functionality is used to support the ADDF seamlessly, but it is not
according the ITU-T standard. Therefore it is disabled by default.
If you activate this functionality, it replaces the behaviour of inserting an

E12cAIS alarm when a loss of signal is detected. The VC12 and E1 signals
are replaced by an all-zeros signal.
SSM1010 Insertion
Check this box to report an outgoing SSM value of 1010 (overriding the
normal SSM SEC value when switching to holdover) when the timing
switches to holdover due to the detection of excessive frequency offset on
the active E1/DS1 port used as a timing reference. Note that if another
timing reference is available, it is chosen, and the E1/DS1 excessive
frequency offset is not encoded in the SSM value.
Note
This functionality is not according the ITU-T standard! Therefore it is
disabled by default.
Disable IP Forwarding
Check this box to disable IP Forwarding on the system. This prevents
connectivity from the system LAN interface to the PPP links and vice versa.

Issue 1-3
Item code
Identifies the type of ADDF.
 ADH103 for ADX201 2RU for 64 E1/DS1 interfaces
Catalogue number
Displays the order number.
Serial number
Displays the serial number of the ADDF. This number is factory assigned
per product and is useful for tracking hardware.
Manufacturing Date
Displays the month and year of manufacture. This information is based on
the serial number of the system.
System Mode
The ADDF can operate in E1 mode or DS1 mode. The default mode is the
E1 mode. When changing from one system mode to another, the interface
cards need to be replaced with correct types. All provisioning of the ADDF
is removed when changing the system mode. And the ADDF performs a
recovery action.
In DS1 system mode, some features are not available:
 No near end and far end PDH performance monitoring
 No test access output port
Other features will work in the same way for DS1 as for E1.
9.3 Configuring pluggable items

Pluggable items refer to interface cards and SFPs. The pluggable items
can be inserted and removed while the ADDF is powered (hot pluggable).
General instructions for installation of ADX201, you can see in chapter
Installation guide in ADX100, ADX200, and ADX201 User Guide.
NOTICE: Electrostatic discharge (ESD) may damage hardware

components. To avoid ESD damage:
– Before handling hardware units, check that the site is an ESD-
protected area (EPA). If the area is not ESD-protected, create a
temporary EPA.
– When handling hardware units, wear an ESD wrist strap or use a
corresponding protection method, and do not touch the connector
surfaces.

Issue 1-3
Figure 17 System – Pluggable Items
9.3.1 Selecting an interface card
ADDF supports the following interface card (IFC) types:

 ADC102. 8 DS1 interfaces, RJ45 connector, 100 Ohm
 ADC103. 8 E1 interfaces, coax connector, 75 Ohm
 ADC104. 8 E1 interfaces, RJ45 connector, 120 Ohm
The ADDF automatically detects an inserted interface card. The default
tributary slot state is AUTO. When the IFC has a supported item code
(ADC101-ADC120), the state changes from AUTO to ASSIGNED, and the
IFC becomes operational. This takes less than one minute.
Selecting the desired TS (Tributary Slot) shows the following details.
Figure 18 Slot – TS3

Issue 1-3
Current State
The current state can be AUTO or ASSIGNED. When the inserted IFC has
an item code that is not supported, the IFC remains in the AUTO state and
an IFCcWUI (IFC Wrong Unit Inserted) alarm is reported. When the
inserted IFC is defective, an IFCcEQF (IFC Equipment Failure) alarm is
reported. The IFC needs to be replaced by a correct one.
When no IFC in the ASSIGNED state is present, an IFCcUNP (IFC Unit Not
Present) alarm is reported, which will be due to a removal. In AUTO state,
an IFCcUNP alarm is not reported.
Item code
The item code identifies the type of Interface Card. Currently, ADC104 is
available for the ADDFs. The ADC104 has 8 ports E1 (G.703) 120 Ohm
ports with RJ45 connectors. The ADDF is prepared for future versions of
Interface Cards, as it supports item codes starting from ADC101 up to
ADC120 in this release. Future Interface Cards might have different
impedance or connector types.
Catalogue number
Displays the catalogue number of the interface card without connector.
Note
Interface cards can only be ordered including a connector.
Serial Number
Displays the serial number of the selected IFC. This number is factory
assigned per product, and is useful for tracking hardware.
Last Accepted
Displays the item code of the IFC that was present and accepted before the
current one. This information is of use when more item codes are
supported, and IFC replacements are performed.
Change State to Auto
This can be used when the state of a slot is ASSIGNED while the IFC has
been removed, and no alarming for this situation is required. This operation
might be service affecting when an Interface Card is present.
Accept Pluggable Item
This can be used when an IFC has been replaced with another type (item
code). This is of use when more item codes are supported. If traffic is
running before executing this operation, this action is not service affecting.

Issue 1-3
9.3.2 Replacing an IFC
When an interface card is replaced with the same item code, the ADDF
accepts the IFC and the IFC remains in the ASSIGNED state. When an IFC
is replaced with another IFC having a different but supported item code, an
IFCcREPL alarm is reported, and the user has the option to accept this
IFC. The alarm notifies the user of the change in item code. In the Last
Accepted field, the user can view the previous item code, and decide if the
change is requested. When selecting Accept Pluggable Item, the state of
the inserted IFC changes to ASSIGNED. All provisioning regarding this IFC
will be taken over.
Behavior when no Interface Card is inserted:
When no IFC is inserted, the related VC12 termination points are available.
In upstream direction, an AIS is inserted into the payload (E1 signal). When
provisioning VC12 termination point settings, they will not be effective until
an IFC is inserted. In this situation, you can pre-provision the VC12 TTP.
9.3.3 Selecting a small form pluggable (SFP)
The ADDF has two SFP positions related to the line ports.
When selecting an SFP, the following details are shown.
Figure 19 SFP1

Issue 1-3
Current state
Displays the current state of the SFP. The state can be ASSIGNED or
AUTO.
 ASSIGNED: The current SFP is accepted and operational, when no
alarms are present.
 AUTO: No SFP is present, or the inserted SFP is not accepted, see
chapter SFP replacement and acceptance for more details.
Qualifier
Identifies the type of SFP. This is according to ITU-T G.957. All module
qualifiers are accepted by the ADDF. The module qualifier for optical SFPs
has the format I/S/L-X.Y.
 In which I/S/L identifies if it is an intra (I), short(S) or long (L) haul.
 X identifies the rate of the SFP: 1 – 155 Mb/s, 4 – 622 Mb/s.
 Y identifies the wavelength of the SFP: 1 – 1310 nm, 2 – 1550 nm, 3
– 1550 nm dispersion shifted.
S1.1 is a short haul 1310 nm STM-1 SFP.
Electrical SFPs will have STM1-e as module qualifier.
If the module qualifier cannot be determined, it is assigned the Unknown
qualifier. This can be due to vendors not following the inventory coding.
These SFPs are accepted.
Wavelength (nm)
Displays the transmitted wavelength of the SFP.
Link Type
Displays the type of optical fibre to be used (9 um single mode), or type of
coaxial for an electrical SFP.
Link Max Length
Displays the allowed link distance.
Vendor fields
Identifies the vendor specific details.
The connector type, transceiver code and length are for troubleshooting
purposes. Check the Multi Source Agreement (MSA SFP-8074) of the SFP
for more details.
Last accepted
Indicates the type of SFP that was accepted previously. This is important
when the SFP has been replaced.

Issue 1-3
9.3.4 Replacing and accepting an SFP
When the state of the SFP is AUTO, and an SFP is inserted, the SFP is
accepted, irrespective of the module qualifier. When the state of the SFP is
ASSIGNED, and an SFP is inserted, then it is actually a replacement. In
this case, the inserted SFP module qualifier is compared with the last
accepted. If they differ, a SFPcWUI alarm is raised, and the SFP is not
accepted. Transmission is shut down. This alarm notifies the operator on a
change of SFP type. When this change is acceptable, the state of the SFP
has to be changed to AUTO.
This action accepts the SFP, and the state is changed to ASSIGNED.
When a timing reference is assigned from this port, the timing reference
has to be unassigned before changing the state to AUTO.
9.3.5 Single Fibre SFPs
The ADDF supports single fibre or bidirectional SFPs. It is important to

have matching SFPs at each end of the fibre connection. The wavelength
used for transmitting should be different.
9.4 Configuring XConnects

For connecting the E1/T1 transmission network, the ADX must have a
connection via STM-1 links to a TDM interface. ADX can have up to 63 E1
or T1 interfaces and two STM-1 interfaces. XConnects in Web UI can
resolve it.
The following figure displays an example of Xconnects.
Figure 20 XConnects

Issue 1-3
There are two blank in Figure XConnects. In the left blank it is STM-1
interface and both SPFs are broken down into 63 threads. In the right
blank, there are 8 tributary slots (TS). Each tributary slot has 8 tributary
ports (TP); one TP is interface to E1 or T1.
9.5 Configuring Termination Points

The termination points configuration has three phases, which are RS/MS,
VC4, and VC12.
For an example of RS/MS configuration, see the figure below:
Figure 21 RS/MS configuration
The important fields are Expected Mode and Transmitted Mode. The
value of these two fields can be String or Repeating Byte. Open MGW,
however, can only support the String value. The suggested value in ADX
should be String.
You can use the same value for these fields also in VC4 and VC12
configuration.

Issue 1-3
9.6 Configuring MSP

The ADDF supports MSP line port protection; this enables restoration of
traffic when a failure has been detected on one of the line sections
including SFP failures. Unidirectional and bidirectional MSP for both
revertive and non-revertive operation is supported.
Figure 22 MSP configuration
It is recommended that some parameter configurations are consistent with

the configuration of the Open MGW. These parameters include SW Type,
Operation, Worker, and Protection.
9.7 Configuring Timing Sources

The ADDF has the ability to provision three independent timing sources.
One from one of the E1 ports and two from both line ports, but Open MGW,
however, only supports line port timing. In case MSP is provisioned, only
one line port reference (worker MSP section) is available.

Issue 1-3
Figure 23 Timing Sources configuration
9.8 Configuring system software and software upgrade

ADDF supports one load line for both products. For more information about
software releases, refer to the release notes.
For more information on how to update the firmware, see chapter Getting
the correct firmware version.
The ADDF has two software memory banks.
MENU: MAINTENANCE | SYSTEM | DETAILS
The detailed content of both banks is shown.
Figure 24 Maintenance – Software – Details

Issue 1-3
Bank 1 contains the active ISD and Bank 2 the inactive.
Image Status Meaning

Bank 1 Bank 2
active inactive Normal situation, both banks are filled and the software in Bank 1 is
currently running
active soak A software upgrade has taken place and the sanity process is not yet
finished. The software in Bank 1 is currently running. When the sanity
process is finished, the new state (bank1/bank2) is active/inactive if
the upgrade is successful, or soak/error if a recovery has taken place
before expiry of the sanity timer.
soak error during An ISD switch has been unsuccessful (only applicable for the inactive
last image bank). If this error occurs the image is valid but a transition error
transition occurred. The action can be repeated and become successful.
active empty Normal situation for an ADDF leaving the factory. Bank2 is empty and
the software of Bank 1 is running
Item Code
Identifies the software release, refer to release notes for details.
Software Version
Identifies the software release, sub release, maintenance release, or load
drop version.
Build Time:yyyy-mm-:dd hh:mm:ss
Displays the build time and date.
Note
To allow limited hitless downgrading of software, follow the instructions
in chapter Default database and software downgrade. If downgrading is
required, do so immediately after receiving an ADDF. If this is not
possible (anymore), you have to take care that local access to the node
is possible.
9.8.1 Installing software
1. To upload a new ISD to the inactive bank, select:

MAINTENANCE | SOFTWARE | INSTALL

Issue 1-3
Figure 25 Software upload
2. Select Browse...
A file browser is started at the PC.
Note
The text in the Browse... button depends on your local language
settings.
3. Select the needed ISD from the browser that opened and click Apply.
The ISD is uploaded to the ADDF, which takes about five minutes. A
progress indicator showing the progress of the upload is displayed.
The size of an ISD is about 7.2 Mb.
Figure 26 Loading the software

Issue 1-3
When the upload is finished, the details of the uploaded ISD are shown.
Figure 27 Software upload finished
Note
The value for the Software version field in the screenshot in this manual
does not show the most recent version of the software.
9.8.2 Selecting an inactive ISD
This option is only available for the admin user.

When selecting an inactive ISD, the ADDF system switches over to the
inactive ISD. The ADDF recovers, and the connection to the Web browser
is lost. This action is performed when a software upgrade is required.
Before activation, check that the ISD state is inactive, and the ISD specific
details such as Item code and Software version correspond with the ISD
requested.
During recovery, the ADDF database is converted (when necessary) to the
new software version.
Note
If you select an inactive ISD, a warning is shown to indicate the impact
of the operation.
During recovery after an ISD switch, a sanity timer is running. This timer
enables the ADDF to fall back to the previous ISD if the switch was not
successful, for example, due to a conflict in the database. In this way, the
service is never affected. When this happens, the ADDF comes up with the
previous ISD. Check in this case whether the upgrade you were performing
is supported. The sanity timer will run for about one minute after the ADDF
is manageable. The ADDF being manageable is indicated by the green
LED stopping to blink.

Issue 1-3
4. ADDF recovery takes a few minutes, during this period the activity
LED will blink with 2 Hz. frequency.
5. After the green LED has stopped blinking, you can log into the ADDF,
alarm evaluation has been finished.
6. After the green LED has stopped blinking, the sanity timer will run for
one minute. Do not perform any database manipulations or
provisioning changes during this period. If the system restarts while
the sanity timer is running, for example due to a power cycle, the
ADDF selects the previous active software. The database changes
that were made during the sanity period are lost.
Check if the requested ISD is active after the ADDF is up again (Bank 1
always contains the active ISD). If the switchover was not successful, the
state of the second bank is "error during last image transition". This could
be caused by a power outage during recovery.
A software upgrade is not service affecting when correctly carried out.
Note
After a software upgrade has been performed, do not obtain any
changes in the ADDF configuration within one minute after you were
able to login, or the green LED stopped blinking.
For more configuration alternatives, see the Appendices 1-4 in this

document.

Issue 1-3
Commissioning ADDF
10 Commissioning ADDF
There are no ADDF-specific tasks that should be performed during the
commissioning phase.
See the Commissioning Open MGW customer document for general
commissioning instructions.

Issue 1-3
11 Integrating ADDF
There are no ADDF-specific tasks that should be performed during the
integration phase.
See the Integrating Open MGW into the MSC Server System customer
document for general integration instructions. If you are using ADDF, you
need to configure the PDH/TDM as described in section Configuring PDH
for TDM transport of the above mentioned document.
Note
In Ui5.0 release, you need to perform one specific task during the
integration phase, that is, setting the system time.
The system has an accurate Real Time Clock on board and will survive
a power outage of at least ten minutes. The time of this clock should be
set by the user. The clock is used for adding a time stamp to reported
alarms.
See Appendix 1 Configuring the system time for detailed instructions.

Issue 1-3
Performance monitoring
12 Performance monitoring
12.1 PM overview
The system supports non-intrusively near end and far end performance
monitoring on E1. It is possible to monitor up to 64 monitor points
simultaneously. For this purpose the following counters are available.
 BBE-counter: counts the number of Background Block Errors in the
CRC-4 overhead of timeslot 0 in the E1-signal for near end PM or the
number of REI indications in the E1-signal for far end PM.
 ES-counter: counts the Errored Seconds, every second which has
one error or more will be declared errored.
 SES-counter: counts the Severely Errored Seconds, every second
which has more than 300 BBEs will be declared severely errored.
Every second with a raised E1cLOS, E1cAIS or P12ScLOF is also
declared severely errored
 UAS-counter: counts the UnAvailable Seconds. Displays the same
value as the SES-counter as soon as more than 10 consecutive SES
errors occur.
 FAS-counter: counts the number of Frame Alignment Signal errors in
the incoming E1 signal.
 EFS-counter: counts the EFS percentage. The percentage of error
free seconds as part of the measured seconds.
 DM-counter: counts the Deteriorated Minutes Percentage. The
percentage of deteriorated minutes as part of the measured minutes.
A minute is deteriorated if the CRC-4 violation is reported for 60
consecutive seconds.
Note
P12ScLOF alarms are not reported on the GUI.
Furthermore six unavailable periods, UAPs, time stamps are maintained.

These time stamps contain the start and end time of an UAS.

Issue 1-3
The system also supports system performance monitoring. This is a single

monitoring point which has the following counters available.
 Power Fail-counter: counts the number of power failures on one of
the dual power feeds of the system.
 Timing Link Switch-counter: counts changes of the system timing
state and the selected timing source.
The counters are stored in current and history bins of 15 minutes (15m) and
24 hours (24h). Performance monitoring can be provisioned for all E1 ports.
The table shows the number of available bins.
Table 11. Available bins
Bin 15m 24h
Current 1 1
History 16 1
The counters can be provisioned to raise alarms (Threshold Crossing
Alerts). Such an alarm is raised if the value of a counter is larger than the
provisioned threshold.
Note
After a cold or warm reset the PM data is lost.
12.2 Add/Delete PM points

To Add or Delete PM points, select PM | PDH | NE |ADD/DEL.
Figure 28. Add or delete PM points
Add
The selection can be added with a 15 minute register (with or without
alarmed), 24 hours register (with or without alarmed) or both. To provision a

Issue 1-3
PM selection, select the trib Slot - trib Port combination, check 15 minute
register,24 hours register or both. Optionally check alarmed, next click Add.
Delete
To delete it, select the trib Slot - trib Port combination, select a 15 minute
register, 24 hours register or both and click Delete.
12.3 PM Threshold
The PM points can be provisioned to raise alarms with option alarm
enabled (Threshold Crossing Alerts). Such an alarm is raised if the value of
a counter is larger than the provisioned raise threshold. The alarm is
cleared if the value in a succeeding bin is smaller than the provisioned clear
threshold. These thresholds can be provisioned per 15 minutes (15m) and
24 hours (24h) bin per port.
Select PM | PDH | NE | THRESHOLDS.
Figure 29. Select Trib slot - Trib port
Select the Trib slot - Trib port combination and click Edit.

Issue 1-3
Figure 30. PM Thresholds
The figure shows the default values for the BBE, ES, SES, UAS, FAS,
EFS and DM clear and raise counters for the selected combination. The
alarmed flag is used to enable/disable the alarming for thresholding.
12.4 PM Current Data View/Reset/Refresh

Use PM | PDH | NE | CURRENT DATA to display the actual PM data.
Figure 31. PM Current data
Next select the Trib slot - Trib port combination, check 15m and/or 24h and
click View.

Issue 1-3
Figure 32. View Current PM data
Click Reset to reset the current data view. All counters of the selected ports
for both near end and far end will be set to 0 and Suspect will change into
Yes.
Suspect
The suspect flag indicates that the performance data for the current period
may not be reliable (ITU- T 822). The main reasons to set the suspect flag
is when a bin is started and if a history bin lacks 10 seconds of data. The
value of the suspect flag is Yes (set) or No (not set).
Use Refresh to retrieve the actual data, due to the algorithm it has a delay
of 10 seconds.
12.5 PM History data View

Use PM | PDH | NE | HISTORY DATA to achieve the logged PM data. Use
Figure 33. PM History data

Issue 1-3
Next select the Trib slot - Trib port combination, check any combination of
15m, 24h, and nonzero and click View. Option nonzero will retrieve only
bins with counters that is more than 0.
Figure 34. View History PM data
of 10 seconds.
12.6 PM UAP Log

Per PM point six unavailable periods (UAPs) are maintained. These
periods contain the Begin and End time of a UAP.
Use PM | PDH | NE | UAP LOG to display the UAP log selection screen,
next click View.
Figure 35. PM UAP log selection

Issue 1-3
Figure 36. PM UAP log view
Begin shows the start time of the UAP, End the end time.
of 10 seconds
12.7 Configure System Performance Monitoring

To enable System Performance Monitoring select PM|System|Add/Del.
The PM points can be provisioned to raise alarms with option alarm

enabled (Threshold Crossing Alerts). Such an alarm is raised if the value of
a counter is larger than the provisioned raise threshold. The alarm is
cleared if the value in a succeeding bin is smaller than the provisioned clear
threshold. These thresholds can be provisioned per 15 minutes (15m) and
24 hours (24h) bin per port. After enabling either 15m or 24h monitoring the
thresholds can be set.

Issue 1-3
12.8 System PM Current Data View/Reset/Refresh

Use PM|System|Current Data to display the actual PM data.
Click Reset 15min bin / Reset 24hrs bin to reset the current data view. All
counters of the selected period will be set to 0 and Suspect will change into
Yes.
Suspect
The suspect flag indicates that the performance data for the current period
may not be reliable (ITU-T822). The main reasons to set the suspect flag is
when a bin is started and if a history bin lacks 10 seconds of data. The
value of the suspect flag is Yes (set) or No (not set).
of 10 seconds.
12.9 System PM History Data View/Refresh

Use PM|System|History Data to display the logged PM data.

Issue 1-3
of 10 seconds.
.

Issue 1-3
13 ADDF alarms
13.1 Alarming
The System supports alarm reporting for all SDH levels (RS, MS, VC4 and
VC12), equipment related alarms, port related alarms and synchronization
related alarms. These alarms will be reported to the Web browser, the
SNMP manager when provisioned and can be visible at the System LEDs.
When a defect is present it will be reported as an alarm within 2.5 ± 0.5
seconds. When the cause of a raised alarm is cleared within 10 ± 0.5
seconds the clearing will be reported and the alarm is added to the history
list.
13.1.1 Most recent alarm bar
Below the System layout on the Web browser the most recent alarm is
shown with the raised time, and the number of outstanding active alarms.
Figure 37. Recent Alarm List
Total, Most recently raised, Raised

Total represents the number of alarms. Most recently raised is shown with
the location and the type of alarm, followed by the severity. The time
Raised is shown based in the local time zone.
[!]: This button appears when the alarm situation changes: either a new
alarm is raised or an existing alarm has been cleared. Press [!] to clear this
indicator.
Alarm refresh rate
MENU: ALARMS | GUI SETTINGS
Figure 38. GUI Settings

Issue 1-3
ADDF alarms
This refresh rate is specific for every Browser connection and will be set to
the default value of 5 seconds when reloading the browser page or re-
logging in to the System. Selecting None/Stop will no longer update the
most recent alarm bar. The refresh rate can be set to 1, 5, 10, 60, 300
seconds or none/stop.
13.2 LED indicators

Though led indicators are described in this section no provisioning is
applicable for them.
System LED indicators
The System has three LED indicators:
 Active LED (green): indicating System is on (power led) and the
initializing status.
 Yellow LED: indicating a minor fault is reported.
 Red LED: indicating a major fault is reported.
For the Yellow and Red Led some specific behavior is there:
They do indicate only those alarms that are the consequence of defects
detected in the System. This means that SSF, RDI and AIS alarms do not
contribute to the LED state.
When a loss of signal alarm (STM1cLOS or E12cLOS or DS1cLOS) is
present the led will blink, but when at the same time another alarm with
same severity is raised the led will be lit continuously.
LAN Port LED indicators
The LAN port has two LED indicators:
 Green LED: LAN link status. LAN communication should be possible
from or to the System, if the link is up.
 Yellow LED: LAN activity present.

Issue 1-3
13.3 System alarms

Alarm Description Default Default
severity reporting
SYScDBBCKP Meaning of the alarm: Major Yes
 This alarm is raised when a database backup failed. It
is cleared when a database backup finished
successfully. The same alarm is used for autonomous
database backups as well as for the 'Backup Now'
functionality.
SYScTIME Meaning of the alarm: Major Yes

 The System time is not set or lost. The System time is
running from start up on the default linux clock.
Effect of the alarm:

 Alarms will be reported with a wrong timestamp, not
the real time.
Instructions for operator:

 System time has not been provisioned. Or System
time has been lost due to a power outage longer than
10 minutes.
SYScPFA Meaning of the alarm: Major No

 Power failure on telecom power feed (-48V)
connector A.

 When this alarm is reported the System has another
power feed, but redundant powering on feed A is
unavailable.

 No power connected to power feed A. Or voltage is
below 40.5 Volt. Or the -48 and 0 connections are
swapped, the System will operate but a SYScPFA is
reported. The default reporting state is not reported.
When monitoring is required the state must be set to
reported. The AU4 container contains AIS.
SYScPFB Meaning of the alarm: Major No

 Power failure on telecom power feed (-48V)
connector B.

 When alarm is reported the System has another
power feed, but redundant powering on feed B is
unavailable.

Issue 1-3
ADDF alarms
 No power connected to power feed B. Or voltage is

below 40.5 Volt. Or the -48 and 0 connections are
swapped, the System will operate but a SYScPFB is
reported. The default reporting state is not reported.
When monitoring is required the state must be set to
reported.
Note: For Power over Ethernet no power monitor is

available. This is a nonredundant input and mixing PoE
and telecom power feed is forbidden.
SYScEQF Meaning of the alarm: Major Yes

 An equipment failure has been detected on the
System.

 The System has become unreliable.

 Replace the System, and return the failed System.
SYScROUTE Meaning of the alarm: Minor

 There are more than 50 nodes in an OSPF AS.

 Performance problems can occur.

 Reduce the number of nodes in the OSPF AS
13.4 Pluggable items

severity reporting
IFCcUNP Meaning of the alarm: Major Yes
 A unit not present for the identified slot has been
detected, although a unit is expected.

 Transmission provisioned towards this slot will be lost.

 The interface card of an assigned slot has been
removed. Reinsert the correct Interface Card or when
no Interface Card is desired for this slot position
change the slot state to AUTO.

Issue 1-3
IFCcWUI Meaning of the alarm: Major Yes

 A wrong unit inserted has been detected for the
identified slot.

 Transmission provisioned towards this slot will be
disabled; the interface on the card will be shut down.
When a port of the Interface Card is assigned as
timing source this reference is declared failed with a
SYNCcTLF, to prevent synchronization from an
invalid reference.

 The inserted interface card has a not supported item
code. Replace the Interface Card by a supported
type.
IFCcREPL Meaning of the alarm: Major Yes

 A different Interface Card as the previous inserted
one has been inserted. But the item code of the
inserted Interface Card is within the range of
supported Interface Cards.

 Transmission is retained towards the Interface Card,
but depending on the e.g. impedance of this card and
the previous inserted card, transmission might be
affected.

 Accept the Interface Card. Take care cabling is
according to this Interface Card.
IFCcEQF Meaning of the alarm: Major Yes

 An equipment failure has been detected on the
identified Interface Card.

 Transmission is not shut down, but due to the nature
of the failure transmission can be lost. When a port of
the Interface Card is assigned as timing source this
reference is declared failed with a SYNCcTLF, to
prevent synchronization from an invalid reference.

 Replace IFC.
SFPcUNP Meaning of the alarm: Major Yes

 A SFP not present has been detected for the
identified line port position.

 Transmission to that line port will be lost.

Issue 1-3
ADDF alarms

 Reinsert a correct SFP with the correct module
qualifier.
SFPcWUI Meaning of the alarm: Major Yes

 A wrong SFP inserted has been detected for the
identified line port. The module qualifier of the
inserted SFP differs from the last accepted SFP.

 Transmission will be shut down to this line port. When
this port is assigned as timing source this reference
will be declared failed with a SYNCcTLF.

 Reinsert an SFP with an identical module qualifier as
the last accepted one. Or change the state to AUTO
and the System will set the current inserted SFP to
operational.
SFPcEQF Meaning of the alarm: Major Yes

 An equipment failure has been detected for the
inserted SFP.

 Transmission is not shut down, but due to the nature
of the fault transmission can be affected.

 Replace the SFP with an identical one (same module
qualifier) and return the failed SFP.
13.5 Synchronization alarms

severity reporting
SYNCcBHO Meaning of the alarm: Major Yes
 System timing has fall back to hold over mode. The
System is running on its hold over clock. None of the
provisioned references is available or has sufficient
quality.

 Transmission is not affected, but the System timing is
not locked to a valid reference.

Issue 1-3
 Check if any timing source is provisioned. Check if the

provisioned timing sources do have a timing link
failure SYNcTLF and if they are in MONITORED
mode.
SYNCcTLF Meaning of the alarm: Major Yes

 A timing link failure has been detected for the
identified timing source. No reference assigned for
this timing source or the signal has one of the next
failures:
- For line ports: RS1cTIM, STM1 cLOS,
STM1cLOF, MS1cAIS
- For tributary ports: E12cLOS, E12cAIS,
DS1cLOS or DS1cAIS.
 Or the timing reference has a frequency deviation of
more than ±15 ppm related to the internal clock of the
System.

 This timing source will not be part of the System
timing selection. When another reference is available
the System timing will select that one. When no other
timing source is available the System timing will
switch to holdover and the SYNCcBHO will be
reported.

 Check the signal provided to the timing source has a
defect and resolves that cause, or if none timing
source has been assigned to the identified timing
source.
SYNCcLRR Meaning of the alarm: Major Yes

 Loss of re-timing reference, a retimed E1 port has
fallen back in its retiming mode.

 The output frequency of this E1 port does not have
the quality requested. The System connected to it,
using this timing source must use another timing
reference.

 The System timing QL is below the acceptance QL of
the retimed E1 port. Check why System timing QL
has decreased.
13.6 Port alarms

Issue 1-3
ADDF alarms

severity reporting
E12cLOS Meaning of the alarm Major Yes
 The identified E1 port has a loss of signal detected.

 Transmission via this E1 port in the upstream
direction will be lost and AIS is inserted in the
upstream direction.

 Check cabling towards the E1 port.
E12cAIS Meaning of the alarm: Minor Yes

 On the ingress direction of the identified E1 port AIS
is detected.

 Signal is present at the E1 port but this signal
contains AIS. This is due to a defect at the System
connected to the E1 port.

 Check alarms on the System connected to the E1
port.
STM1cLOS Meaning of the alarm: Major Yes

 The identified line port has a loss of signal detected.

 Transmission via this line port in the downstream
direction is lost. In the downstream direction AIS is
inserted. In the upstream direction (return path) MS
RDI is inserted.

 Check cabling on the line port.
STM1cLOF Meaning of the alarm: Major Yes

 The identified line port has signal present but no
correct STM-1 frame is detected.

RDI is inserted

 Check signal provided to this line port. E.g. a STM4
signal might be provided or input might be
overloaded.

Issue 1-3
DS1cLOS Meaning of the alarm: Major Yes

 The identified DS1 port has a loss of signal detected.

 Transmission via this DS1 port in the upstream
direction will be lost and AIS is inserted in the
upstream direction.

 Check cabling towards the DS1 port
DS1cAIS Meaning of the alarm: Minor Yes
 On the ingress direction of the identified DS1 port AIS
is detected.

 Signal is present at the DS1 port but this signal
contains AIS. This is due to a defect at the System
connected to the DS1 port.

 Check alarms on the System connected to the DS1
port
13.7 Termination point alarms

severity reporting
RS1cTIM Meaning of the alarm: Major Yes
 A trail trace identifier mismatch has been detected on
the identified line port.

RDI is inserted

 Check the accepted and expected TTI for this port.
The System might be connected to the wrong far end
system or port.
RS1cSSF Meaning of the alarm: Major Yes

 A server signal fail on the RS layer has been detected
for the identified line port. The root cause is a failure
in the layer above.

 Transmission is lost in the downstream direction of
this line port.

Issue 1-3
ADDF alarms

 Check the root cause of this RS1cSSF. Might be due
to a STM1cLOS, or STM1cLOF.
MS1cSSF Meaning of the alarm: Major Yes

 A server signal fail on the MS layer has been
detected for the identified line port. The root cause is
a failure in the layer above.

 Transmission is lost in the downstream direction of
this line port.

 Check the root cause of this failure. Might be due to a
STM1cLOS, STM1cLOF or RS1cTIM.
MS1PcSSF Meaning of the alarm: Major Yes

 A server signal fail has been detected on the MS1
protection layer, only applicable when MSP is
provisioned.

 Transmission is lost in downstream direction of the
MS protection group

 Both line ports do have an MS related failure, or a
forced switch is in place to a failed line port.
MS1cAIS Meaning of the alarm: Minor Yes

 AIS is detected in the MS signal of the identified line
port. The root cause will be a failure in the far end
system.

 Transmission is lost in the downstream direction. In
the upstream direction MS RDI is inserted.

 Check alarms on the far end system.
MS1cRDI Meaning of the alarm: Minor Yes

 A remote defect indication is detected on the
identified line port.

 At the far end system an MS failure is detected.

Issue 1-3
 Check MS alarming on the far end system.
MS1cDEG Meaning of the alarm: Minor Yes

 The number of B2 background block errors detected
on the identified line port does exceed the provisioned
degraded threshold.

 Transmission is affected as bit errors will disturb the
signal.

 The STM-1 signal received has a degraded quality
due to too much attenuation or dispersion. Check the
optical path or the SFP being used at the far end has
insufficient power. In some cases overload of the
input signal might lead to an MS degraded signal.
MS1PcFOP Meaning of the alarm: Major Yes

 STM-1 MS Protection switching protocol failure. This
alarm is raises if there is a configuration mismatch
between the Near End and Far End node of a bi-
directional MSP group.
AU4cAIS Meaning of the alarm: Minor Yes

 The AU4 container contains AIS.

 Transmission in the downstream direction is lost.

 The root cause is in the layer above or due to a failure
in the far end system. Check MS and RS alarms on
the related line port or alarms on the far end system.
AU4cLOP Meaning of the alarm: Major Yes

 No valid AU4 pointer is present in the AU4 container.

 Transmission in the downstream direction is lost.

 An invalid AU4 signal is received.
VC4cSSF Meaning of the alarm: Major Yes

 A server signal fail has been detected on the
identified VC4 termination point

 Transmission is lost in the downstream direction and
VC4 RDI inserted in the upstream direction.

Issue 1-3
ADDF alarms

 The root cause of this alarm is a failure in the layer
above. This might be due to a RS, MS or AU4 failure
which sends AIS downstream.
VC4cUNEQ Meaning of the alarm: Major Yes

 The received signal label (C2 byte) at the VC4
termination points is zero.

 Transmission is lost in the downstream direction, AIS
is inserted. In the upstream direction VC4 RDI is
inserted.

 The far end system connected to might not have a
VC4 cross connection towards this system.
VC4cPLM Meaning of the alarm: Major Yes

 The received signal label (C2 byte) at the VC4
termination differs from the expected value. The type
of traffic in the VC4 does not match.

is inserted.

 The VC4 coming from the far end system does not
have a label 01 (equipped) or TUG structured (02) but
a different kind of traffic. Check in the details of the
related VC4 TTP the accepted TSL value. The far end
system does have wrong type of traffic. The
VC4cPLM alarm is not under control of the monitoring
flag.
VC4cTIM Meaning of the alarm: Major Yes

 A trail trace identifier mismatch has been detected at
the identified VC4 termination point. The accepted
(received) trail trace (J1 byte) does not match the
expected trail trace and TIM detection is enabled.

is inserted. In the upstream direction VC4 RDI is
inserted.

 Check the expected and accepted trail trace. A
difference might be due to a wrong cross connect in
the transmission path between the near and far end
VC4 TTP. If no match is required TIM detection can
be disabled thus no alarms is raised and no

Issue 1-3
consequent actions are executed.
VC4cDEG Meaning of the alarm: Minor Yes

 The number of background block errors in the
received B3 byte does exceed the provisioned
degraded threshold.

 Transmission is affected as bit errors are present.

 Check upstream cabling and or equipment, an
MS1cDEG might also be present.
VC4cLOM Meaning of the alarm: Major Yes
 The VC4 received does not contain the TU12 multi
frame indicator.

 Transmission is affected in downstream direction, AIS
is inserted.

 As no VC4cPLM is raised the traffic type is correct,
but the TUG structured VC4 may contain a TU3
container instead of only TU12.
VC4cRDI Meaning of the alarm: Minor Yes

 The VC4 remote defect indicator is detected in the
received VC4.

 Transmission might be affected at the far end side.

 The far end system has detected a downstream
failure at VC4 level. Check alarming at the far end
system.
TU12cAIS Meaning of the alarm: Minor Yes

 The TU12 contains AIS. The TU12cAIS is identified
by the TU12 number (klm) at the line port side.

 Transmission is lost in this TU12, no consequent
actions.

 Check upstream defects.
TU12cLOP Meaning of the alarm: Major Yes

 No TU12 pointer is detected in the TU12 identified.
The TU12cLOP is identified by the TU12 number

Issue 1-3
ADDF alarms
(klm) at the line port side.

 Transmission is lost in this TU12 container.

 Check far end provisioning, a TUG without TU12
pointer might be used e.g. TU3.
VC12cSSF Meaning of the alarm: Major Yes

 The VC12 layer is unavailable for traffic due to a
failure in layers above (VC4, MS).

 Transmission is lost. For a VC12 trail termination
point AIS is inserted downstream and VC12 RDI is
inserted upstream in case of a bi-directional cross
connect.

 Check alarming at the VC4 layer.
VC12cUNEQ Meaning of the alarm: Major Yes

 The received signal label (V5 byte) at the VC12
termination points is zero.

 Transmission is lost in the downstream direction. For
a VC12 trail termination point AIS is inserted. In the
upstream direction VC12 RDI is inserted. When
provisioning cross connects on both side of a
connection, temporarily a VC12cUNEQ might be
raised due to the absence of the cross connect at the
far end.

 The far end system connected to might not have a
VC12 cross connection towards this system or any
other System in the transmission path.
VC12cPLM Meaning of the alarm: Major Yes

 The received signal label (V5 byte) at the VC12
termination differs from the expected value. The type
of traffic in the VC12 does not match.

a VC12 trail termination point AIS is inserted.

 The VC12 coming from the far end system does not
have a label 01 (equipped) or asynchronous (02) but

Issue 1-3
a different kind of traffic. Check in the details of the

related VC12 TTP the accepted TSL value. The far
end system does have wrong type of traffic. The
VC12cPLM alarm is not under control of the
monitoring flag.
VC12cTIM Meaning of the alarm: Major Yes

 A trail trace identifier mismatch has been detected at
the identified VC12 termination point. The accepted
(received) trail trace (J2 byte) does not match the
expected trail trace and TIM detection is enabled.

a VC12 trail termination point AIS is inserted. In the
upstream direction VC12 RDI is inserted.

 Check the expected and accepted trail trace. A
difference might be due to a wrong cross connect in
the transmission path between the near and far end
VC12 TTP. If no match is required TIM detection can
be disabled thus no alarms is raised and no
consequent actions are executed.
VC12cDEG Meaning of the alarm: Minor Yes

 The number of background block errors in the
received TU BIP byte exceeds the provisioned
degraded threshold.

 Transmission is affected as bit errors are present.

 Check upstream equipment and or cabling, a
VC4cDEG or MS1cDEG might be present.
VC12cRDI Meaning of the alarm: Major Yes

 The VC12 remote defect indicator is detected in the
received VC4.

 Transmission might be affected at the far end side.

 The far end system has detected a downstream
failure at VC12 level. Check alarming at the far end
system.

Issue 1-3
ADDF alarms
13.8 Performance monitoring alarms

P12sNBBEcTHR15 Meaning of the alarm: Minor Yes
 The number of BBE errors for the 15m NE bin
exceeds the threshold.

signal.
P12sNBBEcTHR24 Meaning of the alarm: Minor Yes
 The number of BBE errors for the 24h NE bin

signal.
P12sNEScTHR15 Meaning of the alarm: Minor Yes

 The number of ES errors for the 15m NE bin exceeds
the threshold.

signal.
P12sNEScTHR24 Meaning of the alarm: Minor Yes

 The number of ES errors for the 24h NE bin exceeds
the threshold.

signal.
P12sNSEScTHR15 Meaning of the alarm: Minor Yes

 The number of SES errors for the 15m NE bin

signal.
P12sNSEScTHR24 Meaning of the alarm: Minor Yes

 The number of SES errors for the 24h NE bin

signal.

Issue 1-3
P12sNUAScTHR15 Meaning of the alarm: Minor Yes

 The number of UAS errors for the 15m NE bin

signal.
P12sNUAScTHR24 Meaning of the alarm: Minor Yes

 The number of UAS errors for the 24h NE bin

signal.
P12sNFAScTHR15 Meaning of the alarm: Minor Yes

 The number of Frame Alignment Signal errors for the
15m NE bin exceeds the threshold.

signal.
P12sNFAScTHR24 Meaning of the alarm: Minor Yes

 The number of Frame Alignment Signal errors for the
24h NE bin exceeds the threshold.
P12sNEFScTHR15 Meaning of the alarm: Minor Yes

 The Error Free Seconds percentage for the 15m NE
bin exceeds the threshold.

signal.
P12sNEFScTHR24 Meaning of the alarm: Minor Yes

 The Error Free Seconds percentage for the 24h NE
P12sNDMPcTHR15 Meaning of the alarm: Minor Yes

 The Deteriorated Minute percentage for the 15m NE
bin exceeds the threshold. (The font and format for
this sentence is different with others)

signal.
P12sNDMPcTHR24 Meaning of the alarm: Minor Yes

 The Deteriorated Minute percentage for the 24h NE

Issue 1-3
ADDF alarms

signal.
P12sFBBEcTHR15 Meaning of the alarm: Minor Yes

 The number of BBE errors for the 15m FE bin

signal.
P12sFBBEcTHR24 Meaning of the alarm: Minor Yes

 The number of BBE errors for the 24h FE bin exceeds
the threshold.

signal.
P12sFEScTHR15 Meaning of the alarm: Minor Yes

 The number of ES errors for the 15m FE bin exceeds
the threshold.

signal.
P12sFEScTHR24 Meaning of the alarm: Minor Yes

 The number of ES errors for the 24h FE bin exceeds
the threshold.

signal.
P12sFSEScTHR15 Meaning of the alarm: Minor Yes

 The number of SES errors for the 15m FE bin

signal.
P12sFSEScTHR24 Meaning of the alarm: Minor Yes

 The number of SES errors for the 24h FE bin exceeds
the threshold.

Issue 1-3

signal.
P12sFUAScTHR15 Meaning of the alarm: Minor Yes

 The number of UAS errors for the 15m FE bin

signal.
P12sFUAScTHR24 Meaning of the alarm: Minor Yes

 The number of UAS errors for the 24h FE bin exceeds
the threshold.

signal.
P12sFEFScTHR15 Meaning of the alarm: Minor Yes

 The Error Free Seconds percentage for the 15m FE

signal.
P12sFEFScTHR24 Meaning of the alarm: Minor Yes

 The Error Free Seconds percentage for the 24h FE

signal.
P12sFDMPcTHR15 Meaning of the alarm: Minor Yes

 The Deteriorated Minute percentage for the 15m FE

signal.
P12sFDMPcTHR24 Meaning of the alarm: Minor Yes

 The Deteriorated Minute percentage for the 24m FE

signal.

Issue 1-3
ADDF alarms
13.9 Digital input alarms

ENVcDI Meaning of the alarm: Major No
 A digital input alarm raised due to a customized digital
input.

 Transmission is not affected.

 Check the cause of the alarm.

Issue 1-3
14 Troubleshooting ADDF
All troubleshooting related to PDH and SDH is described in the Open MGW
customer documentation. For more information, see the Troubleshooting
Open Multimedia Gateway document.
For more information about resolving alarms and problems, see Chapter
RESOLVING ALARMS AND PROBLEMS GUIDE on page 156 of User
Guide ADX100, ADX200, ADX201.

Issue 1-3
Appendix 1 Configuring the system time
Appendix 1 Configuring the system time

The system time can be set manually.
The system has an accurate Real Time Clock on board and will survive
a power outage of at least ten minutes. The time of this clock should be
set by the user. The clock is used for adding a time stamp to reported
alarms and logs.
When no time is set, the default Linux time is taken at startup: January
1, 1970. The SYScTIME alarm is reported, if the RTC indicates that its
time is invalid. The alarm is cleared when the system time is set.
MENU: SYSTEM | TIME | MANUAL
Figure 39 System – Time (yyyy.mm.dd hh:mm:ss)
System time (UTC)

Shows the current time of the ADDF. A Refresh is needed to retrieve
the current value.
Host date and time (Local or UTC)
Shows the date and time of the PC connected to the ADDF. This field is
continuously updated.
You can change the time in two ways:
 Sync: Use this button to place the current Host date and time to
the System time.
 Fill in the values in the System time field.
Note
Use the correct format and values. Then press Apply.

Issue 1-3
Appendix 2: Managing system recovery

Some actions related to the ADDF software or database may result in an
ADDF System recovery. An ADDF System recovery takes a few
minutes. An ADDF System recovery is not service affecting.
Communication with the web browser(s) and SNMP manager(s) is lost.
Two minutes after the recovery, the user can login again. During
recovery, the green (active) LED blinks. When the LED has stopped
blinking, the alarms are evaluated. After the ADDF has come up, a cold
restart trap is sent to the provisioned SNMP manager(s).
In case of a system upgrade, the status of the ADDF is indicated as
soaked (see System software and software upgrade).
When a database failure is detected, ADDF automatically invokes an
ADDF System recovery at any time.
Figure 40 System initialization

Issue 1-3
Appendix 3 Configuring system database

A new ADDF has one default database, addf.db. This default database
is included in the ADDF software and is never lost. Database handling
can only be executed by admin users. The ADDF supports 8 databases,
one of which is active.
All provisioning items are part of the database, except for the IP, OSPF
and SNMP settings. The SNMP and IP settings are retained when
restoring, uploading, selecting, or deleting databases. The default
database has the following properties:
 Line and tributary ports in AUTO mode
 No VC12 crossconnections present
 Fixed VC4 crossconnect from Line1 <-> VC#1 and Line2 <->
VC4#2
 VC4 termination monitoring mode: Monitored
 No ADDF name and location
The default database also contains the default alarm settings.
Select MAINTENANCE | DATABASE to display an overview of all
databases.

Issue 1-3
Figure 41 Databases
The database is identified by its name. A postfix (active) after the

database name marks the active database.
Selecting a new database
Selecting a new database might result in incompatibility between the
current running software and the structure of the selected database. For
this reason, so called database conversion scripts are needed, which
are included in the active ISD.
Conversion is only supported from a lower database version to a higher
one. If, for example, you select a database version #1 and the current
running software supports database version #3, a conversion form #1 ->
#3 is needed. The ADDF first converts #1 -> #2, followed by a
conversion from #2 -> #3. ADDF then removes both the original (#1) and
the intermediate (#2) database(s). For fail safe operation, you should
make a backup of this database by downloading it to a host system.
Note
The converted database receives the hardware identification of the
hardware on which the conversion takes place.
This operation takes a few seconds, and it is also dependent on the

amount of conversions needed. The request might be rejected if:
 A database is selected for which conversion is required but no
tooling or script is available. Note that this implies that the
selection of a database with a version number higher than the
current active database version number is rejected.
 The database file does not exist, because it has been removed by
a concurrent database operation.
 The database does not match the ADDF hardware.
 Communication with the ADDF is lost due to a concurrent
operation that results in a recovery action, for example, active
database selection, or software upgrade.
 Software sanity check is in progress, and database selection is not
permitted.
The type indicating the hardware it supports:
 19inch2u-v1, ADH103, ADX201

Issue 1-3
Note
Databases are not compatible between ADDFs. For example, a
database for ADX100 is not compatible with a database for ADX201. A
database for a specific hardware version only operates on that hardware
version. The type of the database identifies the platform it suits. When
selecting an invalid database type, the selection is rejected.
Maintaining the database manually
Note
If a database operation is selected, a warning is displayed to indicate the
impact.
MENU: SYSTEM | DATABASE | MANUAL
Figure 42 Database maintenance
Restore
With this option, you can upload a database to the ADDF. By selecting
Browse, you can select the desired database via the PC connected to

Issue 1-3
the ADDF. A database must have the extension .db. The upload takes
less than one minute, depending on your network connection. Typical
database size is about 100 Kbytes. When the upload is finished, the
uploaded database is shown in the database list.
Note
The text in the Browse... button depends on your local language
settings.
Backup
With this option, you can make a copy (download) of the selected
database towards the connected PC.
1. Click on the file to backup.
2. Click Backup.
3. Follow the instructions.
Rename
With this option, you can rename the selected database.
Note
Rename without entering the .db extension.
Delete
With this option, you can remove a database from the ADDF. When
deleting the active database, the ADDF recovers and comes up with the
default database retaining the database name. Service is lost, but the
SNMP, OSPF and IP settings are not lost.
You can delete the default database, but it will still be present in the
ADDF software. When necessary, this database is created again and
started up.
Set as active
This option activates the selected database. The ADDF recovers. And
connection to the Web browser is lost. When the selected database has
different settings than the current one, transmission is affected. When
the selected database has identical settings, transmission is not
affected.
Copy Active
This option creates a copy of the active database with a specified
database name. This copy is stored on the ADDF.

Issue 1-3
Figure 43 Database Copy Active
Handling a default database and software downgrade

Chapter System database describes the default database included in the
software load. The operator can also save an existing configuration as a
new default database. This default database is used when the ADDF
starts up without an active database, for example, after a manual delete
operation, or when the ADDF system is downgraded from a new release
to an older one that does not support the database format of the new
release. This allows for a limited hitless downgrade when the following
steps are followed:
1. Save the current database as the new default database before you
perform an upgrade from an old release O to a new release N.
2. Switch to the new release N. The system converts the active
database to the new database format of release N.
3. If you decide that the old release should be used again, then
switch back to release O.
4. The system detects an incompatible database on the system and
deletes it. The previously saved default database is used.
5. The system uses the old release O with the database saved in
step 1. If no provisioning changes have been made between step
2 and 3, no impact on traffic is seen.
A saved default database is automatically named as default.db.
Using smart defaults
The database of one ADDF can be used at another ADDF of the same
hardware platform type. Specific databases can be prepared on one
ADDF, which can be uploaded to other ADDFs in the field. In this way,
an ADDF can be operational within a short period of time. In addition to
that, databases for specific scenarios, such as emergency cases, can be
stored at the required ADDF. When an emergency occurs, the specific
database can then be selected.

Issue 1-3
Appendix 4 Configuring log files

The user can retrieve log files manually.
Retrieving log files manually
1. To retrieve a log file manually, select:
MENU: MAINTENANCE | LOG | MANUAL
Figure 44 Manual log files
2. Use Backup to download the log file cmdlog.txt to a local file.

Use Delete to delete the log file from the ADDF.
Forwarding log file entries to a remote syslog server
The entries stored in the log file can be forwarded to a remote syslog
server. The operator has to specify the IP address of the remote server
and the port number. This feature should be used in combination with
remote management through a PPP link. If both PPP links are down, the
entries cannot be forwarded. A maximum of 200 entries are stored in the
system and sent to the remote syslog server when one of the PPP
links is up. If more than 200 entries are lost, the complete log file can be
retrieved using the FTP or TFTP option.

Issue 1-3
Appendix 4 Configuring log files
Figure 45 Maintenance- Log - Remote

Issue 1-3
Appendix 5 Transmission terms and definitions
Short overview of transmission terms used in this chapter:

Downstream
This is the direction coming from the STM-1 aggregate side into the
ADDF, the de-multiplexing direction.
Upstream
This the direction from the termination points towards the STM-1
aggregate side, the multiplexing direction.
Near end
This is the system at the local side of a protected connection.
Far end
This is the system terminating the transmission point at the other side of
a protected connection.
Connection
An end-to-end related path carrying service, which is terminated at both
ends.
Consequent action
This is an autonomous action of the ADDF. When a failure in the ADDF
is detected, it is reported as an alarm. This action inserts, for example,
an AIS signal in the downstream direction, or an RDI in the upstream
direction in case of a bidirectional crossconnect.
Ingress
The incoming side of a port.
Egress
The outgoing side of a port.

Issue 1-3

ADX 201 Installing - Addx PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ADX 201 Installing - Addx PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Open Multimedia Gateway, Rel. Ui5.

Installing Active DDF Device

DN0973532 © Nokia Siemens Networks 1 (94)

2 (94) © Nokia Siemens Networks DN0973532

Summary of changes ........................................................................................... 6

1 Product overview ................................................................................. 8

2 Hardware description .......................................................................... 9

3 ADDF HW configuration with Open MGW ........................................ 15

4 Hardware installation ......................................................................... 19

7 Configuring O&M connections.......................................................... 32

8 Installing software ............................................................................. 35

9 Provisioning of the ADDF without Open MGW ................................ 37

DN0973532 © Nokia Siemens Networks 3 (94)

9.3 Configuring pluggable items ................................................................. 40

10 Commissioning ADDF ....................................................................... 53

13 ADDF alarms ...................................................................................... 64

14 Troubleshooting ADDF ...................................................................... 84

Appendix 1 Configuring the system time ......................................................... 85

Appendix 2: Managing system recovery .......................................................... 86

4 (94) © Nokia Siemens Networks DN0973532

Appendix 3 Configuring system database ....................................................... 87

Appendix 4 Configuring log files ...................................................................... 92

Appendix 5 Transmission terms and definitions ............................................. 94

DN0973532 © Nokia Siemens Networks 5 (94)

Changes between document issues are cumulative. Therefore, the latest

Changes between issue 1-3 and issue 1-2

6 (94) © Nokia Siemens Networks DN0973532

DN0973532 © Nokia Siemens Networks 7 (94)

Figure 1 Open MGW architecture with ADDF

ADDF consists of HW and SW module. For HW module, see Chapter 2 to

8 (94) © Nokia Siemens Networks DN0973532

2.1 Active Digital Cross-Connect ADX201

Figure 2 Active Digital Distribution Frame ADX201

9 (94) © Nokia Siemens Networks DN0973532

Dimensions: 88 x 450 x 171 mm (HxWxD)

Weight: 3.1 kg (with interface cards)

Table 1 ADX201 technical data

2.1.1 Interface card for external E1/T1 interfaces

The ADX201 supports following interface cards:

Figure 3 E1/T1 RJ-45 interface card

10 (94) © Nokia Siemens Networks DN0973532

Figure 4 E1/mini-coaxial interface card

2.1.2 Specifications of external E1/T1 interfaces

PDH TDM interfaces

Table 2.TDM E1 interface specifications

Interface type PDH (ITU-T G.703)

11 (94) © Nokia Siemens Networks DN0973532

Framing structure G.704

Table 3 TDM T1 interface specifications

E1 and T1 balanced cable

12 (94) © Nokia Siemens Networks DN0973532

Table 4 RJ-45 connector pinouts

E1 unbalanced (coaxial) cable

Table 5 Mini coax connector pinouts

2.2 Power distribution unit

13 (94) © Nokia Siemens Networks DN0973532

Figure 5 Front and rear view of PDU

14 (94) © Nokia Siemens Networks DN0973532

3 ADDF HW configuration with Open MGW

15 (94) © Nokia Siemens Networks DN0973532

Figure 6 Two different cabinets’ configurations of ADX201 devices

16 (94) © Nokia Siemens Networks DN0973532

In case longer cables are needed, they are provided by Services.