User Manual (ADX)

User Guide
ADX100, ADX200, ADX201

ADX-7077 2055-01, Issue 1
March 2007
ADC Telecommunications, Inc.

Copyright
Copyright © 2007 ADC Telecommunications, Inc.
All rights reserved
The software contains proprietary information of ADC. It is provided under a license
agreement containing restrictions on use and disclosure and is also protected by
copyright law. Reverse engineering of the software is prohibited.
Due to continued product development this information may change without notice. The
information and intellectual property contained herein is confidential between ADC and
the client and remains the exclusive property of ADC. If you find any problems in the
documentation, please report them to us in writing. ADC does not warrant that this
document is error-free.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted
in any form or by any means, electronic, mechanical, photocopying, recording or
otherwise without the prior written permission of ADC.
Revision History
Issue: Issue 1
Date: 2007, March
Reason for change: Issued for release 1.3 of Systems.
Trademark Information
ADC and ADC Telecommunications are registered trademarks of ADC
Telecommunications, Inc.
Disclaimer of liability
Contents herein are current as of the date of publication. ADC reserves the right to
change the contents without prior notice.
In no event shall ADC be liable for any damages resulting from loss of data, loss of use,
or loss of profits and ADC further disclaims any and all liability for indirect, incidental,
special, consequential or other similar damages. This disclaimer of liability applies to all
products, publications and services during and after the warranty period.
This publication may be verified at any time by contacting ADC’s Technical Assistance
Centre.
This publication may be verified at any time by contacting ADC’s
Technical Assistance Center at 1-800-366-3891, extension 73475 (in
U.S.A. or Canada) or 952-917-3475 (outside U.S.A. and Canada), or by
e-mail to bcg_tac@adc.com (mailto:bcg_tac@adc.com).
2 © ADC Telecommunications, Inc.

Chapter March 2007 • ADX-7077 2055-01, Issue 1
Contents
1 About this manual 9

1.1 Safety warnings 9
1.2 Documentation conventions 9
2 General information 11
2.1 Warranty / software 11
2.2 Software service agreement 11
2.3 Repair / exchange policy 11
2.4 Repair charges 11
2.5 Replacement / spare products 12
2.6 Returned material 12
2.7 Customer information and assistance 12
2.7.1 Telephone 12
2.7.2 Post 13
2.7.3 Product information and technical assistance by e-mail 14
3 ETSI Compliance statements 15

3.1 Environmental 15
3.2 ESD and EMC 15
3.3 Safety 15
4 General safety precautions 17

4.1 Safety precautions 17
4.2 Power precautions 17
4.3 Environmental precautions 18
4.4 Mechanical precautions 18
5 System description 19
5.1 System overview and features 19
5.1.1 Key features 19
5.2 Feature descriptions 19
5.2.1 System software 20
5.2.2 System database 20
5.2.3 User administration 20
5.2.4 Log file 20
5.2.5 Real Time Clock 20
5.2.6 Powering 20
5.2.7 Test access port 21
5.2.8 Visual indicators 21
5.2.9 Inventory management 21
5.2.10 Tributary slots 21
5.2.11 Pluggable items 21
5.2.12 Line Protection (MSP) 21
5.2.13 Synchronization 21
5.2.14 E1 retiming 21
5.2.15 Alarm reporting 22
5.2.16 Cross connects 22
5.2.17 Overhead functions 22
5.2.18 Web server 22
5.2.19 SNMP 22
© ADC Telecommunications, Inc. 3

5.2.20 Single and Dual fiber SFPs 22

5.2.21 Path protection 22
5.2.22 Loopback 22
5.2.23 Remote management 22
5.3 Description of the interfaces 23
5.3.1 ADX100 Interfaces 23
5.3.4 E1 interfaces 24
6 Specifications 25
6.1 Hardware specifications 25
6.2 Dimensions and weight 25
6.2.1 ADX100 25
6.2.2 ADX200 26
6.2.3 ADX201 27
6.3 Environmental 27
6.4 Availability 28
6.5 Power 28
6.6 Interfaces 28
6.7 Synchronization 28
6.8 Mapping 28
6.9 Short ordering list 29
7 Management and remote management 31

7.1 Open shortest path first (OSPF) 31
7.2 Supported areas 31
7.3 Routers for OSPF 31
7.3.1 Area Border Router (ABR) 31
7.3.2 Autonomous System Border Router (ASBR) 32
7.3.3 Designated router and the backup designated router 32
7.3.4 Unnumbered network 32
7.4 Address resolution protocol (ARP) 32
7.5 The proxy address resolution protocol (PARP) 32
7.6 Link costs and signal rate 33
7.7 Line protection and OSPF 33
7.8 Assigning IP addresses for system management 33
7.9 Routing examples 35
7.9.1 Local management, host directly connected to System LAN and no routing protocol 35
7.10 Remote management examples 37
7.10.1 Terminal application and host connected to LAN 37
7.10.2 Multiple hosts and mix applications 40
7.10.3 Example with ASBR 41
7.10.4 Example with proxy ARP 42

8 Subnetwork connection protection (SNCP) 45

8.1 Introduction 45
8.2 Non intrusive monitoring (NIM) of line ports 46
8.3 Provisioning aspects 46
9 Port loopback functionality 47
10 Installation guide 49
10.1 General notices 49
10.2 Tools 49
10.3 Accessories 49
10.4 Mounting and installation ADX100 51
10.4.1 ADX100 for LSA-PLUS PROFIL rod mounting 51
10.5 ADX100 without Interface Cards 56
10.5.1 Interface Card installation 56
10.6 Mounting instructions ADX200 and ADX201 62
10.6.1 ADX200 62
10.6.2 Mounting material 200 (included in box) 62
10.6.3 ADX201 63
10.6.4 Mounting material ADX201 (included in box) 63
10.6.5 Mounting the ADX200/ADX201 63
10.7 Cables and pinning 68
10.7.1 DC power cable 68
11 Set up of the System 71

11.1 Connectors 71
11.1.1 LAN connector 71
11.1.2 Local Management console port 71
11.1.3 Telecom power feed 71
11.1.4 SFP modules 71
11.1.5 Interface Cards 71
11.1.6 Test access output 71
11.2 Powering 72
11.3 IP address management 72
11.3.1 IP management without DHCP server 72
11.3.2 LAN port provisioning via WEB browser 74
11.3.3 LAN provisioning via Ip2Box 75
12 GUI Settings and system authorization 77

12.1 Web browser and navigation 77
12.2 GUI settings 77
12.3 GUI features 77
12.4 User groups, login and rights 78
12.4.1 ADX100 Login screen 79
12.4.2 ADX100 GUI System Overview 80
12.4.4 ADX200 GUI System overview 81
12.4.6 ADX201 GUI System overview 82

12.5 Log file for System settings 83

12.6 Menu structure 84
13 Provisioning 87
13.1 Introduction 87
13.1.1 ADX100, ADX200 and ADX201 differences 87
13.2 Transmission terms and definitions 87
13.3 System time 88
13.4 Pluggable items 89
13.4.1 Interface Card 89
13.4.2 IFC replacement. 90
13.4.3 Small Form Pluggable 91
13.4.4 SFP replacement and acceptance 92
13.4.5 Single Fiber SFPs 92
13.5 System recovery 93
13.6 System software 93
13.6.1 Select inactive ISD 94
13.7 System database 96
13.7.1 Database maintenance 97
13.8 Ports and termination points 99
13.8.1 Ports 99
13.8.2 Line ports 99
13.8.3 Tributary Ports 100
13.8.4 Termination Points 101
13.8.5 Degraded Threshold provisioning and handling 105
13.8.6 Trail Trace Identifier provisioning and handling 106
13.8.7 Provisioning trail trace identifiers 107
13.8.8 Test access output 108
13.8.9 Remote error indication 109
13.9 Cross connects 109
13.9.1 Definitions 109
13.9.2 Listing, editing and deleting cross connects 111
13.9.3 Adding cross connects 113
13.10 Transmission protection MSP 117
13.10.1 Precautions 117
13.10.3 Creating an MSP pair 119
13.10.4 Deleting an MSP pair 120
13.10.5 MSP details 120
13.10.6 External MSP switch requests 121
13.11 Synchronization 122
13.11.2 Provisioning timing sources 124
13.11.3 Provisioning line port references 125
13.11.4 Provisioning tributary port references 126
13.11.5 System timing 127
13.11.6 System timing reference selection 128
13.11.7 Retiming E1 ports 129
13.12 SNMP 131
13.12.1 Current alarm list with SNMP 132
13.13 OSPF provisioning 132
13.13.1 OSPF settings 132
13.13.2 OSPF Interfaces 133
13.13.3 OSPF Systems 135
13.14 Alarming 135
13.14.1 Most recent alarm bar 135
13.15 Current Alarms 136
13.16 History alarms 137
13.17 Alarm profiles, severities, reporting and LEDs 138
13.17.1 Severities and reporting 138
13.17.2 Displaying provisioned alarm severities and reporting states 138
13.17.3 Reporting mode 138
13.17.4 LED indicators 139

14 Resolving alarms and problems guide 141

14.1 Introduction 141
14.2 Location 141
14.3 Alarm list overview 142
14.3.1 Monitoring mode 143
14.3.2 Pluggable item state 143
14.3.3 Replacing Systems 143
14.4 Alarm descriptions 143
14.4.1 System Alarms 143
14.4.2 Pluggable items 144
14.4.3 Synchronization alarms 145
14.4.4 Port alarms 146
14.4.5 Termination point alarms 147
14.5 SDH overview 150
14.5.1 SDH multiplex structure 150
14.5.2 SDH termination points 151
14.6 Synchronization Network 153
14.6.1 Provisioning for this network 154
15 List of acronyms and abbreviations 157
16 Index 161

Chapter 1 About this manual March 2007 • ADX-7077 2055-01, Issue 1

Chapter 1 About this manual March 2007 • ADX-7077 2055-01, Issue 1
1 ABOUT THIS MANUAL

This manual provides detailed information on the Active Digital Cross Connect ADX100,
ADX200 and ADX201 Systems. This document has been issued for Release 1.3 (see
"System software" on page 93). This user manual is written for end users responsible for
installation, network management and maintenance. It deals with installation, first set up,
full provisioning and management of the System and contains a guide to alarms (see
"Resolving alarms and problems guide" on page 139). This manual is in most cases
common for all products, ADX100, ADX200 and ADX201. In those cases where
differences exist they will be outlined. General information will be referred to as System,
instead of ADX100, ADX200 and ADX201.
1.1 Safety warnings

Important safety admonishments are used throughout this manual to warn of possible
hazards to persons or equipment. An admonishment identifies a possible hazard. The
admonishments — in the form of a Note, Caution and Danger — must be followed at all
times. These warnings are flagged by use of the triangular alert icon and are listed in
order of severity of injury or damage and likelihood of occurrence.
Note: Important information.
Caution: Failure to carefully read this information can lead to personal injury or
serious damage to the appliance or both.
Danger: Failure to carefully read this information can lead to death, personal injury
as well as serious damage to the appliance.
1.2 Documentation conventions

References to screen dumps of the software:
Clickable items like buttons are indicated by this font.
A selection from a menu is shown as: MENU1 | MENU2, in which MENU2 is a submenu of
MENU1.
Data fields or selections are referred to in this font.

Chapter 2 General information March 2007 • ADX-7077 2055-01, Issue 1

2 GENERAL INFORMATION
2.1 Warranty / software

The Product and Software warranty policy and warranty period for all ADC proaducts is
published in ADC’s Warranty/Software Handbook. Contact the Broadband Connections
Group (BCG) Technical Assistance Center at 1-800-366-3891, extension 73475 (in
U.S.A. or Canada) or 952-917-3475 (outside U.S.A. and Canada) for warranty or software
information or for a copy of the Warranty/Software Handbook.
2.2 Software service agreement

ADC software service agreements for some ADC Products are available at a nominal fee.
Contact the BCG Technical Assistance Center at 1-800-366-3891, extension 73475 (in
U.S.A. or Canada) or 952-917-3475 (outside U.S.A. and Canada) for software service
agreement information.
2.3 Repair / exchange policy

All repairs of ADC Products must be done by ADC or an authorized representative. Any
attempt to repair or modify ADC Products without authorization from ADC voids the
warranty.
If a malfunction cannot be resolved by the normal troubleshooting procedures contact
BCG Technical Assistance Center at 1-800-366-3891, extension 73475 (in U.S.A. or
Canada) or 952-917-3475 (outside U.S.A. and Canada). A telephone consultation can
sometimes resolve a problem without the need to repair or replace the ADC Product.
If, during a telephone consultation, ADC determines the ADC Product needs repair, ADC
will authorize the return of the affected Product for repair and provide a Return Material
Authorization number and complete shipping instructions. If time is critical, ADC can
arrange to ship the replacement Product immediately. In all cases, the defective Product
must be carefully packed and returned to ADC.
2.4 Repair charges

If the defect and the necessary repairs are covered by the warranty, and the applicable
warranty period has not expired, the Buyer’s only payment obligation is to pay the
shipping cost to return the defective Product. ADC will repair or replace the Product at no
charge and pay the return shipping charges.
Otherwise, ADC will charge a percentage of the current Customer Product price for the
repair or NTF (No Trouble Found). If an advance replacement is requested, the full price
of a new unit will be charged initially. Upon receipt of the defective Product, ADC will
credit Buyer with 20 percent of full price charged for any Product to be Out-of-Warranty.
Products must be returned within (30) days to be eligible for any advance replacement
credit. If repairs necessitate a visit by an ADC representative, ADC will charge the current
price of a field visit plus round trip transportation charges from Minneapolis to the Buyer’s
site.

2.5 Replacement / spare products

Replacement parts, including, but not limited to, button caps and lenses, lamps, fuses,
and patch cords, are available from ADC on a special order basis. Contact BCG
Technical Assistance Center at 1-800-366-3891, extension 73475 (in U.S.A. or Canada)
or 952-917-3475 (outside U.S.A. and Canada) for additional information.
Spare Products and accessories can be purchased from ADC. Contact Sales
Administration at 1-800-366-3891, extension 63000 (in U.S.A. or Canada) or 952-917-
3000 (outside U.S.A. and Canada) for a price quote and to place your order.
2.6 Returned material

Contact the ADC Product Return Department at 1-800-366-3891, extension 73748 (in
U.S.A. or Canada) or 952-917-3748 (outside U.S.A. and Canada) to obtain a Return
Material Authorization number prior to returning an ADC Product.
All returned Products must have a Return Material Authorization (RMA) number clearly
marked on the outside of the package. The Return Material Authorization number is valid
for 90 days from authorization.
2.7 Customer information and assistance
2.7.1 Telephone
Europe General
Sales Administration: +32-2-712-65 00
Technical Assistance: +32-2-712-65 42
Europe toll free numbers

Germany: 0180 2232923
United Kingdom: 0800 960236
Spain: 900 983291
France: 0800 914032
Italy: 0800 782374

USA and Canada

Sales: 1-800-366-3691 Extension 73000
Technical Assistance: 1-800-366-3891
Connectivity Extension: 73475
Wireless Extension: 73476
Asia / Pacific
Sales Administration: +65-6294-9948
Technical Assistance: +65-6393-0739
Elsewhere
Sales Administration: +1-952-938-8080
Technical Assistance: +1-952-917-3475
2.7.2 Post
USA
ADC Telecommunications, Inc
PO Box 110
Minneapolis MN55440-1101
USA
Singapore
ADC Telecommunications (S’PORE) PTE. LTD
100 Beach road
#18-01 Shaw towers
Singapore 189702
Germany
ADC Krone
Beeskowdamm 3-11
14167 Berlin
Germany

2.7.3 Product information and technical assistance by e-mail
connectivity.tac@adc.com
wireless.tac@adc.com
euro.tac@adc.com
asiapacific.tac@adc.com

Chapter 3 ETSI Compliance statements March 2007 • ADX-7077 2055-01, Issue 1
3 ETSI COMPLIANCE STATEMENTS
3.1 Environmental
The System has been certified to comply with ETSI 300019
Class 3.1 for operational conditions
Class 1.2 for storage
Class 2.3 for transportation
3.2 ESD and EMC

The EMC properties are in conformity with:
EN 300 386 v1.2.1 (2000-03)
EN 300 386 v1.3.1 (2001-09)
EN 300 386 v1.3.2 (2003-05)
3.3 Safety
Safety meets:
Electrical safety: According to IEC 950 and/or EN 60950-1
CE qualification:
According to low voltage directive 73/23/EEC and
EMC directive 89/336/EEC
Optical safety: Is determined by the SFP inserted
Thermal safety: Surface temperature or exposed component below 75 0C

Chapter 3 ETSI Compliance statements March 2007 • ADX-7077 2055-01, Issue 1

Chapter 4 General safety precautions March 2007 • ADX-7077 2055-01, Issue 1
4 GENERAL SAFETY PRECAUTIONS
4.1 Safety precautions
Caution: Read the installation section before you connect the system to the power
source.
Caution: This system is intended for installation in restricted areas. A restricted

area is where access can only be gained by service employees through the use of a
specific tool, lock and key, or other means of security, and is controlled by the authority
responsible for the location.
Caution: Only trained and qualified employees are allowed to install or replace the
Systems.
Caution: All ports are safety extra-low voltage (SELV) circuits. SELV circuits
should only be connected to other SELV circuits.
4.2 Power precautions
Caution: Only a DC power source that is isolated from AC mains with reinforced
insulation and that complies with the SELV requirements can be connected to the
system.
Caution: This product must be connected to an IEC60950 compliant limited power

source OR a Power over Ethernet (PoE) IEEE802.3af compliant power source.
Caution: This product relies on the buildings installation for short-circuit (over
current) protection. Ensure that the protective device is rated not greater than 1 ampere.
Caution: Do not use Power over Ethernet simultaneously with Telecom power
feeding.
Caution: Remove power before connecting or disconnecting ground or power wires

to the system.
To ensure that all power is OFF, locate the circuit breaker on the panel board that
services the DC circuit, switch the circuit breaker to the OFF position, and tap the switch
handle of the circuit breaker in the OFF position.

Chapter 4 General safety precautions March 2007 • ADX-7077 2055-01, Issue 1
Caution: Wire the DC power supply using the appropriate connectors at the wiring
end (see "Installation guide" on page 49). The proper wiring is ground to ground,
positive to positive, and negative to negative. Note that the ground wire should always
be connected first and disconnected last.
Caution: The system needs to be grounded during operation.
4.3 Environmental precautions
Danger: Do not work on the system or connect or disconnect cables during periods
of lightning activity.
4.4 Mechanical precautions
Caution: The blank face plates prevent vermin and dust to enter the system as well
as exposure to electromagnetic interference.

Chapter 5 System description March 2007 • ADX-7077 2055-01, Issue 1
5 SYSTEM DESCRIPTION
5.1 System overview and features

The System is an active digital cross connect. It reduces the amount of 2 Mb/s cabling in
the central office. It offers a distribution function which is fed with two STM-1 aggregate
signals via fiber or coax. The E1 payload channels can be fully flexible cross connected
towards any E1 port, for example terminated with an LSA-PLUS connector. The System
supports E1 unframed transmission, and is transparent for framed E1 signals. It also
supports the ability to non-intrusively monitor any connection at E1 level.
5.1.1 Key features

A short list of the key features supported by the System
Integrated web server with intuitive Graphical User Interface (GUI) with online help
Command logging
Flexible username and password provisioning
SNMP manageable for alarming
Sub network connection protection (SNCP)
Remote management
Loopback functions E1 incoming, E1 outgoing and STM-1 outgoing
Non service affecting software upgrading (hitless upgrading)
Full flexible VC12 cross connect (uni- and bidirectional)
Non intrusive monitoring of any connection in the System
Line protection (MSP)
Two STM-1 aggregate signal (optical or electrical)
Dual and single fiber interworking
Degraded signal reporting and provisionable thresholds
Synchronization, free running or selectable reference
E1 retiming outputs
8 slot positions for Interface Cards on the ADX100 and ADX201, 4 slot positions on
the ADX200
8 times 2.048 Mb/s according to G.703 interface per Interface Card
Simple and rapid installation
Database backup and restore
Smart defaults, use of prepared databases
5.2 Feature descriptions

This section will give a short description of the features supported by the System (see
"Provisioning" on page 85).

5.2.1 System software

The System software supports all System products. The System has two memory banks
containing the active and an inactive software version. The software is stored in non
volatile (flash) memory.
Remote and local software downloads are supported. Software upgrades are non service
affecting. They do not affect data communication settings.
5.2.2 System database

The System database contains all provisioned settings of the System except for the IP
and SNMP related settings. The System supports 8 databases of which one is active.
Databases are reusable between Systems of the same hardware version. For example
between one ADX100 and another ADX100.
At first start up the System has a default database in which no cross connects and other
transmission related settings are provisioned.
A database operation does not have impact on the data communication settings.
5.2.3 User administration

The System supports three user levels:
view: Members of the view group have read access only.
config: Members of the config group have access to normal transmission related
operations.
admin: Members of the admin group are responsible for maintenance activities like
software upgrading, database operations, user group administration and IP and
SNMP settings. The privileges of the members of the admin group also include the
privileges of the members of the config group.
5.2.4 Log file

The System maintains a log file (first in first out) to keep track of changes when system
settings are changed. Per event the log file include a time stamp, a user identification and
a descriptive text.
5.2.5 Real Time Clock

The System has an accurate (better than 4.6 ppm) Real Time Clock on board. The time
of this clock can bet set by the user and will survive a power outage of at least ten
minutes. The clock is used for adding a time stamp to reported alarms.
The internal System time is in UTC format. However during management via the GUI
alarm raise and clear times are represented in the local time zone of the browser.
5.2.6 Powering
The System has two telecom power connections for -48/-60 V DC that can be used as
redundant power feeds. The power is monitored. By default power fails are not reported.
Alternatively, the System can be powered using Power over Ethernet. Powering via PoE
is not monitored.

5.2.7 Test access port

Both the ADX200 and ADX201 have a dedicated test access output. This output provides
an E1 signal which can be measured with an analyzer. Every connection can be directed
to the test access output port to provide a non intrusive monitoring point.
5.2.8 Visual indicators

The System has three LED indicators. The green / active led indicates the System is
powered on. The yellow and red LEDs indicate the kind of current alarms. The LAN port
has a link status LED (green) and an activity LED (yellow) indication.
5.2.9 Inventory management

The inventory data of the pluggable items, SFPs or Interface Cards, and the main module
can be retrieved.
5.2.10 Tributary slots

The ADX100 and ADX201 have 8 tributary slot positions. The ADX200 has 4 slot
positions. These tributary slots contain the E1 ports on the access side of the System.
Each tributary slot contains 8 E1 ports.
5.2.11 Pluggable items

The System has two cages for SFPs for dual- and single fiber operation or for STM-1
electrical. The SFPs are hot pluggable and will be AUTO discovered by the System.
The Interface Cards are hot pluggable and are automatically detected by the System. The
Interface Cards contain 8 tributary ports.
5.2.12 Line Protection (MSP)

The System 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 MSP for both revertive and non-revertive operation is supported.
5.2.13 Synchronization
The System can be synchronized externally via each of the line ports and one of the E1
tributary ports. An internal (free running) clock with an accuracy of ± 4.6 ppm (or better)
has been integrated. When no suitable reference is available the System will use its
holdover clock.
5.2.14 E1 retiming
Every E1 port individually can be provisioned in retiming mode. In this mode the outgoing
E1 signal will be retimed with the System clock. This way the E1 signal can be used as
timing reference for a next System connected to the System.

5.2.15 Alarm reporting

The System supports the alarm reporting of current alarms. They will be reported on the
web browser and to an SNMP manager if provisioned. The alarms can also be visible on
the System LEDs. The System has a log for 500 cleared alarms. For every alarm the
severity and reporting state can be provisioned. Every port and termination point has a
monitoring mode to control the alarming.
Alarms can be downloaded in a tab separated file for off line processing using e.g. excel.
5.2.16 Cross connects

Cross connects can be fully flexible added, between line and tributary ports, between line
and line ports and between tributary and tributary ports. Both uni- and bidirectional cross
connects are supported. Bidirectional cross connects transmit traffic in two directions,
unidirectional cross connects transmit traffic in one direction.
5.2.17 Overhead functions

Full access is available to the SDH overhead. RS, MS, VC4 and VC12 overhead can be
viewed and provisioned. Like full trail trace identifier provisioning.
5.2.18 Web server

The System has an integrated web server, thus no additional management System is
needed. Only a web browser is needed. Via this web browser the System can be
managed.
5.2.19 SNMP
The System supports alarm reporting towards an SNMP manager. Five different SNMP
managers can be added. Both SNMPv1 and SNMPv2 are supported. User specific MIB
files are supported.
5.2.20 Single and Dual fiber SFPs

The System supports both single and dual fiber small form-factor pluggables, SFPs (see
"Short ordering list" on page 28). An SFP is the optical/electrical STM-1 line interface
unit.
5.2.21 Path protection

The System supports VC12 SNCP path protection.
5.2.22 Loopback
The Systems supports port loopback on the following levels):
E1 incoming
E1 outgoing
STM-1 outgoing
5.2.23 Remote management

The System supports remote management via the multiplex section embedded
communication channel (MS-DCC).

5.3 Description of the interfaces
5.3.1 ADX100 Interfaces

Figure 1. ADX100 interfaces - left-side view
Legend:
IFC is Interface card
1a. SFP, STM-1 interface, LP2
1b. SFP, STM-1 interface, LP1
2. Serial console port
3. Power over Ethernet, LAN management interface and LEDs
4. Power feeds, left is PFB, right is PFA

Figure 2. ADX200 E1 port numbering
Legend:
1. E1 Interfaces, 4 slots
2. Test port
3. Alarm indicators
4. Digital input
6. SFPs, STM-1 interfaces: left is LP1, right is LP2
8. Power feeds, upper is PFA, lower is PFB


Figure 3. ADX201 E1 port numbering
Legend:
1. E1 Interfaces, 8 slots
2. Test port
3. Alarm indicators
4. Digital input
6. SFPs, STM-1 interfaces: left is LP1, right is LP2
8. Power feeds, upper is PFA, lower is PFB
5.3.4 E1 interfaces
Each interface card has the following pins.
Table 1. E1 interfaces
Tx Rx
Interface card 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8

Chapter 6 Specifications March 2007 • ADX-7077 2055-01, Issue 1
6 SPECIFICATIONS
6.1 Hardware specifications

The available hardware platforms are:
PROFIL version with the ADX100 main module, in which 8 interface cards with 8 E1
ports can be inserted. The ADX100 should be installed on 95mm ADC PROFIL rod
mounting frames (see "Mounting and installation ADX100" on page 51).
1 RU height, 32*E1 & test access output, hardware prepared for digital inputs. The
ADX200 is suited for 19 inch rack mounting, 1 RU height and can have up to 32 E1
2Mb/s interfaces using 4 Interface Cards.
ADX201 is suited for 19 inch rack mounting, 2 RU height, and can have up to 64 E1
6.2 Dimensions and weight
6.2.1 ADX100
PROFIL version with the ADX100 main module, in which 8 interface cards with 8 E1 ports
can be inserted. The ADX100 should be installed on 95mm ADC PROFIL rod mounting
frames (see "Mounting and installation ADX100" on page 51).
Dimensions: 244 x 165 x 138.5 mm (HxWxD)
Weight: 2.3 kg (with interface cards)
1,7 kg (without interface cards)

Figure 4. Dimensions ADX100
6.2.2 ADX200
ADX200 is suited for 19 inch rack mounting, 1 RU height and can have up to 32 E1 2Mb/s
interfaces using 4 Interface Cards.
Dimensions: 44 x 450 x 171 mm (HxWxD)
Weight: 2 kg (with interface cards)

6.2.3 ADX201
ADX201 is suited for 19 inch rack mounting, 2 RU height, and can have up to 64 E1
Dimensions: 88 x 450 x 171 mm (HxWxD)
Weight: 3,1 kg (with interface cards)
6.3 Environmental
Operating temperature: +5 0C to + 40 0C acc. ETSI 300 019-2-3 class 3.1
Storage temperature: -25 0C to + 70 0C according to ETSI 300 019-2-1 class 1.2
Operating humidity: 5 to 95% according to ETSI 300 019-2-3 class 3,2
Storage humidity: 10 to 100% according to ETSI 300 019-2-1 class 1.2
Transport: according to ETSI 300-019-2-2 Class 2.3

6.4 Availability
MTBF ADX100 > 70 years, excluding Interface Cards and SFPs.
MTBF ADC101 > 450 years.
6.5 Power
Power -48/-60V DC or Power over Ethernet, via the signal wires
class 0 on the LAN interface , according to IEEE 802.3af.
Power consumption ADX100 6.5 Watt (Excluding Interface Cards)
ADC101 0.65 Watt
The maximum power dissipation 12.95 Watt

when IFCs and SFPs are inserted
6.6 Interfaces
STM-1 interface Depending on SFP in use.
E1 interface ADC101 2.048 Mb/s ± 50 ppm, HDB3 coded signal
according to ITU-T G.703-9 (120 Ohm)
LAN interface 10/100 Base T non sensing interface, no MDI/MDX AUTO
detection.
Local console port DB9 connector, signal levels according to ITU-T V.28 and
EIA232.
Test access output port (ADX200 and ADX201) via three banana receptacles (120 Ohm Siemens
banana-type) Providing E1 HDB-3 coded signal according to ITU-T G.703-9.
6.7 Synchronization
Timing according to ITU-T G.813, option 1. Free running accuracy ± 4,6 ppm.
Support of SSM algorithm according to ITU G.784.
E1 retiming
6.8 Mapping
E1 Interface at 2048 kbit/s ± 50 ppm, HDB3 coded and conforming to G.703-9 is
asynchronously mapped via VC-12 in TU-12, using the structure:
STM-1->AU4->VC4->TUG3–>TUG2->TU12->VC12->P12x->E12
Note in this mode the system does not assume any formating/framing of the 2048
kbit/Sec signal so also framed signals are supported.

6.9 Short ordering list

Description ADC Catalog #
Systems
ADX100 PROFILE version without Interface cards ADX-7077 2 001-00
ADX200 System 1RU height, without Interface cards ADX-7077 2 018-00
ADX200 System 2RU height, without Interface cards ADX-7077 2 020-00
Interface Cards
System Interface Card 8x 2 Mb/s 120 Ω
with 17-pole LSA-PLUS+ IDC EC connector ADX-7077 2 016-00
Documentation
System Customer Documentation CD R1.1 ADX-7077 2055-00
SFPs
SFP 155 Mb/s 1310nm 20 km, LC connector ADX-7077 2 022-00
SFP 155 Mb/s Bidirectional/Single Fiber, ADX-7077 2 027-00
TX 1310nm, RX 1550nm, 20 km, SC connector
TX 1550nm, RX 1310nm 40 km, SC connector
SFP 155 Mb/s STM-1e, COAX, DIN 1.0/2.3 connector ADX-7077 2 021-00
Cables
COAX, DIN 1.0/2.3 – DIN 1.0/2.3, 1m ADX-7077 2 033-00
COAX, DIN 1.0/2.3 – DIN 1.0/2.3, 2m ADX-7077 2 034-00
COAX, DIN 1.0/2.3 – DIN 1.0/2.3, 3m ADX-7077 2 035-00
COAX, DIN 1.0/2.3 – DIN 1.0/2.3, 4m ADX-7077 2 036-00
COAX, DIN 1.0/2.3 – DIN 1.0/2.3, 5m ADX-7077 2 037-00
COAX, DIN 1.0/2.3 – DIN 1.6/5.6, 1m ADX-7077 2 038-00
COAX, DIN 1.0/2.3 – DIN 1.6/5.6, 2m ADX-7077 2 039-00
COAX, DIN 1.0/2.3 – DIN 1.6/5.6, 3m ADX-7077 2 040-00
COAX, DIN 1.0/2.3 – DIN 1.6/5.6, 4m ADX-7077 2 041-00
COAX, DIN 1.0/2.3 – DIN 1.6/5.6, 5m ADX-7077 2 042-00
Power and Hub options
AC/DC Converter. AC Input: 120/230 VAC, 50Hz, ADX-7077 2 015-00
DC Output 36 – 72 VDC, Output 48 VDC, 0.5A, 24W
Miscellaneous
LSA-PLUS insertion tool S :6417 2 055-01
Blank face plate ADX-7077 2 010-01

Chapter 7 Management and remote management March 2007 • ADX-7077 2055-01, Issue 1

7 MANAGEMENT AND REMOTE MANAGEMENT

This section gives some functional background information for the System. Also some
provisioning (see page 85) aspects will already be mentioned, however not in detail.
The System supports the following management options:
Local management
Remote management using a LAN connection
Remote management using an Access Network
The System is designed to achieve an optimum between routing aspects, easy
configuration and maintenance. To achieve this, dynamic routing is used instead of static
routing.
7.1 Open shortest path first (OSPF)

Open shortest path first is an example of a link state routing protocol. Neighbour routers
tell each other their connections and status. In this way the routers create a map with the
network topology. Routes are quickly recalculated in case of topological changes. In
OSPF the cheapest path is calculated via cost metrics.
OSPF is a hierarchical interior gateway protocol (IGP). IGP stands for a set of routing
protocols in Autonomous Systems (AS). An AS is a collection of nodes/routers in the
same network with OSPF enabled, thus sharing the same network information.
OSPF supports multiple areas to limit the amount of routing related traffic. If
communication between other areas or other networks is required, there must be a way
out. An ASBR (see page 32) is used for this purpose.
To use OSPF you must enable it, at that point you must also specify a router ID for the
System. This router ID is also used for system/host addressing. The router ID must be
unique and cannot be equal to 0.0.0.0.
Since OSPF allows classless routing (defined in RFC 1817), discontinuous addressing is
allowed.
7.2 Supported areas

An OSPF network can be divided into areas. The System, however, supports only one
area. Since OSPF AS requires that all routers are connected to the backbone area (also
known as area 0 or area 0.0.0.0) this is the only area supported by the System.
The System supports up to 50 routers per AS. If more routers are connected all Systems
will give the SYScROUTE alarm (see page 144). No guarantee can be given that the
Systems function properly if this alarm is raised. As a user you must take appropriate
actions to avoid or to solve these problems.
OSPF protocol interworking is only supported for systems from the same family.
Authentication is realized by means of a simple password check.
7.3 Routers for OSPF
7.3.1 Area Border Router (ABR)

An area border router connects one or more OSPF areas to the backbone. Since the
System only supports this backbone network ABRs are not supported.

7.3.2 Autonomous System Border Router (ASBR)

Autonomous system border routers are routers on the border of an OSPF AS. They are
used to communicate with external networks. The system supports the ASBR
functionality.
The ASBR router can be used for remote management of the network.
To become an ASBR
A System becomes functionally an ASBR if the following conditions are met:
A local (LAN) default route is provisioned or a default route is received from a DHCP
server.
OSPF is enabled for the System.
OSPF is enabled for the System LAN interface.
Default route advertisement is enabled.
7.3.3 Designated router and the backup designated router

As the number of nodes in a LAN network grows the link state messages will increase to
the square. To be more specific: N nodes result in N*(N-1) link state messages. To
reduce the number and size of messages from increasing, the System automatically
assigns one of the routers as a designated router.
The designated router plays a critical role in the link state advertisement. As a fall back
possibility the System also addresses one of the routers as a backup designated router.
If the designated router (DR) fails, the back-up designated router (BDR) automatically
takes over the role.
Each router is assigned an 8-bit priority, indicating its ability to be selected as the DR or
BDR. All multi-access networks must have a DR. A BDR may also be selected. The
backup ensures there is no extended loss of routing capability if the DR fails.
The DR and BDR are selected using information contained in hello packets. The device
with the highest OSPF router priority on a segment becomes the DR for that segment.
The same process is repeated to select the BDR. In case of a tie, the router with the
highest RID is selected. A router declared the DR is ineligible to become the BDR. Once
elected, the DR and BDR proceed to establish adjacencies with all routers on the multi-
access segment.
7.3.4 Unnumbered network

Unnumbered network (point-to-point links between routers) is not supported in this
release. As a consequence the user will have to assign an IP address for a point-to-point
interface.
7.4 Address resolution protocol (ARP)

The address resolution protocol allows the host to find the physical address (MAC) of a
target host on the same physical network, given only the target's IP address.
7.5 The proxy address resolution protocol (PARP)

The proxy address resolution protocol (PARP) is a way to make a machine a logical part
of a physical network whilst it is not physically connected to that network. Proxy ARP can
only be enabled for the LAN ports.

Normally the system for which proxy ARP is enabled will only respond to ARP requests
for known network elements and OSPF enabled networks .
An advantage of proxy ARP above ASBR is that no static route provisioning is needed for
the gateway outside the AS. A disadvantage is that the subnet mask of the gateway
router outside the AS must be large enough to contain all systems and networks outside
the AS.
7.6 Link costs and signal rate

For the System no link layer protocol configuration for the embedded DCC links is
required. The System uses PPP (point-to-point protocol) over HDLC. It uses the MS-DCC
communication channel. The signal rate is 576 kbit/second.
The link costs are:
LAN: 10
DCC: 174
Local: 1
The System does not support load balancing (dividing traffic over equal-costs routes).
7.7 Line protection and OSPF

If a system can be managed via an MSP protected link, OSPF is best be enabled for both
working and protection port at both sides of the protected link.
7.8 Assigning IP addresses for system management

A System can have multiple IP addresses:
per line port a user provisioned IP (/32) interface address
a user provisioned LAN IP address, either default or obtained from DHCP
if OSPF is enabled a user provisioned IP (/32) host address, which is also used as a
Router ID
Note: We strongly recommend to use a convention to provision the IP addresses to

the Systems. Moreover within the total network the IP addresses must be unique.

The table shows the convention used in this manual.

Table 2. Convention used in this manual: IP address (A.B.C.D) in dotted decimal
notation
Type A B C D
NE LAN Interface 10 12 LAN#: 0 - 255 NE#: 1 - 99
LP1 (PPP0) interface 192 168 1 NE#: 1 - 99
LP2 (PPP1) interface 192 128 2 NE#: 1 - 99
System or host address / router ID 10 15 0 NE#: 1 - 99
Directly connected Host / Manager LAN 10 12 LAN#: 0 - 255 Host#: 100 - 254
interface
Host or manager LAN interface in access 80 80 LAN#: 0 - 255 Host#: 100 - 254
network
Access Router LAN interface 80 80 LAN#: 0 - 255 Router#: 80-99
Systems can be accessed by IP addresses. The figure shows an example. If OSPF is
disabled the LAN IP address should be used.
Figure 7. System access problems when using LAN IP address
10.12.0.100 / 24 Host#1
default route
10.12.0.1
(10.12.0.x / 24) 192.168.1.1 / 32 192.168.2.4 / 32
ospf ospf
10.12.0.1 / 24 [10]
ospf
NE#1 [174] NE#4
(10.15.0.1) (10.15.0.4)
Autonomous System
192.168.2.1 / 32
192.168.1.4 / 32
ospf
[174] [174] ospf
SDH 'ring'
192.168.1.2 / 32
ospf 192.168.2.3 / 32
NE#2 NE#3 ospf
(10.15.0.2) [174] (10.15.0.3)
10.12.1.2 / 24 10.12.1.3 / 24
ospf ospf
[10] [10]
(10.12.1.x / 24)
[link cost]
(Router ID)
Note: : The notation (10.15.0.1) or more general (A.B.C.D) in the network element
(NE#x)indicates the router ID and also that OSPF is enabled at System level.
If there are no errors (so NE#2 and NE#3 are connected via the LAN) in the OSPF
enabled network the OSPF protocol will accces NE#3 via the shortest path. This path is:
Host1 <-> NE#1 <-> NE#2 <-> NE#3, costs: 174 + 10 = 184
Now a LAN error occurs, as shown in the figure. In this case no rerouting takes place
because the 10.12.1.x/24 network is still available. Therefore NE#3 cannot be reached
anymore.
A better solution is achieved if the host uses the System router ID, being 10.15.0.3, to
reach NE#3. In this case NE#3 remains accessible via the rerouting path:
Host1 Ù NE#1 Ù NE#4 Ù NE#3, costs: 174 + 174 +1 = 349

7.9 Routing examples

This chapter describes some management network examples. These examples explain
the functioning of the basic routing options.
7.9.1 Local management, host directly connected to System LAN and no routing protocol
This section describes:
System and host in the same subnet (on page 35)
System and host connected to an access network (on page 35)
7.9.1.1 System and host in the same subnet
Figure 8. Example of a System and host in the same subnet.
In order to communicate with each other the system and host must be part of the same
subnet.
Note: We advise an equal size of the subnet for all systems connected to the LAN.
If Proxy ARP is used it is mandatory to use one subnet mask for all connected elements.
The number of hosts and systems that can be connected depends on the size of the
subnet mask. It can be calculated with:
2 (32-X) - 1
With X is the size of the subnet mask and -1 because the broadcast address
(255.255.255.255) must be excluded.
7.9.1.2 System and host connected to an access network
Figure 9. Example of an access network

In this case local management traffic is realized by communication over the local System
LAN interface. If the host wants to access the System that is not in the same subnet it will
use the default route entry. This is the ethernet address for router RT#1. RT#1 will deliver
the message to the next element. If the access network is properly connected System
(NE#1) can be accesed by the host.
The system will use the default route of RT#2 to reponse to the host.
Note: For hosts with multiple LAN ports you can sometimes specify a default route
per LAN port. This depends on the operating system, and behavior is undefined.

7.10 Remote management examples
7.10.1 Terminal application and host connected to LAN

Figure 10. Example of remote management, host directly connected to a System LAN
The point-to-point protocol (PPP) is used to establish the connection between NE#1 and
NE#2. Now the interface address of NE#1 is known by NE#2 and the other way round.
This is something taken care of by the PPP protocol.
So NE#1 can be reached via:
LP1: 192.168.1.1
LP2: 198.168.2.1
And NE#2 can be reached via:
LP1: 192.168.1.2
LP2: 198.168.2.2
NE#2 is an ASBR (this can be set with the GUI). If OSPF is enabled on System level and
on line port level the OSPF protocol provides the routing table of NE#1 with 10.15.0.2 and
NE#2 with 10.15.0.1. Also the default route, 10.12.0.100, will be advertised.
Note that for the communication between Host#1 and NE#1 it is needed that NE#1 knows
how to access the 10.12.0.x / 24 network. Without OSPF this information is not distributed
and communication fails.
Table 3. Routing table NE#1
Destination Mask Gateway Flags Metric Interface
192.168.1.1 32 192.168.1.2 UGH 348 ppp0
192.168.1.2 32 0.0.0.0 UH 0 ppp0
192.168.2.1 32 192.168.1.2 UGH 348 ppp0
10.15.0.2 32 192.168.1.2 UGH 175 ppp0
192.168.2.2 32 0.0.0.0 UH 0 ppp1
10.127.127.0 30 0.0.0.0 U 0 eth0
10.12.0.0 24 192.168.1.2 UG 184 ppp0
0.0.0.0 0 192.168.1.2 UG 10 ppp0

Table 4. Routing table NE#2

Destination Mask Gateway Flags Metric Interface
192.168.1.1 32 0.0.0.0 UH 0 ppp0
192.168.1.2 32 192.168.1.1 UGH 348 ppp0
192.168.2.1 32 0.0.0.0 UH 0 ppp1
10.15.0.1 32 192.168.1.1 UGH 175 ppp0
192.168.2.2 32 192.168.1.1 UGH 348 ppp0
10.12.0.0 24 0.0.0.0 U 0 eth0
0.0.0.0 0 10.12.0.100 UG 10 eth0
Remarks for routing table

Flags:
U: route is up, G: route is to a gateway, H: route is to a host, if this flag is not set, it is
a route to a network
From this table it becomes clear that the host can reach NE#1 via NE#2. The following
takes place when you login with the address 10.15.0.1:
1. The Host cannot find this address on the LAN, so it will use the default gateway:
10.12.0.2.
2. NE#2 receives the message and checks the address 10.15.0.1 in its routing table,
and use: 192.168.1.2.
3. NE#1 responses to the host via 192.168.1.2.
4. Next 10.12.0.x/24 is used, because this is advertised by OSPF.
Note: For the local LAN of NE#1 it is needed to use a LAN IP address that doesn't
fit in the LAN network of Host#1. For example, 10.127.127.1/30. It is advised to disable
DHCP for NE#1. Otherwise IP address conflicts may occur. If 10.127.127.1/30 is used,
then the IP subnet addresses are: 10.127.127.0 10.127.27.1, 10.127.127.2 and
10.127.127.3. The first one is often not allowed and the last one is a broadcast. So both
cannot be used as a host address.
Caution: If you use a LAN address for NE#1 that is in the same subnet as the
default route of the host, you cannot reach NE#1 by its router ID anymore. In this case
NE#1 will notice that a shorter route exists if a request from NE#2 comes in, namely the
local LAN of NE#1.

Remarks:
Router Table evaluation
The default route (destination is 0.0.0.0) is always the last entry evaluated in the
table.
Local addresses
The system software does not use the routing table if a local destination address is
involved. This means that the costs and actual route can be ignored for a local PPP
interface.
Local PPP interface costs
The System routing table shows that the path costs to the local PPP interface has
twice the expected value. This is because this route is regarded as advertised by the
neighbour and the cost to reach the neighbour are also included. However they play
no role in the costs for the shortest path.
Local PPP interface addresses
For the local PPP interfaces the neighbour PPP interface address shows up in the
routing table.
PPP interface regarded as a host address
According to the System routing table a PPP interface is regarded as a host address
which is not the case. A /32 address is interpreted as a host address.
0.0.0.0 destination address
This entry is the default gateway. For Host#1 the default route is 10.12.0.2 (LAN
interface of NE#2). For NE#2 (ASBR) the default route is the LAN interface of Host#1
(10.12.0.100). For NE#1 (remotely managed via a protected point-to-point
connection) the default route is 192.168.1.2 (LP1) via which also the 10.12.0.0 / 24
network is routed.
NE#1 <-> NE#2 path
The route from NE#2 to NE#1 and the route from NE#1 to NE#2 are in this case both
routed via the same port (LP1) which is a coincidence. Also note that the path cost is
the sum of the PPP link (174) and the local loop Router ID address (1).

7.10.2 Multiple hosts and mix applications

Figure 11. Example of application mix and multiple host
192.168.1.1 / 32 192.168.1.2 / 32 10.12.0.2 / 24 10.12.0.100 / 24
ospf ospf ospf default route:
10.12.0.2
10.127.127.1 / 30
(no dhcp)
NE#1
(10.15.0.1) NE#2
SDH terminal (10.15.0.2)
Host#1
10.12.0.3 / 24
192.168.2.1 / 32 192.168.2.2 / 32 default route:
ospf ospf 10.12.0.5
Host#2 192.168.1.4 / 32 192.168.1.5 / 32 NE#3

ospf ospf
10.12.1.100 / 24
default route
10.12.1.4 Autonomous System
10.12.0.5 / 24
10.12.1.4 / 24 ospf
ospf
NE#5
NE#4 (10.15.0.5) 192.168.2.5 / 32
(10.15.04)
ospf
192.168.2.6 / 32
ospf
192.168.2.4 / 32
ospf SDH ring
192.168.1.6 / 32
192.168.2.7 / 32 ospf 10.127.127.1 / 30
NE#7 NE#6
ospf (10.15.0.7) (10.15.0.6) (no dhcp)
192.168.1.7 / 32
ospf
10.127.127.1 / 30
(no dhcp)
Both hosts are able to access any of the systems. All Systems, except NE#3, are OSPF
enabled. So the topology of the network is advertised from neighbour to neighbour.
The designated router can either be NE#2 or NE#5. Normally NE#5 becomes the
designated router because it has an router ID greater than the router ID of NE#2.
Example 1, Host#2 wants to access NE#3

This is achieved by the fact that NE#5 has OSPF enabled on the LAN interface. This will
be advertised to, amongst others, NE#4. So if Host#2 wants to access NE#3 via
10.12.0.3 the following takes place:
1. The message is sent to the default route, being 10.12.1.4, this is NE#4.
2. NE#4, in its turn will access the next hop. This is NE#5.
3. NE#5 will put the message forward to its LAN network: 10.12.0.5/24.
4. NE#3 will pick it up from the LAN network.
5. The reply from NE#3 to Host#2 is guaranteed because:
1. NE#4 and NE#5 both have OSPF enabled.
2. NE#5 receives the message from NE#3 via the default route of NE#3,
10.12.0.5/24.
3. Via the routing table of NE#5 the message will be forwarded to NE#4, because
NE#4 reported the local network 10.12.1.x/24.
4. NE#4 forwards the message to the local area network.

Example 2, Host#1 wants to access a System in the SDH ring

Host#1 sends the message to NE#2 because its default route is to NE#2. Because OSPF
is enabled for all Systems, NE#2 forwards the message to NE#5. And so on. Also NE#2
recognizes that a shorter path exists. Therefor it will send a so called redirect message to
Host#1. Now Host#1 may change its routing table.
7.10.3 Example with ASBR

Figure 12. Example of configuration with Autonomous system border routing
To make NE#6 an ASBR it must have a default route to the LAN network and
advertisement must be enabled. In this way all systems in the access network can be
reached, but only if RT#1 is provisioned for it. This can be done on per individual address
base or by assigning one entry: 10.15.0.0/28 -> 80.80.2.6. This covers the range
10.15.0.0 ... 10.15.0.14.
The access network does not get any status information of the autonomous system. This
implies that only internal failures inside the AS can be addressed/resolved. To make it
more reliable you might consider to involve NE#7 and RT#2 also in the routing scheme.
However the network becomes more complex.

Note that routing protocol inter-working between RT#1 and NE#6 cannot take place
because of the OSPF password authentication.
Caution: Host#1 can use or misuse the routing network to access remote nodes,
like SNMP#1. The routing is not designed for this through traffic. It should be avoided.
7.10.4 Example with proxy ARP

Figure 13. Example of Proxy ARP configuration
Instead of using ASBR and a static routing table for RT#2 to get to the access network
(see "Example with ASBR" on page 41), it is also possible to use proxy ARP on an
ASBR. The applied subnet mask /24 (preferred multiple of 8), gives access to a relative
large subnet. You may want to use /28 which is sufficient in the depicted case.
Note that routing protocol inter-working between RT#1 and NE#7 cannot take place
because of the OSPF password authentication.
A proxy ARP enabled system will not respond to an ARP request if the routing path
involves the network interface via which the ARP request was received. Only OSPF
enabled systems can be managed via the access network. The managed nodes and at
least the LAN port of NE#7 and RT#1 are part of one subnet.

It is not allowed to have multiple access routers reporting the same or overlapping
subnet. This may result in unmanageable Systems (see "Avoiding management problems
with proxy ARP" on page 43).
Avoiding management problems with proxy ARP

The figure shows a configuration in which management problems may occur if the
connection between NE#3 and NE#4 is OSPF enabled. Because an ARP request for
NE#4 by Host#1 can be answered both NE#2 and NE#1.
Figure 14. Proxy ARP example
10.15.0.100 / 24
10.15.0.12 / 24
10.15.0.11 / 24 ospf
ospf Host#1 proxy arp
proxy arp
NE#1 NE#2
(10.15.0.1) (10.15.0.2)
OSPF
NE#5 NE#3
(10.15.0.5) No OSPF (10.15.0.3)
NE#4
(10.15.0.4)
The table shows who is answering on a proxy ARP request if more nodes have their LAN
settings provisioned as proxy ARP.
Table 5. Proxy ARP example
Host#1 ARP request for is answered by
10.15.0.1 NE#1 NE#1
10.15.0.2 NE#2 NE#2
10.15.0.3 NE#3 NE#2
10.15.0.4 NE#4 NE#1
10.15.0.5 NE#5 NE#1
Note: If the connection between NE#3 and NE#4 was OSPF enabled an NE#4
ARP request would also be answered by NE#2. In this way NE#4 might become
unmanageable.
Note: If resilience is not needed, only one System per LAN network should have
the Proxy ARP feature enabled, this keeps the management network as simple as
possible.

Chapter 8 Subnetwork connection protection (SNCP) March 2007 • ADX-7077 2055-01, Issue 1

8 SUBNETWORK CONNECTION PROTECTION (SNCP)
8.1 Introduction
The system supports subnetwork connection protection. With the aid of SNCP the
System protects a low order virtual container (sub) network connection. At the head-end
the virtual container is permanently bridged into two tributary units (TU), at the tail-end the
selection is made.
When a defect occurs, or as a result of a user request, the traffic is rerouted to the non-
defective TU. Both resources together form a so called 1+1 protection group (PG).
Only non-revertive switching is supported. This means that the TU where the traffic was
rerouted to, remains active when the error disappears. Manual, forced and clear
commands are supported.
For reliable monitoring of SNCP protected cross-connects the system supports multiple
protected cross-connects which share the same worker and protection leg. Sharing of
only one leg is not supported and rejected by the System.
The system supports SNC/N subnetwork protection (refer to ITU-T G.841). In this
protection scheme the following criteria are used for determination of the active traffic
selected path:
A server signal failure on the subnetwork connection.
A trace identifier mismatch (TIM), per SNCP connection a user can exclude TIMs
from the switching conditions. LPdTIM results in a consequent action that takes 3 TTI
frames to clear, the TTI frame during which the switch occurs is also lost, together 4
TTI frames = 32 ms.
An unequipped virtual container (UNEQ).
A degraded signal (DEG) condition occurs, user can set the threshold for the DEG
criteria (see "Degraded Threshold provisioning and handling" on page 105).
Before an SNCP protection switch is executed the Hold Off Time must have been
elapsed. This time is adjustable between 0 and 10 seconds in steps of 1/10 of a second.
This time can be set per SNCP protection group. If multiple switch requests are
simultaneously active, their hold-off timers run independently. The switching is completed
within 50 ms after fault detection plus the hold off time.
Worker (from) and protection(prot) legs are linked to different Line Ports. The protected
port always links to a tributary port. The settings for the Non Intrusive Monitors (NIM) are
retrieved from the VC12 termination point (VC12TTP) associated with the protected (to-
leg) port. This applies to:
Accepted TTI provisioning
TIM setting
Degraded Threshold setting
monitoring mode
For reliable monitoring of SNCP protected cross-connects the system supports multiple
protected cross-connects which share the same worker and protection leg. Sharing of
only one leg is not supported and rejected by the System. Note that at most one of the
cross connects can be bidirectional.
Note: NIM ports shared settings are retrieved from the last provisioned VC12
trail trace termination point. The initial NIM settings are copied from the
first associated VC12 trail trace termination point with an SNCP protection group.

8.2 Non intrusive monitoring (NIM) of line ports
Note: Changing the termination settings for a protected VC12 termination point will
also be applied to the worker and protection NIM settings.
This may harm your configuration.
See also provisioning (see "SNCP Cross connects uni- and bidirectional" on page 114).
8.3 Provisioning aspects

An SNCP protected cross-connect can be created in two ways:
Adding a protection leg to an unprotected cross-connect.
This operation is non-service effecting.
Create from scratch.
An SNCP cross-connect can be removed by either:
Convert an SNCP protected cross-connect into a unprotected cross-connect. This
can be done by removing either the worker or protection leg. Which makes a hitless
conversion possible even if the near end and the far end do not select the same
path.
Remove the SNCP protected cross-connect.
Provisioning notes:
Swapping of worker (from-leg) and protection (prot-leg) requires two user operations.
First the from-leg is removed and next the prot-leg is assigned with the previous
worker leg.
In order to change the leg of an SNCP protected cross-connect one needs to
temporarily convert the cross-connect into an unprotected one by removing the
worker or protection leg. After this a different protection leg can be added to the
unprotected cross-connect resulting in the changed SNCP protected cross-connect.
Caution: Also the test ports can be provisioned as an ordinary port, in fact it is an
ordinary port for which only the outgoing signal is made available. By changing the
settings of the test port, the above mentioned settings are used for the cross connect in
stead of the settings of the originally applied tributary port.

Chapter 9 Port loopback functionality March 2007 • ADX-7077 2055-01, Issue 1
9 PORT LOOPBACK FUNCTIONALITY

The Systems supports port loopback on the following levels):
E1 incoming
E1 outgoing
STM-1 outgoing
Figure 15. Port loopback functions
Incoming Outgoing
VC12 unequipped AU4 MS-AIS
Test
IFC 1 LP 1
VC12
E1 AIS
IFC n LP 2
Outgoing
E1 AIS
A warning is displayed if you create a loopback request. This because unexpected side
effects may occur, for example in the synchronization domain.
Note: The simultaneous support of an incoming and an outgoing loopback for the
same port is not supported and is rejected by the system.
Note: The combination port loopback and using the port as timing reference is not
allowed. The system prevents that this can be provisioned.
E1 incoming loopback
The System accepts at most one incoming E1 port loopback. If you want to add a new E1
port loopback you first have to locate the existing one (see page 100) and then remove it.

Chapter 9 Port loopback functionality March 2007 • ADX-7077 2055-01, Issue 1
The implementation of an E1 port loopback results in inserting and forwarding VC12

unequipped. The consequent action of forwarding VC12 Unequipped for an incoming E1
loopback will finally result at the far end in generating E1 AIS (Unequipped is not defined
for E1).
Note: To avoid local alarm messages the locally generated VC12 Alarms are
suppressed if you implement an E1 incoming port loopback.
E1 outgoing loopback
If you create an E1 outgoing port loopback an E1 AIS alarm is forwarded in the signal
leaving the system.
Note: There are no restrictions regarding the number of outgoing port loopbacks.
STM-1 outgoing loopback

If you create an STM-1 outgoing port loopback an MS-AIS alarm is forwarded in the
signal leaving the system. On the outgoing loopback no alarm is raised but a signal
containing an E1-AIS and MS-AIS is sent out.

Chapter 10 Installation guide March 2007 • ADX-7077 2055-01, Issue 1
10 INSTALLATION GUIDE
This section describes the installation procedures for:
ADX100 for LSA-PLUS PROFIL rod mounting.
ADX200 and ADX201 for 19 ” rack mounting.
The following installation procedures are described in this section:
Installation ADX100.
Installation ADX100 (without interface cards).
Exchange ADX100 Main Module.
Installation ADX200 and ADX201.
10.1 General notices
Caution: Work ESD safe!

Take appropriate ESD precautions when unpacking, installing or decommissioning the
product. Use a wrist wrap when handling SFP modules and interface cards.
Caution: The equipment may only be installed and operated by qualified

employees.
Note: After unpacking, the equipment shall be inspected for damage.
10.2 Tools
The following tools are needed:
LSA-PLUS insertion tool
Screw driver Phillips head EN60 900 (PZ1 and PZ2)
10.3 Accessories
Figure 16. External AC/DC Power supply 48V

Figure 17. SFPs (various types)
Figure 18. Interface Card, can be ordered separately
Figure 19. Power supply connectors for -48/-60V DC inputs (included in box)
Figure 20. Wire guide for ADX200/ADX201 (included in box)

Figure 21. Blank Face plate, can be ordered separately
Figure 22. Four bolts, two left two right
10.4 Mounting and installation ADX100
10.4.1 ADX100 for LSA-PLUS PROFIL rod mounting

This section describes how to mount an ADX100 on a rod in an ETSI rack or 19" rack.
Figure 23. ADX100 rod mounting

10.4.1.1 ADX100 with 2 Mb/s E1 connections
An installed ADX100. Next sections provide the installation instructions.

Figure 24. ADX100 with E1 connections
10.4.1.2 Rod and rack specifications
LSA-PLUS PROFIL rod mounting (Profile rod diameter: 12mm, pitch between profile
rods: 95mm).
Fixed or Movable PROFIL Frame installation.
Caution: The profile rods bust must be properly grounded!
Figure 25. ETSI rack mounting
125,00 250,00 125,00

55,00 110,00 55,00
42,50 85,00 42,50
ADDF ADDF
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
12,00
95,00 95,00
FixedSchwenkbare
Profile FrameInstallation,
Installation,z.B.
e.g.19"-Einbau
ETSI (max. 500
)
Figure 26. 19 inch rack mounting

ca . c a.
30 ° 30 °
122,50 205,00 122,50
52,50 65,00 52,50
40,00 40,00 40,00
ADDF ADDF
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8 1 1 2 3 4 5 6 7 8
12,00
95,00 95,00
MovableSchwenkbare
Profile Frame Installation,
Installation, z.B.
e.g. 19"-Einbau
19 rack (max. 450 mm)

10.4.1.3 Mounting to profile rods

1. Open the lock bar.
2. Mount on PROFIL rod.
3. Fastening the screws, to fix the system on the PROFIL rods.

10.4.1.4 Connecting 2 Mb/s (E1) Interfaces

1. Insert jumper wire from left side into cable guide.
2. Push jumper wire into LSA contact.
3. Fixate jumper wire with LSA-PLUS Insertion Tool.
10.4.1.5 Connecting interfaces
To connect the interface use:

Cable core diameter: 1.5 mm² max.
Externally fused with 1A.
To install:
1. Connect Power Supply, Telecom power OR Power over Ethernet.

2. Insert SFP transceivers and connect fiber or COAX STM-1 connectors to SFPs.
10.4.1.6 Remove and Insert label holders ADX100

1. Loosen label holder.
2. Remove it.
3. Insert it.

4. Click.
10.5 ADX100 without Interface Cards

ADX100 for LSA-PLUS PROFIL rod mounting without Interface Cards.
Figure 27. ADX100 without Interface Cards
See also:
Rod and rack specifications (on page 52)
Mounting to profile rods (on page 53)
Interfaces (see "Connecting 2 Mb/s (E1) Interfaces" on page 53) and connection of
interfaces (see "Connecting interfaces" on page 54)
Label Holder attachment (see "Remove and Insert label holders ADX100" on page
55)
10.5.1 Interface Card installation

1. Insert Interface Card.

2. Slide in Interface Card and push gently.
3. Fasten Interface Card screws.
Figure 28. ADX100 equipped with Interface Cards (Max 8)
10.5.1.1 Blank Face plate installation

1. Install Blank Faceplate in all openings and

2. finally fasten all screws.
10.5.1.2 Exchange ADX100 Main Module
Caution: This option is only for exceptional cases, handle very carefully!

Figure 29. ADX100 Main Module
1. Disconnect interfaces from equipment:

power supply connector
SFP
LAN

To disconnect interface (see "Connecting interfaces" on page 54):

1. Disconnect fiber or COAX STM-1 connectors from SFPs and remove SFP
transceivers.
2. Disconnect DC power supply.
To remove Interface Card:

1. Loosen screws (2x) on the left and right side of each interface card.
2. Pull Interface Card with pull mechanism (rear end of LSA-PLUS Insertion Tool)
gently about 1 cm to the front.
10.5.1.3 Removing the frame

1. Loosen screws (4x).

2. Gently pull frame to the front and turn to the right side (in case possible, temporary
fixate provisional to the profile bar).
10.5.1.4 Install ADX100 Main Module

Preparations to install:
1. Loosen screws (2x) Support ADX100 Main Module from below with one hand.
2. Release lock lever and remove ADX100 from the Profile Rod.
Main Module Installation:

1. Open lock bar.
2. Fixate to the Profile rod by fastening screws (2x).
10.5.1.5 Mount Frame

1. Position Frame on the ADX100 Main Module and fasten screws (4x).
Caution: Do NOT fasten screws with excessive force.

10.5.1.6 Install Interface Cards

1. Installation of interface cards (see page 56).
10.5.1.7 Connect Power, SFPs and fibers or coax

1. Connect Power supply, SFPs and fibers or coax (see "Connecting interfaces" on
page 54).
10.6 Mounting instructions ADX200 and ADX201
10.6.1 ADX200
Figure 30. ADX200 with Interface Cards
10.6.2 Mounting material 200 (included in box)

4x Cage nut M6 for 2 mm material thickness, St/Zn (ADC 6821 3 023-00)
4x Lock washer J6,4, St/Zn blue (ADC 590998)
4x Flat head screw ISO 7045-M6X16, St/Zn (ADC 591392)
1x Wire guide

10.6.3 ADX201
Figure 31. ADX201 with Interface Cards
10.6.4 Mounting material ADX201 (included in box)

6x Cage nut M6 for 2 mm material thickness, St/Zn (ADC 6821 3 023-00)
6x Lock washer J6,4, St/Zn blue (ADC 590998)
6x Flat head screw ISO 7045-M6X16, St/Zn (ADC 591392)
2x Wire guide (see page 49)
10.6.5 Mounting the ADX200/ADX201
Note: Brackets can be mounted on 2 depths.
1. Undo screws.
2. Position mounting brackets on required depth.

3. Mount System into frame.

Figure 32. Mounting the ADX200
Figure 33. Mounting the ADX201
10.6.5.1 Use of wiring brackets
Add wiring brackets on left side if required.

Figure 34. One bracket on 1U System

Figure 35. Two brackets on 2U System
10.6.5.2 Wire routing
An example for both Systems is shown below.

Figure 36. Wire Routing ADX200
Figure 37. Wire Routing ADX201

10.6.5.3 Connecting interfaces
Inserting SFPs

1. Inserting SFPs.
Connecting power
Specifications (see "Cables and pinning" on page 68):
Connect Power Supply, Telecom power OR Power over Ethernet.
Cable core diameter: 1.5 mm² max.
Externally fused with 1A
Lock connector with screws in connector.
1. Connecting Power.
Test connector
A special 3 pin Siemens banana connector or single banana plugs can be used.
1. Connecting Test Access Output.
Inserting interface cards


1. Insert card.
2. Fasten screws.
Removing interface cards

1. Loosen screws.
2. Remove card.

10.7 Cables and pinning
10.7.1 DC power cable

Figure 38. DC Power Cable
Red Strain relief

+ Phoenix
-
Ground
Blue
Green/yellow
mounted
L (according to installation)
10.7.1.1 LAN - Power over Ethernet cable
Figure 39. Power over Ethernet Wiring

White-Orange
TxOutP 1 1a
TxOutN 2 1b Orange
White-Green
RxInP 3 2a
RxInN 6 2b
Green
Blue
NC 4 3a
NC 5 3b
White-Blue
White-Brown
NC 7 4a
NC 8 4b
Brown
Using the spare wires (4,5,7,8) is optional. Length must be within 100 meters, cable type
must be CAT5 or better.
10.7.1.2 Serial / Console cable
Figure 40. Local Console Port Wiring

Note: Length up to 20 m. Do not connect an open, not terminated, long cable.
The COM port is a DB-9 receptacle style connector providing an RS-232 DCE interface
for local communications. A DB-9 straight through cable is used for data communications.
When this port is connected to a terminal it is called a console port.
This port does not support a modem. It is used for local access to the unit and is used to
set the initial communication parameters. Shielded cable is recommended and the
maximum cable length is 20 m. A 1:1 cable is required to connect this port to the DTE
com port of a PC.
Figure 41. 9-Pin D-Sub connector

Chapter 11 Set up of the System March 2007 • ADX-7077 2055-01, Issue 1

11 SET UP OF THE SYSTEM

This section will provide the information needed during the first set up of the System. An
overview is given of the physical connectors of the System. The settings of the IP
parameters for accessing the System will be described. An overview of the web browser
set up and behavior is outlined.
11.1 Connectors
11.1.1 LAN connector

The System 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 direct connection. Additionally the LAN port supports Power
over Ethernet according to IEEE802.3af (alternative a and b are supported)
11.1.2 Local Management console port

A serial 9 pole sub–d connector according to RS232C is available for changing local
management control settings. The connection settings are: 38400 b/s, no parity, 8 data
bits, one start, stop bit. The System does not require hardware control wires to be
connected.
11.1.3 Telecom power feed

The System has two telecom power feeds with a nominal voltage of -48/-60 V DC. The
connector type is a Phoenix mini-Combicon connector. The power fed to these
connectors is distributed simultaneously to the System. When having both power feeds
supplied, failing of one of them does not interrupt the System.
11.1.4 SFP modules

The System has two cages for SFP modules. An inserted SFP will be taken into service
without user provisioning, assuming no SFP was inserted before. The SFPs are hot
pluggable (see "Pluggable items" on page 88).
11.1.5 Interface Cards

The ADX100 and ADX201 have 8 slot positions for Interface Cards, called the tributary
slots. The ADX200 has 4 slot positions. The ADC101 Interface Card is supported.
Inserting an Interface Card will directly set this card to operational. The Interface Cards
are hot pluggable (see "Pluggable items" on page 88). Each interface card has 8 ports
which are called the tributary ports.
11.1.6 Test access output

The ADX200 and ADX201 have a dedicated E1 test access output. The test access
output is implemented by using three banana receptacles at the front side: two for signal
and one for ground. The connector is the commonly used Siemens type 3 pole banana.
The E1 signal is according to G.703-9 in 120 Ohm. For the ADX201 this port is also
logically routed to port 8 on tributary slot 8.

11.2 Powering
Connect power to the System (see "Installation guide" on page 49). During the start up
the activity (green) led will flash with 2 Hz, connecting with a web browser to the System
is not possible. After 3 minutes the System is operational and the green led stops
flashing. A connection via the web browser can be made. The first minute alarm
information is not available.
Monitoring the presence of power is enabled when setting the alarm for power failure to
reported (default it is not reported). Each power has its own detector, SYScPFA and
SYScPFB. When this alarm is raised power might not be present at the input or the
corresponding fuse is broken. Check this by measuring the input voltage. Fuses are not
field replaceable.
Note: A swap of -/+ will result in a power failure alarm, although the System is
powered.
Additionally the System supports Power over Ethernet. This power feed has no
monitoring facility for a loss of power.
Caution: Do not simultaneously provide Telecom powering and Power over

Ethernet.
11.3 IP address management

The System can be managed via the 10/100BASE-T Ethernet LAN interface. To get
access to the management interface the System must have a valid (known) IP address, in
the subnet range of the LAN it is connected to.
The first time a connection needs to be set-up with a web browser to the System this can
be done with a direct PC to System LAN connection. The System has an integrated web
server. The HiThere utility can be used to discover the System equipment on present on
the LAN (see page 71), no router must be present between the System and PC.
The default address of the System 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 is equal to 255.0.0.0 (RFC950).
11.3.1 IP management without DHCP server

When no DHCP server is used a new default address needs to be provisioned for the
System. After System recovery the System will perform a limited number of attempts to
obtain an IP address/mask from a DHCP server. When not successful no further requests
will be made.
A DHCP can be user controlled.
There are three options to change the IP settings.
Via the web browser
Using the IP2Box utility.
Via the local management console port
All options have an equivalent result.

Figure 42. DHCP state transistions
11.3.1.1 Provisioning via local console port
Connect a PC to the local console port. Use an utility like ‘hyperterm’ or ‘putty’. When
connected to the System a prompt appears. Press enter type the password, adm123.
Now you have access to the functionality. To change the IP settings you have to type:
dbs dr set_ip.The format is:
dbs dr set_ip <ipAddress> <subNetMask> <defaultGateway> <DHCP>, with:
<ipAddress> = <xxx.xxx.xxx.xxx>
<subNetMask> = <xx>
<defaultGateway> = <xxx.xxx.xxx.xxx>
<DHCP> = <0 or 1>
Check accurately the filled in address before entering this.
The System parameters will directly apply.
Note: The provisioned default gateway should be reachable, otherwise 0.0.0.0 will
be applied.
11.3.1.2 Provisioning IP address with DHCP client
After a System recovery the System DHCP client will perform a number of attempts to
obtain an IP address/mask from a DHCP server (if DHCP is enabled). If this is successful
this IP address/mask will become operational. If this is not successful the System will fall
back to its default IP settings, but keeps trying to obtain a DHCP assigned address.

When the default IP settings are changed after the DHCP assignment these will become
operational. Changing of the default IP settings is described (see page 73) and is similar.
11.3.1.3 HiThere utility
The HiThere utility can be installed on a Windows PC. This utility is used to discover the
Systems on the subnet the PC is connected to. Each System is installed with a HiThere
server program. The System responds with its MAC address, IP address, sub net mask,
IP default gateway and Linux host name.
From the HiThere utility direct access can be obtained to the GUI, by selecting the
requested System with the right mouse button.
Figure 43. HiThere Utility
Note: In case multiple Systems are using the default IP address, they can be
distinguished by their MAC address.
11.3.2 LAN port provisioning via WEB browser
Note: Only members of the admin group can change the LAN settings.
MENU: SYSTEM-LAN SETTINGS

Figure 44. LAN port settings
IP address
The factory programmed IP address is 10.127.127.1.
Note: After the change has been made connection with the web browser could be
lost and has to be set up with the new address.
Mask
The default value is 8, values between 8 and 30 can be provisioned. Provision the
applicable value for your environment.
Gateway
The factory programmed value is 0.0.0.0. You can provision the default gateway address.
This change will directly become effective if DHCP is disabled.
MAC Address
The MAC address of the System. The MAC address of the Systems always starts with
the Organization Unique Identifier (OUI) 00 0f 25. This is a read-only value fixed for every
System. The MAC address is also printed on the label present on the System.
Note: In case of a DHCP assigned IP address, the IP address field does not reflect
this assigned address.
DHCP
If you enable this option the Sytem will immedately try to obtain the LAN IP details (IP
address, mask, gateway) from a DHCP server. If this fails the Default values will be
restored. These values are also used if you disable this option (again).
Note: The current gateway can be obtained via OSPF, in that case an IP interface
address of the ASBR System is shown or the IP address of the external access
router/gateway. This gateway address is only be applied if it can be reached directly
without involvement of an ASBR System.
11.3.3 LAN provisioning via Ip2Box

IP2Box needs to be installed on a Windows PC. The IP2Box utility uses the MAC address
to connect to the System.

Figure 45. Ip2Box Utility
Use the MAC address to connect to the System. Next you fill in the requested IP address,
Subnet mask and Default Gateway. Additionally a Host Name needs to be entered, next
select Assign to apply the settings.
Validation: Check on correctness of entered values. Check if the IP address entered
already exists on the local subnetwork. The user is warned about this.
Ping: Ability to ping to an IP address of a System.
Note: The DHCP settings are not changed.

Chapter 12 GUI Settings and system authorization March 2007 • ADX-7077 2055-01, Issue 1
12 GUI SETTINGS AND SYSTEM AUTHORIZATION
12.1 Web browser and navigation

The System has an integrated web server. Supported browsers are Mozilla Firefox and
Internet Explorer 6.0.
12.2 GUI settings

A short list of settings required for the web browser:
Enable Java scripting, if disabled System cannot be managed.
The html data is not encrypted, the url will start with http://.
The GUI language is English.
Allow pop ups, as warnings and error messages will be shown in a pop up window.
The screen size is 1024 (horizontal) * 768 (vertical).
12.3 GUI features

Update after edit
After a provisioning change has been made and Apply has been selected, the window
will reappear with the changes been made.
Clickable items via System layout

Some items shown on the System overview (see "ADX201 GUI System overview" on
page 82) are directly clickable.
Field colors convention

For the field colors following convention is used. Editable fields are clearly marked as
yellow and non-editable fields are non colored. When the value of a field is changed
during a provisioning action the color will change into blue. By clicking the Apply button
the changes are applied and the field color is changed back into yellow. You can use
Refresh to cancel the the provisioning action.
Simultaneous sessions
The System supports five different sessions simultaneously. When a sixth session is
started the first session will be closed automatically.
Refresh button
Every window has a refresh button, to get the current state of the settings and statuses of
the window.
Smart selection
The System tries to predict the next selection. This is applicable for those windows in
which a list is shown. This is the case when adding cross connects, editing ports or
termination points. When there is no next logical selection no pre-selection will be made,
but always a list of valid termination points is presented.
Access to related items

In several menus the quick navigation option is available to go direct to related items. Like
in the SFP details you can go directly to the associated line port.

Restart of browser after System recovery

After a System recovery the browser will restart and come up with the welcome screen.
12.4 User groups, login and rights
Note: Login is case sensitive.
The System supports three user groups. Per group at least 10 users can be supported.
User names are unique per system. Each user can change the password after entering
the existing password first. The user should enter the new password twice before the new
password is applied. By default a number of login names already are available.
The user groups and their default login(s) are:
view group
Members of the view group have read access only. On the GUI, buttons which could
normally trigger a change of system setting are made invisible.
The view group has one default login name:
1. Login name: view
Password: empty
config group
Members of the config group have access to normal transmission related operations.
The config group has two default login names.
1. Login name 1: user
Password: adc123
2. Login name 2: config
Password: adc123
admin group
Members of the admin group are responsible for maintenance activities like software
upgrading, database operations, user group administration and IP and SNMP
settings.
Only users in the admin group can create or remove users. They can also provide
initial passwords for new users. The password of already existing users can be
changed by an admin user without knowledge about the existing password.
There must always be at least one user in the admin group. FFor this reason the user
admin cannot be removed. The admin group has one default login name:
1. Login name: admin
Password: adm123
Note: Also an expert/root user exists via which all the default password settings
can be restored to their factory defaults. Contact ADC for this procedure.
Note: The login screen and System layout differs per platform.
Note: The login screen contains the user name and password.
Caution: It is recommended to change the passwords of admin and config users

after installation.

12.4.1 ADX100 Login screen

The welcome screen contains the user identification and password.
Figure 46. ADX100 Login Screen

12.4.2 ADX100 GUI System Overview

Both the System layout, which represents the hardware, and the menu access is different
for the three platforms. But the menu structure and the submenus are completely similar.
The ADX100 System overview represents the hardware with the 8 tributary slots shown
and the 8 E1 ports, separated in transmit (TX) and receive (RX) side. This overview is
independent of pluggable items being present or not.
Figure 47. ADX100 GUI System Overview
Directly accessible via the overview, by clicking the object are:

LAN POE: LAN settings (see "Set up of the System" on page 69)
LP1/2: SFP details
ADX100 icon: System details
Alarm list: By clicking ALM led area
One of the E1 ports: Details of the E1 port provisioning, in this case there’s no
difference when accessing it via RX or TX.
Tributary slots: By clicking on TS1, TS2, etc.
[!]: 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.
For future releases:
SERIAL: Access to the serial console port
B1/B2: The power connectors
Please refer to the detailed descriptions of these menus (see "Provisioning" on page 85).


Figure 48. ADX200 Welcome Screen
12.4.4 ADX200 GUI System overview

The ADX200 System overview represents the System with the four tributary slots.
LP1/2: SFP details
TEST: The test access output port can be accessed via this button (see "Test
access output" on page 108). Selecting this port gives cross connect information on
this port. The user is able to see which cross connect is made towards the test
access output port. Additionally the existing cross connect can be edited, the type
uni-or bidirectional will be retained. When no cross connect exists, a unidirectional
cross connect can be added. The port and VC12 related setting of the test access
output are accessible via TS8.8.
DIG: Indicates the hardware prepared digital inputs


Figure 50. ADX201 Welcome Screen
12.4.6 ADX201 GUI System overview

The ADX201 System overview represents the System with the eight tributary slots.
LP1/2: SFP details
TEST: The test access output port can be accessed via this button (see "Test
access output" on page 108). Selecting this port gives cross connect information on
this port. The user is able to see which cross connect is made towards the test
access output port. Additionally the existing cross connect can be edited, the type
uni-or bidirectional will be retained. When no cross connect exists, a unidirectional
cross connect can be added. The port and VC12 related setting of the test access
output are accessible via TS8.8.


DIG: Indicates the hardware prepared digital inputs
12.5 Log file for System settings

The System maintains a log file (first in first out) to keep track of changes when system
settings are changed. Per event the log file include a time stamp, a user identification and
a descriptive text. The sort order depends on the provisioning moment. The size of the file
is about 100 kB. Contact ADC for details.
Only users of the admin group can access logfiles. They can download (Backup) them
from the System in WordPad format, as well as Delete them from the system.
Note: Deleting the logfile results in creating a new logfile which shows that the
logfile was deleted.
Note: The time stamp is in UTC time.

12.6 Menu structure

The menu structure is identical for all System platforms. Only the representation differs:
the ADX100 is represented vertically, the ADX200 and ADX201 horizontally.
The details of the menus are described (see "Provisioning" on page 85) except for the
LAN settings which is described elsewhere (see page 72).
Note: Depending on the login rights (see page 76) some menus are not shown.
Note: The ADX100 does not have a separate test port.
Note: Use <Shift-Click> to open a new window or tab.
System menu
SYSTEM | DETAILS
SYSTEM | IP SETTINGS | INTERFACES
SYSTEM | IP SETTINGS | ROUTES
SYSTEM | IP SETTINGS | OSPF | GENERAL
SYSTEM | IP SETTINGS | OSPF | INTERFACES
SYSTEM | IP SETTINGS | OSPF | SYSTEM
SYSTEM | TIME
SYSTEM | SNMP SETTINGS
SYSTEM | PLUGGABLE ITEMS
Maintenance menu
MAINTENANCE | SOFTWARE | DETAILS
MAINTENANCE | SOFTWARE | INSTALL
MAINTENANCE | DATABASE
MAINTENANCE | LOG
MAINTENANCE | USERS
MAINTENANCE | LOGOUT
Alarms menu
ALARMS | CURRENT
ALARMS | HISTORY
ALARMS | PROFILE/SEVERTITIES
ALARMS | GUI SETTINGS

XConnects menu
XCONNECTS | LIST
XCONNECTS | ADD BIDIRECTIONAL | LP -> TP
XCONNECTS | ADD BIDIRECTIONAL | TP -> LP
XCONNECTS | ADD BIDIRECTIONAL | LP -> LP
XCONNECTS | ADD BIDIRECTIONAL | TP -> TP
XCONNECTS | ADD UNIDIRECTIONAL | LP -> TP
XCONNECTS | ADD UNIDIRECTIONAL | TP -> LP
XCONNECTS | ADD UNIDIRECTIONAL | LP -> LP
XCONNECTS | ADD UNIDIRECTIONAL | TP -> TP
XCONNECTS | ADD SNCP BIDIR | LP1 -> TP <- LP2
XCONNECTS | ADD SNCP BIDIR | LP2 -> TP <- LP1
XCONNECTS | ADD SNCP UNIDIR | LP1 -> TP < -LP2
XCONNECTS | ADD SNCP UNIDIR | LP2 -> TP < -LP1
Transimission menu
TRANSIMISSION | PORTS | LINE PORTS
TRANSIMISSION | PORTS | TRIB PORTS
TRANSIMISSION | TERMINATION POINTS | RS/MS
TRANSIMISSION | TERMINATION POINTS | VC4
TRANSIMISSION | TERMINATION POINTS | VC12
TRANSIMISSION | DEGRADED TRESHOLDS
Timing menu
TIMING | SYSTEM TIMING
TIMING | TIMING SOURCES
MSP menu
MSP | DETAILS
MSP | CREATE
Help menu
Help is available for version 1.3.1 and upwards.
HELP

Chapter 13 Provisioning March 2007 • ADX-7077 2055-01, Issue 1

13 PROVISIONING
13.1 Introduction
Provisioning of the System is done via the Web browser. When a login as admin is
required this is explicitly mentioned.
13.1.1 ADX100, ADX200 and ADX201 differences

All screens and menus shown are similar for all three hardware platforms. The System
layout part of the screen is not shown in this section. When differences exist they will be
mentioned explicitly. Differences to be aware of are:
The ADX200 has only 4 slot positions, thus 32 E1 ports, 32 VC12 termination points.
The ADX100 does not have a specific test access output like the ADX200 and
ADX201.
Difference in the welcome screen and System layout screen per System.
13.2 Transmission terms and definitions

Short overview of transmission terms and definitions used throughout this Section:
Downstream
This is the direction coming from the STM-1 aggregate side into the System, 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 System. When a failure in the System is detected this
is reported as an alarm. This action will insert e.g., an AIS signal in the downstream
direction or RDI in the upstream direction in case of a bidirectional cross connect.
Ingress
The incoming side of a port.
Egress
The outgoing side of a port.

13.3 System time

The System has an accurate Real time clock on board that provides the System time.
This System time is used to add a time stamp to reported alarms on the web browser and
SNMP traps/notifications. When no time is set the default Linux time is taken at startup:
January 1, 1970. The SYScTIME alarm is reported. The accuracy of the real time clock is
± 4.6 ppm or better.
The system software synchronizes the real-time clock to the network timing (see
"Synchronization" on page 122). The real time clock has an inaccuracy of less then 3
minuter per year.
MENU: SYSTEM | TIME
Figure 52. System Time
System Time
This field shows the current time of the System (see page 143). A refresh is needed to
get the current value.
Host date and time (local or UTC)
This field shows the date and time of the PC connected to the System. This field is
continuously updated.
Changing the time can be done in two ways:
Sync: Using this button to place the current Host date and time to the System time.
Filling in the values in the System time field. Be aware to use the correct format and
values. Then press Edit.

13.4 Pluggable items

Pluggable items are the Interface Cards and SFPs. The pluggable items can be inserted
and removed while the system is powered (hot pluggable).
Caution: Pluggable items, SFPs and Interface Cards, need to be handled

according to ESD guidelines.
MENU: SYSTEM | PLUGGABLE ITEMS

Figure 53. Pluggable Items Overview
13.4.1 Interface Card

The System supports the ADC101 Interface Card. The System will automatically discover
an inserted Interface Card. The default tributary slot state is AUTO. When the IFC has a
supported item code (ADC101-ADC120) the state will change from AUTO to ASSIGNED
and the IFC will be operational, this takes less than one minute.
Selecting the desired TS (Tributary Slot) will show the details.
Figure 54. Interface Card Details
Current State
The current state can be AUTO or ASSIGNED.
When the inserted IFC has an item code that is not supported, the state will remain AUTO
and IFCcWUI (IFC Wrong Unit Inserted) is reported. When the inserted IFC is defective
an IFCcEQF (IFC Equipment Failure) is reported. The IFC needs to be replaced by a
correct one.
When no IFC is present in ASSIGNED mode and IFCcUNP is reported (IFC Unit Not
Present), this will be due to a removal. In AUTO mode no reporting of a Unit not Present
is done.

Item code
The item code identifies the type of Interface Card. Currently the ADC101 is available for
the Systems. The ADC101 has 8 ports E1 (G.703) 120 Ohm ports with ADC LSA-PLUS
IDC edge connectors. The System is prepared for future versions of Interface Cards, as
item code ADC101 up to ADC120 is supported in this release. Future Interface Cards
might have different impedance or connector types.
Catalog number
The catalog number (see page 28) of the interface card without connector.
Note: Interface cards can only be ordered including a connector. A short ordering
list is included in this manual (see page 28).
Serial Number
The serial number of the selected IFC. This number is factory assigned per product and is
useful for tracking hardware.
Last Accepted
The item code of the IFC which was present and accepted before the current one. This
information is of use when in future 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 will
be of use when more item codes are supported. When before executing this operation
traffic is running, this action is not service affecting.
13.4.2 IFC replacement.

When an Interface Card is replaced with the same item code, the System will accept the
IFC and the state remains ASSIGNED. When an IFC is replaced with another IFC having
a different but supported itemcode an IFCcREPL alarm will be reported and the user has
the option to accept this IFC. The alarm will notify the user of the change in item code. In
the last accepted field the user can view the previous item code and he can decide if the
change is requested. When selecting Accept Pluggable Item the inserted IFC will
become 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. But in
upstream direction 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.

13.4.3 Small Form Pluggable

The System has two SFP positions related to the line ports.
Figure 55. SFP Details
When selecting an SFP the details will be shown.

Current state
State can be ASSIGNED, 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 SFP replacement
and acceptance for more details.
Qualifier
The module qualifier identifies the type of SFP. This is according to ITU-T G.957. All
module qualifiers will be accepted by the System. The module qualifier for optical SFPs
has the format I/S/L-X.Y.
In which I/S/L identifies if it is a 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.
Example
S1.1 is a short haul 1310 nm STM-1 SFP.
Electrical SFPs will have STM1-e as module qualifier.
If the module qualifier can’t be determined it will get the Unknown qualifier. This can be
due to vendors not following the inventory coding. These SFPs will be accepted.
Wavelength
The transmitted wavelength of the SFP.
Link Type
Type of optical fiber to be used (9 um single mode) or coaxial for an electrical SFP.
Link max length
The allowed link distance.

Vendor fields
Identifying the vendor specifics.
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 which was accepted previously. This is important when the SFP
has been replaced.
13.4.4 SFP replacement and acceptance

When the SFP state is AUTO and an SFP is inserted this will be accepted irrespective of
the module qualifier. When the SFP state is ASSIGNED and an SFP is inserted, then in
fact it is a replacement. In this case the inserted SFP module qualifier will be compared
with the last accepted. When they differ an SFPcWUI will be raised and the SFP is not
accepted. Transmission will be shut down. This alarm notifies the operator on a change of
SFP type. When this change is acceptable the SFP state has to be changed to AUTO.
This action will accept the SFP and the state will change to ASSIGNED. When a timing
reference is assigned from this port the timing reference has to be unassigned before
changing the state to AUTO.
13.4.5 Single Fiber SFPs

The System supports single fiber or bidirectional SFPs. It is important to have matching
SFPs at each end of the fiber connection. The wave length used for transmitting should
be different (see page 92).

13.5 System recovery

Some actions related to the System software or database may result in a System
recovery. A System recovery will take about 3 minutes. A System recovery is not service
affecting. Communication with the web browser(s) and SNMP manager(s) will be lost.
Two minutes after the recovery the user can login again. During the recovery the green
(active) led will blink. When the led has stopped blinking the alarms are evaluated. After
the System has come up a cold restart trap will be sent to the provisioned SNMP
manager(s).
In case of a system upgrade the status of the System is indicated as soaked. (see
"System software" on page 93)
When at any time a database failure is detected the System will invoke automatically a
System recovery.
Figure 56. System initialization
13.6 System software

The System supports one load line for all three products. The System software for
release 1.3 with Item code ADW130 supports the ADX100, ADX200 and ADX201.
The System has two software memory banks.
MENU: MAINTENANCE | SYSTEM | DETAILS
The detailed content of both banks is shown.
Figure 57. ISD Details
Bank 1 contains the active ISD and Bank 2 the inactive.

Status of Bank 1 and Bank 2

Image Status
Bank 1 Bank 2 Meaning

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
last image inactive bank). If this error occurs the image is valid but a transition
transition error occurred. The action can be repeated and become successful.
active empty Normal situation for a System leaving the factory. Bank2 is empty
and the software of Bank 1 is running
Item Code
Identifies the software release:
ADW100 release 1.0
ADW110 release 1.1
ADW120 release 1.2
ADW130 release 1.3
ADW130B release 1.3.1
Software Version
Identifying software release, sub release, maintenance release, load drop version.
Build time
Build time and date.
13.6.1 Select inactive ISD

This option is only available for the ‘admin’ user
When selecting the inactive ISD the System will switch over to the inactive ISD. The
System will recover and connection to the Web browser is lost. This action will be
performed when a software upgrade is required. Check before activating that the inactive
ISD state is inactive and the ISD specific details as Item code and software version do
correspond with the ISD requested. During recovery the System database will be
converted when necessary to the new software version.
Note: If you select the 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
System to fall back to the previous ISD when the switch was not successful e.g., due to a
conflict in the database. In this way service will never be affected. When this happens the
System will come 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
System is manageable. The System being manageable is indicated by the green led
stopping to blink.

1. System recovery takes about 3 minutes, during this period the activity LED will blink
with 2 Hz. frequency.
2. After the green LED has stopped blinking you can login to the System, alarm
evaluation will has been finished.
3. 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, e.g. due to a power cycle, while the sanity timer is running, the
System selects the previous active software. The database changes which were
made during the sanity period are lost.
Check after the System is up again whether the requested ISD is active. (Bank 1 always
contains the active ISD) When a switch over 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.
Caution: After a software upgrade has been performed do not obtain any changes
in the System configuration within one minute after you could login or the green led has
stopped blinking.
To upload a new ISD to the inactive bank select: MAINTENANCE | SOFTWARE | INSTALL
Figure 58. Software Upload
By selecting Browse..., a file browser is started at the PC. From this browser select the
ISD. The ISD will be uploaded to the System. This will take about 5 minutes, the size of
an ISD is about 6.5 Mb.
Note: The text in the Browse... button depends on your local language settings.
A progress indicator will be displayed.

Figure 59. Loading the software
Caution: Do not select any other menu during the software upload, this will stop
the upload.
When the upload is finished the details of the uploaded ISD are shown.

Figure 60. Software Upload Completed
Note: The value for the Software version field in the screen dump in this manual
does not show the most recent version of the software.
13.7 System database

A new System has one database, the default database addf.db. This default database is
included in the System software and will never be lost. Database handling can only be
executed by ‘admin’ users. The System supports 8 databases of which one is active.
All provisioning items are part of the database except for the IP, OSPF and SNMP
settings. The SNMP and IP settings will be retained when restoring, uploading, selecting
or deleting databases. The default database has the following properties:
Line and tributary ports in AUTO mode
No VC12 cross connections present
Fixed VC4 cross connect from Line1 <-> VC#1 and Line2 <-> VC4#2
VC4 termination monitoring mode: Monitored
No System name and location
The default database also contains the default alarm settings (see page 141).
Select MAINTENANCE | DATABASE to display an overview of all databases.
Figure 61. Database Listing
The database can be identified by the name, if active this is shown by (active) as postfix.

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, included in the active ISD.
Conversion is only supported from a lower to a higher database version. If for example a
database version #1 is selected while the current running software is supporting database
version #3 a conversion form #1 -> #3 is needed. The System first converts #1 -> #2
followed by a conversion from #2 -> #3. The original (#1) and intermediate (#2)
database(s) are all removed by the system. For fail safe operation the user might decide
to make a backup of this database by downloading it to a host system.
Note: That the converted database gets the hardware identification of the hardware
on which the conversion takes place.
This operation takes a few seconds and is also dependent on the amount of conversions
needed. The request might be rejected if:
1. 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.
2. The database file is not existing because it has been removed by a concurrent
database operation.
3. The database does not match the system hardware.
4. Communication with the system is lost due to a concurrent operation which result is a
recovery, e.g. active database selection, and software upgrading.
5. Software sanity is in progress, database selection is not permitted.
The type indicating the hardware it supports:
Profile-v1, ADH101, ADX100
19inch1u-v1, ADH102, ADX200
19inch2u-v1, ADH103, ADX201
Note: Databases are not compatible between the Systems. For example a
database for ADX200 is not compatible with a database for ADX201. A database for a
specific hardware version will only operate on that hardware version. The type of the
database identifies the platform it suites. When selecting an invalid type this will be
rejected.
13.7.1 Database maintenance
Note: If a database operation is selected a warning will be displayed to indicate the

impact.

Figure 62. Database maintenance
Restore
Using this option, a database can be uploaded to the System. By selecting Browse you
can pick the desired database via the PC connected to the System. A database should
have extension .db. The upload takes less than 1 minute, (depending on your network
connection). The typical database size is about 100 Kbytes. When finished the uploaded
database will be shown in the database list.
Note: The text in the Browse... button depends on your local language settings.
Backup
With the backup option a copy (download) of the selected database can be made towards
the connected PC.
1. Click on the file to backup.
2. Click Backup.
3. Follow the instructions.
Rename
The selected database can be renamed.
Note: Rename without entering the .db extension.
Delete
Deleting the database will remove the database from the System. When deleting the
active database the System will recover and come up with the default database retaining
the database name, service will be lost. The SNMP, OSPF and IP settings will not be lost.
Deleting the default database is possible but it still is present in the System software,
when necessary this database will be created again and started up.
Set as active
This will activate the selected database. The System will recover and connection to the
Web browser is lost. When the selected database has different settings as the current
one transmission will be affected. When the selected database has identical settings
transmission will not be affected.

Copy Active
This option makes a copy of the active database to a database name to be specified.
This copy will be stored on the System.
Figure 63. Database Copy Active
Smart defaults
A database of one System can be used at another System of the same hardware platform
type. Specific databases can be prepared on one System which can be uploaded to
Systems in the field. In this way a System can be operational in a short time. Next to that
databases for specific scenario’s, like emergency cases, can be stored at the System
required. When an emergency occurs this database can be selected.
13.8 Ports and termination points
13.8.1 Ports
The System has two STM-1 line ports and 8 E1 tributary ports per interface card. A
common concept in provisioning of the line and tributary ports is the monitoring mode.
The monitoring mode of a port controls the alarm reporting. The default value is AUTO.
The options for the monitoring mode are:
MONITORED: In this mode alarm reporting is on.
AUTO: In this mode no alarms are reported.
NOT MONITORED: In this mode no alarms are reported.
The AUTO mode has an AUTO mode timer whose default value is 10 minutes. A port in
AUTO mode will go to monitored when until expiry of the specified AUTO mode timer
continuously a valid signal is present. The timer will start when a valid signal is detected.
The AUTO mode timer can be provisioned between 0 and 30 minutes in steps of 1
minute.
13.8.2 Line ports

The Line port selection can be made with, MENU: TRANSMISSION | PORTS | LINE PORTS
Figure 64. Line Port Selection

When selecting Edit of a selected line port you can set the details for this port.
Figure 65. Line Port Details
The Port AutoMode Time, Port Monitor Mode, and Out Loopback can be provisioned.
Force Do Not Use
By default this value is disabled. When enabling this option the SSM out value will be set
to Do Not Use (SSM value 1111). The far end system connected to this line port will not
select this signal for synchronization (on page 122), when QL enabled is selected.
13.8.3 Tributary Ports

The E1 tributary ports support unframed E1 transmission. In fact they are transparent for
any type of 2 Mb/s signal according to ITU-T G.703, e.g. framed with or without CAS
(channel associated signalling).
Note: In the selection list of tributary ports only those are shown of ASSIGNED
Interface Cards.
The tributary port selection can be made in Menu: TrANSMISSION | PORTS | TRIB PORTS.
Figure 66. Tributary Port Selection
To show the details of the selected tributary port press Edit.

Figure 67. Tributary Port Details

The Port AutoMode Time, Port Monitor Mode as well as the User Label can be
provisioned. The user label will be displayed during: E1 port provisioning, the provisioning
of a cross connect involving a tributary port, and E1/VC12 termination point related alarm.
Note: Changing the label while an alarm exists results in clearing the alarm,
immediately followed by raising the alarm with the new label.
The timing related items do concern the retiming feature (see "Retiming E1 ports" on
page 129).
Default value Timing Mode is: Self Timed, in this mode the retiming (see "Retiming E1
ports" on page 129) option is disabled.
In the screen Tributary Port Selection in this section the Loopback is set to In Loopback
(see "Port loopback functionality" on page 47).
13.8.4 Termination Points

At a termination point the virtual container is terminated (sink) and constructed (source).
The following levels of termination points can be accessed:
RS and MS Regenerator section (see "RS and MS section" on page 101)
VC4 (see page 102)
VC12 (see page 104)
RS and MS section
The RS and MS termination point selection can be made with TRANSMISSION | TERMINATION
POINTS | RS/MS.
Figure 68. RS/MS Selection
The RS and MS termination points are direct related to the physical line ports. The
monitoring mode therefore cannot be provisioned and is slaved to the related line port
mode. The monitoring mode of the RS/MS TTPs controls the alarming on these points.
Use Edit to show the details of the selected RS/MS termination point.

Figure 69. RS/MS Details
RS Termination point
For the RS termination point the J0 byte Trail Trace identifier can be provisioned (see
"Trail Trace Identifier provisioning and handling" on page 106).
Specific for the J0 byte is in the Non specific byte mode the J0 value is 01.
MS Termination point
For the MS termination point the degraded threshold value set can be selected. This
defines the threshold at which an MS degraded alarm will be reported,
Two sets are available. These sets can be provisioned separately (see "Degraded
Threshold provisioning and handling" on page 105).
VC4 termination points

The System has two VC4 termination points which are directly related to the line ports, of
which one is selected independently per port. Line port 1 has a fixed VC4 cross connect
to VC4 #1 and Line port 2 towards VC4 #2.
The default monitoring mode of the VC4 termination points is monitored. The VC4 TTP
monitoring mode controls the alarming (see "Resolving alarms and problems guide" on
page 139) on this point, except for the VC4cPLM and VC4cLOM which will be reported
irrespective of the monitoring mode.
In the menu TRANSMISSION | TERMINATION POINTS | VC4 the selection can be made.
Figure 70. VC4 Termination Point Selection

Note: When MSP protection is enabled the VC4 termination point related to the
protection line port does not exist (see "Transmission protection MSP" on page 117).
Use Edit to get the details of the selected termination point.

Figure 71. VC4 Termination Point Details
Trail Trace
The default mode is Non specific byte. More details are available (see "Trail Trace
Identifier provisioning and handling" on page 106).
Trail Signal Label
The trail signal label (C2 byte) identifies the type of traffic in the VC4 container. The
transmitted signal label is fixed TUG structured (02). The accepted (received) TSL must
be TUG structured (02) or equipped (01), other values indicate a type of traffic not
supported by the System. A VC4cPLM (Payload Mismatch) alarm will be raised when the
accepted TSL has a different value then 01 or 02. As consequent action AIS is inserted
downstream. The VC4cPLM alarm is not under control of the monitoring flag. In case the
TSL has a value 0, indicating unequipped, a VC4cUNEQ alarm is raised. This might be
due to no VC4 cross connect present at the far end.
Accepted status
Indicates the response to the accepted trail signal label.
Normal: The trail signal is correct
Unequipped: Trail signal label is 0, unequipped. The cross-path is broken (see
"Resolving alarms and problems guide" on page 139).
AIS: The VC4 container contains AIS, and the C2 byte contains all ones.
Directionality
Indicates if the termination point is part of a uni- or bidirectional cross connect. The VC4
is a fixed bidirectional cross connect.
Monitoring Mode
The default mode is monitored. When no alarming is required the mode can be set to Not
Monitored.
Degraded threshold
The selection of the degraded threshold value defines at which threshold a VC4
degraded alarm is reported. The choice can be made for threshold set 1 or 2 (see
"Degraded Threshold provisioning and handling" on page 105).

VC12 termination point

The System has 64 VC12 termination points. For the ADX201 this is 32 + 1 test access
output. Irrespective of the presence of Interface Cards the VC12 terminations points are
available.
The list of VC12 termination points can be retrieved via TRANSMISSION | TERMINATION POINTS |
VC12
Figure 72. VC12 Termination Point Selection
The default monitoring mode of a VC12 termination point is Not Monitored.
Note: When applying a bidirectional cross connect, or unidirectional in which the

VC12 TTP is the To point, towards a VC12 termination point the monitoring mode will
be set to Monitored.
Use Edit to get the details of the VC12 termination point.

Figure 73. VC12 Termination Point Details
Trail Trace
The default mode is repeating byte. More details are available (see "Trail Trace Identifier
provisioning and handling" on page 106).

Trail signal label

The trail signal label (V5 byte) identifies the type of traffic in the VC12 container. The
transmitted signal label is fixed asynchronous (02). The accepted (received) TSL must be
asynchronous (02) or equipped (01), other values indicate a type of traffic not supported
by the System. A VC12cPLM (Payload Mismatch) alarm will be raised when the accepted
TSL has a different value then 01 or 02. As consequent action AIS is inserted
downstream. The VC12cPLM alarm is not under control of the monitoring flag. In case the
TSL has a value 0, indicating unequipped, a VC12cUNEQ alarm is raised. This might be
due to no VC12 cross connect present at the far end or intermediate system.
Accepted status
Indicates the response to the accepted trail signal label
Normal: The trail signal is correct
Unequipped: Trail signal label is 0, unequipped. The cross-path is broken (see
"Resolving alarms and problems guide" on page 139).
AIS: The VC12 container contains AIS, and the V5 byte contains all ones
Monitoring Mode
The default value is Not Monitored. The mode will be set automatically to Monitored when
a bidirectional cross connect is applied towards this VC12 TTP, or when a unidirectional
cross connect is made with the VC12 TTP as to point. When deleting the cross connect
the monitoring mode remains as it was. When no alarm reporting is required or after the
cross-connect is removed, the monitoring mode can be set to not monitored.
Degraded threshold
A choice can be made for threshold set 1 or 2 (see "Degraded Threshold provisioning
and handling" on page 105). The specific values for these sets can be provisioned with
MENU: TRANSMISSION | DEGRADED THRESHOLDS.
13.8.5 Degraded Threshold provisioning and handling

For every termination point two sets of degraded thresholds can be provisioned. The
value of the provisioned degraded threshold defines the number of background block
errors in the related path or section overhead which lead to a Degraded Signal alarm,
when the number is exceeded. When using MSP protection, an MS degraded can cause
a protection switch.
The default value of the degraded value corresponds with the severely error second
declaration in the Performance Monitoring domain.
The duration value defines the number of consecutive seconds in which the errors of the
degraded signal exceed the threshold value. This value can be provisioned from 2 to 10
seconds, the default is 7 seconds.
The degraded thresholds can be provisioned for MS, VC4 and VC12 level.
Table 6. Degraded Threshold Levels
Signal level Default value Relative value of the default Range
STM-1 (MS) 28800 15% 1..192000
VC4 2400 30% 1..8000
VC12 600 30% 1..2000
The degraded threshold can be defined as two global sets per level, and per specific
termination point the threshold set 1 or 2 can be chosen.
Select TRANSMISSION | DEGRADED THRESHOLDS to get the global set for all levels.

Figure 74. Degraded Thresholds Overview
Two sets of degraded thresholds exist. On every individual termination point of the
corresponding level you can make a selection out of the two sets.
13.8.6 Trail Trace Identifier provisioning and handling

The trail trace identifier (TTI) enables an end to end check on the transmission path. The
source will send a transmitted trail trace identifier which is received at the destination
(accepted trail trace identifier). When enabling TIM (Trace Identifier Mismatch) detection
the accepted trail trace identifier will be compared with the expected value. When a
mismatch is detected a TIM alarm is reported. As consequent action of the TIM, AIS is
sent downstream and RDI is inserted in the upstream direction. VC12 RDI is sent
upstream only in case of a VC12 bidirectional cross connect.
Transmitted TTI: The TTI inserted in the section/path overhead.
Expected TTI: The expected TTI.
Accepted TTI: The received TTI.
Trail Trace Identifier modes

Non Specific Byte
In this mode a constant value will be sent in the TTI. For the System this is 01 for the
RS level and 00 for VC4 and VC12. In this mode no transmitted and accepted value
can be provisioned. For J0 (RS) a trail trace dentifier mismatch will be detected when
the accepted TTI does have a different value than 01. For J1 and J2 a trail trace
identifier mismatch will be detected when no non specific byte is received. When TIM
detection is enabled a TIM alarm for this termination point is reported and as
consequent action AIS is sent downstream and RDI upstream.
String
In this mode a 15 byte string can be provisioned for the transmitted and expected
value. On the transmitted byte a CRC check byte is added internally in the System.
The values to be entered must be according to the ITU-T T.50 character set. When
TIM detection is enabled and the accepted (received) trail trace identifier differs from
the expected one, a TIM alarm is reported and as consequent action AIS is sent
downstream and RDI upstream.

13.8.7 Provisioning trail trace identifiers

Figure 75. Trail Trace Provisioning
When selecting the requested termination point to be changed, the trail trace identifiers
can be provisioned. This behavior is similar for all levels VC12, VC4 and RS. The
example is a VC12 level.
Trail Trace Identifier

Accepted status
Indicates the status of the accepted trail trace.
Normal: Accepted TTI is valid. In this case also the fields Accepted Mode and
Accepted value are visible. The Accepted value field can be represented in ascii or
hexadecimal format by clicking on the toggle ascii/hex.
AIS: The container contains AIS, no TTI available
Unavailable: The TTI value can’t be determined. Might be due to an unstable
accepted TTI.
Unequipped: The VC12/VC4 container has an unequipped signal label, not
applicable for RS
Expected mode
Provisionable expected mode: String or Repeating byte mode
Expected
The trail trace identifier (string or bytes) expected by the system.
Transmitted mode
Provisionable mode: String or Repeating byte mode
Transmitted
The trail trace identifier (string or bytes) to transmit.
TIM detection
When this check box is enabled, trace identifier mismatch will be checked. An alarm will
be reported and as consequent action AIS will be inserted downstream and RDI in the
upstream direction. VC12 RDI is sent upstream only in case of a bidirectional cross
connect.

Trail Signal label

Accepted status
See above.
Transmitted
See above.
General
Degraded Threshold
The degraded treshold can be set to Threshold Set 1 or Threshold Set 2.
Monitor Mode
The default mode is Monitored for a termination point involved in a cross connect (see
page 101). When no alarming is required the mode can be set to Not Monitored.
Directionally
Cross connect type associated with the termination point.
Threshold set 1: Threshold 1 Duration (sec), Threshold 1 Count and
Threshold set 2: Threshold 2 Duration (sec), Threshold 2 Count
Per VC12 termination point you can specify when a signal is considered to be degraded
(DEG is declared). For this purpose you can choose from two sets of values:
Threshold set 1 existing of:
Threshold 1 Duration (in seconds) and
Threshold 1 Count
Threshold set 2 existing of:
Threshold 2 Duration (in seconds) and
Threshold 2 Count
A signal is considered to be degraded (DEG is declared) if within a number of
consecutive seconds a number of block errors per second has been detected. The
intervals can be specified with Threshold 1 Duration or Threshold 2 Duration, the number
of block errors with Threshold 1 Count or Threshold 2 Count.
The degraded signal is withdrawn if within the number of consecutive seconds the
number of block errors, for each second, was smaller than the specified value.
13.8.8 Test access output

The ADX200 and ADX201 support a dedicated test access output port. This test access
output is available at three banana receptacles, E1 signal according to G.703 in 120
Ohm.
For the ADX100 no dedicated port is present, but in fact every E1 port can be used as
test access output port.
A bridge can be provisioned via a unidirectional cross connect from the existing cross
connect to the E1 port to be used as a test port.
Caution: The ADX201 test access output port is only active when an Interface
Card is present in Slot 8. When no Interface Card is present in TS8,8 AIS is transmitted
on the test access output.
The test access output is referred to with TS8.8. In the ADX201 this port is also routed to
tributary slot 8 port 8. Add a unidirectional cross connect from the connection to be
monitored. Select the from point to distinguish the direction you want to monitor. The
VC12 termination point related to the test access port is also available and can be used
to view the VC12 path overhead. The output signal of TS8.8 in the ADX201 will be
identical to the signal on the test access output.

When bridging a unidirectional cross connect to the E1 port to be used as test port from
the cross connect to be measured.
The test access output cross connect provisioning can be directly viewed when clicking
TEST in the System overview.
Figure 76. Test Access Output
The current cross connect to the test access output (TS8.8) is shown, and in this screen
this connection can also be changed, when another connection needs to be monitored.
The TS8.8 is always the To point. When no cross connects exists, one can be added.
Furthermore also the test output can be path protected (see "SNCP Cross connects uni-
and bidirectional" on page 114).
13.8.9 Remote error indication

The System supports remote error indication (REI). This is supported for all layers MS,
VC4 and VC12. The REI is inserted in the upstream direction and corresponds with the
measured background block error rate in the downstream direction. When the far end
system supports far end performance monitoring these values can be used for the
measurements. Both VC4 and VC12 should be bidirectional.
13.9 Cross connects

To provide transmission over the System, cross connects have to be provisioned. From
each line port a fixed VC4 cross connect is present towards the low order cross connect
function. Within this low order cross connect VC12 cross connects can be provisioned.
Cross connects can be made full flexible, from:
every tributary port towards every TU12 (klm) on the line port, and vice versa
amongst line ports
amongst tributary port
The actions on cross connects consists of adding and deleting cross connects. Two basic
types of cross connects can be made
Unidirectional
Bidirectional
These types will be outlined in detail.
13.9.1 Definitions
Cross connects can be added and deleted. In this chapter the provisioning parameters
are listed.

From
The From point in a cross connect defines the originating point. Choosing which point will
become the from is mainly of importance when adding unidirectional cross connects.
Note that from an existing cross connect the from point can be edited, however this is not
possible for the to point.
To
The To point of a cross connect defines the destination point. At this point the VC12 path
overhead is terminated if it is a VC12 termination point. In the System VC12 termination
points do only exist at the tributary slot related points.
Prot
The protection point from a path protected cross connect.
VC12 SNCP path protection

The System supports VC12 SNCP path protection. The protection switch can be triggered
to become active if ,a TIM (Trace Identifier Mismatch),an UNEQ (unequipped VC) or a
DEG (degraded signal) condition occurs on the service connection (if the stand-by
connection does not show these defects).
VC12 Termination point

At a VC12 termination point the VC12 path is terminated at a To point and generated at a
From point. The provisioning of the VC12 termination point can be made (see "Ports and
termination points" on page 99). VC12 termination points only exist at the tributary port.
There is a fixed relation between the tributary port number and the VC12 TTP number.
These are noted as TSX.Y where X is the slot position and Y is the port number. Cross
connects can be added irrespective of the presence of Interface Cards.
TU12 connection termination points (see page 150)

The TU12 connection termination points do exist at the line ports. These points are noted
as LPX .klm. where X is the line port number and the klm identifies the position of the
TU12 in the VC4, the so called TU12 numbering:
k = 1 ... 3 = TUG3
l = 1 ... 7 = TUG2
m =1 ... 3 = TU12
The line port TU12 points are not terminated in the System but at the end points of a
VC12 path. In fact the line port points are TU12 non intrusive points, no overhead is
added or extracted.
When MSP is provisioned only the TU12 points from the worker MSP leg are available.
In the not cross connected TU12s, VC12 unequipped is inserted in the upstream
direction.
Type
The type identifies if the cross connect is unidirectional or bidirectional.

Bidirectional
A bidirectional cross connect supports traffic in two directions. Bidirectional cross
connects can be made between:
Line port and tributary port
Traffic coming from the line port is dropped to the connected port (downstream) and
traffic from the tributary port is added to the line port signal (upstream).
Tributary and tributary port
Traffic is connected in both directions between two tributary ports.
Line port and line port
Traffic is connected in both direction at TU12 level between the line ports selected.
This connection type can be used when there is no need to drop traffic in this
System. This type is called through cross connect.
Unidirectional
A unidirectional cross connect supports traffic in one direction. Coming from the From
point towards the To point. For the unidirectional cross connect several applications do
exist. Major difference with the bidirectional is that unidirectional cross connects can be
made between two free points but also can be added to the from point of an existing
cross connect (bridging) They only can be added to the from point, you have to realize
this when adding cross connects which you later want to bridge with a unidirectional cross
connect.
Loop back cross connect
A unidirectional cross connect with the same from and to point, can be used as a
VC12 loop back.
Broadcasting
Uni directional cross connects can be multiple bridged. In this way a broadcast
function is supported. Multiple outputs are provided with one source signal. The
source signal is coming from the “From” point. The number of bridged points is
unlimited. The return path is unassigned. A point which is once being used as a “To”
point can only be used once.
Test access output port
The test access output is available at the ADX200 and ADX201 platform. This output
can be used by adding a unidirectional cross connect to this port, with the test access
output as to point. For non intrusive monitoring the test access output can be added
as unidirectional (bridged) to an existing cross connect to be monitored (see "Test
access output" on page 108).
Unidirectional cross connects can be made between the same type of points as
bidirectional. As unidirectional cross connects do not have a return path no RDI and REI
will be inserted (see page 151).
13.9.2 Listing, editing and deleting cross connects

MENU: XCONNECT | LIST
To delete or edit cross connects use

Figure 77. Cross Connect List
Delete
When selecting the cross connect to be deleted and next clicking delete, this cross
connect will be deleted. No further message is shown and transmission via this cross
connect will be lost.
Details
To show and modify the settings of the cross connect.
Note: If a user considers that in the future an unprotected cross connect might be
changed into a protected it is important to realize that LP<->TP is different than TP<-
>LP. Only the first one allowes the conversion to a protected cross connect.
Figure 78. Details XConnect
The change can be made by selecting the new From / Protection point and selecting
Apply.

13.9.3 Adding cross connects

The System supports sequentially adding cross connects. After a cross connect has been
added the window returns with a pre-selection for the next logical selection. When no next
logical selection is available no pre-selection is made. In the selection list only available
cross connect candidates are listed. Once a point has been cross connected it will be
removed from the selection list. Supported are:
Bidirectional cross connects (on page 113)
Unidirectional cross connects (on page 113)
Protected SNCP Bidirectional cross connects (see "SNCP Cross connects uni- and
bidirectional" on page 114)
Protected SNCP Unidirectional cross connects (see "SNCP Cross connects uni- and
bidirectional" on page 114)
Bidirectional cross connects

Adding a bidirectional cross connect will set the VC12 termination point(s) involved to
monitored. Adding a unidirectional cross connect will set the mode to monitored if the
VC12 termination point is the To point. Deleting a cross connect will not change the
monitoring mode. For a bidirectional cross connect not always a VC12 termination point is
involved. When connecting to a line port a TU12 CTP (connection termination point)is
involved and these do not have a monitoring mode.
Bidirectional cross connects can be made using following options:
LP -> TP
TP -> LP
LP -> LP
TP -> TP
Figure 79. Add Bidirectional Cross Connect
When selecting CROSS CONNECTS | ADD BI DIRECTIONAL | TP -> LP a bidirectional cross connect
from a tributary port to a line port can be made.
Select the desired to and from point, and next select Add. The cross connect will be
established. If you assign a user label (see page 100) it is also shown in the screen.

Unidirectional cross connects

Adding a bidirectional cross connect will set the VC12 termination point(s) involved to
monitored. Adding a unidirectional cross connect will set the mode to monitored if the
VC12 termination point is the To point. Deleting a cross connect will not change the
monitoring mode. For a bidirectional cross connect not always a VC12 termination point is
involved. When connecting to a line port a TU12 CTP (connection termination point)is
involved and these do not have a monitoring mode.
Unidirectional cross connects can be made as:
LP -> TP
TP -> LP
LP -> LP
TP -> TP
When selecting CROSS CONNECTS | ADD UNI DIRECTIONAL | TP - >LP you can add a unidirectional
cross connect from a tributary port to a line port.
Figure 80. Add Unidirectional Cross Connect
Select the desired to and from point and next select Add, the cross connect will be
established.
Note: This is the same for the other add unidirectional cross connect options.
13.9.3.1 SNCP Cross connects uni- and bidirectional
An SNCP protected cross-connect can be created in two ways:

Adding a protection leg to an unprotected cross-connect. This operation is non-
service effecting.
Create from scratch.
An SNCP cross-connect can be removed by either:
Convert a SNCP protected cross-connect into a unprotected cross-connect. This can
be done by removing either the worker or protection leg. Which makes a hitless
conversion possible even if the near and the far end do not select the same path.
Remove the SNCP protected cross-connect A SNCP protected cross-connect can be
either uni- or bidirectional. SNCP uni- or bidirectional cross connects can be made as:
LP1 ->TP <- LP2
LP2 -> TP <- LP1
When selecting XCONNECTS | ADD SNCP UNIDIRECTIONAL | LP1 -> TP <- LP2 you can add an SNCP
unidirectional cross connect for tributary port

Figure 81. Add SNCP Unidirectional Cross Connect
Select the desired ports, next select Add, the cross connect will be established.
Note: This is the same for the other add uni- or bidirectional SNCP cross connects.
Note: 1+1 MSP and SNCP are mutual exclusive.
Note: For SNCP protected unidirectional cross connects only the selector is
provisioned, and not the bridge. A bridge can also be created manually.
Swapping worker and protection

Swapping of worker (from-leg) and protection (prot-leg) requires two user operations.
1. First the from-leg is removed
2. hereafter the prot-leg is assigned with the previous worker leg.
In order to change the leg of an SNCP protected cross-connect:
1. one needs to temporarily convert the cross-connect into an unprotected one by
removing the worker or protection leg.
2. Now a different protection leg can be added to the unprotected cross-connect
resulting in the changed SNCP protected cross-connect.
An SNCP protected cross-connect can be either uni- or bidirectional.
Editing cross connects
To edit an SNCP cross connect use menu: XCONNECTS | LIST, select a cross connect and
press Details.

Figure 82. Editing a cross connect
In this screen the following fields are shown:
Current
Accepted TTI Status and value: identifies the accepted status (see page 104) and
value. This data is shown for the Protection and From leg. Per leg a non intrusive
monitor is supported.
Type: identifies the type of cross connect (see "SNCP Cross connects uni- and
bidirectional" on page 114).
Common settings
Accepted TTI Status: identifies the accepted status (see page 104).
TIM detection: identifies if the Trail Identifier Mismatch is enabled (see page 106).
Monitoring mode: can be monitored or not-monitored (see page 104).
Selected Degraded Threshold: identifies the threshold set (see "Degraded Threshold
provisioning and handling" on page 105).

SNCP Group
State: identifies the state of the SCNP group. The state can be:
Failed: There is a failure.
Manual: The user executed a manual switch.
Forced: The user executed a forced switched.
Degraded:The signal was degraded (see "Degraded Threshold provisioning and
handling" on page 105)
No request: There was no request for this group.
Active: either the worker or protection is active.
Edit
Remove Leg: to remove the worker or protection leg.
Switch request: The state of an SNCP group either be the result of a user or a
System switch request. Priorities are assigned to switch requests, the lower the
number, the higher the priority:
1. Clear, executed by user
2. Force, executed by user
3. System forced, executed System
4. System degraded, executed System
5. Manual, executed System
Note: You cannot overrule the status of an SNCP group with a switch request
having a lower priority than the current priority. In this case you first have to execute a
"Clear" request and then the actual request.
13.10 Transmission protection MSP

In terminal applications 1+1 Multiple Section Protection in unidirectional mode, revertive
and non revertive is supported. The MSP protocol is compliant with ITU-T G.841/Clause
7.1 and ETS 300417-3-1.
The MSP protocol enables the user in an end to end terminal application to have an STM-
1 section protected. Both worker and protection leg carry the same information. At the
receiver side the selection for worker or protection is made. When using MSP only one
VC4 (63*VC12) container can be transmitted instead of two. Only the VC4 related to the
worker MSP leg will be available.
The service interruption due to an MSP switch will be shorter than 50 ms.
An MSP pair can be set up between line port 1 and line port 2. With line port 1 as worker
and line port 2 as protection and vice versa.
13.10.1 Precautions
When provisioning an MSP pair:
The protection leg may not carry traffic (no cross connects provisioned).
The protection leg may not be assigned as timing reference.
When above precautions are not full filled an error message is shown on the Web
browser when trying to create an MSP pair.

13.10.2 Definitions
Unidirectional
In unidirectional mode the switching of near end and far end are independent.
Switch criteria
Failures detected at the MS layer will lead to an MSP switch. When at the MS section an
MS1cSSF or MS1cAIS is detected a signal fail will be declared for that leg. When an MS
degraded is detected the leg will be declared Degraded.
Signal fail
A signal fail indicates that the corresponding leg has an MS failure. Also SFP failures are
included.
Degraded
The corresponding leg has an MS degraded alarm, based on the degraded threshold
provisioning (see "Degraded Threshold provisioning and handling" on page 105).
Worker
The leg defined as worker during MSP setup.
Protection
The leg defined as protection side during MSP setup.
Active leg
The leg currently active, the selected input source.
Standby leg
The leg currently not active.
Non-revertive
In non revertive mode the traffic will switch to the protection when a failure has been
detected at the worker side and remains at the protection side when the failure has been
cleared.
Revertive
In case of a failure in revertive mode the traffic switches to the protection side and will
switch back when the failure has been cleared after expiry of the wait to restore timer.
Wait to Restore (WTR)

The wait to restore timer, only applicable in revertive mode, defines the time the switch
will revert after a failure has been cleared. During expiry of the wait to restore time no
failure should be detected otherwise the state will return to failed. To avoid intermittent
behavior of the MSP switch, due to a toggling MS1 failure, between failed and not failed,
the WTR timer is used. In this way a MS1 layer needs to be non-failed for a certain
period, this period is the WTR time.
External switch requests

The user can invoke switch requests via the web browser to override the automatic
switching (see "External switch requests" on page 118). In case of maintenance this
might be useful.

MSP and alarming

The alarm location used for the VC4 and TU12 locations will differ when MSP is enabled.
As these termination points are in the traffic path, related to the active leg, the alarm
location will be LPa indicating it is related to the active leg. Check the MSP details to find
out which leg is active.
13.10.3 Creating an MSP pair

To create an MSP pair select PROTECTION | MSP | CREATE.
Figure 83. Creating an MSP Pair
The MSP pair can be created with LP1 as worker and LP2 as protection or vice versa.
Select the operation mode required, non-revertive or revertive and select Create. Once
the MSP pair has been created no changes regarding operation mode or
worker/protection side can be made. To change this the pair has to be deleted and
recreated with the required settings.
Note: If a port is carrying traffic or the MSP pair already exists, a warning is
displayed.
Figure 84. MSP Port is carrying traffic

13.10.4 Deleting an MSP pair

When an MSP is required to be deleted, select PROTECTION | MSP | DETAILS, next click Delete.
Figure 85. MSP Overview
The MSP pair will be pre-selected, as there is only one MSP pair available. Select Delete
to have the MSP pair deleted. This might be service affecting, only if near end and far end
are both set to worker no service impact is to be expected.
13.10.5 MSP details

This section will describe the MSP details window.
Select menu: PROTECTION | MSP | DETAILS, next select an MSP protection group and press
Edit.
Figure 86. MSP Details
Worker
Assigned
Indicates which line port is defined as worker leg.
SignalState
Indicates the state of the worker leg.
Error free: No failures detected.
Failed: An MS signal fail has been detected.
Degraded: An MS degraded has been detected.
Protection
Assigned
Indicates which line port is defined as protection leg.
SignalState
Indicates the state of the protection leg (see Worker signal state).

Active
Indicates which leg is currently active
State
The state can be:
No request: No change to the current switch state of the MSP pair.
Failed: A failure has been detected at one or both MSP legs.
Degraded: An MS degraded has been detected to one or both of the MSP legs.
Wait to restore: A recent failure has been cleared, the wait to restore timer is
running.
Forced: A forced switch request is set.
Manual: A manual switch request is set.
Lockout: The MSP protection is locked out, worker is selected.
Switch request: More details are available (see "External switch requests" on page
118).
Operation: Indicates the mode of operation revertive or non revertive.
SW type: The System only supports unidirectional, bidirectional is not supported.
WTR: Wait to restore timer. More information is available (see "External switch
requests" on page 118). In non revertive mode this timer is grayed out.
Switch Request
To override the MSP automatic switching you can invoke an external switch request (see
"External switch requests" on page 118).
13.10.6 External MSP switch requests

To override the MSP automatic switching the user can invoke an external switch request.
The switching can be executed in the window.PROTECTION | MSP DETAILS
Figure 87. MSP Switch Requests
Executing switch requests may lead to a service interruption of less than 50 ms. The
current switch state is shown in the state field.
When executing a switch request a warning will pop up, to indicate switching might be
service affecting, the user has then the option to cancel the switch request.

Switch request
Choose from:
Clear: To clear an outstanding switch request, including WTR timer.
Lockout: When setting the switch state to lockout, MSP protection switching is
disabled. The worker leg is selected for traffic.
Forced Sw to worker: Enforces switching traffic to the worker line. It overrides
automatic switching even in case of a signal fail or signal degrade. This can be
service affecting.
Forced Sw to protection: Enforces switching traffic to the protection line. It
overrides automatic switching in case of a signal degrade but not in case of a signal
fail on protection. This can be service affecting.
Manual Sw to worker: Switches conditionally traffic to the worker line. When a
failure is present at the worker line switching is rejected. In case a failure is raised
during the manual to worker state traffic will switch to the protection line. When e.g. a
forced request or lockout is outstanding a manual request will be rejected, the forced
request first has to be cleared.
Manual Sw to protection: Switches conditionally traffic to the protection line. When
a failure is present at the protection line switching is rejected. In case a failure, Signal
Fail and Signal Degrade, is raised during the manual to protection state, traffic will
switch to the worker line. When a forced request is outstanding a manual request will
be rejected, the forced request first has to be cleared.
Wait to restore
The WTR (wait to restore) timer is only applicable in revertive mode. The default value is
5 minutes. This timer can be provisioned between 0 and 60 minutes in steps of 1 minute.
Setting the timer to 0 minutes will disable the wait to restore timer.
Note: The provisioned WTR value is displayed.
13.11 Synchronization
The intention of Synchronization is to synchronize the whole SDH network to one master
clock. The provisioning of the individual network elements must be aligned to be
synchronized from one side and forward the reference towards the other side of the
network. Before provisioning the System a network synchronization plan must be
available, including a backup plan when the master clock fails, preventing timing loops in
any scenario.
The System has an internal clock according to ITU-T G.781 option-1. with an accuracy of
± 4.6 ppm of its nominal frequency
The System can be synchronized via:
Both STM-1 line port interfaces.
One of the 2Mb/s ports.
Provisioning and maintaining synchronization consists out of three main areas,
Assigning and defining the references to be used which is described (see
"Provisioning timing sources" on page 124).
Provisioning of the System timing, like WTR timer, locked or free running mode, and
use of the SSM algorithm which is described (see "Provisioning timing sources" on
page 124).
External timing switch request, to overrule the automatic timing selection algorithm.
Changing the synchronization setting takes some time to complete the details shown on a
window returned after the action is not up to date. A refresh of the window is needed to
get the actual details.

Note: In an appendix (see "Synchronization Network" on page 153) an example is

given for provisioning synchronization of a network.
13.11.1 Definitions
Timing source
A timing source is a provisionable reference from which the System can be synchronized.
The System can be synchronized from both the line ports or from one of the E1. In case
MSP is provisioned only one line port reference, the worker MSP section, is available.
Quality Level (QL)

The quality level indicates the quality level of a reference or System. This QL is
transmitted in the STM-1 overhead in the synchronization status message, the S1 or SSM
byte. For E1 signals no QL is supported.
Reference Fail
A reference fail will be declared when the signal related to that reference has a failure
which impacts the timing reliability. This can be transmission related failures like
STM1cLOS,STMcLOF, MS1cAIS, E1cLOS or E1cAIS. Another cause might be an
excessive frequency offset of the reference. When the frequency of the reference has a
deviation of more than ± 15 ppm to the internal clock the reference will be declared failed.
Note that in this case no port level alarm is raised.
SSM byte
The SSM byte contains the quality indication of the reference. The System supports this
only for the STM-1 line port signals. The definitions according to G.781 are listed below.
The SSM byte is only applicable when QL is enabled. When QL is disabled DNU is sent
out and the incoming SSM bytes are ignored.
Table 7. QL Overview
QL S1/byte* Accuracy Description
DNU 1111 Not Do not use for synchronization, indicates the
applicable signal should not be used for synchronization.
Unknown Not No QL information is available
applicable
PRC 0010 10-11 Primary reference clock.
-9
SSU-T 0100 1.5.10 Synchronization supply unit-transit, indicates
the timing is derived from a transit SSU
SSU-L 1000 3.10-8 Synchronization supply unit-local indicates the
timing signal is derived from a local SSU.
SEC 1011 4.6.10-6 SDH equipment clock indicates the timing
signal is derived by an SDH equipment clock
(internal System clock)
*the first nibble of the S1 byte is 0000.
QL-in
The QL-in indicates the received SSM byte from a timing reference.

QL timing source
The assigned QL of a timing source. When Auto is provisioned this value is equal to the
QL-in, when a value has been provisioned this value will be the QL-out.
Outgoing SSM
The outgoing SSM value is transmitted in the S1 byte of the STM-1 signal, the line ports.
This is not supported for the E1 ports. The outgoing SSM is not visible at the user
interface.
In case the System is in holdover or free running mode the SSM out is SEC.
In case the System is locked to a certain port the SSM out on this port is DNU, to
prevent timing loops in the network.
The SSM out on the line ports represents the System QL, except for the active
reference see previous case.
In case of an MSP pair both line ports will have the same SSM out value.
When QL is disabled the SSM out will be DNU.
13.11.2 Provisioning timing sources

The System has the ability to provision three independent timing sources. One from one
of the E1 ports and two from both line ports.
When selecting menu: TIMING | TIMING SOURCES the three timing sources are listed:
Figure 88. Timing Sources List
Timing Source
A timing source is a provisionable reference from which the System can be synchronized.
The System can be synchronized from both the line ports or from one of the E1. In case
MSP is provisioned only one line port reference, the worker MSP section, is available.
Assigned to
Indicates the reference assigned to the timing source.
Active
Indicates the state of the timing source.
Active: This timing source is currently the source for the System timing
Not active: This timing source is currently not the source for the System timing
Failed: This timing source failed.

Signal Status
Indicates the status of the signal provided to the timing source
Normal: No signal fail, the signal is valid
Failed: A failure has been detected for this reference
Wait to restore: A recent failure on this reference has been cleared and during
expiring of the wait to restore timer the state is wait to restore.
Not connected: No reference has been assigned to this timing source.
QL Timing source
The quality level of this timing source.
When selecting the timing source to be viewed or edited select Edit.
13.11.3 Provisioning line port references

Figure 89. Edit timing source
Assigning and editing the reference are separate actions, it is preferred to first assign the
reference and next edit the settings.
Assign
Select the line port to be assigned to this timing source and select the assign button. Only
the line port references available are shown. When MSP is enabled only the worker port
of the MSP pair is available.
Edit
Choose from:
Reference: indicates the assigned reference to this timing source.
Reference fail: indicates if the reference has a signal fail.
Error Free: no reference fail.
Fail: reference fail is present. For a line port reference this can be due to a
STM1cLOS, STM1cLOF, RS1cTIM, MS1cAIS or an excessive frequency offset
of the reference signal.
Monitored
Choose from:
Monitored
Not monitored: Now a timing source failure can be reported for this timing source
with a SYNCcTLF.
QL-in
The quality level as indicated by the SSM byte of the reference.

QL status
Status can be valid or invalid:
Valid: The QL has a valid value.
Invalid:The QL has an invalid (unknown) value.
QL Timing source
The assigned quality level of the timing source, which is input for the timing source
selection.
QL provisioned
For line port references the default value is AUTO. When using AUTO the QL level is
taken from the SSM value received from this reference. When this reference is unable to
provide a SSM value a provisioned value can be chosen according to the quality of this
reference. Be aware when using a provisioned value changes in the quality of this
reference will not be recognized (see page 128).
Signal Status
Indicates the status of the timing reference:
Normal: The signal is valid
Failed: A failure has been detected for this reference
Wait to restore: A recent failure has been cleared for this reference. During expiring
of this timer the state is wait to restore
Not connected: No reference has been assigned to this timing source.
Clear WTR
When the state is wait to restore this state can be overruled by clearing the wait to restore
timer, select this box and click apply.
Priority
The priority of this timing source, used in the selection for System timing.
Lockout
When this box is selected the timing source is locked out. The reference will not be used
as timing reference. The default value is locked out. When provisioning the timing source
the lockout needs to be deselected when the timing source is required to be operational.
Using lockout for a reference is useful in maintenance operations. Each reference
individually can be locked out.
13.11.4 Provisioning tributary port references

When selecting the timing source to be edited:
Figure 90. Tributary Timing Source Provisioning

Only differences with provisioning line port (see "Provisioning line port references" on
page 125) references are explained.
Reference
Only references from Interface Cards which are in the ASSIGNED state are available.
Only one E1 port from all tributary ports can be selected.
QL-in
As the System does not support SSM values for the E1 ports, there is no QL-in value.
Reference status
A reference fail for an E1 port may be due to:
E1cLOS or E1cAIS.
An excessive frequency offset of the reference.
QL provisioned
As the System does not support SSM for E1 tributary ports thus a QL value needs to be
provisioned. A value corresponding to the quality of the reference needs to be chosen. Be
aware that changes in the frequency accuracy of this reference will not be observed. The
default value is SSUT.
13.11.5 System timing

When provisioning System timing, the timing mode can be chosen and the use of the
SSM algorithm. Next to that timing reference switches can be made to overrule the
automatic selection when the System is under maintenance. Provisioning and switching
are separate actions in the System timing menu.
Select menu: TIMING | SYSTEM TIMING
Figure 91. System Timing Provisioning
State
Indicates the System timing state:
Normal: The System is locked to a reference, only applicable in locked mode.
Holdover: The System has fallen back to its holdover clock, all references available
are failed. Only applicable in locked mode.
Free Running: The System is in free running mode. System timing is running on its
internal clock, timing mode will be free running
Mode
Defines the System timing mode of the System.

Free running mode: In free running mode the System is synchronized via the
internal clock. No external references are used for System timing. The System
quality will be SEC.
Locked mode: In locked mode the System will be synchronized by an external
reference. The selection is based on the provisioned timing sources (see "System
timing" on page 127).
QL
Indicates the System quality level.
QL Enabled (see page 128) If this selection box is cheked, the System will use the SSM
algorithm to select a timing reference. Furthermore the System Quality level (outgoing
SSM) will indicate SEC in free running mode and the QL-out of the selected timing source
in locked mode. When QL is not enabled the System timing will not select timing
references based on the SSM algorithm but will do this only based on the priority of the
references. The System Quality level (outgoing SSM) will be set to DNU.
WTR Time
Defines the wait to restore timer. The default value is 5 minutes. The timer can be
provisioned between 0 and 60 minutes, in 1 minutes steps. When using 0 no WTR is
being used. To avoid intermittent behavior of the timing reference switch, due to a
reference that toggles between failed and not failed, the WTR timer is used. In this way a
reference needs to be non-failed for a certain period, this period is the WTR time.
Switch Status
Indicates the timing reference switch state which has been made in the timing switch
window.
Selection
The timing source to be switched. Select the timing source 1, 2 or 3.
Switch Request
Timing reference switching is normally not service affecting, however in case of retimed
E1 ports a reference switch might be service affecting (see "Retiming E1 ports" on page
129).
when executing a switch request a warning will pop up to indicate the action might be
service affecting. The user has the option to cancel the switch request. Impact of service
due to timing reference switches is very low.
The following switch request are available to override the automatic selection process
(the lower number, the higher the priority):
Clear: To clear an outstanding switch request, including WTR timer.
Forced: A forced switch completely overrules the automatic selection process.
Irrespective of the state of the reference. Even a failed or not connected reference
may be selected and will result the System to switch to holdover state.
Manual: A manual switch only overrides the automatic selection process in the
priority selection. In case a reference fail or a another reference has a better QL the
automatic selection will take over.
13.11.6 System timing reference selection

The selection of the active reference can operate in two modes, priority based (on page
128) and SSM based (see "SSM based algorithm" on page 129).
Each timing source can be provisioned with a priority. These priorities can be 1,2 or 3.
The lower this number the higher the priority. Multiple timing references may have the
same priority.
Priority based selection is operational when QL is disabled. The reference with the
highest priority will be selected. In case multiple references have the same priority the
selection is random. When a reference fails the next in priority will be chosen, when the
first becomes non-failed the System will revert to the reference with the highest priority.

When multiple references have the same priority and one of them fails, the other one,
with same priority will be chosen. When the failed reference becomes available again the
System will not revert to that one.
SSM based algorithm

When QL is enabled the selection is SSM based. The reference with the highest quality
will be chosen. See table 1 for the QL definitions. The quality levels in descending order
are PRC, SSU-T, SSU-L, SEC.
The following rules are applicable for the SSM based selection:
All references that are not failed and do not have SSM=DNU are considered for
selection
The reference with the highest QL will be selected.
In case multiple references have the same QL, the one with the highest priority is
selected.
In case multiple references have the same QL and the same priority, the selection is
random.
In case no suitable reference is available the System will switch to holdover and a
SYNCcBHO is reported.
13.11.7 Retiming E1 ports

Each individual E1 port can be provisioned in retiming mode. In retiming mode the
frequency of the outgoing E1 signal is resynchronized with the System frequency. A
retimed E1 output port can be used as timing reference for the System connected to. As
the E1 signal coming from the retimed port has the System timing frequency. In normal
operation, self-timed, the frequency of the E1 output signal is the floating avarage of the
frequency of the E1 input signal.
Using an E1 port in retiming mode might affect the traffic on this connection. When there
is a frequency difference between the incoming E1 payload signal and the System
frequency, this will cause bit errors. The frequency difference is handled with a buffer.
When there is a frequency difference this buffer will over- or underflow. Each over- or
underflow will lead to a buffer re-center. This will cause a controlled slip. A frequency
difference of 1 ppm will lead to a slip once per halve minute.
The provisioning of retiming is part of the E1 port provisioning.
Select the menu TRANSMISSION | PORTS | TRIB PORTS, then select the tributary port and click
Edit.
Figure 92. Retiming Provisioning

Timing Mode
Default timing mode is Self Timed, also Re-Timed can be selected.
Self Timed: Normally the E1 output signals are Self Timed. This means that the E1is
recovered from its TU12 envelope by deleting all non-E1 octets. This yields a gapped
signal which is consequently smoothed by means of a Phase Locked Loop. A
disadvantage of this method is that the slow phase variations introduced by
occasional TU12 pointer adjustments or VC12 stuff-bits are too low frequency to be
filtered by the PLL, which acts as a low-pass filter for phase variations (equivalent 3
dB bandwidth below 1 Hz). For normal applications, this wander introduced by
occasional pointer and mapping adjustments can be safely ignored. However, in
case the E1 output is used by the attached equipment as a reference for a (high
quality) clock, it may be rejected due to these phase excursions.
Re-Timed: Alternatively, the E1 output signal can be Re-Timed by the internal
oscillator of the System. This avoids phase excursions due to TU12 pointer
adjustments. A necessary condition is that the internal System clock is locked to a
reference that is synchronous with the equipment that generated the E1 that is to be
retimed. Otherwise, the buffer in the E1 output circuit will regularly overflow or
underflow. Each overflow or underflow event leads to a buffer re-center (causing
frame loss events in the downstream equipment) or a controlled slip (avoiding OOF
in downstream equipment, but only supported in ISDN mode).
Accepted Timing QL
This defines the minimum quality level for which the port will be retimed. When the
System QL is below this value the port will switch to its fall back mode. When QL is
disabled in the System timing settings the retimed port will not check on the acceptance
timing QL and will always stay retimed.
Timing Fall back mode
The default mode is none.
None: The port will stay re-timed but the quality of the frequency is below the
acceptance quality level.
Self timed: The port will switch to self timed when the QL of the System is below the
acceptance QL.
AIS: When the System QL is below the acceptance QL the E1 port will sent out AIS.
System QL
The current QL of the System
Port timing state
Identifies the current state
Normal: The port is working in the provisioned mode
Fall back: The port is provisioned in re-timed mode but is in fall back mode, due to
the System QL being below the acceptance QL
Report timing alarms
Default value is disabled. When setting this to enabled an alarm is raised when the port is
in fall back mode, due to the System QL being below the acceptance QL. The
SYNCcLRR alarm will be reported for this port.

13.12 SNMP
SNMP settings can only be changed with admin rights.
The System supports a Simple Network Management Protocol (SNMP) agent. This
enables the System to sent SNMP alarm traps or notifications to an SNMP manager, also
the current raised alarms can be requested. The System supports both SNMPv1 and
SNMPv2. The user can provision up to five SNMP managers. These are identified by
their IP address. The community string has to be entered, public and a selection for traps
v1 and or v2 notifications can be made.
Autonomous events are reported to the SNMP manager. In the trap notification the alarm
description, location, severity and time stamp is shown and if it is a raise or clearing.
Requesting the current alarm list is possible when using the enterprise MIB with prefix:
iso.org.dcd.internet.private.enterprise AimValleyBV(1.3.6.1.4.1.23862).
Before being able to show this list you have to import the System MIB to the SNMP
browser. The MIB files are available at the System software CD. Please contact ADC for
MIB files. Next you compile the MIB in the SNMP browser. Now the browser is able to
retrieve the current alarm list. These actions will be specific for the SNMP browser being
used.
The alarm reporting towards the SNMP manager is identical as the alarms reported at the
web browser.
Select menu: SYSTEM | SNMP SETTINGS
Figure 93. SNMP Details
Manager IP address
The IP address of the SNMP manager.
Read Community
Provisionable authentication string.
V1 trap / V2 Trap
Select V1 Trap if SNMPv1 traps are required. Select V2 Trap if SNMPv2 notifications are
required.
If both are enabled a trap and notification is reported.
Alarm community
Allows the user to group alarm traps.

13.12.1 Current alarm list with SNMP

Figure 94. Example of a current alarm list on a SNMP browser
Note: The UTC time is used (see page 20).
13.13 OSPF provisioning
13.13.1 OSPF settings

The OSPF setting can be provisioned via the menu: SYSTEM | IP SETTINGS | OSPF | GENERAL.
Figure 95. OSPF Settings
OSPF General
Enabled
To enable or disable the OSPF. The default is disabled. If enabled you also must
provision the System with a router ID.
Router ID
To enter the System OSPF router ID. The router ID is a /32 IP address that uniquely
identifies the router within an AS. The default is 0.0.0.0.
RFC1583
OSPF standard, read only value. It shows that OSPF version 2 is supported.
ABR
Not applicable in this version (see page 31). Read only value.

ASBR
Indicates if this System is an ASBR (see page 32) or not. If this system is provisioned as
an ASBR than the route will be advertised.
Version
Indicates the OSPF version. Read only value.
Apply: To confirm the changes.
OSPF ASBR:
Default routes:
Advertise: To enable or disable default route advertisement. .
Metric: Link costs (see page 33), read only value.
Metric Type: The default route advertised by an ASBR has a cost metric of 'Type 2'
('E2'). This means that the internal path cost for reaching an ASBR node is not taken
into account. Only the advertised external costs (LAN=10) matters for the decision
which ASBR node should be used as default route. Read only value
Apply: To confirm the changes.
Manual routes (Not supported):
Advertise: Read only value.
Metric: Read only value.
Metric Type: Read only value.
Refresh
To update this window.
List Interfaces
To go to the management interfaces of this System.
List OSPF Interfaces
To go to the interface OSPF settings (see page 133).
13.13.2 OSPF Interfaces

The OSPF interfaces can be reached via the menu: SYSTEM | IP SETTINGS | OSPF | INTERFACES.
Figure 96. OSPF Interfaces
Name
Displays the name of the OSPF interface.
Enabled
Displays whether the OSPF interface is activated.
Area
Displayes the Area of the OSPF
Refresh

List Interfaces
To go to the management interfaces of this System.
Edit
Select the interface to edit and click Edit.
LAN (see page 74)
LP1 or LP2, see figure Interface LP1
Figure 97. Interface LP1
Remote IP address
The IP address as it is assigned at the remote side of the point to point link.
IP Address
Own IP address for this line port. Can be changed, press Apply to confirm.
Remote IP address
Fixed to 32.
13.13.2.1 OSPF LAN/LP Interfaces
The OSPF LAN/LP interfaces can be reached via the menu: SYSTEM | IP SETTINGS | OSPF |
INTERFACES. A window appears. In this window click List OSPF Interface
Figure 98. OSPF Interfaces LAN or LP
Depending on the selection LAN or LP1 /LP2 the screen displays OSPF Interface LAN,
OSPF Interface LP1 or OSPF Interface LP2. The following fields are shown:
Enabled
Displays whether the OSPF interface is activated or not. From this screen the value can
be set to enabled or disabled.
Area
Displays the Area of the OSPF. Read only value.
Metric
Link costs (see page 33). Read only value.
Router Priority
Used to determine the designated router (see page 32).. Read only value.
Auth Type, Auth Key
Used to check if another Systems belongs to the family. Read only value.
Hello Interval (sec), Router Dead Interval (sec)
OSPFs send hello packets to their neighbours. They are used to check whether the
neighbours can be reached or not. If a System (router) cannot be reached for a Router
Dead Interval time the router entries for this router are removed.

Apply
To confirm the changes.
LSA Retr (sec) / Transit Delay (sec)
LSAs are exchanged between adjacent OSPF routers. This is done to synchronize the
link state database on each device.
When a router generates or modifies an LSA, it must communicate this change
throughout the network. The router starts this process by forwarding the LSA to each
adjacent device. Upon receipt of the LSA, these neighbors store the information in their
link state database and communicate the LSA to their neighbors. This store and forward
activity continues until all devices receive the update. This process is called reliable
flooding. Two steps are taken to ensure this flooding effectively transmits changes without
overloading the network with excessive quantities of LSA traffic:
Transit Delay: Each router stores the LSA for a period of time before propagating the
information to its neighbors. If, during that time, a new copy of the LSA arrives, the
router replaces the stored version. However, if the new copy is outdated, it is
discarded.
LSA Retr: To ensure reliability, each link state advertisement must be acknowledged.
Multiple acknowledgements can be grouped together into
a single acknowledgement packet. If an acknowledgement is not received within, the
original link state update packet is retransmitted.
Refresh
List OSPF Interfaces
To go to the OSPF interfaces of this System.
13.13.3 OSPF Systems

The OSPF setting can be provisioned via the menu: SYSTEM | IP SETTINGS | OSPF | SYSTEMS.
Figure 99. OSPF Systems
RouterID: Shows OSPF enabled systems that can be reached, note the RouterId is
displayed.
13.14 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.14.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 100. 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 (see page 20).
[!]: 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 101. GUI Settings
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.15 Current Alarms

The current alarms window shows all current outstanding alarms. When selecting ALARMS |
CURRENT the current alarm list will be shown
Figure 102. Current Alarm List
Location
This identifies the location of the alarm.
Alarm type
This identifies the type of alarm.
Severity
This indicates the severity of the alarm, as defined in the alarm profile.
Raised
The time stamp based on the System time of the System, presented in the local time (see
page 20) zone.

Details
When selecting an alarm in the list and next clicking details the long alarm description will
be shown in a pop up window. The long alarm description will also be shown when
pointing the alarm with the mouse indicator at the alarm, not available when using
Internet Explorer 6.0.
Figure 103. Alarm Details VC12vUNEQ
To have the current alarm (see "Resolving alarms and problems guide" on page 139) list
updated to the current situation, you have to refresh it. Notifications towards the
provisioned SNMP manager will be sent autonomously.
13.16 History alarms

The System has a log for 500 cleared alarms. Alarms which are cleared will be put in the
alarm history with the alarm type, severity, time raised and time cleared time stamp.
An alarm status change is automatically updated in the history.
MENU: ALARMS | HISTORY.
Figure 104. Alarm History List
Refresh
The history list is not autonomously updated, a refresh (see "Most recent alarm bar" on
page 135) is needed. The System has a log for 500 cleared alarms. It this number is
exceeded the first entry is removed from the list.
Note: Retrieving a large alarm history list might take 10 seconds.
Clear
To clear the history list and start with a clean list again.
Details
Select the alarm and click Details. Additional information will be displayed in a pop-up.
This additional information also comes available if you point the alarm with the mouse
indicator. This option is not available for Internet Explorer 6.0.
Backup
Alarms can be downloaded in a tab separated file for off line processing using e.g. excel.
To current alarms
Shows the currently present alarms.
Note: Times shown are based on the local time zone (see page 20).

13.17 Alarm profiles, severities, reporting and LEDs
13.17.1 Severities and reporting

The alarm severity and reporting state can be provisioned per alarm type individually.
Figure 105. Alarm Profile List
13.17.2 Displaying provisioned alarm severities and reporting states

When selecting menu: ALARMS | PROFILE/SEVERITIES, the list of all alarms with the current
provisioned severity and reporting state is shown.
Severity
The severity of an alarm indicates the impact of the alarm.
Major: Urgent alarm, that requires direct action
Minor: Non urgent alarm, requires deferred maintenance action
Info: Information alarm
Changing the severity of a not outstanding alarm will be effective the next time the alarm
will be raised. Changing the severity of an active alarm will clear this alarm, and put it in
the history list, and re-raise the alarm with the new severity and a new time stamp.
The severity of an active alarm is directly reflected on the LED indicators (on page 139).
13.17.3 Reporting mode

When changing the reporting state of an inactive alarm this will be effective the next time
the alarm cause is present.
Changing the state of an active alarm has a slightly different behavior. When changing
the state of an active alarm from reported to not reported this will not clear the alarm, this
will be effective the next time this alarm will be present. When changing the state of an
active alarm from not reported to reported, so currently this alarm is present but not
reported, this will be effective directly.
Figure 106. Severity Settings
When selecting the alarm to be changed and selecting edit the changes can be made.

Severity
The severity can be set to Major, Minor or Info.
Reported
The reporting state:
False: the alarm will not be reported
True: the alarm will be reported
13.17.4 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 E1cLOS) 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.

Chapter 14 Resolving alarms and problems guide March 2007 • ADX-7077 2055-01, Issue 1

14 RESOLVING ALARMS AND PROBLEMS GUIDE
14.1 Introduction
This section describes the alarms which can be reported by the System, a description is
given of the alarm and some probable root causes. Alarms are split up into logical levels.
This section is intended for maintenance employees and network operators. This section
provides information to support in their tasks to resolve alarms or analyze end customer
complaints.
Current alarms are identified by the location, alarm type, severity and a time stamp of the
raise time.
14.2 Location
The location identifies the detection point. This can be:
System: A System related fault.
IFC: Related to the Interface Card, followed by a slot position.
SFP: Related to an SFP, in line port 1 (LP1) or line port 2 (LP2).
Line port: Line port 1 or 2.
VC4 termination point: Identified by related line port, LP1, LP2 or the active line
port (LPa) in case of MSP.
VC12 termination point: Identified by tributary slot number, followed by the port
number.
VC12 monitoring point: Identified by related line port, followed by klm indication.
AU alarm: identified by line port number, LP1, LP2 or the active line port (LPa) in
case of MSP.
TU alarm: identified by line port number, LP1, LP2 or the active line port (LPa) in
case of MSP, followed by the klm indication.

14.3 Alarm list overview

The table shows all defined alarm types and their default severity and default LED state.
Table 8. Alarm Types with Default Severity and LED Indication
Alarm type Default Severity Default LED state Default Reporting
AU4cAIS (see page 148) Minor None Yes
AU4cLOP (see page 148) Major Red Yes
E12cAIS (see page 146) Minor None Yes
E12cLOS (see page 146) Major Red Blinking Yes
IFCcEQF (see page 145) Major Red Yes
IFCcREPL (see page 145) Major Red Yes
IFCcUNP (see page 144) Major Red Yes
IFCcWUI (see page 144) Major Red Yes
MS1cAIS (see page 147) Minor None Yes
MS1cDEG (see page 147) Minor Yellow Yes
MS1cRDI (see page 147) Minor None Yes
MS1cSSF (see page 147) Major None Yes
MS1PcSSF (see page 147) Major None Yes
RS1cSSF (see page 147) Major None Yes
RS1cTIM (see page 147) Major Red Yes
SFPcEQF (see page 145) Major Red Yes
SFPcUNP (see page 145) Major Red Yes
SFPcWUI (see page 145) Major Red Yes
STM1cLOF (see page 146) Major Red Yes
STM1cLOS (see page 146) Major Red Blinking Yes
SYNCcBHO (see page 145) Major Red Yes
SYNCcLRR (see page 146) Major Red Yes
SYNCcTLF (see page 145) Major Red Yes
SYScEQF (see page 144) Major Red Yes
SYScPFA (see page 143) Major Red No
SYScPFB (see page 144) Major Red No
SYScROUTE (see page 144) Minor Yellow Yes
SYScTIME (see page 143) Major Red Yes
TU12cAIS (see page 149) Minor None Yes
TU12cLOP (see page 149) Major Red Yes
VC12cDEG (see page 150) Minor Yellow Yes
VC12cPLM (see page 149) Major Red Yes
VC12cRDI (see page 150) Major None Yes
VC12cSSF (see page 149) Major None Yes
VC12cTIM (see page 150) Major Red Yes
VC12cUNEQ (see page 149) Major Red Yes
VC4cDEG (see page 149) Minor Yellow Yes
VC4cLOM (see page 149) Major Red Yes
VC4cPLM (see page 148) Major Red Yes
VC4cRDI (see page 149) Minor None Yes
VC4cSSF (see page 148) Major None Yes
VC4cTIM (see page 148) Major Red Yes
VC4cUNEQ (see page 148) Major Red Yes
Alarm type
This is a short name (mnemonic) of the fault cause according to the ITU standards:
G.783, G.784 and G.806.

Severity
This identifies the provisioned severity for the alarm. The default severity (see "Alarm
profiles, severities, reporting and LEDs" on page 138) is listed by the descriptions.
Time stamp
The time stamp identifies the raise time of the alarm. This time is based on the System
time of the System (see page 20).
Reporting state
The default reporting state for all alarms is reported, except for the SYScPFA and
SYScPFB alarm. When an alarm is required not to be reported this can be provisioned
(see "Alarming" on page 135).
14.3.1 Monitoring mode

The monitoring mode of a port or termination point (see "Ports and termination points" on
page 99) controls the alarming. If the monitoring mode is monitored, alarms will be
reported on that point. If the state is not monitored, alarms will not be reported.
14.3.2 Pluggable item state

The pluggable items state affects the reporting of alarms. In the assigned state all alarms
are reported. In the AUTO state only the EQF and WUI alarms are reported (see
"Pluggable items" on page 88).
14.3.3 Replacing Systems

When a complete System needs to be replaced, the database of the previous System can
be used on the other System. In this way the System will be directly operational. But the
IP, OSPF and SNMP parameters need to be provisioned as they are not part of the
database.
14.4 Alarm descriptions

The alarm descriptions are shown as:
Alarm description.
Impact of the alarm.
Cause and action to clear the alarm.
14.4.1 System Alarms
SYScTIME
The System time is not set or lost. The System time is running from start up on the default
linux clock.
Alarms will be reported with a wrong timestamp, not the real time.
System time has not been provisioned. Or System time has been lost due to a power
outage longer than 10 minutes.
SYScPFA
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.
SYScPFB
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.
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 non-
redundant input and mixing PoE and telecom power feed is forbidden.
SYScEQF
An equipment failure has been detected on the System
The System has become unreliable
Replace the System, and return the failed System
SYScROUTE
There are more than 50 nodes in an OSPF AS.
Performance problems can occur.
Reduce the number of nodes in the OSPF AS (see page 31).
14.4.2 Pluggable items
IFCcUNP
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. (see page 89)
IFCcWUI
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
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 (see page 89). Take care cabling is according to this Interface
Card.
IFCcEQF
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
A SFP not present has been detected for the identified line port position.
Transmission to that line port will be lost.
Reinsert a correct SFP with the correct module qualifier (see page 90).
SFPcWUI
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 (see
page 92).
SFPcEQF
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.
14.4.3 Synchronization alarms
SYNCcBHO
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.
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
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, STM1cLOS, STM1cLOF, MS1cAIS
For tributary ports: E1cLOS or E1cAIS.
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 resolve that cause, or if
none timing source has been assigned to the identified timing source.
SYNCcLRR
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 a timing source must use an other timing reference.
The System timing QL is below the acceptance QL of the retimed E1 port. Check why
System timing QL has decreased.
14.4.4 Port alarms
E12cLOS
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
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
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
The identified line port has signal present but no correct STM-1 frame is detected
direction AIS is inserted. In the upstream direction (return path) MS RDI is inserted
Check signal provided to this line port. E.g. a STM4 signal might be provided or input
might be overloaded (to much optical power).

14.4.5 Termination point alarms
RS1cTIM
A trail trace identifier mismatch has been detected on the identified line port.
direction AIS is inserted. In the upstream direction (return path) MS 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
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.
Check the root cause of this RS1cSSF. Might be due to a STM1cLOS, or STM1cLOF.
MS1cSSF
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
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
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
A remote defect indication is detected on the identified line port.
At the far end system an MS failure is detected.
Check MS alarming on the far end system
MS1cDEG
The number of B2 background block errors detected on the identified line port does
exceed the provisioned degraded threshold (see "Degraded Threshold provisioning and
handling" on page 105).
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.
AU4cAIS
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
No valid AU4 pointer is present in the AU4 container.
Transmission in the downstream direction is lost.
An invalid AU4 signal is received.
VC4cSSF
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.
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
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
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.
Transmission is lost in the downstream direction, AIS 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
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.
Transmission is lost in the downstream direction, AIS 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 consequent
actions are executed.

VC4cDEG
The number of background block errors in the received B3 byte do 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
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 in stead of only TU12.
VC4cRDI
The VC4 remote defect indicator is detected in the received VC4.
Transmission might be affected at the far end side.
The far end systems has detected a downstream failure at VC4 level. Check alarming at
the far end system.
TU12cAIS
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
No TU12 pointer is detected in the TU12 identified. The TU12cLOP is identified by the
TU12 number (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
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
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
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.

inserted.
The VC12 coming from the far end system does not have a label 01 (equipped) or
asynchronous (02) but 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
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.
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
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
The VC12 remote defect indicator is detected in the received VC4.
Transmission might be affected at the far end side.
The far end systems has detected a downstream failure at VC12 level. Check alarming at
the far end system.
14.5 SDH overview
14.5.1 SDH multiplex structure

Figure 107. SDH Multiplexing Structure

14.5.2 SDH termination points

Figure 108. SDH Termination Points

SDH Events
Table 9. SDH Events
Physical / Regenerator Section (RS) Multiplex Section (MS)
LOS Loss Of Signal MS-AIS MS Alarm Indication Signal
LOF Loss Of Frame MS-BIP MS Bit Interleaved Parity error
RS-TIM RS Trace Identifier Mismatch MS-REI MS Remote Error Indication
RS-BIP RS Bit Interleaved Parity MS-RDI MS Remote Defect Indication
PHY Physical (sfp) los and clock K2 APS signaling byte
monitor
A1-2 Framing bytes B2 Error monitor
J0 Trace identifier M1 Backwards section status
B1 Error monitor H1-2 AU pointer
Higher order Path (HP) Lower order Path (LP)

AU-AIS AU Alarm Indication Signal TU-AIS TU Alarm indication signal
AU-LOP Loss Of AU Pointer TU-LOP Loss of TU pointer
HP-UNEQ HP Unequipped TU-LOM TU Loss of multi frame alignment
HP-TIM HP Trace Identifier Mismatch LP-UNEQ LP Unequipped
HP-BIP HP Bit Interleaved Parity error LP-TIM LP Trace identifier mismatch
HP-REI HP Remote Error Indication LP-BIP LP Bit Error Monitor
HP-RDI HP Remote Defect Indication LP-REI LP Remote Error Indication
HP-PLM HP Payload Label Mismatch LP-RDI LP Remote Defect Indication
C2 Signal label LP-PLM LP PayLoad Mismatch
J1 Trace identifier V5 Error monitor, signal label and backward
status
B3 Error monitor J2 Trace identifier
G1 Backward path status
H4 TU pointer

14.6 Synchronization Network

Figure 109. Example of a synchronization plan for a ring network with four Systems.

14.6.1 Provisioning for this network
General provisioning for this network:

System timing: QL enabled
System timing mode: Locked
All provisioned timing sources are not in lockout mode.
Provisioning System 1
Timing source 1: Assigned to TS1.8, QL provisioned SSU_T, priority 2
Timing source 2: Assigned to Line port 2, QL:AUTO, priority 3
Timing source 3: Assigned to Line port 1, QL: AUTO, priority 1
Timing source 1: Assigned to Line port 2, Q: AUTO, priority 1
Timing source 2: Assigned to Line port 1, QL: AUTO, priority 2.
Timing source 2: Assigned to Line port 1, QL: AUTO, priority 2.
Timing source 2: Assigned to Line port 1, Q: AUTO, priority 2.
Timing source 3: Assigned to Trib port TS8.2, QL provisioned PRC, priority 1
During normal operation the synchronization is as shown. The PRC clock on timing
source 3 on System4 has got the best quality:
System4 will select Timing source 3 (PRC is the best quality).
System3 will select Timing source 1 (LP2) as this one reference has the highest
priority.
System2 will select Timing source 1 (LP2) as this reference has the highest priority.
System1 will select Timing source 3 (LP1) as this reference has the highest priority.

14.6.1.1 Network failure 1
Interesting is to see what happens when a failure occurs. In the figure a failure on the
PRC clock is present. The Systems will switch over to their next best reference. At first
instance System4 falls back to holdover. Due to this System1 will switch over to Timing
source 1, the SSU_T reference on TS1.8. Next System4 will switch over to Timing source
1. System3 will retain at Timing source 1 and System2 will retain at Timing source 1.
Figure 110. Timing Network with Failure 1

14.6.1.2 Network failure 2
In the figure a failure has occurred on the incoming side of Line port 2 on System2. In this
case System2 will switch over from Timing source 1 to Timing source 2 (LP1). The other
Systems do not switch over.
Figure 111. Synchronization Failure

Chapter 15 List of acronyms and abbreviations March 2007 • ADX-7077 2055-01, Issue 1
15 LIST OF ACRONYMS AND ABBREVIATIONS

This section gives an overview and detailed description of acronym and abbreviations.
ALM
Alarm
AIS
Alarm Indication Signal
AS
Autonomous System
ASBR
Autonomous System Border Router
AU
Administrative Unit
AUG
Administrative Unit Group
BCG
Broadband Connection Group
CAS
Channel Associated Signaling
CI
Customer Interface
CO
Central Office
CRC
Cyclic Redundancy Code
CTP
Connection Termination Point
DHCP
Dynamic Host Configuration Protocol
DNU
Do Not Use
E1
2 Mb/s signal according to ITU-T G.703

EMC
Electro-Magnetic Compatibility
EN
Engineering Norms
ESD
Electro-Static Discharge
ETSI
European Telecommunication Standardization Institute
GND
Ground
HDB-3
High Density Binary 3 code
IDC
Insulation Displacement Connector
IEEE
The Institute of Electrical and Electronics Engineers
IFC
Interface Card
ISD
Image System Database
ITU-T
International Telecommunication Union – Technical standard group
LAN
Local Area Network
LED
Light Emitting Diode
LP
Line Port
LSA
Line Separator Adaptor
MAC
Media Access Control
MON
Monitor

MS
Multiplex Section
MSA
Multi-Source Agreement
MSP
Multiplex Section Protection
MTBF
Mean Time Between Failure
OSPF
Open Shorted Path First
PPM
Parts Per Million
PRC
Primary Reference Clock
RMA
Return Material Authorization
QL
Quality Level (timing quality)
RS
Regenerator Section
SDH
Synchronous Digital Hierarchy
SEC
SDH Equipment Clock
SELV
Safety Extra-Low Voltage
SFP
Small Form factor Pluggable
SNMP
Simple Network Management Protocol
SSM
Synchronization Status Message
SSU-L
Synchronization Supply Unit-Local

SSU-T
Synchronization Supply Unit-Transit
STM-1
Synchronous Transport Module -1
TIM
Trail trace Identifier Mismatch
TP
Tributary Port
TS
Tributary Slot
TSL
Trail Signal Label
TTI
Trail Trace Identifier
TTP
Tail Termination Point
TU
Tributary Unit
TUG
Tributary Unit Group
VC-n
Virtual Container of nth level
WTR
Wait To Restore

Chapter 16 Index March 2007 • ADX-7077 2055-01, Issue 1
Blank Face plate installation • 57

16 INDEX C
Cables and pinning • 66, 68
A CAS • 157
ABOUT THIS MANUAL • 9 CI • 157
Access to related items • 77 Clickable items via System layout • 77
Accessories • 49, 63 CO • 157
Active leg • 118 Connect Power, SFPs and fibers or
Adding cross connects • 113 coax • 62
Address resolution protocol (ARP) • 32 Connecting 2 Mb/s (E1) Interfaces •
ADX100 • 25 54, 56
ADX100 for LSA-PLUS PROFIL rod Connecting interfaces • 54, 56, 59, 62,
mounting • 51 66
ADX100 GUI System Overview • 80 Connecting power • 66
ADX100 Interfaces • 23 Connection • 87
ADX100 Login screen • 79 Connectors • 71
ADX100 with 2 Mb/s E1 connections • Consequent action • 87
52 CRC • 157
ADX100 without Interface Cards • 56 Creating an MSP pair • 119
ADX100, ADX200 and ADX201 Cross connects • 22, 109
differences • 87 CTP • 157
ADX200 • 26, 62 Current alarm list with SNMP • 132
ADX200 GUI System overview • 81 Current Alarms • 136
ADX200 Interfaces • 23 Customer information and assistance •
ADX200 Login screen • 81 12
ADX201 • 27, 63 D
ADX201 GUI System overview • 77,
82 Database maintenance • 97
ADX201 Interfaces • 24 DC power cable • 68
ADX201 Login screen • 82 Definitions • 109, 118, 123
AIS • 157 Degraded • 118
Alarm descriptions • 143 Degraded Threshold provisioning and
Alarm list overview • 96, 142 handling • 45, 102, 103, 105, 116,
Alarm profiles, severities, reporting 117, 118, 147
and LEDs • 138, 143 Deleting an MSP pair • 120
Alarm reporting • 22 Description of the interfaces • 23
Alarm type • 142 Designated router and the backup
Alarming • 135, 143 designated router • 32, 134
Alarms menu • 84 DHCP • 157
ALM • 157 Dimensions and weight • 25
Area Border Router (ABR) • 31, 132 Disclaimer of liability • 2
AS • 157 Displaying provisioned alarm severities
ASBR • 157 and reporting states • 138
Assigning IP addresses for system DNU • 157
management • 33 Documentation conventions • 9
AU • 157 Downstream • 87
AU4cAIS • 142, 148
AU4cLOP • 142, 148 E
AUG • 157 E1 • 157
Autonomous System Border Router E1 incoming loopback • 47
(ASBR) • 31, 32, 133 E1 interfaces • 24
Availability • 28 E1 outgoing loopback • 48
Avoiding management problems with E1 retiming • 21
proxy ARP • 43 E12cAIS • 142, 146
E12cLOS • 142, 146
B Editing cross connects • 115
BCG • 157 Egress • 87
Bidirectional cross connects • 113 EMC • 158

EN • 158 Introduction • 45, 87, 141

Environmental • 15, 27 Inventory management • 21
Environmental precautions • 18 IP address management • 72, 84
ESD • 158 IP management without DHCP server •
ESD and EMC • 15 72
ETSI • 158 ISD • 158
ETSI COMPLIANCE STATEMENTS ITU-T • 158
• 15
Example with ASBR • 41, 42 K
Example with proxy ARP • 42 Key features • 19
Exchange ADX100 Main Module • 58
External MSP switch requests • 121 L
External switch requests • 118, 121
LAN • 158
F LAN - Power over Ethernet cable • 68
LAN connector • 71, 72
Far end • 87 LAN port provisioning via WEB
Feature descriptions • 19 browser • 74, 134
Field colors convention • 77 LAN provisioning via Ip2Box • 75
LED • 158
G
LED indicators • 138, 139
GENERAL INFORMATION • 11 Line ports • 99
General notices • 49 Line Protection (MSP) • 21
GENERAL SAFETY PRECAUTIONS Line protection and OSPF • 33
• 17 Link costs and signal rate • 33, 133,
GND • 158 134
GUI features • 77 LIST OF ACRONYMS AND
GUI settings • 77 ABBREVIATIONS • 157
GUI Settings and system authorization Listing, editing and deleting cross
• 84 connects • 111
GUI SETTINGS AND SYSTEM Local Management console port • 71
AUTHORIZATION • 77 Local management, host directly
connected to System LAN and no
H routing protocol • 35
Hardware specifications • 25 Location • 141
HDB-3 • 158 Log file • 20
Help menu • 85 Log file for System settings • 83
History alarms • 137 Loopback • 22
HiThere utility • 74 LP • 158
LSA • 158
I
M
IDC • 158
IEEE • 158 MAC • 158
IFC • 158 Maintenance menu • 84
IFC replacement. • 90 MANAGEMENT AND REMOTE
IFCcEQF • 142, 145 MANAGEMENT • 31
IFCcREPL • 142, 145 Mapping • 28
IFCcUNP • 142, 144 Mechanical precautions • 18
IFCcWUI • 142, 144 Menu structure • 84
Ingress • 87 MON • 158
Inserting interface cards • 66 Monitoring mode • 143
Inserting SFPs • 66 Most recent alarm bar • 135, 137
Install ADX100 Main Module • 60 Mount Frame • 61
Install Interface Cards • 62 Mounting and installation ADX100 •
Installation guide • 18, 72 25, 51
INSTALLATION GUIDE • 49 Mounting instructions ADX200 and
Interface Card • 89, 144, 145 ADX201 • 62
Interface Card installation • 56, 62 Mounting material 200 (included in
Interface Cards • 71 box) • 62
Interfaces • 28

Mounting material ADX201 (included Protection • 118

in box) • 63 Provisioning • 19, 31, 80, 84
Mounting the ADX200/ADX201 • 63 PROVISIONING • 87
Mounting to profile rods • 53, 56 Provisioning aspects • 46
MS • 159 Provisioning for this network • 154
MS1cAIS • 142, 147 Provisioning IP address with DHCP
MS1cDEG • 142, 147 client • 73
MS1cRDI • 142, 147 Provisioning line port references • 125,
MS1cSSF • 142, 147 127
MS1PcSSF • 142, 147 Provisioning timing sources • 122, 124
MSA • 159 Provisioning trail trace identifiers • 107
MSP • 159 Provisioning tributary port references •
MSP and alarming • 119 126
MSP details • 120 Provisioning via local console port •
MSP menu • 85 73, 74
MTBF • 159
Multiple hosts and mix applications • Q
40 QL • 159
QL timing source • 124
N
QL-in • 123
Near end • 87 Quality Level (QL) • 123
Network failure 1 • 155
Network failure 2 • 156 R
Non intrusive monitoring (NIM) of line Real Time Clock • 20, 132, 136, 137,
ports • 46 143
Non-revertive • 118 Reference Fail • 123
Refresh button • 77
O
Remote error indication • 109
Open shortest path first (OSPF) • 31, Remote management • 22
144 Remote management examples • 37
OSPF • 159 Remove and Insert label holders
OSPF Interfaces • 133 ADX100 • 55, 56
OSPF LAN/LP Interfaces • 134 Removing interface cards • 67
OSPF provisioning • 132 Removing the frame • 59
OSPF settings • 132 Repair / exchange policy • 11
OSPF Systems • 135 Repair charges • 11
Outgoing SSM • 124 Replacement / spare products • 12
Overhead functions • 22 Replacing Systems • 143
Reporting mode • 138
P Reporting state • 143
Path protection • 22 Resolving alarms and problems guide •
Pluggable item state • 143 9, 102, 103, 105, 137
Pluggable items • 21, 71, 89, 143, 144 RESOLVING ALARMS AND
Port alarms • 146 PROBLEMS GUIDE • 141
Port loopback functionality • 101 Restart of browser after System
PORT LOOPBACK recovery • 78
FUNCTIONALITY • 47 Retiming E1 ports • 101, 128, 129
Ports • 99 Returned material • 12
Ports and termination points • 99, 110, Revertive • 118
143 Revision History • 2
Post • 13 RMA • 159
Power • 28 Rod and rack specifications • 52, 56
Power precautions • 17 Routers for OSPF • 31
Powering • 20, 72 Routing examples • 35
PPM • 159 RS • 159
PRC • 159 RS and MS section • 101
Precautions • 117 RS1cSSF • 142, 147
Product information and technical RS1cTIM • 142, 147
assistance by e-mail • 14

Synchronization Network • 123, 153

S SYScEQF • 142, 144
Safety • 15 SYScPFA • 142, 143
Safety precautions • 17 SYScPFB • 142, 144
Safety warnings • 9 SYScROUTE • 31, 142, 144
SDH • 159 SYScTIME • 88, 142, 143
SDH Events • 152 System Alarms • 143
SDH multiplex structure • 110, 150 System and host connected to an access
SDH overview • 150 network • 35
SDH termination points • 111, 151 System and host in the same subnet •
SEC • 159 35
Select inactive ISD • 94 System database • 20, 96
SELV • 159 SYSTEM DESCRIPTION • 19
Serial / Console cable • 68 System menu • 84
Set up of the System • 80, 81, 82 System overview and features • 19
SET UP OF THE SYSTEM • 71 System recovery • 93
Severities and reporting • 138 System software • 9, 20, 93
Severity • 143 System time • 88
SFP • 159 System timing • 127, 128
SFP modules • 71 System timing reference selection •
SFP replacement and acceptance • 92, 126, 128
145
T
SFPcEQF • 142, 145
SFPcUNP • 142, 145 Telecom power feed • 71
SFPcWUI • 142, 145 Telephone • 12
Short ordering list • 22, 29, 90 Terminal application and host
Signal fail • 118 connected to LAN • 37
Simultaneous sessions • 77 Termination point alarms • 147
Single and Dual fiber SFPs • 22 Termination Points • 101, 108
Single Fiber SFPs • 92 Test access output • 71, 81, 82, 108,
Small Form Pluggable • 91, 145 111
Smart defaults • 99 Test access port • 21
Smart selection • 77 Test connector • 66
SNCP Cross connects uni- and The proxy address resolution protocol
bidirectional • 46, 109, 113, 114, 116 (PARP) • 32
SNMP • 22, 131, 159 TIM • 160
Software service agreement • 11 Time stamp • 143
SPECIFICATIONS • 25 Timing menu • 85
SSM • 159 Timing source • 123
SSM based algorithm • 128, 129 To become an ASBR • 32
SSM byte • 123 Tools • 49
SSU-L • 159 TP • 160
SSU-T • 160 Trademark Information • 2
Standby leg • 118 Trail Trace Identifier modes • 106, 116
STM-1 • 160 Trail Trace Identifier provisioning and
STM-1 outgoing loopback • 48 handling • 102, 103, 104, 106
STM1cLOF • 142, 146 Transimission menu • 85
STM1cLOS • 142, 146 Transmission protection MSP • 103,
Subnetwork connection protection 117
(SNCP) • 115 Transmission terms and definitions •
SUBNETWORK CONNECTION 87
PROTECTION (SNCP) • 45 Tributary Ports • 47, 100, 113
Supported areas • 31 Tributary slots • 21
Switch criteria • 118 TS • 160
SYNCcBHO • 142, 145 TSL • 160
SYNCcLRR • 142, 146 TTI • 160
SYNCcTLF • 142, 146 TTP • 160
Synchronization • 21, 28, 88, 100, 122 TU • 160
Synchronization alarms • 145 TU12cAIS • 142, 149

TU12cLOP • 142, 149

TUG • 160
U
Unidirectional • 118
Unidirectional cross connects • 113,
114
Unnumbered network • 32
Update after edit • 77
Upstream • 87
Use of wiring brackets • 64
User administration • 20
User groups, login and rights • 78
V
VC12 termination point • 101, 104, 116
VC12cDEG • 142, 150
VC12cPLM • 142, 149
VC12cRDI • 142, 150
VC12cSSF • 142, 149
VC12cTIM • 142, 150
VC12cUNEQ • 142, 149
VC4 termination points • 101, 102
VC4cDEG • 142, 149
VC4cLOM • 142, 149
VC4cPLM • 142, 148
VC4cRDI • 142, 149
VC4cSSF • 142, 148
VC4cTIM • 142, 148
VC4cUNEQ • 142, 148
VC-n • 160
Visual indicators • 21
W
Wait to Restore (WTR) • 118
Warranty / software • 11
Web browser and navigation • 77
Web server • 22
Wire routing • 65
Worker • 118
WTR • 160
X
XConnects menu • 85


User Manual (ADX)

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

User Manual (ADX)

Transféré par

Droits d'auteur :

Formats disponibles

User Guide

ADX100, ADX200, ADX201

ADC Telecommunications, Inc.

2 © ADC Telecommunications, Inc.

1 About this manual 9

3 ETSI Compliance statements 15

4 General safety precautions 17

© ADC Telecommunications, Inc. 3

5.2.20 Single and Dual fiber SFPs 22

7 Management and remote management 31

4 © ADC Telecommunications, Inc.

8 Subnetwork connection protection (SNCP) 45

9 Port loopback functionality 47

11 Set up of the System 71

12 GUI Settings and system authorization 77

© ADC Telecommunications, Inc. 5

12.5 Log file for System settings 83

6 © ADC Telecommunications, Inc.

14 Resolving alarms and problems guide 141

15 List of acronyms and abbreviations 157

© ADC Telecommunications, Inc. 7

8 © ADC Telecommunications, Inc.

1 ABOUT THIS MANUAL

1.1 Safety warnings

Note: Important information.

1.2 Documentation conventions

© ADC Telecommunications, Inc. 9

10 © ADC Telecommunications, Inc.

2.1 Warranty / software

2.2 Software service agreement

2.3 Repair / exchange policy

2.4 Repair charges

© ADC Telecommunications, Inc. 11

2.5 Replacement / spare products

2.6 Returned material

2.7 Customer information and assistance

Europe toll free numbers

12 © ADC Telecommunications, Inc.

USA and Canada

© ADC Telecommunications, Inc. 13

2.7.3 Product information and technical assistance by e-mail

14 © ADC Telecommunications, Inc.

3 ETSI COMPLIANCE STATEMENTS

3.2 ESD and EMC

© ADC Telecommunications, Inc. 15

16 © ADC Telecommunications, Inc.

4 GENERAL SAFETY PRECAUTIONS

4.1 Safety precautions

Caution: This system is intended for installation in restricted areas. A restricted

4.2 Power precautions

Caution: This product must be connected to an IEC60950 compliant limited power

Caution: Remove power before connecting or disconnecting ground or power wires

© ADC Telecommunications, Inc. 17

Caution: The system needs to be grounded during operation.

4.3 Environmental precautions

4.4 Mechanical precautions

18 © ADC Telecommunications, Inc.

5.1 System overview and features

5.1.1 Key features

5.2 Feature descriptions

© ADC Telecommunications, Inc. 19

5.2.1 System software