Active Digital Cross-Connect

ASX System
User Manual

ADCP-80-578 • Issue 2 • 8/2008

1449203 Rev A
ADCP-80-578 • Issue 2 • 8/2008 • Preface

COPYRIGHT
© 2008, ADC Telecommunications, Inc.
All Rights Reserved

REVISION HISTORY
ISSUE DATE REASON FOR CHANGE
1 10/2007 Original.
2 08/2008 References to a blinking LED on powerup were deleted on pages 20, 62, 65, 118, and 119; LED defini-
tion was removed from page xii; section 6.5.1. was deleted; typo in Figure 2 on page 1 was corrected.

TRADEMARK INFORMATION
ADC is a registered trademark of ADC Telecommunications, Inc.

DISCLAIMER OF LIABILITY
Contents herein are current as of the date of publication. ADC reserves the right to change the contents without prior notice. In no
event shall ADC be liable for any damages resulting from loss of data, loss of use, or loss of profits and ADC further
disclaims any and all liability for indirect, incidental, special, consequential or other similar damages. This disclaimer of
liability applies to all products, publications and services during and after the warranty period.
This publication may be verified at any time by contacting ADC’s Technical Assistance Center at 1-800-366-3891, extension 73475
(in U.S.A. or Canada) or 952-917-3475 (outside U.S.A. and Canada), or by e-mail to [email protected].

ADC Telecommunications, Inc.

P.O. Box 1101, Minneapolis, Minnesota 55440-1101
In U.S.A. and Canada: 1-800-366-3891
Outside U.S.A. and Canada: (952) 938-8080
Fax: (952) 917-1717

Page ii
 ADCP-80-578 • Issue 2 • 8/2008 • Preface

TABLE OF CONTENTS

Content Page

About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix

Admonishments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
General Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix
Standards Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
ESD and EMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
List of Acronyms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
1 PRODUCT DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 System Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 ASX Panel Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4.1 LAN Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4.2 Craft Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4.3 Power Feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4.4 Ground Stud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4.5 Optical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4.6 Alarm Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.5 ASX GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.6 System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.6.1 Summary of System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.6.2 System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.6.3 System Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.6.4 User Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.6.5 Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.6.6 Real Time Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.6.7 Powering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.6.8 Pluggable Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6.9 Inventory Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6.10 Line Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6.11 Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6.12 E1 Retiming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6.13 Alarm Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6.14 Cross Connects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6.15 Overhead Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6.16 Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6.17 SNMP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6.18 Single and Dual Fiber SFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6.19 Path Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6.20 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Page iii
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008 • Preface

TABLE OF CONTENTS

Content Page

1.7 Summary of User Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.8 Dimensions and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2 HARDWARE INSTALLATION PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1 Overview of Equipment Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2 Unpacking and Inspection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3 Tools and Materials Required for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.4 Mounting the Panel on the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.5 Connecting the Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.6 Powering Up the Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.7 Installing Cross-Connect Jumpers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.7.1 Wire-Wrap Cross Connect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.7.2 LSA Cross Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7.3 Cross Connect Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3 PATCHING AND TESTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4 FUNCTIONAL BACKGROUND INFORMATION FOR ASX SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.1 Open Shortest Path First (OSPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.2 Supported Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.3 Routers for OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.3.1 Area Border Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.3.2 Autonomous System Border Router (ASBR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.3.3 Designated Router and the Backup Designated Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.3.4 Unnumbered Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.4 Address Resolution Protocol (ARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.5 Proxy Resolution Protocol (PARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.6 Link Costs and Signal Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.7 Line Protection and OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.8 Assigning IP Addresses for System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.9 Routing Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.9.1 Local Management, Host Directly Connected to System LAN and No Routing Protocol . . . . . . . . . . 30
4.9.1.1 System and Host in Same Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.9.1.2 System and Host Connected to Access Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.10 Route Management Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.10.1 Terminal Application and Host Connected to LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.10.2 Multiple Host and Mix Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.10.2.1 Example One: Net #2 Wants to Access Net #3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.10.2.2 Example Two: Host #1 Wants to Access a System in the SDH Ring . . . . . . . . . . . . . . . . . . . . . 35
4.10.3 Example With ASBR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.10.4 Example With Proxy ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.10.4.1 Avoiding Management Problems With Proxy ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.11 Subnetwork Connection Protection (SNCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.11.1 Non-intrusive Monitoring (NIM) of Line Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Page iv
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008 • Preface

TABLE OF CONTENTS

Content Page

4.11.2 Provisioning Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.12 Port Loopback Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5 SYSTEM SOFTWARE SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1 IP Address Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1.1 IP Management Without DHCP Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1.1.1 Provisioning via Local Console Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.1.1.2 Provisioning IP Address With DHCP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.1.2 LAN Port Provisioning via Web Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.1.3 LAN Provisioning in LP2Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.2 GUI Settings and System Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.2.2 GUI Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.2.3 GUI Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.2.4 User Groups, Logins, and Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.2.5 ASX Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.2.6 ASX GUI System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.2.7 Log File for System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.2.8 Menu Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6 WEB BROWSER (ASX GUI) WINDOWS AND PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.1 Master Index of Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.2 Transmission Terms and Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.3 System Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.3.1 System - Time Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.3.2 Changing the Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.4 Pluggable Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.4.1 Pluggable Items Selector Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.4.2 Interface Card (IFC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.4.3 IFC Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.4.4 Small Form Pluggable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.4.5 SFP Replacement and Acceptance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.4.6 Single Fiber SFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.5 System Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.6 System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.6.1 Selecting an Inactive ISD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.7 System Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.7.1 Selecting a New Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.7.2 Database Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.7.2.1 Restoring a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.7.2.2 Backing Up a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.7.2.3 Renaming a Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.7.2.4 Deleting a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Page v
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008 • Preface

TABLE OF CONTENTS

Content Page

6.7.2.5 Activating a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

6.7.2.6 Copying an Active Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.8 Ports and Termination Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.8.1 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.8.2 Line Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.8.3 Tributary Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.8.4 Termination Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.8.4.1 RS and MS Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.8.4.2 VC4 Termination Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.8.4.3 VC12 Termination Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.8.5 Degraded Threshold Provisioning and Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.8.6 Trail Trace Identifier Provision and Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.8.7 Provisioning Trail Trace Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.8.8 Remote Error Indication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.9 Cross Connects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.9.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.9.2 Listing, Editing, and Deleting Cross Connects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.9.2.1 Displaying Cross Connect Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.9.2.2 Editing a Cross Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.9.2.3 Deleting a Cross Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.9.3 Adding Cross Connects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.9.3.1 Bidirectional Cross Connects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.9.3.2 Unidirectional Cross Connects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6.9.3.3 SNCP Cross Connects Uni- and Bi-Directional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.9.3.4 Swapping Worker and Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.10 Transmission Protection MSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
6.10.1 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
6.10.2 Definitions and Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
6.10.3 Creating an MSP Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.10.4 Deleting an MSP Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.10.5 MSP Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.10.6 External MSP Switch Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
6.11 Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.11.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6.11.2 Provisioning Timing Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
6.11.3 Provisioning Line Port References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6.11.4 Provisioning Tributary Port References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6.11.5 Provisioning System Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
6.11.6 System Timing Reference Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
6.11.7 Retiming E1 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
6.12 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Page vi
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008 • Preface

TABLE OF CONTENTS

Content Page

6.12.1 Current Alarm List With SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

6.13 OSPF Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
6.13.1 OSPF Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
6.13.2 OSPF Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.13.2.1 OSPF LAN/LP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6.13.3 OSPF Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
7 ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
7.1 Most Recent Alarm Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
7.2 Alarm Refresh Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
7.3 Current Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
7.4 Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
7.5 Alarm Profiles, Severities, Reporting, and LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
7.5.1 Alarm Profile List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
7.5.2 Changing the Alarm Reported Mode or Severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
7.5.3 LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
7.5.3.1 System LED indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
7.6 Resolving Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
7.6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
7.6.2 Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
7.7 Alarm List Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
7.7.1 Monitoring Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
7.7.2 Pluggable Item State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
7.7.3 Replacing Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
7.8 Alarm Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
7.8.1 System Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
7.8.1.1 SYScTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
7.8.1.2 SYScPFA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
7.8.1.3 SYScPFB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
7.8.1.4 SYScEQF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
7.8.1.5 SYScROUTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
7.8.2 Pluggable Items Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
7.8.2.1 IFCcUNP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
7.8.2.2 IFCcWUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
7.8.2.3 IFCcREPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
7.8.2.4 IFCcEQF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
7.8.2.5 SFPcUNP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
7.8.2.6 SFPcWUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
7.8.2.7 SFPcEQF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
7.8.3 Synchronization Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
7.8.3.1 SYNCcBHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
7.8.3.2 SYNCcTLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Page vii
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008 • Preface

TABLE OF CONTENTS

Content Page

7.8.3.3 SYNCcLRR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

7.8.4 Port Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
7.8.4.1 E12cLOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
7.8.4.2 E12cAIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
7.8.4.3 STM1cLOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
7.8.4.4 STM1cLOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
7.8.5 Termination Point Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
7.8.5.1 RS1cTIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
7.8.5.2 RS1cSSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
7.8.5.3 MS1cSSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
7.8.5.4 MS1PcSSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
7.8.5.5 MS1cAIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
7.8.5.6 MS1cRDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
7.8.5.7 MS1cDEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
7.8.5.8 AU4cAIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
7.8.5.9 AU4cLOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
7.8.5.10 VC4cSSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
7.8.5.11 VC4cUNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
7.8.5.12 VC4cPLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
7.8.5.13 VC4cTIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
7.8.5.14 VC4cDEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
7.8.5.15 VC4cLOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
7.8.5.16 VC4cRDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
7.8.5.17 TU12cAIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
7.8.5.18 TU12cLOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
7.8.5.19 VC12cSSF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
7.8.5.20 VC12cUNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
7.8.5.21 VC12cPLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
7.8.5.22 VC12cTIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
7.8.5.23 VC12cDEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
7.8.5.24 VC12cRDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
7.9 SDH Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
7.9.1 SDH Multiplex Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
7.9.2 SDH Termination Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
7.9.3 SDH Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.10 Synchronization Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
7.10.1 Provisioning for This Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Page viii
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008 • Preface

ABOUT THIS MANUAL

This manual provides the following information:

• An introductory description of the ASX system;
• Instructions for installing and using the ASX panel;
• Background functional information on the ASX system;
• Software setup instructions;
• Instructions for use of the ASX GUI;
• Instructions for responding to alarms and system problems.

ADMONISHMENTS

Important safety admonishments are used throughout this manual to warn of possible hazards to
persons or equipment. An admonishment identifies a possible hazard and then explains what
may happen if the hazard is not avoided. The admonishments — in the form of Dangers,
Warnings, and Cautions — must be followed at all times. These warnings are flagged by use of
the triangular alert icon (seen below), and are listed in descending order of severity of injury or
damage and likelihood of occurrence.

Danger: Danger is used to indicate the presence of a hazard that will cause severe personal
injury, death, or substantial property damage if the hazard is not avoided.

Warning: Warning is used to indicate the presence of a hazard that can cause severe personal
injury, death, or substantial property damage if the hazard is not avoided.

Caution: Caution is used to indicate the presence of a hazard that will or can cause minor
personal injury or property damage if the hazard is not avoided.

GENERAL SAFETY PRECAUTIONS

Danger: This equipment uses a Class 1 Laser according to FDA/CDRH rules. Laser radiation
can seriously damage the retina of the eye. Do not look into the ends of any optical fiber. Do not
look directly into the optical transceiver of any digital unit or exposure to laser radiation may
result. An optical power meter should be used to verify active fibers. A protective cap or hood
MUST be immediately placed over any radiating transceiver or optical fiber connector to avoid
the potential of dangerous amounts of radiation exposure. This practice also prevents dirt
particles from entering the adapter or connector.

Danger: Do not look into the ends of any optical fiber. Exposure to laser radiation may result.
Do not assume laser power is turned-off or the fiber is disconnected at the other end.

Danger: Wet conditions increase the potential for receiving an electrical shock when installing
or using electrically-powered equipment. To prevent electrical shock, never install or use
electrical equipment in a wet location or during a lightning storm.

Page ix
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008 • Preface

Caution: Read the installation section of this manual before you connect the system to the
power source.

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

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

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

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

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

Caution: This product relies on the buildings installation for short-circuit (over current)
protection. Ensure that the protective device is rated not greater than 1 ampere.

Caution: Do not use Power over Ethernet simultaneously with Telecom power feeding.

Caution: Remove power before connecting or disconnecting ground or power wires to the
system. To ensure that all power is OFF, locate the circuit breaker on the panel board that
services the DC circuit, switch the circuit breaker to the OFF position, and tap the switch
handle of the circuit breaker in the OFF position.

Caution: Wire the DC power supply using the appropriate connectors at the wiring end. The
proper wiring is ground to ground, positive to positive, and negative to negative. Note that the
ground wire should always be connected first and disconnected last.

Caution: The system needs to be grounded during operation.

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

Page x
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008 • Preface

STANDARDS CERTIFICATION

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

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)

Safety

Safety meets:
• Electrical safety:
– According to IEC 950 and/or EN 60950-1
• CE qualification:
– According to low voltage directive 73/23/EEC and
EMC directive 89/336/EEC
• Optical safety:
– Is determined by the SFP inserted
• Thermal safety:
– Surface temperature or exposed component below 75 0C

Page xi
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008 • Preface

LIST OF ACRONYMS AND ABBREVIATIONS

The acronyms and abbreviations used in this manual are detailed in the following list:
ALM Alarm
AIS Alarm Indication Signal
AS Autonomouc System
ASBR Autonomous System Border Router
AU Administrative Unit
AUG Administrative Unit Group
BCG Broadband Connection Group
CAS Channel Associated Signaling
CI Customer Interface
CO Central Office
CRC Cyclic Redundancy Code
CTP Connection Termination Point
DHCP Dynamic Host Configuration Protocol
DNU Do Not Use
E1 2 Mb/s signal according to ITU-T G.703
EMC Electro Magnetic Compatbility
EN Engineering Norms
ESD Electrostatic Discharge
ETSI European Telecommunication Standardization Institute
IFC Interface Card
IP Internet Protocol
ISD Image System Database
ITU-T International Telecommunication Union – Technical standard group
GND Ground
GUI Graphical User Interface
LAN Local Area Network
LED Light Emitting Diode
LP International Electrotechnical Commission
LP Line Port
LSA Line Separator Adaptor
MAC Media Access Control
MON Monitor
MS Multiplex Section
MSA Multi-Source Agreement
MSP Multiplex Section Protection
MTBF Mean Time Between Failure
OSPF Open Shortest Path First
PPM Parts Per Million
PRC Primary Reference Clock
RMA Return Material Authorization

Page xii
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008 • Preface

QL Quality Level (timing quality)

RS Regenerator Section
SDH Synchronous Digital Hierarchy
SFP Small Form factor Pluggable
SNMP Simple Network Management Protocol
SSM Synchronization Status Message
SSU-L Synchronization Supply Unit - Local
SSU-T Synchronization Supply Unit - Transit
STM-1 Synchronous Transport Module - 1
TIM Trail Trace identifier Mismatch
TP Tributary Port
TS Tributary Slot
TSL Tributary Signal Label
TTI Trail Trace Identifier
TTP Trail Termination Point
TU Tributary Unit
TUG Tributary Unit Group
VC-n Virtual Container of n* level
WTR Wait to Return

Page xiii
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008 • Preface

Page xiv
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

1 PRODUCT DESCRIPTION

1.1 General Description

The ASX system combines an ASX Add Drop Multiplexer (ADM), a FLEXDSX test and patch
panel, and an ASX Remote Control Graphical User Interface (GUI). Figure 1 shows the system
components. Figure 2 shows the ASX panel, which contains the ADM and the FLEXDSX.

REMOTE
NEs ASX REMOTE
CONTROL GUI
SDH
NETWORK

LAN/
INTERNET

2 STM-1s ASX PANEL

ADM

FLEXDSX

64 E1s

LOCAL PATCH
AND TEST ACCESS 22161-A

Figure 1. ASX System Components

ADM

FLEXDSX

22167-A

Figure 2. ASX Panel

Page 1
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

1.2 System Function

The ASX System takes an STM-1 frame from an SDH optical network, separates the STM-1
frame into its component E1 frames, and routes the E1 circuits into a FLEXDSX panel,
providing the ability to cross-connect, patch, or monitor the E1 circuits at a local site. Figure 3
shows the functional components of the System.

REMOTE REMOTE ASX

NEs COMPUTER GUI

SNMP
SDH AGENT
NETWORK
LAN/ SNMP
REMOTE
INTERNET MANAGER
PROVISIONING,
ALARMS

LAN/ REMOTE
INTERNET
LOCAL
INTERNET
PROTOCOL
(IP) CRAFT
INTERFACE

ASX
ALARMS
CONTROL

LAPTOP
2 STM-1s SDH INTERFACE
ADM CARDS

ASX
PANEL
FLEXDSX ASX
CONSOLE

LEDs ALARM
CONTACTS

MONITOR
ACCESS

MO MO
O O
I I

FLEXDSX MI MI

MONITOR
EI ACCESS LOCAL
CIRCUIT NE
NE NE EXAMPLE
CROSS-CONNECT

22164-A
LOCAL NEs

Figure 3. System Function

Page 2
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Some functional features include the following:

1. SDH Network—is a high bandwidth backhaul network employing SDH protocol. SDH
(Synchronous Digital Hierarchy) is a standard used for Time-Division Multiplexing
(TDM), a scheme in which time slots are used to share network resources.
2. SDH ADM—is an SDH Add Drop Multiplexer within the ASX. It interfaces with the
optical network, either by removing (“dropping”) STM-1 frames from the network data
stream or, in a reverse direction, by inserting (“adding”) STM-1 frames into the network
data stream. STM-1 (Synchronous Transport Module) is a frame of variable length used to
combine smaller frames into a format permitting data speeds of up to 155.52 Mbit/s. An
STM-1 frame can hold as many as 63 E-1 circuits. The ADM also has a mux/demux
function. On the receiving side, it divides the STM-1 frame into eight parts, providing one
part to each of the eight Interface Cards. In the transmit direction, it receives eight signals
from the Interface Cards and aggregates them into a single STM-1 signal.
3. Interface Cards—are eight circuit boards within the ASX ADM. On the receiving side,
each card divides the signal received from the ADM into eight E1s circuits. In the transmit
direction, each card receives eight signals from the circuit modules, combines them, and
passed the combined signal to the ADM.
4. ASX Control—consists of hardware and software components that interpret and package
the STM-1 frames and interact with the System user by means of the ASX GUI. ASX
control includes SDH routing functions such as Open Shortest Path First (OSPF) routing.
5. Alarm—is a function within ASX control that discovers and report alarm conditions.
Specific alarms are reported by name to the ASX GUI. In addition, the alarm state in
general, in terms of whether any minor or major alarm exists, is reported to the ASX front
console Minor and Major Alarm LEDs and alarm contacts.
6. SNMP Agent—is a software program on the remote computer that allows a remote
SNMP manager via the internet to be notified of alarms as well as to query and set some
system parameters.
7. LAN/INTERNET—is the network that provides the connection between the ASX and the
remote computer on which the ASX GUI is running. This may be a Local Area Network
(LAN) or any network connected to the LAN via the internet.
8. ASX GUI—is a Graphical User Interface providing remote control of the ASX. Using the
ASX GUI, the remote user provision signals and alarm thresholds, maintain a system
database, query for alarms, and so on.
9. Craft Interface—is a local interface that allows an onsite service technician to interact
with the ASX using a laptop computer.

10. FLEXDSX—is a cross-connect panel built into the ASX. Onsite personnel can use this
panel to cross-connect or patch E-1 circuits to local Network Elements. The panel also
provides test and monitor access to the E-1 circuits. The panel accommodates up to 16
circuit modules, each capable of providing access to four E-1 circuits, for a total of up to
63 E-1 circuits per panel.

Page 3
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

1.3 ASX Panel Components

The ASX panel is available in two models, wire-wrap and LSA. Figure 4 shows the main
external components of the panel.

ALARM CONTACTS KRAFT

MAJOR MINOR INTERFACE
ASX OPTICAL POWER INTERNET
COMPONENT INTERFACE INTERFACE LEDs GROUND INTERFACE

MOUNTING
VERTICAL EAR (4 PLACES)
CABLE GUIDE
(2 PLACES)

22156-A

FLEXDSX CIRCUIT
COMPONENT MODULE
(16 PLACES)

Figure 4. Panel Components

Included are:
• ASX Component—is the active component of the ASX containing a compact SDH add
drop multiplexer,. This component also contains the hardware and software providing
remote control of the unit through an SNMP interface.
• Network Interface—is the physical connection point for the network optical fibers. The
interface consists of two Small Form Factor Pluggable (SFP) connectors accommodating
four optical fibers.
• Power Interface—is the –48/–60 VDC power input for the ASX ADM. The interface
consists of two sets of three pins (+, –, and GND). One set is used for primary power input.
The other set is used for redundant power input.
• Alarm Contacts—provide local alarm notification through the use of two sets of alarm
contacts. Each set has three contacts: Normally Open (NO), Common (C), and Normally
Closed (NC). The contacts can be wired locally as either NO-C or NC-C with a shorted or
open circuit, respectively, indicating an alarm condition.
• LEDs—are high-brilliance Light Emitting Diodes (LEDs) indicating power present
(green), minor alarm (yellow), and major alarm (red).

Page 4
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

• Craft Interface—provides a command-based, text interface for a local technician. This

interface allows the technician to query or set SNMP parameters or to become notified of
alarms.
• Ethernet Interface—connects the ASX system to an local area network and through the
internet to any remote computer capable of tieing into the system using an internet
browser.
• FLEXDSX Component—is the passive component of the system. The FLEXDSX panel
holds up to 16 FLESDSX circuit modules.
• Circuit Module—provides cross-connect and patch access to four E-1 circuits. Each
circuit module has two “odd” and two “even” jack cards. Each jack card has four bantam
sized ports: monitor out, out, monitor in, and in. The circuit modules are of two types,
wire wrap and LSA, shown in Figure 5

22157-A
WIRE WRAP LSA
MODULE MODULE

Figure 5. Panel Components

• Mounting Ear—is designed to allow mounting on a 600 mm ETSI rack.

• Vertical Cable Guide—can be used to provide a physical routing path for cross-connect
cables.

Page 5
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

1.4 Connectors

1.4.1 LAN Connector

The System has one LAN 10/100 BASE-T full/half duplex MDI interface. Cross wire (MDX)
detection is not supported. If the PC does not support MDI/MDX switching, a PC cross-cable is
required for direct connection. This interface is intended for singlemode fibers terminated with
LC connectors.

1.4.2 Craft Interface

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

1.4.3 Power Feed

The ASX panel has two power feeds with a nominal voltage of -48/-60 VDC. Each power feed
has three pins (+, –, and GND). The first three pins from the left (when viewed from the front of
the panel) are the primary power input. The next three pins are the redundant power input. A
Phoenix mini-Combicon connector is provided with the product for connection to the power
feeds. It is a six-position connector with three positions assigned to each power feed. The
connector accepts copper wire in the size range 28-16 AWG.

1.4.4 Ground Stud

The ASX panel has a ground stud located on the front of the panel for use in grounding the
panel to office ground. The stud is intended for copper wire of size AWG 18 or higher.

1.4.5 Optical Interface

The panel has an optical interface on the front of the panel. Physically, the interface consists of
two Small Form-factor Pluggables (SFPs) transceivers. The transceivers are intended for
singlemode fibers terminated with LC connectors.

1.4.6 Alarm Contacts

The ASX panel has alarm contacts intended for use in a local alarm reporting system. The
contacts are in two sets, one each for minor and major alarms. Each set consists of NO, NC, and
COMMON contacts. (The contacts may be wired as either NO or NC as required for the local
alarm reporting system.) Two Molex connectors are provided with the product for connection to
the alarm contacts. Each connector has four positions with two positions being used and two
remaining unused corresponding to the labeling on the front of the panel. The connector accepts
copper wire in the size range 24-16 AWG.

Page 6
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

1.5 ASX GUI

The System has an integrated web server that can be accessed using a web browser. Supported
browsers are Mozilla Firefox and Internet Explorer 6.0.

The ASX System overview window shown in Figure 6 indicates the general setup of the GUI.
On the left side of the window are launch pads for menu selections. The menu headings shown
represent the major parts of the system as follows:
• System Menu—provides System configuration functions including IP settings, OSPF
settings, and SNMP settings.
• Maintenance Menu—is used for querying the software versions and maintaining the
System database, log file, and users and passwords.
• Alarms—provides the ability to view and examine current alarms as well as alarm history.
Alarm severities and thresholds can be managed.
• Xconnect Menu—is not used in this application.
• Transmission Menu—is used to provision signals.
• Timing Menu—is used to set System timing and timing sources.
• MSP Menu—is used to set up MSP protected lines.

The central portion of the system overview window represents another major portion of the GUI
which is viewing and editing details for specific ports within the ASX. The eight rows represent
the eight Interface Cards, each of which has a tributary port (TP) whereby it receives its input
signal from the ADM and line ports (LP) whereby it passes an E1 signal to one of the
FLEXDSX circuits accessible on the front of the panel.

Figure 6. ASX System Overview

For a more detailed introduction to the ASX GUI, refer to Section 5, System Software Setup, on
Page 43.

Page 7
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

1.6 System Features

1.6.1 Summary of System Features

Below is a short list of the key features supported by the ASX System:
• Integrated web server with intuitive Graphical User Interface (GUI)
• SNMP manageable for alarming
• Sub network connection protection (SNCP)
• Remote management
• Loopback functions E1 incoming, E1 outgoing and STM-1 outgoing
• Non service affecting software upgrading (hitless upgrading)
• Full flexible VC12 cross connect (uni- and bidirectional)
• Non intrusive monitoring of any connection in the System
• Line protection (MSP)
• Two STM-1 aggregate signal (optical or electrical)
• Dual and single fiber interworking
• Degraded signal reporting and provisionable thresholds
• Synchronization, free running or selectable reference
• E1 retiming outputs
• Eight slot positions for Interface Cards
• Eight times 2.048 Mb/s according to G.703 interface per Interface Card
• Simple and rapid installation
• Database backup and restore
• Smart defaults, use of prepared databases
• Local E-1 cross-connect and test and patch access
• Local major and minor alarm contacts for onsite alerts
• Local LEDs (power on, major and minor alarms)
• Wire wrap or LSA cross-connect options

Topics below expand on some of these features.

1.6.2 System Software

The ASX System software (installed on the same computer as the ASX GUI) supports all
System products. The System has two memory banks containing the active and an inactive
software version. The software is stored in non volatile (flash) memory.

Page 8
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Remote and local software downloads are supported. Software upgrades are non service
affecting. They do not affect data communication settings.

1.6.3 System Database

The System database (installed on the same computer as the ASX GUI) contains all provisioned
settings of the System except for the IP and SNMP related settings. The System supports eight
databases, of which one is active. Databases are reusable between Systems of the same
hardware version (for example between one ASX system and another ASX system).

At first start up, the System has a default database in which no cross connects and other
transmission related settings are provisioned. A database operation does not have impact on the
data communication settings.

1.6.4 User Administration

The ASX GUI supports three user levels:

• View—Members of the view group have read access only.
• Config—Members of the config group have access to normal transmission related
operations.
• Admin—Members of the admin group are responsible for maintenance activities like
software upgrading, database operations, user group administration, and IP and SNMP
settings. The privileges of the members of the admin group also include the privileges of
the members of the config group.

1.6.5 Log File

The System maintains a log file (first in first out) to keep track of changes when system settings
are changed. Per event, the log file includes a time stamp, a user identification, and descriptive
text. The log file can be viewed using the ASX GUI.

1.6.6 Real Time Clock

The System has an accurate (better than 4.6 ppm) Real Time Clock on board. The time of this
clock can bet set by the user and will survive a power outage of at least ten minutes. The clock is
used for adding a time stamp to reported alarms. The internal System time is in UTC format;
however, during management via the GUI alarm, raise and clear times are represented in the
local time zone of the browser.

1.6.7 Powering

The System has two telecom power connections for -48/-60 V DC that can be used as redundant
power feeds. The power is monitored. By default, power fails are not reported. Alternatively, the
System can be powered using Power over Ethernet. Powering via PoE is not monitored.

Page 9
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

1.6.8 Pluggable Items

The ASX panel uses two types of pluggable items:

• Small Form-factor Pluggables (SFPs)—provide the physical STM-1 interface on the
front of the panel. Included are SFPs for dual- and single fiber operation or for STM-1
electrical. SFPs are hot pluggable and are automatically discovered by the System.
• Interface Cards (IFCs)—each take an eighth part of the STM-1 signal (provided by the
internal ADM) and divide the signal into eighth E1 circuits that are output to the
corresponding eight tributary ports. IFCs are hot pluggable and are automatically detected
by the System.

1.6.9 Inventory Management

The ASX GUI can be used to review inventory data for the “pluggable items” described in the
previous topic. The function provides a master list in which any item can be selected to view
details for that item.

1.6.10 Line Protection

The System supports Multiplex Section Protection (MSP) line port protection; this allows
restoration of traffic when a failure has been detected on one of the line sections, including SFP
failures. Unidirectional MSP for both revertive and non-revertive operation is supported.

1.6.11 Synchronization

The ASX System can be synchronized externally via each of the line ports and one of the E1
tributary ports. An internal (free running) clock with an accuracy of ± 4.6 ppm (or better) has
been integrated. When no suitable reference is available, the System will use its holdover clock.

1.6.12 E1 Retiming

Every E1 port individually can be provisioned in retiming mode. In this mode, the outgoing E1
signal will be retimed with the System clock. In this way the E1 signal can be used as a timing
reference for a next System (with the SDH network) connected to the System being accessed
through the ASX GUI.

1.6.13 Alarm Reporting

The ASX System supports the alarm reporting of current alarms. Alarms are reported on the
web browser and to an SNMP manager if provisioned. The alarms can also be visible on the
System LEDs. The System has a log for 500 cleared alarms. For every alarm, the severity and
reporting state can be provisioned. Every port and termination point has a monitoring mode to
control the alarming.

Page 10
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

1.6.14 Cross Connects

The ASX GUI provides the ability to create logical cross-connects (within the ASX ADM, not
using the FLEXDSX circuit modules); however, in the multiplexing application of the ASX
described in this manual, logical cross connects are not usually created.

Logical cross connects are used in a Digital Automatic Cross Connect (DAX) application of the
ASX3 (not documented in this manual). When used, logical cross connects can be fully flexibly
added between line and tributary ports, between line and line ports, and between tributary and
tributary ports. Both uni- and bidirectional cross connects are supported. Bidirectional cross
connects transmit traffic in two directions; unidirectional cross connects transmit traffic in one
direction.

1.6.15 Overhead Functions

Full access is available to the SDH overhead. RS, MS, VC4, and VC12 overhead can be viewed
and provisioned (for example, full trail trace identifier provisioning).

1.6.16 Web Server

The System has an integrated web server, thus no additional management system is needed.
Only a web browser is needed. Via this web browser, the System can be managed.

1.6.17 SNMP Server

The System supports alarm reporting towards an SNMP manager. Five different SNMP
managers can be added. Both SNMPv1 and SNMPv2 are supported. User specific MIB files are
supported.

1.6.18 Single and Dual Fiber SFPs

The System supports both single and dual fiber small form-factor pluggables, SFPs. An SFP is
the optical/electrical STM-1 line interface unit.

1.6.19 Path Protection

The System supports VC12 SNCP path protection.

1.6.20 Loopback

The Systems supports port loopback on the following levels:

• E1 incoming
• E1 outgoing
• STM-1 outgoing

Page 11
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

1.7 Summary of User Tasks

Table 1 summarizes all System tasks.

Table 1. ASX GUI Master Index of Tasks

TASK # DESCRIPTION REFER TO SECTION

Prepare for use of the system
1 Learn about the basic makeup and function of the ASX System. 1 on Page 1
2 Read background technical information on ASX System functions. 4 on Page 25
Install the ASX panel
1 Unpack the System hardware. 2.2 on Page 17
2 Mount the panel on the rack. 2.4 on Page 18
3 Install basic wiring (ground, alarm contacts, optical, ethernet, power). 2.5 on Page 19
4 Install cross-connects to local DSX panel. 2.7 on Page 20
Set up the ASX GUI
1 Set up IP address for web browser. 5.1 on Page 43
2 Log in to the ASX GUI. 5.2.5 on Page 50
3 Set up passwords (System administrator only). 5.2.4 on Page 49
4 Launch from system overview window to specific tasks. 5.2.6 on Page 50
5 Determine, change the System time. 6.3 on Page 56
Provision ASX System (not sequential)
1 Determine the current status of pluggable items (IFCs and SFPs). 6.4.1 on Page 58
2 Display, edit details for an Interface Card (IFC). 6.4.2 on Page 58
3 Replace an IFC (causing the new IFC to become “accepted” and “assigned”). 6.4.3 on Page 60
4 Display, edit details for a Small Form-factor Pluggable (SFP). 6.4.4 on Page 60
5 Replace an SFP (causing the new SFP to become “accepted” and “assigned”). 6.4.5 on Page 61
6 Respond to a System recovery; interpret the console port alarm status signals. 6.5 on Page 62
7 Check which software memory bank is active; switch to the other bank. 6.6 on Page 62
8 Backup, copy, rename, activate, restore, or delete a System database. 6.7 on Page 65
9 Provision a specific Line Port (LP1/2) for a specific IFC. 6.8.2 on Page 69
10 Provision a specific Tributary Port (TP1-8) for a specific IFC. 6.8.3 on Page 70
11 Provision a termination point for an RS/MS section, VC4, or VC12. 6.8.4 on Page 72
12 Provision a threshold for a termination point “degraded signal alarm.” 6.8.5 on Page 77
13 Provision a Trail Trace Identifier (TTI) for a trail termination point TIM alarm. 6.8.6 on Page 78
14 Create, provision a Multiple Section Protection (MSP) pair for an STM-1. 6.10 on Page 89
15 Synchronize the SDH network to one master clock; provision timing sources. 6.11 on Page 95
16 Provision the SNMP manager IP address, traps, and alarm community. 6.12 on Page 105
17 Provision Open Shortest Path First (OSPF) settings. 6.13 on Page 107

Page 12
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 1. ASX GUI Master Index of Tasks

TASK # DESCRIPTION REFER TO SECTION

Alarms and Troubleshooting
1 View and respond to System alarms (using ASX GUI). 7 on Page 113

1.8 Dimensions and Specifications

Figure 7 shows the ASX panel dimensions. Table 2 lists ASX system specifications.

17.50 IN.
(44.5 CM)

8.72 IN.
(22.1 CM)

22.31 IN. 10.28 IN.

(56.7 CM) (26.1 CM)
24.14 IN.
(61.3 CM) 22152-A

Figure 7. ASX Panel Dimensions

Table 2. ASX System Specifications

ITEM SPECIFICATION COMMENT

Physical
Dimensions (HxWxD) 3.47 x 19.35 x 11.55 inches 8.8 x 49.1 x 29.3 cm
Color Putty white
Rack mounting Mounts on 95mm ADC PROFIL
rod mounting frames
Hardware Platform

Page 13
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Table 2. ASX System Specifications, continued

ITEM SPECIFICATION COMMENT

Panel PROFIL version with ASX main accommodates 8 interface cards
module with 8 E1 ports
Interface card
type ADC101 supports 8 E1 G.703 (120 Ohm)
ports per card
power consumption 0.65 Watt
Environmental
Operating temperature –5º C to +40º C acc. ETSI 300 019-2-3 class 3.1
Storage temperature –25º C to +70º C acc. ETSI 300 019-2-1 class 1.2
Operating humidity 0% to 95% humidity acc. ETSI 300 019-2-3 class 3.2
Storage humidity 0% to 100% humidity acc. ETSI 300 019-2-1 class 1.2
Transport acc. ETSI 300-019-2-2 Class 2.3
Availability
MTBF ASX100 > 70 years, excluding Interface
Cards and SFPs
MTBF ADC101 > 450 years
Power
Source -48/-60V DC or Power over Ether-
net, via the signal wires class 0 on
the LAN interface , according to
IEEE 802.3af.
Consumption 6.5Watt (Excluding Interface Cards)
Interfaces
STM-1 interface Depending on SFP in use
E1 interface ADC101 2.048 Mb/s ± 50 ppm, acc. ITU-T G.703-6
HDB3 coded signal
E1 interface impedance 120 Ohm
LAN interface 10/100 Base T non sensing inter- no MDI/MDX AUTO detection
face,
Local console port DB9 connector, signal levels acc. ITU-T V.28 and EIA232.
Synchronization
Timing accuracy Free running accuracy ± 4,6 ppm acc. ITU-T G.813, option 1
Algorithm support SSM acc. ITU G.784
E1 retiming
E1 Interface Mapping
Speed 2048 kbit/s ± 50 ppm

Page 14
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 2. ASX System Specifications, continued

ITEM SPECIFICATION COMMENT

Type HDB3 coded acc. G.703-9
Mode mapped via VC-12 in TU-12* using structure: STM-1->AU4-
>VC4->TUG3–>TUG2->TU12-
>VC12->P12x->E12

* Note in this mode the system does not assume any formatting/framing of the 2048
kbit/Sec signal so also framed signals are supported.

Page 15
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Page 16
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

2 HARDWARE INSTALLATION PROCEDURES

This section contains instructions for installing the ASX panel. Procedures are provided here for
unpacking the product, installing the panel on a rack, and wiring the panel. Procedures are also
provided for testing and patching of E! circuits using the FLEXDSX circuit modules.

All procedures documented in this section are done at the physical site where the ASX panel is
located.

2.1 Overview of Equipment Installation

Installation involves the following main tasks:

1. Unpacking and inspecting the product.
2. Obtaining tools and materials required for installation.
3. Mounting the panel on a rack.
4. Installing the basic cabling for the panel including grounding, optical fibers, Ethernet
cable, alarm contacts, optical cable, and power inputs.
5. Installing the semi-permanent cross-connect cables between the front panel of the ASX
panel (FEXDSX circuit modules) and a local DSX panel.

2.2 Unpacking and Inspection

Use the following procedure to unpack and inspect the cabinet and all accessories:
1. Open the shipping carton(s) and carefully unpack the cabinet and any accessories from the
protective packing material.
2. Open the cabinet doors (requires 216B key tool) and check for broken or missing parts. If
there are damages, contact ADC for an RMA (Return Material Authorization) and to
reorder if replacement is required.

2.3 Tools and Materials Required for Installation

The following tools and materials are required for installation

• Wire cutter
• Screwdriver (flat blade)
• Singlemode optical fibers (two primary, two secondary) with LC connectors
• AW wire in the following sizes (AWG 18 or higher, AWG 22 or higher)
• Ethernet Cat 5 cable (10/100)
• (For local craft interface if to be used) RS-232 cables with DB-9 connector
• Wire lacing

Page 17
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

2.4 Mounting the Panel on the Rack

The ASX panel is a 19-inch rack mount panel designed to be mounted on a standard E-1 rack.
The panel mounts with four screws included with the shipped items.

Use the following procedure to mount the panel on the rack (Figure 8):
1. Determine the rack location where the panel will be mounted.
2. Position the panel in line with the rack location selected.
3. Secure the panel to the rack using the four screws provided.

22176-A

Figure 8. Installing the Panel on the Rack

Page 18
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

2.5 Connecting the Panel

Connect the panel using the following procedure (Figure 9):

POWER INTERFACE (-48/-60 VDC) (OPTIONAL)

TERMINATE WITH PHOENIX ALARM CRAFT INTERFACE
MINICOMBICON CONNECTOR CONTACTS USE RE-232 CABLE
(PROVIDED) TERMINATE TERMINATED WITH
NETWORK INTERFACE (STM-1) WITH MOLEX DB-9 CONNECTOR
USE SINGLE MODE OPTICAL FIBER CONNECTORS
(PROVIDED) LAN INTERFACE
TERMINATED WITH LC CONNECTORS
(10/100)
(2 PRIMARY (TX/RX), 2 REDUNDANT)
USE ETHERNET
CAT 5 CABLE

GROUND
USE AWG 18
OR HIGHER
COPPER WIRE

22211-A

Figure 9. Installation Wiring Diagram

1. Install a ground wire from the ground stud on the ASX front panel to office ground. Use
copper wire AWG 18 or higher.
2. Locate the two Molex connectors (ADC part number 1317429) provided with the product.
Install copper wires in the connectors for connection from the local alarm reporting system
to the alarm contacts on the front of the panel. The alarm contacts can be wired as either
Normally Open (NO-C) or Normally Closed (NC-C). Wire the connectors using copper
wire in the size range 24-16 AWG. Note that each connector has four positions of which
two positions will be used and two positions will be unused corresponding to the labeling
on the front of the panel.

Note: The configuration of used and unused positions will differ for the two connectors
because the configuration of alarm contacts is different for minor and major alarms (to
reduce the possibility for the connectors to be mistakenly reversed).

3. Connect the Cat 5 Ethernet cable from the ASX panel to the PC providing the LAN. The
LAN interface must be a 10/100 BASE-T full/half duplex MDI interface. Cross wire
(MDX) detection is not supported.

Note: If the PC does not support MDI/MDX switching, a PC cross-cable is required for
direct connection.

Page 19
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

4. Connect the four network optical fibers to the SFPs on the ASX front panel. These must be
single mode fibers terminated with LC connectors.
5. Locate the six-position Phoenix mini-Combicon connector (ADC part number 1303445)
provided with the product. Install copper wires in the connector for connection from the
local power source to the power interface on the front of the panel. The first three pins
from the left (when viewed from the front of the panel) are the primary power input. The
next three pins are the redundant power input. The connector accepts copper wire in the
size range 28-16 AWG. The power interface has a nominal voltage of -48/-60 V DC.

2.6 Powering Up the Panel

Apply power to the System and wait for the system to complete its power-up sequence.
Connecting with a Web browser to the System is not possible at this time. After 3 minutes the
System is operational. A connection via the Web browser can then be made. For the first minute
of operation, alarm information is not available.

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

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

2.7 Installing Cross-Connect Jumpers

In a typical installation, cross-connect jumpers are installed between the ASX panel circuit
modules and a DSX panel connected to local NEs. Once installed, these cross connections are
left in place semi-permanently and only reconfigured in unusual circumstances. To cross-
connect between circuit modules for two network elements, use the wire-wrap pins or LSA
cross connect field located on the lower area of the circuit module. Figure 10 shows a circuit
module with a wire wrap cross connect field.

Page 20
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

LED
INSULATION
(ONE TURN ON
MONITOR OUT
THREE CORNERS OF PIN)

OUT STRIPPED WIRE

(FIVE TURNS)
PATCH AND TEST
IN
JACK FIELD

MONITOR IN

RECOMMENDED
WIRE WRAP (ONE PIN)

TRACER LAMP
TO
WIRE WRAP
CROSS-CONNECT RO
FIELD TI
SHADED AREA IDENTIFIES
RI
ONE CIRCUIT
12121-A

FRONT VIEW

Figure 10. Cross-Connect Field and Patch and Test Jack Field

2.7.1 Wire-Wrap Cross Connect

For a wire-wrap connection, use five-conductor 24 AWG jumpers, cross-connect DSX circuits
as shown in Figure 11. Terminal identification is as shown in the installation drawing
accompanying each panel.
• Connect the TL of the first termination to the TL of the second termination (green wire).
• Connect the OUT of the first termination to the IN of the second termination (blue wire
and blue-white wire).
• Connect the IN of the first termination to the OUT of the second termination (orange wire
and orange-white wire).

Remove any discontinued jumper by disconnecting each end and cutting off the bare ends.
Remove each end of the jumper from the vertical wireways, and carefully remove the jumper
from the horizontal wireway by pulling at either end. This method will allow the jumper to be
removed without snagging or placing undue strain on the remaining jumpers.

Page 21
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

GREEN TL
BLUE TWISTED PAIRS
TO
5 CONDUCTOR
BLUE-WHITE OUT RO JUMPER WIRE
ORANGE TI TL

ORANGE-WHITE IN RI TO
OUT
RO

CROSS-CONNECT TI
TERMINAL BLOCKS IN
RI

11893-B

Figure 11. Cross-Connect Wiring

2.7.2 LSA Cross Connect

For an LSA connection, use LSA-plus connectors to cross-connect DSX circuits as shown in
Figure 11 (ignoring wire color). Terminal identification is as shown in the installation drawing
accompanying each panel.

2.7.3 Cross Connect Routing

Cross-connect jumpers should be routed as shown in Figure 12. All cross-connect jumpers
should use the horizontal wireways between bays, and the vertical wireways within the bay.
Whenever a jumper changes direction, it should do so where a ring, tray or fanning strip is
located. This will allow the jumpers to be dressed neatly without strain or interfering with other
jumpers. All discontinued jumpers should be removed from the DSX wireways, to prevent
unnecessary buildup and congestion.

Page 22
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

UPPER
JUMPER
WIREWAYS

CROSS-
CONNECT
A B

VERTICAL
JUMPER C
WIREWAYS

B A

D
LOWER
JUMPER
WIREWAYS

ROUTING RULES:

A. ALL JUMPERS IN THE LEFT-HAND SIDE OF THE CROSS-CONNECT FIELD SHOULD ENTER AND LEAVE THE BAY
FROM THE LEFT VERTICAL WIREWAYS.
B. ALL JUMPERS IN THE RIGHT-HAND SIDE OF THE CROSS-CONNECT FIELD SHOULD ENTER AND LEAVE THE BAY
FROM THE RIGHT VERTICAL WIREWAYS.
C. ALL INTRABAY CROSS-CONNECTS SHOULD USE THE VERTICAL RINGS EXCEPT WHEN TERMINATIONS ARE IN THE
SAME PANEL.
D. ALL INTERBAY JUMPERS SHOULD USE HORIZONTAL WIREWAYS.

E. ALL INTERBAY JUMPERS ORIGINATING IN THE UPPER HALF OF THE CROSS-CONNECT FIELD SHOULD ROUTE VIA
THE UPPER HORIZONTAL WIREWAYS.
F. ALL INTERBAY JUMPERS ORIGINATING IN THE LOWER HALF OF THE CROSS-CONNECT FIELD SHOULD ROUTE VIA
THE LOWER HORIZONTAL WIREWAYS.
8464-B

Figure 12. Recommended Cross-Connect Routing in DSX Bays

Page 23
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

3 PATCHING AND TESTING

For patching and testing use the patch and test bantam jackfield identified in Figure 10 on Page
21. Refer to ADCP-80-514, “DSX-1 Operational Procedures”, for individual procedures such as
in-service and out-of-service patching.

Page 24
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

4 FUNCTIONAL BACKGROUND INFORMATION FOR ASX SYSTEM

This section provides some functional background information on the ASX System. Also, this
section describes some aspects of provisioning, however not in detail.

The ASX System supports the following management options:

• Local management
• Remote management using a LAN connection
• Remote management using an Access Network

The System is designed to achieve an optimum between routing aspects, easy configuration, and
maintenance. To achieve this, dynamic routing is used instead of static routing.

4.1 Open Shortest Path First (OSPF)

Open Shortest Path First (OSPH) is an example of a link state routing protocol. Neighbor
routers tell each other their connections and status. In this way, the routers create a map with the
network topology. Routes are quickly recalculated in case of topological changes. In OSPF, the
cheapest path is calculated using cost metrics.

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

OSPF supports multiple areas to limit the amount of routing related traffic. If communication
between other areas or other networks is required, there must be a way out. An ASBR is used for
this purpose (see Section 4.3.2 on Page 26).

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

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

4.2 Supported Areas

An OSPF network can be divided into areas. The System, however, supports only one area.
Since OSPF AS requires that all routers are connected to the backbone area (also known as area
0 or area 0.0.0.0), this is the only area supported by the System.

The System supports up to 50 routers per AS. If more routers are connected, all Systems will
give the SYScROUTE alarm (see Section 7.8.1.5 on Page 122). No guarantee can be given that
the Systems function properly if this alarm is raised. As a user you must take appropriate actions
to avoid or to solve these problems.

Page 25
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

OSPF protocol interworking is only supported for systems from the same family.
Authentication is realized by means of a simple password check.

4.3 Routers for OSPF

4.3.1 Area Border Router

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

4.3.2 Autonomous System Border Router (ASBR)

Autonomous system border routers are routers on the border of an OSPF AS. They are used to
communicate with external networks. The system supports the ASBR functionality.

The ASBR router can be used for remote management of the network.

Becoming an ASBR

A System becomes functionally an ASBR if the following conditions are met:

• A local (LAN) default route is provisioned or a default route is received from a DHCP
server.
• OSPF is enabled for the System.
• OSPF is enabled for the System LAN interface.
• Default route advertisement is enabled.

4.3.3 Designated Router and the Backup Designated Router

As the number of nodes in a LAN network grows, the link state messages will increase to the
square. To be more specific: N nodes result in N*(N-1) link state messages. To reduce the
number and size of messages from increasing, the System automatically assigns one of the
routers as a designated router.

The designated router plays a critical role in the link state advertisement. As a fall back
possibility, the System also addresses one of the routers as a backup designated router. If the
designated router (DR) fails, the back-up designated router (BDR) automatically takes over the
role.

Each router is assigned an 8-bit priority, indicating its ability to be selected as the DR or BDR.
All multi-access networks must have a DR. A BDR may also be selected. The backup ensures
there is no extended loss of routing capability if the DR fails.

Page 26
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

The DR and BDR are selected using information contained in hello packets. The device with the
highest OSPF router priority on a segment becomes the DR for that segment. The same process
is repeated to select the BDR. In case of a tie, the router with the highest RID is selected. A
router declared the DR is ineligible to become the BDR. Once selected, the DR and BDR
proceed to establish adjacencies with all routers on the multi-access segment.

4.3.4 Unnumbered Network

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

4.4 Address Resolution Protocol (ARP)

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

4.5 Proxy Resolution Protocol (PARP)

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

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

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

4.6 Link Costs and Signal Rate

For the System no link layer protocol configuration for the embedded DCC links is required.
The System uses PPP (point-to-point protocol) over HDLC. It uses the MS-DCC
communication channel. The signal rate is 576 kbit/second.

The link costs are:

• LAN: 10
• DCC: 174
• Local: 1

The System does not support load balancing (dividing traffic over equal-costs routes).

Page 27
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

4.7 Line Protection and OSPF

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

4.8 Assigning IP Addresses for System Management

A System can have multiple IP addresses:

• Per line port, a user-provisioned IP (/32) interface address;
• A user provisioned LAN IP address, either default or obtained from DHCP;
• If OSPF is enabled, a user-provisioned IP (/32) host address, which is also used as a
Router ID.

Note: We strongly recommend to use a convention to provision the IP addresses to the

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

Table 3 shows the convention used in this manual.

Table 3. Conventions Used in This Manual for IP Address

Type A B C D
NE LAN Interface 10 12 LAN#: 0 - 255 NE#: 1 - 99
LP1 (PPP0) interface 192 168 1 NE#: 1 - 99
LP2 (PPP1) interface 192 128 2 NE#: 1 - 99
System or host address / router ID 10 15 0 NE#: 1 - 99
Directly connected Host / Manager 10 12 LAN#: 0 - 255 Host#: 100 - 254
LAN interface
Host or manager LAN interface in 80 80 LAN#: 0 - 255 Host#: 100 - 254
access network
Access Router LAN interface 80 80 LAN#: 0 - 255 Router#: 80-99

Systems can be accessed by IP addresses. The figure shows an example. If OSPF is disabled, the
LAN IP address should be used.

Page 28
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

System Access Problems When Using IP Addresses

Figure 13 illustrates how system access problems can occur.

10.12.0.100 / 24 Host#1
default route
10.12.0.1
(10.12.0.x / 24) 192.168.1.1 / 32 192.168.2.4 / 32
ospf ospf
10.12.0.1 / 24 [10]
ospf
NE#1 [174] NE#4
(10.15.0.1) (10.15.0.4)
Autonomous System
192.168.2.1 / 32
192.168.1.4 / 32
ospf
[174] [174] ospf
SDH 'ring'
192.168.1.2 / 32
ospf 192.168.2.3 / 32
NE#2 NE#3 ospf
(10.15.0.2) [174] (10.15.0.3)

10.12.1.2 / 24 10.12.1.3 / 24
ospf ospf
[10] [10]

(10.12.1.x / 24)
[link cost]
(Router ID)

Figure 13. System Access Problems When Using LAN IP Address

Note: The notation (10.15.0.1) or more general (A.B.C.D) in the network element (NE#x)
indicates the router ID and also that OSPF is enabled at System level.

If there are no errors (so NE#2 and NE#3 are connected via the LAN) in the OSPF enabled
network the OSPF protocol will access NE#3 via the shortest path. This path is:

Host#1 <-> NE#1 <-> NE#2 <-> NE#3, costs: 174 + 10 = 184

Now a LAN error occurs, as shown in the figure. In this case, no rerouting takes place because
the 10.12.1.x/24 network is still available. Therefore NE#3 cannot be reached anymore.

A better solution is achieved if the host uses the System router ID, being 10.15.0.3, to reach
NE#3. In this case NE#3 remains accessible via the rerouting path:

Host#1 <-> NE#1 <-> NE#4 <-> NE#3, costs: 174 + 174 +1 = 349

Page 29
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

4.9 Routing Examples

This section describes some management network examples that illustrate the functioning of the
basic routing options.

4.9.1 Local Management, Host Directly Connected to System LAN and No Routing Protocol

These examples include:

• System and host in the same subnet (Section 4.9.1.1)
• System and host connected to an access network (Section 4.9.1.2)

4.9.1.1 System and Host in Same Subnet

In order to communicate with each other, the system and host must be part of the same subnet.

Figure 14. Example of System and Host in Same Subnet

Note: We advise an equal size of the subnet for all systems connected to the LAN.

If Proxy ARP is used, it is mandatory to use one subnet mask for all connected elements.

The number of hosts and systems that can be connected depends on the size of the subnet mask.
It can be calculated with:

2 (32-X) - 1

where X is the size of the subnet mask. -1 is included in the calculation because the broadcast
address (255.255.255.255) must be excluded.

4.9.1.2 System and Host Connected to Access Network

In this case, local management traffic is realized by communication over the local System LAN
interface. If the host wants to access the System that is not in the same subnet, it will use the
default route entry. This is the ethernet address for router RT#1. RT#1 will deliver the message
to the next element. If the access network is properly connected, System (NE#1) can be
accessed by the host.

Page 30
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

The system will use the default route of RT#2 to response to the host.

Figure 15. Example of an Access Network

Note: For hosts with multiple LAN ports, you can sometimes specify a default route per
LAN port. This depends on the operating system, and behavior is undefined.

4.10 Route Management Examples

This section contains examples of various types of route management.

4.10.1 Terminal Application and Host Connected to LAN

The point-to-point protocol (PPP) is used to establish the connection between NE#1 and NE#2.
Now the interface address of NE#1 is known by NE#2 and the other way round. This is
something taken care of by the PPP protocol.

So NE#1 can be reached via:

• LP1: 192.168.1.1
• LP2: 198.168.2.1

And NE#2 can be reached via:

• LP1: 192.168.1.2
• LP2: 198.168.2.2

Page 31
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

NE#2 is an ASBR (this can be set with the GUI). If OSPF is enabled on System level and on
line port level, the OSPF protocol provides the routing table of NE#1 with 10.15.0.2 and NE#2
with 10.15.0.1. Also the default route, 10.12.0.100, will be advertised.

Note that for the communication between Host#1 and NE#1 it is needed that NE#1 knows how
to access the 10.12.0.x / 24 network. Without OSPF, this information is not distributed and
communication fails.

Figure 16. Example of Remote Management, Host Directly Connected to System LAN

Table 4. Rounding Table NE #1

DESTINATION MASK GATEWAY FLAGS METRIC INTERFACE

192.168.1.1 32 0.0.0.0 UGH 348 ppp0
192.168.1.2 32 192.168.1.1 UH 0 ppp0
192.168.2.1 32 0.0.0.0 UGH 348 ppp0
10.15.0.2 32 192.168.1.2 UGH 175 ppp0
192.168.2.2 32 192.168.1.2 UH 0 ppp1
192.127.127.0 30 0.0.0.0 U 0 ppp0
10.12.0.0 24 0.0.0.0 UG 148 ppp0
0.0.0.0 0 192.168.1.2 UG 10 ppp0

Table 5. Rounding Table NE #2

DESTINATION MASK GATEWAY FLAGS METRIC INTERFACE

192.168.1.1 32 0.0.0.0 UG 0 ppp0
192.168.1.2 32 192.168.1.1 UGH 348 ppp0
192.168.2.1 32 0.0.0.0 UH 0 ppp1
10.15.0.1 32 192.168.1.1 UGH 175 ppp0
192.168.2.2 32 192.168.1.1 UGH 348 ppp0
10.12.0.0 24 0.0.0.0 U 0 ppp0
0.0.0.0 0 10.12.0.100 UG 10 ppp0

Page 32
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Remarks for Rounding Table

Flags

U: route is up. G: route is to a gateway. H: route is to a host. If this flag is not set, it is a route to
a network.

From this table, it becomes clear that the Host can reach NE#1 via NE#2. The following takes
place when you login with the address 10.15.0.1:
1. The Host cannot find this address on the LAN, so it will use the default gateway:
10.12.0.2.
2. NE#2 receives the message and checks the address 10.15.0.1 in its routing table, and use:
192.168.1.2.
3. NE#1 responses to the host via 192.168.1.2.
4. Next 10.12.0.x/24 is used, because this is advertised by OSPF.

Note: For the local LAN of NE#1, it is necessary to use a LAN IP address that doesn't fit
in the LAN network of Host#1 (for example, 10.127.127.1/30). It is advised to disable
DHCP for NE#1. Otherwise, IP address conflicts may occur. If 10.127.127.1/30 is used,
then the IP subnet addresses are: 10.127.127.0 10.127.27.1, 10.127.127.2, and
10.127.127.3. The first one is often not allowed and the last one is a broadcast. So both
cannot be used as a host address.

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

Remarks

• Router Table evaluation

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

• Local addresses
The system software does not use the routing table if a local destination address is
involved. This means that the costs and actual route can be ignored for a local PPP
interface.

• Local PPP interface costs

The System routing table shows that the path costs to the local PPP interface has twice the
expected value. This is because this route is regarded as advertised by the neighbor and the
cost to reach the neighbor are also included. However they play no role in the costs for the
shortest path.

Page 33
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

• Local PPP interface addresses

For the local PPP interfaces the neighbor PPP interface address shows up in the routing
table.

• PPP interface regarded as a host address

According to the System routing table a PPP interface is regarded as a host address which
is not the case. A /32 address is interpreted as a host address.

• 0.0.0.0 destination address

This entry is the default gateway. For Host#1 the default route is 10.12.0.2 (LAN interface
of NE#2). For NE#2 (ASBR) the default route is the LAN interface of Host#1
(10.12.0.100). For NE#1 (remotely managed via a protected point-to-point connection) the
default route is 192.168.1.2 (LP1) via which also the 10.12.0.0 / 24 network is routed.

• NE#1 <-> NE#2 path

The route from NE#2 to NE#1 and the route from NE#1 to NE#2 are in this case both
routed via the same port (LP1) which is a coincidence. Also note that the path cost is the
sum of the PPP link (174) and the local loop Router ID address (1).

4.10.2 Multiple Host and Mix Applications

In this configuration, shown in Figure 17, both hosts are able to access any of the systems. All
Systems, except NE#3, are OSPF enabled. So the topology of the network is advertised from
neighbor to neighbor.

The designated router can either be NE#2 or NE#5. Normally, NE#5 becomes the designated
router because it has an router ID greater than the router ID of NE#2.

4.10.2.1 Example One: Net #2 Wants to Access Net #3

This is achieved by the fact that NE#5 has OSPF enabled on the LAN interface. This will be
advertised to, among others, NE#4. So if Host#2 wants to access NE#3 via 10.12.0.3, the
following takes place:
1. The message is sent to the default route, being 10.12.1.4. This is NE#4.
2. NE#4, in its turn will access the next hop. This is NE#5.
3. NE#5 will put the message forward to its LAN network: 10.12.0.5/24.
4. NE#3 will pick it up from the LAN network.

Page 34
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

192.168.1.1 / 32 192.168.1.2 / 32 10.12.0.2 / 24 10.12.0.100 / 24

ospf ospf ospf default route:
10.12.0.2

10.127.127.1 / 30
(no dhcp)
NE#1
(10.15.0.1) NE#2
SDH terminal (10.15.0.2)
Host#1

10.12.0.3 / 24
192.168.2.1 / 32 192.168.2.2 / 32 default route:
ospf ospf 10.12.0.5

Host#2 192.168.1.4 / 32 192.168.1.5 / 32 NE#3

ospf ospf
10.12.1.100 / 24
default route
10.12.1.4 Autonomous System
10.12.0.5 / 24
10.12.1.4 / 24 ospf
ospf
NE#5
NE#4 (10.15.0.5) 192.168.2.5 / 32
(10.15.04)
ospf
192.168.2.6 / 32
ospf

192.168.2.4 / 32
ospf SDH ring

192.168.1.6 / 32
192.168.2.7 / 32 ospf 10.127.127.1 / 30
NE#7 NE#6
ospf (10.15.0.7) (10.15.0.6) (no dhcp)
192.168.1.7 / 32
ospf
10.127.127.1 / 30
(no dhcp)

Figure 17. Example of Application Mix and Multiple Hosts

5. The reply from NE#3 to Host#2 is guaranteed because:

a. NE#4 and NE#5 both have OSPF enabled.
b. NE#5 receives the message from NE#3 via the default route of NE#3, 10.12.0.5/24.
c. Via the routing table of NE#5, the message will be forwarded to NE#4, because NE#4
reported the local network 10.12.1.x/24.
d. NE#4 forwards the message to the local area network.

4.10.2.2 Example Two: Host #1 Wants to Access a System in the SDH Ring

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

Page 35
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

4.10.3 Example With ASBR

Figure 18 shows an example of a system with ASBR. To make NE#6 an ASBR, it must have a
default route to the LAN network and advertisement must be enabled. In this way, all systems in
the access network can be reached, but only if RT#1 is provisioned for it. This can be done
either on a per individual address basis or by assigning a single entry: 10.15.0.0/28 -> 80.80.2.6.
This covers the range 10.15.0.0 ... 10.15.0.14.

The access network does not get any status information of the autonomous system. This implies
that only internal failures inside the AS can be addressed/resolved. To make it more reliable,
you might consider also involving NE#7 and RT#2 in the routing scheme; however, the network
thereby becomes more complex.

Figure 18. Example of System With Autonomous System Border Routing

Page 36
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Note that routing protocol inter-working between RT#1 and NE#6 cannot take place because of
the OSPF password authentication.

Caution: Host#1 can use or misuse the routing network to access remote nodes, like SNMP#1.
The routing is not designed for this through traffic. It should be avoided.

4.10.4 Example With Proxy ARP

Instead of using ASBR and a static routing table for RT#2 to get to the access network (see
“Example with ASBR” on page ), it is also possible to use proxy ARP on an ASBR. Figure 19
shows an example The applied subnet mask /24 (preferred multiple of 8), gives access to a
relatively large subnet. You may want to use /28 which is sufficient in the depicted case.

Figure 19. Example of Proxy ARP Configuration

Page 37
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Note that the routing protocol inter-working between RT#1 and NE#7 cannot take place because
of the OSPF password authentication.

A proxy ARP enabled system will not respond to an ARP request if the routing path involves
the network interface via which the ARP request was received. Only OSPF enabled systems can
be managed via the access network. The managed nodes and at least the LAN port of NE#7 and
RT#1 are part of one subnet.

It is not allowed to have multiple access routers reporting the same or overlapping subnet. This
may result in unmanageable Systems (see next topic).

4.10.4.1 Avoiding Management Problems With Proxy ARP

Figure 20 shows a configuration in which management problems may occur if the connection
between NE#3 and NE#4 is OSPF enabled. The problem occurs because an ARP request for
NE#4 by Host#1 can be answered by both NE#2 and NE#1.

10.15.0.100 / 24

10.15.0.12 / 24
10.15.0.11 / 24 ospf
ospf Host#1 proxy arp
proxy arp

NE#1 NE#2
(10.15.0.1) (10.15.0.2)

OSPF

NE#5 NE#3
(10.15.0.5) No OSPF (10.15.0.3)

NE#4
(10.15.0.4)

Figure 20. Proxy ARP Example

Table 20 below shows who is answering on a proxy ARP request if more nodes have their LAN
settings provisioned as proxy ARP.

Table 6. 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

Page 38
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 6. Proxy ARP Example

HOST #1 ARP REQUEST FOR IS ANSWERED BY

10.15.0.4 NE#4 NE#1
10.15.0.5 NE#5 NE#1

Note: If the connection between NE#3 and NE#4 was OSPF enabled, an NE#4 ARP
request would also be answered by NE#2. In this way, NE#4 might become
unmanageable.

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

4.11 Subnetwork Connection Protection (SNCP)

The system supports subnetwork connection protection. With the aid of SNCP, the System
protects a low order virtual container (sub) network connection. At the head-end, the virtual
container is permanently bridged into two tributary units (TU). At the tail-end, the selection is
made.

When a defect occurs, or as a result of a user request, the traffic is rerouted to the non-defective
TU. Both resources together form a so called 1+1 protection group (PG).

Only non-revertive switching is supported. This means that the TU where the traffic was
rerouted to remains active when the error disappears. Manual, forced, and clear commands are
supported.

For reliable monitoring of SNCP-protected cross-connects, the system supports multiple

protected cross-connects that share the same worker and protection leg. Sharing of only one leg
is not supported and rejected by the System.

The system supports SNC/N subnetwork protection (refer to ITU-T G.841). In this protection
scheme, the following criteria are used for determination of the active traffic selected path:
• A server signal failure on the subnetwork connection;
• A trace identifier mismatch (TIM);

Note: Per SNCP connection, a user can exclude TIMs from the switching conditions.
LPdTIM results in a consequent action that takes 3 TTI frames to clear, the TTI frame
during which the switch occurs is also lost, together 4 TTI frames = 32 ms.

• An unequipped virtual container (UNEQ);

• A degraded signal (DEG) condition occurs.

Note: The user can set the threshold for the DEG criteria (see Section 6.8.5 on Page 77).

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

Page 39
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

SNCP protection group. If multiple switch requests are simultaneously active, their hold-off
timers run independently. The switching is completed within 50 ms after fault detection plus the
hold off time.

Worker (from) and protection(prot) legs are linked to different Line Ports. The protected port
always links to a tributary port. The settings for the Non Intrusive Monitors (NIM) are retrieved
from the VC12 termination point (VC12TTP) associated with the protected (to-leg) port. This
applies to:
• Accepted TTI provisioning
• TIM setting
• Degraded Threshold setting
• monitoring mode

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

Note: NIM ports shared settings are retrieved from the last provisioned VC12 trail trace
termination point. The initial NIM settings are copied from the first associated VC12 trail
trace termination point with an SNCP protection group.

4.11.1 Non-intrusive Monitoring (NIM) of Line Ports

Note: Changing the termination settings for a protected VC12 termination point will also
be applied to the worker and protection NIM settings.
This may harm your configuration.

See also provisioning (see ).

4.11.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. This can be
done by removing either the worker or protection leg. Which makes a hitless conversion
possible even if the near end and the far end do not select the same path.
• Remove the SNCP protected cross-connect.

Page 40
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Provisioning notes:
• Swapping of worker (from-leg) and protection (prot-leg) requires two user operations.
First the from-leg is removed and next the prot-leg is assigned with the previous worker
leg.
• In order to change the leg of an SNCP protected cross-connect one needs to temporarily
convert the cross-connect into an unprotected one by removing the worker or protection
leg. After this a different protection leg can be added to the unprotected cross-connect
resulting in the changed SNCP protected cross-connect.

Caution: Also the test ports can be provisioned as an ordinary port, in fact it is an ordinary port
for which only the outgoing signal is made available. By changing the settings of the test port,
the above mentioned settings are used for the cross connect in stead of the settings of the
originally applied tributary port.

4.12 Port Loopback Functionality

The Systems supports port loopback on the following levels):

• E1 incoming
• E1 outgoing
• STM-1 outgoing

Figure shows port loopback functionality.

E1 Incoming Loopback

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

The implementation of an E1 port loopback results in inserting and forwarding VC12

unequipped. The consequent action of forwarding VC12 Unequipped for an incoming E1
loopback will finally result at the far end in generating E1 AIS (Unequipped is not defined for
E1).

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

Page 41
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Incoming Outgoing

VC12 unequipped AU4 MS-AIS

Test

IFC 1 LP 1

VC12

E1 AIS
IFC n LP 2

Outgoing

E1 AIS

Figure 21. Port Loopback Functions

E1 Outgoing Loopback

If you create an E1 outgoing port loopback an E1 AIS alarm is forwarded in the signal leaving
the system.

Note: There are no restrictions regarding the number of outgoing port loopbacks.

STM-1 Outgoing Loopback

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

Page 42
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

5 SYSTEM SOFTWARE SETUP

This section provides the information needed during the first set up of the System. Included are
an overview the physical connectors of the System, a description of the settings of the IP
parameters for accessing the System, and an overview of the Web browser (ASX GUI) set up
and behavior.

5.1 IP Address Management

The System can be managed via the 10/100BASE-T Ethernet LAN interface. To get access to
the management interface, the System must have a valid (known) IP address, in the subnet range
of the LAN it is connected to.

The first time a connection needs to be set-up with a web browser to the System, this can be
done with a direct PC to System LAN connection. The System has an integrated web server.
The Hi There utility can be used to discover that the System equipment is present on the LAN;
no router must be present between the System and PC.

The default address of the System is 10.127.127.1/8. Depending on the use of a DHCP server in
your network, you can provision the LAN port settings. The subnet mask notation /8 is equal to
255.0.0.0 (RFC950).

5.1.1 IP Management Without DHCP Error

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

A DHCP can be user controlled.

There are three options to change the IP settings:

• Via the web browser
• Using the IP2Box utility.
• Via the local management console port

All options have an equivalent result.

Figure 22 shows DHCP state transitions.

Page 43
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Figure 22. DHCP State Transitions

5.1.1.1 Provisioning via Local Console Control

Connect a PC to the local console port. Use a utility like ‘hyperterm’ or ‘putty’. When
connected to the System, a prompt appears. Press enter, type the password, adm123. Now you
have access to the functionality. To change the IP settings you have to type: dbs dr set_ip. The
format is:

dbs dr set_ip <ipAddress> <subNetMask> <defaultGateway> <DHCP>, with:

• <ipAddress> = <xxx.xxx.xxx.xxx>
• <subNetMask> = <xx>
• <defaultGateway> = <xxx.xxx.xxx.xxx>
• <DHCP> = <0 or 1>

Page 44
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Check the keyed in address carefully before entering the address. The System parameters will
directly apply.

Note: The provisioned default gateway should be reachable; otherwise 0.0.0.0 is applied.

5.1.1.2 Provisioning IP Address With DHCP Client

After a System recovery the System DHCP client will perform a number of attempts to obtain
an IP address/mask from a DHCP server (if DHCP is enabled). If this is successful, this IP
address/mask will become operational. If this is not successful, the System will fall back to its
default IP settings, but will keep trying to obtain a DHCP assigned address.When the default IP
settings are changed after the DHCP assignment, these settings will become operational.
Changing of the default IP settings in this case is similar to what has just been described for IP
management without a DHCP server (see Section 5.1.1 on Page 43).

Hi There Utility

Figure 23 shows the Hi There utility.

Figure 23. Hi There Utility

Page 45
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

The Hi There utility can be installed on a Windows PC. This utility is used to discover the
Systems on the subnet the PC is connected to. Each System is installed with a Hi There server
program. The System responds with its MAC address, IP address, sub net mask, IP default
gateway, and Linux host name.

From the Hi There utility, direct access can be obtained to the GUI, by selecting the requested
System with the right mouse button.

Note: In a situation where multiple Systems are using the default IP address, they can be
distinguished by their MAC address.

5.1.2 LAN Port Provisioning via Web Browser

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

From the System menu, select

SYSTEM | LAN SETTINGS

to display the LAN settings window (Figure 24).

Figure 24. LAN Port Settings

Interpret and set the fields as follows:

• IP Address—The factory programmed IP address is 10.127.127.1.

Note: After the change has been made, connection with the web browser could be lost and
has to be set up with the new address.

• Mask—The default value is 8. Values between 8 and 30 can be provisioned. Provision the
applicable value for your environment.
• Gateway—The factory programmed value is 0.0.0.0. You can provision the default
gateway address. This change will directly become effective if DHCP is disabled.

Page 46
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

• MAC Address—The MAC address of the System. The MAC address of the Systems
always starts with the Organization Unique Identifier (OUI) 00 0f 25. This is a read-only
value fixed for every System. The MAC address is also printed on the label present on the
System.

Note: In case of a DHCP assigned IP address, the IP address field does not reflect this
assigned address.

• DHCP—If you enable this option the System will immediately try to obtain the LAN IP
details (IP address, mask, gateway) from a DHCP server. If this fails the Default values
will be restored. These values are also used if you disable this option (again).

Note: The current gateway can be obtained via OSPF, in that case an IP interface address
of the ASBR System is shown or the IP address of the external access router/gateway. This
gateway address is only be applied if it can be reached directly without involvement of an
ASBR System.

5.1.3 LAN Provisioning in LP2Box

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

Figure 25. LP2Box Utility

Use the MAC address to connect to the System. Next fill in the requested IP address, Subnet
mask, and Default Gateway. Additionally a Host Name needs to be entered. Next select Assign
to apply the settings.

Two other fields of interest in this window:

• Validation—when selected, causes the utility to check on correctness of entered values. It
checks if the IP address entered already exists on the local subnetwork. If so, the user is
warned.
• Ping—Provides the ability to ping to an IP address of a System.

Note: The DHCP settings are not changed.

Page 47
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

5.2 GUI Settings and System Authorization

5.2.1 Introduction

The System has an integrated web server providing a Graphical User Interface (GUI) for
querying and provisioning the System. Browsers supported for use of the GUI are Mozilla
Firefox and Internet Explorer 6.0. This section contains instructions and guidelines for setting
up the web browser.

5.2.2 GUI Settings

A short list of settings required for the web browser:

• Enable Java scripting (if it is disabled, the 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 are shown in pop up windows.
• Set the screen size to 1024 (horizontal) by 768 (vertical).

5.2.3 GUI Features

The GUI has the following general features:

• Update After Edit—After a provisioning change has been made and Apply has been
selected, the window will reappear with the changes displayed.
• Field Colors Convention—Editable fields are clearly marked as yellow and non-editable
fields are non-colored. When the value of a field is changed during a provisioning action,
the field color changes to blue. Clicking the Apply button causes all changes currently
keyed in blue fields to be applied and the field color changes back to yellow. You can use
Refresh to cancel the provisioning action.
• Simultaneous Sessions—The System supports five different sessions simultaneously.
When a sixth session is started the first session will be closed automatically.
• Refresh Button—Every window has a refresh button, to get the current state of the
settings and statuses of the window.
• Smart Selection—The System tries to predict the next selection. This is applicable for
those windows in which a list is shown. This is the case when adding cross connects and
editing ports or termination points. When there is no next logical selection, no pre-
selection is made, but a list of valid termination points is always presented.
• Access to Related Items—In several menus, the quick navigation option is available to go
directly to related items. For example, from the SFP details window 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.

Page 48
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

5.2.4 User Groups, Logins, and Rights

Note: Login is case-sensitive.

The System supports three user groups. Per group, at least ten users can be supported. User
names are unique per system. Each user can change the password after entering the existing
password first. The user is required to enter the new password twice before the new password is
applied. By default, a number of login names are already 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 that
could normally trigger a change of system setting are made invisible.
The view group has one default login name:
– 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.
The view group has one default login name:
– Login name 1: user
– Password: adc123
– Login name 2: config
– Password: adc123

• admin group—Members of the admin group are responsible for maintenance activities
like software upgrading, database operations, user group administration and IP and SNMP
settings.
Only users in the admin group can create or remove users. They can also provide initial
passwords for new users. The password of already existing users can be changed by an
admin user without knowledge about the existing password.
There must always be at least one user in the admin group. For this reason the user admin
cannot be removed.
The admin group has one default login name:
– Login name: admin
– Password: adm123

Note: Also an expert/root user exists via which all the default password settings can be
restored to their factory defaults. Contact ADC for this procedure.

Note: The login screen and System layout differs per platform.

Page 49
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Note: The login screen contains the user name and password.

Caution: It is recommended to change the passwords of admin and config users after
installation.

5.2.5 ASX Login Screen

The welcome screen shown in Figure 26 contains the user identification and password.

Figure 26. ASX Login Screen

5.2.6 ASX GUI System Overview

The ASX System overview shown in Figure 27 represents the hardware with the eight tributary
slots shown and the eight E1 ports, separated in transmit (TX) and receive (RX) side. This
overview is independent of pluggable items being present or not.

Figure 27. ASX System Overview Window

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

• LAN POE—LAN settings (see )
• LP1/2—SFP details.
• ASX Icon—System details.
• ALM LEDs—Alarm list.

Page 50
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

• E1 Port—(Any port) Details of the E1 port provisioning. In this case, there’s no difference
when accessing it via RX or TX.
• Tributary Slot—(Any slot) Slot details.
• [!}—This button appears when the alarm situation changes: either a new alarm is raised or
an existing alarm has been cleared. Press [!] to clear this indicator.

For future releases:

• SERIAL—Access to the serial console port.
• B1/B2— Power connectors.

5.2.7 Log File for System Settings

The System maintains a log file (first in first out) to keep track of changes when system settings
are changed. Per event the log file include a time stamp, a user identification and a descriptive
text. The sort order depends on the provisioning moment. The size of the file is about 100 kB.
Contact ADC for details.

Only users of the admin group can access logfiles. They can download (Backup) them from the
System in WordPad format, as well as Delete them from the system.

Note: Deleting the logfile results in creating a new logfile which shows that the logfile was
deleted.

Note: The timestamp is on the UTC time.

5.2.8 Menu Structure

The menu structure is represented vertically.

The details of the menus are described (see on page ) except for the LAN settings which is
described in this section.

Note: Depending on the login rights (see page ) some menus are not shown.

Note: Use <Shift-Click> to open a new window or tab.

System menu

System | Details

System | IP Settings | Interfaces

System | IP Settings | Routes

Page 51
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

System | IP Settings | OSPF | General

System | IP Settings | OSPF | Interfaces

System | IP Settings | OSPF | System

System | Time

System | SNMP settings

System | Pluggable Items

Maintenance menu

Maintenance | Software | Details

Maintenance | Software | Install

Maintenance | Database

Maintenance | Log

Maintenance | Users

Maintenance | Logout

Alarms menu

Alarms | Current

Alarms | History

Alarms | Profile/Severtities

Alarms | GUI Settings

XConnects menu

XConnects | List

XConnects | Add Bidirectional | LP -> TP

XConnects | Add Bidirectional | TP -> LP

XConnects | Add Bidirectional | LP -> LP

XConnects | Add Bidirectional | TP -> TP

Page 52
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

XConnects | Add Unidirectional | LP -> TP

XConnects | Add Unidirectional | TP -> LP

XConnects | Add Unidirectional | LP -> LP

XConnects | Add Unidirectional | TP -> TP

XConnects | Add SNCP Bidir | LP1 -> TP <- LP2

XConnects | Add SNCP Bidir | LP2 -> TP <- LP1

XConnects | Add SNCP Unidir | LP1 -> TP < -LP2

XConnects | Add SNCP Unidir | LP2 -> TP < -LP1

Transmission menu

Transimission | Ports | Line Ports

Transimission | Ports | Trib Ports

Transimission | Termination Points | RS/MS

Transimission | Termination Points | VC4

Transimission | Termination Points | VC12

Transimission | Degraded Tresholds

Timing menu

Timing | System Timing

Timing | Timing Sources

MSP menu

MSP | Details

MSP | Create

Page 53
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Page 54
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

6 WEB BROWSER (ASX GUI) WINDOWS AND PROCEDURES

This section contains instructions for using the ASX GUI to provision the System. If a new user,
refer to Section 5.2 on Page 48 for information on setup and basic use of the GUI.

Note: When a login as admin is required, this is explicitly mentioned.

6.1 Master Index of Tasks

Table 7 lists the tasks that can be done with the ASX GUI and indicates which section of this
manual to refer to for more information.

Table 7. ASX GUI Master Index of Tasks

TASK # DESCRIPTION REFER TO SECTION

1 Log in, launch from startup (System overview) window to specific functions. 5.2 on Page 48
2 Determine, change the System time. 6.3 on Page 56
3 Determine the current status of pluggable items (IFCs and SFPs). 6.4.1 on Page 58
4 Display, edit details for an Interface Card (IFC). 6.4.2 on Page 58
5 Replace an IFC (causing the new IFC to become “accepted” and “assigned”). 6.4.3 on Page 60
6 Display, edit details for a Small Form-factor Pluggable (SFP). 6.4.4 on Page 60
7 Replace an SFP (causing the new SFP to become “accepted” and “assigned”). 6.4.5 on Page 61
8 Respond to a System recovery; interpret the console port alarm status signals. 6.5 on Page 62
9 Check which software memory bank is active; switch to the other bank. 6.6 on Page 62
10 Backup, copy, rename, activate, restore, or delete a System database. 6.7 on Page 65
11 Provision a specific Line Port (LP1/2) for a specific IFC. 6.8.2 on Page 69
12 Provision a specific Tributary Port (TP1-8) for a specific IFC. 6.8.3 on Page 70
13 Provision a termination point for an RS/MS section, VC4, or VC12. 6.8.4 on Page 72
14 Provision a threshold for a termination point “degraded signal alarm.” 6.8.5 on Page 77
15 Provision a Trail Trace Identifier (TTI) for a trail termination point TIM alarm. 6.8.6 on Page 78
16 List all existing cross connects; edit or delete a cross connect. 6.9.2 on Page 83
17 Add a bidirectional cross connect (LP->TP, TP->LP, LP->LP, TP->TP). 6.9.3.1 on Page 85
18 Add a unidirectional cross connect (LP->TP, TP->LP, LP->LP, TP->TP). 6.9.3.2 on Page 86
19 Add an SNCP bi/unidirectional cross connect (LP1->TP<-LP2, LP2->TP<-LP1). 6.9.3.3 on Page 87
20 Swap worker and protection legs for an SNCP cross connect. 6.9.3.4 on Page 88
21 Create, provision a Multiple Section Protection (MSP) pair for an STM-1. 6.10 on Page 89
22 Synchronize the SDH network to one master clock; provision timing sources. 6.11 on Page 95
23 Provision the SNMP manager IP address, traps, and alarm community. 6.12 on Page 105
24 Provision Open Shortest Path First (OSPF) settings. 6.13 on Page 107
25 View and respond to System alarms. 7 on Page 113

Page 55
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

6.2 Transmission Terms and Definitions

This is a short overview of the transmission terms and definitions used throughout this section.
• Downstream—The direction coming from the STM-1 aggregate side into the System, the
de-multiplexing direction.
• Upstream—The direction from the termination points towards the STM-1 aggregate side.
The multiplexing direction.
• Near End—The System at the local side of a protected connection..
• Far End—The system terminating the transmission point at the other side of a protected
connection.
• Connection—An end-to-end related path carrying service, which is terminated at both
ends.
• Consequent Action—An autonomous action of the System. When a failure in the System
is detected this is reported as an alarm. This action will insert (for example, an AIS signal)
in the downstream direction or an 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.

6.3 System Time

The System has an accurate real time clock on board that provides the System time. This
System time is used to add a time stamp to reported alarms on the web browser and SNMP
traps/notifications.

When no time is set, the default Linux time is taken at startup: January 1, 1970. The SYScTIME
alarm is reported. The accuracy of the real time clock is ± 4.6 ppm or better.

The System software synchronizes the real-time clock to the network timing (see Section 6.11,
Synchronization, on Page 95). The real time clock has an inaccuracy of less then three minutes
per year.

6.3.1 System - Time Window

The System Time window is used to view or set the System time. Figure 28 shows the System
Time window. Table 8 describes the System Time window fields. To display the window, select
the following from the ASX GUI menu:

SYSTEM | TIME

Page 56
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Figure 28. System Time Window

Table 8. System Time Window Fields

FIELD NAME DESCRIPTION COMMENT

System Time Shows current System time A refresh is needed to get the
current value
Host Date and Time Shows date and time PC con- This field is continuously
(Local or UTC) nected to System updated

6.3.2 Changing the Time

Changing the time can be done in two ways using the System - Time window:
• To place the current Host date and time to the System time, click on the Sync button.
• To key in a System time, key in the values in the System time field. Be sure to use the
correct format and values, then click on Edit.

6.4 Pluggable Items

Pluggable items are of two types, Small Form Factor Pluggables (SFPs) and Interface Cards
(IFCs), which are identified in terms of the Tributary Slot (TS) in which they are installed.
Pluggable items are “hot pluggable” (they can be inserted and removed while the system is
powered on).

Caution: Pluggable items (SFPs and Interface Cards) need to be handled according to ESD
guidelines.

Page 57
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

6.4.1 Pluggable Items Selector Window

The Pluggable Items Selector window shows the current status of all pluggable items known to
the System. Table 29 shows the Pluggable Items window. Table 9 describes the fields. To
display the window, select the following from the ASX GUI menu:

SYSTEM | PLUGGABLE ITEMS

Figure 29. Pluggable Items Selector Window

Table 9. Pluggable Items Selector Window Fields

FIELD NAME DESCRIPTION COMMENT

Interface Card Will be either SFPn for Small Selecting an item will show
Form Pluggable or TSn for Trib- the details
utary Slot where n is the number
of that item
Status Assigned or Auto See following topics

6.4.2 Interface Card (IFC)

In the Pluggable Items Selector, Interface Cards are identified as Tributary Slots (TS), each with
a unique item number. The System supports the ADC101 Interface Card. The System will
automatically discover an inserted Interface Card (IFC). The default tributary slot state is
AUTO. When the IFC has a supported item code (ADC101-ADC120), the state will change
from AUTO to ASSIGNED and the IFC will be operational; this takes less than one minute.

Selecting the desired TS (Tributary Slot) displays the details for that item. Figure 30 shows the
Interface Card Details window. Table 10 describes the fields.

Page 58
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Figure 30. Interface Card Details Window

Table 10. Interface Cards Details Window Fields

FIELD NAME COMMENT

Current State When the inserted IFC has an item code that is not supported, the state will
remain AUTO and IFCcWUI (IFC Wrong Unit Inserted) is reported. When the
inserted IFC is defective an IFCcEQF (IFC Equipment Failure) is reported. The
IFC needs to be replaced by a correct one. When no IFC is present in
ASSIGNED mode and IFCcUNP is reported (IFC Unit Not Present), this will
be due to a removal. In AUTO mode no reporting of a Unit not Present is done
Item Code The item code identifies the type of Interface Card. Currently the ADC101 is
available for the Systems. The ADC101 has 8 ports E1 (G.703) 120 Ohm ports
with ADC LSA-PLUS IDC edge connectors. The System is prepared for future
versions of Interface Cards, as item code ADC101 up to ADC120 is supported
in this release
Catalog Number The catalog number of the interface card without connector. (Note: Interface
cards can only be ordered including a connector. A short ordering list is
included in this manual)
Serial Number The serial number of the selected IFC. This number is factory assigned per
product and is useful for tracking hardware
Last Accepted The item code of the IFC which was present and accepted before the current
one. This information is of use when in future more item codes are supported,
and IFC replacements are performed
Change State to This can be used when the state of a slot is ASSIGNED while the IFC has been
Auto removed, and no alarming for this situation is required. This operation might be
service affecting when an Interface Card is present
Accept Plugga- This can be used when an IFC has been replaced with another type (item code).
ble Item This will be of use when more item codes are supported. When before execut-
ing this operation traffic is running, this action is not service affecting

Page 59
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

6.4.3 IFC Replacement

When an IFC is replaced with another IFC having a different but supported item code, an
IFCcREPL alarm is reported and the user has the option to accept this IFC. The alarm notifies
the user of the change in item code.

In the last accepted field, the user can view the previous item code and can decide if the change
is requested. When Accept Pluggable Item is selected, the inserted IFC becomes ASSIGNED.
All provisioning regarding this IFC is taken over.

Behavior When No Interface Card is inserted

When no IFC is inserted, the related VC12 termination points are available, but in an upstream
direction AIS is inserted into the payload (E1 signal). When VC12 termination point settings
are provisioned, they do not become effective until an IFC is inserted. In this situation, you can
pre-provision the VC12 TTP.

6.4.4 Small Form Pluggable

The System has two SFP positions related to the line ports. When an SFP is selected in the
Pluggable Items Selector window, the details for the SFP are displayed in a details window.
Figure 31 shows the Pluggable Items Details window. Table 11 describes the fields.

Figure 31. SFP Details Window

Page 60
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 11. SFP Details Window Fields

FIELD NAME COMMENT

Current State ASSIGNED: The current SFP is accepted and operational, when no alarms are
present. AUTO: No SFP is present or the inserted SFP is not accepted, see SFP
replacement and acceptance for more details
Qualifier Identifies the type of SFP per ITU-T G.957. All module qualifiers are accepted
by the System. The module qualifier for optical SFPs has the format I/S/L-X.Y.
in which I/S/L identifies if it is a intra(I), short(S) or long(L) haul; X identifies
the rate of the SFP (1 – 155 Mb/s, 4 – 622 Mb/s); and Y identifies the wave-
length of the SFP (1 – 1310 nm, 2 – 1550 nm, 3 – 1550 nm dispersion shifted).
Example: S1.1 is a short haul 1310 nm STM-1 SFP.
Notes: (1) Electrical SFPs will have STM1-e as module qualifier. (2) If the
module qualifier can’t be determined it will get the Unknown qualifier. This
can be due to vendors not following the inventory coding. These SFPs will be
accepted
Wavelength 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 The connector type, transceiver code and length are for troubleshooting pur-
poses. Check the Multi Source Agreement (MSA SFP-8074) of the SFP for
more details
Last Accepted Indicates the type of SFP which was accepted previously. This is important
when the SFP has been replaced

6.4.5 SFP Replacement and Acceptance

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

6.4.6 Single Fiber SFPs

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

Page 61
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

6.5 System Recovery

Some actions related to the System software or database may result in a System recovery. A
System recovery takes about three minutes. A System recovery is not service affecting.
Communication with the web browser(s) and SNMP manager(s) are lost. Two minutes after the
recovery, the user can login again. After the System has come up, a cold restart trap is sent to the
provisioned SNMP manager(s).

In case of a system upgrade, the status of the System is indicated as soaked.

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

Note: A user can define the alarm priorities (see Section 7.5, Alarm Profiles, Severities,
Reporting, and LEDs, on Page 116).

Note: An alarm output is set if an alarm with the appropriate severity is present, also if the
cause is remotely detected (for example, receiving an AIS). Note that only a locally
detected cause of an alarm contributes to the alarm LEDs (see Section 7.5.3, LED
Indicators, on Page 118).

Note: The alarm output is steady. For example, in case of a loss of signal, the output is
continuously on.

6.6 System Software

The System supports one Load Line. The current System software release is:

release 1.3 with Item code ADW130(B)

The System has two software memory banks called Bank 1 and Bank 2. Bank 1 contains the
active Image System Database (ISD) and Bank 2 the inactive. The memory banks can be
queried using the window shown in Figure 32.

Page 62
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 8 summarizes the possible combinations of bank statuses that may be shown in the
window. To display the window, select the following from the ASX GUI menu:

MAINTENANCE | SYSTEM | DETAILS

Figure 32. ISD Details Window

Table 12. ISD Details Bank Status Summary

Image Status
Bank 1 Bank 2 Meaning
Active Inactive Normal situation. Both banks are filled and the software in Bank 1 is currently
running
Active Soak A software upgrade has taken place and the sanity process is not yet finished.
The software in Bank 1 is currently running. When the sanity process is fin-
ished, the new status (either Bank1 or Bank2) is Active or Inactive if the
upgrade is successful, or Soak or Error if a recovery has taken place before
expiration of the sanity timer
Soak Error during last An ISD switch has been unsuccessful (only applicable for the inactive bank).
image transition If this error occurs, the image is valid but a transition error occurred. The
action can be repeated and become successful
Active Empty Normal situation for a System leaving the factory. Bank 2 is empty and the
software of Bank 1 is running

6.6.1 Selecting an Inactive ISD

Note: This option is only available for the ‘admin’ user.

When an inactive ISD is selected, the System switches over to the inactive ISD. The System will
recover and connection to the Web browser is lost.

Page 63
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

This action will be performed when a software upgrade is required. Before activating the
inactive ISD, check that the ISD status is in fact Inactive and that ISD specific details such as
Item code and software version correspond with the ISD requested. During recovery, the
System database will be converted when necessary to the new software version.

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

During recovery after an ISD switch, a sanity timer is running. This timer enables the System to
fall back to the previous ISD when the switch was not successful (for example, due to a conflict
in the database). In this way, service is never affected. When a switch is unsuccessful, check
whether the upgrade you were performing is supported. The sanity timer will run for about one
minute after the System is manageable.
Some other facts to be aware of:
1. System recovery takes about three minutes.
2. After the recovery is done, you can login to the System; alarm evaluation has been
completed.
3. Do not perform any database manipulations or provisioning changes during this period. If
the system restarts (for example, due to a power cycle) while the sanity timer is running,
the System selects the previous active software. The database changes made during the
sanity period are lost.

Check after the System is up again whether the requested ISD is active. (Bank 1 always contains
the active ISD.) When a switch over was not successful, the state of the second bank is “error
during last image transition.” This could be caused by a power outage during recovery.

A software upgrade is not service affecting when correctly carried out.

Caution: After a software upgrade has been performed do not attempt any changes in the
System configuration within one minute after you login.

To upload a new ISD to the inactive bank, select

MAINTENANCE | SOFTWARE | INSTALL

to display the software install dialog shown in Figure 33.

Figure 33. Software Install Dialog

Page 64
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Click on Browse to browse on the PC for the ISD of interest. Select the ISD to be installed.
When selected, the ISD is uploaded to the System. This will take about five minutes. The size of
an ISD is about 6.5 Mb.

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

A progress indicator is displayed in the dialog as shown in Figure 34.

Figure 34. Progress Indicator

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

When the upload is finished, the details of the uploaded ISD are shown in a separate window
(Figure 35).

Figure 35. Software Upload Completed

Note: The Software Version number in this figure (above) is shown as an example only; it
is not the most recent version number of the software.

6.7 System Database

A new System has one database, the default database: addf.db. This default database is included
in the System software and will never be lost. Database handling can only be executed by
‘admin’ users. The System supports eight databases, of which one is active.

To display an overview of all database, select the following from the ASX GUI menu

MAINTENANCE | DATABASES

Page 65
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

to display the Database Listing window (Figure 36).

Figure 36. Database Listing Window

The databases can be identified by name. The currently active database is identified by the
postfix “(active)”.

6.7.1 Selecting a New Database

Selecting a new database may result in incompatibility between the current running software
and the structure of the selected database. For this reason, so called database conversion scripts
are needed, included in the active ISD.

Conversion is only supported from a lower to a higher database version. If for example a
database version #1 is selected while the current running software is supporting database
version #3, a conversion form #1 -> #3 is needed. The System first converts #1 -> #2 followed
by a conversion from #2 -> #3. The original (#1) and intermediate (#2) database (or multiple
intermediate databases, if present) are removed by the system. For fail safe operation, the user
can make a backup of this database by downloading it to a host system.

Note: The converted database gets the hardware identification of the hardware on which
the conversion takes place.

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

Page 66
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

1. A database is selected for which conversion is required but no tooling or script is available.
Note that this implies that the selection of a database with a version number higher than
the current active database version number is rejected.
2. The database file is not existing because it has been removed by a concurrent database
operation.
3. The database does not match the system hardware.
4. Communication with the system is lost due to a concurrent operation which result is a
recovery (for example, 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, ADH104, ASX

6.7.2 Database Maintenance

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

impact.

For database maintenance, use the Database Listing window (shown in Figure 36 on Page 66).

MENU: MAINTENANCE | DATABASES

6.7.2.1 Restoring a Database

Using this option, a database can be uploaded to the System. Using Browse, select the desired
on the PC connected to the System. A database can be recognized by the extension .db.
A database restore usually takes less than one minute (depending on your network connection).
The typical database size is about 100 Kbytes. When finished, the uploaded database will be
shown in the database list.

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

6.7.2.2 Backing Up a Database

With the backup option, a copy (download) of the selected database can be made on the
connected PC.
To backup a database, select it and click on the Backup button. Follow the instructions.

6.7.2.3 Renaming a Database

To delete a database, select it and click on the Rename button.

Page 67
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Note: Key in the new name without entering the .db extension.

6.7.2.4 Deleting a Database

Deleting the database removes the database from the System. When an active database is
deleted, the System will recover and come up with the default database, retaining the database
name; service will be lost. The SNMP, OSPF, and IP settings are not 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.

To delete a database, select it and click on the Delete button.

6.7.2.5 Activating a Database

Activating a database causes the System to recover; connection to the Web browser is lost.
When the selected database has different settings than the current one, transmission is also
affected. When the selected database has identical settings, transmission is not affected.

To activate a database, select it and click on the Set as Active button.

6.7.2.6 Copying an Active Database

This option makes a copy of the active database. The database copy will have the filename
entered. The database copy will be stored on the System.

Figure 37 shows the dialog used for entering the filename. After keying in the filename, click on
the Apply button to complete the copy.

Figure 37. Database Copy Active Dialog

Using Database Copies for Multiple Systems

A database copy of one System can be used at another System of the same hardware platform
type. Specific databases can be prepared on one System and then uploaded to Systems in the
field. In this way, the multiple Systems can be operational in a short time.

Page 68
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Using Database Copies for Specific Situations

Database copies can also be prepared for specific situations, like emergency cases. The database
copies can be stored and used as needed. When a situation occurs for which a database copy has
been prepared, the database copy can be set to active.

6.8 Ports and Termination Points

6.8.1 Ports

The System has two STM-1 line ports and 8 E1 tributary ports per interface card.

Monitoring Mode

A common concept in provisioning of the line and tributary ports is the monitoring mode. The
monitoring mode of a port controls the alarm reporting. The default value is AUTO. The options
for the monitoring mode are:
• MONITORED—In this mode, alarm reporting is on.
• AUTO—In this mode, no alarms are reported.
• NOT MONITORED—In this mode, no alarms are reported.

The AUTO mode has an AUTO mode timer for which the default value is 10 minutes. A port in
AUTO mode goes to MONITORED when a valid signal is continuously present on the port for
greater than the period of time specified in the AUTO mode time. The timer starts whenever a
valid signal is detected. The AUTO mode timer can be provisioned between 0 and 30 minutes in
steps of one minute.

6.8.2 Line Ports

The Line Ports Selector window (Figure 38) shows the current monitor mode and Out
Loopback state of the two Line Ports. To display the window, use:

MENU: TRANSMISSION | PORTS | LINE PORTS

Figure 38. Line Ports Selector Window

Page 69
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

To provision a Line Port, select the Line Port name and click on the Edit button to display the
Line Port Details window, shown in Figure 39.

Figure 39. Line Port Details Window

After the Line Port is displayed, you can proceed to provision the Line Port. The Port
Automode Time, Port Monitor Mode, and Out Loopback values can be provisioned.

Force Do Not Use

By default, the Force Do Not Use value is disabled. When this value is set to Enabled, the SSM
out value will be set to “Do Not Use” (SSM value 1111). The far end system connected to this
line port will not select this signal for synchronization when QL enabled is selected. For more
information on synchronization, see Section 6.11, Synchronization, on Page 95.

6.8.3 Tributary Ports

The E1 tributary ports support unframed E1 transmission. In fact, they are transparent for any
type of 2 Mb/s signal according to ITU-T G.703; for example, they are framed with or without
CAS (Channel Associated Signalling).

Note: In the selection list of tributary ports, only those ports are shown of ASSIGNED
Interface Cards.

The tributary port selection can be made using the Tributary Ports Selector window, shown in
Figure 40. To display the window, use:

MENU: TRANSMISSION | PORTS | TRIB PORTS

Page 70
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Figure 40. Tributary Ports Selector

To display the details for a tributary port, select the port and click on the Edit button. Figure 41
shows the Tributary Port Details window.

Figure 41. Tributary Port Details Window

After displaying the port details, you can proceed to provision the port. The Port AutoMode
Time, Port Monitor Mode, and User Label can be provisioned. The user label is displayed
during E1 port provisioning, the provisioning of a cross connect involving a tributary port, and
for an E1/VC12 termination point related alarm.

Note: Changing the User 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 (Section 6.11.7, Retiming E1 Ports, on
Page 103).

Default value for the Timing Mode setting is “Self Timed.” In this mode, the retiming option is
disabled. See Section 6.11.7, Retiming E1 Ports, on Page 103.

Page 71
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

In the Tributary Port Selector window (shown in Figure 40 on Page 71), the Loopback field is
set to “In Loopback” (see Section 4.12, Port Loopback Functionality, on Page 41).

6.8.4 Termination Points

At a termination point, the virtual container is terminated (sink) and constructed (source). The
following levels of termination points can be accessed:
• RS and MS Regenerator section (see “RS and MS Section” below)
• VC4 (see page )
• VC12

6.8.4.1 RS and MS Section

The RS and MS termination point selection can be using the RS/MS Selection window shown in
Figure 42. To display the window, use:

MENU: TRANSMISSION | TERMINATION POINTS | RS/MS

Figure 42. RS/MS Selection Window

The RS and MS termination points are direct related to the physical line ports. The monitoring
mode therefore cannot be provisioned and is slaved to the related line port mode. The
monitoring mode of the RS/MS TTPs controls the alarming on these points. Use Edit to show
the details of the selected RS/MS termination point (Figure 43).

Page 72
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Figure 43. RS/MS Details Window

RS Termination Point

For the RS termination point (rsTTP), the J0 byte Trail Trace identifier can be provisioned (see
Section 6.8.6, Trail Trace Identifier Provision and Handling, on Page 78). Specific for the J0
byte is, in the Non specific byte mode the J0 value is 01.

MS Termination Point

For the MS termination point (msTTP), the degraded threshold value set can be selected. This
defines the threshold at which an MS degraded alarm will be reported.Two sets are available.
These sets can be provisioned separately (see Section 6.8.5, Degraded Threshold Provisioning
and Handling, on Page 77).

6.8.4.2 VC4 Termination Points

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

The default monitoring mode of the VC4 termination points is monitored. The VC4 TTP
monitoring mode controls the alarming on this point, except for the VC4cPLM and VC4cLOM
which will be reported irrespective of the monitoring mode (see Section 7.6, Resolving Alarms,
on Page 118 ).

To select a VCR ports for provisioning, use the selector window (Figure 44). To display the
window, use:

MENU TRANSMISSION | TERMINATION POINTS | VC4

Page 73
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Figure 44. VC4 Termination Points Selector Window

Note: When MSP protection is enabled, the VC4 termination point related to the
protection line port does not exist (see Section 6.10, Transmission Protection MSP, on
Page 89).

Use Edit to get the details of the selected termination point (Figure 45).

Figure 45. VC4 Termination Point Details Window

Table 13 describes the fields.

Page 74
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 13. VC12 Termination Point Fields

FIELD NAME DESCRIPTION

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

6.8.4.3 VC12 Termination Point

The System has 64 VC12 termination points. Irrespective of the presence of Interface Cards, the
VC12 terminations points are available.

The list of VC12 termination points can be retrieved using the window shown in Figure 46. To
display the window, select the following from the System menu:

TRANSMISSION | TERMINATION POINTS | VC12

Page 75
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Figure 46. VC12 Termination Point Selector Window

The default monitoring mode of a VC12 termination point is Not Monitored.

Note: When applying a bidirectional cross connect, or unidirectional in which the VC12
TTP is the To point toward a VC12 termination point, the monitoring mode will be set to
Monitored.

Use Edit to get the details of the VC12 termination point in the details window (Figure 47).
Table 14 describes the fields.

Figure 47. VC12 Termination Point Details Window

Page 76
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 14. VC12 Termination Point Details Fields

FIELD NAME DESCRIPTION

Trail Trace The default mode is repeating byte. Fore more details, see Section 6.8.6, Trail
Trace Identifier Provision and Handling, on Page 78
Trace Signal Label The trail signal label (V5 byte) identifies the type of traffic in the VC12 container.
The transmitted signal label is fixed asynchronous (02). The accepted (received)
TSL must be asynchronous (02) or equipped (01), other values indicate a type of
traffic not supported by the System.
A VC12cPLM (Payload Mismatch) alarm will be raised when the accepted TSL
has a different value then 01 or 02. As consequent action AIS is inserted down-
stream. The VC12cPLM alarm is not under control of the monitoring flag.
In case the TSL has a value 0, indicating unequipped, a VC12cUNEQ alarm is
raised. This might be due to no VC12 cross connect present at the far end or inter-
mediate 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
Section 7.6, Resolving Alarms, on Page 118).
– 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 Moni-
tored when a bidirectional cross connect is applied towards this VC12 TTP, or
when a unidirectional cross connect is made with the VC12 TTP as to point. When
deleting the cross connect the monitoring mode remains as it was. When no alarm
reporting is required or after the cross-connect is removed, the monitoring mode
can be set to not monitored
Degraded Threshold A choice can be made for threshold set 1 or 2 (see Section 6.8.5, Degraded Thresh-
old Provisioning and Handling, on Page 77). The specific values for these sets can
be provisioned with
MENU: TRANSMISSION | DEGRADED THRESHOLDS

6.8.5 Degraded Threshold Provisioning and Handling

For every termination point, two sets of degraded thresholds can be provisioned. The value of
the provisioned degraded threshold defines the number of background block errors in the related
path or section overhead which lead to a Degraded Signal alarm, when the number is exceeded.
When using MSP protection, an MS degraded can cause a protection switch.

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

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

The degraded thresholds can be provisioned for MS, VC4 and VC12 level, as shown in
Table 15.

Page 77
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Table 15. Degraded Threshold Levels

RELATIVE VALUE OF
SIGNAL LEVEL DEFAULT VALUE THE DEFAULT RANGE
STM-1 (MS) 28800 15% 1..192000
VC4 2400 30% 1..8000
VC12 600 30% 1..2000

The degraded threshold can be defined as two global sets per level, and per specific termination
point the threshold set 1 or 2 can be chosen.

To get the global set for all values, use the Degraded Thresholds Overview window (Figure 48).
You can display the window using:

MENU: TRANSMISSION | DEGRADED THREHOLDS

Figure 48. Degraded Thresholds Overview Window

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

6.8.6 Trail Trace Identifier Provision and Handling

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

Page 78
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

• Transmitted TTI: The TTI inserted in the section/path overhead.

• Expected TTI: The expected TTI.
• Accepted TTI: The received TTI.

Trail Trace Identifier Modes

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

6.8.7 Provisioning Trail Trace Identifiers

When selecting a requested termination point to be changed, the trail trace identifiers can be
provisioned. This behavior is similar for all levels VC12, VC4 and RS. The example is a VC12
level (Figure 49). Table 16 describes the fields.

Figure 49. Trail Trace Provisioning Window

Page 79
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Table 16. Trail Trace Provisioning Fields

FIELD NAME DESCRIPTION

Trail Trace Identifier
Accepted Status Indicates the status of the accepted trail trace:
– Normal: Accepted TT1 is valid. In this case, also, the fields Accepted Mode and
Accepted Value are visible. The Accepted Value field can be represented in ascii
hexa decimal format by clicking on the toggle ascii/hex.
– AIS: The container contains AIS, no TT1 available.
– Unavailable: The TT1 value cannot be determined. This might be due to an
unstable accepted TT1.
– Unequipped: The VC12/VC4 container has an unequipped signal label, not
applicable for RS
Expected Mode Provisionable expected mode: String or Repeating byte mode
Expected The trail trace identifier (string or bytes) expected by the system
Transmitted Mode Provisionable mode: String or Repeating byte mode
Transmitted The trail trace identifier (string or bytes) to transmit
TIM Detection When this check box is enabled, trace identifier mismatch will be checked. An
alarm will be reported and as consequent action AIS will be inserted downstream
and RDI in the upstream direction. VC12 RDI is sent upstream only in case of a
bidirectional cross connect
Trail Signal Label
Accepted Status See above
Transmitted See above
General
Degraded Threshold The degraded threshold 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.
When no alarming is required the mode can be set to Not Monitored
Directionality Cross connect type associated with the termination point
Threshold 1 Duration/ Per VC12 termination point you can specify when a signal is considered to be
Count OR degraded (DEG is declared). For this purpose you can choose from two sets of val-
Threshold 2 Duration/ ues:
Count Threshold set 1 existing of:
Threshold 1 Duration (in seconds) and
Threshold 1 Count
Threshold set 2 existing of:
Threshold 2 Duration (in seconds) and
Threshold 2 Count
A signal is considered to be degraded (DEG is declared) if within a number of con-
secutive seconds a number of block errors per second has been detected. The inter-
vals can be specified with Threshold 1 Duration or Threshold 2 Duration, the
number of block errors with Threshold 1 Count or Threshold 2 Count.
The degraded signal is withdrawn if within the number of consecutive seconds the
number of block errors, for each second, was smaller than the specified value

Page 80
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

6.8.8 Remote Error Indication

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

6.9 Cross Connects

To provide transmission over the System, cross connects have to be provisioned. From each line
port, a fixed VC4 cross connect is present towards the low order cross connect function. Within
this low order cross connect, VC12 cross connects can be provisioned. Cross connects can be
made full flexible, from:
• Every tributary port towards every TU12 (klm) on the line port, and vice versa
• Among line ports
• Among tributary ports

The actions on cross connects consist of adding and deleting cross connects. Two basic types of
cross connects can be made
• Unidirectional
• Bidirectional

These types will be outlined in detail.

6.9.1 Definitions

Cross connects can be added and deleted. In this section, the parameters for provisioning them
are listed.

From

The From point in a cross connect defines the originating point. Choosing which point will
become the From is mainly of importance when adding unidirectional cross connects. Note that
from an existing cross connect the from point can be edited, however this is not possible from
the To point.

To

The To point in a cross connect defines the destination point. At this point the VC12 path
overhead is terminated if it is a VC12 termination point. In the System, VC12 termination
points only exist at the tributary slot related points.

Path Protection (VC12 SNCP)

The System supports VC12 SNCP path protection. The protection switch can be triggered to
become active if a TIM (Trace Identifier Mismatch), an UNEQ (unequipped VC), or a DEg

Page 81
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

(degraded signal) condition exists on the service connection (if the stand-by connection does not
show these defects).

VC12 Termination Point

At a VC12 termination point, the VC12 path is terminated to a To point and generated at a From
point. The provisioning of the VC12 termination point can be made (see Section 6.8, Ports and
Termination Points, on Page 69). VC12 termination points only exist at the tributary port. There
is a fixed relation between the tributary port number and the VC12 TTP number. There are
noted as TSX.Y where X is the slot position and Y is the port number. Cross connects can be
added irrespective of the presence of Interface Cards.

TU12 Connection Termination Points

Note: For related alarms, refer to Section 7.6, Resolving Alarms, on Page 118.

TU12 connection termination points exist at the line ports. These points are noted as LPX.klm
where X is the line port and klm identifies the position of the TU12 in the VC4, the so-called
TU12 numbering:
• k = 1...3 = TUG3
• l = 1...7 = TUG2
• m = 1...3 = TU12

The line port TU12 points are not terminated in the System at the end points of a VC12 path. In
fact, the line port points are TU12 non-intrusive points; no overhead is added or extracted.

When MSP is provisioned, only the TU12 points from the MSP leg are available.

If the not cross connected TU12s, VC12 unequipped is inserted in upstream direction.

Type

The type identifies if the cross connect is bidirectional or unidirectional. The following
definitions apply:

Bidirectional

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

• Line port and tributary port—Traffic coming from the line port is dropped to the
connected port (downstream) and traffic from the tributary port is added to the line port
signal (upstream).
• Tributary and tributary port—Traffic is connected in both directions between two
tributary ports.

Page 82
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Line port and line port—Traffic is connected in both direction at TU12 level between the
line ports selected. This connection type can be used when there is no need to drop traffic
in this System. This type is called through cross connect.

Unidirectional

A unidirectional cross connect supports traffic in one direction. Coming from the From point
towards the To point. For the unidirectional cross connect several applications do exist. Major
difference with the bidirectional is that unidirectional cross connects can be made between two
free points but also can be added to the from point of an existing cross connect (bridging) They
only can be added to the from point, you have to realize this when adding cross connects which
you later want to bridge with a unidirectional cross connect.

• Loop back cross connect—A unidirectional cross connect with the same from and to
point, can be used as a VC12 loop back.
• Broadcasting—Uni directional cross connects can be multiple bridged. In this way a
broadcast function is supported. Multiple outputs are provided with one source signal. The
source signal is coming from the “From” point. The number of bridged points is unlimited.
The return path is unassigned. A point which is once being used as a “To” point can only
be used once.

Unidirectional cross connects can be made between the same type of points as bidirectional. As
unidirectional cross connects do not have a return path no RDI and REI will be inserted.

6.9.2 Listing, Editing, and Deleting Cross Connects

To delete or edit cross connects use the Cross Connect List window (Figure 50). To display the
window, select:

MENU: XCONNECT | LIST

Figure 50. Cross Connect List Window

Page 83
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

6.9.2.1 Displaying Cross Connect Details

To show and modify the settings of the cross connect, select the cross connect in the Cross
Connect List window.

Note: If a user considers that in the future an unprotected cross connect might be changed
into a protected it is important to realize that LP<->TP is different than TP<->LP. Only the
first one allowed the conversion to a protected cross connect.

Figure 51. XConnect Details Window

6.9.2.2 Editing a Cross Connect

To edit a cross connect, select the cross connect in the Cross Connect List window, select the
new From / Protection points, and click on Apply.

6.9.2.3 Deleting a Cross Connect

To delete a cross connect, select the cross connect in the Cross Connect List window and click
on Delete. No further message is shown and transmission via this cross connect will be lost.

6.9.3 Adding Cross Connects

The System supports sequentially adding cross connects. After a cross connect has been added,
the window returns with a pre-selection for the next logical selection. When no next logical
selection is available, no pre-selection is made. In the selection list, only available cross connect
candidates are listed. Once a point has been cross connected, it will be removed from the
selection list. Supported are:
• Bidirectional cross connects (see Section 6.9.3.1 below)
• Unidirectional cross connects (see Section 6.9.3.2 on Page 86)

Page 84
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

• Protected SNCP Bidirectional cross connects (see Section 6.9.3.3 on Page 87)
• Protected SNCP Unidirectional cross connects (see Section 6.9.3.4 on Page 88)

6.9.3.1 Bidirectional Cross Connects

Adding a bidirectional cross connect sets the VC12 termination point(s) involved to monitored.
Adding a unidirectional cross connect sets the mode to monitored if the VC12 termination point
is the To point. Deleting a cross connect will not change the monitoring mode. For a
bidirectional cross connect, a VC12 termination point is not always involved. When connecting
to a line port, a TU12 CTP (connection termination point) is involved and these do not have a
monitoring mode.

To add a bidirectional cross connect, select:

MENU: CROSS CONNECTS | ADD BI DIRECTIONAL

then select from the following options:

• LP -> TP
• TP -> LP
• LP -> LP
• TP -> TP

Figure 52 shows an example.

Figure 52. Add Bidirectional Cross-Connect

Select the desired to and from point, then click on Add. The cross connect will be established.
If you assign a user label, it is also shown in the screen. For more information on user labels,
refer to Section 6.8.3, Tributary Ports, on Page 70.

Page 85
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

6.9.3.2 Unidirectional Cross Connects

Adding a bidirectional cross connect will set the VC12 termination point(s) involved to
monitored. Adding a unidirectional cross connect will set the mode to monitored if the VC12
termination point is the To point. Deleting a cross connect will not change the monitoring mode.
For a bidirectional cross connect, a VC12 termination point is not always involved. When
connecting to a line port, a TU12 CTP (connection termination point) is involved and these do
not have a monitoring mode.

To add a unidirectional cross connect, select:

MENU: CROSS CONNECTS | ADD UNI DIRECTIONAL

then select from the following options:

• LP -> TP
• TP -> LP
• LP -> LP
• TP -> TP

Figure 53 shows an example.

Figure 53. Add Unidirectional Cross Connect

Select the desired to and from point, the click on Add. The cross connect will be established.

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

Page 86
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

6.9.3.3 SNCP Cross Connects Uni- and Bi-Directional

An SNCP protected cross connect can be either uni- or bidirectional, and, in either case, can be
either of the following:
LP1 ->TP <- LP2

LP2 -> TP <- LP1

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.
• Creating from scratch.

An SNCP cross connect can be removed by either:

• Converting a SNCP protected cross connect into a unprotected cross connect. This can be
done by removing either the worker or protection leg. This makes a hitless conversion
possible even if the near and the far end do not select the same path.
• Removing the SNCP protected cross connect.

Example

To create an SNCP unidirectional cross connect for LP1 -> TP <- LP2, select

MENU: XCONNECTS | ADD SNCP UNIDIRECTIONAL | LP1 -> TP <- LP2

to display a window such as shown in Figure 54.

Figure 54. Add SNCP Unidirectional Cross Connect

Select the desired ports, then click on Add. The cross connect will be established.

Note: This is the same for the other add uni- or bidirectional SNCP cross connects.

Page 87
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Note: MSP and SNCP are mutually exclusive.

Note: For SNCP protected unidirectional cross connects, only the selector is provisioned,
and not the bridge. A bridge can also be created manually.

6.9.3.4 Swapping Worker and Protection

Swapping of worker (from-leg) and protection (prot-leg) requires two user operations. First the
from-leg is removed, then the prot-leg is assigned to the previous worker leg.
In order to change the leg of an SNCP protected cross-connect:
1. Temporarily convert the cross-connect into an unprotected one by removing the worker or
protection leg.
2. Add a different protection leg to the unprotected cross-connect, resulting in the changed
SNCP protected cross-connect.

Note: The SNCP protected cross-connect can be either uni- or bidirectional.

Editing SNCP Cross Connects

To edit an SNCP cross connect, use MENU: XCONNECTS | LIST to list the cross connects,
then select a cross connect and press Details to display a window such as shown in Figure 55.
Table 17 describes the fields.

Figure 55. Editing a SNCP Cross-Connect

Page 88
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 17. SNCP Cross Connect Fields

FIELD NAME DESCRIPTION

Current
Accepted TT1 Status Identifies the accepted status and value. This data is shown for the Protection and
and Value From leg. Per leg a non intrusive monitor is supported
Type Identifies the type of cross connect (see Section 6.9.3.3, SNCP Cross Connects
Uni- and Bi-Directional, on Page 87)
Common Settings
Accepted TT1 Status Identifies the accepted status
TIM Detection Identifies if the Trail Identifier Mismatch is enabled (see Section 6.8.7, Provision-
ing Trail Trace Identifiers, on Page 79)
Monitoring Mode Can be monitored or not-monitored
Selected Degraded Identifies the threshold set (see Section 6.8.5, Degraded Threshold Provisioning
Threshold and Handling, on Page 77)
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 Section 6.8.5, Degraded Threshold Provisioning and Handling, on Page 77).
– No request: There was no request for this group.
– Active: Either the worker or protection is active
Edit
Remove Leg To remove the worker or protection leg
Switch Request The state of an SNCP group either be the result of a user or a System switch
request. Priorities are assigned to switch requests, the lower the number, the higher
the priority:
– Clear: Executed by user
– Force: Executed by user
– System: Forced, executed by System
– System: Degraded, executed by System
– Manual: Executed by System

Note: You cannot overrule the status of an SNCP group with a switch request having a
lower priority than the current priority. In this case you first have to execute a “Clear”
request and then the actual request.

6.10 Transmission Protection MSP

In terminal applications 1+1 Multiple Section Protection (MSP) in unidirectional mode,

revertive and non revertive is supported. The MSP protocol is compliant with ITU-T G.841/
Clause 7.1 and ETS 300417-3-1.

Page 89
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

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. The selection for
worker or protection is made at the receiver side. When MSP only is used, one VC4 (63*VC12)
container can be transmitted instead of two. Only the VC4 related to the worker MSP leg will be
available.

The service interruption due to an MSP switch will be shorter than 50 ms.

An MSP pair can be set up between line port 1 and line port 2 (with line port 1 as worker and
line port 2 as protection, and vice versa).

6.10.1 Precautions

When an MSP pair is provisioned:

• The protection leg may not carry traffic (no cross connects provisioned).
• The protection leg may not be assigned as timing reference.

When the above precautions are not followed, an error message is shown on the Web browser
when an attempt is made to create an MSP pair.

6.10.2 Definitions and Concepts

The following definitions and related concepts are important to understand when provisioning
MSP pairs:
• Unidirectional—In unidirectional mode, the switching of near end and far end are
independent.
• Switch Criteria—Failures detected at the MS layer lead to an MSP switch. When an
MS1cSSF or MS1cAISis detected at the MS section, a signal fail is declared for that leg.
When an MS degraded is detected, the leg is declared Degraded.
• Signal Fail—A signal fail indicates that the corresponding leg has an MS failure. SFP
failures are also included.
• Degraded—The corresponding leg has an MS degraded alarm, based on the degraded
threshold provisioning (see Section 6.8.5, Degraded Threshold Provisioning and
Handling, on Page 77).
• 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 switches to the protection side when a
failure has been detected at the worker side. It remains at the protection side when the
failure has been cleared.

Page 90
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

• Revertive—In case of a failure in revertive mode, the traffic switches to the protection
side and switches back when the failure has been cleared after expiry of the wait to restore
timer.
• Wait to Restore—The wait to restore timer, only applicable in revertive mode, defines the
time the switch will revert after a failure has been cleared. During expiry of the wait to
restore time, no failure should be detected, otherwise the state will return to failed. To
avoid intermittent behavior of the MSP switch, due to a toggling MS1 failure, between
failed and not failed, the WTR timer is used. In this way, an MS1 layer needs to be non-
failed for a certain period; this period is the WTR time.
• External Switch Requests—The user can invoke switch requests via the web browser to
override the automatic switching . In case of maintenance this might be useful.
• MSP and Alarming—The alarm location used for the VC4 and TU12 locations will
differ when MSP is enabled. As these termination points are in the traffic path, related to
the active leg, the alarm location will be LPa indicating it is related to the active leg. Check
the MSP details to find out which leg is active.

6.10.3 Creating an MSP Pair

To create an MSP pair, select:

MENU: PROTECTION | MSP | CREATE

to display the window shown in Figure 56.

Figure 56. Creating an MSP Pair

An 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, then click on Create. Once the MSP pair
has been created, no changes regarding operation mode or worker/protection side can be made.
To change these settings, the pair has to be deleted and recreated with the desired settings.

Note: If a port is carrying traffic or the MSP pair already exists, a warning is displayed
(Figure 57).

Page 91
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Figure 57. MSP Port Is Carrying Traffic

6.10.4 Deleting an MSP Pair

When an MSP is required to be deleted, use

MENU: PROTECTION | MSP | DETAILS

to display the window shown in Figure 58.

Figure 58. MSP Selector

The MSP pair will be pre-selected, as there is only one MSP pair available. Select Delete to have
the MSP pair deleted.

This may be service affecting; however, if near end and far end are both set to worker, no service
impact is expected.

6.10.5 MSP Details

To view details for an MSP pair, use

MENU: PROTECTION | MSP | DETAILS

to display the window shown in Figure 58 above.

The MSP pair will be pre-selected, as there is only one MSP pair available.

Page 92
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Select Edit to display an MSP Details window (Figure 59). Table 18 describes the fields.

Figure 59. MSP Details Window

Table 18. MSP Details Fields

FIELD NAME DESCRIPTION

Worker
Assigned Indicates which line port is defined as worker leg
Signal State 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
Signal State 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
Active Indicates which leg is currently active
State The state can be:
– No request: No change to the current switch state of the MSP pair.
– Failed: A failure has been detected at one or both MSP legs.
– Degraded: An MS degraded has been detected to one or both of the MSP legs.
– Wait to restore: A recent failure has been cleared, the wait to restore timer
is running.
– Forced: A forced switch request is set.
– Manual: A manual switch request is set.
– Lockout: The MSP protection is locked out; worker is selected.
Switch Request To override the MSP automatic switching, you can invoke an external switch
request (see Section 6.10.2, Definitions and Concepts, on Page 90)
(Unnamed)
SW Type The System only supports unidirectional. Bidirectional is not supported
Operation Indicates the mode of operation revertive or non revertive
WTR Wait to restore timer. More information is available (see “External switch requests”
on page ). In non revertive mode, this timer is grayed out

Page 93
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

6.10.6 External MSP Switch Requests

To override the MSP automatic switching, the user can invoke an external switch request. To
execute a switch request, select

MENU: PROTECTION | MSP DETAILS

to display the window shown in Figure 60.

Figure 60. MSP Switch Requests

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

When a switch request is initiated, a warning pops up to indicate switching may be service
affecting. The user has then the option to cancel the switch request.

For Switch Request, choose from the following choices:

• Clear—To clear an outstanding switch request, including WTR timer.
• Lockout—When setting the switch state to lockout, MSP protection switching is disabled.
The worker leg is selected for traffic.
• Forced Sw to Worker—Enforces switching traffic to the worker line. It overrides
automatic switching even in case of a signal fail or signal degrade. This can be service
affecting.
• Forced Sw to Protection—Enforces switching traffic to the protection line. It overrides
automatic switching in case of a signal degrade but not in case of a signal fail on
protection. This can be service affecting.
• Manual Sw to Worker—Switches conditionally traffic to the worker line. When a failure
is present at the worker line switching is rejected. In case a failure is raised during the
manual to worker state traffic will switch to the protection line. When e.g. a forced request
or lockout is outstanding a manual request will be rejected, the forced request first has to
be cleared.

Page 94
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

• Manual Sw to Protection—Switches conditionally traffic to the protection line. When a

failure is present at the protection line switching is rejected. In case a failure, Signal Fail
and Signal Degrade, is raised during the manual to protection state, traffic will switch to
the worker line. When a forced request is outstanding a manual request will be rejected,
the forced request first has to be cleared.

Wait to Restore Timer

The WTR (wait to restore) timer is only applicable in revertive mode. The default value is five
minutes. This timer can be provisioned between 0 and 60 minutes in steps of one minute.
Setting the timer to 0 minutes will disable the wait to restore timer.

Note: The provisioned WTR value is displayed.

6.11 Synchronization

The intention of Synchronization is to synchronize the whole SDH network to one master clock.
The provisioning of the individual network elements must be aligned to be synchronized from
one side and forward the reference towards the other side of the network. Before provisioning
the System, a network synchronization plan must be available, including a backup plan when
the master clock fails, preventing timing loops in any scenario.

The System has an internal clock corresponding 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 (see Section 6.11.2, Provisioning Timing
Sources, on Page 97).
• Provisioning of the System timing, like WTR timer, locked or free running mode, and use
of the SSM algorithm (see Section 6.11.2, Provisioning Timing Sources, on Page 97).
• External timing switch request, to overrule the automatic timing selection algorithm.

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

Note: In Section 7.10, Synchronization Network, on Page 134, an example is given for
provisioning synchronization of a network.

Page 95
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

6.11.1 Definitions

The following definitions are important in synchronization:

• Timing Source—is a provisionable reference from which the System can be
synchronized. The System can be synchronized from both the line ports or from one of the
E1. In case MSP is provisioned only one line port reference, the worker MSP section, is
available.
• Quality Level (QL)—indicates the quality level of a reference or System. This QL is
transmitted in the STM-1 overhead in the synchronization status message, the S1 or SSM
byte. For E1 signals no QL is supported.
• Reference Fail—is declared when the signal related to that reference has a failure which
impacts the timing reliability. This can be transmission related failures like
STM1cLOS,STMcLOF, MS1cAIS, E1cLOS or E1cAIS. Another cause might be an
excessive frequency offset of the reference. When the frequency of the reference has a
deviation of more than ± 15 ppm to the internal clock the reference will be declared failed.
Note that in this case no port level alarm is raised.
• SSM Byte—contains the quality indication of the reference. The System supports this
only for the STM-1 line port signals. The definitions according to G.781 are listed below.
The SSM byte is only applicable when QL is enabled. When QL is disabled DNU is sent
out and the incoming SSM bytes are ignored. Table 19 provides an overview.
Table 19. QL Overview

QL S1/byte* Accuracy Description

DNU 1111 Not applicable Do not use for synchronization, indicates the signal
should not be used for synchronization
Unknown Not applicable No QL information is available
PRC 0010 10-11 Primary reference clock
SSU-T 0100 1.5.10-9 Synchronization supply unit-transit, indicates the timing
is derived from a transit SSU
SSU-L 1000 3.10-8 Synchronization supply unit-local indicates the timing
signal is derived from a local SSU.
SEC 1011 4.6.10-6 SDH equipment clock indicates the timing signal is
derived by an SDH equipment clock (internal System
clock)

* The first nibble of the S1 byte is 0000.

• QL-in—indicates the received SSM byte from a timing reference.

• QL Timing Source—assigned QL of a timing source. When Auto is provisioned this
value is equal to the QL-in, when a value has been provisioned this value will be the QL-
out.
• Outgoing SSM—is transmitted in the S1 byte of the STM-1 signal, the line ports. This is
not supported for the E1 ports. The outgoing SSM is not visible at the user interface.

Page 96
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

– In a case where the System is in holdover or free running mode, the SSM out is
SEC.
– In a case where the System is locked to a certain port, the SSM out on this port is
DNU, to prevent timing loops in the network.
– On line ports, the SSM out represents the System QL (except for the active
reference, see previous case).
– For an MSP pair, both line ports have the same SSM out value.
– When the QL is disabled, the SSM out is DNU.

6.11.2 Provisioning Timing Sources

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

To view timing source, select

MENU: TIMING | TIMING SOURCES

to display the Timing Sources List (Figure 61). Table 20describes the fields.

Figure 61. Timing Source List Window

Table 20. Timing Sources List Fields

FIELD NAME DESCRIPTION

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. When the MSP is provisioned, only one line port
reference, the worker MSP section, is available
Assigned to Active Indicates the reference assigned to the timing source

Page 97
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Table 20. Timing Sources List Fields

FIELD NAME DESCRIPTION

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 QL Indicates the status of the signal provided to the timing source
– Normal: No signal fail, the signal is valid
– Failed: A failure has been detected for this reference
– Wait to restore: A recent failure on this reference has been cleared
and during expiring of the wait to restore timer the state is wait
to restore.
– Not connected: No reference has been assigned to this timing source.
QL Timing Source The quality level of this timing source

6.11.3 Provisioning Line Port References

To edit timing source details for a line port, select the line port in the Reference field in the
Timing Sources List (shown in Figure 61 on Page 97); then click on Edit to display the Timing
Source Details window (Figure 62).

Figure 62. Editing Timing Source Details Window (Line Port)

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

Page 98
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

1. Assign
Select the line port to be assigned to this timing source and select the assign button. Only
the line port references available are shown. When MSP is enabled only the worker port of
the MSP pair is available.

2. Edit
Choose from:
Reference: indicates the assigned reference to this timing source.

– Reference fail: indicates if the reference has a signal fail.

– Error Free: no reference fail.
– Fail: reference fail is present. For a line port reference this can be due to a
STM1cLOS, STM1cLOF, RS1cTIM, MS1cAIS or an excessive frequency offset
of the reference signal.

3. Monitored
Choose from:
– Monitored
– Not monitored: Now a timing source failure can be reported for this timing source
with a SYNCcTLF.
Table 21 describes other fields in the window.

Table 21. Editing Timing Source Detail Fields

FIELD NAME DESCRIPTION

Edit
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 Provisioned For line port references the default value is AUTO. When using AUTO, the QL
level is taken from the SSM value received from this reference. When this refer-
ence is unable to provide a SSM value, a provisioned value can be chosen accord-
ing to the quality of this reference. Be aware when using a provisioned value,
changes in the quality of this reference will not be recognized
Signal Status Indicates the status of the timing reference:
– Normal: The signal is valid
– Failed: A failure has been detected for this reference
– Wait to restore: A recent failure has been cleared for this reference.
During expiring of this timer the state is wait to restore
– Not connected: No reference has been assigned to this timing source.

Page 99
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Table 21. Editing Timing Source Detail Fields

FIELD NAME DESCRIPTION

Clear WTR When the state is wait to restore this state can be overruled by clearing the wait to
restore timer, select this box and click Apply
Priority The priority of this timing source, used in the selection for System timing
Lockout When this box is selected the timing source is locked out. The reference will not be
used as timing reference. The default value is locked out. When provisioning the
timing source the lockout needs to be deselected when the timing source is required
to be operational. Using lockout for a reference is useful in maintenance opera-
tions. Each reference individually can be locked out

6.11.4 Provisioning Tributary Port References

To edit timing source details for a tributary port, select the tributary port in the Reference field in
the Timing Sources List (shown in Figure 61 on Page 97); then click on Edit to display the
Timing Source Details window (Figure 62).

Figure 63. Editing Timing Source Details Window Tributary Port)

The procedure is the same as explained for provisioning a line port (see Section 6.11.3,
Provisioning Line Port References, on Page 98). Only differences with provisioning line port
are explained.
• Reference
Only references from Interface Cards which are in the ASSIGNED state are available.
Only one E1 port from all tributary ports can be selected.

• QL-in
As the System does not support SSM values for the E1 ports, there is no QL-in value.

Page 100
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

• Reference status
A reference fail for an E1 port may be due to:
– E1cLOS or E1cAIS.
– An excessive frequency offset of the reference.

• QL provisioned
As the System does not support SSM for E1 tributary ports thus a QL value needs to be
provisioned. A value corresponding to the quality of the reference needs to be chosen. Be
aware that changes in the frequency accuracy of this reference will not be observed. The
default value is SSUT.

6.11.5 Provisioning System Timing

When provisioning System timing, the timing mode can be chosen and the use of the SSM
algorithm. Next to that timing reference, switches can be made to overrule the automatic
selection when the System is under maintenance. Provisioning and switching are separate
actions in the System timing menu. To provision System timing, select

MENU: TIMING | SYSTEM TIMING

to display the window shown below (Figure 64). Table 22 describes the relevant fields.

Figure 64. System Timing Provisioning Window

Table 22. System Timing Details Fields

FIELD NAME DESCRIPTION

System
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 avail-
able are failed. Only applicable in locked mode.
Free Running: The System is in free running mode. System timing is running on
its internal clock, timing mode will be free running

Page 101
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Table 22. System Timing Details Fields

FIELD NAME DESCRIPTION

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

6.11.6 System Timing Reference Selection

The selection of the active reference can operate in two modes, priority based and SSM based
(see SSM Based Algorithm on Page 103).

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.

Page 102
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Priority based selection is operational when QL is disabled. The reference with the highest
priority will be selected. In case multiple references have the same priority the selection is
random. When a reference fails the next in priority will be chosen, when the first becomes non-
failed the System will revert to the reference with the highest priority.

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

SSM Based Algorithm

When QL is enabled, the selection is SSM based. The reference with the highest quality will be
chosen. For QL definitions, see Table 19 on page 96. The quality levels in descending order are
PRC, SSU-T, SSU-L, SEC.

The following rules are applicable for the SSM based selection:
• All references that are not failed and do not have SSM=DNU are considered for selection
• The reference with the highest QL will be selected.
• In case multiple references have the same QL, the one with the highest priority is selected.
• In case multiple references have the same QL and the same priority, the selection is
random.
• In case no suitable reference is available the System will switch to holdover and a
SYNCcBHO is reported.

6.11.7 Retiming E1 Ports

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

Using an E1 port in retiming mode might affect the traffic on this connection. When there is a
frequency difference between the incoming E1 payload signal and the System frequency, this
causes bit errors. The frequency difference is handled with a buffer. When there is a frequency
difference, this buffer over- or underflows. Each over- or underflow leads to a buffer re-center.
This causes a controlled slip. A frequency difference of 1 ppm leads to a slip once per halve
minute.

The provisioning of retiming is part of the E1 port provisioning.

To retime E1 ports, select

MENU: TRANSMISSION | PORTS | TRIB PORTS

to display the E1 ports then select the port of interest and click on Edit to display the E1 Trib
Ports Retiming Provisioning window shown in Figure 65.

Page 103
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Figure 65. E1 Trib Port Retiming Provisioning Window

Table 23. System Timing Details Fields

FIELD NAME DESCRIPTION

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

Page 104
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 23. System Timing Details Fields

FIELD NAME DESCRIPTION

System QL The current QL of the System
Port Timing State Identifies the current state
– Normal: The port is working in the provisioned mode
– Fall back: The port is provisioned in re-timed mode but is in fall back mode,
due to the System QL being below the acceptance QL
Report Timing Alarm Default value is disabled. When setting this to enabled an alarm is raised when the
port is in fall back mode, due to the System QL being below the acceptance QL.
The SYNCcLRR alarm will be reported for this port

6.12 SNMP

Note: SNMP settings can only be changed with admin rights.

The System supports a Simple Network Management Protocol (SNMP) agent. This enables the
System to sent SNMP alarm traps or notifications to an SNMP manager, also the current raised
alarms can be requested. The System supports both SNMPv1 and SNMPv2. The user can
provision up to five SNMP managers. These are identified by their IP address. The community
string has to be entered, public, and a selection for traps v1 and or v2 notifications can be made.

Autonomous events are reported to the SNMP manager. In a trap notification, the alarm
description, location, severity, and time stamp are shown, and if it is a raise or clearing.
Requesting the current alarm list is possible when using the enterprise MIB with prefix:
iso.org.dcd.internet.private.enterprise
AimValleyBV(1.3.6.1.4.1.23862)

Before being able to show this list, you have to import the System MIB to the SNMP browser.
The MIB files are available at the System software CD. Please contact ADC for MIB files.
Next, you compile the MIB in the SNMP browser. Now the browser is able to retrieve the
current alarm list. These actions will be specific for the SNMP browser being used.

The alarm reporting towards the SNMP manager is identical as the alarms reported at the web
browser.

To edit SNMP settings, select

MENU: SYSTEM | SNMP SETTINGS

to display the SNMP Details window shown in Figure 66. Table 24 describes the fields.

Page 105
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Figure 66. SNMP Details Window

Table 24. SNMP Details Window Fields

FIELD NAME DESCRIPTION

Manager IP Address The IP address of the SNMP manager
Read Community Provisionable authentication string
V1 trap / V2 Trap Select V1 Trap if SNMPv1 traps are required. Select V2 Trap if SNMPv2 notifica-
tions are required. If both are enabled a trap and notification is reported
Alarm community Allows the user to group alarm traps

6.12.1 Current Alarm List With SNMP

Figure 67 shows an example.

Figure 67. Current Alarms List on an SNMP Browser

Note: The UTC time is used (see Section 1.6.6, Real Time Clock, on Page 9).

Page 106
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

6.13 OSPF Provisioning

6.13.1 OSPF Settings

To provision OSPF settings, select

MENU: SYSTEM | IP SETTINGS | OSPF | GENERAL

to display the window shown below (Figure 68). Table 25 describes the fields.

Figure 68. OSPF Settings Window

Table 25. OSPF Settings Fields

FIELD NAME DESCRIPTION

OSPF General
Enabled Used to enable or disable the OSPF. The default is disabled. If enabled, you also
must provision the System with a router ID
Router ID Used to enter the System OSPF router ID. The router ID is a /32 IP address that
uniquely identifies the router within an AS. The default is 0.0.0.0.
RFC1583 OSPF standard, read only value. It shows that OSPF version 2 is supported
ABR Not applicable in this version (see Section 4.3.1, Area Border Router, on Page 26).
Read only value
ASBR Indicates if this System is an ASBR (see Section 4.3.2, Autonomous System Bor-
der Router (ASBR), on Page 26).
Version Indicates the OSPF version. Read only value
OSPF ASBR If this system is provisioned as an ASBR, then the route is advertised
Manual Routes Not supported
Apply To confirm the changes
List OSPF interfaces To go to the interface OSPF settings (see Section 4.3, Routers for OSPF, on Page
26)
List interfaces To go to the management interfaces of this System

Page 107
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

6.13.2 OSPF Interfaces

TO view OSPF interfaces, select

SYSTEM | IP SETTINGS | OSPF | INTERFACES

to display the window shown below (Figure 69). Table 26 describes the fields.

Figure 69. OSPF Interfaces Window

Table 26. OSPF Interfaces Windows Fields

FIELD NAME DESCRIPTION

Name Displays the name of the OSPF interface
Enabled Displays whether the OSPF interface is activated
Area Displays the Area of the OSPF
Refresh Used to update the window
List interfaces Used to go to the management interfaces of this System
Edit Select the interface to edit and click Edit
– LAN (see Section 5.1.2, LAN Port Provisioning via Web Browser, on Page 46)
– LP1 or LP2 displays the window such as shown below (Figure 70).
Table 27 describes the fields.

Figure 70. Interface LP1 Window

Page 108
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 27. Interface LP1 Window Fields

FIELD NAME DESCRIPTION

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
Mask Fixed to 32

6.13.2.1 OSPF LAN/LP Interfaces

To reach the OSPF LAN/LP interfaces select the following from the ASX GUI menu:

SYSTEM | IP SETTINGS | OSPF | INTERFACES

A window appears. In this window, select LAN or LP1/LP2. Depending on the selection, the
screen displays the OSPF Interface LAN, OSPF Interface LP1, or OSPF Interface LP2 window.
Figure 71 shows an example.

Figure 71. OSPF Interfaces LAN or LP Window

Table 28. OSPF Interfaces LAN or LP Fields

FIELD NAME DESCRIPTION

Enabled Displays whether the OSPF interface is activated or not. From this screen the value can be
set to enabled or disabled
Area Displays the Area of the OSPF. Read only value
Metric Link costs. Read only value
Router Priority Used to determine the designated router. Read only value
Auth Type, Auth Key Used to check if another Systems belongs to the family. Read only value
Hello Interval (sec), OSPFs send hello packets to their neighbors. They are used to check whether the neighbors
Router Dead Interval (sec) can be reached or not. If a System (router) cannot be reached for a Router Dead Interval
time the router entries for this router are removed
Apply To confirm the changes

Page 109
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Table 28. OSPF Interfaces LAN or LP Fields

FIELD NAME DESCRIPTION

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

Page 110
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

6.13.3 OSPF Systems

To provision the OSPF setting, select

MENU: SYSTEM | IP SETTINGS | OSPF | SYSTEMS

to display the window shown in Figure 72.

Figure 72. OSPF Systems Window

The field RouterID shows the OSPF enabled systems that can be reached. Note that RouterID is
displayed.

Page 111
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Page 112
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

7 ALARMS

The System supports alarm reporting for all SDH levels (RS, MS, VC4, and VC12), equipment-
related alarms, port-related alarms and synchronization-related alarms. These alarms will be
reported to the Web browser, the SNMP manager when provisioned, and can be visible at the
System LEDs.

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

7.1 Most Recent Alarm Bar

In the most recent alarms bar in the Web browser, the most recent alarm is shown with the raised
time and the number of outstanding active alarms (Figure 73). Table 29 describes the fields.

Figure 73. Most Recent Alarm List

Table 29. Most Recent Alarm List Fields

FIELD NAME DESCRIPTION

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

7.2 Alarm Refresh Rate

The alarm refresh rate is the rate at which alarms are reported. This refresh rate is specific for
every Browser connection. It is set to the default value of five seconds when reloading the
browser page or when re-logging in to the System.

To display the GUI settings for the alarm refresh rate, select

MENU: ALARMS | GUI SETTINGS

to display the Alarm GUI Settings window, shown in Figure 74.

Page 113
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Figure 74. Current Alarm List

Selecting None/Stop causes the most recent alarm bar to not be updated. The refresh rate can be
set to 1, 5, 10, 60, 300 seconds or none/stop.

7.3 Current Alarms

The Current Alarms window (Figure 75) shows all current outstanding alarms. To display the
window, select

MENU: ALARMS | CURRENT

Table describes the fields.

Figure 75. Current Alarm List Window

Table 30. Current Alarm List Fields

FIELD NAME DESCRIPTION

Location Identifies the location of the alarm
Type Identifies the type of the alarm
Severity Indicates the severity of the alarm, as defined in the alarm profile

Page 114
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 30. Current Alarm List Fields

FIELD NAME DESCRIPTION

Raised Time stamp based on the System time of the System, presented in the local time zone
(see Section 1.6.6, Real Time Clock, on Page 9)
Details When selecting an alarm in the list and next clicking details, the long alarm description
is shown in a pop up window (Figure 76). The long alarm description is also shown
when pointing the alarm with the mouse indicator at the alarm, not available when using
Internet Explorer 6.0

Figure 76. Alarm Details VC12vUNEQ

To have the current alarm list updated to the current situation, you have to refresh it (see
Section 7.6, Resolving Alarms, on Page 118). Notifications towards the provisioned SNMP
manager are sent autonomously.

7.4 Alarm History

The System has a log for 500 cleared alarms. Alarms that are cleared are put in the alarm history
with the alarm type, severity, time raised, and time cleared time stamp.

An alarm status change is automatically updated in the history.

To view the alarms log, select

MENU: ALARMS | HISTORY

to display the Alarms History window (Figure 77).

Figure 77. Alarm History List Window

Page 115
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Table 31. Current Alarm List Fields

FIELD NAME DESCRIPTION

Refresh The history list is not autonomously updated, a refresh is needed. The System has a log
for 500 cleared alarms. It this number is exceeded the first entry is removed from the
list.
NOTE: Retrieving a large alarm history list might take ten seconds.
Clear To clear the history list and start with a clean list again
Details Select the alarm and click Details. Additional information will be displayed in a pop-
up. This additional information also comes available if you point the alarm with the
mouse indicator. This option is not available for Internet Explorer 6.0
Backup Alarms can be downloaded in a tab separated file for off line processing (using, for
example, Excel)
To current alarms Shows the currently present alarms.
NOTE: Times shown are based on the local time zone (see Section 1.6.6, Real
Time Clock, on Page 9).

7.5 Alarm Profiles, Severities, Reporting, and LEDs

7.5.1 Alarm Profile List

The alarm severity and reported mode can be provisioned per alarm type individually. To
display the alarm types, select

MENU: ALARMS | PROFILE/SEVERITIES

to display the alarm profile list (Figure 78). Table 32 describes the fields.

Figure 78. Alarm Profile List Window

Page 116
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Table 32. Current Alarm List Fields

FIELD NAME DESCRIPTION

Cause Is indicated by the alarm type (see Section 7.8, Alarm Descriptions, on Page 121)
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 is effective the next time the alarm is
raised. Changing the severity of an active alarm clears this alarm, puts it in the history
list, and re-raises the alarm with the new severity and a new time stamp.
The severity of an active alarm is directly reflected on the LED indicators (see
Section 7.5.3, LED Indicators, on Page 118)
Reported Mode See next topic

7.5.2 Changing the Alarm Reported Mode or Severity

To change the alarm reported mode or severity, first list the alarm in the Alarm Profile list (just
shown in Figure 78 on Page 116), then select the alarm of interest in the list and click on the
Edit button to display the Severity Settings window (Figure 79). Table describes the fields.

Figure 79. Severity Settings Window

Table 33. Severity Settings Window Fields

FIELD NAME DESCRIPTION

Severity Can be set to Major, Minor or Info
Reported Mode Has two values: True (alarm will be reported); False (alarm will not be reported).
Immediate result of a change in reported mode depends on whether the alarm is pres-
ently active or not active, as follows:
– When the reported mode of an inactive alarm is changed, this becomes effective
the next time the alarm cause is present.
– When the reported mode of an active alarm is changed from reported to not
reported, this does not clear the alarm. The change in reported mode becomes
effective the next time the alarm cause is present.
– When the reported mode of an active alarm is changed from not reported to
reported, this becomes effective at once and the alarm is reported at once

Page 117
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

7.5.3 LED Indicators

Though LED indicators are described in this section, no provisioning is applicable for them.

7.5.3.1 System LED indicators

The System has three LED indicators:

• Green LED—if lit, indicates the System is on (power LED) and the initializing status.
• Yellow LED—if lit, indicates a minor fault is reported.
• Red LED—if lit, indicates a major fault is reported.

In addition, for the Yellow LED and Red LED, the following applies:

• These LEDs indicate only those alarms that are the consequence of defects detected in the
System. This means that SSF, RDI, and AIS alarms do not contribute to the LED state.

7.6 Resolving Alarms

7.6.1 Introduction

This section describes the alarms that can be reported by the System. For each alarm type, there
is a specific description and a description of some probable root causes. Alarm types are split up
into logical levels.

This section is intended for maintenance employees and network operators. This section
provides information to support them in their tasks of resolving alarms or analyzing end
customer complaints.

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

7.6.2 Location

The location of an alarm identifies the detection point. This can be any of the following:
• 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—related to Line port 1 or 2.
• VC4 termination point—identified by related line port, LP1, LP2 or the active line port
(LPa) in case of MSP.
• VC12 termination point—identified by tributary slot number, followed by the port
number.
• VC12 monitoring point—identified by related line port, followed by klm indication.

Page 118
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

• AU alarm—identified by line port number, LP1, LP2 or the active line port (LPa) in case
of MSP.
• TU alarm—identified by line port number, LP1, LP2 or the active line port (LPa) in case
of MSP, followed by the klm indication.

7.7 Alarm List Overview

Table 34 shows all defined alarm types and their default severity and default LED state.

Table 34. Alarm List Overview

DEFAULT DEFAULT LED

ALARM TYPE SEVERITY STATE DEFAULT REPORTING
AU4cAIS ( Minor None Yes
AU4cLOP Major Red Yes
E12cAIS Minor None Yes
E12cLOS Major Red Yes
IFCcEQF Major Red Yes
IFCcREPL Major Red Yes
IFCcUNP Major Red Yes
IFCcWU Major Red Yes
MS1cAIS Minor None Yes
MS1cDEG Minor Yellow Yes
MS1cRDI Minor None Yes
MS1cSSF Major None Yes
MS1PcSSF Major None Yes
RS1cSSF Major None Yes
RS1cTIM Major Red Yes
SFPcEQF Major Red Yes
SFPcUNP Major Red Yes
SFPcWUI Major Red Yes
STM1cLOF Major Red Yes
STM1cLOS Major Red Yes
SYNCcBHO Major Red Yes
SYNCcLRR Major Red Yes
SYNCcTLF Major Red Yes
SYScEQF ( Major Red Yes
SYScPFA Major Red No
SYScPFB Major Red No
SYScROUTE Minor Yellow Yes

Page 119
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Table 34. Alarm List Overview, continued

DEFAULT DEFAULT LED

ALARM TYPE SEVERITY STATE DEFAULT REPORTING
SYScTIME Major Red Yes
TU12cAIS Minor None Yes
TU12cLOP Major Red Yes
VC12cDEG Minor Yellow Yes
VC12cPLM Major Red Yes
VC12cRDI Major None Yes
VC12cSSF Major None Yes
VC12cTIM Major Red Yes
VC12cUNEQ Major Red Yes
VC4cDEG Minor Yellow Yes
VC4cLOM Major Red Yes
VC4cPLM Major Red Yes
VC4cRDI Minor None Yes
VC4cSSF Major None Yes
VC4cTIM Major Red Yes
VC4cUNEQ Major Red Yes
AU4cAIS Minor None Yes
AU4cLOP Major Red Yes

Table 35. Alarm List Overview Columns

COLUMN DESCRIPTION
Alarm Type This is a short name (mnemonic) of the fault cause according to the ITU standards: G.783,
G.784 and G.806
Severity This identifies the provisioned severity for the alarm. The default severity is listed by the
descriptions (see Section 7.5, Alarm Profiles, Severities, Reporting, and LEDs, on Page
116)
Time Stamp The time stamp identifies the raise time of the alarm. This time is based on the System time
of the System (see Section 1.6.6, Real Time Clock, on Page 9)
Reported Mode The default reported mode for all alarms is reported, except for the SYScPFA and
SYScPFB alarm. When an alarm is required to not be reported, this can be provisioned (see
Section 7.5.2, Changing the Alarm Reported Mode or Severity, on Page 117)

Page 120
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

7.7.1 Monitoring Mode

The monitoring mode of a port or termination point controls the alarming. If the monitoring
mode is monitored, alarms are reported on that point. If the state is not monitored, alarms are
not reported. See Section 6.8, Ports and Termination Points, on Page 69.

7.7.2 Pluggable Item State

The pluggable items state affects the reporting of alarms. In the assigned state all alarms are
reported. In the AUTO state, only the EQF and WUI alarms are reported (see Section 6.4,
Pluggable Items, on Page 57).

7.7.3 Replacing Systems

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

7.8 Alarm Descriptions

This section contains details for each type of ASX alarm.

7.8.1 System Alarms

7.8.1.1 SYScTIME

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

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

System time has not been provisioned. Or System time has been lost due to a power outage
longer than 10 minutes.

7.8.1.2 SYScPFA

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

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

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

Page 121
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

7.8.1.3 SYScPFB

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

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

No power connected to power feed B. Or voltage is below 40.5 Volt. Or the -48 and 0
connections are swapped, the System will operate but a SYScPFB is reported. The default
reporting state is not reported, When monitoring is required, the state must be set to reported.

Note: For Power over Ethernet no power monitor is available. This is a non-redundant
input and mixing PoE and telecom power feed is forbidden.

7.8.1.4 SYScEQF

An equipment failure has been detected on the System

The System has become unreliable

Replace the System, and return the failed System

7.8.1.5 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 Section 4.1, Open Shortest Path First (OSPF),
on Page 25).

7.8.2 Pluggable Items Alarms

7.8.2.1 IFCcUNP

A unit not present for the identified slot has been detected, although a unit is expected.

Transmission provisioned towards this slot will be lost

The Interface Card of an assigned slot has been removed. Reinsert the correct Interface Card or
when no Interface Card is desired for this slot position change the slot state to AUTO (see
Section 6.4.2, Interface Card (IFC), on Page 58 )

7.8.2.2 IFCcWUI

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

Page 122
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

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

The inserted Interface Card has a not supported item code. Replace the Interface Card by a
supported type.

7.8.2.3 IFCcREPL

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

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

Accept the Interface Card (see Section 6.4.2, Interface Card (IFC), on Page 58). Take care
cabling is according to this Interface Card.

7.8.2.4 IFCcEQF

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

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

Replace IFC.

7.8.2.5 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 Section 6.4.4, Small Form
Pluggable, on Page 60).

7.8.2.6 SFPcWUI

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

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

Page 123
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Reinsert an SFP with an identical module qualifier as the last accepted one. or change the state
to AUTO and the System will set the current inserted SFP to operational (see Section 6.4.4,
Small Form Pluggable, on Page 60).

7.8.2.7 SFPcEQF

An equipment failure has been detected for the inserted SFP.

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

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

7.8.3 Synchronization Items

7.8.3.1 SYNCcBHO

System timing has fall back to hold over mode. The System is running on its hold over clock.
None of the provisioned references is available or has sufficient quality.

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

Check if any timing source is provisioned. Check if the provisioned timing sources do have a
timing link failure SYNcTLF and if they are in MONITORED mode.

7.8.3.2 SYNCcTLF

A timing link failure has been detected for the identified timing source. No reference assigned
for this timing source or the signal has one of the next failures:
• For line ports: RS1cTIM, STM1cLOS, STM1cLOF, MS1cAIS.
• For tributary ports: E1cLOS or E1cAIS

Or the timing reference has a frequency deviation of more than ±15 ppm related to the internal
clock of the System.

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

Check the signal provided to the timing source has a defect and resolve that cause, or if none
timing source has been assigned to the identified timing source.

7.8.3.3 SYNCcLRR

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

Page 124
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

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

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

7.8.4 Port Alarms

7.8.4.1 E12cLOS

The identified E1 port has a loss of signal detected.

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

Check cabling towards the E1 port

7.8.4.2 E12cAIS

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

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

Check alarms on the System connected to the E1 port

7.8.4.3 STM1cLOS

The identified line port has a loss of signal detected.

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

Check cabling on the line port.

7.8.4.4 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 downstream direction
AIS is inserted. In the upstream direction (return path) MS RDI is inserted.

Check signal provided to this line port. E.g. a STM4 signal might be provided or input might be
overloaded (to much optical power).

Page 125
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

7.8.5 Termination Point Alarms

7.8.5.1 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 downstream direction
AIS is inserted. In the upstream direction (return path) MS RDI is inserted

Check the accepted and expected TTI for this port. The System might be connected to the
wrong far end system or port.

7.8.5.2 RS1cSSF

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

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

Check the root cause of this RS1cSSF. Might be due to a STM1cLOS, or STM1cLOF.

7.8.5.3 MS1cSSF

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

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

Check the root cause of this failure. Might be due to a STM1cLOS, STM1cLOF or RS1cTIM.

7.8.5.4 MS1PcSSF

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

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

Both line ports do have an MS related failure, or a forced switch is in place to a failed line port.

7.8.5.5 MS1cAIS

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

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

Check alarms on the far end system.

Page 126
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

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

7.8.5.7 MS1cDEG

The number of B2 background block errors detected on the identified line port does exceed the
provisioned degraded threshold (see Section 6.8.5, Degraded Threshold Provisioning and
Handling, on Page 77).

Transmission is affected as bit errors will disturb the signal.

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

7.8.5.8 AU4cAIS

The AU4 container contains AIS.

Transmission in the downstream direction is lost.

The root cause is in the layer above or due to a failure in the far end system. Check MS and RS
alarms on the related line port or alarms on the far end system.

7.8.5.9 AU4cLOP

No valid AU4 pointer is present in the AU4 container.

Transmission in the downstream direction is lost.

An invalid AU4 signal is received.

7.8.5.10 VC4cSSF

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

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

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

Page 127
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

7.8.5.11 VC4cUNEQ

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

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

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

7.8.5.12 VC4cPLM

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

Transmission is lost in the downstream direction, AIS is inserted.

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

7.8.5.13 VC4cTIM

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

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

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

7.8.5.14 VC4cDEG

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

Transmission is affected as bit errors are present.

Check upstream cabling and or equipment, an MS1cDEG might also be present.

7.8.5.15 VC4cLOM

The VC4 received does not contain the TU12 multi frame indicator.

Page 128
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

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.

7.8.5.16 VC4cRDI

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

Transmission might be affected at the far end side.

The far end systems has detected a downstream failure at VC4 level. Check alarming at the far
end system.

7.8.5.17 TU12cAIS

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

Transmission is lost in this TU12, no consequent actions.

Check upstream defects.

7.8.5.18 TU12cLOP

No TU12 pointer is detected in the TU12 identified. The TU12cLOP is identified by the TU12
number (klm) at the line port side.

Transmission is lost in this TU12 container.

Check far end provisioning, a TUG without TU12 pointer might be used e.g. TU3.

7.8.5.19 VC12cSSF

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

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

Check alarming at the VC4 layer.

7.8.5.20 VC12cUNEQ

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

Transmission is lost in the downstream direction. For a VC12 trail termination point AIS is
inserted. In the upstream direction VC12 RDI is inserted. When provisioning cross connects on

Page 129
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

both side of a connection, temporarily a VC12cUNEQ might be raised due to the absence of the
cross connect at the far end.

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

7.8.5.21 VC12cPLM

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

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) or asynchronous
(02) but a different kind of traffic. Check in the details of the related VC12 TTP the accepted
TSL value. The far end system does have wrong type of traffic. The VC12cPLM alarm is not
under control of the monitoring flag.

7.8.5.22 VC12cTIM

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

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 cross connect
in the transmission path between the near and far end VC12 TTP. If no match is required TIM
detection can be disabled thus no alarms is raised and no consequent actions are executed.

7.8.5.23 VC12cDEG

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

Transmission is affected as bit errors are present.

Check upstream equipment and or cabling, a VC4cDEG or MS1cDEG might be present.

7.8.5.24 VC12cRDI

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

Transmission might be affected at the far end side.

Page 130
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

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

7.9 SDH Overview

7.9.1 SDH Multiplex Structure

Figure 80. SDH Multiplex Structure

Page 131
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

7.9.2 SDH Termination Points

Figure 81. SDH Termination Points

Page 132
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

7.9.3 SDH Events

Table 36 lists SDH Events

Table 36. 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 Mis- MS-REI MS Remote Error Indica-
match tion
RS-BIP RS Bit Interleaved Parity MS-RDI MS Remote Defect Indica-
tion
PHY Physical (sfp) los and clock K2 APS signaling byte
monitor
A1-2 Framing bytes B2 Error monitor
J0 Trace identifier M1 Backwards section status
B1 Error monitor H1-2 AU pointer

Higher order Path (HP) Lower order Path (LP)

AU-AIS AU Alarm Indication Sig- TU-AIS TU Alarm indication signal
nal
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 Mis- LP-UNEQ LP Unequipped
match
HP-BIP HP Bit Interleaved Parity LP-TIM LP Trace identifier mis-
error match
HP-REI HP Remote Error Indica- LP-BIP LP Bit Error Monitor
tion
HP-RDI HP Remote Defect Indica- LP-REI LP Remote Error Indication
tion
HP-PLM HP Payload Label Mis- LP-RDI LP Remote Defect Indica-
match tion
C2 Signal label LP-PLM LP PayLoad Mismatch
J1 Trace identifier V5 Error monitor, signal label
and backward status
B3 Error monitor J2 Trace identifier
G1 Backward path status
H4 TU pointer

Page 133
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

7.10 Synchronization Network

Table 82 shows an example of a synchronization plan for a ring network with four Systems.

Figure 82. Example of Synchronization Network

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

Page 134
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

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

Provisioning System 2
• Timing source 1: Assigned to Line port 2, Q: AUTO, priority 1
• Timing source 2: Assigned to Line port 1, QL: AUTO, priority 2.

Provisioning System 3
• Timing source 1: Assigned to Line port 2, QL: AUTO, priority 1
• Timing source 2: Assigned to Line port 1, QL: AUTO, priority 2.

Provisioning System 4
• Timing source 1: Assigned to Line port 2, QL: AUTO, priority 1
• Timing source 2: Assigned to Line port 1, Q: AUTO, priority 2.
Timing source 3: Assigned to Trib port TS8.2, QL provisioned PRC, priority 1

During normal operation the synchronization is as shown. The PRC clock on timing source 3 on
System4 has got the best quality:
• System4 will select Timing source 3 (PRC is the best quality).
• System3 will select Timing source 1 (LP2) as this one reference has the highest priority.
• System2 will select Timing source 1 (LP2) as this reference has the highest priority.
• System1 will select Timing source 3 (LP1) as this reference has the highest priority.

Page 135
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Network Failure 1

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

Figure 83. Network Failure 1

Page 136
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Network Failure 2

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

Figure 84. Network Failure 2

Page 137
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

Page 138
© 2008, ADC Telecommunications, Inc.
 ADCP-80-578 • Issue 2 • 8/2008

Index
A C
activating a database 68 C12cUNEQ alarm 129
adding cross connects 84 changing alarm reported mode or s everity 117
Address Resolution Protocol (ARP) 27 connecting panel 19
alarm contacts 6 connectors 5
alarm descriptions 121 copying an active database 68
alarm history 115 Craft interface 6
Alarm History List window 115 Cross Connect List window 83
Alarm List Overview 119 cross connect routing 22
Alarm Profile List window 116 cross-connect jumpers 20
alarm profiles, severities, reporting, and LEDs current alarms 114
116 Current Alarms List window 106, 114
alarm refresh rate 113 D
alarms 113 Database Listing window 66
Alarms menu 52 default database 65
alarms, resolving 118 Degraded threshold provisioning and handling
ASBR example 34 77
assigning IP addresses for system management Degraded Thresholds Overview window 78
28 deleting a cross connect 84
ASX GUI 50 deleting a database 68
features 48 deleting an MSP pair 92
introduction 7, 48 DHCP state transitions, diagram 44
log file 51 dimensions 13
master index of tasks 55 E
menu structure 51 E1 ports, retiming 103
settings 48 E1 Trib Port Retiming Provisioning window 104
user groups, logins, and rights 49 E1 tributary ports 70
windows and procedures 55 E12cAIS alarm 125
ASX panel E12cLOS alarm 125
connecting 19 editing a cross connect 84
dimensions 13 editing SNCP cross connects 88
installing cross-connect jumpers 20 external MSP switch requerst 94
mounting on rack 18 F
patching and testing 24 functional background, ASX system
powering up 20 ASX system
ASX panel components 4 functional background 25
ASX System Overview window 50 G
AU4cAIS alarm 127 ground stud 6
AU4cLOP alarm 127 H
Autonomous System Border Router (ASBR) 26 Hi There Utility 45
B I
backing up a database 67 IFC replacement 60
bidirectional cross connects 85 IFCcEQF alarm 123

Page 139
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

IFCcREPL alarm 123 O

IFCcUNP alarm 122 Open Shortest Path First (OSPF) 25
IFCcWUI alarm 122 optical interface 6
Image System Database (ISD) 62 OSPF interfaces 108
inactive ISD, selecting 62 OSPF Interfaces LAN or LP window 109
installation overview 17 OSPF Interfaces window 108
Interface Card Details window 58 OSPF LAN/LP interfaces 109
Interface Cards (IFCs) 58 OSPF provisioning 107
Interface LP1 window 108 OSPF routers 26
IP address management 43 OSPF Settings window 107
IP management without DHCP error 43 OSPF systems 111
L OSPF Systems window 111
LAN connector 6 P
LAN port provisioning via web browser 46 patching and testing 24
LAN Port Settings window 46 pluggable items 57
LAN provisioning in LP2Box 47 pluggable items alarms 122
LED indicators 118 Pluggable Items Selector window 58
Line Port Details window 70 port alarms 125
line port references, provisioning 98 port loopback functionality 41
Line Ports Selector window 69 port loopback functions, diagram 42
line protection and OSPF 28 ports and termination points 69
link costs and signal rate 27 power feed 6
listing, editing, and deleting cross connects 83 powering up panel 20
local management, host directly connected to product description
System LAN 30 ASX panel components 4
login screen 50 connectors 5
LP2Box Utility 47 dimensions 13
LSA cross connect 22 general description 1
M specifications 13
memory banks, system software 62 system function 2
Most Recent Alarm Bar 113 provisioning for this network 134
mounting panel on rack 18 provisioning IP address with DHCP client 45
MS1cAIS alarm 126 provisioning line port references 98
MS1cDEG alarm 127 provisioning system timing 101
MS1cRDI alarm 127 provisioning tributary port references 100
MS1cSSF alarm 126 provisioning via local console control 44
MS1PcSSF alarm 126 proxy ARP example 37
MSP Details window 93 Proxy Resolution Protocol (PARP) 27
MSP menu 53 R
multiple host and mix applications 34 renaming a database 67
N resolving alarms 118
network failure, diagram 137 restoring a database 67
network provisioning 134 retiming E1 ports 103
non-intrusive monitoring (NIM) of line ports 40 routing examples 30
RS/MS Details window 73

Page 140
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

RS/MS Selection window 72 inventory management 10

RS1cSSF alarm 126 line management 10
RS1cTIM alarm 126 log file 9
S loopback 11
SDH events, diagram 132 overhead functions 11
SDH events, table 133 path protection 11
SDH multiplex structure, diagram 131 powering 9
SDH overview 131 real time clock 9
SDH termination points, diagram 132 single and dual fiber SFPs 11
selecting a new database 66 SNMP server 11
setup of system software 43 synchronization 10
Severity Settings window 117 System database 9
SFP Details window 60 System software 8
SFP replacement and acceptance 61 user administration 9
SFPcEQF alarm 124 web server 11
SFPcUNP alarm 123 System menu 51
SFPcWUI alarm 123 system overview window 50
Simple Network Management Protocol (SNMP) system recovery 62
105 system software memory banks 62
single fiber SFPs 61 System software setup 43
SNCP cross connects 87 System Time window 56
SNMP Details window 106 System Timing Provisioning window 101
specifications 13 system timing reference selection 102
STM1cLOF alarm 125 system timing, provisioning 101
STM1cLOS alarm 125 T
Subnetwork Connection Protection (SNCP) 39 terminal application and host connected to LAN
summary of user tasks 12 31
swapping worker and protection 88 termination point alarms 126
SYNCcLRR alarm 124 termination points 72
SYNCcTLF alarm 124 testing 24
synchrnoization items alarms 124 Timing menu 53
synchronization 95 Timing Source List window 97
synchronization network, diagram 134 tools and materials required for installation 17
SYScEQF alarm 122 trail trace identifier provision and handling 78
SYScPFA alarm 121 Trail Trace Provisioning window 79
SYScPFB alarm 122 Transmission menu 53
SYScROUTE alarm 122 transmission protection MSP 89
SYScTIME alarm 121 transmission terms and definitions 56
System access problems when using IP address- Tributary Port Details window 71
es 29 tributary port references, provisioning 100
system alarms 121 Tributary Ports Selector window 71
System features 8 TU12cAIS alarm 129
alarm reporting 10 TU12cLOP alarm 129
cross connects 11 U
E1 retiming 10 unidirectional cross connects 86

Page 141
© 2008, ADC Telecommunications, Inc.
ADCP-80-578 • Issue 2 • 8/2008

unpacking and inspection 17

user tasks, summary 12
V
VC12 termination point 75
VC12 Termination Point Details window 76
VC12 Termination Point Selector window 76
VC12cDEG alarm 130
VC12cPLM alarm 130
VC12cRDI alarm 130
VC12cSSF alarm 129
VC12cTIM alarm 130
VC4 Termination Point Details window 74
VC4 termination points 73
VC4cDEG alarm 128
VC4cLOM alarm 128
VC4cPLM alarm 128
VC4cSSF alarm 127
VC4cTIM alarm 128
VC4cUNEQ alarm 128
W
wire-wrap cross connect 21
X
XConnect Details window 84
Y
YNCcBHO alarm 124
Z
Maintenance menu 52
XConnects menu 52

Page 142
© 2008, ADC Telecommunications, Inc.
 PHONE:
U.S.A. or CANADA
Sales: 1-800-366-3691
Extension 73000
Technical Assistance: 1-800-366-3891
Connectivity Extension: 73475
Wireless Extension: 73476
EUROPE
Sales Administration: +32-2-712-65 00
Technical Assistance: +32-2-712-65 42
EUROPEAN TOLL FREE NUMBERS
Germany: 0180 2232923
UK: 0800 960236
Spain: 900 983291
France: 0800 914032
Italy: 0800 782374
ASIA/PACIFIC
Sales Administration: +65-6294-9948
Technical Assistance: +65-6393-0739
ELSEWHERE
Sales Administration: +1-952-938-8080
Technical Assistance: +1-952-917-3475
WRITE:
ADC Telecommunications (S’PORE) PTE, LTD;
100 Beach Road, #18-01, Shaw Towers.
Singapore 189702.

ADC Telecommunications, INC

PO Box 1101,
Minneapolis, MN 55440-1101, USA

ADC European Customer Service, INC

Belgicastraat 2,
1930 Zaventem, Belguim

PRODUCT INFORMATION AND TECHNICAL ASSISTANCE:

[email protected]
[email protected]
[email protected]
[email protected]
13944-O

Contents herein are current as of the date of publication. ADC reserves the right to change the contents
without prior notice. In no event shall ADC be liable for any damages resulting from loss of data,
loss of use, or loss of profits and ADC further disclaims any and all liability for indirect, incidental,
special, consequential or other similar damages. This disclaimer of liability applies to all products,
publications and services during and after the warranty period.