2416 sdh field service module user’s guide

2416 SDH Field Service ModuleUser’s Guide

Document #50-17838-01, Rev AMay 2001

Global Headquarters20400 Observation DriveGermantown, Maryland 20876-4023 USAToll Free 1-800-638-2049 • Tel +1-301-353-1550 • Fax +1-301-353-0234www.acterna.com

NoticeEvery effort was made to ensure that the information in this document was accurate at the time of printing. However, infor-mation is subject to change without notice, and Acterna reserves the right to provide an addendum to this document with information not available at the time that this document was created.

Copyright© Copyright 2001, Acterna, LLC., doing business as Acterna. All rights reserved. Acterna, The Keepers of Communica-tions, and its logo are trademarks of Acterna, LLC. No part of this guide may be reproduced or transmitted electronically or otherwise without written permission of the publisher.

TrademarksActerna and TestPad 2000 are trademarks or registered trademarks of Acterna in the United States and/or other countries.

Specifications, terms, and conditions are subject to change without notice. All trademarks and registered trademarks are the property of their respective companies.

Ordering InformationThis guide is a product of Acterna's Technical Information Development Department, issued as part of the 2416 SDH Field Services Module User’s Guide. The ordering number for a published guide is 80-17838-01, Rev A.

Federal Communications Commission (FCC) NoticeThis product was tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This product generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this product in a residential area is likely to cause harmful interference, in which case you will be required to correct the interference at your own expense.

The authority to operate this product is conditioned by the requirements that no modifications be made to the equipment unless the changes or modifications are expressly approved by Acterna.

Industry Canada RequirementsThis Class A digital apparatus complies with Canadian ICES-003.

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.

EMC Directive ComplianceThis product was tested and conforms to the EMC Directive, 89/336/EEC as amended by 92/31/EEC and 93/68/EEC for electromagnetic compatibility. A copy of the Declaration of Conformity is provided in this manual.

CAUTION: This is a Class A product. In a domestic environment, this product may cause radio interference, in which case, the user may be required to take adequate measures.

Low Voltage Directive ComplianceThis product was tested and conforms to the Low Voltage Directive, 73/23/EEC as amended by 93/68/EEC. Conformity with this directive is based upon compliance with the harmonized safety standard, EN60950. A copy of the Declaration of Con-formity is provided in this manual.

CAUTION: The 2416 SDH Field Service module is a Class 1 laser product.

2416 SDH Field Service ModuleUser’s Guide v

Safety Information

Important Safety Instructions

The following table defines safety terms. Failure to observe these pre-cautions while using the 2416 SDH Field Service Module, violates the intended use of this product.

When using the product, basic safety precautions should always be followed to reduce the risk of fire, shock, and injury to persons, includ-ing the following:

1 Read and follow all warning notices and instructions marked on the product and included in the manual.

2 Use only the AC Adapter/Charger supplied with the product.

3 Do not use AC Adapter/Charger outdoors or in wet or damp locations.

4 Connect the AC Adapter/Charger to the correct mains voltage, as indicated on the ratings label.

5 Do not allow anything to rest on the power cord, and do not locate the product where persons can walk on the power cord.

6 Avoid using this product during an electrical storm. There may be a remote risk of electric shock from lightning.

7 Do not use this product in the vicinity of a gas leak or in any explosive environment.

Safety definitions

Term Description

DANGER Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.

WARNING Indicates a potentially hazardous situation which, if notavoided, could result in death or serious injury.

CAUTION Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. It may also be used to alert against unsafe practices.

2416 SDH Field Service Modulevi User’s Guide

Safety Information

8 Do not attempt to service this product yourself, as opening or removing covers may expose you to dangerous, high voltage points and other hazards. Refer all servicing to qualified service personnel.

9 CAUTION: Danger of explosion if battery is incorrectly replaced. Dispose of used batteries according to the manufacturer's instructions.

10 CAUTION: Never look into the optic transmitters when the unit is ON.

11 CAUTION: Use of controls or adjustments or performance of procedures other than those specified herein may result in hazardous radiation exposure.

12 Do not connect this product directly to the telecommunication network/outside plant leads.

Symbols

The following safety symbol is used on the 2416 SDH Field Service Module. All safety precautions must be observed when operating, servicing, or repairing the 2416 SDH Field Service Module. Failure to comply with the following safety precautions or with hazard cautions and warnings used throughout this manual violates the intended use of this instrument.

Save these instructions

GENERAL HAZARD

This icon represents a general warning or caution.

CAUTION: HIGH VOLTAGE

This icon represents a caution, risk of electrical shock.

2416 SDH Field Service ModuleUser’s Guide vii

Contents

About This Guide .................................................................... xix

Purpose and scope ......................................................................... xix

Assumptions.................................................................................... xix

Getting technical assistance ............................................................ xx

Using this guide............................................................................... xxi

Conventions..............................................................................xxii

Safety terminology ...................................................................xxiii

Chapter 1—SDH Module Overview ....................................1

About the SDH Field Service module.................................................2

Features and capabilities ...................................................................2

Physical description ...........................................................................3

Chapter 2—Instrument Setup...............................................5

About instrument setup ......................................................................6

Assembling the module......................................................................6

Powering the module .........................................................................6

Setting the language ..........................................................................7

Installing options ................................................................................9

Connecting the printer......................................................................10

2416 SDH Field Service Moduleviii User’s Guide

Contents

Maintaining the battery.....................................................................11

Recharging the battery ..............................................................11

Replacing the battery.................................................................12

Chapter 3—Guided Tour.......................................................15

About the guided tour.......................................................................16

Exploring the unit .............................................................................16

Top panel...................................................................................16

Bottom panel..............................................................................17

Front panel.................................................................................17

Navigating the user interface ...........................................................18

Application buttons ....................................................................18

Test setup button .......................................................................19

Configuration summary bar .......................................................19

Results display...........................................................................19

Action buttons ............................................................................19

Message display ........................................................................19

System icons .............................................................................20

Permanent keys.........................................................................21

Viewing system information .............................................................22

Configuring system settings.......................................................22

Configuring a test .............................................................................24

Performing a timed test..............................................................26

Selecting physical triggers .........................................................26

Configuring histograms..............................................................27

Saving test configurations ................................................................28

Loading test configurations........................................................29

Deleting, renaming, and copying files........................................30

Formatting the internal drive ......................................................31

Connecting the unit for testing .........................................................33

Laser safety ...............................................................................34

Operating modes .......................................................................34Terminate mode ..................................................................34Thru mode...........................................................................35

2416 SDH Field Service ModuleUser’s Guide ix

Contents

MUX mode ..........................................................................36

Viewing test results ..........................................................................37

Printing test results...........................................................................38

Activating timed print .................................................................39

Printing to file .............................................................................40

Selecting the print type ..............................................................40

Creating headings......................................................................41

Printing standard categories ......................................................41

Printing histograms ....................................................................42

Printing a selected range from the event log .............................44

Using the remote control feature......................................................46

Chapter 4—PDH Testing.......................................................47

About PDH testing............................................................................48

Viewing 2M timeslots .......................................................................48

Conducting performance analysis....................................................49

Performing a round trip delay test ....................................................52

Identifying anomalies and defects....................................................53

Generating errors.......................................................................53

Simulating alarms ......................................................................55

Performing BER testing....................................................................56

Monitoring network traffic .................................................................57

Verifying APS switchover time .........................................................59

Scenario: Troubleshooting a 45M service........................................62

Evaluating the situation..............................................................62

Conclusion .................................................................................66

Chapter 5—SDH Testing.......................................................67

About SDH testing............................................................................68

Conducting performance analysis....................................................68

Identifying anomalies and defects....................................................70

Generating errors.......................................................................70

2416 SDH Field Service Modulex User’s Guide

Contents

Simulating alarms ......................................................................72

Performing BER testing....................................................................74

Analyzing pointer movements ..........................................................75

Identifying trace messages ..............................................................78

Scenario: Turning up an STM-16 service.........................................80


Conclusion .................................................................................83

Chapter 6—MUX Testing ......................................................85

About MUX testing ...........................................................................86

Testing a multiplexer ........................................................................86

Scenario: Turning up a multiplexer ..................................................88


Conclusion .................................................................................90

Chapter 7—Interpreting Test Results .............................91

About interpreting test results ..........................................................92

Interpreting summary results............................................................92

Interpreting signal results .................................................................94

Interpreting BERT results.................................................................95

Interpreting PDH frame results.........................................................97

Interpreting performance results ....................................................100

Interpreting SOH results.................................................................104

Interpreting HP results ...................................................................106

Interpreting LP results ....................................................................108

Interpreting LEDs ...........................................................................111

Viewing the event log .....................................................................113

Chapter 8—Troubleshooting ............................................115

About troubleshooting ....................................................................116

Solving problems............................................................................116

Installing and setup..................................................................116

2416 SDH Field Service ModuleUser’s Guide xi

Contents

Question............................................................................116Answer ..............................................................................116Question............................................................................117Answer ..............................................................................117

Operating the module ..............................................................117Question............................................................................117Answer ..............................................................................117

Performing tests.......................................................................118Question............................................................................118Answer ..............................................................................118Question............................................................................118Answer ..............................................................................118

Chapter 9—Customer Services .......................................119

About our services .........................................................................120

Customer service locations ............................................................120

Instrument services ........................................................................120

Consulting Services .......................................................................121

Test systems field engineering and installation..............................122

Technical training ...........................................................................123

Warranty information......................................................................124

Equipment return instructions ........................................................126

Appendix A—Specifications .............................................129

About the specifications .................................................................130

Physical specifications ...................................................................130

Environmental specifications..........................................................130

Electrical specifications ..................................................................131

Network interface connectors.........................................................131

PDH specifications .........................................................................132

Output signals..........................................................................132

Input signals.............................................................................133

Measurement types .................................................................134

2416 SDH Field Service Modulexii User’s Guide

Contents

SDH specifications .........................................................................136

Output signals..........................................................................136

Input signals.............................................................................138

Measurement types .................................................................138

Results display specifications ........................................................141

Appendix B—Remote Control Commands .................143

About using the remote control ......................................................144

Command syntax ...........................................................................144

Configuration commands.........................................................145

Result commands....................................................................145

Configuration commands ...............................................................145

System configuration commands.............................................146

BERT configuration commands ...............................................147

2M configuration commands....................................................148

8M configuration commands....................................................149

34M configuration commands..................................................150

45M configuration commands..................................................150

140M configuration commands................................................151

SDH configuration commands .................................................152

STM1_E configuration commands...........................................156

Result commands ..........................................................................156

Signal result commands ..........................................................156

LED result commands .............................................................157

PDH frame result commands...................................................159

BERT result commands...........................................................161

Performance result commands................................................161

SOH result commands.............................................................164

HP result commands ...............................................................165

LP result commands ................................................................166

Misc. result commands ............................................................167

Appendix C—Field Descriptions.....................................169

SDH Module Field Descriptions .....................................................170

2416 SDH Field Service ModuleUser’s Guide xiii

Contents

Glossary.....................................................................................177

Index ............................................................................................183

2416 SDH Field Service ModuleUser’s Guide xiv

Tables

Table 1 — System tray icons ........................................................20

Table 2 — Permanent softkeys.....................................................21

Table 3 — SDH module signal results ..........................................94

Table 4 — BERT results ...............................................................96

Table 5 — PDH frame results .......................................................97

Table 6 — Performance results ..................................................101

Table 7 — SOH results ...............................................................104

Table 8 — HP results ..................................................................106

Table 9 — LP results...................................................................108

Table 10 — LED panel..................................................................112

Table 11 — Physical specifications...............................................130

Table 12 — Environmental specifications.....................................130

Table 13 — Electrical specifications .............................................131

Table 14 — PDH output signals....................................................132

2416 SDH Field Service ModuleUser’s Guide xv

Tables

Table 15 — PDH input signals ......................................................133

Table 16 — PDH measurement types ..........................................134

Table 17 — SDH output signals....................................................136

Table 18 — SDH input signals ......................................................138

Table 19 — SDH measurement types ..........................................138

Table 20 — Results display specifications....................................141

Table 21 — System configuration commands ..............................146

Table 22 — BERT configuration commands.................................147

Table 23 — 2M configuration commands .....................................148

Table 24 — 8M configuration commands .....................................149

Table 25 — 34M configuration commands ...................................150

Table 26 — 45M configuration commands ...................................150

Table 27 — 140M configuration commands .................................151

Table 28 — SDH configuration commands...................................152

Table 29 — STM_1E configuration commands ............................156

Table 30 — Signal result commands ............................................156

Table 31 — LED result commands ...............................................157

Table 32 — PDH frame result commands ....................................159

Table 33 — BERT Result Commands ..........................................161

Table 34 — Performance results commands................................161

Table 35 — SOH result commands ..............................................164

2416 SDH Field Service Modulexvi User’s Guide

Tables

Table 36 — HP result commands .................................................165

Table 37 — LP result commands..................................................166

Table 38 — Miscellaneous result commands ...............................167

2416 SDH Field Service ModuleUser’s Guide xvii

Figures

Figure 1 — Top panel ..................................................................16

Figure 2 — Bottom panel .............................................................17

Figure 3 — SDH module front panel ............................................17

Figure 4 — Main window..............................................................18

Figure 5 — Terminate Mode connection......................................35

Figure 6 — Thru Mode connection...............................................36

Figure 7 — MUX Mode connection ..............................................37

Figure 8 — Printer Management window.....................................39

Figure 9 — Histogram printout .....................................................44

Figure 10 — Selected range printout ............................................46

Figure 11 — APS Switchover.........................................................61

Figure 12 — All Summary Results OK...........................................92

Figure 13 — Summary Results Error display.................................93

Figure 14 — Signal results for SDH and 140M ..............................94

Figures

2416 SDH Field Service Modulexviii User’s Guide

Figure 15 — BERT results .............................................................95

Figure 16 — PDH frame results for 140M and 2M.........................97

Figure 17 — Performance results ................................................100

Figure 18 — SOH results .............................................................104

Figure 19 — HP results................................................................106

Figure 20 — LP results ................................................................108

Figure 21 — LED results for SDH and 140M ...............................111

Figure 22 — LED panel................................................................112

Figure 23 — Mapping structure....................................................137

2416 SDH Field Service ModuleUser’s Guide xix

Preface

About This Guide

Purpose and scope

The purpose of this guide is to help you successfully use the SDH Field Service module features and capabilities. This guide includes task-based instructions that describe how to assemble, use, and troubleshoot the module. Additionally, this guide provides a complete description of Acterna’s warranty, services, and repair information, including terms and conditions of the licensing agreement.

Assumptions

This guide is intended for novice, intermediate, and experienced users who want to use the module effectively and efficiently. We are assuming that you have basic computer and mouse/track ball experience and are familiar with basic telecommunication concepts and terminology.

2416 SDH Field Service Modulexx User’s Guide

About This Guide

Getting technical assistance

If you need assistance or have questions related to the use of this product, call or email Acterna’s Technical Assistance Center (TAC) for customer support.

During off-hours you can request assistance by doing one of the following: leave a voice mail message at the Technical Assistance number in your region; email North American Technical Assistance Center, [email protected], or European Technical Assistance Center, [email protected]; or submit your question using our online Technical Assistance Request form at www.acterna.com.

Technical assistance centers

Region Phone Number Hours of Operation

Americas 1-800-638-2049 M-F, 8:00 a.m. to 8:00 p.m., EST

Europe, Africa, and Mid-East

00800 882 85822 (European Freephone)

+800 882 85822(Acterna UK)

+49 (0) 7121 86 1262 (Acterna Germany)

+33 (0) 1 39 30 24 24 (Acterna France)

M-F, 8:30 a.m. - 5:00 p.m. GMT

Asia and the Pacific +852 2892 0990 (Hong Kong)

+86 10 6833 7477 (China)

+61 3 9690 6700(Australia)

M-F, 9:00 a.m. - 5:30 p.m.

M-F, 9:00 a.m. - 5:30 p.m.

M-F, 8:30 a.m. - 5:30 p.m.

2416 SDH Field Service ModuleUser’s Guide xxi

Using this guide

Using this guide

The following table is a roadmap to using this guide efficiently; however, all chapters in this guide can be used for reference purposes:

The remainder of this guide provides supplementary information. The Appendices provide reference information. The Glossary defines terms, abbreviations, and acronyms. To locate specific information, refer to the Index.

Locating information

To Refer to

Become familiar with module Chapter 1 “SDH Module Overview”

Set up the module for use Chapter 2 “Instrument Setup”

Explore the unit, navigate the user interface, and perform basic functional tasks

Chapter 3 “Guided Tour”

Learn to use and apply features in a field environment

Chapter 4 “PDH Testing” Chapter 5 “SDH Testing” Chapter 6 “MUX Testing”

Interpret test results Chapter 7 “Interpreting Test Results”

Troubleshoot the unit Chapter 8 “Troubleshooting”

Learn about the warranty Chapter 9 “Customer Services”

2416 SDH Field Service Modulexxii User’s Guide

About This Guide

Conventions This guide uses naming conventions and symbols, as described in the following tables:

Typographical conventions

Description Example

Commands appear in this typeface. On the Status bar, click Start.

Switches that you press on a unit appear in this TYPEFACE.

Press the AUX switch.

Code and output messages appear in this typeface.

All results okay

Text you must enter exactly as shown appears in this typeface.

Type: a:\set.exe in the dialog box

A vertical bar | means “or”: only one option can appear in a single command.

platform [a|b|e]

Square brackets [ ] indicate an optional argument.

login [platform name]

Slanted brackets < > group required arguments.

<password>

Hazard and note icons

Icon Description

This icon represents a general hazard.

This icon represents a risk of electrical shock.

2416 SDH Field Service ModuleUser’s Guide xxiii

Using this guide

Safety terminology The following table defines safety terms used throughout this manual. Failure to observe these precautions while using the module, violates the intended use of this product.

This icon represents a Note indicating related infor-mation or tip.

Hazard and note icons (continued)

Icon Description

Safety definitions

Term Description

DANGER Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.

WARNING Indicates a potentially hazardous situation which, if notavoided, could result in death or serious injury.

CAUTION Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. It may also be used to alert against unsafe practices.

2416 SDH Field Service Modulexxiv User’s Guide

About This Guide

2416 SDH Field Service ModuleUser’s Guide 1

Chapter 1

1 SDH Module Overview

This chapter provides a general description of the module. Topics discussed in this chapter include the following:

“About the SDH Field Service module” on page 2

“Features and capabilities” on page 2

“Physical description” on page 3

2416 SDH Field Service Module2 User’s Guide

Chapter 1 — SDH Module Overview

About the SDH Field Service module

The SDH Field Service module is part of the 2000 Test Platform. It offers high-speed testing from E1 to STM-16c in a battery-powered mobile unit. The module enables you to turnup, troubleshoot, and maintain networks. It combines graphical user interface technology and a touch-sensitive screen to simplify test setup. The innovative icon-driven interface is easy to learn, and the large display provides ample space for displaying test results.

Features and capabilities

The module provides the test capabilities you need to accurately install and commission services. Features include the following:

Qualification of SDH rings

Timing and synchronization verification

Identification of anomalies and defects

Bit error rate testing (BERT) on STM-16, STM-4, STM-1, E4, DS3, E3, E2, and E1 digital links

Analysis at interface rate or any supported tributary rate

Out-of-service testing of a multiplexer

In-service monitoring of network traffic

Verification of APS switch over time at PDH drop rates

2M and Nx64 analysis

Round-trip delay measurements

Time/date stamp of user-selected conditions (Event Log)

Works in combination with the 2M and data, xDSL, copper loop qualification, and SONET field service modules


Physical description

Physical description

The SDH Field Service module is a hand-held test set that is designed around a powerful and flexible architecture, which includes the 2416 application module and the Acterna TestPad 2000. The modular design enables the Acterna TestPad 2000 to easily convert from one test technology to another by swapping the application modules. The module also comes with a hand strap and a kickstand.


Chapter 1 — SDH Module Overview


Chapter 2

2 Instrument Setup

This chapter provides step-by-step instructions to assemble and set up the module for use. Topics discussed in this chapter include the following:

“About instrument setup” on page 6

“Assembling the module” on page 6

“Powering the module” on page 6

“Setting the language” on page 7

“Installing options” on page 9

“Connecting the printer” on page 10

“Maintaining the battery” on page 11


Chapter 2 — Instrument Setup

About instrument setup

When you receive the module, you can configure the module to run installed options, to operate in another language, to print test results, and to run on battery power. Before using battery power, make sure that you are familiar with battery maintenance procedures and maintenance.

Assembling the module

The modular design includes a 1/4-turn screw (counterclockwise to release; clockwise to secure) on the application module for simple release and swapping out of modules.

To assemble the module

1 Attach the Acterna Test Pad 2000 to the 2416 application module.

2 Turn the screw clockwise to secure the module.

The module is ready to use.

Powering the module

The power is supplied by the battery or the AC power adapter. The power adapter plug is located on the bottom panel and provides 19 VDC connection.

To power the module, push the power switch to the ON position. The Power LED, located on the front panel, illuminates green when the module is powered.

NOTE:

The 2416 application module is compatible only with the A25000, TestPad 2000, Rev 3 and greater. For more information, refer to Chapter 8 “Troubleshooting” page 115.


Setting the language

Setting the language

The module supports languages for English, French, Italian, German, and Spanish.

To change to the local language

1 Press the System button and select Tools > Languages.



The Languages window appears.

The Languages on Card box displays the languages that have not been added to the module. To add a language, select the language and press the right arrow to move it to the Languages on Unit box.

2 To select the language for the module, press the Current Language field and select the language.

3 Press OK.

4 Power cycle the module to accept the language change.

The module is ready to use in the selected language.


Installing options

Installing options

To install options from the PCMCIA card

1 Verify that the label on the card is marked with the options identified for installation.

2 Turn the module power OFF.

3 Insert the PCMCIA card in Slot 1 (closest to the front panel).

4 Turn the module power ON.

5 Press the System button and select Tools > Optioning.

6 In the Features on Card box, select the option to install.

7 Press the right arrow to move the option into the Features Installed box.

8 Repeat steps 6 and 7 for each option you want to install.

NOTE:

If you are installing a software upgrade and an option upgrade, you must perform the software upgrade installation first.



9 Press OK when finished.

10 When the prompt appears, turn the module power OFF.

11 Remove the PCMCIA card and turn the module power ON.

The module is ready to use with the installed options.

Connecting the printer

The printer connector, located on the top panel, is an 8-pin connector used to connect the module to a serial printer, such as the PR-40B. The 8-pin connector presents a DTE interface, requiring the use of a null modem or reversing cable if you connect to a PC. You can use a standard communications program on your PC to capture the printout, and if you wish, save it.

To connect the printer to the module

1 Turn the module OFF.

2 Connect the cable from the interface connector on the printer to the interface connector on the module.

3 Turn the module ON.

4 Press the System button and select Tools > Printer Mgmt >

Settings.

N NOTE:

Use the printer cable provided with the module. Operability of the printer port cannot be guaranteed if you use a cable longer than three meters.


Maintaining the battery

The Settings tab appears.

5 Verify that the parameters in the Settings tab match the parameters for the printer.

6 Turn the printer ON.

The printer is now ready to print.


Recharging the battery

The Battery Low LED illuminates when the battery is at 25 percent or below full charge and indicates that the battery needs to be recharged. You can continue to use the module and recharge the battery at the same time.

NOTE:

Some PC communication programs may require the Terminator parameter to be set to CR/LF.



To charge the battery

1 Connect the AC adapter from the 19VDC connector to an AC power supply.

2 Let the module charge for up to 1.5 hours.

The Charge LED illuminates when the battery is charging. The charge duration is the same regardless of the module being on or off.

Replacing the battery

You can “hot swap” the battery, without losing test results, if you have access to an AC power source.

To hot swap the battery

1 Connect the AC power adapter to the module.

2 Unlock the battery access door by turning the screw clockwise.

3 Open the battery access panel and pull the strap to remove the battery.

4 Align the new battery with the terminals facing up and pointing toward the battery compartment.

5 Verify that you can read the terminal markings (-) V D C (+) at the top end of the battery.

6 Slide the new battery into the battery compartment until the terminals click into place.

The bottom of the battery should be approximately 0.25 inches inside the compartment.

7 Lock the battery door by turning the screw counter-clockwise.

Continue testing

NOTE:

It is recommended that you turn off the module to change the battery, but if you do not want to disturb current testing, leave the module turned on with the AC power adapter plugged in.



CAUTION:

Danger of explosion if battery is incorrectly replaced.

Replace only with the same or equivalent type recommended by the manufacturer. Dispose of used batteries according to the manufac-turer's instructions.

ATTENTION:

Il y a danger d’explosion s’il y a remplacement incorrect de la batterie.

Remplacer uniquement avec une batterie du même type ou d’un type équivalent recommandé par le constructeur. Mettre au rebut les bat-teries usagées conformément aux instructions du fabricant.

ATTENZIONE:

Pericolo di esplosione se la batteria non e sostituita correttamente.

Sostituirla soltanto con lo stesso tipo o con un tipo equivalente racco-mandato dal fabbricante. Eliminare le batterie usate secondo le istruzioni del fabbricante.

AVISO:

Peligro de explosión si la batería es sustituida incorrectamente.

Recambiela solamente por el mismo tipo o por un tipo equivalente recomendado por el fabricante. Deposite las baterías usadas según las instrucciones del fabricante.

ACHTUNG:

Explosionsgefahr bei falschem Einbau der Ersatzbatterie.

Bitte nur Ersatzbatterien des gleichen Typs verwenden oder equiva-lente. Typen nach Herstellerempfehlung. Bitte entsorgen Sie gebrauchte Batterien nach den Herstellerangaben.


Chapter 3

3 Guided Tour

This chapter introduces you to the module and provides step-by-step instructions for performing basic tasks. Topics discussed in this chapter include the following:

“About the guided tour” on page 16

“Exploring the unit” on page 16

“Navigating the user interface” on page 18

“Viewing system information” on page 22

“Configuring a test” on page 24

“Saving test configurations” on page 28

“Connecting the unit for testing” on page 33

“Viewing test results” on page 37

“Printing test results” on page 38

“Using the remote control feature” on page 46


Chapter 3 — Guided Tour

About the guided tour

This tour introduces you to the components of the module and provides instructions for performing basic functional tasks. After you are familiar with the module and the basic tasks, you are ready to begin testing.

Exploring the unit

Top panel The top panel (see Figure 1) provides the printer connector, dual PCMCIA card door, and the test connectors.

The Dual PCMCIA card door enables the insertion of two Type I PCMCIA cards or one Type III PCMCIA card for software upgrades and file storage. Slot 1 is closest to the front panel. Slot 2 is closest to the back of the module.

Figure 1 — Top panel

Test Connectors

PCMCIA card door

Printer Connector


Exploring the unit

Bottom panel The bottom panel (see Figure 2) provides the Power switch, AC adapter plug, handset connection, and the battery access panel.

Figure 2 — Bottom panel

Front panel The front panel (Figure 3) provides the touch-sensitive LCD screen, speaker and microphone It also provides the Power, Charge, and Low Battery LEDs.

Figure 3 — SDH module front panel

Battery access panel

Power switchAC adapter plug

Handset connector

Status LEDs

Touch sensitive LCD screen

Power LEDs



Navigating the user interface

The user interface provides the platform to configure tests and view results (see Figure 4). It is a touch screen that is divided into separate areas for test configuration and test results

Figure 4 — Main window

Application buttons The application buttons are located at the top of the window. They provide quick access to each test. When you press a button, the operating mode list appears.

Application buttons Test setup button

Results display

Configuration summary bar

Action buttons

System iconsMessage display

Permanent keys

NOTE:

We recommend using the stylus supplied with the module to activate functions on the touch-sensitive screen.



Test setup button The Test Setup button is located on the upper right corner of the main window. When you press this button, a Quick Configuration list appears. This list displays the current configuration for the selected test. Select any of these fields to go directly to that setup tab or select General if the field you want to modify is not listed.

For descriptions of tabs and data fields, refer to Appendix C “Field Descriptions” page 169.

Configuration summary bar

The configuration summary bar displays the current test being performed and the configuration settings.

Results display The Results Display windows are used to display the category results. The results can be shown in either text or graph format. See “Viewing test results” on page 37.

Action buttons The action buttons are located above the message display bar. The action buttons perform additional application specific functions. Each mode of operation presents different buttons that perform different actions. They may or may not be active and are application dependent.

Message display The message display bar displays the status and current events, such as APS test status. This bar is always displayed even while configuring the system.

NOTE:

There are tabs that are available for every interface, such as Struc-ture, BERT, and Error Insert. Some tabs that appear may be depen-dent on values entered on another tab. When configuring a test, make sure to complete all of the tabs that are appropriate for the test being completed.



System icons The System icons provide access to system settings.

Table 1 describes the function of each system tray icon.

Table 1 — System tray icons

Icons Description

Laser Control — Turns the laser on and off.

– When the icon is red and (|) is displayed, the laser is ON.

– When the icon is gray and (O) is displayed (as shown), the laser is OFF.

History Reset — Clears all history LEDs.

Speaker Volume — Activates the volume control window to set the speaker volume or to mute the volume.

Battery Status — Displays current battery strength by bar graph and percentage value.

System — Accesses basic functions, such as storing configurations, printing, installing options and languages, and automating tests. Also restarts a test, clears the event log, and marks a range end of the event log items.

This icon changes to red to indicate errors (is useful when the summary result window is not open).



Permanent keys Table 2 describes the function of each permanent keys.

Table 2 — Permanent softkeys

Icon Description

Restart — Performs the test restart function, including resetting the current test results and clearing any errors and/or alarms.

File — Activates the System Settings window, which allows you to view the software revision level and installed options, and to set preferences such as time and date.

Brightness — Adjusts the brightness on the color screen. There are two gradients of brightness:

– Low brightness (maximizes battery life)– High brightness for enhanced viewing

Battery Status — Not functional on the module. Battery status is indicated on the system tray icon on the bottom right corner of the main window.

Printer Setup — Activates the Printer Management tabs, which enables you to print result categories and histograms, and set printer interface parameters.

Help — Accesses Help.



Viewing system information

System information, including the date, time, time elapsed, and the number of power failures is displayed in the Results Display window.

To view system information

1 Press the Category Selection button and select Misc. > System.

The system information appears.

Configuring system settings

To configure system settings

1 Press the System button and select Tools > System Settings.


Viewing system information

The System Settings window appears.

2 Complete the information in the following tabs:

– On the Preferences tab, set the date and time. Also, enable sound and the screen saver.

– On the Set Date/Time tab, set the current date and time.

– On the Revisions tab, display the current version of the software. The first line is the current revision.

– On the Reset tab, reset all system settings to factory defaults.

3 Click OK to complete system settings configuration.

NOTE:

The screen saver is only available when using AC power.



Configuring a test

Before running a test, you need to define the circuit being tested and set up the test that you want to perform.

To configure a test

1 On the Application Button bar, press the test button for the circuit you want to test or press MUX if you are testing a multiplexer.

2 Select the operating mode. For MUX tests, select the receive and transmit rates.

3 To configure the test, press the Setup button.

A Quick Configuration list appears.

4 Select a specific field to go directly to that setup tab or select General if the field you want to define is not listed.


Configuring a test

5 To define the transmit payload, select the Structure tab

The Structure tab appears.

6 Complete the data fields to define the transmit payload.

7 Complete the other tabs and data fields that are specific to your test Refer to Appendix C “Field Descriptions” 169 for descriptions of tabs and data fields.

8 When you are finished configuring the test, press OK to accept the new values.

NOTE:

There are setup tabs that are available for every test, such as Struc-ture, BERT, and Error Insert. Other setup tabs are dependent on the circuit being tested and/or configurations selected on other tabs. When configuring a test, make sure to complete all tabs and data fields that are appropriate for your test.



Performing a timed test

A timed test allows you to continually run a test for a specified amount of time. At the end of a timed test, all results are frozen except for LED status.

To perform a timed test

1 After you have configured the test, press the Timed Test tab.

2 Check the Enable Timed Test box. Enter the length of the test (1 min. to 49d, 23h, and 59 min.).

3 Press OK to accept the test setup. This starts the timer. Press the Restart key to restart the timer.

When you start the test, it will run for the time specified. The configuration summary bar indicates that the test being performed is a timed test.

Selecting physical triggers

The module provides an event trigger feature for physical layer results. The Physical Trigger tab in the Setup Test window contains all events for the PDH and SDH interfaces and is organized into six categories: Signal, Framing, Performance, Alarm, BERT, and PDH APS (PDH analysis rates only).

When configuring test setup, use the Physical Trigger tab to select the event categories you want to capture in the Event Log. The event type, date, and time stamp are logged in the Event Log.

To set physical triggers

1 On the main window, press Setup > General.

The Setup Test window appears.

2 Press the Physical Triggers tab.

3 Select the event categories you want to capture in the Event Log.

4 Press OK to save the selection.

After the test begins, the data collects in the Event Log (see “Viewing the event log” on page 113).


Configuring a test

Configuring histograms

The histogram configuration allows you to choose which results the system will collect and the size of each sample of data to be collected. If you change the configuration, the buffer is cleared and the new histogram data is reset. All results are cleared as well.

The histogram buffer size for an individual result is determined by the total number of samples for all histogram results. For example, if the histogram buffer size is 6,000 samples and you select 3 histogram results, the buffer collects up to 2,000 samples at a given time and stores these in the result bucket. If the number of samples collected exceeds the bucket size, the oldest sample is erased.

To configure the histogram collection settings

1 Press Setup > Histograms.

2 Press the Histogram Settings tab.

3 Check the box to enable histogram collections.



4 Set the sample interval time.

5 Select a category tab and select the results you want to collect for the histogram. The category tabs that appear are based on the current test setup.

6 When finished, press OK.

To print histograms, refer to “Printing histograms” on page 42.

Saving test configurations

The module allows you to save configuration settings to be loaded for future tests; thus enabling you to quickly set up tests. The module can store up to ten different test configurations on the internal drive and many more on the PCMCIA cards.

To save the current test configuration

1 After you have completed the Setup Test tabs to configure your test, press OK.

2 Press the System button and select File > Save.

NOTE:

The module calculates the approximate maximum duration (total buffer size) of the histogram for each result based on the sample size and the results you select. If you select a smaller sample interval or more results, the maximum duration will be shorter for each histo-gram.



The Save Test Setup window appears.

3 From the Drive list, select the drive to store the configuration: Internal 1, Card 1, or Card 2.

4 Press the Filename field and use the keypad that appears to enter the file name in standard DOS format (8 characters with no spaces).

5 Press Save.

The configuration file is now ready to load for future tests.

Loading test configurations

Loading a saved test configuration file can help you quickly set up a test.

To load a saved file

1 Press the System button and select File > Load.



The Load Test Setup window appears.

2 From the Drive list, select the drive to load the configuration: Internal 1, Card 1, or Card 2.

3 Highlight a configuration file and press Load.

The test is configured and you can begin testing.

Deleting, renaming, and copying files

The File Maintenance feature allows you to delete, rename, and copy test configuration files.

To delete, rename, or copy a file

1 Press the System button and select File > Maintenance.



The File Maintenance window appears.

2 Select the file type from the File Type list: Test Setup, Script File (future), Extended File (Special System Files), or Print File.

3 Select the drive from the Drive list: Internal 1, Card 1, or Card 2.

– To delete a file, select the file and press Delete.

– To copy a file, select the file and enter a new filename in the Filename text box. Press Copy.

– To rename a file, select the file and enter the new filename in the Filename text box. Press Rename.

4 Press Close.

Formatting the internal drive

To format the internal drive

1 Press the System button and select File > Maintenance.

The File Maintenance window appears.

2 Press the Drive tab.



The Drive window appears.

3 Select Internal 1 from the Drive list.

Information about the drive is displayed.

4 Press Format to erase the contents of the drive.

5 Press Close.


Connecting the unit for testing


After you have configured a test, you are ready to connect the test unit. After the module is connected, results automatically begin to accumulate.

The module is equipped with the following connectors:

One E1 Receive (Balanced 120 Ω Twin-ax)

One E1 Transmit (Balanced 120 Ω Twin-ax)

One E1/E3/DS3 Receive (Unbalanced 75 Ω BNC)

One E1/E3/DS3 Transmit (Unbalanced 75 Ω BNC)

One E1 Reference Clock Input (Unbalanced, Square 75 Ω, BNC)

One E4/STM-1 Electrical Receive (Unbalanced 75 Ω BNC)

One E4/STM-1 Electrical Transmit (Unbalanced 75 Ω BNC)

One STM-1/4/16 Optical Receive (FC/PC, SC or ST, with Safety cover)

One 1550nm STM-1/4/16 Optical Transmit (FC/PC, SC or ST, with Safety cover)

One 1310nm STM-1/4/16 Optical Transmit (FC/PC, SC or ST, with Safety cover)

The module displays yellow LEDs next to the physical connectors to indicate which connectors to use based on the test configuration. For example, if the current test configuration is receiving an E1 signal while transmitting an STM-1(E) signal, the LEDs next to the E1 receive BNC and the E4/STM-1 transmit BNC are illuminated.

NOTE:

For optical testing, there are no separate LEDs for each transmitter. To verify which connector is active, refer to the Configuration Sum-mary bar.



Laser safety Next to each optical connector is a red LED to indicate whether the associated laser is active. The LED next to the transmit connector indicates that the laser is turned on. The LED next to the receive connector indicates that the fiber to the connector carries a live optical signal.

Operating modes There are three operating modes for performing tests: Terminate, Through, and MUX. Each mode requires a different hookup. Each mode is described below with an example of a proper hookup.

Terminate mode In Terminate mode, both the transmit and receive are set at the same rate. In SDH applications, both transmit and receive are electrical or optical, not mixed.

The module generates data for transmission independent of received data. The same mapping, tributary, and BERT pattern selections apply both to the Transmit and Receive data.

NOTE:

When connecting to a 2M circuit, you should connect to either the 75 Ω or the 120 Ω balanced receive connector, but not both. Doing so may result in erroneous errors.

CAUTION: HAZARDOUS LIGHT EXPOSURE

Do not look into laser when enabled! The unused optical transmitters should always be covered with the attached screw caps.

CAUTION: DAMAGE TO TEST UNIT

When looping the unit back to itself through a short length of optical fiber, it is necessary to insert an optical attenuator in the circuit to pro-tect the receiver from overload. Similar caution should be observed when connecting the unit to a network element.



Figure 5 shows how to connect the module for terminate testing.

Figure 5 — Terminate Mode connection

Thru mode In Thru mode, both the transmit and receive are set at the same rate. In SDH applications, both transmit and receive are electrical or optical, not mixed.

While operating in Thru mode, the module is intended to appear to the network as a section terminating equipment or repeater. In addition to signal regeneration, the module terminates and regenerates certain bytes in the section overhead. It therefore cleans up any errors that exist in the input signal for these bytes. These bytes include the A1 and A2 bytes (frame word), B1 byte, B2 bytes, and the J0 byte (contains the section trace). In Thru mode, you are able to insert frame, B1, and B2 errors, and the J0 byte.



Figure 6 shows how to connect the module for thru testing.

Figure 6 — Thru Mode connection

MUX mode In MUX mode, the module wraps a specific multiplexer using a BERT pattern.


Viewing test results

Figure 7 shows how to connect the module for MUX testing.

Figure 7 — MUX Mode connection

Viewing test results

Category results are displayed in the Results Display windows.

To view results for a category

1 Press the Category Selection button to display the result category list.



2 From the category result list, select a result category. For some categories, select the sub-category.

The results appear on the Dual Test Results display. For descriptions of each category and the results, refer to Chapter 7 “Interpreting Test Results” page 91.

Printing test results

The module allows you to print test results, events, and histograms using the Printer Management window (see Figure 8 on page 39). The following sections describe how to configure the Printer Management window to select the print mode, print location, print type, create headings for printouts, and configure printer settings.



Figure 8 — Printer Management window

Activating timed print

Only Standard (Std) Categories may be set to timed print.

To activate timed print

1 On the Printer Management window, press the Mode tab.

2 In the Print Mode box, press Timed.

3 Press the Interval field. Use the keypad that appears to enter the print interval.

NOTE:

If timed print is activated, and another print job is processed during the set interval, the timed print scheduled is ignored. Timed print is resumed at the next scheduled interval.



Printing to file The printer management feature allows you to save printouts to the internal drive or to one of the PCMCIA cards so that you can print files at another time.

To print to file


2 Set the appropriate Print Mode and Print Type.

3 In the Print Location box, press File.

4 Select where to save the file from the Device list.

5 Press the Filename box and use the keypad that appears to type in the name of the file (8 characters and no spaces). The system automatically saves the file as a .prt file.

6 Press Print.

Selecting the print type

The Print Type selection allows you to select the type of results you want to print.

NOTE:

If an existing file is selected for print, the file is appended to the file you just selected to print.

To print Select

Standard categories. Std Categories

Displayed results, including collection buffer results, in the left or right window.

Print Left/Right Results Window

NOTE: The Event Log only appears on the left display window, and can only be printed when Left Result Window is selected as the print type.

Current test configurations. Print Configurations



Creating headings The Headings tab allows you to enter headings that will print at the top of each printout. Each heading has a maximum of 40 characters.

To create a heading

1 On the Printer Management window, press the Headings tab.

2 Press a heading line and use the keypad that appears to enter the heading text.

Printing standard categories

The Std Categories tab appears when it is selected in the Mode tab. Standard categories include PDH Frame, SDH (includes SOH, HP, and LP), LED, Performance, Signal, Test Specific, and System. The Test Specific category prints the results based on the current test and prints only statistic-related results.

To print standard categories


2 Verify that Std Categories is checked as the print type.

3 Press the Std Categories tab.

4 Check the box next to each category you want to print.

Histogram results. When selected, the tabs associated with the histogram print feature appears (see “Printing histograms” on page 42).

Print Histogram

Specified data range within a collection buffer. (This prints the selected range)

Print Selected Range

Selected range of event data within the event log. You can print the events and any associated data stored in the capture buffer. (The same as Print Selected Range, but applies only to Event Log data.)

Print Selected Range Plus Data

To print Select



Printing histograms The Histogram print function allows you to print specific results based on the current test and the histogram configuration (see “Configuring histograms” on page 27). You can select different results to be printed from the same histogram buffer. For example, you can collect a variety of results for your histogram; however, you may only want to print certain results. After you collect the results, you can change the print configuration to print the results in any combination on the histogram printout.

To configure histogram print settings


2 Verify that Histogram is selected as the print type.

3 Press the Histogram tab.

The Histogram tab appears.

4 Select First Sample to set the histogram to print from the first sample in the buffer.

or

Select Set Start Date/Time to manually enter the start date and time. Press the Date and Time fields and use the keypad to enter the date and time.



5 Select Last Sample to set the histogram to print up to the last sample in the histogram buffer.

or

Press Set Duration to set the duration of the histogram print. Press the duration field and use the keypad to enter the days, hours, and minutes.

6 Press the Bar Interval field and set the number of hours and minutes represented by each bar in the histogram for the printout.

7 Select the results to be printed from the other tabs. The tabs that appear are based on the histogram configuration.

8 Press Print.

NOTE:

The module calculates the approximate maximum duration (total buffer size) of the histogram for each result based on the sample size and the results you select. If you select a smaller sample interval or more results, the duration for each histogram will be shorter.

NOTE:

Only histogram results that are valid to the current test configuration or that are set for collection are enabled for print selection. All other fields are disabled. See “Configuring histograms” on page 27 to define the histogram settings.



Figure 9 displays a sample Histogram printout.

Figure 9 — Histogram printout

Printing a selected range from the event log

The Selected Range and Selected Range Plus Data print options allow you to print a selected range of collection or trace buffers. Prior to printing the range, you must mark the range of buffer data you want to print.

NOTE:

Range selection only supports one marked range and the range is not saved through power down.



To select a range of buffer data

1 Open the event log in the left results window.

2 Press the Pause button in the results window to pause the displayed data.

3 Select the first result item by pressing the result.

4 Press the System button and select Mark Range End.

5 Select the last result item by pressing the result.

All of the result items between the two selected results are highlighted to confirm the selected range.

6 To print the range, press the System button and select Tools > Printer Mgmt.

7 On the Printer Management window, select the Mode tab.

8 Verify that Selected Range or Selected Range Plus Data is selected as the print type.

9 Press Print.



An example of a printout for a selected range is displayed in. Figure 10.

Figure 10 — Selected range printout

Using the remote control feature

See Appendix B “Remote Control Commands” page 143 for detailed remote control procedures, syntax, and commands.


Chapter 4

4 PDH Testing

This chapter provides step-by-step instructions for performing PDH testing. Topics discussed in this chapter include:

“About PDH testing” on page 48

“Viewing 2M timeslots” on page 48

“Conducting performance analysis” on page 49

“Performing a round trip delay test” on page 52

“Identifying anomalies and defects” on page 53

“Performing BER testing” on page 56`

“Monitoring network traffic” on page 57

“Verifying APS switchover time” on page 59

“Scenario: Troubleshooting a 45M service” on page 62


Chapter 4 — PDH Testing

About PDH testing

The module provides the ability to perform tests for PDH rates, including 2M, 8M, 34M, 45M, and 140M (E1, E2, E3, DS3, and E4 respectively). PDH testing verifies the quality of the circuit, identifies problems on the network that cause degraded performance, and primarily, maintains that the network is in accordance with ITU-T recommendations.

Viewing 2M timeslots

The 2M view displays an overview of all 32 timeslots. It displays an activity indicator of received byte and ABCD bits in MFAS framing. An empty circle denotes no activity for the corresponding time slot.

To view the 2M timeslots

1 Press the Category Selection button and select Misc. > 2M View.

NOTE:

When connecting to a 2M circuit, you should connect to either the 75 Ω or the 120 Ω balanced receive connector, but not both. Doing so may result in erroneous errors.


Conducting performance analysis

The 2M view appears on the main window.


Bit error measurements are used to measure the quality of a circuit. The ITU-T recommends various PRBS test patterns that simulate real traffic, after which different methods are used to analyze the bit errors and alarms to produce a measurement of the quality of a line. The measurements are used as the basis for Service Level Agreements. The module conducts PDH performance analysis for ITU-T specifications G.821, G.826, M.2100.

The module allows you to perform a timed test that captures information for a user-defined length of time. The module calculates the performance results based on the fixed time interval.

To conduct performance analysis

1 On the Application Button bar, press 2M, 34M, 45M, or 140M and select Terminate.

2 Press Setup > General.




3 Complete the Structure and corresponding tabs to configure the transmit payload. Refer to Appendix C “Field Descriptions” on page 169 for descriptions of tabs and data fields.

4 Select the BERT tab.

The BERT Setup tab appears.

5 Select the test pattern from the Pattern list.

– If you select 2ˆ15-1, 2ˆ20-1, or 2ˆ23-1, select the Pattern Type. Select Normal to use the selected pattern as it appears or select Invert to use the inverted pattern.

– If you select User Programmable, define the pattern.

6 Select the Timed Test tab.



The Timed Test Setup tab appears.

7 Check the Enable Timed Test box. Enter the length of the test (1 min. to 49d, 23h, and 59 min.).

8 Press OK to accept the test setup.

9 Connect a cable from the active transmit connector to the DUT receive connector.

10 Connect a cable from the active receive connector to the DUT transmit connector. Refer to “Connecting the unit for testing” on page 33 for information about using the connectors.

After the module is connected, results automatically begin to accumulate.

11 Press the Restart key to clear results and begin the test.

12 To view BERT results, press the Category Selection button and select BERT.

13 To view performance results, press the Category Selection button and select Performance > G.821 / G.826 OOS / G.826 ISM / M.2100 OOS / M.2100 ISM.

See “Interpreting BERT results” on page 95 and “Interpreting performance results” on page 100 for information on interpreting results.



Performing a round trip delay test

Round trip delay measurements are performed on looped back circuits (analysis rates 2M, 8M, 34M, and 45M) to troubleshoot and isolate excessive timing problems in networks. These measurements can also be used to confirm that the intended loopbacks in the network have occurred before proceeding with other network maintenance.

To measure round trip delay

1 On the Application Button bar, press 2M, 34M, or 45M and select Terminate.

2 To configure the test, press Setup > General.





5 Select Delay from the Pattern list.


Identifying anomalies and defects






10 To view results, press the Category Selection button and select BERT.

See “Interpreting BERT results” on page 95 for information on interpreting results.


Within PDH networks, there are many conditions that can result in the occurrence of anomalies and defects. Anomalies can lead to faults such as parity errors, and defects that can result in the total interruption of a connection. You can use the module to generate errors and simulate alarms, and analyze the corresponding response signals to enable troubleshooting and maintenance of network links.

Generating errors To generate errors

1 To analyze response signals, select the physical triggers for each signal. Then, view the events that are generated in the Event Log (see “Selecting physical triggers” on page 26).

2 On the Application Button bar, press 2M, 34M, 45M or 140M and select Terminate.






5 Select the Error Insert tab.

The Error Insert Setup tab appears.

6 Select the type of error to generate. If you select Bit Error/TSE, you must also select the rate. If you select an FAS error, you must select the Frame Error Count.




After the module is connected, results automatically begin to accumulate


11 Press the Insert Error action button to insert errors.

12 View the Event Log for physical trigger events.



13 View the alarm results on the LED panel. To view LED results on the main window, press the Category Selection button and select LED.

See “Interpreting LEDs” on page 111 and “Viewing the event log” on page 113 for information on interpreting results.

Simulating alarms To simulate alarms

1 On the Application Button bar, press 2M, 34M, 45M or 140M and select Terminate.



3 Complete the Structure tab to configure the transmit payload. Refer to Appendix C “Field Descriptions” on page 169 for descriptions of the tabs and data fields.

4 Select the 2M, 8M, 34M, 45M, or the 140M tab. This will depend on the analysis rate you selected in the Structure tab.

The Setup tab appears.

5 On the bottom of the tab are the alarms that may be simulated for the test. Select ON for each alarm you want to simulate.




7 Connect a cable from the active transmit connector to the DUT receive point.

8 Connect a cable from the active receive connector to the DUT transmit point. Refer to “Connecting the unit for testing” on page 33 for information about using the connectors.

After the module is connected, results automatically begin to accumulate

9 Press the Restart ley to clear results and begin the test.

10 View the Event Log for physical trigger events.


See “Interpreting LEDs” on page 111 for information on interpreting results.

Performing BER testing

The bit error rate (BER) test consists of determining the relationship between erroneous bits to the total received bits. The module generates a psuedorandom binary sequence (PRBS) which simulates the transmission of live traffic. This sequence is either received by another test set or looped back to the originating test set which then compares it bit by bit with the expected result. Any erroneous bits are reported as bit errors and a corresponding bit error rate is calculated based on the frequency of the errors.

To perform BER testing

1 On the Application Button bar, press 2M, 34M, 45M or 140M. and select Terminate.




Monitoring network traffic

3 Complete the Structure and corresponding tabs to configure the transmit payload. Refer to Appendix C “Field Descriptions” on page 169 for descriptions of the data fields.







8 Connect a cable from the active receive connector to the DUT transmit connector. Refer to “Connecting the unit for testing” on page 33 for information about the connectors on the module.


9 Press the Restart softkey to clear results and begin the test.



Monitoring network traffic

Testing in the through mode allows you to unobtrusively monitor network traffic for troubleshooting or performing In-Service Monitoring (ISM) performance measurements in accordance with ITU-T recommendations.



To monitor network traffic

1 On the Application Button bar, press 2M, 34M, 45M or 140M. and select Thru.


3 Select the Structure tab.

4 Complete the Structure and corresponding tabs to configure the transmit payload. Refer to Appendix C “Field Descriptions” on page 169 for descriptions of the data fields.

5 Select the 2M, 8M, 34M, 45M, or the 140M tab. This will depend on the analysis rate you selected in the Structure tab.

The Setup tab appears. This is an example of the 2M configuration tab.

6 Set the Rx Input to Monitor.

– If you are testing a 2M circuit, select Monitor or Bridge.

– If you select Monitor, set the Rx Mon Atten for accessing Protected Monitor Points (PMP).

7 Connect a cable from the active receive connector to DUT transmit connector. Refer to “Connecting the unit for testing” on page 33 for information about the connectors on the module.


Verifying APS switchover time



9 To view results, press the Category Selection button and then the appropriate results category.

See Chapter 7 “Interpreting Test Results” page 91 for information on interpreting results.


When an APS mechanism is installed, its conformance to the prescribed switchover time from ‘working line’ to ‘protection line’ becomes critical. If the network switch-over does not take place within the stipulated time, it may set off a number of alarms, rendering certain route segments, or even the complete ring, unserviceable.

The module measures the APS switchover time of an SDH network by measuring the effect to an end customer off a PDH drop. This ensures that the end effect to a customer is a loss of framing less than the ITU-T recommendation of 50 ms.

To verify APS switch-over time

1 On the Application Button bar, press 2M, 34M, 45M or 140M. and select Terminate.



4 Select the Analysis Rate for the PDH drop.

5 Select the Physical Triggers tab.

6 Check PDH APS.




8 Connect a cable from the active transmit connector to the DUT receive connector. Refer to “Connecting the unit for testing” on page 33 for information about the connectors on the module.

9 Connect a cable from the active receive connector to the DUT transmit connector.

10 After the module has established Frame Sync, press the Start APS action button to enable the test.

11 Enable the APS switchover by forcing the network to switch to the backup lines. This is accomplished in one of two ways:

Figure 11 on page 61 illustrates this methodology.

Method Description

Interrupting the signal

Physically interrupt the signal by pulling it from the ADM.

Inserting errors Use another test set in Through mode to insert errors until the network switches.



Figure 11 — APS Switchover

After the module detects a Loss of Frame Sync, it automatically begins to measure the time in milliseconds until Frame Sync is re-established at the analysis rate. The event log appears on the left results window and the signal results appear on the right results window.

See “Interpreting signal results” on page 94 for information on interpreting results.



Scenario: Troubleshooting a 45M service

The following scenario describes how to configure a histogram collection and to analyze service performance.

Evaluating the situation

You have received a trouble ticket for a 45M service. The customer reports network congestion during the hours of midnight to two-o-clock a.m. To locate the source of the problem, set up a histogram to collect data during the hours of congestion.

To configure the histogram to collect data

1 On the Application Button bar, press 45M > Thru.



The Structure Setup tab appears.

The Analysis Rate must be 45M when testing a 45M service.

4 Set the Framing and Tx Timing to match that of the service being tested.

5 Select the 45M tab.



The 45M Setup tab appears.

6 Set the Framing to match that of the service being tested.

7 Press OK to accept the test configuration.

8 To configure the histograms, press Setup > Histograms.

9 Select the Histogram Settings tab.

The Histogram Settings tab appears.



10 Check the Enable Histogram Collection box. Specify the Sample Interval time as the amount of time between the collection of samples of each result to be histogrammed. (1440 minutes = 1 day).

11 Select each result tab and check off each result to collect in the histogram. These should correspond with the problems that the customer reports.

12 Press OK to accept the histogram configuration.

13 Connect a cable from the 2M/34M/45M active transmit connector to the DUT receive connector.

14 Connect a cable from the 2M/34M/45M active receive connector to the DUT transmit connector.


NOTE:

The module calculates the approximate maximum duration (total buffer size) of the histogram for each result based on the sample size and the results you select. If you select a smaller sample interval or more results, the maximum duration will be shorter for each histo-gram.




Report back to the customer premises the following day.

To print the histogram data and analyze service performance

1 Connect the printer to the module and configure the printer settings (see “Connecting the printer” on page 10). Turn the printer ON.

2 Press the System button and select Tools > Printer Mgmt

3 Select the Mode tab.

4 Verify that Histogram is selected for the print type.

5 Select the Histogram tab.

The Histogram tab appears.

6 Select Set Start Date/Time to manually enter the start date and time. Press the Date and Time fields and use the keypad to enter the date and time.

7 Select Set Duration to set the duration of the histogram print. Press the duration field and use the keypad to enter the hours and minutes.

8 Press the Bar Interval field and set the number of hours and minutes represented by each bar in the histogram for the printout.



9 Select each result tab and check off each result to print. The tabs that appear are based on the histogram configured in the previous procedure.

10 Press Print.

11 After the printouts are complete, locate the events that occurred between the hours of congestion.

The information on the printout enables you to analyze and troubleshoot the service performance.

Conclusion You have successfully configured a histogram and used this data to troubleshoot service problems. Histograms are an easy way to monitor service performance over a long period of time. Use this procedure when troubleshooting other network services.


Chapter 5

5 SDH Testing

This chapter provides step-by-step instructions for performing SDH testing. Topics discussed in this chapter include the following:

“About SDH testing” on page 68

“Conducting performance analysis” on page 68

“Identifying anomalies and defects” on page 70

“Performing BER testing” on page 74

“Analyzing pointer movements” on page 75

“Identifying trace messages” on page 78

“Scenario: Turning up an STM-16 service” on page 80


Chapter 5 — SDH Testing

About SDH testing

The module provides the ability to perform tests for STM rates, including STM-1 (E), STM-1 (O), STM-4, and STM-16. SDH testing verifies the quality of the circuit, identifies problems on the network that cause degraded performance, and primarily, maintains that the network is in accordance with ITU-T recommendations.


Bit error measurements are used to measure the quality of a circuit. The ITU-T recommends various PRBS test patterns that simulate real traffic, after which different methods are used to analyze the bit errors and alarms to produce a measurement of the quality of the line. These measurements are used as the basis for Service Level Agreements.

The module conducts SDH performance analysis for ITU-T specifications G.821, G.826, and M.2101.

To conduct performance analysis

1 On the Application Button bar, press STM-1 (E), STM-1 (O), STM-4, or STM-16 and select Terminate.

2 To configure the test, press the Setup > General.


3 Complete the Structure and corresponding tabs to configure the transmit payload. For descriptions of data fields, refer to Appendix C “Field Descriptions” page 169.

CAUTION: DAMAGE TO TEST UNIT

When looping the unit back to itself through a short length of optical fiber, it is necessary to insert an optical attenuator in the circuit to pro-tect the receiver from overload. Similar caution should be observed when connecting the unit to a network element.



4 Select the BERT tab and select the test pattern from the Pattern list.

– If you select 2ˆ15-1, 2ˆ20-1, or 2ˆ23-1, 2ˆ31-1select the Pattern Type. Select Normal to use the selected pattern as it appears or select Invert to use the inverted pattern.


5 Select the Timed Test tab and check the Enable Timed Test box. Enter the length of the test (1 min. to 49d, 23h and 59 min.).




9 If you are performing an optical test, press the Laser system button to turn the laser on.



11 To view BERT results, press the Category Selection button and select BERT.

12 To view performance results, press the Category Selection button and select Performance > G.821 / G.826 / M.2100 / M.2101.


See “Interpreting performance results” on page 100 for information on interpreting performance results.






Within SDH networks, there are many conditions that can result in the occurrence of anomalies and defects. Anomalies can lead to faults, such as parity errors, and defects that can result in the total interruption of a connection. You can use the module to generate errors and simulate alarms, and analyze the corresponding response signals to enable troubleshooting and maintenance of network links.

Generating errors To generate errors

1 Before analyzing response signals, select the desired physical trigger categories (see “Selecting physical triggers” on page 26).




4 Complete the Structure and corresponding tabs to configure the transmit payload. Refer to Appendix C “Field Descriptions” page 169 for descriptions of data fields.

5 Select the Error Insert tab.



The Error Insert Setup tab appears.

6 Select the type of error to generate.

– If you select Bit Error/TSE, you must also select the rate.

– If you select an FAS or Framing error, you must select the Frame Error Count.











12 Press the Insert Error action button to insert errors.

13 View the Event Log for physical triggers events.



Simulating alarms To simulate alarms

1 Before analyzing response signals, select the physical triggers for each signal (see “Selecting physical triggers” on page 26).




4 Complete the Structure tab to configure the transmit payload. Refer to Appendix C “Field Descriptions” page 169 for descriptions of data fields.

5 Select the SDH tab.



The SDH tab appears. On the bottom of the tab are the alarms that may be simulated for the test.

6 In Alarm Type, select the type of alarm to simulate.

7 In Alarm Insertion, select ON.

8 Repeat step 6 and 7 for each alarm you want to simulate

Alarms are mutually exclusive for SDH.



11 Connect a cable from the active receive connector to the DUT transmit connector. Refer to “Connecting the unit for testing” on page 33 for information about using the connectors .






After the module is connected, results automatically begin to accumulate and alarms instantly begin transmitting.


14 View the Event Log for physical triggers events.



Performing BER testing

The bit error rate (BER) test consists of determining the ratio of erroneous bits to the total received bits. The module generates a psuedorandom binary sequence (PRBS) which simulates the transmission of live traffic. This sequence is either received by another test set or looped back to the originating test set which then compares it bit by bit with the expected result. Any erroneous bits are reported as bit errors and a corresponing bit error rate is calculated based on the frequency of the errors.

To perform BER testing




3 Complete the appropriate tabs and data fields to configure the transmit payload. Refer to Appendix C “Field Descriptions” page 169 for descriptions of the data fields.




Analyzing pointer movements





8 Connect a cable from the active receive connector to the DUT transmit point. Refer to “Connecting the unit for testing” on page 33 for information about the connectors on the module.







Each SDH Frame contains an Administrative Unit (AU-n) pointer indicating the offset of the frame start relative to the multiplex section frame start. Lower order constructs contain Tributary Unit (TU-n) pointers that indicate the offset of the payload frame start relative to the higher order Virtual Container frame start.





The module allows you to analyze received pointer values and to adjust transmitted pointer values. Transmit pointers may be incremented or decremented by one, or assigned arbitrary values accompanied by the New Data Flag (NDF).

To analyze pointer movements


When testing an SDH circuit, three action buttons appear at the bottom of the main window: Pointer +1, Pointer -1, and NDF.



3 Complete the appropriate tabs and data fields to configure the transmit payload. For descriptions of the data fields, refer to Appendix C “Field Descriptions” page 169.

4 Select the SDH tab.

The SDH tab appears.

5 Select the Pointer Type. The choices available are dependent on the structure for the transmit payload.





8 Connect a cable from the active receive connector to the DUT transmit connector. For information about the connectors on the module, see “Connecting the unit for testing” on page 33.


10 During the test, use the action buttons to increment, decrement, or assign an arbitrary value to the pointer.

– Pointer + / - increases or decreases the pointer.

– NDF (New Data Flag) allows you to specify a new pointer value by typing in the value.

11 To view results, press the Category Selection button and select HP or LP.

See “Interpreting HP results” on page 106 or “Interpreting LP results” on page 108 for information on interpreting results.





Identifying trace messages

Trace identifiers are used by receivers to verify continued connection to the intended transmitter.

Using the module, you can generate and analyze Regenerator Section and Path Trace messages transmitted in the J0, J1, and J2 overhead bytes. All formats indicated in G.707 are supported.

To identify trace messages




3 Complete the appropriate tabs and data fields to configure the transmit payload. For descriptions of the data fields, refer to Appendix C “Field Descriptions” page 169.

4 Select the VC-3 POH, VC-4 POH, VC-12 POH or the SOH tab (this depends on the Structure selection).

The VC-n POH or SOH Setup tab appears.

5 Select the Path Trace Format.


Identifying trace messages

– If you select 64-Byte, you must also select the Trace Terminator.

6 Press the Path Trace String field and use the keypad to enter a character message. The default is “2416 TEST SET.”

Remaining bytes are filled with null characters.




10 Verify that the message was sent correctly. View the Event Log to verify that no events were generated. Also, verify that the LED display illuminates Green for the appropriate LEDs.

See “Interpreting LEDs” on page 111 for information on interpreting results.

See “Viewing the event log” on page 113 for information on viewing events.





Scenario: Turning up an STM-16 service

The following scenario describes how to qualify and verify a new SDH service.


You have installed a new STM-16 service at a customer premise. To turn up the new service, perform BER testing and analyze performance measurements.

To verify an STM-16 service

1 Press STM-16 > Terminate.




The Structure Setup tab appears.

4 Define the transmit payload to correspond with the service being tested.








7 Select the Timed Test tab.



The Timed Test setup window appears.

8 Check the Enable Timed Test box and enter the duration of the test (1 min. to 49d, 23h, and 59 min.).



11 Connect a cable from the active receive connector to the DUT transmit connector. For information about using the connectors, refer to “Connecting the unit for testing” on page 33.




14 To view results, press the Category Selection button and





– Select BERT to view BERT results.

– Select Performance to view performance results.

See “Interpreting BERT results” on page 95 and “Interpreting performance results” on page 100 for information on interpreting results.

Conclusion You have successfully performed BERT and Performance Analysis to turn up a new SDH service. The BERT (bit error rate test) consists of determining the relationship between erroneous bits to the total received bits. Performance Analysis measurements are the basis for Service Level Agreements. Use these procedures when turning up other SDH services.


Chapter 6

6 MUX Testing

This chapter provides step-by-step instructions for performing MUX testing. Topics discussed in this chapter include the following:

“About MUX testing” on page 86

“Testing a multiplexer” on page 86

“Scenario: Turning up a multiplexer” on page 88


Chapter 6 — MUX Testing

About MUX testing

Because the transmitter and receiver on the module can operate independently, the module can perform out-of-service testing of a multiplexer. The test is performed by sending a signal through a multiplexer high speed interface and analyzing its tributary from a low-speed drop side.

Testing a multiplexer

To test a multiplexer, a payload is generated and is tested to verify that it is correctly mapped in the Virtual Container (MUX) and that is correctly received (DeMUX).

To test a multiplexer

1 On the Application Button bar, press the MUX button and select the receive interface and transmit interface.


The Setup Test window appears. Refer to Appendix C “Field Descriptions” for descriptions about the tabs and data fields.

3 Select the Rx Structure tab and select the Analysis Rate and Framing.

4 Select the Tx Structure tab and select the Virtual Container on which to send the payload.

NOTE:

Some add/drop muxes incorporate a laser safety feature that disables the transmit laser when the corresponding receiver is not receiving laser light. This feature may need to be disabled on the add/drop mux.

N NOTE:

The Receive and Transmit selections in the following procedures refer to the Receive and Transmit on the module, not the device under test.


Testing a multiplexer

5 Complete the Tributary Selection for the path being tested.

6 Set the Tx Timing (external is from Rx).



9 Connect a cable from the active receive connector to the DUT transmit connector.




12 Press the Category Selection button and select Signal. Select the rate at which the payload was transmitted.

13 Verify the payload was mapped correctly in the Virtual Container.

14 Press the Category Selection button and select Signal. Select the rate at which the payload was received.

15 Verify that the payload was received correctly.





Scenario: Turning up a multiplexer

The following scenario describes the process to verify and qualify a new multiplexer.


You have just installed a new multiplexer. To turn up the new multiplexer, verify that the transmit payload is mapped correctly on the Virtual Container and that the receive payload is received correctly. In this scenario, 140M is the receive interface and STM-4 is the transmit interface.

To turn up the new multiplexer

1 On the Application Button bar, press the MUX button. Select 140M as the receive interface and STM-4 as the transmit interface.



3 Select the Rx Structure tab.

The Rx Structure tab appears.

4 From the Analysis Rate list, select 140M.

5 Specify the Framing.


Scenario: Turning up a multiplexer

6 Select the Tx Structure tab.

The Tx Structure tab appears.

7 The VC Mapping is set to VC-4.

8 Enter 1 for the STM-N tributary.

9 Specify the Tx Timing.

10 Connect a cable from the STM-1/4/16 Optical Transmit connector to the DUT receive connector.

11 Connect a cable from the E4/STM-1 Electrical Receive connector to the DUT transmit connector.




14 Press the Category Selection button and select Signal > At SDH.





15 Verify that the payload was mapped correctly in the Virtual Container.

16 Press the Category Selection button and select Signal > At 140M.

17 Verify that the payload was received correctly.

18 Repeat Steps 8 - 16 for each STM-N tributary (2, 3, and 4).

Conclusion You have successfully turned-up the new multiplexer by verifying that the payload is mapped and received correctly for each STM-1 tributary at the STM-4 rate. Correct mapping verifies that the multiplexer can successfully transmit and receive at different rates.


Chapter 7

7 Interpreting Test Results

This chapter describes the test results for each result category in the module. Topics discussed in this chapter include the following:

“About interpreting test results” on page 92

“Interpreting summary results” on page 92

“Interpreting signal results” on page 94

“Interpreting BERT results” on page 95

“Interpreting PDH frame results” on page 97

“Interpreting performance results” on page 100

“Interpreting SOH results” on page 104

“Interpreting HP results” on page 106

“Interpreting LP results” on page 108

“Interpreting LEDs” on page 111

“Viewing the event log” on page 113


Chapter 7 — Interpreting Test Results

About interpreting test results

After you have connected the module, results for the configured test automatically accumulate. Select a category in each display window to analyze the results for your test.

Interpreting summary results

The Summary category provides a summary of the most important test results. The All Summary Results OK message is displayed when all of the summary results are within the recommended specifications and no alarms are present (see Figure 12).

Figure 12 — All Summary Results OK

NOTE:

Results are blank if gating criteria has not been met. Criteria exam-ples include Signal Present, Frame Sync Present, Pointer Present, and BERT Pattern Sync Present.


Interpreting summary results

When errors are detected, the Summary Result display window lists each error that occurred (see Figure 13).

Figure 13 — Summary Results Error display

The System button also changes to red to indicate that there is a summary error if the Summary Result display window is not currently displayed.

To display the list of errors that occurred, press the System button and select Summary Results.



Interpreting signal results

Figure 14 displays an example of signal results for SDH and 140M.

Figure 14 — Signal results for SDH and 140M

Table 3 describes the test results for the Signal category.

Table 3 — SDH module signal results

Result Description

1310 nm Rx Lvl (dBm)

The optical power of the incoming 1310nm optical signal if it is 1310 nm wavelength.

1550 nm Rx Lvl(dBm)

The optical power of the incoming 1550nm optical signal if it is 1550 nm wavelength.

APS Time (ms) The amount of time it takes to regain frame sync while running an APS test.

Code Err Cnt The number of code violations detected.

Code Err Rate The number of code errors detected divided by the number of bits received. This result is calculated after initial signal presence is established.


Interpreting BERT results

Interpreting BERT results

Figure 15 displays an example of BERT results.

Figure 15 — BERT results

Ref Freq (Hz) The frequency of the received 2M external reference signal.

Rx Delta (ppm) The deviation in ppm from the standard ITU frequency.

Rx Freq (Hz) The frequency of the received data.

Rx Lvl (dBnom or dBdsx)

The level of the incoming electrical signal.

Rx Max Dev (ppm)

The maximum deviation of the receive frequency since the last test restart.

Signal Loss/LOS

The number of signal losses since initial signal detection

Tx Freq (Hz) The frequency of the data generating frequency.

Table 3 — SDH module signal results (continued)

Result Description



Table 4 describes the results for the BERT category.

Table 4 — BERT results

Result Description

Bit Errors / TSE The number of Bit Errors detected in the test pattern since pattern synchronization was achieved.

Bit Error Rate The total number of bit errors detected divided by the number of pattern bits received after initial pattern synchronization excluding patter loss periods.

Pattern Slip The number of pattern slips detected in the received pseudorandom test pattern. Pattern Slips occur when one or more bits of the test pattern are deleted or repeated.

Pattern Sync Loss

The number of synchronization losses since the initial pattern synchronization.

Pattern Slip Sec The total number of test seconds in which pattern slips were detected since initial pattern synchronization.

Pattern Loss Sec

The total number of seconds in which pattern synchronization losses were detected since the initial pattern synchronization.

Trip Delay (ms) The measurement is made on the delay test patterns in the selected channel.


Interpreting PDH frame results


Figure 16 displays and example of PDH frame results for 140M and 2M.

Figure 16 — PDH frame results for 140M and 2M

Table 5 describes the test results for the PDH category.

Table 5 — PDH frame results

Result Description

C-Bit Errors The number of times an M-frame contains a mismatch between the majority rule of the C-Bit path parity bits (CP-bits) and the parity calculated from the information bits in the previous M-frame, and the passage of 1 or more M-frames without a DS3 frame sync loss.

C-Bit Err Rate The number of C-Bit parity errors detected divided by the total number of multiframes received.

C-Bit Err Sec The number of test seconds in which at least one parity error was counted.



CRC Errors The number of Cyclic Redundancy Code Errors (CRC-4) errors received while in FAS-CRC or MFAS-CRC synchronization.

CRC Err Rate The number of CRC errors detected divided by the total number of CRC bits received.

CRC Sync Loss The number of CRC Sync losses detected. This result accumulates after initial frame sync is established, and stops during frame loss.

FEBE The number of Far End Blocks Errors received since last test restart.

FEAC The FEAC message is displayed if 2 consecutive repetitions of one of the following messages are received in the C-Bit FEAC channel.

– Comm Equip Fail NSA– DS3 Idle– DS3 Out of Frame– DS3 LOS/HBER– DS3 Equip Fail SA– DS3 Equip Fail NSA– Mult DS1 LOS/HBER– Single DS1 LOS/HBER– DS1 Equip Fail SA– DS1 Equip Fail NSA

Far OOF Sec The number of seconds in which the DS3 yellow alarm was present for at least some part of the test second.

FAS BER The number of bit errors received divided by the number of FAS bits received. This result accumulates after initial frame sync is established.

FAS Bit Errors The number of FAS bit errors detected. This result accumulates after initial frame sync is established, and stops during frame loss.

FAS Errors The number of FAS Words received that contain an error.

Table 5 — PDH frame results (continued)

Result Description



FAS Err Rate The number of FAS Words received divided by the number of frames received. This result is calculated after initial frame sync is established.

FAS Sync Loss The number of Frame Alignment Signal (FAS) sync losses detected since the last test restart.

Frame Errs The number of F-Bit errors detected. This result accumulates after initial frame sync is established, and stops during frame loss.

Frame Err Rate The number of F-Bit errors received divided by the number of F-Bits received. This result is calculated after initial frame sync is established.

Frame Err Sec The number of seconds in which at least one frame error was received. This result is calculated after initial frame sync is established.

Frame Sync Loss

The number of Frame Sync losses detected since the last test restart.

MFAS Errors The number of Multiframe Alignment Signal (MFAS) errors received since MFAS or MFAS-CRC synchronization.

MFAS Err Rate The number of MFAS errors received divided by the number of multiframes received. This result is calculated after initial multiframe sync is established.

MFAS Sync Loss

The number of MFAS sync losses since initial MFAS sync.

Near OOF Sec The number of seconds in which DS3 frame sync was not present or AIS was present for at least some part of the test second.

NFAS Word The N-FAS word contains the Si and Sa bits.

Parity Errors The number of times M-Frame contains a mismatch between either parity bit (p-bits) and the parity calculated from the information bits in the previous M-frame and the passage of one or more M-frames without DS3 frame sync loss.


Result Description



Interpreting performance results

Figure 17 displays an example of performance results for G.821 and M.2100 ISM.

Figure 17 — Performance results

Parity Err Rate The number of parity errors divided by the number of bits received.

Parity Err Sec The number of test seconds in which at least one parity error was counted.

REBE The number of Remote End Block Errors (REBE) detected while in CRC-4 multiframe alignment.

Rx Xbits The current state of Rx X-Bits. It will be ‘00’, ‘11’, ‘01’, or ‘10’.


Result Description



Table 6 describes the test results for the Performance category.

Table 6 — Performance results

Result Description

% Avail Sec The percentage of test seconds that are available seconds.

% Degraded Min

The percentage of test minutes that are degraded.

% Errored Sec The percentage of test seconds that are errored.

% Err Free Sec The percentage of test seconds that are error free.

% Sev Err Sec The percentage of test seconds that are severely errored.

Available Sec The available time starts with the first second of a ten consecutive second period in which none of those ten seconds are severely errored.

BERT Bkgnd BER

The ratio of BERT background block errors to the total number of BERT blocks received.

BERT Bkgnd Blocks

The ratio of background block errors to the total number of blocks received.

BERT Errored Blocks

The number of blocks with bit errors based on the ITU G.826 specification.

BIP Bkgnd BER The ratio of BIP background block errors to the total number of BIP blocks received.

BIP Bkgnd Blocks

The number of blocks with BIP errors that were not part of a severely errored second based on the ITU G.826 specification.

BIP Errored Blocks

The number of blocks with BIP errors based on the ITU G.826 specification for SDH.

Bkgnd Block Err The number of blocks with errors that were not part of a severely errored second based on the ITU G.826 specification. The errors will be FAS errors for 2M non-CRC, 8M, 34M, and 140M. The errors will be CRC errors for 2M CRC. The errors will be parity errors for 45M.



Bkgnd BER The ratio of errored blocks to total blocks during a fixed measurement interval, excluding all blocks during Severely Errored Seconds and unavailable time.

Consec SEC The number of times 3 or more consecutive severely errored seconds occurred.

CRC Bkgnd BER

The ratio of CRC background block errors to the total number of CRC blocks received.

CRC Bkgnd Blocks

The number of blocks with CRC errors that were not part of a severely errored seconds based on the ITU G.826 specification.

CRC Errored Blocks

The number of blocks with CRC errors based on the ITU G.826 specification for PDH.

Degraded Min The degraded test minutes are counted by grouping test seconds (from available time) into blocks of 60 excluding seconds labeled as severely errored seconds. If such a block contains a bit error ratio greater than 1 x 10(-6), the minute is Degraded.

Errored Blocks The number of blocks with errors based on the ITU G.826 specification. The errors will be FAS errors for 2M non-CRC, 8M, 34M, and 140M. The errors will be CRC errors for 2M CRC. The errors will be parity errors for 45M.

Errored Sec The number of seconds in error as specified by ITU G.821, G.826, M.2100, or M.2101.1 for errored seconds.

Error Free Sec For out-of-service operation, this indicates a count of test seconds that do not contain any bit errors. For in-service operation, this indicates a count of test seconds that do not contain any anomalies or defects.

Err Sec Ratio The ratio of errored seconds to total seconds in available time during a fixed measurement.

FAS Bkgnd BER

The ratio of FAS background block errors to the total number of FAS blocks received.

Table 6 — Performance results (continued)

Result Description



FAS Bkgnd Blocks

The number of blocks with FAS errors that were not part of a severely errored seconds based on the ITU G.826 specification.

FAS Errored Blocks

The number of blocks with FAS errors based on the ITU G.826 specification for PDH.

Parity Bkgnd BER

The ratio of parity background block errors to the total number of parity blocks received.

Parity Bkgnd Blocks

The number of errors with parity errors that were not part of a severely errored second based on the ITU G.826 specification.

Parity Errored Blocks

The number of blocks with parity errors based on the ITU G.826 specification for PDH.

Sev Err Sec The number of seconds that are severely errored as specified by ITU G.821, G.826, M.2100, or M.2101.1 for severely errored seconds.

Severely ESR The ratio of severely errored seconds to total seconds in available time during a fixed measurement.

Unavail Sec The unavailable time starts with the first second of a ten consecutive second period in which each of those ten seconds are severely errored.

Table 6 — Performance results (continued)

Result Description



Interpreting SOH results

Figure 18 displays an example of SOH results.

Figure 18 — SOH results

Table 7 describes the test results for the SOH category.

Table 7 — SOH results

Result Description

B1 Errors The number of B1 errors detected. This result accumulates after initial frame sync is established.

B1 Error Rate The equivalent line error rate calculated from the number of B1 errors detected and the total number of bits received.

B2 Errors The number of B2 errors detected. This result accumulates after initial frame sync is established.

B2 Error Rate The equivalent line error rate calculated from the number of B2 errors detected and the total number of received bits included in the B2 calculation.

Bridge Req Code

The interpreted value of the K1 Byte Bridge request code as described in ITU Rec G.841.


Interpreting SOH results

Dest Node ID The value of the K1 Byte Destination node ID field as described in ITU Rec. G.841.

FAS Errors The number of errored FAS words received.

FAS Err Rate The number of FAS errors divided by the number of frames received.

LOF Loss of Frame count since test restart.

K1 Chan The interpreted value of the K1 Byte Channel number field as described in ITU Rec. G.783.

K2 Chan The interpreted value of the K2 Byte Channel number field as described in ITU Rec. G.783.

MSP Arch The interpreted value of the K2 Byte Architecture field as described in ITU Rec. G.783.

MS-REI The sum of the REI counts decoded from the M1 byte of the section overhead.

MS-REI Rate The equivalent line error rate calculated from the MS-REI count.

OOF The number of Out of Frame events detected. This result accumulates after initial frame sync is established.

Path Code The interpreted value of the K2 Byte path code field as described in ITU Rec. G.841.

Req Code The interpreted value of the K1 Byte Request code as described in ITU Rec. G.783.

Source Node ID The value of the K2 Byte Source node ID field as described in ITU Rec. G.841.

Section Trace The received section trace string decoded from J0 Byte.

Status The interpreted value of the K2 Byte Status field as described in ITU Rec. G.841 (Ring) or G.783 (Linear).

Table 7 — SOH results (continued)

Result Description



Interpreting HP results

Figure 19 displays an example of HP results.

Figure 19 — HP results

Table 8 describes the test results for the HP category.

Table 8 — HP results

Result Description

AU-4 LOP The number of AU-4 Loss of Pointer events since the last test restart.

AU-4 Ptr Decrement

The number of AU-4 pointer decrements since the last test restart.

AU-4 Ptr Increment

The number of AU-4 pointer increments since the last test restart.

AU-4 Ptr Justification

The sum of all AU-4 pointer increment and decrement counts since the last test restart.

AU-4 Ptr NDF The number of AU-4 new data flags received since the last test restart. Three consistent new pointers received are also counted as one NDF.


Interpreting HP results

AU-4 Ptr Received

The value of the AU-4 pointer received in the H1 and H2 bytes of the Section Overhead. If the received value is outside the valid range, the result will display ‘Invalid.’ The result will be blank if the pointer is not available.

AU-4 Ptr Transmitted

The value of the transmitted AU-4 pointer.

VC-4 B3 Err Count

The number of VC-4 B3 errors detected. This result accumulates after initial frame sync is established and stops during frame loss.

VC-4 B3 Error Rate

The equivalent line error rate calculated using the VC-4 B3 Error Count.

VC-4 Path Status

The binary display of the received VC-4 G1 byte.

VC-4 Path Trace

The message identifying the source of the VC-4 path data.

VC-4 REI The total counts contained in the first four bits in the G1 byte of the foreground VC-4 Path Overhead.

VC-4 REI Rate The equivalent line error rate calculated using the VC-4 REI Error Count.

VC-4 Signal Label

The composition of the received VC-4 container, decoded from the VC-4 Path Overhead C2 Byte.

Table 8 — HP results (continued)

Result Description



Interpreting LP results

Figure 20 displays an example of LP results.

Figure 20 — LP results

Table 9 describes the test results for the LP category.

Table 9 — LP results

Result Description

TU-12 Ptr Decrement

The number of TU-12 pointer decrements detected since the last test restart.

TU-12 Ptr Increment

The number of TU-12 pointer increments detected since the last restart.

TU-12 Ptr Justification

The sum of all TU-12 pointer increment and decrement counts since the last test restart.

TU-12 LOP Count

The number of TU-12 Loss of Pointer events since the last test restart.

TU-12 Ptr NDF The number of TU-12 new data flags received since the last test restart. Three consistent new pointers received are also counted as one NDF.


Interpreting LP results

TU-12 Ptr Received

The value of the TU-12 pointer received in the V1 and V2 bytes of the TU-12 Path Overhead. If the received value is outside of the valid range, the result displays ‘Invalid.’. The result will be blank if the pointer is not available.

TU-12 Ptr Transmitted

The value of the transmitted TU-12 pointer.

TU-3 Ptr Decrement

The number of TU-3 pointer decrements detected since the last test restart.

TU-3 Ptr Increment

The number of TU-3 pointer increments detected since the last restart.

TU-3 Ptr Justification

The sum of all the TU-3 pointer increment and decrement counts since the last test restart.

TU-3 LOP Coun The number of TU-3 Loss of Pointer events since the last test restart.

TU-3 Ptr NDF The number of TU-3 new data flags received since the last test restart. Three consistent new pointers received are also counted as one NDF.

TU-3 Ptr Received

The value of the TU-3 pointer received in the H1 and H2 bytes of the TU-3 Path Overhead. If the received value is outside the valid range, the result displays ‘Invalid.’. The result will be blank if the pointer is not available.

TU-3 Ptr Transmitted

The value of the transmitted TU-3 pointer.

VC-12 BIP2 Error

The number of BIP2 errors detected. This result accumulates after initial frame sync is established and stops during frame loss.

VC-12 BIP2 Error Rate

The equivalent line error rate calculated using the VC-12 BIP2 Error Count.

VC-12 REI Count

The total of set REI bits. The REI bit is contained in the V5 byte, bit 3.

VC-12 REI Rate The equivalent line error rate calculated using the VC-12 REI Count.

Table 9 — LP results (continued)

Result Description



VC-12 V5 Byte The binary display of the received VC-12 Path Overhead V5 byte.

VC-12 Signal Label

The decoded message of bit 5 - 7 of the VC-12 Path Overhead V5 byte. This indicates how the 2M data is mapped into the container.

VC-3 B3 Err Count

The number of VC-3 B3 errors detected. This result accumulates after initial frame sync is established and stops during frame loss.

VC-3 B3 Error Rate

The equivalent line error rate calculated using the VC-3 B3 Error Count.

VC-3 Path Trace

The message identifying the source of the VC-3 path data.

VC-3 REI Count The sum of the counts contained in the first four bits in the G1 byte of the foreground VC-3 Path Overhead.

VC-3 REI Rate The equivalent line error rate calculated using the VC-3 REI Count.

VC-3 Signal Label

The composition of the received VC-3 container. It is decoded from the received C2 byte in the VC-3 Path Overhead.

Table 9 — LP results (continued)

Result Description


Interpreting LEDs

Interpreting LEDs

There are two locations to view LED status results. You can view the LED results on the Dual Test Results Display (see Figure 21).

Figure 21 — LED results for SDH and 140M

You can also view selected LED status results on the LED panel (see Figure 22).



Figure 22 — LED panel

The description of the status of key signals and conditions are described in Table 10.

Table 10 — LED panel

LED Condition

Signal Signal status and history

Pattern Sync Pattern Sync status and history

Fr Sync (SDH) STM-N frame synchronization status and history

Concat AU-4 Concatenation status

MS AIS MS-AIS status and history

MS RDI MS-RDI status and history


Viewing the event log

Viewing the event log

The Event Log results collects events from any number of applications in the system from predefined triggers (see “Selecting physical triggers” on page 26), and can store up to 500 events. As the results are placed into the event log, time stamps are added and event specific data is stored. After the event log is full, the next request to store information in the buffer wraps and overwrites enough entries to store the new request.

To view the event log

1 Press Category Selection button and select Misc. > Event Log.

AU LOP AU-4 LOP status and history

AU AIS AU-4 AIS status and history

HP RDI VC-4 RDI status and history

TU LOP TU-N LOP status and history

TU AIS TU-N AIS status and history

LP RDI VC-3 or VC-12 RDI status and history as applicable

Fr Sync (PDH) Frame sync status and history at the PDH rate

140 Alarm E4 AIS or RDI status and history

45M Alarm DS3 AIS or RDI status and history

34M Alarm E3 AIS or RDI status and history

8M Alarm E2 AIS or RDI status and history

2M Alarm E1 AIS, R-AIS, MFAS AIS, TS-16 RDI status and history

User Reserved for future use

Table 10 — LED panel (continued)

LED Condition



The Event Log appears on the left window.

2 Press the Pause button to stop the display while the module collects data.

3 For details on an event, press the specific event on the list. Additional details for the event appear in the event window located above the event log heading.

4 Press the Data button to list all associated capture data on each event that caused the trigger event.

5 Press the Play button to return to normal state and allow the module to display new events.

6 To clear the event log, press the System button and select Clear Event Log.

NOTE:

An event marked by an asterisk (*) indicates that there is associated capture data for the event. If the event is not marked with (*), the Data button does not appear.


Chapter 8

8 Troubleshooting

This chapter describes how to identify and correct problems related to the module. Topics discussed in this chapter include the following:

“About troubleshooting” on page 116

“Solving problems” on page 116


Chapter 8 — Troubleshooting

About troubleshooting

If you experience problems using the module, you may be able to solve these problems on your own after referring to this section. If you experience significant problems with the module, call the Technical Assistance Center (see “Getting technical assistance” on page xx).

Solving problems

The following section describes common problems that you may encounter while using the module. Before getting technical assistance, verify that you have exhausted all possibilities.

Installing and setup The following questions may be asked about installing and setting up the module.

Question The unit will not power up. Why?

Answer There are several reasons why the unit may not be powering.

Check the power source and restart the unit.

– If the unit is running on the AC power adapter, verify that the power source is adequate.

– If the unit is running on the battery, verify that there is enough battery charge.

The unit must have 25 percent or more battery power to charge up the unit for the first time with a new test pad.

Check to see that the unit is locked between the test pad and the application module. The unit will not power up if the module is not properly assembled.

The module is operable only with Rev 3 test pads manufactured as of March 2001 (serial number A25000 and greater). No


Solving problems

damage will occur in the event that you plug the 2416 application module into an older test pad (Rev 1 or 2). A warning window appears upon power up.

“This Application Module is only compatible with the TestPad 2000 Rev 3 and above or Serial Number A25000 and above.”

Question How do I configure the module for another language?

Answer See “Setting the language” on page 7 to configure the module for another language.

Before you can configure the module for another language, you must install the desired language from a PCMCIA card if it is not already installed.

Operating the module

The following questions may be asked about operating and performing basic functions on the module.

Question I cannot print test results. Why?

Answer Verify that the printer cable is properly connected to the module. For instructions to connect the printer to the module, refer to “Connecting the printer” on page 10.

NOTE:

The label on the back of the test pad identifies the version of the Test-Pad. All test pads that are returned for service and do not have a revi-sion sticker, will have a revision sticker added to the back of the UIM to indicate the following:

Rev 2 — Test pads manufactured and sold prior to March 2001

Rev 3 — Test pads manufactured after March 2001


Chapter 8 — Troubleshooting

Verify that the parameters in the Printer Management > Settings window are properly set for the printer or PC.

Verify that the printer is turned on and that it is loaded with paper.

Performing tests The following questions may be asked about completing tests on the module.

Question I am getting inconsistent test results. Why?

Answer Verify that your test connectors are set up properly according to the test being run. For information about using the connectors, refer to “Connecting the unit for testing” on page 33. This is the primary reason for inconsistent test results.

Verify that the correct timing source is selected in the Structure setup tab.

Verify that the correct line interface is selected.

Verify that the correct mapping, tributaries, and analysis rates are selected.

Question Why are the result values blank?

Answer Results are blank if gating criteria has not been met. Criteria examples include Signal Present, Frame Sync Present, Pointer Present, and BERT Pattern Sync Present.


Chapter 9

9 Customer Services

This chapter describes the customer services available through Acterna. Topics discussed in this chapter include the following:

“About our services” on page 120

“Customer service locations” on page 120

“Instrument services” on page 120

“Consulting Services” on page 121

“Test systems field engineering and installation” on page 122

“Technical training” on page 123

“Warranty information” on page 124

“Equipment return instructions” on page 126


Chapter 9 — Customer Services

About our services

Acterna offers unmatched services to support purchased equipment, including a wide range of customer care, technical support (see “Getting technical assistance” on page xx), instrument maintenance, and training services. Acterna customer service specialists are fully trained to help customers find the answers they are looking for. Call Customer Services for the following:

Information on products and services, including upgrades, calibration, training, software enhancement agreements (SEAs), and product maintenance agreements. Our representatives can also provide assistance with product returns and repairs.

Expert technical support, including help with product configuration, circuit qualification, and complete network trouble sectionalization. Acterna is also available on a contractual basis to provide customized application development, network consulting and management services, software customization, and test procedure development.

Warranty periods and other specific conditions are according to the sales conditions for this product.

Customer service locations

For questions regarding Acterna products and services, including return authorizations and repairs, technical support (see “Getting technical assistance” on page xx), training, and all other available services, contact your local distributor or Acterna Customer Service.

Instrument services

To maintain your organization’s long-term investment, Acterna will structure a service plan to fit your network performance goals and budget. Acterna understands the impact of equipment down time on


Consulting Services

operations and is staffed to ensure a quick turnaround. Available services include the following:

Product Repair — All equipment returned for service is tested to the same rigorous standards as newly manufactured equipment. This ensures products meet all published specifications, including any applicable product updates.

Calibration — Acterna’s calibration methods are ISO 9001 approved and based on NIST standards. Each calibration comes with a dated certificate, instrument stickers, and a data sheet.

Factory Upgrades — Any unit returned for a hardware feature enhancement will also receive applicable product updates and will be thoroughly tested, ensuring peak performance of the complete feature set.

Software Enhancement Agreements — These agreements assist in keeping equipment up to date with the latest software features, by providing automatic notification of any new software enhancements and changes for Acterna products.

Product Maintenance Agreements — Yearly service and calibration maintenance agreements simplify billing and help ensure the equipment is always operating at optimum levels. Product maintenance agreements can be used to extend a current warranty or provide protection for out-of-warranty units.

Other Pricing Options — For out-of-warranty repairs, Acterna offers two additional pricing options: time and material pricing and flat rate pricing. Under time and material pricing, customers are billed for the actual cost of the repair, making this a cost-effective method for minor repairs. Under flat rate pricing, customers pay a fixed service charge to repair unit failures (excluding damage or abuse), resulting in simplified paperwork and easier budgeting.

Consulting Services

The Product Enhancement Group offers one of the broadest and most experienced resource portfolios in the communications testing



industry. This team of professionals offers expertise in software development, test procedure development, and network consulting, as well as years of expert test knowledge. Support is available for all core Acterna product lines:

Network Consulting and Management — Provides services such as productivity analysis, test strategy assessment, on-site applications assistance, and specialized training.

Software Customization — Develops scripts for remote and automated testing, statistics, and emulation.

Test Procedure Development — Creates procedures for automated testing, network testing, and compliance testing.

Test systems field engineering and installation

Acterna offers a range of support services for our centralized test systems, designed around the needs of the customer’s network. These services help preserve the investment over the life of the equipment. Available services include the following:

Critical Services Program — Provides technical support at any time, 7 days a week, 24 hours a day. Replacement parts are guaranteed to arrive within 48 hours of contacting Acterna.

Maintenance Contracts — Cost-effective management for networks with multiple test systems.

Out-of-Warranty Service Agreement — Covers the test system for failures after the warranty expires, including all time and material costs and return shipping costs to the customer site.

Field Engineering and Installation Service — Provides a variety of options for implementing the test system into the network, including installation, configuration, upgrades, and on-site technical support.


Technical training

Technical training

By providing both experienced instructors and a hands-on atmosphere, Acterna training is designed to optimize test strategies and employee development requirements. Available services include the following:

Customized Technical Training — Designed to incorporate real-life challenges technicians face daily, while addressing the customer’s training requirements, Acterna provides training at the customer’s designated site, so the whole staff is trained at one time. Step-by-step reviews of current technologies and products enable new or experienced technicians to translate theory into practical, hands-on expertise.

Public Courses — Regularly scheduled, in-depth, hands-on product and technology courses are offered worldwide. Public courses provide a learning environment that allows individuals from different companies to share their knowledge and experience with their peers.

Computer-Based Training (CBT) — Acterna’s CBT complements our hands-on technical training. With CBT, customers can learn about emerging communications technologies at their own convenience — at work, at home, or while traveling. Acterna’s CBT courses cover technology topics such as ATM, frame relay, ISDN, LAN basics, and more.

Customized Multimedia Course Development — Multimedia courseware can be created to customer specifications, making it easier to learn new test instruments or applications. These custom packages provide consistent educational content and training for the entire staff. Students learn at their own pace on their own PC.

Consulting and Needs Analysis Services — Acterna can help identify training needs and develop customized training curricula to maximize learning opportunities, all while providing a measurable return on investment.



Warranty information

The warranties described herein shall apply to all commercially available Acterna products. Any additional or different warranties shall apply only if agreed to by Acterna in writing. These warranties are not transferable without the express written consent of Acterna.

Hardware Warranty — Acterna warrants that Hardware Product sold to customer shall, under normal use and service, be free from defects in materials and workmanship. The warranty period and other specific conditions will be according to the sales conditions for this product. If installation services have been ordered, the warranty period shall begin on the earlier of (1) completion of installation, or (2) thirty (30) days after shipment to Customer. If Installation Services have not been ordered, the warranty period shall begin upon shipment to Customer. Hereafter these periods of time shall be collectively referred to as the “Initial Warranty Period.”

Acterna’s obligation and customer’s sole remedy under this Hardware Warranty is limited to the repair or replacement, at Acterna’s option, of the defective product. Acterna shall have no obligation to remedy any such defect if it can be shown: (a) that the Product was altered, repaired, or reworked by any party other than Acterna without Acterna’s written consent; (b) that such defects were the result of customer’s improper storage, mishandling, abuse, or misuse of Product; (c) that such defects were the result of customer’s use of Product in conjunction with equipment electronically or mechanically incompatible or of an inferior quality; or (d) that the defect was the result of damage by fire, explosion, power failure, or any act of nature.

Acterna warrants that Products returned to Acterna for repair shall be warranted from defective materials and workmanship for one (1) year for the same repair issue, and ninety (90) days for a different repair issue from date of shipment from Acterna to customer, or until the end of the Initial Warranty Period, whichever is longer. Risk of loss or damage to Product returned to Acterna for repair or replacement shall be borne by customer until delivery to Acterna. Upon delivery of such product, Acterna


Warranty information

shall assume the risk of loss or damage until that time that the product being repaired or replaced is returned and delivered to customer. Customer shall pay all transportation costs for equipment or software shipped to Acterna for repair or replacement. Acterna shall pay all transportation costs associated with returning repaired or replaced product to customer.

Software Warranty — Acterna warrants that Software Products licensed to Customer shall, under normal use and service, and for a period of ninety (90) days from the date of shipment of the Software to Licensee (the “Warranty Period”), perform in all material respects in accordance with the published specifications for such Software as established by Acterna. However, Acterna does not warrant that the Software will operate uninterrupted or error free, operate in the combination with other software, meet Customer’s requirements, or that its use will be uninterrupted.

Acterna’s obligation and Customer’s sole and exclusive remedy under this Software Warranty is limited to, at Acterna’s option, either (i) correcting the material errors reported to Acterna in writing by Customer during the Warranty Period and which Acterna is able to reproduce, (ii) replacing such defective Software, provided that Acterna received written notice of such defect within the Warranty Period, or (iii) provided that Acterna received written notice of such defect within the Warranty Period, terminating the License and, upon return to Acterna of the Software, Documentation and all other materials provided by Acterna under the applicable License, providing Customer with a refund of all charges paid with respect thereto. Acterna shall have no warranty obligations hereunder if (a) the Software is altered or modified or is merged with other software by Customer or any third party or (b) all or any part of the Software is installed on any computer equipment other than the Designated Server or used with any operating system for which the Software is not designed.

Services Warranty — Acterna warrants that the Services provided by Acterna, if any, shall be performed promptly, diligently and in a professional manner in accordance with the commercial standards of the industry. Acterna shall not, however, be responsible for any delays that are not due to Acterna’s fault or



negligence or that could not have reasonably been foreseen or provided against.

WARRANTY DISCLAIMER — FOR HARDWARE, SOFTWARE, AND/OR SERVICES FURNISHED BY ACTERNA, THE FOREGOING WARRANTEES ARE IN LIEU OF ALL OTHER WARRANTEES AND CONDITIONS, EXPRESS OR IMPLIED. ACTERNA SPECIFICALLY DISCLAIMS ALL OTHER WARRANTIES, EITHER EXPRESS OR IMPLIED, ON ANY HARDWARE, SOFTWARE, DOCUMENTATION OR SERVICES INCLUDING BUT NOT LIMITED TO WARRANTIES RELATING TO QUALITY, PERFORMANCE, NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AS WELL AS THOSE ARISING FROM ANY COURSE OF DEALING, USAGE OR TRADE PRACTICE. UNDER NO CIRCUMSTANCES WILL ACTERNA BE LIABLE FOR ANY INDIRECT OR CONSEQUENTIAL DAMAGES RELATED TO BREACH OF THIS WARRANTY.

Equipment return instructions

For each piece of equipment returned for repair, attach a tag that includes the following information:

Owner’s name, address, and telephone number.

The serial number, product type, and model.

Warranty status. (If you are unsure of the warranty status of your instrument, contact Acterna Customer Service.)

A detailed description of the problem or service requested.

The name and telephone number of the person to contact regarding questions about the repair.

The return authorization (RA) number (US customers), or reference number (European Customers).

If possible, return the equipment using the original shipping container and material. If the original container is not available, the unit should be carefully packed so that it will not be damaged in transit; when needed, appropriate packing materials can be obtained by contacting Acterna Customer Services. Acterna is not liable for any damage that may occur during shipping. The customer should clearly mark the


Equipment return instructions

Acterna-issued RA or reference number on the outside of the package and ship it prepaid and insured to Acterna.

Appendix A

2416 SDH Fields Service ModuleUser’s Guide 129

A Specifications

The purpose of this appendix is to describe the environment and operating specifications for the module. The topics discussed in this appendix include the following:

“About the specifications” on page 130

“Physical specifications” on page 130

“Environmental specifications” on page 130

“Electrical specifications” on page 131

“Network interface connectors” on page 131

“PDH specifications” on page 132

“SDH specifications” on page 136

“Results display specifications” on page 141

2416 SDH Fields Service Module130 User’s Guide

Appendix A — Specifications

About the specifications

The following sections describe the physical, environmental, and electrical specifications, as well as PDH and SDH specifications.

Physical specifications

Table 11 lists the physical specifications of the module.

Environmental specifications

Table 12 lists the environmental specifications of the module.

Table 11 — Physical specifications

Parameter Specification

Height 7.5 inches / 19 cm

Width 11.5 inches / 29.2 cm

Depth 2.25 inches / 5.7 cm

Weight 5 lbs / 2.5 Kg

Display Color TFTscreen: 6.4 inchesResolution: 640 x 480 pixels (VGA standard)

PCMCIA Types I & II

Table 12 — Environmental specifications


Operating Temperature

32 to 104F0 to 40 C

Storage Temperature

-4 to 158 F-20 to 70 C


Electrical specifications

Electrical specifications

Table 13 lists the electrical specifications of the module.

Network interface connectors

The network interface connectors are as follows:

Reference Clock BNC 2.048 Mbp/s E1 or 2.048 MHz square

E1 balanced Transmit Twin-Ax

E1 balanced Receive Twin-Ax

E1, E3, DS3 Unbalanced Receive BNC

E1, E3, DS3 Unbalanced Transmit BNC

E4, STM-1e Unbalanced Receive BNC

E4, STM-1e Unbalanced Transmit BNC

STM-1, STM-4, STM-16 Receive Optical

Relative Humidity

10 to 90% RH, non-condensing

Table 12 — Environmental specifications (continued)


Table 13 — Electrical specifications


Battery Type 10.8 V Nickel-Metal-Hydride (NiMH)

Operating Time 25 minutes nominal battery life at room temperature

Recharging Time

2 hour maximum while unit is off.4 hour maximum while unit is on

AC adapter 50 to 60 Hz100 to 120 / 200 to 240 VAC



STM-1, STM-4, STM-16 Transmit High Power Optical 1310nm

STM-1, STM-4, STM-16 Transmit High Power Optical 1550nm

The module comes equipped with two Lemosa Twin-ax cables.

PDH specifications

Output signals Table 14 lists the PDH output signal specifications.

Table 14 — PDH output signals


Rates 75 Ω Ω Ω Ω unbalanced output, BNC: 2M, 34M, 45M, 140M

120 Ω Ω Ω Ω balance output, Twin-Ax: 2M

Line codes 2M & 34M: HDB3, AMI45M: B3ZS140M: CMI

Internal clock generation (at all rates)

4.6 ppm over 3 years

Clock sync to external signals (via 75 Ω unbalanced input, BNC)

Reference Clock at 2.048 MHz, 2.048 Mbit/s, or from the Rx signal

Error Injection PDH: Code, BIT, Frame (FAS, MFAS), CRC, Pattern Slip45M: Code, BIT, Frame, Parity, C-Bit Parity, Pattern Slip

Alarm Generation PDH: AIS, MFAS-AIS (2M), RDI, MFAS-RDI, LOF45M: AIS, RDI, LOF, Far End Alarm, Idle, FEBE

Test patterns (2M, 8M, 34M, 45M)

PRBS: 211-1, 215-1, 220-1, 223-1, 215-1 (inv), 220-1 (inv), 223-1 (inv), All Ones, All Zeros, 1:1, 1:3, 1:4, 1:7, AutoProgrammable: User Programmable (up to 32 bits)


PDH specifications

Input signals Table 15 describes the PDH input signal specifications.

Test Patterns (140M) 223-1, 223-1 (inv), 231-1, 231-1 (inv), Auto

Framing FAS, FAS CRC, MFAS, MFAS CRC, Unframed, C-Bit, M-13

Table 14 — PDH output signals (continued)


Table 15 — PDH input signals


Rates 75 Ω Ω Ω Ω unbalanced input, BNC: 2M, 34M, 45M, 140M

120 Ω Ω Ω Ω balance input, Twin-Ax: 2M

Line codes 2M & 34M: HDB3, AMI45M: B3ZS140M: CMI

Clock recovery pulling range

±100 ppm

Selectable Protected Monitor Point (PMP) gain

20, 23, 26, 30 dB resistive

Bridge mode Provides >10x the line impedance (for E1 interface only)

Cable loss range (Term) 2M: 0dB to -30dB34M, 45M, 140M: 0dB to -12dB 45M:0 to 900 feet from a high source, or 0 to 450 feet from a DSX source

Cable loss range (Monitor)

2M, 34M, 140M: 20, 23, 26, or 30 dB resistive loss plus 0dB to 6dB cable loss for 2M, and 0 to 12dB cable loss for 34M and 140M.45M: 22dB resistive loss plus 0 to 450 feet of cable loss.

Cable loss range (Bridge)

2M:0dB to -30dB, with the line terminated elsewhere.



Measurement types Table 16 describes the specification for PDH measurement types.

Table 16 — PDH measurement types


Error Measurement PDH: Code, Bit Error/TSE Count and Rate, CRC Error Count and Rate, REBE Count, FAS Bit Error Count and Rate, FAS Word Error Count and Rate, MFAS Word Error Count and Rate, FAS Sync Loss Count, MFAS Sync Loss Count, Pattern Slip Count and Seconds45M: Code, Bit Error/TSE Count and Rate, Frame Error Count, Rate and Seconds, Frame Sync Loss Count, Near End OOF Seconds, Far End OOF Seconds, Parity Error Count, Rate and Seconds, C-Bit Parity Error Count, Rate and Seconds, FEBE Count

Input Signal Measurement

For signals meeting G.703 criteria.

Frequency Measurement Range

+ / - 100 ppm

Alarm Detection PDH: LOS, LOF, AIS, TS-16 AIS, TS-16 RDI, RDI, Loss of Pattern Sync45M: LOS, LOF, C-Bit Parity Error, RDI, AIS, Far End Alarm, Idle, Loss of Pattern Sync

Measurement interval Continuous or Timed

Round Trip Delay 2M, 8M, 34M, 45M: 1µ to 10 seconds.

Evaluation to ITU-T Recommendation G.821

ES, EFS, SES, DM, UAS

The SES and DM thresholds are user-defined


PDH specifications


EB, BBE, ES, EFS, SES, and UAS

The SES Error Block threshold is user-defined.

Simultaneous in-service measurement of near end of a selected path: FAS at 140/34/8 or 2 Mbits/s, CRC-4, 45M Parity, 45M Frame Bit Errors

Anomalies evaluated include 2M FAS, 8M FAS, 34M FAS, 140M FAS, CRC-4, 45M Parity Errors, 45M Frame Errors. Defects evaluated include LOS, AIS, and Frame Sync Loss

Out of service measurement adds the use of bit errors in the test pattern for PDH.

Evaluation of PDH to ITU-T Recommendation M.2100

ES, EFS, SES, and UAS

Simultaneous in-service measurement of near end of a selected path: Anomalies evaluated include 2MFAS, 8M FAS, 34MFAS, 140MFAS, CRC-4, 45M Parity Errors, 45M Frame Errors. Defects evaluated include LOS, AIS, and Frame Sync Loss

Out of service measurement adds the use of bit errors in the test pattern for PDH.

Table 16 — PDH measurement types (continued)




SDH specifications

Output signals Table 17 lists the specifications for the SDH output signals. See Figure 23 on page 137 for a diagram of the SDH Mapping structure.

Table 17 — SDH output signals


Rates STM-16, STM-4, STM-1

The generation of STM-4 or STM-16 TX signals consist of one internally generated STM-1 tributary signal with the remaining tributaries filled with Unequipped.

Line Codes STM-1e: CMISTM-1/4/16: NRZ

Wavelength 1310 nm, 1310 & 1550 nm (switchable)

Output Level 1310 nm or 1550 nm:High Pwr: +2.0 to -4.3 dBm

Mappings VC-4-16c, VC-4-4c, VC-4, VC-3 (E3), VC-3 (DS3), VC-12

Synchronization Internal, Recovered, 2M Reference Clock

Error Injection VC-4: B1, B2 parity errors, FAS, MS-REI, VC-4 B3, VC-4 REI, BIT errors/TSE, code errorsVC-12 additionally: VC-12 BIP2, VC-12 REIVC-3 additionally: VC-3 B3, VC-3 REI

Alarm Generation VC-4: LOS, LOF, MS-AIS, MS-RDI, AU-LOP, AU-AIS, VC-4 RDIVC-12: TU-12 LOP, TU-12 AIS, VC-12 RDI, VC-12 RFIVC-3: TU-3 LOP, TU-3 AIS, VC-3 RDI

Trace Identifier J0, J1, J2: programmable 16 byte ASCII sequence with CRCJ1, J2 additionally: programmable 64 byte ASCII sequenceJ0, J2 additionally: single Byte Hexidecimal


SDH specifications

Figure 23 illustrates the SDH mapping structure,

Figure 23 — Mapping structure

Test Patterns 223-1, 231-1, 223-1(inv), 231-1 (inv), Auto

APS Switchover Time Measured on a PDH drop for linear and ring-mode, 1 ms accuracy.

Pointer Control Increment, Decrement, NDF

Table 17 — SDH output signals (continued)




Input signals Table 18 list the SDH input signal specifications.

Measurement types Table 19 lists the SDH measurement type specifications.

Table 18 — SDH input signals


Rates Optical: STM-1o, STM-4, STM-1675 Ω Ω Ω Ω unbalanced input, BNC: STM-1e

Line Codes STM-1e: CMISTM-1/4/16: NRZ

Clock recovery pulling range

± 100 ppm

Input Sensitivity -8.0 to -28.0 dBm

Input overload protection > -6 dBm

Selectable Protected Monitor Point (PMP) gain (STM-1e)

20, 23, 26, 30 dB resistive

Cable loss range (Term) STM-1e: 0dB to -12dB

Cable loss range (Monitor)

STM-1e: 20, 23, 26, or 30 dB resistive loss plus 0dB to 12dB cable loss.

Table 19 — SDH measurement types


APS Time Criteria for measurement: Loss of frame sync at analysis rate.

Max. measurable switch-over time: 127 msResolution: 1 ms


SDH specifications

Error Measurement B1 Error Count and Rate, B2 Error Count and Rate, Bit Error/TSE Count and Rate, FAS Word Error Count and Rate, OOF Count, LOF Count, MS REI Count and Rate, AU-LOP Count, VC-4REI Count and Rate, TU-12LOP Count, VC-12REI Count and Rate, CMI Code Error Count and Rate, Slip Count, VC-3 REI Count and Rate TU-3 LOP Count, VC-4 B3 Error Count and Rate, VC-12 BIP2 Error Count and Rate

Frequency Measurement Range

+ / - 100 ppm

Input Signal Measurement

Optical: for signals meeting G.957 criteriaElectrical: for signals meeting G.703 criteria.

Alarm Detection LOS, OOF, LOF, MS-AIS, MS-RDI, AU-AIS, AU-LOP, VC-4 RDI, TU-3 AIS, TU-3 LOP, VC-3 RDI, TU-12 AIS, TU-12 LOP, TU-12 LOM, VC-12 RDI, VC-12 RFI,

All alarms are evaluated and displayed in parallel

Measurement Interval Continuous and Timed

Pointer Analysis of AU and TU pointer action: Increment, Decrement, Pointer Value, NDF, and PJE

SOH and POH Display of key SOH and POH bytes, including interpretation of APS information in K1 and K2, Sync Status in S1, and Signal Label in C2/V5.

Trace Identifier J0: display of 16 byte ASCII sequenceJ1, J2: display of 16 or 64 byte ASCII sequence


ES, EFS, SES, DM, UAS

The SES and DM thresholds are user-defined

Table 19 — SDH measurement types (continued)





EB, BBE, ES, EFS, SES, and UAS

The SES Error Block threshold is user-defined.

Anomalies evaluated include: B3, BIP2

Defects evaluated include: TU-12 LOP, TU-12 LOM, TU-12 AIS, TU-3 LOP, TU-3 AIS, VC3 UNEQUIPPED, AUN LOP, AUN AIS, VC4 UNEQUIPPED.

Out-of-service measurement adds the use of bit errors in the test pattern for SDH.

Evaluation to ITU-T Recommendation M.2101

ES, EFS, SES, and UAS

Simultaneous in-service measurement of near end of a selected path.

Anomalies evaluated include: B1, BIP2

Defects evaluated include: TU-12 LOP, TU-12 LOM, TU-12 AIS, TU-3 LOP, TU-3 AIS, VC3 UNEQUIPPED, AUN LOP, AUN AIS, VC4 UNEQUIPPED.

Out of service measurement adds the use of bit errors in the test pattern for SDH.

Table 19 — SDH measurement types (continued)



Results display specifications

Results display specifications

Table 20 lists the specification for results display.

Table 20 — Results display specifications


Event Log Display of all alarm and error events with time stamp.

Resolution of error events and pointers: 50 msMemory capacity: 500 lines

Numerical Display Display of count (absolute) and rate (relative) values for all error types.

Display update rate: 1 second

Histogram Print Print errors, pointer operations / values and alarms as bar graphs vs. time

Units, time axis: 1 to 1440 minutes

Result printout Manual triggered or timed print

Serial: V.24 / RS 232

Result Export Results can be stored on a PCMCIA card in ASCII format


Appendix B

B Remote Control Commands

This appendix describes command lines for your application. The topics discussed in this appendix include the following:

“About using the remote control” on page 144

“Command syntax” on page 144

“Configuration commands” on page 145

“Result commands” on page 156


Appendix B — Remote Control Commands

About using the remote control

Using a serial port to serial port cable, you can set up and control the module through an RS-232-compatible device.

To use the remote control

1 Connect from the serial port on the RS-232-compatible device, such as a PC, to the printer port on the module using a standard reversing cable.

The module defaults to remote control operation. The unit knows when a printer is connected.

2 Set the communications on the PC to the following:

Baud Rate = 9600

Data bits = 8

Parity = none

Stop bits = 1

These settings should match the settings on the module.

Command syntax

The following information describes the syntax and commands used to configure the module for remote control operation (system configurations and results). The tables are organized by application or result category.

NOTE:

If you change the communications settings for the remote control fea-ture, you also change the printer settings because they share the same port.

NOTE:

When remote control operation is anticipated, the local user must exit all setup tabs or the remote user will be unable to change system set-tings.


Configuration commands

The syntax for using the configuration commands is as follows:CONFIG:APPLICATION:RC-NAME(space)VALUE

APPLICATION can be one of the following: SYSTEM, 2M, 34M, 45M, 140M, STM_E, STM_O, HS_BERT, PERF

For example, the set the BERT pattern type to INVERT, the commands would be:

CONFIG:BERT:PATTERN_TYPE INVERT

Result commands Scripts use the following syntax for results:RESULT:APPLICATION:PATH:RC_NAME?

APPLICATION can be any one of the following: 2M, 34M, 45M, 140M, STM_E, STM_O, BERT, HS_BERT, PDH, SDH or PERF

INTFC can be any one of the following: 2M, 8M, 34M, 45M, 140M, LP, HP, or MS.

SERVICE can be ISM or OOS.

BLOCKTYPE can be any of the following: FAS, CRC, PARITY, BERT

Sample command:RESULT:2M:RX1:ABSOLUTE_SLIP_COUNT?

Configuration commands

Configuration commands are used to configure the test being performed.



System configuration commands

Table 21 lists the system configuration commands.

Table 21 — System configuration commands

Command Syntax

Analysis Rate CONFIG:SYSTEM:ANALYSIS_RATE [selection]

NX64, 2M, 8M, 34M, 45M, 140M, BULK.

APS Switchover Time Enable CONFIG:SYSTEM:APS_SWITCH_TIME_ENABLE [ON, OFF]

Error Rate CONFIG:SYSTEM:ERROR_RATE [SINGLE, 1_00E_X (x=2..10)]

Error Type CONFIG:SYSTEM:ERROR_TYPE [selection]

2M_CODE_ERROR, 2M_CRC_ERROR, 2M_FAS_ERROR, 2M_MFAS_ERROR, 8M_FAS_ERROR, 34M_CODE_ERROR, 34M_FAS_ERROR, BIT_ERROR,PATTERN_SLIP, 140M_CODE_ERROR, 140M_FAS_ERROR, 45M_CODE_ERROR, 45M_FRAMING_ERROR, 45M_PARITY_ERROR, 45M_CBIT_PARITY_ERROR, SDH_CODE_ERROR, SDH_FRAMING_ERROR, B1_ERROR, B2_ERROR, VC12_BIP2_ERROR, SDH_MS_REI, VC4_REI, VC3_REI, VC12_REI, VC3_B3_ERROR, VC4_B3_ERROR

Framing CONFIG:SYSTEM:FRAMING [FRAMED, UNFRAMED]

Frame Error Insertion Count CONFIG:SYSTEM:FRAME_ERROR_INSERTION_COUNT [selection]

SINGLE, TWO, THREE, FOUR, CONSECUTIVE, CONTINUOUS, OOF, LOF

G.821 SES Threshold CONFIG:SYSTEM:G821SES_THRESHOLD [1E_2, 1E_3, 1E_4, 1E_5]

G.821 DM Threshold CONFIG:SYSTEM:G821DM_THRESHOLD [1E-4, 1E-5, 1E-6, 1E-7]

G.821 ES MUX Factor CONFIG:SYSTEM:G821MUX_FACTOR [ON, OFF]

G.826 SES Errored Block Threshold

CONFIG:SYSTEM:G826SES_ERR_BLOCK_THRESHOLD [selection]

Range is 1 to 100%

Consecutive Frame Error Count

CONFIG:SYSTEM:CONSECUTIVE_FRAME_ERROR_COUNT [selection]

Range is 2 to 31

Insert Error CONFIG:SYSTEM:INSERT_ERROR [ON, OFF]


BERT configuration commands

Table 22 lists the BERT configuration commands.

Interface CONFIG:SYSTEM:INTERFACE [selection]

2M, 34M, 45M, 140M, STM1_E, STM1_O, STM4, STM16, MUX

Laser Control CONFIG:SYSTEM:LASER_CONTROL [ON, OFF]

Laser Select CONFIG:SYSTEM:LASER_SELECT [1310_NM, 1550_NM]

MUX Receive Interface CONFIG:SYSTEM:MUX_RX_INTERFACE [selection]

2M, 34M, 45M, 140M, STM1_E, STM1_O, STM4, STM16

MUX Transmit Interface CONFIG:SYSTEM:MUX_TX_INTERFACE [selection]

2M, 34M, 45M, 140M, STM1_E, STM1_O, STM4, STM16

Protection Reset CONFIG:SYSTEM:RX_PROTECT_RESET [ON]

Timed Test CONFIG:SYSTEM:TIMED_TEST [ON, OFF]

Timed Test Length CONFIG:SYSTEM:TIMED_TEST_LENGTH [selection]

Range is 1 to 71999 minutes

Transmit Mode CONFIG:SYSTEM:MODE [TERMINATE, THRU]

Transmit Timing CONFIG:SYSTEM:TX_TIMING [INTERNAL, RECOVERED, EXT_DATA, EXT_CLOCK]

Table 21 — System configuration commands (continued)

Command Syntax

Table 22 — BERT configuration commands

Command Syntax

Pattern CONFIG:BERT:PATTERN [selection]

ALL_ONES, ALL_ZEROS, 1_1,1_3, 1_4, 1_7, 2_11, 2_15, 2_20, 2_23, 2_31, PROG, DELAY, AUTO

Pattern Type CONFIG:BERT:PATTERN [NORMAL, INVERT]



2M configuration commands

Table 23 lists the 2M configuration commands.

Programmable Pattern CONFIG:BERT:PROG_PATTERN

Range is 3 to 32 “0” or “1” characters

Table 22 — BERT configuration commands (continued)

Command Syntax

Table 23 — 2M configuration commands

Command Syntax

ABCD bits for Idle CAS Channels

CONFIG:2M:MFAS_IDLE [selection]

Range is 0001 to 1111 binary value

AIS Insertion CONFIG:2M:AIS [ON, OFF]

APS Switch Measurement CONFIG:2M:APS_SWITCH_TIME [ON, OFF]

Framing CONFIG:2M:FRAMING [selection]

UNFRAMED, FAS, FAS_CRC, MFAS, MFAS_CRC, AUTO

Idle Byte CONFIG:2M:IDLE_BYTE

Range is o to 255

Input Termination CONFIG:2M:RX_INPUT [TERM, BRIDGE, MONITOR]

Line Coding CONFIG:2M:LINE_CODING [AMI, HDB3]

MFAS AIS Insertion CONFIG:2M:TS16_AIS [ON, OFF]

Monitor Attenuation CONFIG:2M:RX_MON_ATTEN [selection]

20_DB, 23_DB, 26_DB, 30_DB

Nx64 RX Data Channel Map CONFIG:2M:RX_CHANNEL_MAP [selection]

Range is 31 “0” or “1” characters




Nx64 Tx Data Channel Map CONFIG:2M:TX_CHANNEL_MAP [selection]

Range is 31 “0” or “1” characters

RDI CONFIG:2M:FAS_DISTANT [ON, OFF]

REBE Insertion CONFIG:2M:REBE ON, OFF]

Sa(n) Bit CONFIG:2M:[selection] [ON, OFF]

SA4_BIT, SA5_BIT, SA6_BIT, SA7_BIT, SA8_BIT

Si Bit CONFIG:2M:SI_BIT [0, 1]

Transmit Line Build Out CONFIG:2M:TX_LBO [0_DB, 6_DB, 12_DB]

TS-16 RDI CONFIG:2M:MFAS_DISTANT [ON, OFF]

Table 23 — 2M configuration commands (continued)

Command Syntax


Command Syntax


Frame National Bit CONFIG:8M:NATIONAL_BIT [0, 1]

Frame Rx Tributary CONFIG:8M:RX_TRIB [1, 2, 3, 4]

Frame Tx Tributary CONFIG:8M:TX_TRIB [1, 2, 3, 4]

RDI Insertion CONFIG:8M:REMOTE_ALARM [ON, OFF]






Table 26 lists the 45M configuration commands


Command Syntax



Input Termination CONFIG:34M:RX_INPUT [TERM, MONITOR]

Line Coding CONFIG:34M:LINE_CODING [AMI, HDB3]

Frame National Bit CONFIG:34M:NATIONAL_BIT [0, 1]



20_DB, 23_DB, 26_DB, 30_DB


Transmit Line Build Out CONFIG:34M:TX_LBO [0_DB, 6_DB, 12_DB]



Command Syntax



Far-End Alarm Insertion CONFIG:45M:FAR_END_ALARM [selection]

OFF, DS3_EQUIP_FAILURE_SA, DS3_LOS, DS3_OOF, DS3_AIS, DS3_IDLE, DS3_EQUIP_FAILURE_NSA, COMMON_EQUIP_FAILURE_NSA

FEBE Insertion CONFIG:45M:FEBE [ON, OFF]




Framing CONFIG:45M:FRAMING [UNFRAMED, M13, CBIT]

Idle Channel CONFIG:45M:IDLE_CHANNEL [ON, OFF]


RDI Insertion CONFIG:45M:RAIS [ON, OFF]

Transmit Line Build Out CONFIG:45M:TX_LBO [HIGH, DSX, LOW]

Table 26 — 45M configuration commands (continued)

Command Syntax


Command Syntax







20_DB, 23_DB, 26_DB, 30_DB

National Bit CONFIG:140M:NATIONAL_BIT [selection]

Range is 000 to 111 binary value




SDH configuration commands

Table 28 lists the SDH configuration commands.

Table 28 — SDH configuration commands

Command Syntax

Alarm Insertion CONFIG:SDH:ALARM_INSERTION [ON, OFF]

Alarm Type CONFIG:SDH:ALARM_TYPE [selection]

MS_AIS, MS_RDI, AU_AIS, AU_LOP, VC4_RDI, TU3_AIS, TU3_LOP, VC3_RDI, TU12_AIS, TU12_LOP, VC12_RDI, VC12_RFI

AU4 Pointer Value CONFIG:SDH:AU4_POINTER_VALUE [selection]

Range is 0 to 782

Change Pointer CONFIG:SDH:CHANGE_POINTER ON

MS APS K1 Channel Number CONFIG:SDH:MS_APS_LIN_K1_CHANNEL_NUMBER[selection]

NULL_CHANNEL, WORKING_CHANNEL_1, WORKING_CHANNEL_2, WORKING_CHANNEL_3, WORKING_CHANNEL_4, WORKING_CHANNEL_5, WORKING_CHANNEL_6, WORKING_CHANNEL_7, WORKING_CHANNEL_8, WORKING_CHANNEL_9, WORKING_CHANNEL_10, WORKING_CHANNEL_11, WORKING_CHANNEL_12, WORKING_CHANNEL_13, WORKING_CHANNEL_14, EXTRA_TRAFFIC_CHANNEL

MS APS K2 Channel Number CONFIG:SDH:MS_APS_LIN_K2_CHANNEL_NUMBER[selection]

NULL_CHANNEL, WORKING_CHANNEL_1, WORKING_CHANNEL_2, WORKING_CHANNEL_3, WORKING_CHANNEL_4, WORKING_CHANNEL_5, WORKING_CHANNEL_6, WORKING_CHANNEL_7, WORKING_CHANNEL_8, WORKING_CHANNEL_9, WORKING_CHANNEL_10, WORKING_CHANNEL_11, WORKING_CHANNEL_12, WORKING_CHANNEL_13, WORKING_CHANNEL_14, EXTRA_TRAFFIC_CHANNEL

MS APS MSP Architecture CONFIG:SDH:MS_APS_LIN_MSP_ARCH [ONE_PLUS_ONE, ONE_TO_N]

MS APS MSP Line Status CONFIG:SDH:MS_APS_LIN_STATUS [selection]

RESERVED_000, RESERVED_001, RESERVED_010, RESERVED_011, RESERVED_100, RESERVED_101, MS_RDI, MS_AIS


MS APS Request Code CONFIG:SDH:MS_APS_LIN_REQUEST_CODE [selection]

LOCKOUT_OF_PROTECTION_LP, FORCED_SWITCH_FS, SIGNAL_FAIL_HIGH_PRIORITY_SF_H, SIGNAL_FAIL_LOW_PRIORITY_SF_L, SIGNAL_DEGRADE_HIGH_PRIORITY_SD_H, SIGNAL_DEGRADE_SD_L, UNUSED_1001, MANUAL_SWITCH_MS, UNUSED_0111, WAIT_TO_RESTORE_WTR, UNUSED_0101, EXERCISE_EXER, UNUSED_0011, REVERSE_REQUEST_RR, DO_NOT_REVERT_DNR, NO_REQUEST_NR

MS APS Bridge Request Code

CONFIG:SDH:MS_APS_RING_BRIDGE_REQUEST_CODE [selection]

LOCKOUT_LP_S, FORCED_SWITCH_SPAN_FS_S, FORCED_SWITCH_RING_FS_R, SIGNAL_FAIL_SPAN_SF_S, SIGNAL_FAIL_RING_SF_R, SIGNAL_DEGRADE_PROTECTION_SD_P, SIGNAL_DEGRADE_SPAN_SD_S, SIGNAL_DEGRADE_RING_SD_R, MANUAL_SWITCH_SPAN_MS_S, MANUAL_SWITCH_RING_MS_R, WAIT_TO_RESTORE_WT_R, EXERCISER_SPAN_EXER_S, EXERCISER_RING_EXER_R, REVERSE_REQUEST_SPAN_RR_S, REVERSE_REQUEST_RING_RR_R, NO_REQUEST_NR

MS APS Destination Node ID CONFIG:SDH:MS_APS_RING_DESTINATION_NODE_ID [selection]

Range is 0 to 15

MS APS Path Code CONFIG:SDH:MS_APS_RING_PATH_CODE [LONG, SHORT]

MS APS Source Node ID CONFIG:SDH:MS_APS_RING_SOURCE_NODE_ID [selection]

Range is 0 to 15

MS APS Ring Status CONFIG:SDH:MS_APS_RING_STATUS [selection]

IDLE, BRIDGED_BR, BRIDGED_AND_SWITCHED_BR_SW, RESERVED_011, RESERVED_100, RESERVED_101, MS_RDI, MS_AIS

MS APS Topology CONFIG:SDH:MS_APS_TOPOLOGY [LINEAR, RING]

Pointer Movement Type CONFIG:SDH:POINTER_MOVEMENT_TYPE [INCREMENT, DECREMENT, NDF]

Pointer Type CONFIG:SDH:POINTER_TYPE [AU4, TU3, TU12]

Table 28 — SDH configuration commands (continued)

Command Syntax



Rx Channel CONFIG:SDH:RX_TRIB_STM_N [selection]

STM-4: Range is 1 to 4STM-16: Range is 1 to 16

Rx Structure CONFIG:SDH:RX_MAPPING [VC4, VC3, VC12, VC_4_4C, VC_4_16C]

TUG-2 Rx Channel CONFIG:SDH:RX_TRIB_TUG2 [1, 2, 3, 4, 5, 6, 7]

TUG-3 Rx Channel CONFIG:SDH:RX_TRIB_TUG3 [1, 2, 3]

TU-12 Rx Channel CONFIG:SDH:RX_TRIB_TU12 [1, 2, 3]

Section Trace Format CONFIG:SDH:SECTION_TRACE_FORMAT [16_CRC, C1]

Section Trace String CONFIG:SDH:SECTION_TRACE_STRING [selection]

Range is 0 to 15 characters

Synchronization Status CONFIG:SDH:SOH_SYNC_STATUS [selection]

QUALITY_UNKNOWN, RESERVED_1, REC_G811, RESERVED_2, REC_G812_TRANSIT, RESERVED_3, RESERVED_4, RESERVED_5, REC_G812_LOCAL, RESERVED_6, RESERVED_7, SYNCHRONOUS_EQUIPMENT_TIMING_SOURCE_SETS, RESERVED_8, RESERVED_9, RESERVED_10, DO_NOT_USE_FOR_SYNCHRONIZATION

TU-3 Pointer Value CONFIG:SDH:TU3_POINTER_VALUE [selection]

Range is 0 to 764

TU-12 Pointer Value CONFIG:SDH:TU12:POINTER_VALUE [selection]

Range is 0 to 139

TUG-2 Tx Channel CONFIG:SDH:TX_TRIB_TUG2 [1, 2, 3, 4, 5, 6, 7]

TUG-3 Tx Channel CONFIG:SDH:TX_TRIB_TUG3 [1, 2, 3]

TU-12 Tx Channel CONFIG:SDH:TX_TRIB_TU12 [1, 2, 3]

Tx Channel CONFIG:SDH:TX:TRIB_STM_N [selection]

STM-4: Range is 1 to 4STM-16: Range is 1 to 16


Command Syntax


Tx Structure CONFIG:SDH:TX_MAPPING [VC4, VC3, VC12, VC_4_4C, VC_4_16C]

VC-3 Path Trace Format CONFIG:SDH:VC3_PATH_TRACE_FORMAT [16_CRC, 64_BYTE]

VC-3 Path Trace String (16) CONFIG:SDH:VC3_PATH_TRACE_STRING_16 [selection]

Range is 0 to 15 (characters)



VC-3 Path Trace Terminator CONFIG:SDH:VC3_PATH_TRACE_TERMINATOR [CR, LF, CR_LF]

VC-3 Signal Label CONFIG:SDH:VC3_SIGNAL_LABEL [selection]

UNEQUIPPED, EQUIPPED_NON_SPECIFIC, ASYNC_E3_DS3

VC-4 Path Trace Format CONFIG:SDH:VC4_PATH_TRACE_FORMAT [16_CRC, 64_BYTE]





VC-4 Path Trace Terminator CONFIG:SDH:VC3_PATH_TRACE_TERMINATOR [CR, LF, CR_LF]

VC-4 Signal Label CONFIG:SDH:VC4_SIGNAL_LABEL [selection]

UNEQUIPPED, EQUIPPED_NON_SPECIFIC, TUG_STRUCTURE, ASYNC_E3_DS3, ASYNC_E4

VC-12 J2 Clear Channel Value

CONFIG:SDH:VC12_J2_CLEAR_CHANNEL_VALUE [selection]

Range is 0 - 255

VC-12 Path Trace Format CONFIG:SDH:VC12_PATH_TRACE_FORMAT [16_CRC, CLEAR_CHANNEL]

VC-12 Path Trace String CONFIG:SDH:VC12_PATH_TRACE_STRING [selection]



Command Syntax



STM1_E configuration commands

Table 29 lists the STM_1E configuration commands.

Result commands

Result commands are used to query the remote test unit for a specific result.

Signal result commands

Table 30 lists the Signal result commands.

VC-12 Signal Label xCONFIG:SDH:VC12_SIGNAL_LABEL [selection]

ASYNC, BYTE_SYNC, UNEQUIP, EQUIP_NON_SPECIFIC


Command Syntax

Table 29 — STM_1E configuration commands

Command Syntax

Input Termination CONFIG:STM1_E:RX_INPUT [TERM, MONITOR]

Monitor Attenuation CONFIG:STM1_E:RX_MON_ATTEN [selection]

20_DB, 23_DB, 26_DB, 30_DB

Table 30 — Signal result commands

Command Syntax

APS Switchover Time RESULT:[APPLICATION]:RX1:APS_SWITCHOVER_TIME?

Electrical Input Level RESULT:[APPLICATION]:RX1:RECEIVE_LEVEL?

External Reference Frequency

RESULT:[APPLICATION]:RX1:EXT_REF_FREQUENCY?


LED result commands

Table 31 lists the LED result commands.

Code Error Count RESULT:[APPLICATION]:RX1:CODE_ERROR_COUNT?

Code Error Rate RESULT:[APPLICATION]:RX1:CODE_ERROR_RATE?

Receive Frequency RESULT:[APPLICATION]:RX1:RECEIVE_FREQUENCY?

Receive Frequency Deviation RESULT:[APPLICATION]RX1:RECEIVE_FREQUENCY_PPM?

Receive Frequency Maximum Deviation

RESULT:[APPLICATION]:RX1:MAX_RECEIVE_FREQUENCY_DEV_PPM?

Receive Level 1310nm RESULT:STM_O:RX1:RECEIVE_LEVEL_1310NM_O?

Receive Level 1550nm RESULT:STM_O:RX1:RECEIVE_LEVEL_1550NM_O?

Signal Loss Count RESULT:[APPLICATION]:RX1:SIGNAL_PRESENT.LOSS_COUNT?

Transmit Frequency RESULT:[APPLICATION]:RX1:TRANSMIT_FREQUENCY?

Table 30 — Signal result commands (continued)

Command Syntax

Table 31 — LED result commands

Command Syntax

2M AIS LED RESULT:2M:RX1:AIS_PRESENT?

2M CRC Sync RESULT:2M:RX1:CRC_SYNC?

2M FAS Distant Alarm RESULT:2M:RX1:FAS_DISTANT_ALARM?

2M FAS Sync RESULT:2M:RX1:FAS_SYNC?

2M MFAS Distant Alarm RESULT:2M:RX1:MFAS_DISTANT_ALARM?

2M MFAS Sync RESULT:2M:RX1:MFAS_SYNC?

45M Far End Alarm RESULT:45M:RX1:FAR_END_ALARM?

45M Idle Signal RESULT:45M:RX1:IDLE_SIGNAL?

AIS RESULT:[APPLICATION]:RX1:AIS?

8M, 34M, 45M, and 140M



Alarm RESULT:[APPLICATION]:RX1:ALARM?

AU4 Concatenation RESULT:STM_0:RX1:AU4_CONCAT_INDICATION?

AU4 LOP RESULT:[APPLICATION]:RX1:AU4_LOP?

AU AIS LED RESULT:[APPLICATION]:RX1:AU4_AIS?

Frame Sync RESULT:[APPLICATION]:RX1:FRAME_SYNC?

8M, 34M, 45M, 140M

MS AIS RESULT:[APPLICATION]:RX1:MS_AIS?

MS RDI RESULT:[APPLICATION]:RX1:MS_RDI?

Pattern Synchronization RESULT:[APPLICATION]:RX1:PATTERN_SYNC?

BERT, HS_BERT

Remote Alarm RESULT:[APPLICATION]:RX1:REMOTE_ALARM?

8M, 34M, 45M, 140M

Rx Protection Trip RESULT:STM_O:RX1:RX_PROTECT_TRIP?

Signal Present RESULT:[APPLICATION]:RX1:SIGNAL_PRESENT?

STM-N LOF RESULT:[APPLICATION]:RX1:LOF?

STM-N LP RDI RESULT:[APPLICATION]:RX1:LP_RDI?

STM-N OOF RESULT:[APPLICATION]:RX1:OOF?

Time Slot 16 AIS RESULT:2M:RX1:MFAS_AIS?

TU-12 AIS RESULT:[APPLICATION]:RX1:TU12_AIS?

TU-12 LOM RESULT:[APPLICATION]:RX1:TU12_LOM?

TU-12 LOP RESULT:[APPLICATION]:RX1:TU12_LOP?

TU-3 AIS RESULT:[APPLICATION]:RX1:TU3_AIS?

TU-3 LOP RESULT:[APPLICATION]:RX1:TU3_LOP?

TU AIS RESULT:[APPLICATION]:RX1:TU_AIS?

Table 31 — LED result commands (continued)

Command Syntax


PDH frame result commands

Table 32 lists the PDH Frame result commands.

TU LOP RESULT:[APPLICATION]:RX1:TU_LOP?

VC-12 RDI RESULT:[APPLICATION]:RX1:VC12_RDI?

VC-12 RFI RESULT:[APPLICATION]:RX1:VC12_RFI?



Table 31 — LED result commands (continued)

Command Syntax

Table 32 — PDH frame result commands

Command Syntax

2M CRC Error Count RESULT:2M:RX1:CRC_ERROR_COUNT?

2M CRC Error Rate RESULT:2M:RX1:CRC_ERROR_RATE?

2M CRC Sync Loss Count RESULT:2M:RX1:CRC_SYNC.LOSS_COUNT?

2M FAS Sync Loss Count RESULT:2M:RX1:FAS_SYNC.LOSS_COUNT?

2M MFAS Word Error Count RESULT:2M:RX1:MFAS_ERROR_COUNT?

2M MFAS Word Error Rate RESULT:2M:RX1:MFAS_ERROR_RATE?

2M MFAS Sync Loss Count RESULT:2M:RX1:MFAS_SYNC.LOSS_COUNT?

2M Non-Frame Alignment Word

RESULT:2M:RX1:NFAS_WORD?

2M Remote End Block Error (REBE)

RESULT:2M:RX1:REBE_COUNT?

45M C-Bit Parity Error Count RESULT:45M:RX1:C_BIT_ERROR_COUNT?

45M C-Bit Parity Error Rate RESULT:45M:RX1:C_BIT_ERROR_RATE?

45M C-Bit Error Seconds RESULT:45M:RX1:C_BIT_ERROR_SECS?

45M C-Bit Format RESULT:45M:RX1:C_BIT_FORMAT?



45M Far End Out of Frame Seconds

RESULT:45M:RX1:FAR_END_OOF_SECS?

45M FEAC Word RESULT:45M:RX1:FEAC_WORD?

45M FEBE Count RESULT:45M:RX1:FEBE_COUNT?

45M Frame Error Count RESULT:45M:RX1:FRAME_ERROR_COUNT?

45M Frame Error Rate RESULT:45M:RX1:FRAME_ERROR_RATE?

45M Frame Error Seconds RESULT:45M:RX1:FRAME_ERROR_SECS?

45M Near End Out of Frame Seconds

RESULT:45M:RX1:NEAR_END_OOF_SECS?

45M Parity Error Count RESULT:45M:RX1:PARITY_ERROR_COUNT?

45M Parity Error Rate RESULT:45M:RX1:PARITY_ERROR_RATE?

45M Parity Error Seconds RESULT:45M:RX1:PARITY_ERROR_SECS?

45M Rx X-Bits RESULT:45M:RX1:X_BITS?

FAS Bit Error Count RESULT:[APPLICATION]:RX1:FAS_BIT_ERROR_COUNT?

2M, 8M, 34M, 140M

FAS Bit Error Rate RESULT:[APPLICATION]:RX1:FAS_BIT_ERROR_RATE?

2M, 8M, 34M, 140M

FAS Word Error Count RESULT:[APPLICATION]:RX1:FAS_WORD_ERROR_COUNT?

2M, 8M, 34M, 140M

FAS Word Error Rate RESULT:[APPLICATION]:RX1:FAS_WORD_ERROR_RATE?

2M, 8M, 34M, 140M

Frame Sync Loss Count RESULT:[APPLICATION]:RX1:FRAME_SYNC.LOSS_COUNT?

8M, 34M, 45M, 140M

Table 32 — PDH frame result commands (continued)

Command Syntax


BERT result commands

Table 33 lists the BERT result commands.

Performance result commands

Table 34 lists the Performance result commands.

Table 33 — BERT Result Commands

Command Syntax

Auto Pattern Sync Status RESULT:[BERT_APP]:RX1:AUTO_PATTERN?

Bit Error Count RESULT:[BERT_APP]:RX1:BIT_ERRORS?

Bit Error Rate RESULT:[BERT_APP]:RX1:BIT_ERROR_RATE?

Pattern Slips RESULT:[BERT_APP]:RX1:PATTERN_SLIP?

Pattern Slip Seconds RESULT:[BERT_APP]:RX1:PATTERN_SLIP_SECONDS?

Pattern Sync Loss Count RESULT:[BERT_APP]:RX1:PATTERN_SYNC.LOSS_COUNT?

Pattern Sync Loss Seconds RESULT:[BERT_APP]:RX1:PATTERN_LOSS_SECS?

Round Trip Delay RESULT:BERT:RX1:ROUND_TRIP_DELAY?

Table 34 — Performance results commands

Command Syntax

G.821 Available Time RESULT:[BERT_APP]:RX1:G821_AVAILABLE_SECS?

G.821 Consecutive Severely Errored Seconds

RESULT:[BERT_APP]:RX1:G821_CONSEC_SEVERELY_ERRORED_SECS?

G.821 Degraded Minutes RESULT:[BERT_APP]:RX1:G821_DEGRADED_MINS?

G.821 Errored Seconds RESULT:[BERT_APP]:RX1:G821_ERRORED_SECS?

G.821 Error Free Seconds RESULT:[BERT_APP]:RX1:G821_ERROR_FREE_SECS?

G.821 Percent Available Time RESULT:[BERT_APP]:RX1:G821_PERCENT_AVAILABILITY?

G.821 Percent Degraded Minutes

RESULT:[BERT_APP]:RX1:G821_PERCENT_DEGRADED_MINS?



G.821 Percent Errored Seconds

RESULT:[BERT_APP]:RX1:G821_PERCENT_ERRORED_SECS?

G.821 Percent Severely Errored Seconds

RESULT:[BERT_APP]:RX1:G821_PERCENT_SEVERELY_ERRORED_SECS?

G.821 Severely Errored Seconds

RESULT:[BERT_APP]:RX1:G821_SEVERELY_ERRORED_SECS?

G.821 Unavailable Time RESULT:[BERT_APP]:RX1:G821_UNAVAILABLE_SECS?

G.826 Available Seconds RESULT:PERF:RX1:[INTFC]_[SERVICE]_G826_AVAILABLE_SECS?

G.826 Background Block Errors

RESULT:PERF:RX1:[INTFC]_[SERVICE]_[BLOCKTYPE]_G826_BACKGROUND_BLOCK_ERRORS?

G.826 Background Block Errors Rate

RESULT:PERF:RX1:[INTFC]_[SERVICE]_[BLOCKTYPE]_G826_BACKGROUND_BLOCK_ERRORS_RATE?

G.826 Blocks RESULT:PERF:RX1:[INTFC]_[SERVICE]_[BLOCKTYPE]_G826_BLOCKS?

G.826 Errored Blocks RESULT:PERF:RX1:[INTFC]_[SERVICE]_[BLOCKTYPE]_G826_ERRORED_BLOCKS?

G.826 Errored Seconds RESULT:PERF:RX1:[INTFC]_[SERVICE]_G826_ERRORED_SECS?

G.826 Errored Seconds Rate RESULT:PERF:RX1:[INTFC]_[SERVICE]_G826_ERRORED_SECS_RATE?

G.826 Severely Errored Seconds

RESULT:PERF:RX1:[INTFC]_[SERVICE]_G826_SEVERELY_ERRORED_SECS?

G.826 Severely Errored Seconds Rate

RESULT:PERF:RX1:[INTFC]_[SERVICE]_G826_SEVERELY_ERRORED_SECS_RATE?

G.826 Unavailable Seconds RESULT:PERF:RX1:[INTFC]_[SERVICE]_G826_UNAVAILABLE_SECS?

M.2100 Available Seconds RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2100_AVAILABLE_SECS?

M.2100 Available Seconds Rate

RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2100_AVAILABLE_SECS_RATE?

M.2100 Errored Seconds RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2100_ERRORED_SECS?

M.2100 Errored Seconds Rate

RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2100_ERRORED_SECS_RATE?

Table 34 — Performance results commands (continued)

Command Syntax


M.2100 Error Free Seconds RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2100_ERROR_FREE_SECS?

M.2100 Error Free Seconds Rate

RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2100_ERROR_FREE_SECS_RATE?

M.2100 Severely Errored Seconds

RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2100_SEVERELY_ERRORED_SECS?

For PDH rates, when [SERVICE] is ISM, [INTFC] can only be 2M, 8M, 34M, 45M, or 140M. When [SERVICE] is OOS, [INTFC] can only be PDH.

M.2100 Severely Errored Seconds Rate

RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2100_SEVERELY_ERRORED_SECS_RATE?

M.2100 Unavailable Seconds RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2100_UNAVAILABLE_SECS?

M.2100 Total Seconds RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2100_TOTAL_SECS?

M.2101.1 Available Seconds RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2101_1_AVAILABLE_SECS?

M.2101.1 Percent Available Seconds

RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2101_1_PERCENT_AVAILABLE_SECS?

M.2101.1 Errored Seconds RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2101_1_ERRORED_SECS?

M.2101.1 Error Free Seconds RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2101_1_ERROR_FREE_SECS?

M.2101.1 Percent Errored Seconds

RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2101_1_PERCENT_ERRORED_SECS?

M.2101.1 Percent Error Free Seconds

RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2101_1_PERCENT_ERROR_FREE_SECS?

M.2101.1 Percent Severely Errored Seconds

RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2101_1_PERCENT_SEVERELY_ERRORED_SECS?

M.2101.1 Severely Errors Seconds

RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2101_1_SEVERELY_ERRORED_SECS?

M.2101.1 Unavailable Seconds

RESULT:PERF:RX1:[INTFC]_[SERVICE]_M2101_1_UNAVAILABLE_SECS?

Table 34 — Performance results commands (continued)

Command Syntax



SOH result commands

Table 35 lists the SOH result commands.

Table 35 — SOH result commands

Command Syntax

B1 Error Count RESULT:[APPLICATION]:RX1:B1_ERROR_COUNT?

B1 Error Rate RESULT:[APPLICATION]:RX1:B1_ERROR_RATE?

B2 Error Count RESULT:[APPLICATION]:RX1:B2_ERROR_COUNT?

B2 Error Rate RESULT:[APPLICATION]:RX1:B2_ERROR_RATE?

FAS Word Error Count RESULT:[APPLICATION]:RX1:FAS_WORD_ERROR_COUNT?

FAS Word Error Rate RESULT:[APPLICATION]:RX1:FAS_WORD_ERROR_RATE?

LOF Count RESULT:[APPLICATION]:RX1:LOF.COUNT?

MS APS Bridge Request Code (Ring)

RESULT:[APPLICATION]:RX1:MS_APS_RING_BRIDGE_REQUEST_CODE?

MS APS Detination Node ID (Ring)

RESULT:[APPLICATION]:RX1:MS_APS_RING_DESTINATION_NODE_ID?

MS APS K1 Channel Number (Linear)

RESULT:[APPLICATION]:RX1:MS_APS_LIN_K1_CHANNEL_NUMBER?

MS APS K2 Channel Number (Linear)

RESULT:[APPLICATION]:RX1:MS_APS_LIN_K2_CHANNEL_NUMBER?

MS APS MSP Architecture (Linear)

RESULT:[APPLICATION]:RX1:MS_APS_LIN_MSP_ARCH?

MS APS Path Code (Ring) RESULT:[APPLICATION]:RX1:MS_APS_RING_PATH_CODE?

MS APS Request Code (Linear)

RESULT:[APPLICATION]:RX1:MS_APS_LIN_REQUEST_CODE?

MS APS Source Node ID (Ring)

RESULT:[APPLICATION]:RX1:MS_APS_RING_SOURCE_NODE_ID?

MS APS Status (Linear) RESULT:[APPLICATION]:RX1:MS_APS_LIN_STATUS?

MS APS Status (Ring) RESULT:[APPLICATION]:RX1:MS_APS_RING_STATUS?

MS REI Count RESULT:[APPLICATION]:RX1:MS_REI_COUNT?

MS REI Rate RESULT:[APPLICATION]:RX1:MS_REI_RATE?


HP result commands

Table 36 lists the HP result commands.

Section Trace RESULT:[APPLICATION]:RX1:SECTION_TRACE?

OOF Count RESULT:[APPLICATION]:RX1:OOF.COUNT?

Sync Status RESULT:[APPLICATION]:RX1:SYNC_STATUS?

Table 35 — SOH result commands (continued)

Command Syntax

Table 36 — HP result commands

Command Syntax

AU4 LOP Count RESULT:[APPLICATION]:RX1:AU4_LOP.COUNT?

AU4 NDF Count RESULT:[APPLICATION]:RX1:AU4_NDF_COUNT?

AU4 Pointer Decrement Count

RESULT:[APPLICATION]:RX1:AU4_PTR_DECREMENT_COUNT?

AU4 Pointer Increment Count RESULT:[APPLICATION]:RX1:AU4_PTR_INCREMENT_COUNT?

AU4 Pointer Justification Events

RESULT:[APPLICATION]:RX1:AU4_PTR_JUSTIFICATION_EVENT_COUNT?

AU4 Pointer Received RESULT:[APPLICATION]:RX1:AU4_PTR_RX?

AU4 Pointer Transmitted RESULT:[APPLICATION]:RX1:AU4_PTR_TX?

VC-4 Path Status RESULT:[APPLICATION]:RX1:VC4_G1?

VC-4 Path Trace Message RESULT:[APPLICATION]:RX1:VC4_PATH_TRACE?

VC-4 REI Count RESULT:[APPLICATION]:RX1:VC4_REI_COUNT?

VC-4 REI Rate RESULT:[APPLICATION]:RX1:VC4_REI_RATE?

VC-4 Signal Label RESULT:[APPLICATION]:RX1:VC4_SIGNAL_LABEL?



LP result commands Table 37 lists the LP result commands.

Table 37 — LP result commands

Command Syntax

TU-12 LOP Count RESULT:[APPLICATION]:RX1:TU12_LOP.COUNT?

TU-12 NDF Count RESULT:[APPLICATION]:RX1:TU12_NDF_COUNT?

TU-12 Pointer Decrement Count

RESULT:[APPLICATION]:RX1:TU12_PTR_DECREMENT_COUNT?

TU-12 Pointer Increment Count

RESULT:[APPLICATION]:RX1:TU12_PTR_INCREMENT_COUNT?

TU-12 Pointer Justification Event Count

RESULT:[APPLICATION]:RX1:TU12_PTR_JUSTIFICATION_EVENT_COUNT?

TU-12 Pointer Received RESULT:[APPLICATION]:RX1:TU12_PTR_RX?

TU-12 Pointer Transmitted RESULT:[APPLICATION]:RX1:TU12_PTR_TX?

TU-3 LOP Count RESULT:[APPLICATION]:RX1:TU3_LOP.COUNT?

TU-3 NDF Count RESULT:[APPLICATION]:RX1:TU3_NDF_COUNT?

TU-3 Pointer Decrement Count

RESULT:[APPLICATION]:RX1:TU3_PTR_DECREMENT_COUNT?

TU-3 Pointer Increment Count RESULT:[APPLICATION]:RX1:TU3_PTR_INCREMENT_COUNT?

TU-3 Pointer Justification Event Count

RESULT:[APPLICATION]:RX1:TU3_PTR_JUSTIFICATION_EVENT_COUNT?

TU-3 Pointer Received RESULT:[APPLICATION]:RX1:TU3_PTR_RX?

TU-3 Pointer Transmitted RESULT:[APPLICATION]:RX1:TU3_PTR_TX?

VC-12 BIP2 Error Count RESULT:[APPLICATION]:RX1:VC12_BIP2_ERROR_COUNT?

VC-12 BIP2 Error Rate RESULT:[APPLICATION]:RX1:VC12_BIP2_ERROR_RATE?

VC-12 Path Trace RESULT:[APPLICATION]:RX1:VC12_PATH_TRACE?

VC-12 POH (V5) RESULT:[APPLICATION]:RX1:VC12_POH_V5?




Misc. result commands

Table 38 lists the Miscellaneous result commands.


VC-3 B3 Error Count RESULT:[APPLICATION]:RX1:VC3_B3_ERROR_COUNT?

VC-3 B3 Error Rate RESULT:[APPLICATION]:RX1:VC3_B3_ERROR_RATE?

VC-3 Path Status RESULT:[APPLICATION]:RX1:VC3_G1?

VC-3 Path Trace Message RESULT:[APPLICATION]:RX1:VC3_PATH_TRACE?




Table 37 — LP result commands (continued)

Command Syntax

Table 38 — Miscellaneous result commands

Command Syntax

Date RESULT:SYSAPP::DATE?

Elapsed Time RESULT:SYSAPP::ELAPSED_TIME?

Power Loss Count RESULT:SYSAPP::PWR_FAIL_CNT?

Time RESULT:SYSAPP::TIME?

Time Slot ABCD Bits RESULT:2M:RX1:LINK_OVERVIEW:0.[0-31].CAS_BITS?

Time Slot Rx Byte RESULT:2M:RX1:LINK_OVERVIEW:0.[0-31].RX_BYTE?

Timed Test Remaining RESULT:SYSAPP::TEST_TIME_REMAINING?

Timed Test Time RESULT:SYSAPP::TOTAL_TEST_TIME?

169

Appendix C

C Field Descriptions

This appendix provides descriptions of the setup tabs and data field for test configuration.

170 SDH Module Field Descriptions

Appendix C — Field Descriptions

SDH Module Field Descrip-tions

140M Tab Define the receiver input signal compensation mode as Term or Monitor. Specify the National Bits and activate alarms for simulation.

2M Channels Tab (available for Nx64 only) Select the timeslots (1 to 31) to be analyzed. The receiver framer extracts the selected time slots and enables you to view the data in the 2M View window.

2M ABCD/Sa Tab Only available for framed payloads. Specify the MFAS idle bits, and the NFAS/FAS Word, Si bit, and Sa bits.

2M Tab Specify the framing, line code and the receiver input signal compensation mode. Also specify the line build out and idle bytes and activate alarms for simulation.

34M Tab Specify the receiver input signal compensation mode, line coding, national bit, and line build out. Activate alarms for simulation.

45M Tab Specify the framing, the receiver input signal compensation mode, and activate alarms for simulation.

8M Tab Specify the National Bit and activate alarms for simulation.

Alarm (PDH) The FAS and MFAS framing format provides several built-in alarms. This allows detection

and sectionalization of transmission line or equipment problems in a circuit. Specify ON or OFF for each.

AIS

Far End Alarm

RDI

FEBE

Idle Channel

TS-16 RDI

REBE

TS-16 AIS

2M, 8M, 34M, 45M, and 140M tabs

Alarm Insertion Specify the Alarm Type as ON or OFF.SDH tab

Alarm Type Specify the type of alarm to simulate.

MS-AIS — Multiplex Section Alarm Indication Signal.

MS-RDI — Multiplex Section Remote Defect Indication

AU-AIS —Administrative Unit Alarm Indication Signal.

AU-LOP — Administrative Unit Loss of Pointer.

VC-4 RDI — Virtual Container Remote Defect Indication



VC-12 RFI — Virtual Container Remote Failure Indication

TU-3 AIS — Tributary Unit Alarm Indication Signal.

SDH Module Field Descriptions 171


TU-3 LOP — Tributary Unit Loss of Pointer.

TU-12 AIS — Tributary Unit Alarm Indication Signal

TU-12 LOP — Tributary Unit Loss of Pointer

SDH tab

Analysis Rate Specify the analysis rate of the receiving payload.Structure tab for PDH and SDH.

BERT Tab Specify the pattern and the pattern type as normal or inverted. Or, program a user defined pattern.

Bridge Request Code (Ring) Part of K1 byte.MS APS tab

Channel Number (Linear) The first channel number is part of the K1 byte. The second channel number is part of the K2 byte.MS APS tab

Clear Channel Select Clear Channel as the path trace format. Enter the J2 Clear Channel value from 0 to 255.VC-12 POH tab

Consecutive Frame Errors (SDH Framing Error only) Specify the number of consecutive SDH Frame errors to generate.Error Insert tab

Destination Node ID (Ring) Part of K1 byteMS APS tab

Error Insert Tab Specify the type of error to generate and how it will be generated (rate, frame error count, and consecutive errors).

Error Insert Rate Select the error rate:

Single

1.00E-2

1.00E-3

1.00E-4

1.00E-5

1.00E-6

1.00E-7

1.00E-8

1.00E-9

Error Insert tab

Error Insert Type Select the type of error to generate.

B1 Error

B2 Error

Bit Error / TSE

C-Bit Parity

Code Error

CRC Error

FAS Error

Frame Error

MFAS Error

Parity Error

Pattern Slip

SDH Code Error



SDH Framing Error

SDH MS-REI

VC-3 B3

VC-3 REI

VC-12 BIP2

VC-12 REI

VC-4 B3 Error

VC-4 REI

Error Insert tab

Frame Error Count (Frame errors only) Specify how to generate the frame error. If “Consecutive” is selected, specify how many consecutive errors to generate.Error Insert tab

Framing Select the data to be framed or unframed.Structure tab for PDH and SDH

Framing (2M) Select one of the following framing options

FAS — Frame without CRC

FAS-CRC — Frame with CRC

MFAS — Multiframe without CRC

MFAS-CRC — Multiframe with CRC

2M tab

Framing (45M)

M13 — Every 4 DS1are grouped together into an intermediate DS2 channel, and the C-bits are used to indicate the presence or absence of stuffing.

C-Bit — The first C-bit in M-subframe 1 is always set to 1.

45M tab

G.821 DM Bit Error Threshold Specify the degraded minutes bit error threshold.Performance tab

G.821 ES MUX Factor Specify the errored second MUX factor as ON or OFF.Performance tab

G.821 SES Bit Error Threshold Specify the severely errored second bit error threshold.Performance tab

G.826 SES Errored Block Threshold Specify the severely errored second errored blocks threshold. Range is 1 to 100%.Performance tab

Idle Byte The idle byte is inserted on all unselected channels. Press the field and use the keypad to modify the idle byte based on equipment requirements.2M tab

Laser Select Specify the transmitting laser as 1310 nm 1550 nm. SDH tab

Line Coding Specify the line coding as follows: HDB3 — High Density Bipolar 3.

AMI — Alternate Mark Inversion

2M and 34M tabs



MFAS Idle Bits Specify ABCD Bits for IDLE MFAS subframes2M ABCD/SA tab

MS APS Tab Specify ring or linear network, and K1 and K2 contents.

MSP Architecture (Linear) Part of the K2 byte.MS APS tab

National Bits Bits reserved for national use.8M, 34M, and 140M tabs

Network Topology Specify whether the network is linear or a ring.MS APS tab

NFAS/FAS Word Set the value of each Sa bit. The value is transmitted repeatedly until new values are selected.2M ABCD/Sa tab

Path Code (Ring) Part of the K2 byte.MS APS tab

Path Trace Format Specify the format of the message being transmitted.

16-CRC — up to 15 characters. The module calculates the proper CRC value.

64-Byte — up to 63 bytes and 1 terminator.

Clear Channel

Any remaining bytes are filled with null characters.

VC-4, VC-3, and VC-12 POH tabs

Path Trace String Press on the field and use the keyboard to enter a message according to the format selected.VC-4, VC-3, and VC-12 POH tabs

Pattern Specify the pattern to transmit. All descriptions are for “normal” patterns where applicable.

All Ones — Selects a fixed ones pattern.

All Zeros — Selects a fixed zero pattern.

1:1— Alternating ones and zeroes (10101010) pattern.

1:3 — A one followed by three zeroes (10001000) pattern.

1:4 — A one followed by four zeroes (100001) pattern.

1:7 — A one followed by seven zeroes (100000001) pattern.

2^11-1—A maximum of 10 sequential zeroes and 11 sequential ones.

2^15-1—A maximum of 14 sequential ones and 15 sequential zeroes.

2^20-1— A maximum of 19 sequential zeroes and 20 sequential ones.

2^23-1—A maximum of 22 sequential zeroes and 23 sequential ones.

2^31-1—A maximum of 30 sequential ones and 31 sequential zeroes.



User Programmable — User selects a pattern from 3 to 32 bits long. The default is 01010101.

Auto — The test instrument attempts (at the start of each new test) to detect and synchronize to the received test pattern.

Delay — Test pattern used to perform round trip delay calculation.

BERT tab

Pattern Type Specify the pattern as normal or inverted.BERT tab

Performance Tab Specify the thresholds for G.821 SES bit error, G.821 DM bit error, and G.826 SES errored block. Also switch the G.821 ES MUX factor ON or OFF.

Physical Triggers Tab Select the categories for which to log trigger events.

Signal

Framing

Performance

Alarm

BERT

PDH APS (used to enable APS switchover measurement)

Pointer Type Select the pointer for manipulation (Increment, Decrement, NDF): AU-4 or TU-3.SDH tab

Prog. Pattern (User Programmable only) Enter a pattern from 3 to 32 bits long. Default is 01010101.BERT tab

Request Code (Linear) Part of the K1 byteMS APS tab

Rx Input Specify the receiver input signal compensation modes:

Monitor — In monitor mode, the receiver will terminate the signal, compensate the resistive attenuation suffered by the incoming signal, and also equalize cable loss.

Bridge — (2M only) Bridge mode is used to connect the module to E1 circuits during in-service tests whenever a resistor isolated access point is not available.

Term — In terminate mode, the connection is made to the end of the line. The received signal will be terminated and compensated for cable loss.

2M, 34M, 45M, 140M, and SDH tabs

Rx Mon Atten (Monitor only) Receive Monitor Attenuation. Compensates for 20dB, 23dB, 26dB, 30dB Protective Monitor Points (PMP) which vary from country to country. 2M, 34M, 140M, and SDH tabs

Rx Structure Tab Define the analysis rate, tributary selection, and framing when in MUX mode.



SDH Tab Specify the input signal compensation mode (in STM-1 E only), laser wavelength (optical only), and pointer type. Also activate alarms for simulation.

Section Trace Format Specify the format of the message being transmitted.

16-CRC - up to 15 characters. The module calculates the proper CRC value.

C1 - a value of 1 is transmitted in the J0 Byte.

SOH tab

Section Trace String (J0) Press on the field and use the keypad to enter a 15 byte trace string.SOH tab

Signal Label Specify the signal label value transmitted in the C2 byte (VC-3 and VC-4) or the V5 Byte (VC-12)VC-4, VC-3, and VC-12 POH tab

SOH Tab Specify contents of Section Overhead bytes S1 and J0.

Source Node ID (Ring) Part of the K2 byte.MS APS tab

Status (RIng and Linear) Part of the K2 byte.MS APS tab

Structure Tab (Term and Thru modes) Define the transmitting payload, such as mapping, framing,

analysis rate, Tx timing, and tributaries.

Sync Status Specify the value transmitted in the S1 byte of the Section Overhead.SOH tab

Timed Test Tab Check to box to enable a timed test and specify the test length (1 min. to 49d, 23h and 59 min.).

Trace Terminator Specify the terminator for a 64-Byte trace message:

CR

CR-LF

LF

VC-4 and VC-3 POH tabs

Tributary Selection The specified tributary is used to carry the data generated by the module.

2M — Select a tributary 1-4



STM -n — 1-16 (STM-16), 1-4 (STM-4)

TUG-3 — Select a tributary 1-3

TUG-2 — Select a tributary 1-7

TU-12 — Select a tributary 1-3

VC-12 — Select a tributary 1-63

A VC-12 tributary may be selected by either timeslot number (VC-12 1-63) or a three figure address (TUG-3, TUG-2, TU-12). The module automatically updates all fields to



maintain consistency between the two numbering schemes.Structure tab

Tx LBO (2M and 34M) Specify the level of cable loss:

0 dB

6 dB

12 dB

2M and 34M tab

Tx LBO 45M Specify the level of cable loss:

High

DSX

Low

45M tab

Tx Structure Tab Define the mapping and Tx timing when in MUX mode.

Tx Timing Specify the timing:

Internal

From Rx

Ext Data 1048 kbits/s

Ext Clock 2048kHz

Structure tab

VC-4, VC-3, VC-12 POH Tab Specify the format of the trace message and enter the message string. Specify the signal label.

VC Mapping Specify the Virtual Container on which to transmit the optical payload.

VC-4-16C

VC-4-4C

VC-4

VC-3

VC-12

Structure tab


Glossary

2M — A data stream of nominally 2,048,000 bits per second, the E1 rate.


45M — A data stream of nominally 44,736,000 bits per second, the DS3 rate.

140M — A data stream of nominal-ly 139,264,000 bits per second, the E4 rate..


A

AIS — Alarm Indication Signal. An AIS is a signal transmitted down-stream indicating that an up-stream failure has been detected.

AMI — Alternate Mark Inversion.

The line-coding format whereby successive ones (marks) are al-ternately inverted (sent with polar-ity opposite that of the preceding mark).

Analysis Rate — The bit rate of the data stream being analyzed by the BERT engine. The ana-lyzed data stream can be the full payload or a demultiplexed tribu-tary from the line interface signal.

Anomaly — The smallest discrep-ancy between the actual and de-sired characteristic of an item. The occurrence of an anomaly does not interrupt a function.

APS — Automatic Protection Sys-tem. A means of achieving net-work resiliency through switching devices which automatically switch from a primary circuit to a secondary circuit. This switching process would take place when the primary circuit fails or when the error rate on the primary ex-ceeds a set threshold.

1782416 SDH Field Service Module

User’s Guide

Glossary

AU — Administrative Unit.

B

B3ZS — Bipolar with 3-Zero Sub-stitution.

BER — Bit Error Rate. The ratio of error bits to the total number of bits transmitted. Bit Error Rate is a measurement of transmission quality.

BERT — Bit Error Rate Test. A known pattern of bits is transmit-ted, and errors received are counted to figure the BER. The Bit Error Rate test is used to measure transmission quality.

BIP — Bit Interleave Parity.

BPV — Bipolar Violation. The pres-ence of two consecutive ‘one’ bits of the same polarity on the E car-rier and T carrier line.

BNC — Bayonet Nut Connector. A round, push and twist to lock con-nector.

Bridge Mode — A high impedance tap into an E-1 or T-1 circuit (at a bridge point where no monitor point access is provided) that does not disrupt the existing com-munication line. See also Monitor Point.

C

Clear Channel — A circuit that re-quires no framing or control bits, thus the entire bandwidth is avail-able for communications.

CRC — Cyclic Redundancy Check. A process used to check the in-tegrity of a block of data. A CRC character is generated at the transmission end. Its value de-pends on the hexadecimal value of the number of ones in the data block. And it is added to the data block. The receiving end makes a similar calculation and compares the results with the added charac-ter.

D

dBdsx — 0 dBdsx is the level of a 44 736 kbit/s High level signal passing through 137.2 meters (450 feet) of 75 ohm coaxial cable terminated in a 75 ohm load.

Defects — The occurrence when the density of anomalies has reached a level where the ability to perform a function has been in-terrupted.

Demultiplex — DEMUX. To sepa-rate two or more signals previous-ly combined by compatible multiplexing equipment.

Demultiplexer — A device that pulls several streams of data out of a bigger stream of data.

DEMUX — See Demultiplex.

Destination Node — Those sys-tem nodes which receive mes-sages over the control packet network from the source or trans-mitting node.

DM — Degraded Minutes.


Glossary

DUT — Device Under Test.

E

E1 — See 2M.

E2 — See 8M

E3 — See 34M

E4 — See 140M

ERR — Error

ES — Errored Second.

ESR — Errored Second Ratio.

F

FAS — Frame Alignment Signal. The distinctive signal inserted in every frame or once in a number of frames that always occupies the same relative position within the frame and is used to establish and maintain frame alignment.

FEAC — Far End Alarm and Con-trol.

FC/PC — Face Contact and Point Contact. Designations for fiber optic connectors.

FEBE — Far End Block Error.

Freq — Frequency.

G

G.821 — Error performance of an international digital connection operating at a bit rate below the

primary rate and forming part of an integrated services digital net-work.

G.826 — Error performance pa-rameters and objectives for inter-national, constant bit rate digital paths at or above the primary rate.

H

HDB3 — High Density Bipolar 3. A bipolar coding method that does not allow more than three consec-utive zeros.

Histogram — A graph of contigu-ous vertical bars representing a frequency distribution in which groups or classes of items are marked at equal intervals in as-cending order on the x axis and the number of items in each class in indicated by a horizontal line segment drawn above the x axis at a height equal to the number of items in the class.

HP — High Order Path.

I

ISM — In-Service Monitoring.

ISO — International Organization for Standardization.

ITU — International Telecommuni-cations Union based on Geneva, Switzerland.


User’s Guide

Glossary

L

LCD — Liquid Crystal Display.

LED — Light Emitting Diode.

LBO — Electrical Line Build Out.

Line Coding — A line code is the waveform of voltage or current used to represent the 1s and 0s of a digital signal on a transmission link.Several different types of line coding can be used in PDH sys-tems to represent the same infor-mation in slightly different way.

Line Interface Rate — The bit rate of the signal being recovered by a line interface from a twisted pair, coaxial cable, or a fiber optic ca-ble. A data stream can be extract-ed from the line interface signal and routed to a BERT engine for analysis. The analyzed data stream can be the full payload or a demulitplexed tributary from the line interface signal.

LOF — Loss of Frame.

LOP — Loss of Pointer.

LP — Low Order Path.

Lvl — Level.

M

M.2100 — Performance limits for bringing-into-service of interna-tional PDH paths, sections and transmission systems

M.2101.1 — Performance limits for

bringing-into-service and mainte-nance of international SDH paths and multiplex sections.

M13 — The multiplexer equivalent of T-1. In the U.S. digital hierar-chy, multiplexers are called by the digital signal levels they interface with. For example, a multiplexer, which joins DS-1 channels to DS-3 is called a M1-3. A M1-3 takes 28 DS-1 inputs and combines them into a single 45 megabit per second stream.

Max — Maximum.

MFAS — Multiframe Alignment Signal.

Min — Minimum.

MON — Monitor.

MS — Multiplexer Section.

Multiplex — MUX. To transmit two or more signals over a single channel.

Multiplexer — Electronic equip-ment that allows two or more sig-nals to pass over one communication circuit.

MUX — See Multiplex.

N

Network Topology — The geo-metric arrangement of links and nodes of a network. The geogra-phy of a network.

NDF — New Data Flag.


Glossary

NFAS — Not- Frame Alignment Signal.

NIST — National Institute of Stan-dards and Technology

O

OOF — Out of Frame. An error in framing bits.

OOS — Out of Service Monitoring. The SDH module performs out of service monitoring at the currently selected analysis rate.

P

Payload Pointer — SDH provides payload pointers to permit differ-ences in the phase and frequency of the Virtual Containers (VC-N) with respect to the STM-N frame. Low order pointers are also pro-vided to permit phase differences between VC-1/VC-2 and the high-er order VC-3/VC-4.

PCMCIA — Personal Computer Memory Card International Asso-ciation. The PCMCIA standardiz-es credit-card size packages for memory and input/output for com-puters, laptops, palmtops, and more.

PDH — Plesiochronous Digital Hi-erarchy. Developed to carry digi-tized voice over twisted pair cabling more efficiently.

PJE — Pointer Justification Event.

PMP — Protective Monitor Point.

POH — Path Overhead. SDH over-head assigned to and transported with the payload until the payload is demultiplexed. It is used for functions that are necessary to transport the payload. These functions include parity check and trace capability.

PRBS — Pseudo-Random Bit Se-quence/pattern. A test pattern having the properties of random data, but generated in such a manner that another circuit, oper-ating independently, can synchro-nize on the pattern and detect individual transmission bit errors.

Ptr — Pointer.

R

RDI — Remote Defect Indication. An indication that a failure has oc-curred at the far end of a network.

REBE — Remote End Block Error (2M only)

Ref — Reference.

REI — Remote Error Indication.

Rx — Receive.

S

SDH — Synchronous Digital Hier-archy

SES — Severely Errored Second. A second in which a severe num-ber of errors are detected over a digital circuit.Each error compris-es a code violation.


User’s Guide

Glossary

SOH — Section Overhead

STM — Synchronous Transport Module. The information structure used to support section layer con-nections in the SDH.

STM1 — A data stream of nomi-nally 155,520,000 bits per second (155M).

STM-4 — A data stream of nomi-nally 622,080,000 bits per sec-ond, (622M).

STM-16 — A data stream of nomi-nally 2,488,320,000 bits per sec-ond (2.5G).

Sync — Synchronization.

T

Thru — Through Mode.

Tributary — The lower rate signal input to a multiplexer for combina-tion (multiplexing) with other low rate signals to form an aggregate higher rate signal.

TS-16 — Time Slot 16.

TSE — Test Sequence Error (bit error).

TU — Tributary Unit. The SDH equivalent of a Virtual Channel in SONET terminology.

TUG — Tributary Unit Group.

Tx — Transmit.

U

UIM — User Interface Module.

Unavail — Unavailable.

V

VC — Virtual Container.


Index

Numerics

2M timeslotsviewing, 46

A

Action buttons, 19

Alarmssimulating PDH, 54simulating SDH, 73

Application buttons, 18

APS switchover timeverifying, 59

Assembling the unit, 6

B

Batterymaintaining, 12recharging, 12replacing, 12

BERT testingPDH, 55SDH, 75

Bottom panel, 17

Buttonsaction, 19application, 18setup, 19

C

Calibrationinstrument service, 125

Commands, remote controlconfiguration, 147result, 158syntax, 146

Computer-Based Training (CBT)technical training, 127

Configuration commands, remote control

140M, 1532M, 15034M, 15245M, 1528M, 151BERT, 149SDH, 153STM1_E, 158system, 148

Index


Connectingthe printer, 10the unit for testing, 31

Consulting and Needs Analysis Services

technical training, 127

Copying files, 30

Critical Services Programtest systems field engineering

and installation, 126

Customer Service Locations, 124

Customized Multimedia Course Development

technical training, 127

Customized Technical Trainingcustomer services, 127

D

Deleting files, 30

E

Electrical Specifications, 135

Environmental specifications, 135

Equipment Return Instructionsservice and repair

information, 130

Errorsgenerating PDH, 52generating SDH, 72

Event logprinting a selected range, 42viewing, 116

F

Factory Upgradesinstrument service, 125

Features and capabilities, 2

Field Engineering and Installation Service

test systems field engineering and installation, 126

Files, configurationcopying, 30deleting, 30renaming, 30

Front panel, 17

H

Histogramsconfiguring, 26printing, 39

I

Iconssystem, 19

Informationwarranty, 128

Installationtest systems field engineering

and, 126

Installing options, 9

Instructionsequipment return, 130

Instrument Servicecustomer services, 124

L

Languagesetting, 7

Laser safety, 32

Loading test configurations, 29

Locationscustomer service, 124

Index


M

Maintenance Contractstest systems field engineering


Message display, 19

Modesoperating, 33

MUXmode, 34testing a multiplexer, 88

N

Navigating the user interface, 18

Network Consulting and Management

product enhancement group, 126

O

Operating modes, 33MUX, 34terminate, 33thru, 34

Optionsinstalling, 9

Other Pricing Optionsinstrument service, 125

Out-of-Warranty Service Agreementtest systems field engineering


P

PDHinput signals, 137measurement types, 138output signals, 136specifications, 136

PDH testsBERT, 55generating errors, 52identifying anomalies and

defects, 52monitoring network traffic, 57performance analysis, 47round trip delay, 50simulating alarms, 54verifying APS switchover time, 59

Performance analysisPDH, 47SDH, 70

Permanent softkeys, 21

Physical triggersselecting, 26

Pointer movementsanalyzing, 77

Powering the unit, 6

Printerconnecting, 10

Printinga selected range from the event

log, 42headings, 39histograms, 39selecting print type, 38standard categories, 39test results, 36to file, 37

Problemsresolving, 120

Product Enhancement Groupcustomer services, 126

Product Maintenance Agreementsinstrument service, 125

Product Repairinstrument service, 125

Public Coursestechnical training, 127

Index


R

Recharging the battery, 12

Remote controlcommand syntax, 146configuration commands, 147result commands, 158using, 44

Renaming files, 30

Replacing the battery, 12

Result commands, remote controlBERT, 162HP, 167LED, 159LP, 168Misc., 169PDH frame, 161performance, 163signal, 158SOH, 166

Results, interpretingBERT, 98HP, 109LED, 114LP, 111PDH frame, 100performance, 103signal, 96SOH, 107summary, 94

Return Instructionsequipment, 130

Round trip delay test, 50

S

Safetylaser, 32

Saving test configurations, 28

SDHinput signals, 142measurement types, 142output signals, 140specifications, 140

SDH testsanalyzing pointer movements, 77BERT testing, 75generating errors, 72identifying anomalies and

defects, 71identifying trace messages, 79performance analysis, 70simulating alarms, 73

Serviceinstrument, 124

Service Locationscustomer, 124

Setupassembling the unit, 6installing options, 9setting the language, 7

Setup button, 19

Softkeyspermanent, 21

Software Customizationproduct enhancement group, 126

Software Enhancement Agreementsinstrument service, 125

Specifications, 133electrical, 135environmental, 135PDH, 136physical, 134results display, 144SDH, 140

Summary bar, 19

Index


Systemconfiguring settings, 22icons, 19viewing information, 22

T

Technical Trainingcustomer services, 127

Terminate mode, 33

Test configurationsdeleting, 30loading, 29saving, 28

Test Procedure Developmentproduct enhancement group, 126

Test resultsinterpreting, 93printing, 36viewing, 35

Index


Test Systems Field Engineering and Installation

customer services, 126

Testsanalyzing pointer movements, 77configuring, 23connecting the unit for, 31generating PDH errors, 52generating SDH errors, 72identifying PDH anomalies and

defects, 52identifying SDH anomalies and

defects, 71identifying trace messages, 79monitoring network traffic, 57PDH BERT, 55PDH performance analysis, 47round trip delay, 50SDH BERT, 75SDH performance analysis, 70selecting physical triggers for, 26simulating PDH alarms, 54simulating SDH alarms, 73testing a multiplexer, 88timed, 25verifying APS switchover time, 59

Thru mode, 34

Timed printactivating, 37

Timed test, 25

Timeslotsviewing 2M, 46

Top panel, 16

Tourguided, 15

Trace messagesidentifying, 79

Trainingtechnical, 127

Triggersphysical, 26

Troubleshooting, 119

U

User interface, navigating, 18

W

Warranty Informationcustomer services, 128

2416 sdh field service module user’s guide

Documents