user manual adx

8/21/2019 User Manual Adx

http://slidepdf.com/reader/full/user-manual-adx 1/200

User Guide

ADX100, ADX200, ADX201 ADX-7077 2055-01, Issue 2.1

June 2009

ADC Telecommunications, Inc.



2 © ADC Telecommunications, Inc.

Copyright

Copyright © 2007 ADC Telecommunications, Inc. All rights reserved

The software contains proprietary information of ADC. It is provided under a licenseagreement 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. Theinformation and intellectual property contained herein is confidential between ADC andthe client and remains the exclusive property of ADC. If you find any problems in thedocumentation, please report them to us in writing. ADC does not warrant that thisdocument is error-free.

No part of this publication may be reproduced, stored in a retrieval system, or transmittedin any form or by any means, electronic, mechanical, photocopying, recording orotherwise without the prior written permission of ADC.

Revision History

Current Issue: Issue 2.1

Date: 2009, June

Reason for change: Issued for release 2.0.2 of Systems.

Previous

Issue: Issue 2

Date: 2009, January

Reason for change: Issued for release 2.0.0 of Systems

Trademark Information

ADC and ADC Telecommunications are registered trademarks of ADCTelecommunications, Inc.

Disclaimer of li ability

Contents herein are current as of the date of publication. ADC reserves the right tochange 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 allproducts, publications and services during and after the warranty period.

This publication may be verified at any time by contacting ADC’s Technical AssistanceCentre.

This publication may be verified at any time by contacting ADC’sTechnical Assistance Center at 1-800-366-3891, extension 73475 (inU.S.A. or Canada) or 952-917-3475 (outside U.S.A. and Canada), or bye-mail to [email protected] (mailto:[email protected]).



© ADC Telecommunications, Inc. 3

June 2009 • ADX-7077 2055-01, Issue 2.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 11 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 20 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 21 5.2.6 Powering 21 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 22 5.2.14 E1 retiming 22 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




ADX-7077 2055-01, Issue 2.1 • June 2009

5.2.20 Single and Dual fiber SFPs 22 5.2.21 Path protection 23 5.2.22 Loopback 23 5.2.23 Remote management 23 5.2.24 Performance monitoring 23 5.2.25 Digital inputs 23

5.2.26 FTP 23 5.2.27 Distribution of manual routes 23 5.3 Description of the interfaces 24 5.3.1 ADX100 Interfaces 24 5.3.2 ADX200 Interfaces 24 5.3.3 ADX201 Interfaces 25 5.3.4 E1 interfaces 25

6 Specifications 27

6.1 Hardware specifications 27 6.2 Dimensions and weight 28 6.2.1 ADX100 28 6.2.2 ADX200 29 6.2.3 ADX201 29 6.3 Environmental 30 6.4 Availability 30 6.5 Power 30 6.6 Interfaces 30 6.7 Synchronization 31 6.8 Mapping 31 6.9 Short ordering list 32

7 Management and remote management 33

7.1 Open shortest path first (OSPF) 33 7.2 Supported areas 33

7.3 Routers for OSPF 33 7.3.1 Area Border Router (ABR) 33 7.3.2 Autonomous System Border Router (ASBR) 34 7.3.3 Designated router and the backup designated router 34 7.3.4 Numbered and unnumbered interfaces 34 7.4 Address resolution protocol (ARP) 34 7.5 The proxy address resolution protocol (PARP) 34 7.6 Link costs and signal rate 35 7.7 Line protection and OSPF 35 7.8 Assigning IP addresses for system management 35 7.9 Routing examples 36 7.9.1 Local management, host directly connected to System LAN and no routing protocol 36 7.10 Remote management examples 38 7.10.1 Terminal application and host connected to LAN 38 7.10.2 Multiple hosts and mix applications 41 7.10.3 Example with ASBR 42 7.10.4 Example with proxy ARP 43




June 2009 • ADX-7077 2055-01, Issue 2.1

8 Subnetwork connection protection (SNCP) 45

8.1 Introduction 45 8.2 Provisioning aspects 46

9 Port loopback functionality 47

9.1 E1 incoming loopback 48 9.2 E1 outgoing loopback 48 9.3 STM-1 outgoing loopback 48

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 61 10.6.1 ADX200 61 10.6.2 Mounting material 200 (included in box) 62 10.6.3 ADX201 62 10.6.4 Mounting material ADX201 (included in box) 62 10.6.5 Mounting the ADX200/ADX201 62 10.7 Cables and pinning 67 10.7.1 DC power cable 67 10.7.2 LAN - Power over Ethernet cable 67 10.7.3 Serial / Console cable 68 10.7.4 Digital inputs 69

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.4 Port provisioning 74

11.4.1 Line ports 74 11.4.2 LAN ports 75

12 GUI Settings and system author ization 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.3 ADX200 Login screen 81 12.4.4 ADX200 GUI System overview 81 12.4.5 ADX201 Login screen 82 12.4.6 ADX201 GUI System overview 82




ADX-7077 2055-01, Issue 2.1 • June 2009

12.5 Log file for System settings 83 12.6 Menu structure 83

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 88 13.4 System Time 89 13.4.1 System time manually 89 13.4.2 System time from server(s) 89 13.5 Pluggable items 90 13.5.1 Interface Card 91 13.5.2 IFC replacement. 92 13.5.3 Small Form Pluggable 93 13.5.4 SFP replacement and acceptance 94 13.5.5 Single Fiber SFPs 94 13.6 System recovery 94 13.7 System software 95 13.7.1 Select inactive ISD 96 13.7.2 Install software manually 97 13.7.3 Install software via FTP 98 13.8 System database 99 13.8.1 Database maintenance manually 101 13.8.2 Smart defaults 102 13.8.3 Database backup via FTP 103 13.8.4 Database restore via FTP 105 13.9 Log files 106 13.9.1 Log files manually 106 13.9.2 Log files via FTP 107 13.10 Ports and termination points 108 13.10.1 Ports 108 13.10.2 Line ports 109

13.10.3 Tributary Ports 109 13.10.4 Termination Points 110 13.10.5 Degraded Threshold provisioning and handling 115 13.10.6 Trail Trace Identifier provisioning and handling 116 13.10.7 Provisioning trail trace identifiers 116 13.10.8 Test access output 118 13.10.9 Remote error indication 119 13.11 Cross connects 119 13.11.1 Definitions 120 13.11.2 Listing, editing and deleting cross connects 122 13.11.3 Adding cross connects 123 13.12 Transmission protection MSP 127 13.12.1 Precautions 127 13.12.2 Definitions 128

13.12.3 Creating an MSP pair 129 13.12.4 Deleting an MSP pair 130 13.12.5 MSP details 130 13.12.6 External MSP switch requests 132 13.13 Synchronization 133 13.13.1 Definitions 134 13.13.2 Provisioning timing sources 135 13.13.3 Provisioning line port references 136 13.13.4 Provisioning tributary port references 138 13.13.5 System timing 138 13.13.6 System timing reference selection 140 13.13.7 Retiming E1 ports 140 13.14 SNMP 142 13.14.1 Current alarm list with SNMP 143 13.15 Performance monitoring 144 13.15.1 PM overview 144 13.15.2 Add/Delete PM points 145




June 2009 • ADX-7077 2055-01, Issue 2.1

13.15.3 PM Threshold 145 13.15.4 PM Current Data View/Reset/Refresh 146 13.15.5 PM History data View 147 13.15.6 PM UAP Log 147 13.16 OSPF provisioning 148 13.16.1 OSPF settings 148

13.16.2 OSPF Interfaces 149 13.16.3 OSPF Systems 151 13.16.4 Manual route add/delete 151 13.17 Digital inputs 153 13.18 Alarming 154 13.18.1 Most recent alarm bar 154 13.19 Current Alarms 155 13.20 History alarms 156 13.21 Alarm profiles, severities, reporting and LEDs 157 13.21.1 Severities and reporting 157 13.21.2 Displaying provisioned alarm severities and reporting states 157 13.21.3 Reporting mode 157 13.21.4 LED indicators 158

14 System reset 159

15 Resolving alarms and prob lems guide 161

15.1 Introduction 161 15.2 Location 161 15.3 Alarm list overview 161 15.3.1 Alarm type 162 15.3.2 Severity 162 15.3.3 Time stamp 163 15.3.4 Reporting state 163 15.3.5 Monitoring mode 163

15.3.6 Pluggable item state 163 15.3.7 Replacing Systems 163 15.4 Alarm descriptions 163 15.4.1 System Alarms 163 15.4.2 Pluggable items 164 15.4.3 Synchronization alarms 165 15.4.4 Port alarms 166 15.4.5 Termination point alarms 167 15.4.6 Performance monitoring alarms 170 15.4.7 Digital input alarms 171 15.5 SDH overview 171 15.5.1 SDH multiplex structure 171 15.5.2 SDH termination points 172 15.6 Synchronization Network 174 15.6.1 Provisioning for this network 175

16 Support Tools 179

16.1 HiThere 179 16.1.1 Starting HiThere for the first time 179 16.1.2 HiThere menu structure 180 16.1.3 Find systems on a local subnet 181 16.1.4 Find and add SNMP systems for alarm monitoring 184 16.1.5 Alarm management of monitored and non monitored Systems 185 16.1.6 SNMP trap log 187




ADX-7077 2055-01, Issue 2.1 • June 2009

17 List of acronyms and abbreviations 189

18 Index 195




Chapter 1 About this manual June 2009 • ADX-7077 2055-01, Issue 2.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 2.0.2 (see

"System software" on page 95).

This user manual is written for end users responsible for installation, networkmanagement and maintenance. It deals with installation, first set up, full provisioning andmanagement of the System and contains a guide to alarms (see "Resolving alarms andproblems guide" on page 161). This manual is in most cases common for all products, ADX100, ADX200 and ADX201. In those cases where differences exist they will beoutlined. General information will be referred to as System, instead of ADX100, ADX200and 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. Theadmonishments — in the form of a Note, Caution and Danger — must be followed at alltimes. These warnings are flagged by use of the triangular alert icon and are listed inorder of severity of injury or damage and likelihood of occurrence.

Note: Important information.

Caution: Caution indicates a potentially hazardous situation which, if not avoided,can lead to injury, serious damage to the appliance, or both.

Danger: Danger indicates a potentially hazardous situation which, if not avoided,can lead to death, serious injury as well as serious damage to the appliance.

1.2 Documentation conventions

References to screen dumps o f the sof tware:

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 .

In this manual screen dumps are used to explain functionality and provisioning.Some screen dumps in this manual may refer to former software releases. If nofunctional changes were made for such a screen dump the information in thisparticular screen dump is still valid.




Chapter 1 About this manual June 2009 • ADX-7077 2055-01, Issue 2.1




Chapter 2 General information June 2009 • ADX-7077 2055-01, Issue 2.1

2 GENERAL INFORMATION

2.1 Warranty / software

The Product and Software warranty policy and warranty period for all ADC proaducts ispublished in ADC’s Warranty/Software Handbook. Contact the Broadband ConnectionsGroup (BCG) Technical Assistance Center at 1-800-366-3891, extension 73475 (inU.S.A. or Canada) or 952-917-3475 (outside U.S.A. and Canada) for warranty or softwareinformation 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 (inU.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. Anyattempt to repair or modify ADC Products without authorization from ADC voids thewarranty.

If a malfunction cannot be resolved by the normal troubleshooting procedures contactBCG Technical Assistance Center at 1-800-366-3891, extension 73475 (in U.S.A. orCanada) or 952-917-3475 (outside U.S.A. and Canada). A telephone consultation cansometimes 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, ADCwill 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 canarrange to ship the replacement Product immediately. In all cases, the defective Productmust 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 applicablewarranty period has not expired, the Buyer’s only payment obligation is to pay theshipping cost to return the defective Product. ADC will repair or replace the Product at nocharge and pay the return shipping charges.

Otherwise, ADC will charge a percentage of the current Customer Product price for therepair or NTF (No Trouble Found). If an advance replacement is requested, the full priceof a new unit will be charged initially. Upon receipt of the defective Product, ADC willcredit 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 replacementcredit. If repairs necessitate a visit by an ADC representative, ADC will charge the currentprice of a field visit plus round trip transportation charges from Minneapolis to the Buyer’ssite.

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 (inU.S.A. or Canada) or 952-917-3748 (outside U.S.A. and Canada) to obtain a ReturnMaterial Authorization number prior to returning an ADC Product.

All returned Products must have a Return Material Authorization (RMA) number clearlymarked on the outside of the package. The Return Material Authorization number is validfor 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 / Pacif ic

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

[email protected]

[email protected]

[email protected]

[email protected]




Chapter 3 ETSI Compliance statements June 2009 • ADX-7077 2055-01, Issue 2.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 insertedThermal safety: Surface temperature or exposed component below 75 0C




Chapter 3 ETSI Compliance statements June 2009 • ADX-7077 2055-01, Issue 2.1




Chapter 4 General safety precautions June 2009 • ADX-7077 2055-01, Issue 2.1

4 GENERAL SAFETY PRECAUTIONS

4.1 Safety precautions

Caution: Read the installation section before you connect the system to the powersource.

Caution: This system is intended for installation in restricted areas. A restrictedarea is where access can only be gained by service employees through the use of aspecific tool, lock and key, or other means of security, and is controlled by the authorityresponsible for the location.

Caution: Only trained and qualified employees are allowed to install or replace theSystems.

Caution: All ports are safety extra-low voltage (SELV) circuits. SELV circuitsshould only be connected to other SELV circuits.

4.2 Power precautions

Caution: Only a DC power source that is isolated from AC mains with reinforcedinsulation and that complies with the SELV requirements can be connected to thesystem.

Caution: This product must be connected to an IEC60950 compliant limited powersource OR a Power over Ethernet (PoE) IEEE802.3af compliant power source.

Caution: This product relies on the buildings installation for short-circuit (overcurrent) 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 wiresto the system.To ensure that all power is OFF, locate the circuit breaker on the panel board thatservices the DC circuit, switch the circuit breaker to the OFF position, and tap the switchhandle of the circuit breaker in the OFF position.




Chapter 4 General safety precautions June 2009 • ADX-7077 2055-01, Issue 2.1

Caution: Wire the DC power supply using the appropriate connectors at the wiringend (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 alwaysbe 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 periodsof lightning activity.

4.4 Mechanical precautions

Caution: The blank face plates prevent vermin and dust to enter the system as wellas exposure to electromagnetic interference.




Chapter 5 System description June 2009 • ADX-7077 2055-01, Issue 2.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 inthe central office. It offers a distribution function which is fed with two STM-1 aggregatesignals via fiber or coax. The E1 payload channels can be fully flexible cross connectedtowards any E1 port, for example terminated with an LSA-PLUS connector. The Systemsupports E1 unframed transmission, and is transparent for framed E1 signals.

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

Command logging

Flexible username and password provisioning

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 SystemLine protection (MSP)

Two STM-1 aggregate signals (optical and/or electrical)

Dual and single fiber interworking

Degraded signal reporting and provisionable thresholds

Synchronization, free running or selectable reference

E1 retiming outputs

Database back-up and restore via FTP

Download new version of system software using FTP

Provisioning and retrieval of all managed objects via an SNMP manager

Performance monitoring via an SNMP manager

IP manual route provisioning including support of unnumbered interfaces

Support of NTP client

Non-intrusively performance monitoring on any 2 Mbit/s signal in PDH to SDHdirection.

Performance monitoring on E1 termination points.

Cold and warm System reset.

8 slot positions for Interface Cards on the ADX100 and ADX201, 4 slot positions onthe ADX200





Four independent digital input signals.

8 times 2.048 Mb/s according to G.703 interface per Interface Card

Simple and rapid installation

Database backup and restoreSmart 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 87).

5.2.1 System software

The System software supports all System products. The System has two memory bankscontaining the active and possibly an inactive software version. The software is stored innon volatile (flash) memory.

Remote and local software uploads are supported. Software upgrades are non serviceaffecting. They also do not affect data communication settings.

The System supports installing of new software via FTP.

5.2.2 System database

The System database contains all provisioned settings of the System except for theIP/OSPF and SNMP related settings. The System supports 8 databases of which one isactive. Databases are reusable between Systems of the same hardware version. Forexample between one ADX100 and another ADX100.

At first start up the System has a default database in which no cross connects and othertransmission related settings are provisioned.

A database operation does not have impact on the data communication settings.

5.2.3 User administ ration

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 relatedoperations.

admin: Members of the admin group are responsible for maintenance activities likesoftware upgrading, database operations, user group administration and IP andSNMP settings. The privileges of the members of the admin group also include theprivileges 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 systemsettings are changed. Per event the log file includes a time stamp, a user identificationand a descriptive text.





5.2.5 Real Time Clock

The System has an accurate Real Time Clock on board. The time of this clock can bet setby the user or by enabling NTP 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 GUIalarm 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 asredundant 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 PoEis not monitored.

5.2.7 Test access port

Both the ADX200 and ADX201 have a dedicated test access output. This output providesan E1 signal which can be measured with an analyzer. Every connection can be directedto 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 ispowered on. The yellow and red LEDs indicate the kind of current alarms. The LAN porthas 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 modulecan be retrieved.

5.2.10 Tributary slots

The ADX100 and ADX201 have 8 tributary slot positions. The ADX200 has 4 slotpositions. 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-1electrical. The SFPs are hot pluggable and will be AUTO discovered by the System.

The System has 8 Interface Slots for 8 hot pluggable Interface Cards. The InterfaceCards are automatically detected by the System. The Interface Cards contain 8 tributaryports.

5.2.12 Line Protect ion (MSP)

The System supports MSP line port protection; this enables restoration of traffic when afailure has been detected on one of the line sections including SFP failures.Unidirectional and bidirectional MSP for both revertive and non-revertive operation issupported.





5.2.13 Synchronization

The System can be synchronized externally via each of the line ports and one of the E1tributary 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 itsholdover clock.

5.2.14 E1 retiming

Every E1 port individually can be provisioned in retiming mode. In this mode the outgoingE1 signal will be retimed with the System clock. In this way the E1 signal can be used astiming reference for another System connected to this System.

5.2.15 Alarm repor ting

The System supports the alarm reporting of current and history alarms. They will bereported 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 (history)alarms. For every alarm the severity and reporting state can be provisioned. Every portand 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 lineand line ports and between tributary and tributary ports. Both uni- and bidirectional crossconnects 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 beviewed 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 isneeded. Only a web browser is needed. Via this web browser the System can bemanaged.

5.2.19 SNMPFive different SNMP managers can be added. Both SNMPv1 and SNMPv2 are available.System specific MIB files are supported.

The System is fully SNMP manageable. All settings that can be done using a webbrowser can also be done using SNMP (except the settings of the SNMP screen itself).

5.2.20 Single and Dual fi ber SFPs

The System supports both single and dual fiber small form-factor pluggables, SFPs (see"Short ordering list" on page 32). 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 embeddedcommunication channel (MS-DCC) or via the regenerator section embedded

communication channel (RS-DCC).

5.2.24 Performance monitoring

The System supports non-intrusive performance monitoring on any 2 Mbit/s signalingPDH to SDH direction at the 2 Mbit/s system interface. The System supports performancemonitoring on 64 monitoring points simultaneously. The monitoring is ITU G.821/826compliant.

5.2.25 Digital inputs

The ADX200 and ADX201 both support three floating inputs (DI1, DI2 and DI3) and one

non-floating input (DI4).The ADX100 does not support these inputs.

5.2.26 FTP

The System supports ISD install, database backup, database restore, and log backupusing FTP. The ISD, database and log files are downloaded from or uploaded to a remoteFTP server.

All FTP transfers are done using passive mode.

5.2.27 Distribution of manual routes

The user can add routes to destinations that are outside of the router's OSPF area. Theroutes thus added can be advertised by OSPF into the router's OSPF domain.





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 port3. 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 port3. 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 June 2009 • ADX-7077 2055-01, Issue 2.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 E1ports can be inserted. The ADX100 should be installed on 95mm ADC PROFIL rodmounting frames (see "Mounting and installation ADX100" on page 51).

1 RU height, 32*E1 & test access output, 4 digital inputs. The ADX200 is suited for19 inch rack mounting, 1 RU height and can have up to 32 E1 2Mb/s interfaces using4 Interface Cards.

2 RU height, 64*E1 & test access output, 4 digital inputs. The ADX201 is suited for19 inch rack mounting, 2 RU height, and can have up to 64 E1 2Mb/s interfacesusing 8 Interface Cards.





6.2 Dimensions and weight

6.2.1 ADX100

PROFIL version with the ADX100 main module, in which 8 interface cards with 8 E1 portscan be inserted. The ADX100 should be installed on 95mm ADC PROFIL rod mountingframes (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

1 RU height, 32*E1 & test access output, 4 digital inputs. The ADX200 is suited for 19inch rack mounting, 1 RU height and can have up to 32 E1 2Mb/s interfaces using 4Interface Cards.

Dimensions: 44 x 450 x 171 mm (HxWxD)

Weight: 2 kg (with interface cards)



6.2.3 ADX201

2 RU height, 64*E1 & test access output, 4 digital inputs. The ADX201 is suited for 19inch rack mounting, 2 RU height, and can have up to 64 E1 2Mb/s interfaces using 8Interface Cards.

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 Availabi li ty

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 wiresclass 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 dissipationwhen IFCs and SFPs are inserted

12.95 Watt

6.6 Interfaces

STM-1 interface Depending on SFP in use.

E1 interface ADC101 2.048 Mb/s ± 50 ppm, HDB3 coded signalaccording to ITU-T G.703-9 (120 Ohm)

LAN interface 10/100 Base T non sensing interface, no MDI/MDX AUTOdetection.

Local console port DB9 connector, signal levels according to ITU-T V.28 andEIA232.

Test access output port (ADX200 and ADX201) via three banana receptacles (120 Ohm Siemensbanana-type) Providing E1 HDB-3 coded signal according to ITU-T G.703-9.

Digital inputs - 3 floating inputs DI1, DI2 and DI3. Per input two pins areprovided: DIxP and DIxN (1<=x <=3)

- 1 non-floating input DI4





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 isasynchronously 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 2048kbit/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,TX 1310nm, RX 1550nm, 20 km, SC connector

ADX-7077 2 027-00


ADX-7077 2 028-00


ADX-7077 2 029-00

SFP 155 Mb/s Bidirectional/Single Fiber,TX 1550nm, RX 1310nm 40 km, SC connector

ADX-7077 2 030-00


ADX-7077 2 031-00


ADX-7077 2 032-00

SFP 155 Mb/s STM-1e, COAX, DIN 1.0/2.3 connector ADX-7077 2 021-00Cables

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,DC Output 36 – 72 VDC, Output 48 VDC, 0.5A, 24W

ADX-7077 2 015-00

Miscellaneous

LSA-PLUS insertion tool S :6417 2 055-01

Blank face plate ADX-7077 2 010-01




Chapter 7 Management and remote management June 2009 • ADX-7077 2055-01, Issue 2.1

7 MANAGEMENT AND REMOTE MANAGEMENT

This section gives some functional background information for the System. Also someprovisioning (see page 87) 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, easyconfiguration and maintenance. To achieve this, dynamic routing is used instead of staticrouting.

7.1 Open shortest path fi rst (OSPF)

Open shortest path first is an example of a link state routing protocol. Neighbour routerstell each other their connections and status. In this way the routers create a map with thenetwork topology. Routes are quickly recalculated in case of topological changes. InOSPF the cheapest path is calculated via cost metrics.

OSPF is a hierarchical interior gateway protocol (IGP). IGP stands for a set of routingprotocols in Autonomous Systems (AS). An AS is a collection of nodes/routers in thesame network with OSPF enabled, thus sharing the same network information.

OSPF supports multiple areas to limit the amount of routing related traffic. Ifcommunication between other areas or other networks is required, there must be a wayout. An ASBR (see page 34) is used for this purpose.

To use OSPF you must enable it, at that point you must also specify a router ID for theSystem. This router ID is also used for system/host addressing. The router ID must beunique and cannot be equal to 0.0.0.0.

Since OSPF allows classless routing (defined in RFC 1817), discontinuous addressing isallowed.

7.2 Supported areas

An OSPF network can be divided into areas. The System, however, supports only onearea. Since OSPF AS requires that all routers are connected to the backbone area (alsoknown 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 Systemswill give the SYScROUTE alarm (see page 164). No guarantee can be given that the

Systems function properly if this alarm is raised. As a user you must take appropriateactions 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 fo r OSPF

7.3.1 Area Border Router (ABR)

An area border router connects one or more OSPF areas to the backbone. Since theSystem 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 areused to communicate with external networks. The system supports the ASBRfunctionality.

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 DHCPserver.

OSPF is enabled for the System.

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 tothe square. To be more specific: N nodes result in N*(N-1) link state messages. Toreduce the number and size of messages from increasing, the System automaticallyassigns one of the routers as a designated router.

The designated router plays a critical role in the link state advertisement. As a fall backpossibility 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) automaticallytakes over the role.

Each router is assigned an 8-bit priority, indicating its ability to be selected as the DR orBDR. 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 devicewith 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 thehighest RID is selected. A router declared the DR is ineligible to become the BDR. Onceelected, the DR and BDR proceed to establish adjacencies with all routers on the multi-access segment.

7.3.4 Numbered and unnumbered interfaces

Numbered and unnumbered interfaces (point-to-point links between routers) are bothsupported.

Unnumbered interfaces must be provisioned as 0.0.0.1/32.

7.4 Address resolut ion protocol (ARP)

The address resolution protocol allows the host to find the physical address (MAC) of atarget 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 partof a physical network whilst it is not physically connected to that network. Proxy ARP canonly be enabled for the LAN ports.

Normally the system for which proxy ARP is enabled will only respond to ARP requestsfor known network elements and OSPF enabled networks .





An advantage of proxy ARP above ASBR is that no static route provisioning is needed forthe gateway outside the AS. A disadvantage is that the subnet mask of the gatewayrouter outside the AS must be large enough to contain all systems and networks outsidethe AS.

7.6 Link costs and signal rate

For the System no link layer protocol configuration for the embedded DCC links isrequired. The System uses PPP (point-to-point protocol) over HDLC. It uses the MS-DCCcommunication 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 bothworking 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 aRouter ID

Note: We strongly recommend to use a convention to provision the IP addresses tothe 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 decimalnotation

Type A B C D

NE LAN Interface 10 12 LAN#: 0 - 255 NE#: 1 - 99

LP1 (PPP0) interface (unnumbered) 0 0 0 1

LP2 (PPP1) interface (unnumbered) 0 0 0 1

LP1 (PPP0) interface (numbered) 192 168 1 NE#: 1 - 99

LP2 (PPP1) interface (numbered) 192 168 2 NE#: 1 - 99

System or host address / router ID 10 15 0 NE#: 1 - 99

Directly connected Host / Manager LANinterface

10 12 LAN#: 0 - 255 Host#: 100 - 254

Host or manager LAN interface in accessnetwork

80 80 LAN#: 0 - 255 Host#: 100 - 254

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 isdisabled the LAN IP address should be used.

Figure 7. System access problems when using LAN IP address

192.168.1.1 / 32ospf

192.168.1.2 / 32ospf

10.12.1.2 / 24ospf

192.168.2.3 / 32ospf

10.12.1.3 / 24ospf

Host#110.12.0.100 / 24default route10.12.0.1

(10.12.1.x / 24)

192.168.1.4 / 32ospf

192.168.2.4 / 32ospf

192.168.2.1 / 32ospf

10.12.0.1 / 24ospf

[10] [10]

[10]

[174]

[174]

[174]

[174]

Autonomous System

(10.12.0.x / 24)

SDH 'ring'

NE#4(10.15.0.4)

NE#1(10.15.0.1)

NE#2(10.15.0.2)

NE#3(10.15.0.3)

[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 OSPFenabled 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 placebecause the 10.12.1.x/24 network is still available. Therefore NE#3 cannot be reachedanymore.

A better solution is achieved if the host uses the System router ID, being 10.15.0.3, toreach 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 explainthe functioning of the basic routing options.

7.9.1 Local management, host directly connected to System LAN and no routing protoco l

This section describes:

System and host in the same subnet (on page 37)

System and host connected to an access network (on page 37)





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 samesubnet.

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 thesubnet 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 SystemLAN interface. If the host wants to access the System that is not in the same subnet it willuse the default route entry. This is the ethernet address for router RT#1. RT#1 will deliverthe 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 routeper 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 andNE#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 andNE#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 knowshow to access the 10.12.0.x / 24 network. Without OSPF this information is not distributedand communication fails.

Table 3. Routing table NE#1

Destination Mask Gateway Flags Metric Interface

192.168.1.1

192.168.1.2

192.168.2.1

10.15.0.2

192.168.2.2

10.127.127.0

10.12.0.0

0.0.0.0

32

32

32

32

32

30

24

0

192.168.1.2

0.0.0.0

192.168.1.2

192.168.1.2

0.0.0.0

0.0.0.0

192.168.1.2

192.168.1.2

UGH

UH

UGH

UGH

UH

U

UG

UG

348

0

348

175

0

0

184

10

ppp0

ppp0

ppp0

ppp0

ppp1

eth0

ppp0

ppp0





Table 4. Routing table NE#2

Destination Mask Gateway Flags Metric Interface

192.168.1.1

192.168.1.2

192.168.2.1

10.15.0.1

192.168.2.2

10.12.0.0

0.0.0.0

32

32

32

32

32

24

0

0.0.0.0

192.168.1.1

0.0.0.0

192.168.1.1

192.168.1.1

0.0.0.0

10.12.0.100

UH

UGH

UH

UGH

UGH

U

UG

0

348

0

175

348

0

10

ppp0

ppp0

ppp1

ppp0

ppp0

eth0

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 isa 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.1.

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'tfit in the LAN network of Host#1. For example, 10.127.127.1/30. It is advised to disableDHCP 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 and10.127.127.3. The first one is often not allowed and the last one is a broadcast. So bothcannot be used as a host address.

Caution: If you use a LAN address for NE#1 that is in the same subnet as thedefault route of the host, you cannot reach NE#1 by its router ID anymore. In this caseNE#1 will notice that a shorter route exists if a request from NE#2 comes in, namely thelocal LAN of NE#1.





Remarks:

Router Table evaluation

The default route (destination is 0.0.0.0) is always the last entry evaluated in thetable.

Local addresses

The system software does not use the routing table if a local destination address isinvolved. This means that the costs and actual route can be ignored for a local PPPinterface.

Local PPP interface costs

The System routing table shows that the path costs to the local PPP interface hastwice the expected value. This is because this route is regarded as advertised by theneighbour and the cost to reach the neighbour are also included. However they playno 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 therouting table.

PPP interface regarded as a host address

According to the System routing table a PPP interface is regarded as a host addresswhich 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 (LANinterface 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-pointconnection) the default route is 192.168.1.2 (LP1) via which also the 10.12.0.0 / 24network 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 bothrouted via the same port (LP1) which is a coincidence. Also note that the path cost isthe 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

Autonomous System

SDH terminal

SDH ring

NE#7(10.15.0.7)

NE#4(10.15.04)

NE#6(10.15.0.6)

Host#1

192.168.2.4 / 32ospf

192.168.1.7 / 32ospf

192.168.2.7 / 32ospf

10.127.127.1 / 30(no dhcp)

10.12.0.100 / 24default route:

10.12.0.2

192.168.2.5 / 32ospf

192.168.1.6 / 32ospf

192.168.2.6 / 32ospf

10.127.127.1 / 30(no dhcp)

192.168.1.4 / 32ospf

NE#5(10.15.0.5)

NE#3192.168.1.5 / 32ospf

192.168.1.2 / 32ospf

10.12.0.5 / 24ospf

NE#2(10.15.0.2)

192.168.1.1 / 32ospf

10.12.0.2 / 24ospf

10.12.0.3 / 24default route:10.12.0.5

192.168.2.2 / 32ospf

192.168.2.1 / 32ospf

NE#1(10.15.0.1)

10.127.127.1 / 30(no dhcp)

10.12.1.4 / 24ospf

Host#2

10.12.1.100 / 24default route10.12.1.4

Both hosts are able to access any of the systems. All Systems, except NE#3, are OSPFenabled. 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 thedesignated 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 willbe advertised to, amongst others, NE#4. So if Host#2 wants to access NE#3 via10.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, becauseNE#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 OSPFis enabled for all Systems, NE#2 forwards the message to NE#5. And so on. Also NE#2recognizes 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 andadvertisement must be enabled. In this way all systems in the access network can bereached, but only if RT#1 is provisioned for it. This can be done on per individual addressbase or by assigning one entry: 10.15.0.0/28 -> 80.80.2.6. This covers the range10.15.0.0 ... 10.15.0.14.

The access network does not get any status information of the autonomous system. Thisimplies that only internal failures inside the AS can be addressed/resolved. To make itmore 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 placebecause 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 42), it is also possible to use proxy ARP on an ASBR. The applied subnet mask /24 (preferred multiple of 8), gives access to a relativelarge 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 placebecause of the OSPF password authentication.

A proxy ARP enabled system will not respond to an ARP request if the routing pathinvolves the network interface via which the ARP request was received. Only OSPFenabled systems can be managed via the access network. The managed nodes and atleast 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 overlappingsubnet. This may result in unmanageable Systems (see "Avoiding management problemswith proxy ARP" on page 44).

7.10.4.1 Avoiding management problems with proxy ARP

The figure shows a configuration in which management problems may occur if theconnection between NE#3 and NE#4 is OSPF enabled. Because an ARP request forNE#4 by Host#1 can be answered both NE#2 and NE#1.

Figure 14. Proxy ARP example

NE#5(10.15.0.5)

NE#1(10.15.0.1)

NE#3(10.15.0.3)

10.15.0.12 / 24ospf proxy arp

NE#2(10.15.0.2)

Host#1

NE#4(10.15.0.4)

10.15.0.11 / 24ospf proxy arp

10.15.0.100 / 24

OSPF

No OSPF

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 becomeunmanageable.

Note: If resilience is not needed, only one System per LAN network should havethe Proxy ARP feature enabled, this keeps the management network as simple aspossible.




Chapter 8 Subnetwork connection protection (SNCP) June 2009 • ADX-7077 2055-01, Issue 2.1

8 SUBNETWORK CONNECTION PROTECTION (SNCP)

8.1 Introduction

The system supports subnetwork connection protection. With the aid of SNCP theSystem protects a low order virtual container (sub) network connection. At the head-endthe virtual container is permanently bridged into two tributary units (TU), at the tail-end theselection 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 wasrerouted to, remains active when the error disappears. Manual, forced and clearcommands are supported.

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 trafficselected path:

A server signal failure on the subnetwork connection.

A trace identifier mismatch (TIM), per SNCP connection a user can exclude TIMsfrom the switching conditions. LPdTIM results in a consequent action that takes 3 TTIframes to clear, the TTI frame during which the switch occurs is also lost, together 4TTI frames = 32 ms.

An unequipped virtual container (UNEQ).

A degraded signal (DEG) condition occurs, user can set the threshold for the DEGcriteria (see "Degraded Threshold provisioning and handling" on page 115).

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 aresimultaneously active, their hold-off timers run independently. The switching is completedwithin 50 ms after fault detection plus the hold off time.

Worker (from) and protection(prot) legs are linked to different Line Ports. The protectedport always links to a tributary port. The settings for the Non Intrusive Monitors (NIM) areretrieved 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




Chapter 8 Subnetwork connection protection (SNCP) June 2009 • ADX-7077 2055-01, Issue 2.1

For reliable monitoring of SNCP protected cross-connects the system supports multipleprotected cross-connects which share the same worker and protection leg. Sharing ofonly one leg is not supported and rejected by the System. Note that at most one of thecross connects can be bidirectional.

Note: Shared settings of NIM points are retrieved from the last provisioned VC12trail termination point. The initial NIM settings are copied from the first associated VC12trail termination point with an SNCP protection group.

Note: Changing the termination settings for a protected VC12 trail termination pointwill also be applied to the worker and protection NIM settings. This may harm yourconfiguration.

8.2 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. Thiscan 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 samepath.

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 previousworker leg.

In order to change the leg of an SNCP protected cross-connect one needs totemporarily convert the cross-connect into an unprotected one by removing theworker or protection leg. After this a different protection leg can be added to theunprotected cross-connect resulting in the changed SNCP protected cross-connect.

Caution: Also the test port can be provisioned as an ordinary port for which onlythe outgoing signal is made available. In case of an ADX200 the test port can only beprovisioned as test port. In case of an ADX100 and ADX201 the test port can already bein use as an ordinary port, so in this case the test port settings will overwrite theprevious made settings.




Chapter 9 Port loopback functionality June 2009 • ADX-7077 2055-01, Issue 2.1

9 PORT LOOPBACK FUNCTIONALITY

The Systems supports port loopback on the following levels:

E1 incomingE1 outgoing

STM-1 outgoing

Figure 15. Port loopback functions

Incoming

VC12 unequipped

Outgoing

AU4 MS-AIS

LP 1IFC 1

VC12

E1 AIS

E1 AIS

IFC n LP 2

Outgoing

Test

A warning is displayed if you create a loopback request. This because unexpected sideeffects may occur, for example in the synchronization domain.

Note: The simultaneous support of an incoming and an outgoing loopback for thesame port is not supported and is rejected by the system.

Note: The combination port loopback and using the port as timing reference is notallowed. The system prevents that this can be provisioned.




Chapter 9 Port loopback functionality June 2009 • ADX-7077 2055-01, Issue 2.1

9.1 E1 incoming loopback

The System accepts at most one incoming E1 port loopback. If you want to add a new E1port loopback you first have to locate the existing one (see page 109) and then remove it.

The implementation of an E1 port loopback results in inserting and forwarding VC12unequipped. The consequent action of forwarding VC12 Unequipped for an incoming E1loopback will finally result at the far end in generating E1 AIS (Unequipped is not definedfor E1).

Note: To avoid local alarm messages the locally generated VC12 Alarms aresuppressed if you implement an E1 incoming port loopback.

9.2 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.

9.3 STM-1 outgoing loopback

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




Chapter 10 Installation guide June 2009 • ADX-7077 2055-01, Issue 2.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 not ices

Caution: Work ESD safe! Take appropriate ESD precautions when unpacking, installing or decommissioning theproduct. Use a wrist wrap when handling SFP modules and interface cards.

Caution: The equipment may only be installed and operated by qualifiedemployees.

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 fo r 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.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 ofinterfaces (see "Connecting interfaces" on page 54)

Label Holder attachment (see "Remove and Insert label holders ADX100" on page55)

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 SFPtransceivers.

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

Caution: Work ESD safe!

Take appropriate ESD precautions when unpacking, installing or decommissioning theproduct. Use a wrist wrap when handling SFP modules and interface cards.

1. Loosen screws (4x).

2. Gently pull frame to the front and turn to the right side (in case possible, temporaryfixate provisional to the profile bar).





10.5.1.4 Install ADX100 Main Module

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.

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" onpage 54).

10.6 Mounting inst ruct ions 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

Insert ing SFPs


1. Inserting SFPs.

Connect ing power

Specifications (see "Cables and pinning" on page 67):

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 con nector

A special 3 pin Siemens banana connector or single banana plugs can be used.

1. Connecting Test Access Output.

Insert ing interface cards






1. Insert card.

2. Fasten screws.

Removing inter face cards


1. Loosen screws.

2. Remove card.





10.7 Cables and pinning

10.7.1 DC power cable

Figure 38. DC Power Cable

+

Ground

Blue

Red

Green/yellow-

L (according to installation)

Strain reliefPhoenix

mounted

10.7.2 LAN - Power over Ethernet cableFigure 39. Power over Ethernet Wiring

TxOutP 1 1aTxOutN 2 1b

RxInP 3 2aRxInN 6 2b

NC 4 3aNC 5 3b

NC 7 4aNC 8 4b

Blue

White-Blue

Orange

White-Orange

Green

White-Green

White-Brown

Brown

Using the spare wires (4,5,7,8) is optional. Length must be within 100 meters, cable typemust be CAT5 or better.





10.7.3 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 toset the initial communication parameters. Shielded cable is recommended and themaximum cable length is 20 m. A 1:1 cable is required to connect this port to the DTEcom port of a PC.

Figure 41. 9-Pin D-Sub connector





10.7.4 Digital inputs

Connect external inputs to the DIG IN 9-pole Sub-D front connector. The pin layout of themale connector as used on the System is shown in the figure. See also the specifications.

Figure 42. Digital input connector

Table 6. Connector specifications

Input Pin Note

DI1P 1 1, 4, 5

DI1N 2 1, 4, 5

DI2P 3 1, 4, 5

DI2N 4 1, 4, 5

DI3P 5 1, 4, 5

DI3N 6 1, 4, 5

DI4 8 2,4

GND 7 3

3V3 9 3

Notes:

1) True and false conditions:

- True: 3V <= (DIxP - DIxN) <= 12V

- False: (DixP- DIxN) < 1V

2) DI4 has a fixed internal positive voltage of 3.3V compared to GND

3) Short circuit proof power source of 3.3V

4) Rload < 100 Ohm

5) Extrenal power supply <= 12V




Chapter 11 Set up of the System June 2009 • ADX-7077 2055-01, Issue 2.1

11 SET UP OF THE SYSTEM

This section will provide the information needed during the first set up of the System. Anoverview 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 browserset 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 PCcross-cable is required for direct connection. Additionally the LAN port supports Powerover 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 localmanagement control settings. The connection settings are: 38400 b/s, no parity, 8 databits, one start, stop bit. The System does not require hardware control wires to beconnected.

11.1.3 Telecom power feed

The System has two telecom power feeds with a nominal voltage of -48/-60 V DC. Theconnector type is a Phoenix mini-Combicon connector. The power fed to theseconnectors 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 modu les

The System has two cages for SFP modules. An inserted SFP will be taken into servicewithout user provisioning, assuming no SFP was inserted before. The SFPs are hotpluggable (see "Pluggable items" on page 90).

11.1.5 Interface Cards

The ADX100 and ADX201 have 8 slot positions for Interface Cards, called the tributaryslots. 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 Cardsare hot pluggable (see "Pluggable items" on page 90). Each interface card has 8 portswhich are called the tributary ports.

11.1.6 Test access output

The ADX200 and ADX201 have a dedicated E1 test access output. The test accessoutput is implemented by using three banana receptacles at the front side: two for signaland 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 alsologically 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 upthe activity (green) led will flash with 2 Hz, connecting with a web browser to the System

is not possible. After some minutes the System is operational and the green led stopsflashing. A connection via the web browser can be made. The first minute alarminformation is not available.

Monitoring the presence of power is enabled when setting the alarm for power failure toreported (default it is not reported). Each power has its own detector, SYScPFA andSYScPFB. When this alarm is raised power might not be present at the input or thecorresponding fuse is broken. Check this by measuring the input voltage. Fuses are notfield replaceable.

Note: A swap of -/+ will result in a power failure alarm, although the System ispowered.

Additionally the System supports Power over Ethernet. This power feed has nomonitoring facility for a loss of power.

Caution: Do not simultaneously provide Telecom powering and Power overEthernet.

11.3 IP address management

The System can be managed via the 10/100BASE-T Ethernet LAN interface. To getaccess to the management interface the System must have a valid (known) IP address, inthe 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 canbe done with a direct PC to System LAN connection. The System has an integrated webserver. The HiThere utility can be used to discover the System equipment present on theLAN (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 DHCPserver 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 wi thout DHCP server

When no DHCP server is used a new default address needs to be provisioned for theSystem. After System recovery the System will perform a limited number of attempts toobtain an IP address/mask from a DHCP server. When not successful no further requestswill be made.

A DHCP can be user controlled.

There are three options to change the IP settings.

Via the web browser

Using the HiThere utility.

Via the local management console port

All options have an equivalent result.





Figure 43. 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’. Whenconnected 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 willbe 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 toobtain an IP address/mask from a DHCP server (if DHCP is enabled). If this is successfulthis 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 becomeoperational. Changing of the default IP settings is described (see page 73) and is similar.

11.3.1.3 HiThere utility

The HiThere (see page 179) utility can be installed on a Windows PC. This utility is a.o.used:

to discover the Systems on the subnet the PC is connected to.

for LAN provisioning.

for SNMP alarm trapping.

Each System is installed with a HiThere server program. The System responds with itsMAC address, IP address, subnet mask, IP default gateway and host name.

11.4 Port provisioning

11.4.1 Line ports

Note: Only members of the admin group can change the line port settings.

To setup the line port interface use SYSTEM-IP SETTINGS-INTERFACES. Next select LP1 or LP2 and click Edit.

Figure 44. Line port settings

You can provision numbered (see page 35) and unnumbered (see page 34) interfaces.Unnumbered interfaces must be provisioned as 0.0.0.1/32. Enter the IP Address, nextselect RS-DCC or MS-DCC for remote managament and click Apply.

Table 7. DCC communication

DCC kb/s

MS-DCC 576

RS-DCC 192





11.4.2 LAN ports

11.4.2.1 LAN port provisioning via WEB browser

Note: Only members of the admin group can change the LAN settings.

To setup the LAN interface use SYSTEM-IP SETTINGS-INTERFACES. Next select the LAN interfaceand click Edit.

Figure 45. 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 belost 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 theapplicable 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 withthe Organization Unique Identifier (OUI) 00 0f 25. This is a read-only value fixed for everySystem. 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 reflectthis assigned address.

DHCP If you enable this option the Sytem will immedately try to obtain the LAN IP details (IPaddress, mask, gateway) from a DHCP server. If this fails the Default values will berestored. 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 interfaceaddress of the ASBR System is shown or the IP address of the external accessrouter/gateway. This gateway address is only applied if it can be reached directly

without involvement of an ASBR System.





11.4.2.2 LAN provisioning via HiThere

HiThere (see page 179) needs to be installed on a Windows PC. The utility uses the MACaddress to connect to the System.




Chapter 12 GUI Settings and system authorization June 2009 • ADX-7077 2055-01, Issue 2.1

12 GUI SETTINGS AND SYSTEM AUTHORIZATION

12.1 Web browser and navigation

The System has an integrated web server. Supported browsers are listed in the releasenotes.

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 windowwill reappear with the changes been made.

Clickable items via System layout

Some items shown on the System overview (see "ADX201 GUI System overview" onpage 82) are directly clickable.

Field colors convention

For the field colors following convention is used. Editable fields are clearly marked asyellow and non-editable fields are non colored. When the value of a field is changedduring a provisioning action the color will change into blue. By clicking the Apply buttonthe changes are applied and the field color is changed back into yellow. You can useRefresh to cancel the provisioning action.

Simultaneous sessions

The System supports five different sessions simultaneously. When a sixth session isstarted 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 ofthe window.

Smart selection

The System tries to predict the next selection. This is applicable for those windows inwhich a list is shown. This is the case when adding cross connects, editing ports ortermination points. When there is no next logical selection no pre-selection will be made,but always a valid list is presented.

Access to related items

In several menus the quick navigation option is available to go direct to related items. Likein 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 enteringthe existing password first. The user should enter the new password twice before the newpassword 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: adc123admin group Members of the admin group are responsible for maintenance activities like softwareupgrading, database operations, user group administration and IP and SNMPsettings.

Only users in the admin group can create or remove users. They can also provideinitial passwords for new users.

The following characters are allowed for a user name: [a-z], [A-Z], [0-9], [_-.].

The password of already existing users can be changed by an admin user withoutknowledge about the existing password.

There must always be at least one user in the admin group. For 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 settingscan 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 usersafter 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 differentfor 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 shownand the 8 E1 ports, separated in transmit (TX) and receive (RX) side. This overview isindependent 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 71)

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 israised or an existing alarm has been cleared. Press [!] to clear this indicator.

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 87).






Figure 48. ADX200 Welcome Screen

12.4.4 ADX200 GUI System overview


The ADX200 System overview represents the System with the four tributary slots.

Directly accessible via the overview, by clicking the object are:LAN POE: LAN settings (see "Set up of the System" on page 71)

LP1/2: SFP details



One of the E1 ports: Details of the E1 port provisioning, in this case there’s nodifference when accessing it via RX or TX.

Tributary slots: By clicking on TS1, TS2, etc.


TEST: The test access output port can be accessed via this button (see "Testaccess output" on page 118). Selecting this port gives cross connect information onthis port. The user is able to see which cross connect is made towards the testaccess output port. Additionally the existing cross connect can be edited, the typeuni-or bidirectional will be retained. When no cross connect exists, a unidirectionalcross connect can be added. The port and VC12 related setting of the test accessoutput are accessible via TS8.8.



DIG: Indicates the 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.

Directly accessible via the overview, by clicking the object are:

LAN POE: LAN settings (see "Set up of the System" on page 71)

LP1/2: SFP details



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.






TEST: The test access output port can be accessed via this button (see "Testaccess output" on page 118). Selecting this port gives cross connect information onthis port. The user is able to see which cross connect is made towards the testaccess output port. Additionally the existing cross connect can be edited, the type

uni-or bidirectional will be retained. When no cross connect exists, a unidirectionalcross connect can be added. The port and VC12 related setting of the test accessoutput are accessible via TS8.8.



DIG: Indicates the 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 systemsettings are changed. Per event the log file includes a time stamp, a user identification

and a descriptive text. The sort order depends on the provisioning moment. The size ofthe file is about 100 kB. Contact ADC for details.

Only users of the admin group can access logfiles. They can download (Backup) themfrom 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 thelogfile 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 87) except for theLAN settings which is described elsewhere (see page 72).

Note: Depending on the login rights (see page 78) 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.




Chapter 13 Provisioning June 2009 • ADX-7077 2055-01, Issue 2.1

13 PROVISIONING

13.1 Introduction

Provisioning of the System is done via the Web browser. When a login as admin isrequired this is explicitly mentioned.

13.1.1 ADX100, ADX200 and ADX201 dif ferences

All screens and menus shown are similar for all three hardware platforms. The Systemlayout part of the screen is not shown in this section. When differences exist they will bementioned 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. Themultiplexing 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 protectedconnection.

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 thisis reported as an alarm. This action will insert e.g., an AIS signal in the downstreamdirection 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

MENU: SYSTEM| DETAILS

To show the System name, location and hardware specific details.

Figure 52. System Details

The System parameters such as name and location of the System can be provisioned.

System name A name of 30 characters can be entered.

Location A location of 30 characters can be entered, allowed characters are:

[A-Z][a-z][0-9]+_-./|:;#%~@&*[]()><!?^$.

Evaluation of these characters takes place after pressing Apply. If invalid characterswere entered a warning is displayed and the input is not accepted.

Note: When minimizing the browser, the name and location and are shown.

Note: The current System location and name are shown on the top bar of thebrowser.

VC12 Unequipped Check this box to insert a VC12 Unequipped signal, for all VC12, in the VC12 upstreamdirection when a loss of signal (E12cLOS (see page 166)) is detected on the related E1port.

Caution: This functionality is not according the ITU-T standard! Therefore it isdisabled by default.

If you activate this functionality it replaces the behaviour of inserting an E12cAIS (see

page 166) when a loss of signal is detected. The VC12 and E1 signal will be replaced byan all-zeros signal.

Item code The item code identifies the type of System.

ADH101 for ADX100 PROFIL mount (ADX100 main module).

ADH102 for ADX200 1RU for 32 E1 interfaces.

ADH103 for ADX201 2RU for 64 E1 interfaces

Catalog number The order number (see page 32).

Serial number

The serial number of the System. This number is factory assigned per product and isuseful for tracking hardware.





13.4 System Time

The system time can be set manually (see "System time manually" on page 89) or it canbe retrieved from one or two NTP servers (see "System time from server(s)" on page 89).

13.4.1 System time manually

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 andSNMP traps/notifications. When no time is set the default Linux time is taken at startup:January 1, 1970. The SYScTIME alarm is reported if the RTC indicates that its time isinvalid. The alarm will be cleared when the time is set manually or when NTP is enabled.

MENU: SYSTEM| TIME| M ANUAL

Figure 53. System Time Manual

System Time This field shows the current time of the System (see page 163). A Refresh is needed toget 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 iscontinuously 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 andvalues. Then press Apply.

13.4.2 System time from server(s)

The time can be retrieved from one or two independent NTP servers.

Figure 54. System Time NTP





StatusThe status field shows one of the following statuses: Unreachable, Initializing,Not synchronized or Synchronized. A Refresh is needed to get the current value.

ServeripThis field shows the IP address of the selected NTP server that is used for the

synchronization of the time.

Polltime(s)This non provisionable field shows the update frequency for the synchronization of thetime.

Accuracy (ms)This non provisionable field shows the accuracy of the local NTP entity.

StratumThis non provisionable field shows the hierarchical level of the NTP server that is used forsynchronization of the time. The highest quality NTP server has Stratum 1, systemsgetting their time from this Stratum 1 server, have Stratum 2, and so on.

System Time UTC This field shows the current time of the System (see page 163). A Refresh is needed toget the current value.

Config

Fill in the IP-addresses to retrieve the time from and check one or two boxes. If no IPaddresses of NTP servers are selected, the only way to set the real time clock is via themanual provisioning screen.

After filling in the address(es) of the NTP server(s) press Apply. The Status field willsuccessively display:

Unreachable. This means that the local NTP entity cannot be reached. This is thecase after NTP settings have been changed.

Initializing. This means that the local NTP entity is starting up.Not Synchronized. This means that the local NTP entity does not consider itselfsynchronized to one of the provisioned NTP servers.

Synchronized. This means that the local NTP entity is synchronized to one of theprovisioned NTP servers

A Refresh is needed to get the current value.

13.5 Pluggable items

Pluggable items are the Interface Cards and SFPs. The pluggable items can be insertedand removed while the system is powered (hot pluggable).

Caution: Pluggable items, SFPs and Interface Cards, need to be handledaccording to ESD guidelines.





MENU: SYSTEM| PLUGGABLE ITEMS

Figure 55. Pluggable Items Overview

13.5.1 Interface Card

The System supports the ADC101 Interface Card. The System will automatically discoveran inserted Interface Card. The default tributary slot state is AUTO. When the IFC has asupported item code (ADC101-ADC120) the state will change from AUTO to ASSIGNEDand the IFC will be operational, this takes less than one minute.

Selecting the desired TS (Tributary Slot) will show the details.

Figure 56. 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 AUTOand IFCcWUI (IFC Wrong Unit Inserted) is reported. When the inserted IFC is defectivean IFCcEQF (IFC Equipment Failure) is reported. The IFC needs to be replaced by acorrect one.

When no IFC is present in ASSIGNED mode and IFCcUNP is reported (IFC Unit NotPresent), this will be due to a removal. In AUTO mode no reporting of a Unit not Presentis done.

Item code The item code identifies the type of Interface Card. Currently the ADC101 is available forthe Systems. The ADC101 has 8 ports E1 (G.703) 120 Ohm ports with ADC LSA-PLUSIDC edge connectors. The System is prepared for future versions of Interface Cards, asitem code ADC101 up to ADC120 is supported in this release. Future Interface Cardsmight have different impedance or connector types.

Catalog number The catalog number (see page 32) of the interface card without connector.





Note: Interface cards can only be ordered including a connector. A short orderinglist is included in this manual (see page 32).

Serial Number

The serial number of the selected IFC. This number is factory assigned per product and isuseful for tracking hardware.

Last Accepted The item code of the IFC which was present and accepted before the current one. Thisinformation is of use when in future more item codes are supported, and IFCreplacements 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 affectingwhen an Interface Card is present.

Accept Pluggable Item

This can be used when an IFC has been replaced with another type (item code) this willbe of use when more item codes are supported. When before executing this operationtraffic is running, this action is not service affecting.

13.5.2 IFC replacement.

When an Interface Card is replaced with the same item code, the System will accept theIFC and the state remains ASSIGNED. When an IFC is replaced with another IFC havinga different but supported itemcode an IFCcREPL alarm will be reported and the user hasthe option to accept this IFC. The alarm will notify the user of the change in item code. Inthe last accepted field the user can view the previous item code and he can decide if thechange 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 inupstream direction AIS is inserted into the payload (E1 signal).When provisioning VC12termination point settings they will not be effective until an IFC is inserted, in this situationyou can pre-provision the VC12 TTP.





13.5.3 Small Form Pluggable

The System has two SFP positions related to the line ports.

Figure 57. 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 arepresent.

AUTO: No SFP is present or the inserted SFP is not accepted, see SFP replacementand acceptance for more details.

Qualifier

The module qualifier identifies the type of SFP. This is according to ITU-T G.957. Allmodule qualifiers will be accepted by the System. The module qualifier for optical SFPshas 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 nmdispersion shifted.

ExampleS1.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 bedue 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. Checkthe 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 SFPhas been replaced.

13.5.4 SFP replacement and acceptance

When the SFP state is AUTO and an SFP is inserted this will be accepted irrespective ofthe module qualifier. When the SFP state is ASSIGNED and an SFP is inserted, then infact it is a replacement. In this case the inserted SFP module qualifier will be comparedwith the last accepted. When they differ an SFPcWUI will be raised and the SFP is notaccepted. Transmission will be shut down. This alarm notifies the operator on a change ofSFP 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 timingreference is assigned from this port the timing reference has to be unassigned beforechanging the state to AUTO.

13.5.5 Single Fiber SFPs

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

13.6 System recovery

Some actions related to the System software or database may result in a Systemrecovery. A System recovery will take some minutes. A System recovery is not serviceaffecting. 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. Afterthe System has come up a cold restart trap will be sent to the provisioned SNMPmanager(s).

In case of a system upgrade the status of the System is indicated as soaked (see"System software" on page 95).

When at any time a database failure is detected the System will invoke automatically aSystem recovery.





Figure 58. System initialization

13.7 System softwareThe System supports one load line for all three products. For information about softwarereleases refer to the release notes.

The System has two software memory banks.

MENU: M AINTENANCE | SYSTEM| DETAILS

The detailed content of both banks is shown.

Figure 59. 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 iscurrently running

active soak A software upgrade has taken place and the sanity process is notyet finished. The software in Bank 1 is currently running. When thesanity process is finished the new state (bank1/bank2) isactive/inactive if the upgrade is successful or soak/error if a recoveryhas taken place before expiry of the sanity timer.

soak error duringlast imagetransition

An ISD switch has been unsuccessful (only applicable for theinactive bank). If this error occurs the image is valid but a transitionerror 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, refer to release notes for details.

Software Version Identifying software release, sub release, maintenance release, load drop version.

Build time Build time and date.

Caution: Downgrading of software is not supported. If downgrading is required doso immediately after receiving a System. If this is not possible (anymore) you have totake care that local access to the node is possible.

13.7.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. TheSystem will recover and connection to the Web browser is lost. This action will beperformed when a software upgrade is required. Check before activating that the inactiveISD state is inactive and the ISD specific details as Item code and software version docorrespond with the ISD requested. During recovery the System database will beconverted when necessary to the new software version.

Note: If you select the inactive ISD a warning is shown to indicate the impact of theoperation.

During recovery after an ISD switch, a sanity timer is running. This timer enables theSystem to fall back to the previous ISD when the switch was not successful e.g., due to aconflict in the database. In this way service will never be affected. When this happens theSystem will come up with the previous ISD, check in this case whether the upgrade youwere performing is supported. The sanity timer will run for about one minute after theSystem is manageable. The System being manageable is indicated by the green ledstopping to blink.





1. System recovery takes some minutes, during this period the activity LED will blinkwith 2 Hz. frequency.

2. After the green LED has stopped blinking you can login to the System, alarmevaluation 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, theSystem selects the previous active software. The database changes which weremade during the sanity period are lost.

Check after the System is up again whether the requested ISD is active. (Bank 1 alwayscontains the active ISD) When a switch over was not successful, the state of the secondbank is "error during last image transition". This could be caused by a power outageduring 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 hasstopped blinking.

13.7.2 Install software manually

To upload a new ISD to the inactive bank select: M AINTENANCE | SOFTWARE | INSTALL

Figure 60. Software Upload

By selecting Browse..., a file browser is started at the PC. From this browser select theISD. The ISD will be uploaded to the System. This will take about 5 minutes, the size ofan ISD is about 7.2 Mb.

Note: The text in the Browse... button depends on your local language settings.

A progress indicator will be displayed.

Figure 61. Loading the software





When the upload is finished the details of the uploaded ISD are shown.

Figure 62. Software Upload Completed

Note: The value for the Software version field in the screen dump in this manualdoes not show the most recent version of the software.

13.7.3 Install software via FTP

To upload a new ISD via FTP to the inactive bank select: M AINTENANCE | SOFTWARE | FTP

INSTALL

Figure 63. Software Upload

Enter User , Password , Server , Port and [P ath /]File then click Install:

User : The username as defined on the FTP-server.

Password: The password for the user as defined on the FTP server.

Server : Address of the FTP-server.

Port: Access port of the FTP-server.

[Path/]File: The default path for the user as defined on the FTP-server followed bythe <file>.

Caution: Do not select any other menu during the software upload, this will stopthe upload.

FTP Status During FTP data transfer the Status field changes into Busy, and the Percentage willincrease. Use Refresh to update these fields. Refresh also refreshes the information ofUser , Password , Server , Port and [Path/]File .

Note: The screens below are also valid for FTP database backup/restore.

During the transfer an Abort button appears. Press this button if you want to abort thedata transfer.





Figure 64. Data transfer

When the data transfer is finished successfully the Percentage shows 100 and Statuschanges back to Idle.

Figure 65. Status changes into Idle

When the data transfer did not finish successfully the user can retrieve additionalinformation by pressing Refresh, now an additional Info button will appear. If the userpresses this button additional information will be shown about the failure.

13.8 System database

A new System has one database, the default database addf.db. This default database isincluded in the System software and will never be lost. Database handling can only beexecuted 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 SNMPsettings. The SNMP and IP settings will be retained when restoring, uploading, selectingor 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 161).





Select M AINTENANCE| D ATABASE to display an overview of all databases.

Figure 66. Database

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 runningsoftware and the structure of the selected database. For this reason so called databaseconversion scripts are needed, included in the active ISD.

Conversion is only supported from a lower to a higher database version. If for example adatabase version #1 is selected while the current running software is supporting databaseversion #3 a conversion form #1 -> #3 is needed. The System first converts #1 -> #2followed 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 decideto make a backup of this database by downloading it to a host system.

Note: That the converted database gets the hardware identification of the hardwareon which the conversion takes place.

This operation takes a few seconds and is also dependent on the amount of conversionsneeded. The request might be rejected if:

1. A database is selected for which conversion is required but no tooling or script isavailable. Note that this implies that the selection of a database with a versionnumber higher than the current active database version number is rejected.

2. The database file is not existing because it has been removed by a concurrentdatabase 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 arecovery, 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 adatabase for ADX200 is not compatible with a database for ADX201. A database for aspecific hardware version will only operate on that hardware version. The type of thedatabase identifies the platform it suites. When selecting an invalid type this will berejected.

13.8.1 Database maintenance manually

Note: If a database operation is selected a warning will be displayed to indicate the

impact.

MENU: SYSTEM| D ATABASE | M ANUAL

Figure 67. Database maintenance

Restore Using this option, a database can be uploaded to the System. By selecting Browse youcan pick the desired database via the PC connected to the System. A database shouldhave extension .db. The upload takes less than 1 minute, (depending on your networkconnection). The typical database size is about 100 Kbytes. When finished the uploadeddatabase 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 towardsthe 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 theactive database the System will recover and come up with the default database retainingthe 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 theWeb browser is lost. When the selected database has different settings as the currentone transmission will be affected. When the selected database has identical settingstransmission 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 68. Database Copy Active

13.8.2 Smart defaults

A database of one System can be used at another System of the same hardware platformtype. Specific databases can be prepared on one System which can be uploaded toSystems 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 requiredSystem. When an emergency occurs this database can be selected.





13.8.3 Database backup via FTP


impact.

A backup can be:

scheduled, one time a day and seven days per week or

can be done instantaneous.

Note: As long as nothing has been changed in the database a scheduled backup isnot executed. However changing a parameter and change it back to it's original valueagain is considered as a change.

Note: The User , Password , Server . Port and [Path/]File fields are saved into thedatabase when the user presses the Apply2 button. The software FTP install (see"Install software via FTP" on page 98), Database restore (see "Database restore viaFTP" on page 105) and Log FTP backup (see "Log files via FTP" on page 107) willinitialize their values for the User , Server and Port fields from the database.

MENU: SYSTEM| D ATABASE | FTP | B ACKUP

Figure 69. Database backup via FTP

FTP Status During FTP data transfer the Status field changes into Busy, and the Percentage will

increase. Use Refresh to update these fields. Refresh also refreshes the information ofUser , Password , Server , Port and [Path/]File .











Scheduled backup

Use the pull down menus UTC(hh), UTC(min) and the check boxes (Mon ... Sun) todefine the scheduled backup (to clear these fields use Refresh). All times as shown onthe screen during FTP are in UTC format. Then click Apply1. Next enter User ,

Password , Server , Port and [Path/]File then click Apply2:






Backup now

To start the backup immediately enter User , Password , Server , Port and [Path/]File then

click Backup Now.If a scheduled or backup now fails the SYScDBBCKP alarm is raised.





13.8.4 Database restore via FTP


impact.

MENU: SYSTEM| D ATABASE | FTP | RESTORE

Figure 72. Database restore via FTP







When the data transfer did not finish successfully the user can retrieve additionalinformation by pressing Refresh, now an additional Info button will appear. If the user

presses this button additional information will be shown about the failure.





Restore

To restore the database from an FTP server, enter User , Password , Server , Port and[Path/]File then click Restore:






13.9 Log files

The user can retrieve log files (see "Log file for System settings" on page 83) in two ways:

Manually (see "Log files manually" on page 106) or via

FTP (see "Log files via FTP" on page 107)

13.9.1 Log fil es manually

To retrieve the log file manually use:

MENU: M AINTENANCE | LOG| M ANUAL

Figure 75. Manual log file

Use Backup to download the log file cmdl og. t xt to a local file. Use Delete to delete thelog file from the System.





13.9.2 Log f iles via FTP

To retrieve the log file via FTP use:

MENU: M AINTENANCE | LOG| FTP B ACKUP

Figure 76. FTP log file

Fill in the User , Password , Server, Port and [Path/]File:

















13.10 Ports and termination points

13.10.1 Ports

The System has two STM-1 line ports and 8 E1 tributary ports per interface card. Acommon 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 timercontinuously 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 1minute.





13.10.2 Line ports

The Line port selection can be made with, MENU: TRANSMISSION | PORTS| LINE PORTS

Figure 79. Line Port Selection

When selecting Edit of a selected line port you can set the details for this port.

Figure 80. 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 notselect this signal for synchronization (on page 133), when QL enabled is selected.

13.10.3 Tributary Ports

The E1 tributary ports support unframed E1 transmission. In fact they are transparent forany 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 ASSIGNEDInterface Cards.

The tributary port selection can be made in Menu: Tr ANSMISSION| PORTS| TRIBPORTS.

Figure 81. Tributary Port Selection





To show the details of the selected tributary port press Edit.

Figure 82. Tributary Port Details

The Port AutoMode Time, Port Monitor Mode as well as the User Label can beprovisioned. 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" onpage 140).

Default value Timing Mode is: Self Timed, in this mode the retiming (see "Retiming E1ports" on page 140) 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.10.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 110)

VC4 (see page 111)

VC12 (see page 113)

RS and MS section

The RS and MS termination point selection can be made with TRANSMISSION | TERMINATION

POINTS | RS/MS.Figure 83. RS/MS Selection





The RS and MS termination points are direct related to the physical line ports. Themonitoring mode therefore cannot be provisioned and is slaved to the related line portmode. 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 84. 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 116).

Specific for the J0 byte is in the repeating byte mode the J0 value is 01.

MS Termination point

For the MS termination point the degraded threshold value set can be selected. Thisdefines the threshold at which an MS degraded alarm will be reported,

Two sets are available. These sets can be provisioned separately (see "DegradedThreshold provisioning and handling" on page 115).

VC4 termination po ints

The System has two VC4 termination points which are directly related to the line ports, ofwhich one is selected independently per port. Line port 1 has a fixed VC4 cross connectto VC4 #1 and Line port 2 towards VC4 #2.

The default monitoring mode of the VC4 termination points is monitored. The VC4 TTPmonitoring mode controls the alarming (see "Resolving alarms and problems guide" on

page 161) on this point, except for the VC4cPLM and VC4cLOM which will be reportedirrespective of the monitoring mode.





In the menu TRANSMISSION | TERMINATIONPOINTS | VC4 the selection can be made.

Figure 85. 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 127).

Use Edit to get the details of the selected termination point.

Figure 86. VC4 Termination Point Details

Trail Trace The default mode is repeating byte. More details are available (see "Trail Trace Identifierprovisioning and handling" on page 116).

Trail Signal Label The trail signal label (C2 byte) identifies the type of traffic in the VC4 container. Thetransmitted signal label is fixed TUG structured (02). The accepted (received) TSL mustbe TUG structured (02) or equipped (01), other values indicate a type of traffic notsupported by the System. A VC4cPLM (Payload Mismatch) alarm will be raised when theaccepted TSL has a different value then 01 or 02. As consequent action AIS is inserteddownstream. The VC4cPLM alarm is not under control of the monitoring flag. In case theTSL has a value 0, indicating unequipped, a VC4cUNEQ alarm is raised. This might bedue 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 161).

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 VC4is a fixed bidirectional cross connect.

Monitoring Mode The default mode is monitored. When no alarming is required the mode can be set to NotMonitored.

Degraded threshold The selection of the degraded threshold value defines at which threshold a VC4degraded alarm is reported. The choice can be made for threshold set 1 or 2 (see"Degraded Threshold provisioning and handling" on page 115).

VC12 termination point

The System has 64 VC12 termination points. For the ADX201 this is 32 + 1 test accessoutput. Irrespective of the presence of Interface Cards the VC12 terminations points areavailable.

The list of VC12 termination points can be retrieved via TRANSMISSION | TERMINATIONPOINTS | VC12

Figure 87. 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 theVC12 TTP is the To point, towards a VC12 termination point the monitoring mode willbe set to Monitored.

Use Edit to get the details of the VC12 termination point.





Figure 88. VC12 Termination Point Details

Trail Trace The default mode is repeating byte. More details are available (see "Trail Trace Identifierprovisioning and handling" on page 116).

Trail signal label The trail signal label (V5 byte) identifies the type of traffic in the VC12 container. Thetransmitted signal label is fixed asynchronous (02). The accepted (received) TSL must beasynchronous (02) or equipped (01), other values indicate a type of traffic not supportedby the System. A VC12cPLM (Payload Mismatch) alarm will be raised when the acceptedTSL has a different value then 01 or 02. As consequent action AIS is inserteddownstream. The VC12cPLM alarm is not under control of the monitoring flag. In case theTSL has a value 0, indicating unequipped, a VC12cUNEQ alarm is raised. This might bedue 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 161).

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 whena bidirectional cross connect is applied towards this VC12 TTP, or when a unidirectionalcross connect is made with the VC12 TTP as to point. When deleting the cross connectthe monitoring mode remains as it was. When no alarm reporting is required or after thecross-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 provisioningand handling" on page 115). The specific values for these sets can be provisioned withMENU: TRANSMISSION | DEGRADED THRESHOLDS.





13.10.5 Degraded Threshold provisioning and handling

For every termination point two sets of degraded thresholds can be provisioned. Thevalue of the provisioned degraded threshold defines the number of background blockerrors 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 causea protection switch.

The default value of the degraded value corresponds with the severely error seconddeclaration in the Performance Monitoring domain.

The duration value defines the number of consecutive seconds in which the errors of thedegraded signal exceed the threshold value. This value can be provisioned from 2 to 10seconds, the default is 7 seconds.

The degraded thresholds can be provisioned for MS, VC4 and VC12 level.

Table 8. 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 specifictermination point the threshold set 1 or 2 can be chosen.

Select TRANSMISSION | DEGRADED THRESHOLDS to get the global set for all levels.

Figure 89. Degraded Thresholds Overview

Two sets of degraded thresholds exist. On every individual termination point of thecorresponding level you can make a selection out of the two sets.





13.10.6 Trail Trace Identifier provisioning and handling

The trail trace identifier (TTI) enables an end to end check on the transmission path. Thesource will send a transmitted trail trace identifier which is received at the destination(accepted trail trace identifier). When enabling TIM (Trace Identifier Mismatch) detectionthe accepted trail trace identifier will be compared with the expected value. When amismatch is detected a TIM alarm is reported. As consequent action of the TIM, AIS issent downstream and RDI is inserted in the upstream direction. VC12 RDI is sentupstream 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

Repeating Byte

In this mode a constant value will be sent in the TTI. For the System this is 01 for theRS level and 00 for VC4 and VC12. In this mode no transmitted and accepted valuecan be provisioned. For J0 (RS) a trail trace dentifier mismatch will be detected whenthe accepted TTI does have a different value than 01. For J1 and J2 a trail traceidentifier mismatch will be detected when no non specific byte is received. When TIMdetection is enabled a TIM alarm for this termination point is reported and asconsequent action AIS is sent downstream and RDI upstream.

String

In this mode a 15 byte string can be provisioned for the transmitted and expectedvalue. 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. WhenTIM detection is enabled and the accepted (received) trail trace identifier differs fromthe expected one, a TIM alarm is reported and as consequent action AIS is sentdownstream and RDI upstream.

13.10.7 Provisioning t rail trace identifiers

Figure 90. Trail Trace Provisioning





When selecting the requested termination point to be changed, the trail trace identifierscan be provisioned. This behavior is similar for all levels VC12, VC4 and RS. Theexample is a VC12 level.

Trail Trace Identif ier

Accepted statusIndicates 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 orhexadecimal 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 unstableaccepted TTI.

Unequipped: The VC12/VC4 container has an unequipped signal label, notapplicable 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 willbe reported and as consequent action AIS will be inserted downstream and RDI in theupstream 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 (seepage 110). 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 andThreshold 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 ofconsecutive seconds a number of block errors per second has been detected. Theintervals can be specified with Threshold 1 Duration or Threshold 2 Duration, the numberof 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.10.8 Test access output

The ADX200 and ADX201 support a dedicated test access output port. This test accessoutput is available at three banana receptacles, E1 signal according to G.703 in 120Ohm.

For the ADX100 no dedicated port is present, but in fact every E1 port can be used astest access output port.

A bridge can be provisioned via a unidirectional cross connect from the existing crossconnect to the E1 port to be used as a test port.

Caution: The ADX201 test access output port is only active when an InterfaceCard is present in Slot 8. When no Interface Card is present in TS8,8 AIS is transmittedon the test access output.

The test access output is referred to with TS8.8. In the ADX201 this port is also routed totributary slot 8 port 8. Add a unidirectional cross connect from the connection to bemonitored. Select the from point to distinguish the direction you want to monitor. TheVC12 termination point related to the test access port is also available and can be usedto view the VC12 path overhead. The output signal of TS8.8 in the ADX201 will beidentical 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 clickingTEST in the System overview.





Figure 91. Test Access Output

The current cross connect to the test access output (TS8.8) is shown, and in this screenthis 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 124).

13.10.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 themeasured background block error rate in the downstream direction. When the far endsystem supports far end performance monitoring these values can be used for themeasurements. Both VC4 and VC12 should be bidirectional.

13.11 Cross connects

To provide transmission over the System, cross connects have to be provisioned. Fromeach line port a fixed VC4 cross connect is present towards the low order cross connectfunction. 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 basictypes of cross connects can be made

Unidirectional

Bidirectional

These types will be outlined in detail.





13.11.1 Definitions

Cross connects can be added and deleted. In this chapter the provisioning parametersare listed.

From

The From point in a cross connect defines the originating point. Choosing which point willbecome 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 notpossible for the to point.

To

The To point of a cross connect defines the destination point. At this point the VC12 pathoverhead is terminated if it is a VC12 termination point. In the System VC12 terminationpoints 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 triggeredto become active if ,a TIM (Trace Identifier Mismatch),an UNEQ (unequipped VC) or aDEG (degraded signal) condition occurs on the service connection (if the stand-byconnection 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 aFrom point. The provisioning of the VC12 termination point can be made (see "Ports and

termination points" on page 108). 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. Crossconnects can be added irrespective of the presence of Interface Cards.

TU12 connection termination points (see page 171)

The TU12 connection termination points do exist at the line ports. These points are notedas LPX .klm. where X is the line port number and the klm identifies the position of theTU12 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 aVC12 path. In fact the line port points are TU12 non intrusive points, no overhead isadded 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 upstreamdirection.

Type

The type identifies if the cross connect is unidirectional or bidirectional.





Bidirectional

A bidirectional cross connect supports traffic in two directions. Bidirectional crossconnects can be made between:

Line port and tributary port

Traffic coming from the line port is dropped to the connected port (downstream) andtraffic 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 thisSystem. 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 doexist. Major difference with the bidirectional is that unidirectional cross connects can bemade between two free points but also can be added to the from point of an existingcross connect (bridging) They only can be added to the from point, you have to realizethis when adding cross connects which you later want to bridge with a unidirectional crossconnect.

Loop back cross connect

A unidirectional cross connect with the same from and to point, can be used as aVC12 loop back.

Broadcasting

Uni directional cross connects can be multiple bridged. In this way a broadcastfunction is supported. Multiple outputs are provided with one source signal. Thesource signal is coming from the “From” point. The number of bridged points isunlimited. 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 outputcan be used by adding a unidirectional cross connect to this port, with the test accessoutput as to point. For non intrusive monitoring the test access output can be addedas unidirectional (bridged) to an existing cross connect to be monitored (see "Testaccess output" on page 118).

Unidirectional cross connects can be made between the same type of points asbidirectional. As unidirectional cross connects do not have a return path no RDI and REIwill be inserted (see page 172).





13.11.2 Listing, editing and deleting cross connects

MENU: XCONNECT | LIST

To delete or edit cross connects use

Figure 92. Cross Connect List

Delete When selecting the cross connect to be deleted and next clicking delete, this crossconnect will be deleted. No further message is shown and transmission via this crossconnect 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 bechanged 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 93. Details XConnect

The change can be made by selecting the new From / Protection point and selectingApply.





13.11.3 Adding cross connects

The System supports sequentially adding cross connects. After a cross connect has beenadded the window returns with a pre-selection for the next logical selection. When no nextlogical selection is available no pre-selection is made. In the selection list only availablecross connect candidates are listed. Once a point has been cross connected it will beremoved from the selection list. Supported are:

Bidirectional cross connects (on page 123)

Unidirectional cross connects (on page 124)

Protected SNCP Bidirectional cross connects (see "SNCP Cross connects uni- andbidirectional" on page 124)

Protected SNCP Unidirectional cross connects (see "SNCP Cross connects uni- andbidirectional" on page 124)

13.11.3.1 Bidirectional cross connects

Adding a bidirectional cross connect will set the VC12 termination point(s) involved tomonitored. Adding a unidirectional cross connect will set the mode to monitored if theVC12 termination point is the To point. Deleting a cross connect will not change themonitoring mode. For a bidirectional cross connect not always a VC12 termination point isinvolved. When connecting to a line port a TU12 CTP (connection termination point)isinvolved 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 94. Add Bidirectional Cross Connect

When selecting CROSSCONNECTS | ADDBI DIRECTIONAL| TP -> LP a bidirectional cross connectfrom 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 beestablished. If you assign a user label (see page 109) it is also shown in the screen.





13.11.3.2 Unidirectional cross connects

Adding a bidirectional cross connect will set the VC12 termination point(s) involved tomonitored. Adding a unidirectional cross connect will set the mode to monitored if theVC12 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 isinvolved. When connecting to a line port a TU12 CTP (connection termination point)isinvolved 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 CROSSCONNECTS | ADDUNI DIRECTIONAL | TP - >LP you can add a unidirectionalcross connect from a tributary port to a line port.

Figure 95. Add Unidirectional Cross Connect

Select the desired to and from point and next select Add, the cross connect will beestablished.

Note: This is the same for the other add unidirectional cross connect options.

13.11.3.3 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 canbe done by removing either the worker or protection leg. Which makes a hitlessconversion 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 beeither uni- or bidirectional. SNCP uni- or bidirectional cross connects can be made as:

LP1 ->TP <- LP2

LP2 -> TP <- LP1

When selecting XCONNECTS | ADDSNCP UNIDIRECTIONAL | LP1 -> TP <- LP2 you can add an SNCPunidirectional cross connect for tributary port





Figure 96. 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 isprovisioned, 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 byremoving the worker or protection leg.

2. Now a different protection leg can be added to the unprotected cross-connectresulting in the changed SNCP protected cross-connect.

An SNCP protected cross-connect can be either uni- or bidirectional.

Edit ing cross connects

To edit an SNCP cross connect use menu: XCONNECTS | LIST, select a cross connect andpress Details.





Figure 97. Editing a cross connect

In this screen the following fields are shown:

Current

Accepted TTI Status and value: identifies the accepted status (see page 113) andvalue. This data is shown for the Protection and From leg. Per leg a non intrusivemonitor is supported.

Type: identifies the type of cross connect (see "SNCP Cross connects uni- andbidirectional" on page 124).

Common settings

Accepted TTI Status: identifies the accepted status (see page 113).

TIM detection: identifies if the Trail Identifier Mismatch is enabled (see page 116).

Monitoring mode: can be monitored or not-monitored (see page 113).

Selected Degraded Threshold : identifies the threshold set (see "Degraded Thresholdprovisioning and handling" on page 115).





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 andhandling" on page 115)

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 aSystem 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 requesthaving a lower priority than the current priority. In this case you first have to execute a"Clear" request and then the actual request.

13.12 Transmission protection MSP

In terminal applications 1+1 Multiple Section Protection in unidirectional and bidirectionalmode, revertive and non revertive is supported. The MSP protocol is compliant with ITU-TG.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 thereceiver side the selection for worker or protection is made. When using MSP only oneVC4 (63*VC12) container can be transmitted instead of two. Only the VC4 related to theworker 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 workerand line port 2 as protection and vice versa.

13.12.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.12.2 Definitions

Bidirectional

In bidirectional mode an STM-1 embedded control channel coordinates the switchingactivities at near and far end.

Unidirectional

In unidirectional mode the switching of near end and far end are independent.

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 protectedconnection.

Switch criteria

Failures detected at the MS layer will lead to an MSP switch. When at the MS section anMS1cSSF or MS1cAIS is detected a signal fail will be declared for that leg. When an MSdegraded 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 areincluded.

Degraded

The corresponding leg has an MS degraded alarm, based on the degraded thresholdprovisioning (see "Degraded Threshold provisioning and handling" on page 115).

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 beendetected at the worker side and remains at the protection side when the failure has beencleared.

Revertive

In case of a failure in revertive mode the traffic switches to the protection side and willswitch 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 switchwill revert after a failure has been cleared. During expiry of the wait to restore time nofailure 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 certainperiod, this period is the WTR time.

External switch requests

The user can invoke switch requests via the web browser to override the automaticswitching (see "External switch requests" on page 129). In case of maintenance thismight 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 findout which leg is active.

13.12.3 Creating an MSP pair

To create an MSP pair select MSP | CREATE.

Figure 98. 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), type (Uni-directional orBi-directional) and select Create. Once the MSP pair has been created no changesregarding operation mode or worker/protection side can be made. To change this the pairhas to be deleted and recreated with the required settings.

Note: If a port is carrying traffic or the MSP pair already exists, a warning isdisplayed.

Figure 99. MSP Port is carrying traffic





13.12.4 Deleting an MSP pair

When an MSP is required to be deleted, select MSP | DETAILS, next click Delete.

Figure 100. 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 endare both set to worker no service impact is to be expected.

13.12.5 MSP details

This section will describe the MSP details window.

Select menu: MSP | DETAILS, next select an MSP protection group and click Edit. Now thereare two possibilities the MSP group was provisioned to be Uni-directional or Bi-directional . Both screens are shown.

Figure 101. MSP Uni-directional details

Figure 102. MSP Bi-directional details





Uni- and Bi-directional:

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 isrunning.

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 page129).

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 switchrequests" on page 129). 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 129).

Bi-directional only:

Active Section,:The Active Section indicates Worker or Protection.

APS Code The APS Code indicates the cause of the switch.

Near End, Far End,Under error free circumstances both Near End and Far End are set to Worker and the APS Code of both is NoRequest. If one of the Ends executes a switch request toProtection the other end will immediately follow. So Both Ends are set to Protection.

The initiating End shows the cause of the switch, the following End showsReverseRequest. See also figure MSP switch request .





Figure 103. MSP switch request

The table shows the APS-codes:

Table 9. APS codes

APS Code Descript ion

NoRequest No change to the current switch state of the corresponding MSPsection.

ReverseRequest Switch request initiated by the remote MSP section.

SignalFailHighPriority A failure has been detected at the correspondent MSP section.

SignalDegradeHighPriority

An MS degraded has been detected at the correspondingsection.

Forced A forced switch request is initiated on the corresponding MSPsection.

Manual A manual switch request is initiated on the corresponding MSPsection.

Lockout The MSP protection is locked out, worker is selected by thecorresponding MSP section.

.

13.12.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 MSP | DETAILS.

Figure 104. MSP Switch Requests

Executing switch requests may lead to a service interruption of less than 50 ms. Thecurrent switch state is shown in the state field.

When executing a switch request a warning will pop up, to indicate switching might beservice 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 isdisabled. The worker leg is selected for traffic.

Forced Sw to worker : Enforces switching traffic to the worker line. It overridesautomatic switching even in case of a signal fail or signal degrade. This can beservice affecting.

Forced Sw to protection: Enforces switching traffic to the protection line. Itoverrides automatic switching in case of a signal degrade but not in case of a signalfail on protection. This can be service affecting.

Manual Sw to worker : Switches conditionally traffic to the worker line. When afailure is present at the worker line switching is rejected. In case a failure is raisedduring the manual to worker state traffic will switch to the protection line. When e.g. aforced request or lockout is outstanding a manual request will be rejected, the forcedrequest first has to be cleared.

Manual Sw to protection: Switches conditionally traffic to the protection line. Whena failure is present at the protection line switching is rejected. In case a failure, SignalFail and Signal Degrade, is raised during the manual to protection state, traffic willswitch to the worker line. When a forced request is outstanding a manual request willbe 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 is5 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.13 Synchronization

The intention of Synchronization is to synchronize the whole SDH network to one masterclock. The provisioning of the individual network elements must be aligned to besynchronized from one side and forward the reference towards the other side of thenetwork. Before provisioning the System a network synchronization plan must beavailable, including a backup plan when the master clock fails, preventing timing loops inany 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 135).

Provisioning of the System timing, like WTR timer, locked or free running mode, anduse of the SSM algorithm which is described (see "Provisioning timing sources" onpage 135).

External timing switch request, to overrule the automatic timing selection algorithm.





Changing the synchronization setting takes some time to complete the details shown on awindow returned after the action is not up to date. A refresh of the window is needed toget the actual details.

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

given for provisioning synchronization of a network.

13.13.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 caseMSP 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 istransmitted in the STM-1 overhead in the synchronization status message, the S1 or SSMbyte. For E1 signals no QL is supported.

Reference Fail

A reference fail will be declared when the signal related to that reference has a failurewhich impacts the timing reliability. This can be transmission related failures likeSTM1cLOS,STMcLOF, MS1cAIS, E1cLOS or E1cAIS. Another cause might be anexcessive frequency offset of the reference. When the frequency of the reference has adeviation 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 thisonly 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 sentout and the incoming SSM bytes are ignored.

Table 10. QL Overview

QL S1/byte* Accuracy Description

DNU 1111 Notapplicable

Do not use for synchronization, indicates thesignal should not be used for synchronization.

Unknown Notapplicable

No QL information is available

PRC 0010 10-11 Primary reference clock.

SSU-T 0100 1.5.10-9 Synchronization supply unit-transit, indicatesthe timing is derived from a transit SSU

SSU-L 1000 3.10-8 Synchronization supply unit-local indicates thetiming signal is derived from a local SSU.

SEC 1011 4.6.10-6 SDH equipment clock indicates the timingsignal is derived by an SDH equipment clock(internal System clock)

*the first nibble of the S1 byte is 0000.

QL-inThe 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 theQL-in, when a value has been provisioned this value will be the QL-out.

Outgoing SSMThe 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 userinterface.

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, toprevent timing loops in the network.

The SSM out on the line ports represents the System QL, except for the activereference 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.13.2 Provisioning timing sources

The System has the ability to provision three independent timing sources. One from oneof the E1 ports and two from both line ports.

When selecting menu: TIMING| TIMING SOURCES the three timing sources are listed:

Figure 105. 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 caseMSP 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 duringexpiring 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.13.3 Provisioning l ine port references

Figure 106. Edit timing source

Assigning and editing the reference are separate actions, it is preferred to first assign thereference and next edit the settings.

Assign Select the line port to be assigned to this timing source and select the assign button. Onlythe line port references available are shown. When MSP is enabled only the worker portof 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 aSTM1cLOS, STM1cLOF, RS1cTIM, MS1cAIS or an excessive frequency offsetof the reference signal.

Monitored Choose from:

Monitored

Not monitored: Now a timing source failure can be reported for this timing sourcewith 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 sourceselection.

QL provisioned

For line port references the default value is AUTO. When using AUTO the QL level istaken from the SSM value received from this reference. When this reference is unable toprovide a SSM value a provisioned value can be chosen according to the quality of thisreference. Be aware when using a provisioned value changes in the quality of thisreference will not be recognized (see page 140).

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 expiringof 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 restoretimer, 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 usedas timing reference. The default value is locked out. When provisioning the timing sourcethe 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 referenceindividually can be locked out.





13.13.4 Provisioning tr ibutary port references

When selecting the timing source to be edited:

Figure 107. Tributary Timing Source Provisioning

Only differences with provisioning line port (see "Provisioning line port references" onpage 136) references are explained.

ReferenceOnly 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 beprovisioned. A value corresponding to the quality of the reference needs to be chosen. Beaware that changes in the frequency accuracy of this reference will not be observed. Thedefault value is SSUT.

13.13.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 theautomatic selection when the System is under maintenance. Provisioning and switchingare separate actions in the System timing menu.

Select menu: TIMING| SYSTEM TIMING





Figure 108. 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 itsinternal 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 theinternal clock. No external references are used for System timing. The Systemquality will be SEC.

Locked mode: In locked mode the System will be synchronized by an externalreference. The selection is based on the provisioned timing sources (see "Systemtiming" on page 138).

QL Indicates the System quality level.

QL Enabled (see page 140) If this selection box is cheked, the System will use the SSMalgorithm to select a timing reference. Furthermore the System Quality level (outgoingSSM) will indicate SEC in free running mode and the QL-out of the selected timing sourcein locked mode. When QL is not enabled the System timing will not select timingreferences based on the SSM algorithm but will do this only based on the priority of thereferences. 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 beprovisioned between 0 and 60 minutes, in 1 minutes steps. When using 0 no WTR isbeing 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 areference 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 switchwindow.

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 retimedE1 ports a reference switch might be service affecting (see "Retiming E1 ports" on page140).

when executing a switch request a warning will pop up to indicate the action might beservice affecting. The user has the option to cancel the switch request. Impact of servicedue 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 referencemay be selected and will result the System to switch to holdover state.

Manual: A manual switch only overrides the automatic selection process in thepriority selection. In case a reference fail or a another reference has a better QL theautomatic selection will take over.

13.13.6 System timing reference selection

The selection of the active reference can operate in two modes, priority based (on page140) and SSM based (see "SSM based algorithm" on page 140).

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 thehighest priority will be selected. In case multiple references have the same priority theselection is random. When a reference fails the next in priority will be chosen, when thefirst 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 theSystem will not revert to that one.

SSM based algorithm

When QL is enabled the selection is SSM based . The reference with the highest qualitywill be chosen. See table 1 for the QL definitions. The quality levels in descending orderare 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 forselection

The reference with the highest QL will be selected.

In case multiple references have the same QL, the one with the highest priority isselected.

In case multiple references have the same QL and the same priority, the selection israndom.

In case no suitable reference is available the System will switch to holdover and a

SYNCcBHO is reported.

13.13.7 Retiming E1 ports

Each individual E1 port can be provisioned in retiming mode. In retiming mode thefrequency of the outgoing E1 signal is resynchronized with the System frequency. Aretimed E1 output port can be used as timing reference for the System connected to. Asthe E1 signal coming from the retimed port has the System timing frequency. In normaloperation, self-timed, the frequency of the E1 output signal is the floating avarage of thefrequency of the E1 input signal.





Using an E1 port in retiming mode might affect the traffic on this connection. When thereis a frequency difference between the incoming E1 payload signal and the Systemfrequency, 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- orunderflow 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| TRIBPORTS, then select the tributary port and clickEdit.

Figure 109. 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 E1isrecovered from its TU12 envelope by deleting all non-E1 octets. This yields a gappedsignal which is consequently smoothed by means of a Phase Locked Loop. A

disadvantage of this method is that the slow phase variations introduced byoccasional TU12 pointer adjustments or VC12 stuff-bits are too low frequency to befiltered by the PLL, which acts as a low-pass filter for phase variations (equivalent 3dB bandwidth below 1 Hz). For normal applications, this wander introduced byoccasional pointer and mapping adjustments can be safely ignored. However, incase the E1 output is used by the attached equipment as a reference for a (highquality) clock, it may be rejected due to these phase excursions.

Re-Timed: Alternatively, the E1 output signal can be Re-Timed by the internaloscillator of the System. This avoids phase excursions due to TU12 pointeradjustments. A necessary condition is that the internal System clock is locked to areference that is synchronous with the equipment that generated the E1 that is to beretimed. Otherwise, the buffer in the E1 output circuit will regularly overflow orunderflow. Each overflow or underflow event leads to a buffer re-center (causing

frame loss events in the downstream equipment) or a controlled slip (avoiding OOFin 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 theSystem QL is below this value the port will switch to its fall back mode. When QL isdisabled in the System timing settings the retimed port will not check on the acceptancetiming 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 theacceptance quality level.

Self timed: The port will switch to self timed when the QL of the System is below theacceptance 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 tothe 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 isin fall back mode, due to the System QL being below the acceptance QL. TheSYNCcLRR alarm will be reported for this port.

13.14 SNMP

SNMP settings can only be changed with admin rights.

The System supports a Simple Network Management Protocol (SNMP) agent. TheSystem is fully SNMP manageable. All settings that can be done using a web browsercan also be done using SNMP (except the settings of the SNMP screen itself). TheSystem supports both SNMPv1 and SNMPv2. The user can provision up to five SNMPmanagers. These are identified by their IP address. The community string has to be

entered and a selection for traps v1 and or v2 notifications can be made.

Autonomous alarm events are reported to the SNMP manager. In the trap notification thealarm description, location, severity and time stamp are shown and if it is a raise or aclear.

The SNMP object identifier of the aimvalley specific MIB's is:iso.org.dcd.internet.private.enterprise.aimvalley (1.3.6.1.4.1.23862).

Before being able to use SNMP you have to import the System MIB to the SNMPbrowser. The MIB files are available at the System software CD. Please contact ADC forMIB files. Next you compile the MIB in the SNMP browser. These actions will be specificfor the SNMP browser being used.

Select menu: SYSTEM| SNMP SETTINGS

Figure 110. SNMP Details





Manager IP address The IP address of the SNMP manager.

RO/RW Community Allows the user to group the RO/RW communities

RW If this box is checked the System allows set commands from the managers.

V1 trap / V2 Trap Select V1 Trap if SNMPv1 traps are required. Select V2 Trap if SNMPv2 notifications arerequired.If both are enabled a trap and notification is reported.

Alarm community Allows the user to group alarm traps.

13.14.1 Current alarm list with SNMP

Figure 111. Example of a current alarm list on a SNMP browser

Note: The UTC time is used (see page 21).





13.15 Performance moni toring

13.15.1 PM overview

The system supports non-intrusively performance monitoring on E1. It is possible tomonitor up to 64 monitor points simultaneously. For this purpose the following countersare available.

BBE-counter : counts the number of Background Block Errors in the CRC-4overhead of timeslot 0 in the E1-signal.

ES-counter : counts the Errored Seconds, every second which has one error or morewill be declared errored.

SES-counter: counts the Severely Errored Seconds, every second which has morethan 300 BBEs will be declared severely errored. Every second with a raisedE1cLOS, E1cAIS or P12ScLOF is also declared severely errored

UAS-counter : counts the UnAvailable Seconds. Displays the same value as the

SES-counter as soon as more than 10 consecutive SES errors occur.

Note: P12ScLOF alarms are not reported on the GUI.

Furthermore six unavailable periods, UAPs (see page 147), time stamps are maintained.These time stamps contain the start and end time of an UAS.

The counters are stored in current and history bins of 15 minutes (15m) and 24 hours(24h). Performance monitoring can be provisioned for all E1 ports. The table shows thenumber of available bins.

Table 11. Available bins

bin 15m 24h

Current (see page 146) 1 1

History (see page 147) 16 1

The counters can be provisioned to raise alarms (Threshold Crossing Alerts). Such analarm is raised if the value of a counter is larger than the provisioned threshold (see page145).

Note: After a cold or warm reset (see page 159) the PM data is lost.





13.15.2 Add/Delete PM points

To Add or Delete PM points, select PM | ADD/DEL.

Figure 112. Add or delete PM points

Add

The selection can be added with a 15 minute register (with or without alarmed), 24 hoursregister (with or without alarmed) or both. To provision a PM selection, select the trib Slot - trib Port combination, check 15 minute register,24 hours register or both. Optionallycheck alarmed (see "PM Threshold" on page 145), next click Add.

Delete

To delete it, select the trib Slot - trib Port combination, select a 15 minute register, 24hours register or both and click Delete.

13.15.3 PM Threshold

The PM points can be provisioned to raise alarms with option alarm enabled (ThresholdCrossing Alerts). Such an alarm is raised if the value of a counter is larger than theprovisioned raise threshold. The alarm is cleared if the value in a succeeding bin issmaller than the provisioned clear threshold. These thresholds can be provisioned per 15minutes (15m) and 24 hours (24h) bin per port.

Select PM | THRESHOLDS.

Figure 113. Select Trib slot - Trib port

Select the Trib slot - Trib por t combination and click Edit.





Figure 114. PM Thresholds

The figure shows the default values for the BBE, ES, SES, UAS clear and raise countersfor the selected combination. The alarmed flag is used to enable/disable the alarming (onpage 154) for thresholding.

13.15.4 PM Current Data View/Reset/Refresh

Use PM | CURRENTD ATA to display the actual PM data.

Figure 115. PM Current data

Next select the Trib slot - Trib por t combination, check 15m and/or 24h and click View.

Figure 116. View Current PM data

Click Reset to reset the current data view. All counters of the selected ports will be set to0 and Suspect will change into Yes.

SuspectThe suspect flag indicates that the performance data for the current period may not bereliable (ITU- T 822). The main reasons to set the suspect flag is when a bin is startedand if a history bin lacks 10 seconds of data. The value of the suspect flag is Yes (set) or

No (not set).Use Refresh to retrieve the actual data, due to the algorithm it has a delay of 10 seconds.





13.15.5 PM Histo ry data View

Use PM | HISTORYD ATA to achieve the logged PM data. Use

Figure 117. PM History data

Next select the Trib slot - Trib por t combination, check any combination of 15m, 24h, andnonzero and click View. Option nonzero will retrieve only bins with counters .> 0.

Figure 118. View History PM data

Use Refresh to retrieve the actual data, due to the algorithm it has a delay of 10 seconds.

13.15.6 PM UAP Log

Per PM point six unavailable periods (UAPs) are maintained. These periods contain the Begin and End end time of a UAP.

Use PM | UAP LOG to display the UAP log selection screen, next click View.

Figure 119. PM UAP log selection





Figure 120. PM UAP log view

Begin shows the start time of the UAP, End the end time.

Use Refresh to retrieve the actual data, due to the algorithm it has a delay of 10 seconds.

13.16 OSPF provisioning

13.16.1 OSPF settings

The OSPF setting can be provisioned via the menu: SYSTEM| IP SETTINGS | OSPF | GENERAL.

Figure 121. OSPF Settings

OSPF General

Enabled To enable or disable the OSPF. The default is disabled. If enabled you also mustprovision the System with a router ID.

Router ID

To enter the System OSPF router ID. The router ID is a /32 IP address that uniquelyidentifies 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 33). Read only value.

ASBR Indicates if this System is an ASBR (see page 34) or not. If this system is provisioned asan 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 35), 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 takeninto account. Only the advertised external costs (LAN=10) matters for the decisionwhich 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 149).

13.16.2 OSPF Interfaces

The OSPF interfaces can be reached via the menu: SYSTEM| IP SETTINGS | OSPF | INTERFACES.

Figure 122. 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


List Interfaces To go to the management interfaces of this System.





Edit Select the interface to edit and click Edit.

LAN (see page 75)

LP1 or LP2, see figure Interface LP1

Figure 123. 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.16.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 124. 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 canbe set to enabled or disabled.

Area Displays the Area of the OSPF. Read only value.

Metric Link costs (see page 35). Read only value.

Router Priority Used to determine the designated router (see page 34).. Read only value.

Auth Type, Auth Key Used to check if other Systems belongs to the family. Auth Type is read only Auth Key iseditable. Per OSPF interface (LAN, LP1, LP2) an Auth Key (up to 8 non-extendable ASCII characters) can be provisioned. Default Auth Key is "ospf4adc". By provisioning thesame Auth Keys for non-familiar and familiar systems on an OSPF interface, also thenon-familiar Systems can be managed. In other words the management possibilities aremade more flexible.





Hello Interval (sec), Router Dead Interval (sec) OSPFs send hello packets to their neighbours. They are used to check whether theneighbours can be reached or not. If a System (router) cannot be reached for a RouterDead 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 thelink state database on each device.When a router generates or modifies an LSA, it must communicate this changethroughout the network. The router starts this process by forwarding the LSA to eachadjacent device. Upon receipt of the LSA, these neighbors store the information in theirlink state database and communicate the LSA to their neighbors. This store and forwardactivity continues until all devices receive the update. This process is called reliableflooding. Two steps are taken to ensure this flooding effectively transmits changes withoutoverloading 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, therouter replaces the stored version. However, if the new copy is outdated, it isdiscarded.

LSA Retr: To ensure reliability, each link state advertisement must be acknowledged.Multiple acknowledgements can be grouped together into a single acknowledgementpacket. If an acknowledgement is not received within, the original link state updatepacket is retransmitted.


List OSPF Interfaces To go to the OSPF interfaces of this System.

13.16.3 OSPF Systems

The OSPF setting can be provisioned via the menu: SYSTEM| IP SETTINGS | OSPF | SYSTEMS.

Figure 125. OSPF Systems

RouterID: Shows OSPF enabled systems that can be reached, note the RouterId isdisplayed.

13.16.4 Manual route add/delete

A manual route (see "Management and remote management" on page 33) can be addedto or deleted from the local IP routing table. Manual routes via both numbered andunnumbered interfaces are supported.

Add a manual route

Menu: SYSTEM| IP SETTINGS | ROUTE| M ANUAL





Figure 126. Add a manual routing

Destination Enter the destination address.

Mask Enter the mask.

Gateway In case of a LAN, enter the gateway address that must be used to reach the destination.Do not select a line port now.

Interface In case of a line port select via which port the destination must be reached.

Do not fill in a gateway address now. The gateway must be 0.0.0.0.

Apply Click apply to add the manual routing entry. The system displays a confirmation pop upscreen.

Figure 127. Warning message

List Manual RoutesTo show a list with all manual routes.

List All Routes To show a list with all routes.

Delete a manual rou te

Menu: SYSTEM| IP SETTINGS | ROUTE| M ANUAL

Figure 128. Delete a manual route

DeleteSelect the route to delete and press Delete. Again the warning message will bedisplayed.





13.17 Digital inputs

The ADX200 and ADX201 both support 4 digital inputs. These inputs can be used togenerate alarms and can be provisioned as normally open and normally closed contacts

(see figure). The digital input alarms can be provisioned (see "Alarm profiles, severities,reporting and LEDs" on page 157) as all other alarms. Default the alarms are set to non-reported (see page 157). The digital input alarms are: ENVcDI1, ENVcDI2, ENVcDI3and. ENVcDI4.

To provision a digital input use SYSTEM| DIGITAL INPUTS. Specify a DI label and choose howthe alarm is controlled with Alarm Control (active on No Current or Current). Click Apply when finished.

Figure 129. Digital inputs

Status The status can be Alarmed or Not alarmed .

DI Label

The digital inputs can be provisioned with a label. This label will be shown in the alarmwhen it is raised.

Alarm Control

The alarm control can be provisioned to raise the alarm on Current or No current .





13.18 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 andcan be visible at the System LEDs.

When a defect is present it will be reported as an alarm within 2.5 ± 0.5 seconds. Whenthe cause of a raised alarm is cleared within 10 ± 0.5 seconds the clearing will bereported and the alarm is added to the history list.

13.18.1 Most recent alarm bar

Below the System layout on the Web browser the most recent alarm is shown with theraised time, and the number of outstanding active alarms.

Figure 130. Recent Alarm List

Total, Most recently raised, Raised Total represents the number of alarms. Most recently raised is shown with the locationand the type of alarm, followed by the severity. The time Raised is shown based in thelocal time zone (see page 21).

[!]: This button appears when the alarm situation changes: either a new alarm is raised oran existing alarm has been cleared. Press [!] to clear this indicator.

Alarm refresh rate

MENU: ALARMS| GUI SETTINGS

Figure 131. GUI Settings

This refresh rate is specific for every Browser connection and will be set to the defaultvalue 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 ratecan be set to 1, 5, 10, 60, 300 seconds or none/stop.





13.19 Current Alarms

The current alarms window shows all current outstanding alarms. When selecting ALARMS | CURRENT the current alarm list will be shown

Figure 132. 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 timezone (see page 21).

Details

When selecting an alarm in the list and next clicking DETAILS

the long alarm description willbe shown in a pop up window. The long alarm description will also be shown whenpointing the alarm with the mouse indicator at the alarm, not available when usingInternet Explorer 6.0.

Figure 133. Alarm Details VC12vUNEQ

To have the current alarm (see "Resolving alarms and problems guide" on page 161) listupdated to the current situation, you have to refresh it. Notifications towards theprovisioned SNMP manager will be sent autonomously.





13.20 History alarms

The System has a log for 500 cleared (history) alarms. Alarms which are cleared will beput 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 134. Alarm History List

Refresh The history list is not autonomously updated, a refresh (see "Most recent alarm bar" onpage 154) is needed. The System has a log for 500 cleared (history) alarms. It thisnumber 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 mouseindicator. 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 21).





13.21 Alarm prof iles, severit ies, reporting and LEDs

13.21.1 Severities and reporting

The alarm severity and reporting state can be provisioned per alarm type individually.

Figure 135. Alarm Profile List

13.21.2 Displaying provisioned alarm severities and reporting states

When selecting menu: ALARMS | PROFILE/SEVERITIES, the list of all alarms with the currentprovisioned 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 alarmwill be raised. Changing the severity of an active alarm will clear this alarm, and put it inthe 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 158).

13.21.3 Reporting mode

When changing the reporting state of an inactive alarm this will be effective the next timethe alarm cause is present.

Changing the state of an active alarm has a slightly different behavior. When changingthe state of an active alarm from reported to not reported this will not clear the alarm, thiswill be effective the next time this alarm will be present. When changing the state of anactive alarm from not reported to reported, so currently this alarm is present but notreported, this will be effective directly.

Figure 136. 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 reportedTrue: the alarm will be reported

13.21.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 theSystem. 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, butwhen at the same time another alarm with same severity is raised the led will be litcontinuously.

LAN Port LED indicators

The LAN port has two LED indicators:

Green LED: LAN link status. LAN communication should be possible from or to theSystem, if the link is up.

Yellow LED: LAN activity present.




Chapter 14 System reset June 2009 • ADX-7077 2055-01, Issue 2.1

14 SYSTEM RESET

The System supports two reset methods:

Warm Reset: Always try a warm reset before a cold reset. After a warm reset the PMdata and Alarm History are lost.

Cold Reset: Use a cold reset if the warm reset fails. The effect will be the same as apower down of the System. The System needs about 10 minutes to restart. In thisperiod no traffic and no management is possible. Also now the PM data and AlarmHistory are lost.

Note: After a warm reset or a cold reset you have to login again.

Note: A warm or cold reset possibly interfere transmission and traffic management.

Caution: Do NOT execute resets to often.

To reset the System use SYSTEM| RESET.

Figure 137. System Reset

Note: The System ask to confirm a warm or cold reset,. An example is given for thewarm reset.

Figure 138. Warm Reset Confirmation




Chapter 14 System reset June 2009 • ADX-7077 2055-01, Issue 2.1




Chapter 15 Resolving alarms and problems guide June 2009 • ADX-7077 2055-01, Issue 2.1

15 RESOLVING ALARMS AND PROBLEMS GUIDE

15.1 Introduction

This section describes the alarms which can be reported by the System, a description isgiven 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 sectionprovides information to support in their tasks to resolve alarms or analyze end customercomplaints.

Current alarms are identified by the location, alarm type, severity and a time stamp of theraise time.

15.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 lineport (LPa) in case of MSP.

VC12 termination point: Identified by tributary slot number, followed by the portnumber.

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) incase of MSP.

TU alarm: identified by line port number, LP1, LP2 or the active line port (LPa) incase of MSP, followed by the klm indication.

15.3 Alarm list overv iew

The table shows all defined alarm types and their default severity and default LED state.

Table 12. Alarm Types with Default Severity and LED Indication Alarm type Default Severity Default LED state Default Reporting

AU4cAIS (see page 168) Minor None Yes

AU4cLOP (see page 168) Major Red Yes

E12cAIS (see page 166) Minor None Yes

E12cLOS (see page 166) Major Red Blinking Yes

ENVcDI (see page 171) Major None No

IFCcEQF (see page 165) Major Red Yes

IFCcREPL (see page 165) Major Red Yes

IFCcUNP (see page 164) Major Red Yes

IFCcWUI (see page 164) Major Red Yes

MS1cAIS (see page 167) Minor None Yes

MS1cDEG (see page 167) Minor Yellow Yes

MS1PcFOP (see page 168) Major Red Yes

MS1cRDI (see page 167) Minor None Yes

MS1cSSF (see page 167) Major None Yes

MS1PcSSF (see page 167) Major None Yes





Alarm type Default Severity Default LED state Default Reporting

P12sNBBEcTHR15 (see page170)

Minor None Yes

P12sNBBEcTHR24 (see page170)

Minor None Yes

P12sNEScTHR15 (see page 170) Minor None Yes

P12sNEScTHR24 (see page 171) Minor None Yes

P12sNSEScTHR15 (see page171)

Minor None Yes

P12sNSEScTHR24 (on page 171) Minor None Yes

P12sNUAScTHR15 (see page171)

Minor None Yes

P12sNUAScTHR24 (on page 171) Minor None Yes

RS1cSSF (see page 167) Major None Yes

RS1cTIM (see page 167) Major Red Yes

SFPcEQF (see page 165) Major Red Yes

SFPcUNP (see page 165) Major Red Yes

SFPcWUI (see page 165) Major Red Yes

STM1cLOF (see page 166) Major Red Yes

STM1cLOS (see page 166) Major Red Blinking Yes

SYNCcBHO (see page 165) Major Red Yes

SYNCcLRR (see page 166) Major Red Yes

SYNCcTLF (see page 166) Major Red Yes

SYScDBBCKP (see page 163) Major None Yes

SYScEQF (see page 164) Major Red Yes

SYScPFA (see page 164) Major Red No

SYScPFB (see page 164) Major Red No

SYScROUTE (see page 164) Minor Yellow Yes

SYScTIME (see page 163) Major Red Yes

TU12cAIS (see page 169) Minor None Yes

TU12cLOP (see page 169) Major Red Yes

VC12cDEG (see page 170) Minor Yellow Yes

VC12cPLM (see page 170) Major Red Yes

VC12cRDI (see page 170) Major None Yes

VC12cSSF (see page 169) Major None Yes

VC12cTIM (see page 170) Major Red Yes

VC12cUNEQ (see page 169) Major Red Yes

VC4cDEG (see page 169) Minor Yellow Yes

VC4cLOM (see page 169) Major Red Yes

VC4cPLM (see page 168) Major Red Yes

VC4cRDI (see page 169) Minor None Yes

VC4cSSF (see page 168) Major None Yes

VC4cTIM (see page 168) Major Red Yes

VC4cUNEQ (see page 168) Major Red Yes

15.3.1 Alarm type

This is a short name (mnemonic) of the fault cause according to the ITU standards:G.783, G.784 and G.806.

15.3.2 Severity

This identifies the provisioned severity for the alarm. The default severity (see "Alarmprofiles, severities, reporting and LEDs" on page 157) is listed by the descriptions.





15.3.3 Time stamp

The time stamp identifies the raise time of the alarm. This time is based on the Systemtime of the System (see page 21).

15.3.4 Reporting state

The default reporting state for all alarms is reported, except for the SYScPFA andSYScPFB alarm. When an alarm is required not to be reported this can be provisioned(see "Alarming" on page 154).

15.3.5 Monitoring mode

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

15.3.6 Pluggable item state

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

15.3.7 Replacing Systems

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

15.4 Alarm descr ipt ions

The alarm descriptions are shown as:

Alarm description.

Impact of the alarm.

Cause and action to clear the alarm.

15.4.1 System Alarms

SYScDBBCKPThis alarm is raised when a database backup failed. It is cleared when a databasebackup finished successfully. The same alarm is used for autonomous database backupsas well as for the 'Backup Now' functionality.

SYScTIME

The System time is not set or lost. The System time is running from start up on the defaultlinux clock.

Alarms will be reported with a wrong timestamp, not the real time.

System time has not been provisioned (see "System" on page 88). Or System time hasbeen 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 poweringon feed A is unavailable.

No power connected to power feed A. Or voltage is below 40.5 Volt. Or the -48 and 0connections are swapped, the System will operate but a SYScPFA is reported. Thedefault reporting state is not reported, When monitoring is required the state must be setto reported.

SYScPFB

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

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

No power connected to power feed B. Or voltage is below 40.5 Volt. Or the -48 and 0connections 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 setto 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 33).

15.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 InterfaceCard or when no Interface Card is desired for this slot position change the slot state to AUTO. (see page 91)

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 willbe shut down. When a port of the Interface Card is assigned as timing source thisreference is declared failed with a SYNCcTLF, to prevent synchronization from an invalidreference.

The inserted interface card has a not supported item code. Replace the Interface Card bya supported type.





IFCcREPL

A different Interface Card as the previous inserted one has been inserted. But the itemcode 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 91). Take care cabling is according to this InterfaceCard.

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 belost. When a port of the Interface Card is assigned as timing source this reference isdeclared 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 93).

SFPcWUI

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

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

Reinsert an SFP with an identical module qualifier as the last accepted one. or changethe state to AUTO and the System will set the current inserted SFP to operational (seepage 94).

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 beaffected.

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

15.4.3 Synchronization alarms

SYNCcBHO

System timing has fall back to hold over mode. The System is running on its hold overclock. 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 dohave 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 referenceassigned 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 theinternal clock of the System.

This timing source will not be part of the System timing selection. When anotherreference is available the System timing will select that one. When no other timing sourceis available the System timing will switch to holdover and the SYNCcBHO will bereported.

Check the signal provided to the timing source has a defect and resolve that cause, or ifnone 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 Systemconnected 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 whySystem timing QL has decreased.

15.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 inthe 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 theSystem connected to the E1 port.

Check alarms on the System connected to the E1 port

STM1cLOSThe identified line port has a loss of signal detected.

Transmission via this line port in the downstream direction is lost. In the downstreamdirection 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

Transmission via this line port in the downstream direction is lost. In the downstreamdirection 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 inputmight be overloaded (to much optical power).





15.4.5 Termination point alarms

RS1cTIM

A trail trace identifier mismatch has been detected on the identified line port.

Transmission via this line port in the downstream direction is lost. In the downstreamdirection 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 tothe wrong far end system or port.

RS1cSSF

A server signal fail on the RS layer has been detected for the identified line port. The rootcause 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 rootcause 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 orRS1cTIM.

MS1PcSSF

A server signal fail has been detected on the MS1 protection layer, only applicable whenMSP 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 lineport.

MS1cAIS

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

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

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 doesexceed the provisioned degraded threshold (see "Degraded Threshold provisioning andhandling" on page 115).

Transmission is affected as bit errors will disturb the signal.





The STM-1 signal received has a degraded quality due to too much attenuation ordispersion. Check the optical path or the SFP being used at the far end has insufficientpower. In some cases overload of the input signal might lead to an MS degraded signal.

MS1PcFOP

STM-1 MS Protection switching protocol failure.

This alarm is raises if there is a configuration mismatch between the Near End and FarEnd node of a bi-directional MSP group.

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 MSand 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 upstreamdirection.

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 upstreamdirection VC4 RDI is inserted.

The far end system connected to might not have a VC4 cross connection towards thissystem.

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 TUGstructured (02) but a different kind of traffic. Check in the details of the related VC4 TTPthe accepted TSL value. The far end system does have wrong type of traffic. TheVC4cPLM 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 andTIM detection is enabled.

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





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

VC4cDEGThe number of background block errors in the received B3 byte do exceed theprovisioned 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 atthe far end system.

TU12cAIS

The TU12 contains AIS. The TU12cAIS is identified by the TU12 number(klm) at the lineport 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 theTU12 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 andVC12 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 isinserted. In the upstream direction VC12 RDI is inserted. When provisioning crossconnects on both side of a connection, temporarily a VC12cUNEQ might be raised due tothe absence of the cross connect at the far end.

The far end system connected to might not have a VC12 cross connection towards thissystem or any other System in the transmission path.





VC12cPLM

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

Transmission is lost in the downstream direction. For a VC12 trail termination point AIS is

inserted.

The VC12 coming from the far end system does not have a label 01 (equipped) orasynchronous (02) but a different kind of traffic. Check in the details of the related VC12TTP the accepted TSL value. The far end system does have wrong type of traffic. TheVC12cPLM alarm is not under control of the monitoring flag.

VC12cTIM

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

Transmission is lost in the downstream direction. For a VC12 trail termination point AIS is

inserted. In the upstream direction VC12 RDI is inserted.Check the expected and accepted trail trace. A difference might be due to a wrong crossconnect in the transmission path between the near and far end VC12 TTP. If no match isrequired TIM detection can be disabled thus no alarms is raised and no consequentactions are executed.

VC12cDEG

The number of background block errors in the received TU BIP byte exceeds theprovisioned 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 atthe far end system.

15.4.6 Performance monitoring alarms

P12sNBBEcTHR15

The number of BBE errors for the 15m bin exceeds the threshold. (see page 145)Transmission is affected as bit errors will disturb the signal.

P12sNBBEcTHR24

The number of BBE errors for the 24h bin exceeds the threshold. (see page 145)


P12sNEScTHR15

The number of ES errors for the 15m bin exceeds the threshold. (see page 145)






P12sNEScTHR24

The number of ES errors for the 24h bin exceeds the threshold. (see page 145)


P12sNSEScTHR15The number of SES errors for the 15m bin exceeds the threshold. (see page 145)


P12sNSEScTHR24

The number of SES errors for the 24h bin exceeds the threshold. (see page 145)


P12sNUAScTHR15

The number of UAS errors for the 15m bin exceeds the threshold. (see page 145)


P12sNUAScTHR24

The number of UAS errors for the 24h bin exceeds the threshold. (see page 145)


15.4.7 Digital input alarms

ENVcDI

A digital input alarm raised due to a customized digital input.

Transmission is not affected.

Check the cause of the alarm.

15.5 SDH overview

15.5.1 SDH multiplex s tructure

Figure 139. SDH Multiplexing Structure





15.5.2 SDH termination points

Figure 140. SDH Termination Points





SDH Events

Table 13. 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 clockmonitor

K2 APS signaling byte

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 backwardstatus

B3 Error monitor J2 Trace identifier

G1 Backward path status

H4 TU pointer





15.6 Synchronization Network

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





15.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 2Provisioning System 3





Timing source 2: Assigned to Line port 1, Q: AUTO, priority 3

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 highestpriority.

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.





15.6.1.1 Network failure 1

Interesting is to see what happens when a failure occurs. In the figure a failure on thePRC clock is present. The Systems will switch over to their next best reference. At firstinstance 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 source1. System3 will retain at Timing source 1 and System2 will retain at Timing source 1.

Figure 142. Timing Network with Failure 1





15.6.1.2 Network failure 2

In the figure a failure has occurred on the incoming side of Line port 2 on System2. In thiscase System2 will switch over from Timing source 1 to Timing source 2 (LP1). The otherSystems do not switch over.

Figure 143. Synchronization Failure




Chapter 16 Support Tools June 2009 • ADX-7077 2055-01, Issue 2.1

16 SUPPORT TOOLS

This section describes the use of HiThere (see page 179).

16.1 HiThere

The HiThere (see page 179) utility can be installed on a Windows PC. This utility is a.o.used:

to discover the Systems on the subnet the PC is connected to.

for LAN provisioning.

for SNMP alarm trapping.

Each System is installed with a HiThere server program. The System responds with itsMAC address, IP address, subnet mask, IP default gateway and host name.

The screen below shows all HiThere windows.

Figure 144. HiThere windows

The visibility of these windows can be enabled or disabled with the View menu (see"HiThere menu structure" on page 180). The windows are:

1. Local Systems log.

The SNMP frames:2. SNMP Trap log.

3. Alarm Management for Monitored Systems.

4. Alarm Management for Not Monitored Systems.

16.1.1 Starting HiThere for the first time

After installation HiThere can be started with the Windows Start menu. The followingscreen appears.





16.1.3 Find systems on a local subnet

To find the systems on a local subnet:

1. Enter the Used Host Interface.

2. Select menu: TOOLS| FINDSYSTEMS ON A LOCAL SUBNET.

In the figure below one System is connected to the local subnet of the PC.

Figure 146. Find the systems on a local subnet

You can select a System from the Local Systems log and with the pop up menu you havethe following options:

GUI, to login on the System (see "Login on a System" on page 182).

IP PING, to ping to the System (see "Ping to a System" on page 182).

ASSIGN LOCALSYSTEM IP ADDRESS, to modify the IP address of the System (see "Assign anIP address to a System" on page 183).

ENABLE ALARMMONITORING, to see the alarms of this System (see "Enable AlarmMonitoring" on page 183).

CLOSE, to close.the pop up menu.





16.1.3.1 Login on a System

To login on a System with HiThere:

1. Select a System from the window Local Systems log.

2. Select GUI from the pop up menu.The login screen for the System appears.

Figure 147. Login to a System using HiThere

You can use VIEW | CLEAR LOCALSYSTEMS LOG to clear the local Systems log.

16.1.3.2 Ping to a System

To Ping to a System with HiThere:


2. Select IP PING from the pop up menu.

The Ping results are displayed in the fields Currently Selected IP Address and Last IPPing response, as shown in the figure below.

Figure 148. Ping results





16.1.3.3 Assign an IP address to a System

When a System does not have an IP address, for example when DNS is not supported,you can use HiThere to assign an IP address to the system. The System is identified byits MAC Address.

To assign an IP address to a System with HiThere:


2. Select ASSIGN LOCALSYSTEMIP ADDRESS from the pop up menu.The window as shown below appears.

Figure 149. Assign IP Address

3. Use the MAC address to connect to the System.

4. Fill in the required IP address data for this System.Use Validate input , checks if the IP address entered already exists on the localsubnetwork. The user is warned about this.

5. Click Ip2Box.

16.1.3.4 Enable Alarm Monitoring

To assign an IP address to a System with HiThere:

1. Select a System from the window Local Systems log.2. Select ENABLE ALARMMONITORING from the pop up menu.

The System is added to the window that displays the Monitored Systems (see "Alarmmanagement of monitored and non monitored Systems" on page 185).





16.1.4 Find and add SNMP systems for alarm monitoring

To find the SNMP systems:

1. Select menu: TOOLS| FINDSNMP SYSTEMS

The screen below appears.Figure 150. Find SNMP systems

2. Enter the IP Address Range and Read Community

3. Click Discover A list of SNMP Systems appears, if any.

Figure 151. Export Found SNMP systems

4. Select the System(s) you want to monitor.

5. Click Export The System(s) is (are) added to the Monitored Systems (see "Alarm management ofmonitored and non monitored Systems" on page 185).





16.1.5 Alarm management of monitored and non monitored Systems

HiThere only performs alarm management of Systems which are provisioned (see"SNMP" on page 142) to be managed to do so.

Alarm management can be activated with the menu TOOLS| START ALARMM ANAGEMENT. Once itis active (left screen below) it can be de-activated with TOOLS| STOP ALARMM ANAGEMENT. The Active indication changes into Inactive.

Figure 152.

IP Address The Address of the Monitored System.

# Alarms The number of alarms. If the value is shown between an opening and closing bracketthen this value is not synchronized with the System. However is will be increased on araise of an alarm and decreased on a clear of an alarm. But it remains not synchronized.To synchronize the # Alarms field with the System, select the System in the MonitoredSystem screen and from the pop up menu select Get Alarms. Now the brackets willdisappear and the value will be updated and immediately and the alarms will remainsynchronized with the system.





Figure 153. Get Alarms

16.1.5.1 Getting alarms

This feature is described in the previous section (see "Find and add SNMP systems foralarm monitoring" on page 184).

16.1.5.2 View system details

To view the System details use the pop up menu is the Monitored Systems and selectSystem Details. HiThere will retrieve the details from the system and they will bedisplayed as shown below. The information is read-only.

Figure 154. View system details

16.1.5.3 Add or Remove a System for alarm monitoring

To add or remove a System, go to the Monitored Systems screen and from the pop upmenu select Edit Alarm Monitoring .





Figure 155. Add a system for alarm monitoring

IP Address Address of the remote system to add or remove.

Read Communit yRead Community of the remote system to add or remove.

Alarm Community Alarm Community of the remote system to add or remove. This field is read only.

Submit

Is used to add the System to the monitored systems.

Remove Is use to remove the System to the monitored systems.

Reset Undo all editing in the fields IP address and read Community.

16.1.6 SNMP trap log

In this screen all autonomous messages of the nodes in the network are displayed. Thegathered data contains of an Index (just a sequence number) IP address, Community ,Source, Type (of error), Status, Severity and a TimeStamp. The figure below also show

the pop up menu for the Trap log.You can use VIEW | FREEZESNMP TRAP LOG TO FREEZE the SNMP trap log and VIEW | CLEARSNMP

TRAP LOG to clear the SNMP trap log.

Figure 156. SNMP trap log

GUI This feature is described in another section (see "Login on a System" on page 182).

IP PING This feature is described in another section (see "Ping to a System" on page 182).

ENABLE ALARMMONITORING

This feature is described in another section (see "Enable Alarm Monitoring" on page 183).




Chapter 17 List of acronyms and abbreviations June 2009 • ADX-7077 2055-01, Issue 2.1

17 LIST OF ACRONYMS AND ABBREVIATIONS

This section gives an overview and detailed description of acronym and abbreviations.

ALM

Alarm

AIS

Alarm Indication Signal

APS

Automatic Protection Switching

AS

Autonomous System

ASBR

Autonomous System Border Router

AU

Administrative Unit

AUG

Administrative Unit Group

BBEBackground Block Error

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





DI

Digital Input

DNU

Do Not Use

E1

2 Mb/s signal according to ITU-T G.703

EMC

Electro-Magnetic Compatibility

EN

Engineering Norms

ESDElectro-Static Discharge

ETSI

European Telecommunication Standardization Institute

ES

Errored Seconds

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

LEDLight Emitting Diode





LP

Line Port

LSA

Line Separator Adaptor

MAC

Media Access Control

MON

Monitor

MS

Multiplex Section

MSAMulti-Source Agreement

MSP

Multiplex Section Protection

MTBF

Mean Time Between Failure

OSPF

Open Shorted Path First

PM

Performance Monitoring

PPM

Parts Per Million

PRC

Primary Reference Clock

RMA

Return Material Authorization

QL

Quality Level (timing quality)

RS

Regenerator Section

SDH

Synchronous Digital Hierarchy

SECSDH Equipment Clock





SELV

Safety Extra-Low Voltage

SES

Severely Errored Seconds

SFP

Small Form factor Pluggable

SNMP

Simple Network Management Protocol

SSM

Synchronization Status Message

SSU-LSynchronization 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

Trail Termination Point

TU

Tributary Unit

TUG

Tributary Unit Group

UAPUnAvailable time Period





UAS

UnAvailable Seconds

VC-n

Virtual Container of nth level

WTR

Wait To Restore




Chapter 18 Index June 2009 • ADX-7077 2055-01, Issue 2.1

18 INDEX

A

ABOUT THIS MANUAL • 9Access to related items • 77

Accessories • 49, 62Active leg • 128Add or Remove a System for alarm

monitoring • 186Add/Delete PM points • 145Adding cross connects • 123

Address resolution protocol (ARP) • 34ADX100 • 28ADX100 for LSA-PLUS PROFIL rod

mounting • 51ADX100 GUI System Overview • 80

ADX100 Interfaces • 24ADX100 Login screen • 79

ADX100 with 2 Mb/s E1 connections •52

ADX100 without Interface Cards • 56ADX100, ADX200 and ADX201

differences • 87ADX200 • 29, 61

ADX200 GUI System overview • 81ADX200 Interfaces • 24ADX200 Login screen • 81ADX201 • 29, 62ADX201 GUI System overview • 77,

82ADX201 Interfaces • 25ADX201 Login screen • 82AIS • 189Alarm descriptions • 163Alarm list overview • 99, 161Alarm management of monitored and

non monitored Systems • 183, 184,185

Alarm profiles, severities, reportingand LEDs • 153, 157, 162

Alarm reporting • 22Alarm type • 162

Alarming • 146, 154, 163Alarms menu • 84

ALM • 189APS • 189Area Border Router (ABR) • 33, 148AS • 189

ASBR • 189Assign an IP address to a System • 181,

183Assigning IP addresses for system

management • 35, 74AU • 189

AU4cAIS • 161, 168

AU4cLOP • 161, 168AUG • 189

Autonomous System Border Router(ASBR) • 33, 34, 148

Availability • 30

Avoiding management problems with proxy ARP • 44

B

BBE • 189

BCG • 189Bidirectional • 128Bidirectional cross connects • 123Blank Face plate installation • 57

C

Cables and pinning • 65, 67CAS • 189CI • 189Clickable items via System layout • 77

CO • 189Connect Power, SFPs and fibers or

coax • 61Connecting 2 Mb/s (E1) Interfaces •

53, 56Connecting interfaces • 54, 56, 58, 61,

65

Connecting power • 65Connection • 87Connectors • 71Consequent action • 87CRC • 189Creating an MSP pair • 129

Cross connects • 22, 119CTP • 189Current alarm list with SNMP • 143Current Alarms • 155Customer information and assistance •

12

D

Database backup via FTP • 103, 162Database maintenance manually • 101

Database restore via FTP • 103, 105DC power cable • 67

Definitions • 120, 128, 134Degraded • 128Degraded Threshold provisioning and

handling • 45, 111, 113, 114, 115,

126, 127, 128, 167Deleting an MSP pair • 130

Description of the interfaces • 24Designated router and the backup

designated router • 34, 150DHCP • 189DI • 190Digital input alarms • 161, 171

Digital inputs • 23, 69, 153Dimensions and weight • 28Disclaimer of liability • 2





Displaying provisioned alarm severitiesand reporting states • 157

Distribution of manual routes • 23

DNU • 190Documentation conventions • 9Downstream • 87

E

E1 • 190E1 incoming loopback • 48E1 interfaces • 25E1 outgoing loopback • 48E1 retiming • 22E12cAIS • 88, 161, 166

E12cLOS • 88, 161, 166Editing cross connects • 125Egress • 87EMC • 190

EN • 190Enable Alarm Monitoring • 181, 183,

187ENVcDI • 171Environmental • 15, 30Environmental precautions • 18ES • 190ESD • 190

ESD and EMC • 15ETSI • 190ETSI COMPLIANCE STATEMENTS

• 15Example with ASBR • 42, 43

Example with proxy ARP • 43Exchange ADX100 Main Module • 58

External MSP switch requests • 132External switch requests • 129, 131

F

Far end • 87, 128

Feature descriptions • 20Field colors convention • 77Find and add SNMP systems for alarm

monitoring • 184, 186Find systems on a local subnet • 181FTP • 23

G

GENERAL INFORMATION • 11

General notices • 49GENERAL SAFETY PRECAUTIONS

• 17Getting alarms • 186GND • 190GUI features • 77GUI settings • 77GUI SETTINGS AND SYSTEM

AUTHORIZATION • 77

H

Hardware specifications • 27

HDB-3 • 190Help menu • 85History alarms • 156

HiThere • 74, 76, 179HiThere menu structure • 179, 180HiThere utility • 74

I

IDC • 190IEEE • 190IFC • 190IFC replacement. • 92IFCcEQF • 161, 165IFCcREPL • 161, 165

IFCcUNP • 161, 164IFCcWUI • 161, 164Ingress • 87Inserting interface cards • 65

Inserting SFPs • 65Install ADX100 Main Module • 60

Install Interface Cards • 61Install software manually • 97Install software via FTP • 98, 103Installation guide • 18, 72INSTALLATION GUIDE • 49Interface Card • 91, 164, 165

Interface Card installation • 56, 61Interface Cards • 71Interfaces • 30Introduction • 45, 87, 161Inventory management • 21

IP address management • 72, 83IP management without DHCP server •

72ISD • 190ITU-T • 190

K

Key features • 19

L

LAN • 190LAN - Power over Ethernet cable • 67

LAN connector • 71, 72LAN port provisioning via WEB

browser • 75, 150LAN ports • 75

LAN provisioning via HiThere • 76LED • 190

LED indicators • 157, 158Line ports • 74, 109Line Protection (MSP) • 21Line protection and OSPF • 35Link costs and signal rate • 35, 149,

150

LIST OF ACRONYMS ANDABBREVIATIONS • 189

Listing, editing and deleting crossconnects • 122





Local Management console port • 71Local management, host directly

connected to System LAN and no

routing protocol • 36Location • 161Log file • 20Log file for System settings • 83, 106Log files • 106Log files manually • 106

Log files via FTP • 103, 106, 107Login on a System • 181, 182, 187

Loopback • 23LP • 191LSA • 191

M

MAC • 191Maintenance menu • 84

Management and remote management •151

MANAGEMENT AND REMOTEMANAGEMENT • 33

Manual route add/delete • 151Mapping • 31Mechanical precautions • 18Menu structure • 83

MON • 191Monitoring mode • 163Most recent alarm bar • 154, 156Mount Frame • 61Mounting and installation ADX100 •

27, 28, 51Mounting instructions ADX200 and

ADX201 • 61Mounting material 200 (included in

box) • 62Mounting material ADX201 (included

in box) • 62Mounting the ADX200/ADX201 • 62

Mounting to profile rods • 53, 56MS • 191MS1cAIS • 161, 167MS1cDEG • 161, 167MS1cRDI • 161, 167

MS1cSSF • 161, 167MS1PcFOP • 161, 168MS1PcSSF • 161, 167MSA • 191MSP • 191MSP and alarming • 129MSP details • 130

MSP menu • 85MTBF • 191

Multiple hosts and mix applications •41

N

Near end • 87, 128 Network failure 1 • 176

Network failure 2 • 177 Non-revertive • 128 Numbered and unnumbered interfaces •

34, 74

O

Open shortest path first (OSPF) • 33,164

OSPF • 191OSPF Interfaces • 149OSPF LAN/LP Interfaces • 150OSPF provisioning • 148OSPF settings • 148OSPF Systems • 151

Outgoing SSM • 135Overhead functions • 22

P

P12sNBBEcTHR15 • 162, 170P12sNBBEcTHR24 • 162, 170P12sNEScTHR15 • 162, 170P12sNEScTHR24 • 162, 171P12sNSEScTHR15 • 162, 171P12sNSEScTHR24 • 162, 171P12sNUAScTHR15 • 162, 171

P12sNUAScTHR24 • 162, 171Path protection • 23Performance monitoring • 23, 144Performance monitoring alarms • 170Ping to a System • 181, 182, 187Pluggable item state • 163

Pluggable items • 21, 71, 90, 163, 164PM • 191PM Current Data View/Reset/Refresh •

144, 146PM History data View • 144, 147PM menu • 85PM overview • 144

PM Threshold • 144, 145, 170, 171PM UAP Log • 144, 147Port alarms • 166Port loopback functionality • 110PORT LOOPBACK

FUNCTIONALITY • 47

Port provisioning • 74Ports • 108Ports and termination points • 108, 120,

163Post • 13Power • 30

Power precautions • 17Powering • 21, 72PPM • 191PRC • 191Precautions • 127Product information and technical

assistance by e-mail • 14

Protection • 128Provisioning • 20, 33, 80, 83





PROVISIONING • 87Provisioning aspects • 46Provisioning for this network • 175

Provisioning IP address with DHCPclient • 74

Provisioning line port references • 136,138

Provisioning timing sources • 133, 135Provisioning trail trace identifiers • 116

Provisioning tributary port references •138

Provisioning via local console port •73, 74

Q

QL • 191QL timing source • 135QL-in • 134

Quality Level (QL) • 134

R

Real Time Clock • 21, 143, 154, 155,156, 163

Reference Fail • 134Refresh button • 77

Remote error indication • 119Remote management • 23Remote management examples • 38Remove and Insert label holders

ADX100 • 55, 56Removing interface cards • 66

Removing the frame • 59Repair / exchange policy • 11Repair charges • 11Replacement / spare products • 11Replacing Systems • 163Reporting mode • 153, 157Reporting state • 163

Resolving alarms and problems guide •9, 111, 113, 114, 155

RESOLVING ALARMS ANDPROBLEMS GUIDE • 161

Restart of browser after Systemrecovery • 78

Retiming E1 ports • 110, 139, 140Returned material • 12Revertive • 128Revision History • 2RMA • 191Rod and rack specifications • 52, 56

Routers for OSPF • 33Routing examples • 36RS • 191RS and MS section • 110RS1cSSF • 162, 167RS1cTIM • 162, 167

S Safety • 15

Safety precautions • 17Safety warnings • 9SDH • 191

SDH Events • 173SDH multiplex structure • 120, 171SDH overview • 171SDH termination points • 121, 172SEC • 191Select inactive ISD • 96

SELV • 192Serial / Console cable • 68

SES • 192Set up of the System • 80, 81, 82SET UP OF THE SYSTEM • 71Severities and reporting • 157

Severity • 162SFP • 192SFP modules • 71SFP replacement and acceptance • 94,

165SFPcEQF • 162, 165

SFPcUNP • 162, 165SFPcWUI • 162, 165Short ordering list • 22, 32, 88, 91, 92Signal fail • 128Simultaneous sessions • 77Single and Dual fiber SFPs • 22

Single Fiber SFPs • 94Small Form Pluggable • 93, 165Smart defaults • 102Smart selection • 77

SNCP Cross connects uni- and bidirectional • 119, 123, 124, 126SNMP • 22, 142, 185, 192

SNMP trap log • 187Software service agreement • 11SPECIFICATIONS • 27SSM • 192SSM based algorithm • 140SSM byte • 134

SSU-L • 192SSU-T • 192Standby leg • 128Starting HiThere for the first time • 179

STM-1 • 192STM-1 outgoing loopback • 48

STM1cLOF • 162, 166STM1cLOS • 162, 166SUBNETWORK CONNECTION

PROTECTION (SNCP) • 45SUPPORT TOOLS • 179Supported areas • 33

Switch criteria • 128SYNCcBHO • 162, 165

SYNCcLRR • 162, 166SYNCcTLF • 162, 166Synchronization • 22, 31, 109, 133

Synchronization alarms • 165Synchronization Network • 134, 174SYScDBBCKP • 163





SYScEQF • 162, 164SYScPFA • 162, 164SYScPFB • 162, 164

SYScROUTE • 33, 162, 164SYScTIME • 89, 90, 162, 163System • 88, 163System Alarms • 163System and host connected to an access

network • 36, 37

System and host in the same subnet •36, 37

System database • 20, 99SYSTEM DESCRIPTION • 19System menu • 84System overview and features • 19

System recovery • 94System reset • 144SYSTEM RESET • 159System software • 9, 20, 94, 95System Time • 89System time from server(s) • 89

System time manually • 89System timing • 138, 139System timing reference selection •

137, 139, 140

T

Telecom power feed • 71Telephone • 12Terminal application and host

connected to LAN • 38

Termination point alarms • 167Termination Points • 110, 117

Test access output • 71, 81, 83, 118,121

Test access port • 21Test connector • 65The proxy address resolution protocol

(PARP) • 34

TIM • 192Time stamp • 163Timing menu • 85Timing source • 134To become an ASBR • 34

Tools • 49TP • 192Trademark Information • 2Trail Trace Identifier modes • 116, 126Trail Trace Identifier provisioning and

handling • 111, 112, 114, 116Transmission menu • 85

Transmission protection MSP • 112,127

Transmission terms and definitions •87

Tributary Ports • 48, 109, 123Tributary slots • 21

TS • 192TSL • 192

TTI • 192TTP • 192TU • 192

TU12cAIS • 162, 169TU12cLOP • 162, 169TUG • 192

U

UAP • 192UAS • 193Unidirectional • 128Unidirectional cross connects • 123,

124Update after edit • 77

Upstream • 87Use of wiring brackets • 63User administration • 20User groups, login and rights • 78, 83

V

VC12 termination point • 110, 113, 126VC12cDEG • 162, 170VC12cPLM • 162, 170VC12cRDI • 162, 170VC12cSSF • 162, 169

VC12cTIM • 162, 170VC12cUNEQ • 162, 169VC4 termination points • 110, 111VC4cDEG • 162, 169VC4cLOM • 162, 169VC4cPLM • 162, 168

VC4cRDI • 162, 169VC4cSSF • 162, 168VC4cTIM • 162, 168VC4cUNEQ • 162, 168VC-n • 193View system details • 186Visual indicators • 21

W

Wait to Restore (WTR) • 129

Warranty / software • 11Web browser and navigation • 77

Web server • 22Wire routing • 64Worker • 128WTR • 193

X

XConnects menu • 85

user manual adx

Documents