Digitest

Consumer Access Solutions
LoopCare Test OSS

Guide to Tollgrade Testheads
Revision Q
Release 2.15
December, 2006
040-0376
ELECTRONIC EMISSION NOTICE

Federal Communications Commission (FCC) Statement
Warning: The hardware provided with the LoopCare Testing System generates, uses, and can radiate radio
frequency energy and if not installed and used in accordance with the instruction manual, may cause interference to
radio communications. The hardware has been tested and found to comply with the limits for a Class A computing
device pursuant to Subpart J of Part 15 of FCC Rules. These rules are designed to provide reasonable protection
against such interference when the hardware is operated in a commercial environment. Operation of this equipment
in a residential area is likely to cause interference, in which case the users, at their own expense, will be required to
take whatever measures necessary to eliminate the interference.
NOTICE: Every effort has been made to ensure that the information in this manual is complete and accurate at the
time of printing. However, information is subject to change without notice.
LoopCare is a trademark of Tollgrade Communications, Inc.
DigiTest is a registered trademark of Tollgrade Communications, Inc.
EDGE is a trademark of Tollgrade Communications, Inc.
All other trademarks and copyrights are property of their respective owners.
All figures, screen images, results and diagrams contained in this manual are examples for reference purposes only.
Operational results may vary depending on the configuration of and conditions existing on your telecommunications
system.
This document contains proprietary information that shall be distributed or routed only within Tollgrade
Communications, Inc. and to its authorized clients, except with written permission of Tollgrade.
2006, Tollgrade Communications, Inc., All Rights Reserved

PROPRIETARY TOLLGRADE AND AUTHORIZED CLIENTS ONLY
Tollgrade Communications, Inc.

493 Nixon Road
Cheswick, PA 15024
Revision Q (p/n 040-0376)
Phone: 412-820-1400 0
Fax: 412-820-1530 3
Technical Support: 800-777-5405 o
412-820-1498 9
Orders: 412-820-1305 0
Web Site: www.tollgrade.com m
Release 2.15, December, 2006 ii
About this Guide
Introduction
vii
Organization of This Guide
viii
Conventions Used
ix
Related Documentation
Ordering Documentation
xi
DigiTest Components
1-2
Testing Modules
1-3
Digital Measurement Unit
1-4
Digital Measurement Unit Plus (DMU+)
1-5
Digital Wideband Unit
1-7
1-8
Wideband Transmission Module (WTM)
1-9
Modem Option Card
1-10
Ethernet DMU (E-DMU) Option Card
1-11
DigiTest Configurations
1-1
Introduction
Other Components
vii
2-1
Introduction
2-2
Digital Measurement Node (DMN)
2-3
DWU
2-5
Digital Wideband Node (DWN)
2-6
DigiTest Ethernet DMU (E-DMU)
2-9
The Expert Measurement Unit (EMU)
2-12
LoopCare Communications Gateway
2-13
DMU - CO and RT Applications
2-14
DMU Testing Capabilities
2-18
Deployment of the DWN
2-21
E-DMU - CO and RT Applications
2-22
Issue 2.15, December, 2006 -iii
EMU Installation
3-1
EMU Installation
3-3
Installation of EMU as CO Test Head
3-4
EMU as CO Test Head
3-4
Physical Installation of a DMU/DMU+ Test Head
3-5
DMU Internal Configuration
3-8
DMU+ Internal Configuration
3-13
Resetting the DMU/DMU+ after Entering Data
3-18
LoopCare Database Configuration
3-19
Installation of EMU as Central Office (CO) Wideband Test Head

EMU as Central Office (CO) Wideband Test Head
3-24
Physical DMU-W Test Head Installation
3-25
DMU-W Internal Configuration
3-28
Communication Port Configuration
3-31
Miscellaneous Setup
3-32
Resetting the DMU after Entering Data
3-34
LoopCare Database Configuration (ADEF)
3-35
Installation of a DMU as an RT Test Head
3-41
DMU as an RT Test Head
3-41
Physical DMU Test Head Installation at an RT
3-42
3-44
3-47
Configuring the DMU+
3-48
Configuring the DMU+ to Work with LoopCare
3-49
LoopCare DMU+ Database Configuration?
3-59
Identifying the RMU
3-68
Using an RMU to Test EAIU-supported Lines
3-69
Installation of a Standalone Remote Test Head
-iv
3-24
3-72
Standalone Remote Test Head
3-72
Physical DMU/DMU-W Installation at an LTE
3-73
DMU-R Internal Configuration
3-75
3-78
LoopCare DataBase Configuration
3-79
Associating a Standalone Remote Test Head with an LTE(s)
3-83
Issue 2.15, December, 2006
Installation of the DWN
3-84
DWN Deployment
3-84
DWN Administration
3-85
Installation Checklists
3-89
Overview
3-89
Equipment Checklist
3-90
Installation Activities Checklist
3-94
Reference Documents
3-97
EMU Administration
4-1
Introduction
4-3
Accessing the Tools
4-4
Introduction
4-4
The HADM Tool
4-5
HADM through the dial Utility
4-6
HADM through the nodial Utility
4-8
HADM through Craft Port Access
4-10
EMUadmin, RMUadmin and RMU-Sadmin Access
4-11
DZadmin Access
4-12
Access LoopCare SAM Interface
4-13
Accessing DMU Diagnostics
4-14
Administrative Tools
4-15
Introduction
4-15
Human Administration Interface (HADM)
4-16
Administering a CO Testhead with EMUadmin
4-17
Display and Change Status
4-23
Reset a DMU
4-26
Administering an RT Testhead with RMUadmin Utility
4-27
Administering a Standalone RT Testhead with RMU-S admin Utility4-34
Administering through the DZadmin Utility
4-41
DZadmin Utility
4-42
Display the EMU/RMU Access Tables
4-43
Clear an EMU/RMU Access Table Entry
4-45
Issue 2.15, December, 2006 -v
Display the Virtual Channel Table
4-46
Display DDCMP Data for a Port
4-47
Set DDCMP Error Rate Thresholds for a Port
4-48
Display the Mapping Table
4-49
Install a New DZmaster
4-50
Change Port Status
4-51
Display Port Trouble Counters
4-52
Set Port Trouble Rate Thresholds
4-53
Enabling/Disabling EMU/RMU Access Retry
4-54
DZadmin Codes
4-55
System Administration Mask (SAM)
4-56
Throttling Sanity Tests on DMUs
4-60
4-60
Sanity Tests on DMUs via Modems
E-DMU Configuration
5-1
Introduction
5-2
Replacing Existing DMUs with an E-DMU Extnet
5-5
Initial Deployment of Master/Extenders in an Extnet
5-7
Serial Connection Between Master E-DMU and a Serial Device5-9

E-DMU Administration
-vi
DigiTest EDGE Components and Configurations
5-12
6-1
Introduction
6-2
DigiTest EDGE
6-3
DigiTest EDGE Components
6-5
DigiTest EDGE Installation and Configuration
7-1
Introduction
7-2
Test Access and Communication Properties
7-3
Configuring the EDGE to Work with LoopCare
7-10
Configuring LoopCare - System Configuration
7-24
Configuring LoopCare - ADEF Data Entry
7-27
Create an Access Server Record
7-28
Configure an EDGE as an RMU-S
7-32
Configure an LTE Connected to an EDGE
7-34
Routine Maintenance
7-40
Testing With the DigiTest EDGE
7-41
Complete Layer 1-7 Testing with a LiteSpan
7-47
HUB Installation and Configuration
8-1
Introduction
8-2
Physical Installation
8-3
Configuring and Setting Up the HUB
8-4
8-6
Issue 2.15, December, 2006 -vii
-viii
About this Guide
Introduction
Overview
This section describes the purpose and organization of this guide, the intended
audience, conventions used, and related documents.
Purpose
The LoopCareTM Test Operations Support System (LoopCare) Guide to Tollgrade

Testheads provides information on the components of the DigiTest testheads,
available configurations, and instructions for administering their features and
troubleshooting problems when they occur.
LoopCare is an automated test system that tests and analyzes Plain Old
Telephone Service (POTS), Digital Loop Carrier (DLC), and Integrated Services
Digital Network (ISDN) telephone lines and equipment in support of loop
maintenance operations.
Intended Audience
This guide is intended for the following LoopCare audience:
System administrators
Facilities managers
Repair technicians
Issue 2.15, December, 2006 -vii
Organization of This Guide

Overview
This guide is organized into four chapters:
About This Guide

Describes the purpose, intended audience, and organization of this guide,
and includes a complete list of related LoopCare user documentation.
Chapter 1, DigiTest Components

Describes the DigiTest hardware components that make up the testheads.
Chapter 2, DigiTest Configurations

Describes the configurations in which DigiTest components are delivered
as testheads.
Chapter 3, EMU Installation

Provides instructions for installing the EMU in the LoopCare environment
and for verifying that it is operating properly.
Chapter 4, EMU Administration

Provides instructions for using the EMUadmin utility to configure and
administer EMU options, procedures for accessing the EMU database, and
instructions for configuring modems to work with the EMU.
Chapter 5, E-DMU Configuration

Provides instructions for installing E-DMUs in the LoopCare environment.
Chapter 6, DigiTest EDGE Components and Configurations

Describes the DigiTest EDGE hardware components that make up the
testhead.
Chapter 7, DigiTest EDGE Installation and Configuration

Provides instructions for installing and configuring the DigiTest EDGE in the
LoopCare environmen
-viii
Conventions Used
Overview
The Following special typeface conventions are used in this guide:
Italic type is used to indicate variables and to reference chapters within this
guide or to related documents.
Bold type is used to show emphasis.
Courier is used to indicate screen displays.
Courier Bold is used to indicate what commands or keyboard

characters the user must enter to execute functions.
Courier Bold in all capitals indicates a keyboard key that must be

pressed to execute a function.
A note is used to indicate additional information, a reminder, or a clarification.

NOTE:
This symbol indicates a note.
Issue 2.15, December, 2006 -ix
Related Documentation
Overview
The complete LoopCare Testing System documentation set is listed and

described in the Documentation Installation Guide.
DigiTest System
Documentation
For information about DigiTest System hardware, refer to the documentation

provided with the hardware.
-x
Ordering Documentation
Overview
For copies of the LoopCare documents, contact your LoopCare Customer

Support Representative.
For copies of the DigiTest System documents, contact your DigiTest Customer
Support Representative.
Issue 2.15, December, 2006 -xi
-xii
DigiTest Components
Contents
Introduction
1-2
1-4
1-5
1-7
1-9
Modem Option Card
1-10
1-11
Loop Insertion Loss (LIL) Module
1-12
Issue 2.15, December, 2006 1-1
DigiTest Components
Introduction
Introduction
Overview
1-2
This chapter describes the components of the DigiTest System that are used to
provide test, communications, or administration/maintenance functions in a
LoopCare environment.
DigiTest Components
Introduction
Testing Modules
Overview
This section describes the DigiTest components that perform line tests.
DigiTest Components

Overview
The Digital Measurement Unit (DMU) is a single-port loop measurement device

that can be configured for either No Test or MDF trunk access in CO Testhead
mode. The DMU can also serve as a Remote Terminal (RT) testhead (see the
section on the DMU as Remote Testhead Application below). The DMU circuit
card has two LEDs (see section on LED below) and plugs into the DMN. There
can be two DMUs for each DMN.
Test Port
When the DMU is used as a CO testhead, it can be configured for either No Test
or MDF Access. The test port (DMU Connection Port 1) consists of three leads:
tip, ring, and sleeve. When the DMU is configured as an RT testhead tip and ring
will connect to the Test Access Port (TAP) of the DLCs RT equipment (the sleeve
lead will not be used).
Callback Line
To execute LoopCare interactive callback transactions, the DMU is configured to

connect to tip and ring of a POTS line. The DMU uses this POTS line to call the
tester callback number entered via the TV mask.
Light Emitting
Diodes (LEDs)
The DMU has two Light Emitting Diodes (LEDs).
Data LED - This LED is unlighted when there is no communication to the

DMU. It emits a green light when communication to the DMU is
established.
Status LED - This LED has three status colors, each reflecting one of three
different states:
Red. Indicates a fault or no service.
Green. Indicates normal functioning.
Yellow. Indicates that calibration is in progress.
1-4
DigiTest Components

Overview
The Tollgrade Digital Measurement Unit Plus (DMU+) is an enhanced version of

the currently deployed DMU. The DMU+ is compatible with all the features and
test requests currently supported by the DMU, Ethernet DMU (E-DMU), and
Extended Ethernet DMU (EE-DMU). Therefore, the DMU+ consolidates three
products into one. All features and functions available on the DMU will be
available on the DMU+. Unlike the E-DMU, which had the Ethernet hardware on a
daughter card, the DMU+ has incorporated this hardware on the main board.
Either a modem or Loop Insertion Loss daughter card can be installed on the
DMU+. When installing the DMU+ as a replacement of the DMU the user will not
have to perform any additional ADEF activity on LoopCare. The DMU+ will be
transparent to LoopCare.
LoopCare Release 2.8 includes the following enhancements for the DMU+.
Loop Insertion Loss

Measurement
Loop Insertion Loss Measurement
Date and Time Synchronization
Longitudinal Balance Measurement at 200 Hz
The Loop Insertion Loss Measurement feature (LIL) provides DSL loop
qualification using loop insertion loss measurements instead of loop length
measurements. It requires an optional LIL module on the DMU+. The LIL module
is a daughter card installed on the DMU+ capable of providing a Loop Insertion
Loss value which may be used to determine the data rate capacity for that circuit.
The LIL measurement is performed only by the QUALX request.
The LIL measurement feature is supported on a variety of Central Office and
Remote configurations:
Central Office EMU configurations using switch based NTT test trunks. The
user is required to perform loop insertion loss calibration of lines through
the switch.
DLC RMU and RMU-S testable lines or EAIU lines tested by a DMU-R.
Insertion loss calibration values are not required for these configurations.
To perform LIL measurements on DLC-based lines, the test architecture
must be an EMU-to-DMU-R test architecture, where the DMU-R is a DMU+
with the LIL module (DMU+L).
Loop insertion loss calibration is required for NTT trunk configurations. Depending
on the switch type, either a single calibration is used (e.g. DMS switch) or a
separate calibration must be done for each Line Unit type (e.g., 5ESS switch). If
multiple calibrations are required, then OE retrieval is used to identify which lines
are associated with each calibration value. Insertion loss calibration for one trunk
DigiTest Components
is sufficient for all trunks. There is no need to calibrate all trunks for a given OE
range.
If the speed bin feature is enabled, then DSL data rate prediction is based on the
insertion loss measurement instead of loop length measurements. LoopCare
maintains an internal table for mapping insertion loss returned by the DMU+L to a
Speed Bin (similar to the current Loop Length to Speed Bin Table).
The LIL measurement feature is not supported on:
Lines served by a Universal Digital Loop Carrier (UDLC) or an Integrated

Digital Loop Carrier (IDLC) system with the Central Office test unit
performing the line test
Lines served by an EAIU line unit and tested using a Metallic Test Bus
(MTB) extended by a Metallic Channel Unit (MCU)
Lines served by an MDF trunk. The QUALX test can not be performed on
an MDF trunk since QUALX requires an initial access. All testing on an
MDF trunk is subsequent testing, since an MDF trunk access is initially
required
Date and Time

Synchronization
The DMU+ supports the capability to have the internal date and time synchronized
with the LoopCare server. This capability facilitates support of the product when
resolving maintenance issues.
Longitudinal
Balance
Measurement at 200
Hz
The DMU+ has the capability to perform the longitudinal balance measurement at
200 Hz instead of the 24 Hz at which the DMU performs the measurement.
1-6
DigiTest Components

Overview
The Digital Wideband Unit (DWU) card adds wideband measurement capability to
the DMU. The DMU and the DWU together form a DMU-W. The DWU adds
capabilities such as bridged tap detection and wideband noise measurement to
DMU capabilities.
NOTE:
The DWU cannot function on its own, it must be used in conjunction with a
DMU.
Light Emitting
Diodes (LEDs)
The DWU has two Light Emitting Diodes (LEDs).
Data (Green/Red/Orange) indicates when someone is logged in and some

alarm conditions
Status (Green/Red/Orange) indicates storage memory access or some

alarm conditions.
DigiTest Components
Other Components
Alarm/Fuse Card
The Alarm/Fuse Card holds the fuses for the main power feeds and alarm
contacts. The alarm/fuse card has two LEDs (see LED section below) and plugs
into the center slot on the DMN. The alarm/fuse card has two RJ-45 jacks on its
front panel to provide direct craft access (see Craft Access section below)
Light Emitting
Diodes (LEDs)
The Alarm/Fuse Card contains two LEDs:
Fan. Indicates fan and fuse status.
Power. Indicates power supply status.
Both LEDs on the Alarm/Fuse card are green under normal conditions and red if a
problem is detected.
Craft Ports
1-8
The craft ports are RJ-45 jacks located on the front of the alarm/fuse card. There
is one port for each DMU. The craft port (referred to as DMU Communication Port
2) allows direct interface to the DMU, which can be used for provisioning,
upgrading, and troubleshooting the DMU.
DigiTest Components

Overview
The Wideband Transmission Module (WTM) works in conjunction with the modem
card in a Central Office (CO) DMU to convert the Metallic Channel Unit (MCU) test
path into a data link. This data link is used for communication between the DMU
and DWU, as if they were housed in the same DMN. The CO DMU uses the data
link to request wideband tests from the DWU at the Remote Terminal (RT) and to
obtain test results.
DigiTest Components
Modem Option Card
Modem Option Card

Overview
1-10
The modem option card may be installed on a slot on the DMU main board. The
modem requires a tip and ring connection to a POTS line. The modem permits
remote access to the DMU and is primarily intended for use when the DMU serves
as the remote testhead. The modem configuration on the DMU is also referred to
as DMU Communication Port 3.
DigiTest Components

Overview
The Ethernet DMU (E-DMU) Option Card is a daughter-card that may be installed
on the DMU main board in the slot used for the modem option card. The Ethernet
Option Card provides the ability to directly connect a DMU to a TCP/IP Ethernet
network for communications with the test host. This eliminates the need for an
access server or other specialized network to gain access to the DMU. Users may
extend their Ethernet TCP/IP networks directly to the DMU.
The Ethernet Option Card has an RJ-45 connector that is accessible on the front
of the DMU. This allows the Ethernet Option Card to provide serial port passthrough to a serial device, such as a Telaccord 1000/DAU1000 to drive
Transaction Language 1 (TL-1) access commands.
NOTE:
LoopCare does not support Ethernet Option Card applications where the
modem daughter card is required, such as the Digital Wideband Node
(DWN) architecture.
Supported Protocols
Additional
Information
The Ethernet Option Card supports 10 Base-T Ethernet and the following
protocols:
Telnet
File Transfer Protocol (FTP)
Inbound ping
Dynamic Host Configuration Protocol (DHCP)
For additional information, see DigiTest Ethernet DMU (E-DMU): page 2-9 of this
guide.
1-12
DigiTest Components
Contents
Introduction
2-2
2-3
DWU
2-5
2-6
2-9
2-12
2-13
2-14
2-18
2-21
2-22
Introduction
Introduction
Overview
DigiTest testing modules (DMUs, DMU+s, DWUs, E-DMUs) are delivered with
appropriate associated components in several mounting shelves.
The mounting shelves allow DigiTest components to be delivered conveniently to
customer sites as integrated configurations. The mounting shelves also provide
additional ports appropriate to the function of the configuration.
2-2

Overview
The Digital Measurement Node (DMN) is the mounting shelf for the following plugin components.
Alarm/Fuse Card
Up to two DMUs or DMU+s
Figure 2-1.
Digital Measurement Node (DMN) for DMU2
Figure 2-2.
LoopCare Interface
Port
Digital Measurement Node (DMN) for DMU+
The LoopCare Interface Port is a serial port that connects a DMU/DMU+ directly
to the LoopCare access server. This port is located at the back of the DMN and is
an RJ-45 jack. This interface port is referred to as DMU/DMU+ Communication
Port 1.
Craft Ports
The craft ports are RJ-45 jacks located on the back of the DMN enclosure. There
is one port for each DMU/DMU+. The craft port (referred to as DMU/DMU+
Communication Port 2) allows direct interface to the DMU/DMU+, which can be
used for provisioning, upgrading, and troubleshooting the DMU/DMU+.
IP Port (Front Panel

DMU+)
The IP port connects the DMU+ Master to IP. For information on configuring a
Master/Extender setup, see Configuring the DMU+: page 3-48.
Serial Port (Front

Panel DMU+)
The serial port connects the DMU+ to other serial connected devices, such as a
TelAccord 100. For information on configuring a serial port, see Configuring the
DMU+: page 3-48.
2-4
DWU
DWU
Overview
The DWU and the DMU/DMU+ are the physical testheads that can be used with
an RMU with wideband or in an RMU-S with wideband configuration. The DMU/
DMU+ can function on its own, however, the DWU requires a DMU/DMU+ in order
to function.
.
Figure 2-3.
Digital Measurement Unit - Wideband

Introduction
The Tollgrade Digital Wideband Node (DWN) adds wideband testing capabilities
for universal and integrated Digital Loop Carriers (DLCs) to the narrowband
testing capabilities of DMUs at Central Offices.
This test solution supports complete wideband pre-qualification, installation
testing, and maintenance of ADSL services.
Components
The DWN is the mounting shelf for the following plug-in components.
Alarm/Fuse Card
One WTM
One DWU
Figure 2-4.
POTS Testing for

DLCs
The LoopCare testing architecture for DLCs supports POTS testing by using
switch-based test units located at Central Offices (COs). For the majority of DLCs,
these switch-based test units use Tollgrade Metallic Channel Units (MCUs) to
extend testing functionality from the switch to the Remote Terminal (RT). Since
the MCUs only provide a narrowband test path, this architecture does not support
wideband testing.
Wideband Testing
for DLCs
The DWN is co-located with the DLC-RT. Using the DWN hardware, narrowband
testing from the CO done by the DMU via an MCU pair can be combined with
wideband testing performed by the DWU component of the DWN at the RT site.
2-6
DWN Test Path

Data Link
At the CO, a Digital Measurement Node (DMN) contains only a DMU with a
modem daughter-card incorporating a relay to isolate the tip/ring pair. The DMN
uses a modified J7 adapter at the rear connections.
The WTM works in conjunction with the modem card in the CO DMU to convert
the MCU test path into a data link. This data link is used for communication
between the DMU and DWU, as if they were housed in the same DMN.
Narrowband/
Wideband Testing
During narrowband tests the WTM acts as a pass-through for the requests and
returned results.
The CO DMU can also use the data link to request wideband tests from the DWU
in the DMN at the RT and to obtain test results.
Test Ports
The DWN can have four inputs from MCUs and four outputs to RTs.
Serial Interfaces
The DWN supports 5 serial interfaces. One (default) is assigned as the craft
interface. This connector is on the front panel of the Fuse/Alarm card.
Two RJ45 backplane connectors are general-use communication ports to the
DWN. They can be assigned to several services.
One is used for the backplane interconnect and has no connector.
Craft Access Port
The craft access port is an RS-232 human machine interface (HMI) that allows a
craft person to configure and provision the DWN. This interface is available from
the front panel of the Fuse/Alarm Card using an RJ-45 connector. This interface
may be configured for another service.
Testing Capabilities
NOTE:
When the CO DMU requests narrowband tests, the WTM is a passive passthrough. All narrowband testing capabilities of the DMU are unaffected by
this configuration. If the DWN fails or is powered down, narrowband tests
will not be affected.
The DWN, when used in conjunction with the CO-based DMU and MCU pair,
provides the following measurements to support loop qualification, provisioning
and maintenance of DSL service:
Supported
LoopCare
Wideband Test
Requests
2-8
AC/DC Resistance
AC/DC Voltage
AC/DC Current
Capacitance/Loop Length
Wideband Noise
Wideband Disturber ID
Bridged Tap Detection and Location
Load Coil Detection
Time Domain Reflectometry (TDR)
Date Rate Prediction
Data Rate Optimization
For a list of test requests supported by the DWN, see Appendix A of this guide.

Overview
The DigiTest Ethernet DMU (E-DMU) is a DMU equipped with an Ethernet Option
Card. The daughter card replaces the modem card option on the DMU.
The E-DMU has two RJ-45 connectors:
Ethernet Extender
Card
One is labelled ENET and provides standard 10 Base-T Ethernet. This

allows the DMU to communicate with LoopCare over TCP/IP connections.
The second RJ-45 connector is labelled Serial and provides an RS-232

serial port that can be used for craft access or as an access server RS-232
port. This allows the E-DMU to communicate with one serial device. The
serial port supports a pass-through serial RS232 connection between a
TCP/IP client and the E-DMU.
The Ethernet Extender Card is a variation of the Ethernet Option Card that has
been customized for use on subordinate DMUs. The 2 cards are built from the
same PC board and run the same firmware, but have different components and
are not interchangeable.
The Ethernet Extender Card has one serial port that may be used for craft access
or as an access server RS232 port.
Extnet
Multiple Ethernet Extender Cards may be used with a DMU Ethernet Option Card
(acting as a master) in a Master/Extender configuration (Extnet).
The master and extenders in an Extnet are connected with wire wrap pins that are
either part of the backplane of the DMN or part of a J7 Adapter Board.
The maximum buildout of a Extnet uses 1 master and 7 extenders. Figure 2-5
shows an example of a maximum build out of an Extnet.
J7 ADAPTER BOARD
J7 ADAPTER BOARD
J7 CONNECTOR
J7 CONNECTOR
ETHERNET
EXTENDER
CARD
SERIAL
( FRONT )
EXTENDER
FUSE/
ALARM
CARD
DMU
POWER SUPPLY CARD
POWER SUPPLY CARD
SERIAL
DMU
ETHERNET
EXTENDER
CARD
SERIAL
POWER SUPPLY CARD
FUSE/
ALARM
CARD
DMU
ETHERNET
EXTENDER
CARD
DW N BACKPLANE
EXTENDER
EXTENDER
DMU
ETHERNET
EXTENDER
CARD
SERIAL
( FRONT )
POWER SUPPLY CARD
DW N BACKPLANE
EXTENDER
EXTENDER NETW ORK BUS (TW ISTED PAIR)
J7 ADAPTER BOARD
J7 ADAPTER BOARD
J7 CONNECTOR
J7 CONNECTOR
DW N BACKPLANE
MASTER
ETHERNET/
TCPIP
SERIAL
SERIAL
( FRONT )
ETHERNET
EXTENDER
CARD
SERIAL
( FRONT )
EXTENDER
CRAFT PORT
OR
EXTERNAL SERIAL DEVICE
(E.G. TELACCORD 1000)
EXTENDER
EXTENDER
MASTER/EXTENDER CONFIGURATION W ITH 7 EXTENDERS

SHOWN INSTALLED IN FOUR DIGITAL MEASUREMENT NODES (DMNs)
Figure 2-5.
Serial Port
Application
ETHERNET
EXTENDER
CARD
DMU
POWER SUPPLY CARD
ETHERNET
EXTENDER
CARD
FUSE/
ALARM
CARD
DMU
POWER SUPPLY CARD
SERIAL
POWER SUPPLY CARD
ENET
DMU
POWER SUPPLY CARD
FUSE/
ALARM
CARD
DMU
ETHERNET
OPTION
CARD
DW N BACKPLANE
Maximum Build Out of an Extnet
The interface to a serial device via the serial port supports an interface that does
the following.
Controls test access with commands
Reports status with responses to an external device
An example external device is the Telaccord 1000/DAU1000 or regular DMU. A

custom cable is required to allow communication between the serial port and the
Telaccord 1000/DAU10000 or regular DMU.
2-10
TCP/IP Ports
There are three TCP/IP ports associated with each card (master or extender):
DMU (access DMU for tests, firmware downloads, etc.).
Admin Port (for Ethernet card firmware downloads, and to set up the serial
port baud rate)
Serial Port (acts like a terminal server serial port)
In a maximum buildout of 1 master and 7 extenders, there are 24 possible ports to

which a user may connect:
Master DMU (port 6000)

Master Admin Port (port 6005)
Master Serial Port (port 6010)
Extender 1 DMU (port 6100)

Extender 1 Admin (port 6105)
Extender 1 Serial Port (port 6110)

...

The number of simultaneous TCP/IP connections is limited to 10.

Only the DMU and Serial ports are of interest for the LoopCare OA&M. The Admin
port is not configurable for LoopCare.

Overview
The Expert Measurement Unit (EMU) is a logical central office (CO) testhead that
consists of up to 16 physical, single-port testheads. These physical testheads act
like individual test ports found on other LoopCare testheads (for example, the
Loop Testing System [LTS]), and can be similarly arranged into No Test and/or
MDF trunk groups (with a maximum of ten trunk groups for each EMU).
NOTE:
The 16-testhead configuration reflects LoopCare implementation of
DigiTest System testheads and not any intrinsic limitations of the DigiTest
System.
Supported
Testheads
The EMU may contain any combination of up to 16 of the following testheads:
DMU
DMU-W
E-DMU
The DMU or DMU-W can also be installed at the Remote Terminal (RT) of a
Digital Loop Carrier system and be used as an RT testhead (similar to an RMU or
the RMUW-S).
Capabilities
The EMU provides all the general-purpose loop test capabilities defined in the
LoopCare Test Requests Guide. In addition, the EMU is the platform for other
enhanced LoopCare features and future loop testing services.
The varied services provided by the EMU give it the flexibility to serve different
applications. The EMU, for example, can be used as the primary testhead for a
switch or as a supplemental testhead that provides overlay coverage for specific
features (for example, Load Coil Detection). The application assigned to the EMU
determines the number of lines that may be supported.
2-12

Overview
LoopCare interfaces with the physical testheads using TCP/IP connections

through an access server or through a modem dial-up link. Whether connections
to the EMU are made via a direct TCP/IP access or through dial-up modems,
communication is managed and controlled as part of LoopCares communications
gateway on the LoopCare processor.
The communications gateway is LoopCare software that sets up and establishes
communication to testheads like the EMU, Remote Measurement Unit (RMU),
Compact Measurement Unit (CMU), etc. Once communication is established, the
gateway handles transport of messages between LoopCare and the particular
testhead. Finally, the gateway is also responsible for cleanly disconnecting and
dropping access.
Communications can be monitored and administered using the DZadmin utility,
which is discussed fully in Chapter 3.

Overview
EMUs and DMUs can be used in the test environment in several different ways, all
of which have been mentioned above. This section discusses each of those
applications and provides graphic examples.
EMU as Primary
Testhead
The EMU can be used as the primary CO testhead serving a switch. The EMU in
this configuration has full access to all the lines it serves, like any other LoopCare
testhead (for example, LTS, CMU, and DCTU).
LoopCare
Switch
M
D
F
Customer
Premises
Equipment
NTT
TCP/IP
Network
DMU
DMU
EMU
Access Server
Figure 2-6.
The EMU as Primary CO Testhead.
Figure 2-6, above, illustrates an EMU with two DMU "ports." One port is used for
No Test (NTT) access, while the other port is used for MDF trunk access. The
EMU can have a maximum of 16 DMU "ports" arranged into as many as ten trunk
groups.
(Continued on next page)
2-14

(Continued)
EMU as an Overlay
Central Office
Testhead
The EMU can also be used as an adjunct testhead that supports an existing
primary testhead (LTS or DCTU only). There are two basic overlay configurations
that may be used independently or together:
Support of a DMU-specific enhanced test feature (for example, load coil

tests)
Testhead replacement (for example, LoopCare LTF testhead replacement)
If the arrangement in Figure 2-7 below was set up to test load coils, all basic test
requests continue to go to the LTS primary testhead. All load coil-specific tests will
be routed to the co-existing EMU.
LoopCare
NTT
L
T
S
Switch
NTT
M
D
F
Customer
Premises
Equipment
TCP/IP
Network
EMU
Access Server
Figure 2-7.
EMU as Overlay Testhead.
Figure 2-7, above, illustrates an EMU that overlays an LTS primary testhead. The
EMU has one DMU "port" in this example, but could have up to 16 such ports
configured in as many as ten trunk groups.

(Continued)
DMU as a Remote
Testhead
The DMU can be configured as a Remote Testhead (DMU-R) located at the

Remote Terminal of a DLC configuration. In this configuration, the DMU-R would
work in conjunction with a CO testhead (LTS, DCTU, or an EMU) to complete the
DLC test. LoopCare communicates with the DMU at the RT through an access
server dial-up modem or direct connect via access servers. Figure 2-8 and
Figure 2-9 below illustrate this configuration.
Switch
LoopCare
TCP/IP
Network
NTT
I
D
L
C
Remote
Terminal
(RT)
DMU-R
Access Server
Modem Pool
EMU
Customer
Premises
Equipment
Optional
DWU
Modem
Card
Calls DMU-R
Figure 2-8.
DMU as a Dial-up Remote Testhead.
Figure 2-8 illustrates a DMU-R at the RT working with an EMU at the CO to test
an Integrated Digital Loop Carrier (IDLC) line. LoopCare signals the EMU to begin
CO tests on the DLC line and proceeds to call the DMU-R through the access
server dial-up modem. The DMU-R at the RT then runs tests on the specific line
under examination and returns results to LoopCare when they are completed.The
DMU-R can also have an attached DWU to provide wideband capability.
Note: The DMU-R only supports dialup connections from an Access Servers
Modem Pool. Connections from other types of Modem Pools (datakit or local
machine) are NOT supported.
2-16
Switch
LoopCare
NTT
TCP/IP
Network
Remote
Terminal
(RT)
I
D
L
C
DMU-R
Access Server
Customer
Premises
Equipment
Optional
DWU
Access
Server
EMU
IP
Figure 2-9.
DMU as a Direct Connect Remote Testhead
Figure 2-9 illustrates a DMU-R at the RT working with an EMU at the CO to test
CO tests on the DLC line and proceeds to access the DMU-R through the access
server. The DMU-R at the RT then runs tests on the specific line under
examination and returns results to LoopCare when they are completed.The DMUR can also have an attached DWU to provide wideband capability.

Overview
The DMU can run LoopCare test requests when used in an EMU as a Central
Office (CO) testhead.
EMU as a CO
Testhead
The following tests can be run when using an EMU as a CO testhead:

BENCH (if BMDB feature ON)
CALL
CALLRD
CCOL
CHANGE
CHOME
CO
COIN
CRET
DISP (if BMDB feature ON)
DCOILS
DIAL
DTOUT
FULL
GRM
*INFO
*KEEP
*HELP
LIN
LOC1
LCOILX
LOOK
LOOKIN
LOCATE
LRM
MDFNUM
LOOP
MDFGRP
MON
MDF
QIN
QUICK
PSR
REF1 (if DLC/Enhanced Sectionalization Feature On)

REF2 (if DLC/Enhanced Sectionalization Feature On)
REV
RING#
RING
RINGER
RINGIN
SOAK
*STV
TALK
TALKIN
TONE+
TONE
TONECA
*TV
VER##
XCB
XTONE
2-18
DMU Testing Capabilities (Continued)

DMU as an RT
Testhead
The following test requests can be run when using the DMU as an RT testhead
after bypass (the requests that obtain bypass are FULL, LOOP, TONE, and
TONE+):
BENCH (If BMDB Feature On)
CHANGE
DCOILX
DIAL
DISP (If
BMDB
Feature is
ON)
FULL
*HELP
*INFO
*KEEP
LCOILX
LOOP
LRM
MON
QUICK
REF1 (if DLC/Enhanced Sect Features On)

REF2 (if DLC/Enhanced Sect Feature is On)
REV
RING#
RING
RINGER
SOAK
*STV
TALK
TONE+
TONE
TT
*TV
VER##
XCB
XTONE
Table 2-1. Tests Supported by DMU as RT Testhead
Legend:
All requests preceded by an asterisk ( * ) are really TV mask-level requests and
are not specific to the testhead. In other words, they work no matter what the
testhead is, because they don't involve the testhead to perform their function.
These requests either provide information from the database, or bring up different
user interface screens (for example, TV, STV).
DMU as an RT
Testhead with DWU
All of the test requests listed in Table 2-1 plus the following can be run when using
the DMU as an RT with an attached DWU: BT, TDR, and WNOISE.
BT
TDR
WNOISE
All requests preceded by an asterisk ( * ) are really TV mask-level requests and

are not specific to the testhead. In other words, they work no matter what the
testhead is, because they don't involve the testhead to perform their function.
These requests either provide information from the database, or bring up different
user interface screens (for example, TV, STV).
2-20

Introduction
The DWN is co-located with the DLC-RT. The DWN is inserted into the Test
Access Pair (TAP) path from the MCU to the internal DLC Metallic Test and
Access Unit (MTAU). Using the DWN hardware, narrowband testing from the CO
done by the DMU via a MCU pair can be combined with wideband testing
performed by the DWU at the RT site.
When the EMU performs a POTS test, the DWN acts as a passive pass-through.
Example
Deployment
Figure 2-10 shows an example of a DWN deployment.
CO
LoopCare
RT
COT
Switch
RT
MCU
MCU
NTT
TAP
T,R
CPE
T,R
DWN
DMU
Network
Figure 2-10.
EMU
WTM
DWU
Example of DWN Deployment
NOTE:
Figure 2-10 shows a Universal Digital Loop Carrier (DLC) system, but this
solution will also support Integrated DLC (IDLC) systems.
The DMU shown in the CO is an Expert Measurement Unit (EMU) from the
LoopCare perspective. The CO could also have either an LTS or DCTU collocated
with the EMU.
A single DWN may be connected to up to four MCUs.

Overview
This section discusses possible applications of E-DMUs in test environments and

provides graphic examples.
What has been described above about EMUs and DMUs holds true for E-DMUs.
Where an EMU can contain up to 16 DMUs, up to 8 of them can be E-DMUs
arranged in master/extender configuration (1 master and 7 Extenders). Or a
single E-DMU may provide a serial connection to a serial device. These two
configurations can be combined in one Extnet.
The main difference between DMUs and E-DMUs is that E-DMUs do not require a
separate access server.
NOTE:
The following examples of E-DMU applications are not exclusive of each
other. A site may incorporate 1, 2, or all of these scenarios.
Single DMU
Configuration
The Ethernet Option Card enables a user to control a DMU via a TCP/IP
connection over Ethernet, rather than a dial-up modem. The DMU Ethernet
Option Card acts as a logical access server to the DMU and one additional serial
device, via a front panel RJ-45 connector. A common scenario for the additional
device is connection of the TELACCORD 1000/DAU 1000 to drive TL-1 access
commands.
The Ethernet-only architecture consists of a single Ethernet Option Card installed
in a single DMU (no extenders). In a single E-DMU configuration, the user can
connect to the following.
A DMU
An EtherCard User Interface
A serial port.
This serial pass-through port may be used to control another piece of equipment
such as a Telaccord 1000/DAU1000 or regular DMU. Figure 2-11 shows an
example of this.
2-22
LoopCare
TCP/IP
Network
EOC
DMU
RS232
TL1
Control
Switch
Splitter
DWU
T/R
TelAccord/
DAU1000
MDF
DSLAM
EOC = Ethernet Option Card

Figure 2-11.
The E-DMU as Serial Pass-Through to a Telaccord 1000/DAU1000
A custom cable is required to allow communication between the E-DMUs serial

port and the Telaccord 1000/DAU1000.
E-DMUs in an
Extnet
E-DMUs may be combined in an Extnet network consisting of a Master E-DMU

and up to 7 Ethernet Extenders. Refer to Figure 2-5.
Access to any of the subtending Extender DMUs may be obtained by making a
TCP/IP connection to the Master DMU. The master and extender DMUs are all
accessible via a TCP/IP connection to the Ethernet Option Card on the master. In
this scenario, the Master DMU is equipped with an Ethernet Option Card, while
each Extender DMU is equipped with an Ethernet Extender Card.
For more details on the arrangement of the Master and Extenders, and the setting
of rotary switches and jumpers, see the Supplemental Users Guide for the
Ethernet Option and Ethernet Extender Cards For use with Tollgrades LoopCare
DMU and Nortel DMU.
E-DMU as a Remote
Testhead
The E-DMU can be configured as a Remote Testhead (DMU-R) located at the

Remote Terminal of a DLC configuration. In this configuration, the E-DMU-R
works in conjunction with a CO testhead (LTS, DCTU, or an EMU) to complete the
DLC test. LoopCare communicates with the E-DMU at the RT through a TCP/IP
connection. Figure 2-12 below illustrates this configuration.
Switch
LoopCare
TCP/IP
Network
NTT
Remote
Terminal
(RT)
I
D
L
C
Customer
Premises
Equipment
EOC
DMU
Access Server
EMU
Modem Pool
Figure 2-12.
E-DMU as a Remote Testhead.
Figure 2-12 illustrates an E-DMU at the RT working with an EMU at the CO to test
CO tests on the DLC line and proceeds to connect to the E-DMU through TCP/IP.
The E-DMU at the RT then runs tests on the specific line under examination and
returns results to LoopCare when they are completed.
2-24
EMU Installation
Contents
EMU Installation
3-3
3-4
EMU as CO Test Head
3-4
3-5
3-8
3-13
3-18
3-19
Installation of EMU as Central Office (CO) Wideband Test Head
3-24
3-24
3-25
3-28
3-31
Miscellaneous Setup
3-32
3-34
3-35
EMU Installation
Contents (continued)
Installation of a DMU as an RT Test Head
3-41
3-41
3-42
3-44
3-47
3-48
3-49
3-60
Identifying the RMU
3-69
3-70
Installation of a Standalone Remote Test Head

3-73
3-74
3-76
3-79
3-80
Associating a Standalone Remote Test Head with an LTE(s)
3-84
3-85
DWN Deployment
3-85
DWN Administration
3-86
3-2
3-73
3-90
Overview
3-90
Equipment Checklist
3-91
3-95
Reference Documents
3-98
EMU Installation
EMU Installation
Introduction
This chapter provides an overview of the activities required to install and operate
the following test configurations:
EMU as a Central Office (CO) test head
EMU as a Remote Terminal (RT) test head (RMU)
EMU as a Remote Terminal (RT) test head (RMU) with an attached DWU
EMU as a Central Office (CO) Wideband test head
EMU as a Standalone Remote test head (RMU-S)
The chapter also includes items other than the test heads (for example, Access
Servers, modems, etc.). These items may be considered peripheral from the test
head point of view, but are important elements in the overall system architecture.
By including the peripherals in this chapter you can form a more complete picture
of the entire system architecture.
Note that this section is only an overview. It summarizes installation procedures
and points to appropriate references where details or step-by-step procedures
can be found.
Common System
Prerequisites
System Software Prerequisites

LoopCare software version G10I14.1 or later is required for EMU operations.
Software prerequisites for other LoopCare support systems (BaseWorx,
ORACLE, etc.) are found in the LoopCare Installation Guide or in the specific
LoopCare Release Book that is delivered with the LoopCare software.
Installing the Communication Gateway

The LoopCare processor requires a Communication Gateway setup to talk to the
EMU test heads.
EMU Installation
EMU as CO Test Head

EMU as CO Test Head
Overview
The EMU is a logical CO test head that is made up of one or more physical test
heads (DMUs). This section addresses the following topics:
Environmental Specifications
Physical Installation of a DMU Test head
Peripheral Equipment Setup
Note that these are high level descriptions only. Specific references will be
provided where more detail is required
Environmental
Specifications
3-4
The DMU is designed to reside and operate in a Central Office (CO) environment.
The test head is be able to mount in a standard 19- or 23-inch equipment frame.
Specific operating specifications are found in the DigiTest System Users Guide.
EMU Installation
Physical Installation of a DMU/DMU+

Test Head
Overview
The detailed procedures for physically installing the DMU/DMU+ as a CO test

head are described in Chapter 2 of the DigiTest System Users Guide. This
document discusses the following topics:
Power
Grounding
Ringing supply
Fusing
After you have completed its physical installation, the DMU/DMU+ will be ready
for connecting to peripheral equipment and the internal test head configuration.
Peripheral
Equipment Setup
In order for the DMU/DMU+ to operate it must connect to different pieces of

peripheral equipment, including test trunks, Access Servers, telephone lines, etc.
The list below identifies key pieces of peripheral equipment that will be discussed
in later parts of this document.
No Test Trunks
MDF Test Trunks
Telephone Lines (modem and callback)
Access Server
Trunk Calibration line
IP
EMU Installation
Figure 3-1 shows an overview of a system architecture with an EMU and

associated peripheral equipment.
7
LoopCare
Switch
Comm
Network
CPE
M
D
F
IOP
A
B
NTT I/F
1
Access
Server
DMU
6
DMU
Modems
A
Figure 3-1.
B
EMU Configuration with Peripherals.
Legend:
3-6
1.
The access server is the interface between the DMU and LoopCare.
Access server ports are configured specifically for either direct connect to a
DMU, modem connection, or 5ESS IOP connection. For information on the
setup and provisioning of the Access Server, refer to Appendix J of the
LoopCare Installation Guide.
2.
This item represents the cables and connectors used for directly
connecting a DMU to an Access Server. It is recommended that DMUs
used as CO test heads connect directly to the Access Server. A description
of the cables and connectors for the DMU direct connection are found in
Appendix J of the LoopCare Installation Guide.
EMU Installation
3.
This item is the POTS telephone line from the switch that serves the
internal DMU modem. To avoid clutter in the diagram, telephone line
connections are only shown to one DMU. The modem dial-up connection is
optional because the DMU can directly connect to the Access Server.
LoopCare recommends, however, that each DMU have a modem dial-up to
provide an alternate access for administration and maintenance functions
to be run.
The DMU can also have a second telephone line that can be used as a
back-up telephone number for the modem. This line is optional and is not
shown on Figure 3-1 on page 3-6.
4.
This is the POTS telephone line from the switch that is used as the DMU
callback line. The callback line is required in order to run LoopCare
interactive callback transactions.
5.
This is the No Test Trunk (NTT), which connects tip, ring, and sleeve
terminals on the DMU into the switchs NTT interface circuit. The No Test
Trunk permits the DMU to access and test customer lines through the
switch.
6.
This is the Main Distribution Frame (MDF) test trunk that connects to tip,
ring, and sleeve to a designated jack position on the MDF. The MDF trunk
allows LoopCare to get access directly to the MDF, bypass the switch, and
connect to lines under test via a special patch connection made on the
MDF.
7.
This item is the Trunk calibration line. The Trunk Calibration line is a POTS
line open at the MDF and is used for calibrating the distance and resistance
of the test trunk through the CO. One trunk calibration number is required
for each trunk group on the EMU.
8.
This item represents the cables and connectors used to connect the
Access Server directly to the 5ESS switchs IOP TTY port. This link,
while not specific to the installation of the DMU, is required for
implementing Originating Equipment (OE) retrieval feature.
EMU Installation

After the physical installation of the DMU has been completed, and all peripheral
equipment has been connected, the DMU must be configured for its particular
application. This will require the user to define or verify data in the following areas:
Overview
Device type: CO / RT test head
Port type: NTT or MDF trunk
Connection type: direct or dial-up
Port configuration: baud, parity, etc.
Miscellaneous set-up items: passwords, clock, etc.
Table 3-1 below lists the possible DMU CO test head configurations.
Possible DMU
Configurations
Table 3-1.
Possible DMU Configurations.
Connection
Test Port NTT/
Direct/
Modem
Device Type
MDF
Communication Port Config

Baud
Parity
Data
Bits
Stop
Bits
Access
Parameters
DMU-C
NTT
Direct
9600
Default
DMU-C
MDF
Direct
9600
Default
DMU-C
NTT
Modem
9600
Default
DMU-C
MDF
Modem
9600
Default
NOTE:
For a CO test head application, a direct connection to the Access Server is
recommended over a modem dial-up.
The following paragraphs discuss the different entries that have to be considered
when configuring the internal DMU database.
Device Type
3-8
A DMU can be used either as a CO test head or as an RT test head and the
device type indicates which. The entry is not just a label. It determines what test
commands the DMU will accept. (For a CO test head all test sessions must begin
with either an NTT or MDF access.)
EMU Installation
The device type for a CO test head is DMU-C. The value is entered through the
DMUs Human Administration (HADM) interface, no-dial for direct connect, This is
done by selecting Device Type from the Administration Menu. Refer to the
DigiTest System Users Guide for more information on HADM.
Test Port Type
When the DMU is used as a CO test head, the port trunk access can be either a
No Test or and MDF Trunk. The No Test Trunk (NTT) enables the DMU to access
a subscriber line through the switch; and an MDF trunk provides an access point
on the MDF.
The port type is entered through the DMUs HADM interface, selecting Port Trunk
Type from the Administration Menu. Refer to the DigiTest System Users Guide for
more information on HADM.
Connection Type
There are only two connection configurations available for communicating to a

DMU from LoopCare. They are:
Direct connection off an Access Server port
Dial-up modem connection from LoopCare modem ports
When the DMU is used as a CO test head, the direct connect configuration is
recommended.
The connection type determines which DMU communication port should be
configured. Table 3-2 lists all DMU communication ports, their function, and
specific data entry (if applicable) in HADM. For a DMU CO test head
communication port 1 should be configured.
Table 3-2.
1.
Connection Type and DMU Communication Port Map

Valid hadm Entry Administer/
Configure Port
DMU Comm Port
Connection Type
DMU Direct Connect to

Access Server
LoopCare DIRECT

PCa
TERMINAL DIRECT
Craft Access Directb
Modem Dialupa
DMU Connected to a PC is discussed in the DigiTest System Users

Guide.
EMU Installation
2.
Craft direct port is discussed in the DigiTest System Users Guide.
3.
It is possible for the DMU to be set up for both an LoopCare Direct connect
and a modem dialup. In fact, it is recommended that all DMUs have a
modem dial up to provide an alternative connection path to the DMU in
case of maintenance emergencies.
Enter the value for Connection Type through the Configure Ports field on the
DMUs Administrators Command set (HADM) interface Administration menu.
Select the appropriate communication port for data entry. This option also allows
you to enter other port configuration data that will be discussed in the next section.
Refer to the DigiTest System Users Guide for more information on HADM.
Communication
Port Configuration
Once you know whether the DMU is a direct connect or modem dialup you know
which DMU Communication Port to configure (see Table 3-2). Table 3-3 below
shows the valid values for other key port configuration data. For the DMU the
parameter values for both modem and direct connect DMU are the same.
Table 3-3.
DMU Communication Port Parameter Values for DMU Direct Connect
or Modem Dial-up.
Parameter
Miscellaneous Setup
3-10
Value
Baud Rate
9600
Parity
Data Bits
Stop Bits
1.
Enter the parameter values for the Connection Type through the Configure
Ports field of the DMUs HADM interface Administration menu.
2.
Select the appropriate communication port for data entry. Refer the
There are a number of additional user-tunable entries ranging from timeouts and
thresholds to passwords, all of which can be entered through the HADM and/or
EMUadmin (used only when the DMU is serving as a CO test head) interfaces.
Refer to the DigiTest System Users Guide for more information on HADM. For
more information about EMUadmin, LoopCares administrative interface for the
EMU; refer to Chapter 4, EMU Administration of this guide.
EMU Installation
Table 3-4 below lists the miscellaneous user-settable items, which interface they
can be populated through (HADM or EMUadmin) and the specific subitem or
option for each interface.
Table 3-4.
Additional User-Tunable Entries.
Entry
HADM Administration
Selection
EMUadmin
Timeouts
Additional Functions
Option 1
Clock
Set Clock
--
Password
Passwords
--
Edit/Display DMU
Status
Options 6 and 7
Edit/Display DMUID
--
Calibration
Calibration
--
Timeouts
Timeouts are access-related values like login wait time, access wait time, etc. The
DMU is delivered with default values for each timeout entry. Use those values until
there is a demonstrated need to tune the parameters. For more details on each
timeout value and its default values, see Chapter 4, EMU Administration of this
guide. These entries can be viewed or changed from both HADM and EMUadmin.
Thresholds
Threshold values represent the percent failure on trunks and equipment required
to report a problem to the user. The DMU is delivered with default values for each
timeout entry. Use those values until there is a demonstrated need to tune the
parameters. For more details on each threshold value and its default entries, see
s. For more details on each timeout value and its default values, see Chapter 4,
EMU Administration of this guide. These entries can be viewed or changed from
both HADM and EMUadmin.
Clock
The clock option is used to set the DMUs internal clock. It is not a required
setting. If you elect to set the clock option, you will be able to follow time-stamp
tracing more easily. The clock can be set from the HADM interface
EMU Installation
Password
The DMU has default passwords for a variety of user logins (for example, HADM,
LoopCare computer login, etc.). Although this is not a required setting, the utility
allows you to control user passwords for security purposes. For more information
on passwords, see the DigiTest System Users Guide.
The password entered in the DMU should match the password that is entered for
the DMU in the LoopCare ADEF database.
Status
DMU, Equipment, and Trunk status can be displayed or changed by using the
status option. This data is accessible through either the HADM or EMUadmin
interface. For more information on DMU trunk and equipment status, see s. For
more details on each timeout value and its default values, see Chapter 4, EMU
Administration of this guide.
NOTE:
The initial status of the TLK and WU devices will be NE (Not Equipped). If
applicable for your particular installation, change these statuses to A
(Available) upon installation.
DMUID
The DMUID is the DMUs internal ID. It is usually set to match the DMU test head
ID entered in the LoopCare database. The DMUID is usually automatically
populated when the test head is downloaded or it can be entered through the
HADM interface.
Calibration
This is the DMUs internal calibration schedule and parameters, The DMU is
delivered with default values. The default values should be used unless tuning of
the values becomes necessary.
3-12
EMU Installation

After the physical installation of the DMU+ has been completed, and all peripheral
equipment has been connected, the DMU+ must be configured for its particular
Overview
Device type: CO / RT test head
Miscellaneous set-up items: passwords, clock, etc.
Table 3-5 below lists the possible DMU+ CO test head configurations.
Possible DMU
Configurations
Table 3-5.
Possible DMU+ Configurations.
Connection
(IP/Access
Server/
Test Port NTT/
Modem)
Device Type
MDF
Baud
Parity
Data
Bits
Stop
Bits
Access
Parameters
DMU-C
NTT
Access
Server
9600
Default
DMU-C
MDF
Access
Server
9600
Default
DMU-C
NTT
Modem
9600
Default
DMU-C
MDF
Modem
9600
Default
DMU-C
NTT
IP
38,400
Default
DMU-C
MDF
IP
38,400
Default
NOTE:
For a CO test head application, a direct connection to the Access Server or
IP is recommended over a modem dial-up.
when configuring the internal DMU+ database.
Device Type
EMU Installation
A DMU+ can be used either as a CO test head or as an RT test head and the
device type indicates which. The entry is not just a label. It determines what test
commands the DMU+ will accept. (For a CO test head all test sessions must
begin with either an NTT or MDF access.)
The device type for a CO test head is DMU-C. The device type for an RT is DMUR. The value is entered through the DMUs Human Administration (HADM)
interface. This is done by selecting Device Type from the Administration Menu.
Port Trunk Type
When the DMU+ is used as a CO test head, the port trunk access can be either a
No Test or and MDF Trunk. The No Test Trunk (NTT) enables the DMU to access
a subscriber line through the switch; and an MDF trunk provides an access point
on the MDF.
The port type is entered through the DMU+s HADM interface, selecting Port
Trunk Type from the Administration Menu. Refer to the DigiTest System Users
Guide for more information on HADM.
Connection Type

DMU+ from LoopCare. They are:
IP connection to a Master DMU+ (Extender DMU+s connected to a Master

via arcnet)
When the DMU+ is used as a CO test head, the IP Master/Extender configuration

is recommended.
The connection type determines which DMU+ communication port should be
configured. Table 3-2 lists all DMU+ communication ports, their function, and
specific data entry (if applicable) in HADM. For a DMU+ CO test head
3-14
EMU Installation
Table 3-6.
DMU Comm Port

Configure Port
Connection Type
Direct Connect to
Access Server or IP
DCE - Login Port
Craft Access Direct
Modem Dialupa
DCE - Login Port
Modem Dialup
DCE - Login Port
DMU+ Direct Connect

to PCa
DTE - Data Port
1.
DMU+ Connected to a PC is discussed in the DigiTest System Users

Guide.
2.
Communication
Port Configuration
Once you know whether the DMU+ is a an access server, connect, IP connect or
modem dialup, you know which DMU+ Communication Port to configure (see
Table 3-6 on page 3-15). Table 3-7 on page 3-15 shows the valid values for other
key port configuration data. For the DMU+ the parameter values for both modem
connectivity to the DMU+ and access server connectivity are the same.
Table 3-7.
DMU+ Communication Port Parameter Values for DMU+ Access
Server or Modem Dial-up.
Parameter
1.
Value
Baud Rate
9600
Parity
Data Bits
Stop Bits
2.
Miscellaneous Setup
EMU Installation
EMUadmin (used only when the DMU+ is serving as a CO test head) interfaces.
EMU; refer to Chapter 4, EMU Administration of this guide.
Table 3-8 on page 3-16 lists the miscellaneous user-settable items, which
interface they can be populated through (HADM or EMUadmin) and the specific
subitem or option for each interface.
Table 3-8.
Entry
HADM Administration
Selection
EMUadmin
Clock
Set Clock
--
Password
Passwords
--
Edit/Display DMU
Status
Options 6 and 7
Edit/Display DMUID
--
Calibration
Calibration
--
Timeouts
Option 1
Timeouts
DMU+ is delivered with default values for each timeout entry. Use those values
until there is a demonstrated need to tune the parameters. For more details on
each timeout value and its default values, see Chapter 4, EMU Administration of
this guide. These entries can be viewed or changed from both HADM and
EMUadmin.
3-16
EMU Installation
Clock
The clock option is used to set the DMU+s internal clock. It is not a required
Password
The DMU+ has default passwords for a variety of user logins (for example,
HADM, LoopCare computer login, etc.). Although this is not a required setting, the
utility allows you to control user passwords for security purposes. For more
information on passwords, see the DigiTest System Users Guide.
The password entered in the DMU+ should match the password that is entered for
the DMU+ in the LoopCare ADEF database.
Status
DMU+, Equipment, and Trunk status can be displayed or changed by using the
interface. For more information on DMU+ trunk and equipment status, see s. For
NOTE:
DMUID
The DMUID is the DMU+s internal ID. It is usually set to match the DMU+ test
head ID entered in the LoopCare database. The DMUID is usually automatically
HADM interface.
Calibration
This is the DMU+s internal calibration schedule and parameters, The DMU+ is
EMU Installation
Resetting the DMU/DMU+ after Entering

Data
Overview
After data for the DMU/DMU+ has been entered (Device type, Port Type, etc.), the
DMU/DMU+ should be reset so that those changes can take effect. This can be
done through the DMU/DMU+s HADM interface, Administration menu, Reset
DMU+ sub-item. Refer to the DigiTest System Users Guide.
NOTE:
If you used the dial or nodial utilities to access HADM and an HADM menus
recommended method of leaving the menu does not work, use the following
sequence: press ESC ESC.
3-18
EMU Installation

This section provides a high-level overview of the most important LoopCare
database entries required to setup the EMU. Table 3-9 covers the major ADEF
forms required to enter an EMU. Some key pieces of information on each form are
discussed. Precise details on every LoopCare data entry for EMUs, however, are
not covered in this section. This is not an ADEF training tutorial.
Overview
The goal of the section is to provide enough guidance to help you identify all the
forms and critical entries. It also helps establish the relationship between different
elements in the overall EMU configuration. For specific information about the
LoopCare ADEF database refer to the LoopCare OA&M Guide for Automated
Data Element Form (ADEF) Utility Administrators.
Figure 3-2 shows a basic EMU configuration with key items labeled as they are
shown in the database example in Table 3-9.
Basic EMU
Configuration
5ESS
Switch
Whippany
LoopCare
TCP/IP
Network
Access Server
achilles
IP 121.1.35.65
IOP
NTT
Svc Name
5ESS IOP Port1
Svc Name
mdfacc Port3
CPE
DMU
Svc Name
ntttacc Port2
P4,5
SVC Name
Mpool
M
D
F
EMU: 1000
DMU
M
Modem Pool
Figure 3-2.
Basic EMU Configuration
ADEF Forms
EMU Installation
When entering an EMU for operation in the LoopCare database, there are several
ADEF forms that must be completed. It is recommended to start with the EMU
form, since it will guide you to all the other major forms that require data entry.
With that in mind, now look at the example in Table 3-9.
Table 3-9.
LoopCare ADEF Data Entry Example for EMU
ADEF Form
EMU
3-20
Explanation
The EMU form provides the detailed data for the EMU and all
associated DMUs. Some key data that must be provided includes:
Test head ID - range 800-1599, example 1000.
Region - Administration region which EMU is a member
Communication method - Either modem pool or access

server. For an EMU access server is preferred.
Passwords - computer and human passwords that

LoopCare will enter to access DMU
Dial Group - For modem pool connection only
Trunk Group information - Identify all NTT and MDF trunk

groups, the DMUs that are members of each trunk group. If
the NTG is to be used as an LTF Replacement, add an X in
the field marked LTF Replacement on this page.
Associated calibration data for trunk groups (calibration

TNs, delta offsets, etc.)
Trunk-to-Trunk group mapping information, including

associated trunk-dialing information (rotary or multifrequency)
EMU Installation
Table 3-9.
ADEF Form
EMU (Cont)
Explanation
Trunk Communication-NTT or MDF trunk communication

refers to the information required to connect to the individual
DMUs which are serving as test trunks for the EMU. This
communication information includes the DMU test head TN
for modem dialup connections, and the Access Server ID
and Service Name for Access Server direct connects.
Associated NPANNX/Exchange Key (EXK) mapping to

Trunk Group
NPANNX/EXK testable by EMU
Switch ID for each NPANNX
Steering digits required to dial and access TNs in each

NPANNX
This is not a complete list of all the information required to enter an

EMU successfully in the LoopCare database. It is just an overview
of some of the more important data.
REGION
The REGION form provides data about the LoopCare

administrative region. Some key pieces of information include:
Primary and Backup LoopCare Machine Ids associated with

the region. The Backup LoopCare machine is optional.
Primary and Backup Administration Printer IDs for the

region. The Backup printer ID is optional unless a Backup
LoopCare machine is selected.
Table 3-9.
EMU Installation
ADEF Form
Access
Server
Explanation
The Access Server form provides details about the Access Server
and its different connections. Some key data that must be provided
includes:
Access Server ID - example achilles
IP address - example 121.1.35.65
Service name, TCP ID, and Serial Ports - Each function

provided on the Access Server should have a unique
service name, TCP ID, and Access Server serial port. In this
example the Access Server provides 4 different functions.
They are:
(1) Connection to 5ESS IOP on Port 1 (service name: 5eiop
TCP: 6001)
(2) Connection to NTT DMU on Port 2 (service name: accntt
TCP: 6002)
(3) Connection to MDF DMU on Port 3 (service name:
accmdf TCP: 6003)
(4) Connection to modems on Ports 4 and 5 (service name:
mpool TCP: 6004 and 6005)
3-22
EMU Installation
Table 3-9.
ADEF Form
SWITCH
Explanation
The ADEF SWITCH form provides a great deal of information
about the switch which is beyond the immediate scope of this
discussion. This section will only discuss the switch entries
required for basic EMU operation. These include:
Switch ID - The name of the switch, example whippany
Switch Type - Identifies the kind of switch, example 32

(ESS-5A)
5ESS Switch Communication Information - This information

is required if the OE retrieval feature is enabled. Important
information for this page includes:
(1) Enable 5ESS Communications: a checkbox indicating
on/off status
(2) User ID: the user login to the 5ESS IOP
(3) Communication Information about the connection to the
5ESS switch. Either modem dialup or direct connect
through the Access Server.
(4) Access Server ID and Service name associated with the
direct connect through the Access Server.
(5) Dial Group and TN associated with the modem dialup of
the 5ESS IOP.
UIP Procedures
Further
Information
Once all the LoopCare data has been entered and submitted into the ADEF
database, perform the following procedure:
1.
Activate the database through LoopCare UIP.
2.
Build the specific EMU entered.
3.
Build the region where the EMU is assigned.
4.
Stop and start MGRP. If you want the changes to take effect, you must stop
and restart MGRP.
5.
Download the EMUs through EMUadmin.
This is a simplified version of the LoopCare ADEF database entries and UIP
procedures needed to provide basic test service to an EMU. For more information
on entering the required data on the forms described above, see the Operation,
Administration and Maintenance (OA&M) Guide.
EMU Installation
Installation of EMU as Central Office

(CO) Wideband Test Head
EMU as Central Office (CO) Wideband
Test Head
Overview
The EMU Central Office (CO) Wideband test head is a logical entity that contains
one or more DMU Wideband test units (DMU-W). The DMU-W consists of a single
DMU enclosure which houses a DMU (for metallic assess and testing) and a
DWU (for wideband testing). This section address the following topics:
Physical DMU-W Test head Installation
Peripheral Equipment

NOTE:
A Central Office EMU may have multiple trunk groups. Each trunk group
must consist of the same type DMUs. That is the DMUs in any trunk group
must all be either metallic only test heads or wideband test heads. You
should not mix wideband and metallic DMUs in a single trunk group.
3-24
EMU Installation

Overview
The detailed procedures for physically installing the DMU-W as a Central Office
Test head are described in Chapter 2 of the DigiTest System Users Guide. This
document discusses the following topics:
Power
Grounding
Ringing supply
Fusing
After you have completed its physical installation, the DMU-W will be ready for
connecting to peripheral equipment and the internal test head configuration. Note
that the DMU-W is installed with the DMU. The DMU-W replaced one or more of
the DMUs in the test unit.
Peripheral
Equipment
The DMU CO Wideband test head is an external test head which accesses and
tests lines off of Loop Terminating Equipment (LTE) or switch MDFs. There are
two basic configurations for a DMU-W. These are:
LTE test head using TelAccord access
Standard loop test head using MDF access
Each of these configurations have their own unique peripheral equipment

requirements along with some basic standard setups.
TelAccord Access
Tollgrade DMUs
Tollgrade TelAccord
Telephone lines (modem and callback)
Access Server
MDF Access
Tollgrade DMUs
Telephone lines (modem and callback)
MDF test trunk
Access Server
EMU Installation
LoopCare
TCP/IP
Network
Access
Server
MODEMS
DMU-W
Switch
LTE
TelAccord
MDF
MDF Trunk
DMU-W
3
M
Figure 3-3.
DMU-W TelAccord and MDF Configurations

Legend:
1.
3-26
Access server is the interface to the DMU-W. The Access Server can either
connect directly to a DMU-W (as shown in the DMU-W TelAccord
configuration) or it can connect to the DMU-W via modempool dial-up (as
shown in the DMU-W MDF configuration). The cables and connectors used
EMU Installation
for the DMU-W direct connections are the same as the DMU-C direct
connections. A description of these cables are found in Appendix J of the
LoopCare Installation Guide. The CO test head direct connection is
recommended.
2.
The DMU-W connects to the TelAccord with three leads: Tip, Ring and
Sleeve. These leads effectively establish a No Test Trunk (NTT) access
through the TelAccord to the line under test. In very simple terms, the
TelAccord acts as a sort of switch. Customer lines coming from the Loop
Terminating Equipment (LTE) go into one side of the TelAccord and come
out the other enroute to the customer termination. In addition, the DMU-W
can access and test any LTE line using a special circuit ID (in the form of a
standard TN). More about this special TelAccord access TN will be
discussed later.
3.
A DMU-W can be configured for MDF access and be placed at the MDF.
Using the standard MDF test trunk access routine, the DMU-W connects to
the MDF trunk which is then manually connected to the line under test via a
patch cord (aka shoe).
a.
The access server modem pool is used to dial out and connect the test
heads which are setup for dialup instead of direct connection. The DMU-W
can be either a direct connect or dial-up. The figure illustrates one of each
type, although for CO test heads a direct connection is preferred.
EMU Installation

Overview
Possible DMU CO
Test Head
Configurations
Device Type
After the physical installation of the DMU has been completed, and all peripheral
equipment has been connected, the DMU must be configured for its particular
Device type: CO / Standalone RT test head
Miscellaneous set-up items; passwords, clock, etc.
Table 3-10 below lists the possible DMU CO test head configurations.
Table 3-10.
Possible DMU Configurations.
Connection
Test Port NTT/
Direct/
Modem
MDF

Baud
Parity
Data
Bits
Stop
Bits
Access
Parameters
DMU-C & WB
NTT
Direct
9600
Default
DMU-C & WB
MDF
Direct
9600
Default
DMU-C & WB
NTT
Modem
9600
Default
DMU-C & WB
MDF
Modem
9600
Default
NOTE:
For a CO test head application, a direct connection to the Access Server is
recommended over a modem dial-up.
when configuring the internal DMU database.
Device Type
For wideband applications an EMU device type can be configured as either a
Central Office (DMU-C & WB) or a Standalone Remote (DMU-R & WB) test head.
For this application, the appropriate device type will be DMU-C & WB.
3-28
EMU Installation
The device type entry is not just a label. It determines which test capabilities and
access routines the test head will perform.
The Device Type can be selected through the DMU-S Human Administration
(HADM) interface. From the HADM main menu, select Administration. From the
Administration menu, select Device Type and follow directions. Refer to the
Test Port Type

When the DMU-W is used as a CO test head, port trunk access can be either a
No Test or and MDF Trunk. The NTT selection enables the DMU Wideband test
head to access the line through the TelAccord device. The MDF selection will
provide access to the MDF trunk appearance.
The port type is entered through the DMU HADM interface, selecting Port Type
from the Administration Menu. Refer to the DigiTest System Users Guide for
Connection Type
DMU from LoopCare. They are:
If the DMU-W is used as a CO test head the direct connect is recommended.

The connection type determines which DMU communication port should be
configured. Table 3-11 lists all DMU communication ports, their function, and
specific data entry (if applicable) in HADM. For a DMU CO test head
EMU Installation
Table 3-11.

Configure Port
DMU Comm Port
Connection Type

Access Server
LoopCare DIRECT

PCa
TERMINAL DIRECT
Craft Access Directb
Modem Dialup
1.
DMU Connected to a PC is discussed in the DigiTest System Users

Guide.
2.
3.
It is possible for the DMU to be set up for both an LoopCare Direct connect
Notes:
1.
DMU connected to a PC is discussed in the DigiTest System Users

Guide.
2.
3.
It is possible for the DMU to be setup for both an LoopCare Direct connect
3-30
EMU Installation

Once you know whether the DMU is a direct connect or modem dialup you know
which DMU Communication Port to configure (see Table 3-11) Table 3-12 below
shows the valid values for other key port configuration data. For the DMU the
parameter values for both modem and direct connect DMU are the same.
Table 3-12. DMU Communication Port Parameter Values for DMU Direct Connect
or Modem Dial-up.
Parameter
Value
Baud Rate
9600
Parity
Data Bits
Stop Bits
1.
2.
Select the appropriate communication port for data entry. Refer to the
EMU Installation
Miscellaneous Setup
Miscellaneous Setup
Overview
EMUadmin (used only when the DMU is serving as a CO test head) interfaces.
EMU; refer to s. For more details on each timeout value and its default values, see
Chapter 4, EMU Administration of this guide.
Table 3-13 below lists the miscellaneous user-settable items, which interface they
can be populated through (HADM or EMUadmin) and the specific subitem or
option for each interface.
Table 3-13.
Entry
HADM Administration
Selection
EMUadmin
Timeouts
Additional Functions - 3
Option 1
Thresholds
Additional Functions - 3
Option 2
Clock
Set Clock
--
Password
Passwords
--
Status
Additional Function - 2
Options 6 and 7
DMUID
Additional Function - 1
--
Calibration
Calibration
--
Timeouts
DMU-W is delivered with default values for each timeout entry. Use those values
until there is a demonstrated need to tune the parameters. For more details on
each timeout value and its default values, see s. For more details on each timeout
value and its default values, see Chapter 4, EMU Administration of this guide.
These entries can be viewed or changed from both HADM and EMUadmin.
Thresholds
Threshold values represent the percent failure on trunks and equipment required
to report a problem to the user. The DMU-W is delivered with default values for
each timeout entry. Use those values until there is a demonstrated need to tune
3-32
EMU Installation
Miscellaneous Setup
the parameters. For more details on each threshold value and its default entries,
see s. For more details on each timeout value and its default values, see Chapter
4, EMU Administration of this guide. These entries can be viewed or changed
from both HADM and EMUadmin.
Clock
The clock option is used to set the DMUs internal clock. It is not a required
Password
The DMU-W has default passwords for a variety of user logins (for example,
HADM, LoopCare computer login, etc.). Although this is not a required setting, the
utility allows you to control user passwords for security purposes. For more
information on passwords, see the DigiTest System Users Guide.
The password entered in the DMU should match the password that is entered for
the DMU in the LoopCare ADEF database.
Status
DMU-W, Equipment, and Trunk status can be displayed or changed by using the
interface. For more information on DMU trunk and equipment status, see s. For
DMUID
The DMUID is the DMUs internal ID. It is usually set to match the DMU test head
ID entered in the LoopCare database. The DMUID is usually automatically
HADM interface.
Calibration
This is the DMUs internal calibration schedule and parameters, The DMU is
EMU Installation

Overview
3-34
There are a number of additional user-tunable entries ranging from timeouts to

thresholds that can be set. After data for the DMU has been entered (Device type,
Port Type, etc.), the DMU should be reset so that those changes can take effect.
This can be done through the DMUs HADM interface, Administration menu,
Reset DMU sub-item. Refer to the DigiTest System Users Guide. Note: If you
used the dial or nodial utilities to access HADM and an HADM menus
recommended method of leaving the menu does not work, use the following
sequence: press ESC ESC.
EMU Installation

(ADEF)
Overview

database entries required to setup the EMU for Wideband Testing. Table covers
the major ADEF forms required to enter an EMU. Some key pieces of information
on each form are discussed. Precise details on every LoopCare data entry for
EMUs, however, are not covered in this section. This is not an ADEF training
tutorial.
The goal of the section is to provide enough guidance to help you identify all the
forms and critical entries. It also helps establish the relationship between different
elements in the overall EMU configuration. For specific information about the
LoopCare ADEF database refer to the LoopCare OA&M Guide for Automated
Data Element Form (ADEF) Utility Administrators.
shown in the database example in Table .
EMU Installation
LoopCare
TCP/IP
Network
Access
Server
MODEMS
DMU-W
Switch
LTE
TelAccord
MDF
MDF Trunk
DMU-W
3
M
Figure 3-4.
3-36
Basic EMU Configuration with Database Entries
EMU Installation
ADEF Forms
Table 3-14.
ADEF Form
EMU
Explanation
The EMU form provides the detailed data for the EMU and all
associated DMUs. Some key data that must be provided includes:
Test head ID - range 800-1599, example 1000.
Region - Administration region which EMU is a member
Communication method - Either modem pool or access

server. For an EMU access server is preferred.

Dial Group - For modem pool connection only
Trunk Group information - Identify all NTT and MDF trunk

groups, and all DMUs that belong to each trunk group.
If the trunk group is served by wideband test heads, enter W
in the Wideband field on the NTG/MTG page. If W is
entered in this field, all DMUs in the trunk group must be
wideband test heads.
Associated calibration data for trunk groups (calibration

TNs, delta offsets, etc.)
Trunk-to-Trunk group mapping information, including

associated trunk-dialing information (rotary or multifrequency)
Trunk Communication - NTT or MDF trunk communication

refers to the information required to connect to the individual
DMUs which are serving as test trunks for the EMU. This
communication information includes the DMU test head TN
for modem dialup connections, and the Access Server ID
and Service Name for Access Server direct connects.
Table 3-14.
EMU Installation
ADEF Form
EMU (Cont)
Explanation
Associated NPANNX/Exchange Key (EXK) mapping to

Trunk Group. For wideband testing, if the wideband test
head belongs to an MDF Trunk Group, the associated
NPANNX are the same NPANNX found on the switch. If the
wideband test heads belong to a NTG, then tests will not be
made through the switch, but through a TelAccord device.
The NPANNX will be specially constructed NPANNXs to
identify the TelAccord. A special NPA will be defined by an
environmental variable found in the MGRP.env file. This
variable is called DSLNPA and consists of an unused NPA
for the system to identify a TelAccord access.
NPANNX/EXK testable by EMU
Switch ID for each NPANNX - for wideband tests through

NTG the switch ID must belong to a TelAccord switch entry.
See Switch Section.
Steering digits required to dial and access TNs in each

NPANNX
This is not a complete list of all the information required to enter an

EMU successfully in the LoopCare database. It is just an overview
of some of the more important data.
3-38
EMU Installation
Table 3-14.
ADEF Form
SWITCH
Explanation
The ADEF SWITCH form provides a great deal of information
about the switch which is beyond the immediate scope of this
discussion. This section will only discuss the switch entries
required for basic EMU operation. These include:
Switch ID - The name of the switch, example whippany
Switch Type - Identifies the type of switch for wideband

testing. An NTG TelAccord device must be used. A
TelAccord will appear as a switch in the LoopCare ADEF
Database. The switch type for TelAccord is "34".
5ESS Switch Communication Information - This information is

required if the OE retrieval feature is enabled. Important
information for this page includes:
(1) Enable 5ESS Communications: a checkbox indicating
on/off status
(2) User ID: the user login to the 5ESS IOP
(3) Communication Information about the connection to the
5ESS switch. Either modem dialup or direct connect
through the Access Server.
(4) Access Server ID and Service name associated with the
direct connect through the Access Server.
(5) Dial Group and TN associated with the modem dialup of
the 5ESS IOP.
REGION
The REGION form provides data about the LoopCare

administrative region. Some key pieces of information include:
Primary and Backup LoopCare Machine Ids associated with

the region. The Backup LoopCare machine is optional.
Primary and Backup Administration Printer IDs for the

region. The Backup printer ID is optional unless a Backup
LoopCare machine is selected.
Table 3-14.
EMU Installation
ADEF Form
Access
Server
Explanation
includes:
Access Server ID - example achilles
IP address - example 121.1.35.65
Service name, TCP ID, and Serial Ports - Each function provided
on the Access Server should have a unique service name, TCP ID,
and Access Server serial port. In this example below the Access
Server provides 4 different functions. They are:
TCP: 6001)
TCP: 6002)
accmdf TCP: 6003)
3-40
Dial Group
Only for dial up connection and is not recommended.
Modem
Pool
Only for dial up connection and is not recommended.
EMU Installation
Installation of a DMU as an RT Test

Head
Overview
The DMU test head can also be located at the Remote Terminal of a Digital Loop
Carrier (DLC) system or to support testing of lines served by a 5ESS EAIU. This
configuration is called an RT test head or DMU-R. This section discusses the
following topics:
Physical DMU Test head Installation at an RT
LoopCare ADEF Database Entries for Configuring RT Test head
Attached DWU for Wideband
Note that these are high-level description only. Wherever more detail is required,
specific references will be provided.
For configuring the ADEF database for a DMU-R that is to test EAIU-supported
lines, see Chapter 12 of the System Administration Guide.
Environmental
Specifications
The RT test head is designed to reside and operate in a remote terminal

environment. The test head should be readily mounted in the RT equipment bays.
Refer to the DigiTest System Users Guide for more details on the environmental
specifications.
EMU Installation
Physical DMU Test Head Installation at

an RT
Overview
When you complete the physical installation, the DMU is ready to be connected to
peripheral equipment and for internal parameters to be configured.
The detailed procedures for installing the DMU in the RT are found in the DigiTest
System Users Guide.
Peripheral
Equipment Setup
In order to operate, the DMU must connect to a variety of peripheral equipment,

including telephone lines and RT test access ports. These topics are discussed in
later sections of this Guide.
Figure 3-5 below shows an overview of a system architecture with a DMU RT test
head and associated peripheral equipment.
1
I
D
L
C
Remote
Terminal
CPE
6
Switch
3
DMU
Optional
DWU
4
Modem
5
Figure 3-5.
Basic RT Test head Configuration.

3-42
EMU Installation
Legend:
1.
Switch-Integrated Digital Loop Carrier (IDLC) Central Office circuit.
2.
IDLC Remote Terminal
3.
Test access Port that permits the DMU to connect to customers drop
through the IDLCs RT.
4.
The DMU RT Test head.
5.
Modem dial-up to the DMU RT test head. This dial-up comes from an
Access Server modem pool.
6.
The DMU RT can also be direct connected via an access server.
7.
Customer Drop. Tip and ring of customer cable pair from RT to customer
premises.
EMU Installation

When the physical installation of the DMU is complete, and all peripheral
equipment connected, the DMU must be configured for the RT test head
application. This requires you to define or verify data in the following areas:
Overview
Device type: CO or RT
Port type: Not applicable for RT
Connection type: Direct or dial-up
Miscellaneous setup items: passwords, clocks, etc.
Table 3-15 lists the preferred DMU RT test head configuration.
Preferred DMU RT
Test Head
Configuration
Table 3-15.
DMU R Test head Configuration
Connection
Direct/
Modem
Port NTT/
MDF
Device Type

Baud
Data
Bits
Parity
Stop
Bits
Access
Parameters
DMU-R
--
Direct
9600
Default
DMU-R
--
Modem
9600
Default
DMU-R & WB
--
Direct
9600
Default
DMU-R & WB
--
Modem
9600
Default
Device Type
A DMU can be used as either a CO or RT test head and the Device Type indicates
which one. This entry is not just a label. It determines which test commands the
DMU will accept.
The Device type for an RT test head is DMU-R or DMU-R & WB. Enter the value
through the Device Type option on the Administration Menu in DMUs Human
Administration (HADM) interface. Refer to the DigiTest System Users Guide for
Port Type
Port Type is not required for an RT test head.
3-44
EMU Installation
Connection Type
An RT test head connection type is a modem dial-up or direct connect. The
DMUs modem port is referred to as Communication Port 3 and is the port that
must be configured (see Table 3-2).
1.
Enter the value for the Connection Type through the Configure Ports option
on DMUs HADM interfaces Administration Menu.
2.
Select the appropriate communication port for data entry. This option also
allows you to enter other port configuration data that is be discussed in the
next section. Refer to the DigiTest System Users Guide for more
information on HADM.
Comm Port Configuration

Once you identify the connection type and the proper communication port to
define on the DMU you can enter other connection parameters. These parameters
and the associated values for a modem dialup connection are found in Table 3-16
below.
Table 3-16.
DMU Communication Port Parameters for Modem Dial-up

Parameter
Value
Baud Rate
9600
Parity
Data Bits
Stop Bits
1.
Enter these parameter values for Connection Type through the Configure
Ports option on DMUs HADM interface Administration Menu.
2.
Select the appropriate communication port for data entry. Refer to the
Miscellaneous Setup
Table 3-11 lists all user-tunable settings for the DMU. An RT test head should use
the default values for all settings until you have a specific need to change them.
See s. For more details on each timeout value and its default values, see Chapter
4, EMU Administration of this guide and the DigiTest System Users Guide.
NOTE:
3-46
EMU Installation
EMU Installation

Overview
After data for the DMU has been entered (Device type, Port Type, etc.) the DMU
should be reset so that those changes can take effect. This can be done through
the DMUs HADM interface, Administration menu, Reset DMU sub-item. Refer to
the DigiTest System Users Guide.
EMU Installation
3-48
EMU Installation
Configuring the DMU+ to Work with

LoopCare
Overview
It is necessary to physically modify the DMU+ in order for the DMU+ to inter-work
with LoopCare. The Physical Modification of the DMU+: page 3-49 and
Provisioning the DMU+ Firmware: page 3-51 sections provide high level
guidelines for the configuration of the DMU+. For more detail and diagrams, see
the DMU+ test head and firmware user manuals.
Physical
Modification of the
DMU+
The following table summarizes the settings for the DMU+ Extnet Selector and the
J13, J20, J21, and J22 jumpers required by each of the DMU+ configurations. It is
also necessary to configure the DMU+ firmware to support the selected
configuration.
Table 3-17. Physical Settings for the DMU+

DMU+ Configuration
DMU+ Master IP Connect
Physical Settings
Set the Extnet Selector Id to 1.
Viewing the front of the DMU+
The J20 jumper should be on

the bottom three rows of pins
and the top row should be
uncovered.

the bottom three rows of pins
and the top row should be
uncovered.

the left most two columns of pins
and the other columns of pins
should be uncovered.

the right most two columns of
pins and the left most column of
pins should be uncovered.
EMU Installation

DMU+ Configuration
DMU+ Intermediate Extender
Physical Settings
Set the Extnet Selector Id from 2 to 8,
depending on the number of the
intermediate extender.
3-50

the top two rows of pins and the
bottom row should be
uncovered.

uncovered.

the second from the left and
third from the left columns of
pins and the other columns of

and the right most column of
EMU Installation

DMU+ Configuration
DMU+ Terminated Extender
Physical Settings
Set the Extnet Selector Id to 2 to 8,
depending on the number of
terminating extenders.

uncovered.

uncovered.

the right most two columns of
pins and the other columns of

and the right most column of
DMU+ Communication via External

Access Server
Same settings as DMU+ Master IP

Connect.
DMU+ Communication via Modem

Card
Same settings as DMU+ Master IP

Connect.
NOTE:
In the DMU+ Master IP Connect configuration with Extenders, the
Extenders are connected to the Master via ARCNET wiring in the rear of
the DMN housing. See the DMU+ Test Head Users Manual for more details.
Provisioning the
DMU+ Firmware
At this point it is assumed that the DMU+ is physically installed and powered and
that all other network elements required to support DMU+ communication are in
place.
It is necessary to answer certain questions about the configurations used by the
DMU+, its physical configuration, and its connections to other equipment in order
EMU Installation
to determine how to configure the DMU+ firmware. The following table presents
configuration guidelines based on these questions.
Table 3-18. Guidelines for Configuring the DMU+ Firmware

Question
Will LoopCare communicate with the
DMU+ Master or Extenders?
Database Configuration Guidelines

If yes, then:
1.
Connect the IP cable from the

network to the Ethernet port on
the front of the DMU+.
2.
Identify the following items:
DMU+ IP address
Gateway IP for DMU+ to

use in customer network
ARCNET Routine Table
Subnet Mask for DMU+

to use in customer
network
Go to the DMU+ Firmware

Network Provisioning: page 3-55
for more information on how to
enter this data in the DMU+.
3-52
3.
After the network information

has been entered and the DMU+
rebooted attempt to telnet and
login to the DMU+ to verify the
communication link is working.
4.
Check the network data for the

DMU+s serial ports. See the
DMU+ Firmware Network
Provisioning: page 3-55 section
for more information.
EMU Installation

Question
DMU+ via the Ethernet through
external access server method?

If yes, then:
1.
Connect a port on the access

server to the J8 or J10 port on
the rear of the DMN using the
appropriate cable. The DMU+
mounts on the left or right slot of
the DMN.
2.
Identify the following information

about the access server:
Type of access server
IP address of the access

server.
Serial port/TCP id used to

communicate to DMU+
Serial port configuration

parameter values
required to communicate
to the DMU+ (e.g. baud
rate, parity, bits, stop bits,
etc.).
3.
Configure the access server

database with the data listed
above. Follow the procedures
provided by the access server
vendor.
4.
Telnet and login to the DMU+ to

verify that the communication
link is working.
EMU Installation

Question
DMU+ via the RAC analog modem by
direct dial-up?

If yes, then:
1.
Connect the telephone line to

the RAC internal modem port.
2.
Identify the following

information:
Telephone number used
to connect to the DMU+
analog modem.
The baud rate used to
connect to the DMU+
RAC analog modem.
See the section on DMU+ Serial
Port Provisioning: page 3-56 for
information on how to enter port
data for the DMU+ modem
connection.
3.
DMU+ Craft Port

Interface
After provisioning the DMU+

modem for dial-up
communication, use the dial
utility to connect to the DMU+
and log in.
Under certain conditions, the only method of communicating to the DMU+ is

through the craft or serial port.
When no Ethernet, access server, or modem communication path to the

DMU+ has been established.
One way to connect to a DMU+ craft or serial port is via a direct connection from
the COM1 port on a PC using a program such as Hyperterminal. Table 3-19 on
page 3-55 specifies the required craft or serial port communication parameter
values.
3-54
EMU Installation
Table 3-19. Craft or Serial Port Communication

Information
Communication Parameters
DMU+ Firmware
Network
Provisioning
Baud = 38400
Parity = N
Bytes = 8
Stop Bits = 1
Flow = XON/XOFF
Network data for the DMU+ is configured by logging on to the DMU+ via telnet or
Hyperterminal and using the "supervisor" login. The "router" command takes you
to the router directory. Table 3-20 on page 3-55 describes some key network
configuration commands that are used in the router directory.
Table 3-20. DMU+ Network Configuration Commands

DMU+ Command
Command Description
DEFAULTIP
Add or change the IP address of the

DMU+.
GATEWAY
Add or change the gateway address of

the DMU+.
SUBNET
Add or change the subnet mask of the

DMU+.
DNS
Add or change the DMU+'s DNS IP

address.
ARCCON
Display or set ARCON value.

Enter "ARCON ALT" for modem
configuration or "ARCON STD" for all
other configurations.
DISPLAY
Display network data specific to the

DMU+ serial ports, including their IP
addresses, TCP IDs, timeout values,
routing table and port names.
EMU Installation
Table 3-20. DMU+ Network Configuration Commands

DMU+ Command
Command Description
EXTNET
Display status of the ARCNET.
LoopCare requires a specific TCP ID for each DMU+ serial port. Table 3-21 on
page 3-56 specifies the required TCP IDs.
Table 3-21. TCP IDs Required By LoopCare for DMU+ Serial Ports
DMU+ Device
Port Description
Port TCP ID
Master
Serial port 1
6000
Master
Telnet port
23
Extender 1
Serial port 2
6110
Extender 2
Serial port 3
6210
Extender 3
Serial port 4
6310
Extender 4
Serial port 5
6410
Extender 5
Serial port 6
6510
Extender 6
Serial port 7
6610
Extender 7
Serial port 8
6710
It is necessary to reboot the DMU+ to activate network changes. To reboot, run

the ADMIN command followed by the RESET command on the DMU+ command
menu or power cycle the DMU+.
DMU+ Serial Port

Provisioning
3-56
To enter port configuration data use the PORT command to take you from the
main level of the command menu to the port data entry level.Table 3-22 on page
3-57 describes some key commands that can be entered on the port data entry
level. Changes take place immediately without a reboot of the DMU+.
EMU Installation
Table 3-22. DMU+ Port Configuration Commands

DMU+ Command
Command Description
DISPLAY
Display port data, such as port name,

baud rate, bytes, parity, etc.
CHANGE X
Edit port data.

X = 1 or 4 (port number).
See Table 3-23 on page 3-57.for a
description of each DMU+ port.
Table 3-23 on page 3-57 specifies the values for the Name and Port fields that are
required for the DMU+ to work with LoopCare.
Table 3-23. DMU+ Port Name and Port Field Values

Port Name Field Value
Port Field Value
PORT1
COM1
PORT2
No access
PORT3
No access
PORT4
COM4
PORT5
No access
PORT6
No access
PORT7
No access
PORT8
No access
PORT9
No access
Table 3-24 on page 3-57 provides the settings for a direct serial port connection to
a TelAccord or DAU 1000.
Table 3-24. Settings for a Direct Serial Port Connection to a
TelAccord or DAU 1000
Parameter
Setting
NAME
DSLAM1
PORT
COM4
EMU Installation

Parameter
Setting
BAUD
19200
PAR
WORD
STOP
ECHO
OFF
RTS
OFF
CTS
OFF
DTR
OFF
DEV
DTE
CONN
DIRECT
Settings for a Direct Serial Port Connection to an ASAM 7300: page 3-58
specifies the settings for a direct serial port connection to an ASAM 7300.
Table 3-25. Settings for a Direct Serial Port Connection to an ASAM 7300
Parameter
3-58
Setting
NAME
DSLAM1
PORT
COM4
BAUD
9600
PAR
WORD
STOP
ECHO
OFF
RTS
ON
CTS
ON
DTR
ON
DEV
DTE
CONN
DIRECT
EMU Installation
LoopCare DMU+ Database

Configuration?
Overview
The DMU+ is configured in the ADEF database in the same way as the DMU, but
several automated procedures described below further refine the database
records for DMU+/DMU+Ls.
Considerations
If the DMU+L is the only DMU in an EMU in an office with an LTS/DCTU, it is

recommended that the EMU not be selected as the primary.
For 5ESS NTT test trunks served by a DMU+L the trunk padding resistors must
be removed. In general, 5ESS NTT test trunks served by a DMU should also have
the padding resistors removed for better measurement accuracy.
Entering a DMU+
into the ADEF
Database
The DMU+ and DMU+L are identified by LoopCare when it logs into the
respective test head. No user action is required.This identification occurs on every
LoopCare test request that accesses the DMU+. It also occurs when the SAM
DLOAD and TC requests are executed.
Upon connecting to a DMU-type testhead LoopCare determines the type of DMU
and updates the database and display on the screens noted below. The following
are the values inserted by LoopCare.
DMU = Standard DMU
DMU+ = DMU+
DMU+L = DMU+LIL module
UND = Undiscovered.
Default: UND.
Identifying a DMU+ as an EMU NTT MDF

The results are shown in the read-only "Test Head" field on the OAM/ADEF/EMU/
NTT form. The field applies only to DMU+s or the OAM/ADEF/EMU/MDF TRUNK
form.
EMU Installation
Identifying a DMU+ as an RMU or RMU-S

Once LoopCare identifies the type of DMU, it populates the read-only DMU Type
fields on the OAM/ADEF/RMU/RMU and OAM/ADEF/RMU/RMU-S forms.
Calibrating the
DMU+LIL Module
In order to perform loop insertion loss measurements, follow the procedure

outlined in the LoopCare Administration section of the System Administration
Guide for calibrating the switch using the REF0 command.
LoopCare DMU(2) Database

Configuration
Overview

database entries required to set up the DMU as an RT Test head. Table 3-12 lists
the major ADEF forms required to enter a DMU as a RT test head. Key pieces of
information are discussed after the table. However, precise details on every
LoopCare data entry are not covered in this section. For more details about using
ADEF, see the LoopCare Operation, Administration, and Maintenance (OA&M)
Guide. This section is intended to provide only enough guidance to help you
identify all the forms and critical entries. It also helps establish the relationship
between different elements in the overall configuration.
Figure 3-6 and Figure 3-7 show the dial-up and direct connect configurations with
key items labeled as they are shown in the database example in Table . For this
3-60
EMU Installation
example assume higher level database entries (DCN, Region) have already been
entered since they will not be
I
D
L
C
Remote
Terminal
CPE
Switch
IOP
Modem Pool
Svc Name
5eiop
Svc Name
mpool
Access Server
achilles (121.1.35.65)
Figure 3-6.
RMUid=1
Thid=1000
DCNid=1
DMU-R
Modem
DMU as Remote Test head (Dial-up) with Database Entries (in bold).
EMU Installation
I
D
L
C
Remote
Terminal
CPE
Switch
IOP
Svc Name
5eiop
Svc Name
DMU-R
RMUid=1
Thid=1000
DCNid=1
DMU-R
Access Server
achilles (121.1.35.65)
Figure 3-7.
3-62
DMU as Remote Test head (Direct Connect) with Database Entries (in
bold).
EMU Installation
ADEF Forms
Table 3-26.
LoopCare ADEF Data Entry for LTE-RMU Test Head
ADEF Form
RMU
Explanation
The RMU form provides the detailed data for the DMU set up as
the Remote Terminal (RT) which is known in ADEF as the LTERMU test head. Some of the key information includes:
RMU Test head ID - range 800-1599, example 1.
Test head ID - The CO Test head ID associated with the

RMU, example 1000
DCN - The DCN ID associated with the CO Test head,

example 1
RMU TYPE - Standard, DMU or DMU-W

Communication method - Either modem pool, datakit or

access server
Dial Group - For modem pool connection only (Dial-up only)
Test Head TN - The TN used to dial up the RT Test head

modem (Dial-up only)
Access Server Id and Service Name (Direct Connect only)
For customer environments with LMOS line records, the LTE-RMU

page of the RMU needs to be completed. The information required
for this page includes:
Switch ID of the switch serving the LTE
The LTE ID associated with the RMU
This information is linked with the data on the SWITCH-LTE and

SWITCH-OE pages of the LoopCare ADEF Switch form.
For customer environments with LMOS line records, the
information on the LTE-RMU page of the RMU form is not required.
For a more detailed explanation of how the SWITCH-LTE and LTERMU data is used for RMU testing, see the section "Identifying the
RMU" found later in this chapter.
This is just an overview of some of the more important data
required to enter RMU data.
Table 3-26.
EMU Installation
ADEF Form
Access
Server
Explanation
includes:
Access Server ID- example achilles
IP address- example 121.1.35.65
Service name, TCP ID, and Serial Ports- Each function

They are:
TCP: 6001)
TCP: 6002)
accmdf TCP: 6003)
(5)Connection to RT DMU (service name: rmu3 TCP:6006)
DIAL
GROUP
3-64
The DIAL GROUP form provides part of the dial string used to dial
to the RT test head. It also points to the modempool that will
actually dial out. Some important items on this form include:
Dial Group ID- Number from 1-200.
Prefix- Dial prefix that is part of the dial string. Usually this is
the NPA for the RT Test heads TN.
Modempool ID- This is the ID of the modempool that

actually dials up the RT Test head. The modempool ID must
be a number from 1-200.
EMU Installation
Table 3-26.
ADEF Form
MODEM
POOL
Explanation
The MODEMPOOL form identifies the modempool that actually
dials the RT test head and also provides part of the dial string used
to connect dial out. Some important information includes:
Modempool ID - a number from 1-200.
Dialout digits - part of the dial string for the RT test head.
Usually the prefix to get an outside line or reach long
distance, (9 and or 1).
Modempool Type - local (not recommended for DMU), datakit (also

not recommended for DMU), access server (recommended for
DMU).
The access server entry indicates that the modempool is coming
off an Access Server which has the certified modem types to
connect to a DMU.
Table 3-26.
EMU Installation
ADEF Form
SWITCH
Explanation
Depending on the customer environment (RBOC or GCM) different
entries are required in the ADEF Switch form for RMU testing.
In the RBOC environment, entries in the SWITCH-LTE page of the
Switch form is mainly associated with features like DLC Loop
Calibration and doesnt really impact RMU testing.
In the GCM environment, entries in both the SWITCH-LTE and
SWITCH-OE pages of the Switch form are required to perform
RMU testing.
A more detailed explanation of how this information is used in RMU
testing is found in the section on Identifying the RMU: page 3-68.
The specific entries required for the GCM market in both the
SWITCH-LTE and SWITCH-OE page are listed here.
For the SWITCH-LTE page:
LTE ID
LTE Type (ISLC, USLC, or EAIU)
Test Method (This identifies whether the line is tested via a

bypass pair or an RMU. When the test method indicates
RMU additional information is required in the SWITCH-OE
page for the switch.)
For the SWITCH-OE page:
UIP Procedures
3-66
OE type (identifies the type of OE format for the lines served

by the LTE. Knowledge of the format is important for
correctly parsing the OE.
Low and High OE range. (This marks the range of OE

numbers associated with a particular LTE.)
LTE ID (associated with OE range and OE type and should

be an LTE listed on the SWITCH-LTE page.)
After all LoopCare data has been entered and submitted into the ADEF database,
activate the database through the LoopCare UIP.
EMU Installation
Further
Information
This is a simplified outline of the ADEF entries and UIP procedures needed to
configure a DMU as an RT Test head. For more information on entering the
required data on the forms described above, see the Operation, Administration
and Maintenance (OA&M) Guide.
EMU Installation
Identifying the RMU
Identifying the RMU

Overview
Before you can test with an RMU you must first determine that the line is RMUtestable, and then you must identify the specific RMU that will perform the test. In
the RBOC world both of these items are accomplished through the LMOS line
records. In the line record there is a field called LRRMU. If that field is populated,
then the line is RMU-testable. The value of the LRRMU field is the RMU ID. (Note
the complete RMU ID is the DCN and Test head ID of the CO test head that works
with the RMU, plus the RMUID from the LRRMU field. For example if the CO test
head is DCN 1 Thead 8 and the LRRMU ID is 4, the complete RMU ID is 1-8-4.)
LoopCare then accesses the database to retrieve all relevant information needed
to connect to that RMU and proceeds to get access and test. To summarize the
RBOC RMU world: RMU testability is determined on a line-by-line basis through
the line records.
In the GCM environment, line records are not available so RMU testable lines and
the RMUs that test them have to be identified in a different way. This is done by
retrieving the OE of every line tested, and then searching the database to see if
that OE is associated with an RMU. The user must then identify all the LTEs for all
switches in their environment. This information goes into the respective Switch
forms in ADEF on the SWITCH-LTE page. If the LTE is testable by an RMU, it is
indicated as such in the test method field of the SWITCH-LTE page. Next the OE
range for each LTE is entered in the SWITCH-OE page of the Switch form. At this
point you have a map between a Switch/OE and a particular Switch/LTE
combination. Next, on the RMU form the Switch and LTE(s) associated with the
RMU are entered in the SWITCH-LTE page of the RMU.
When a test is run in a GCM environment, LoopCare retrieves an OE from the
switch serving that line. The OE is examined to determine the associated LTE.
Once the LTE has been identified the database is further examined to see if the
test method for that LTE is RMU. If it is then the RMU is identified by searching the
RMU database for a match on Switch/LTE combination. Once the associated
RMU has been identified, LoopCare retrieves all relevant information needed to
connect to that RMU and proceed with access and testing. To summarize the
GCM RMU world- RMU testability is determined from the Switch OE. The OE is
mapped to a Switch/LTE, if the LTE is RMU testable, the Switch/LTE is then linked
to an RMU.
3-68
EMU Installation
Using an RMU to Test EAIU-supported

Lines
Introduction
EAIU lines tested by an RMU are treated in a very similar way to DLC lines tested
by an RMU. A few initial tests (LOOP, FULL, MET, BENCH, QUALX, TONE(+),
LCOILX, DCOILX, REF1, REF2 and LDX) cause testing to switch from the EMU
at the Host or RSM to the RMU at the EAIU. Once the switch to the RMU is done,
a wider set of subsequent tests can be performed on the loop. The MON test can
also be used as an initial test when a line is traffic busy, but this only sets up the
monitor at the Host using the EMU and does not result in a switch to the RMU.
LOOP, FULL, MET, BENCH, QUALX, TONE(+), LCOILX, DCOILX, REF1, REF2,
LDX and MON on a busy line are the only initial test requests that are allowed on
RMU-tested EAIU lines. On a traffic busy line, the MON test is done solely by the
EMU with no transfer to the RMU. All other initial test requests are blocked with a
suitable message that instructs the user to do a LOOP or FULL test first.
After testing switches to the RMU at the EAIU site, all testing is done by the RMU.
The CO test (and the CO portion of the FULL test) however require the EMU to
manipulate the sleeve lead at the Host to establish bridged access at the EAIU.
Once all testing is complete, the EMU drops access.
Table 3-27 lists the tests that can be done before and after the switch to the EAIU/
RMU. All other tests are rejected with appropriate messages.
Table 3-27.
Use of DMU-R in Testing Lines Supported by an EAIU
REQUEST
Allowed After
"Bypass"
Allowed Before
"Bypass" (Initial) (Subsequent)
Comments
BENCH
If BMDB feature is on.
CHANGE
Not a metallic test Changes Info Line Text
CO
DCOILX
X
X
DIAL
X
X
DISP
FULL
Not a metallic test retrieves BMDB data
Table 3-27.
EMU Installation
REQUEST
Allowed After
Allowed Before
"Bypass"
INFO
Not a metallic test - Gives

Line Information
KEEP
Not a metallic test Extends access timeout
LCOILX
LDX
Comments
This test is accessible

only to the Loop Detect
process. (see the section
on "LDX Test Algorithm."
in Chapter 1 of the Loop
Detection manual).
Access is dropped after
the test.
LOOP
LRM
MET
MON
Initial allowed only on a

traffic busy line
QQUAL
Not a metallic test retrieves BMDB data
QUALX
QUICK
REF1
REF2
REV
RING#
RING
RINGER
SOAK
TALK
TONE
3-70
EMU Installation
Table 3-27.
REQUEST
Allowed After
Allowed Before
"Bypass"
TONE+
TT
XCB
XTONE
Comments
EMU Installation
Installation of a Standalone Remote Test

Head
Overview
Traditionally a DMU could be located at the Remote Terminal of a DLC system to

provide test capability at that point. This is the DMU-R configuration defined
earlier.
A regular DMU-R is always associated with a central office test head (LTS, DMUC, etc.) and can only run metallic tests. In some configurations a DMU-R can
operate as a standalone test head at a remote Loop Terminating Equipment (LTE)
test site. In this standalone mode, the remote test head will be independent of a
CO test head or even associations to a switch.
This section covers the following topics:
Physical DMU or DMU-W Installation of an LTE
RMU-S Internal Configuration
LoopCare ADEF Database Entries for Configuring Standalone RT

Test head
Note that these are high-level descriptions only. Wherever more detail is required,
specific references will be provided.
Environmental
Specifications
3-72
A Standalone Remote Test Head is a DMU-R or DMU-W designed to test lines on

Loop Terminating Equipment (LTE). Refer to the DigiTest System Users Guide for
more details on the environmental specifications.
EMU Installation
Physical DMU/DMU-W Installation at an

LTE
Overview
When you complete the physical installation, the Standalone Remote test head is
ready to be connected to the LTE and to have its internal parameters configured.
For this application, the standalone remote DMU will be connected to the tip and
ring leads of the LTEs test access port (TAP).
The detailed procedures for installing the DMU in the RT are found in the DigiTest
System Users Guide.
Peripheral
Equipment Setup
In order to operate, the DMU must connect to a variety of peripheral equipment,

including telephone lines and Loop Terminating Equipment (LTE) test access
ports. These topics are discussed in later sections of this Guide.
Figure 3-8 below shows an overview of a system architecture with a DMU LTE
test head and associated peripheral equipment
LTE
MTAU
Switch
IF
TAP
1
CUSTOMER
DMU-Rs
LoopCare
Figure 3-8.
TCP/IP
Network
MODEM
POOL
ACCESS
SERVER
Basic Standalone Test head Configuration.
EMU Installation
Legend:
3-74
1.
Loop Terminating Equipment (LTE) - provides wideband services to

customers. It also provides the Test Access Port (TAP) to interface to the
DMU/DMU-W test head. Internally, the LTE connects the test head to the
line under test. It must be associated with the Standalone RMU. This is
done through the ADEF Database.
2.
The Standalone Remote Test head can either be a regular DMU, which has
metallic test capability only, or it can be a DMU-W which has both metallic
and wideband capability. The Standalone RMU must be associated with
the LTE through ADEF. As with all DMUs, the Standalone Remote Test
head can be either directly connected off an access or server or dialed-up
through an access server modem pool. In this example, a direct connection
is shown. All cables and connectors for a direct connect are the same as a
standalone DMU.
3.
Test control interface. This is a line through a TCP/IP network between the
LoopCare processor and the LTE is used to control the test access
process. For example with a Stinger DSLAM this interface is an SNMP link.
EMU Installation

The Standalone Remote Test head must be configured as either a RMU-S or a
RMU-S Wideband. In addition, the follow items need to be set up through the
HADM interface.
Overview
Preferred DMU-R
Standalone Test
Head Configuration
Device Type
Device type: DMU-R or DMU-R WB
Port type: Not applicable
Connection type: Direct or dial-up
configuration Port: RS-232 or Internal Modem
Miscellaneous setup items: passwords, clocks, etc.
Table 3-28 below lists the preferred DMU-R Standalone test head configuration.
Table 3-28.
DMU RT Test Head Configuration
Connection
Test Port NTT/
Direct/
Modem
MDF

Baud
Parity
Data
Bits
Stop
Bits
Access
Parameters
DMU-R
Direct
9600
Default
DMU-R
Dial up
9600
Default
DMU-R & WB
--
Direct
9600
Default
DMU-R & WB
--
Dial up
9600
Default
NOTE:
While it is possible to connect a DMU-R Standalone Test head directly to an
Access Server, that configuration is highly improbable and will not be
considered here.
Device Type
A Standalone remote test head can either be a standalone or a wideband test
head. Depending upon the application, the device type will be either a DMU-R or
DMU-R & WB.
EMU Installation
The device type for a standalone remote test head is entered through the Human
Administration (HADM) interface. Refer to the DigiTest System Users Guide for
Test Port Type

Port Type is not required for an RT test head.
Connection Type
An RT test head connection type is a modem dial-up. The DMUs modem port is
referred to as Communication Port 3 and is the port that must be configured (see
Table 3-2).
1.
Enter the value for the Connection Type through the Configure Ports option
on DMUs HADM interfaces Administration Menu.
2.
Select the appropriate communication port for data entry. This option also
allows you to enter other port configuration data that is be discussed in the
next section. Refer the DigiTest System Users Guide for more information
on HADM.
Comm Port Configuration

Once you identify the connection type and the proper communication port to
define on the DMU you can enter other connection parameters. These parameters
and the associated values for a modem dialup connection are found in Table 3-29
below.
Table 3-29.
DMU Communication Port Parameters for Modem Dial-up

Parameter
Value
Baud Rate
9600
Parity
Data Bits
Stop Bits
1.
Enter these parameter values for Connection Type through the Configure
Ports option on DMUs HADM interface Administration Menu.
2.
Miscellaneous Setup
Table 3-11 lists all user-tunable settings for the DMU. An RT test head should use
the default values for all settings until you have a specific need to change them.
3-76
EMU Installation
See s. For more details on each timeout value and its default values, see Chapter
4, EMU Administration of this guide and the DigiTest System Users Guide.
NOTE:
EMU Installation

After data for the DMU has been entered (Device type, Port Type, etc.) the DMU
should be reset so that those changes can take effect. This can be done through
the DMUs HADM interface, Administration menu, Reset DMU sub-item. Refer to
3-78
EMU Installation

Overview

database entries required to set up the DMU as an Standalone RT Test head.
Table 3-12lists the major ADEF forms required to enter a DMU as a Standalone
RT test head. Key pieces of information are discussed after the table. However,
precise details on every LoopCare data entry are not covered in this section. For
more details about using ADEF, see the LoopCare Operation, Administration, and
Maintenance (OA&M) Guide. This section is intended to provide only enough
guidance to help you identify all the forms and critical entries. It also helps
establish the relationship between different elements in the overall configuration.
shown in the database example in Table 3-30. For this example assume higher
level database entries (DCN, Region) have already been entered since they will
not be discussed here.
LTE
MTAU
Switch
IF
TAP
1
CUSTOMER
DMU-Rs
LoopCare
Figure 3-9.
TCP/IP
Network
MODEM
POOL
ACCESS
SERVER
DMU as Remote Test head with Database Entries
EMU Installation
ADEF Forms
Table 3-30.
3-80
LoopCare ADEF Data Entry for Standalone RT Test head
ADEF Form
Explanation
RMUStandalone
The RMU Standalone form provides the detailed data for the DMU
set up as the RT Standalone Test head. Some of the key
information includes:
RMU-S Sequence No - A system generated number which

is used to associate the RMU-S with an LTE. This number
must be populated on the associated LTE Data Element
Form.
RMU-S ID - ID used by LoopCare to address an RMU test

head.
Communication Info - The communication equipment

needed to connect to the test head. Either Modempool or
Access Server.
Dial Up Group - The Dial group owning the device, used if

Modempool was selected on the Communication Info field.
Test Head TN - Phone number of the test head.
Call Back Dialing - Rotary or Tone.
RMU-S Type - Enhanced or Wideband. If Enhanced is

selected, the RMU-S is capable of load coil testing. If
Wideband is selected, the RMU-S is capable of wideband
testing.
Access Server ID - A unique identifier for the access server,

used if Access Server was selected on the Communication
Info form.
Service Name - A unique identifier for the Service Name of

the TCP service port number. Used if Access Server was
selected on the Communication Info form.
Computer Password - Password for computer access.
Human Password - Password for local access.
EMU Installation
Table 3-30.
ADEF Form
LTE
Access
Server
Explanation
The LTE form provides detailed about communication information
and access method along with the associated RMU-S identification
number. Some key data that must be provided includes:
LTE ID - a unique identifier of the Loop Terminating

Equipment.
Metallic Testing - indicates whether metallic testing is

allowed.
ID Address - The IP address of the LTE.
RMU-S Sequence No. - This is a system generated number

from found on the RMU-S screen. This association simply
indicates which RMU-S can test the LTE.
includes:
Service name, TCP ID, and Serial Ports- Each function

They are:
TCP: 6001)
TCP: 6002)
accmdf TCP: 6003)
Table 3-30.
EMU Installation
ADEF Form
DIAL
GROUP
Explanation
The DIAL GROUP form provides part of the dial string used to dial
to the RT test head. It also points to the modempool that will
actually dial out. Some important items on this form include:
Dial Group ID- Number from 1-200.
Prefix- Dial prefix that is part of the dial string. Usually this is
the NPA for the RT Test heads TN.
Modempool ID- This is the ID of the modempool that

actually dials up the RT Test head. The modempool ID must
be a number from 1-200.
The MODEMPOOL form identifies the modempool that actually

MODEMPO dials the RT test head and also provides part of the dial string used
OL
to connect dial out. Some important information includes:
Modempool ID - a number from 1-200.
Dialout digits - part of the dial string for the RT test head.
Usually the prefix to get an outside line or reach long
distance, (9 and or 1).
Modempool Type - local (not recommended for DMU), datakit (also

not recommended for DMU), access server (recommended for
DMU).
The access server entry indicates that the modempool is coming
off an Access Server which has the certified modem types to
connect to a DMU.
UIP Procedures
After all LoopCare data has been entered and submitted into the ADEF database,
activate the database through the LoopCare UIP,
Further
Information
This is a simplified outline of the ADEF entries and UIP procedures needed to
configure a DMU as an RT Test head. For more information on entering the
required data on the forms described above, see the Operation, Administration
3-82
EMU Installation
Associating a Standalone Remote Test Head with an
LTE(s)
Associating a Standalone Remote Test

Head with an LTE(s)
Overview
A standalone remote test head (RMU-S) can provide test access to one or more
LTEs. The association between the LTE is made on the LTE form. A reference
number (RMU-S Sequence No.) is assigned by the system when entering an
DMU-S using ADEF. This RMU-S Sequence Number is then entered by the user
on the LTE form. This association simply indicates which RMU-S can test the LTE.
EMU Installation
DWN Deployment

DWN Deployment
Introduction
The DWN is co-located with the DLC-RT. The DWN is inserted into the Test
Access Pair (TAP) path from the MCU to the internal DLC Metallic Test and
Access Unit (MTAU). Using the DWN hardware, narrowband testing from the CO
done by the DMU via a MCU pair can be combined with wideband testing
performed by the DWU at the RT site.
When the EMU performs a POTS test, the DWN acts as a passive pass-through.
Example
Deployment
LoopCare
Figure 3-10 shows an example of a DWN deployment.
CO
RT
COT
Switch
RT
MCU
MCU
NTT
TAP
T,R
CPE
T,R
DWN
Network
DMU
Figure 3-10.
EMU
WTM
DWU
Example of DWN Deployment
NOTE:
Figure 3-10 shows a Universal Digital Loop Carrier (DLC) system, but this
solution will also support Integrated DLC (IDLC) systems.
The DMU shown in the CO is an Expert Measurement Unit (EMU) from the
LoopCare perspective. The CO could also have either an LTS or DCTU collocated
with the EMU. The DWN can be connected to up to 4 RTs.
3-84
EMU Installation
DWN Administration
DWN Administration
Introduction
LoopCare provides the ability to provide sanity tests on DWN. The process is
similar to that used for a DMU.
OA&M
Configuration
The ADEF application in OA&M provides the ability to associate DWNs with a
dedicated Telephone Number used for sanity and diagnostics.
1.
On the ADEF menu, select DWN.

A blank DWN page is displayed.
2.
Enter the DWN Name of the new DWN or of the existing DWN to be edited.
If the record exists, it is displayed; go to step 4 to edit the record.
If the record does not exist, you are prompted whether to create a new
DWN record.
3.
Select YES to create a new record.

The cursor moves to the Telephone Number field.
4.
Associating a DWN
with an EMU
Enter the Telephone Number that is to be used for DWN diagnostics.
The wideband capability of the DWN is remote. When configuring an EMU

testhead, the presence of a DWU is indicated in the Wideband field on the NTG
screen. If the DWU associated with the DMU is on a DWN at the RT, enter R.
Sanity Testing
1.
Access the System Administration Mask (SAM).
2.
To test a single DWN, enter data in the following fields.
Field
Description
System
Enter the 2-character identifier of the system the

DWN is deployed on.
PRTR
Enter the 4-character identifier of the printer to which

output is to be sent.
BY
Enter the 2-character identifier of the user (for

identifying printouts).
EMU Installation
DWN Administration
Field
REQ
Description
Enter SAN or PSAN in the REQ field, along with the
appropriate option code:
-U#
This option specifies that you want to run the
Sanity test on the DWN specified by the
system-generated DWN ID (#).
or
To test all the DWNs associated with an NPANNX, enter data in the
following fields.
Field
Description
System
Enter the 2-character identifier of the system the

DWN is deployed on.
PRTR
Enter the 4-character identifier of the printer to which

output is to be sent.
BY
Enter the 2-character identifier of the user (for

identifying printouts).
REQ
Enter SAN or PSAN in the REQ field, along with the

appropriate option code:
-W
This option specifies that you want to run the
Sanity test on all the DWN associated with the
NPANXX entered in the NPANXX field.
NPANNX
Printing
Information
If you enter the -W option in the REQ field, you must

enter the NPANXX associated with the DWNs you
wish to test.
If you request SAN with the -U# option, all data for the DWN will be displayed on
the CRT screen. If PRTR and BY are specified in the request, the data will
additionally be directed to an output device.
If you request SAN with the -W option, as much data as fits for the first test unit
will be displayed on the CRT screen. If any data does not fit, or if there is more
than one test unit, the message SCREEN OVERFLOW--ALL DATA SENT TO
3-86
EMU Installation
DWN Administration
PRTR will be displayed on the bottom line of the screen, and all data will be
directed to an output device. PRTR and BY must be specified for the -W option.
Output Report
A DWN is considered defective if a device does not pass diagnostics testing or if

it is not available for testing. In such cases a detailed sanity report will be
displayed with appropriate status and diagnostics results. When the DWN is
functioning properly, the message NO PROBLEMS FOUND will be displayed
instead of the detailed SAN results.
A sample output is shown in the next section. The output contains the following
information:
SAM I/O Fields
Lines 1 through 3 contain the SAM mask input fields described above
and one output field, EXK, which is the same as the NPANNX field
entered on the mask.
General Information
The next printed lines contain the following general information:
For the Current and

previous tests, the
following results are
reported
DWNID
This is the sequence number used to identify the

DWN.
EXK
This is the exchange key used to identify the DLC

tested by the DWN.
CURR RUN/
PREV RUN
This is the day and time the Sanity test was run for
the current test and the previous test, displayed in 12
hour time as mm-dd hhmmA/P, where A is for AM
and P is for PM.
DIA
The diagnostic result for the DWN
WTU
The diagnostic result for Wideband Transmission

Module.
WU
The diagnostic result for the Wideband Unit.
Equipment Status Results

Each DWN device is displayed with a label followed by the Status Results for that
device: Wideband Transmission Module (WTM) and Wideband Unit (WU). The
valid status results are as follows:
Status
BUSY
Description
Device is Busy
Abbreviation
B
3-88
EMU Installation
DWN Administration
NOT_EQUIP
The test unit is not equipped with

this device
NE
NOCONNECT
Connection Failure. Could not

connect to the DWN
NC
SANITY IN
PROGRESS
Sanity is running
SAN
EMU Installation
Overview
Overview
The installation checklist contains a list of various network elements, equipment,
procedures, and documents required to install and make operational the CO, RT
and/or RT Standalone test head. The checklist consists of three parts:
Table 3-31. Equipment Checklist
Table 3-32. Installation Activities Checklist
Table 3-33. Reference Documentation
Table and Table each contain the following fields:
Item - (for example, DMU Test head)
Status
Explanation
- (for example, Required, Optional)

- Additional details about the item.
EMU Installation
Equipment Checklist
Equipment Checklist
Table 3-31.
Equipment Checklist
Item
Status
Explanation
LoopCare
Processor
Required
LoopCare Processor is an HP T500

series or K460 with UNIX HP10.20. Refer
to LoopCare Installation Guide for more
information.
LoopCare and
Additional
Software
Required
LoopCare software generic G10i14.1 or

higher.
ORACLE 7.3.2.3 also required.
Refer to LoopCare Installation Guide for
more information about all software
prerequisites.
Note: For installation of wideband test
heads the software needed is G10I14.6
or later.
TCP/IP Network
Required
A standard 10 Base-T LAN has been

certified
Access Servers
(AS)
Required
PortMaster - 2 Com OS 3.7.2 or later.

Refer to the LoopCare Installation Guide.
Access Server to
DMU cable &
connector
Required
One AS per DMU. Refer to the LoopCare

Installation Guide for more details.
TelAccord
Option
This is optional if you are setting up

DMU-W TelAccord test configuration.
DMU Test heads
Required
For basic metallic testing the Tollgrade

DigiTest System Test head.
For wideband testing the DMU wideband
test head which includes a DMU and
DWU Card.
3-90
EMU Installation
Equipment Checklist
Table 3-31.
Equipment Checklist
Item
Status
Explanation
Modems
Recommended Paradyne or Multitech Modems required

for Access Server modem pool to provide
dial up connection for DMUs. For more
details on each timeout value and its
default values, see Chapter 4, EMU
Administration of this Guide for more
information about modems.
Access Server to
Modem cable &
connector
Recommended One per modem. If modem pool is

required then cables/connectors
required. It is advisable to have an
Access Server modem pool in any case.
Refer to Appendix J of the LoopCare
Access Server to Optional

5ESS IOP cable
RS-232 Gender
Changers
This cable is required if you intend to use

the Originating Equipment (OE) Retrieval
feature. Refer to the LoopCare
Recommended Male and Female Gender changers

should be kept on hand in case of RS232 connector mismatch. These will
speed installation.
Access Server
Recommended Data-quality POTS telephone lines. One
per modem in the Access Server modem
Modem Telephone
Lines
pool. This is required for an RT test head.
DMU Modem
Telephone Lines
Recommended Data-quality POTS telephone lines. One

per DMU.
Optional
DMU Modem
Backup Telephone
Lines
Data-quality POTS telephone lines to

serve as a backup to the primary DMU
modem line. The backup telephone lines
are optional. One per DMU.
DMU Callback
Telephone Line
Data-quality POTS telephone line

required to complete LoopCare
interactive callback requests. One per
DMU.
Required
Note: This is not required for phase 1 of

the Standalone Remote Test head.
Continued on next page
EMU Installation
Equipment Checklist
Table 3-31.
Equipment Checklist
Item
LoopCare Trunk
Calibration
Telephone Line
Status
Required
Explanation
POTS line open at the MDF used to
calibrate trunk distance and resistance
values. One per EMU trunk group.
Note: Not required for wideband test
head configurations.
No Test Trunk
(NTT)
Required
The tip, ring, and sleeve leads of the

switchs NTT interface circuit need to be
run and connected to the DMU
backplane for NTT testing. Refer to the
DigiTest System Users Guide.
Note: Not required for wideband test
head configurations.
MDF Trunk (MDF) Optional
The tip, ring, and sleeve leads of the

switchs MDF trunk interface need to be
run and connected to the DMU
backplane for MDF trunk testing. Refer to
Remote Terminal
Test Access Pair
Required
For DMUs serving as RT test heads or

LTE test access pair (for Remote Test
head Standalone) the tip and ring of the
RT test pair needs to be run and
connected to the backplane of the DMU.
AC Power
ReceptaclesAccess Server
Required
Standard 110 AC power is required for

the Access Server.
Refer to the PortMaster-2
Communications Server Hardware
Installation Guide.
AC Power
Receptacles
Access Server
Modems
Required
Standard 110 AC power is required for

both the Multitech and Paradyne
modems.
Refer to the administration manuals for
the Multitech and Paradyne modems.
3-92
EMU Installation
Equipment Checklist
Table 3-31.
Item
Equipment Checklist
Status
Required
Central Office
Power,
Grounding, Fuses,
and Alarms
Explanation
The CO test head DMU is powered by 48 V DC supply. This requires a DC
battery return. In addition, the DMU
requires both frame and test grounds to
operate.
Additional requirements include SUP+
and SUP- Ringing Supplies, fuses, and
alarms.
For complete information on all these
items see the DigiTest System Users
Guide.
Remote Terminal Required

Power,
Grounding, Fuses
and Alarms
The RT Test head DMU is powered by 48 V DC supply.

For specific information on power,
grounding, and fuses for the RT
installation, see the DigiTest System
Users Guide.
Note: Standalone Remote Test head
needs DC power -48 V.
Equipment
Frames
Optional
Depending on the availability of space in

the CO or RT additional 19-inch or 23inch equipment bays may be required to
store or mount DMUs, Access Servers,
modems, etc. Each customer should
engineer the equipment layout to
determine if current space is adequate of
if additional equipment frames are
needed.
Refer to the LoopCare Installation Guide
for each piece of equipment to determine
the proper mounting and storage
requirements.
EMU Installation
Table 3-32.
Item
Status
Explanation
Set up LoopCare
processor
Required
Physical setup of HP processor
Install LoopCare
and associated
software
Required
Refer to LoopCare Installation Guide
Setup TCP/IP
Network
Required
Consult your network administrator.
Install Access
Server
Required
Refer to PortMaster-2 Communications

Server Installation Guide.
Install TelAccord
Required
For wideband testing using DMU-C & WB
Configure Access
Server Internal
Database
Required
Install Modems for Recommended Refer to the LoopCare Installation Guide

for cable connections.
Access Server
modem pools
Provision Modems Required
for Access Server
modem pools
Install DMU CO
test head
Refer to the DigiTest System Users

Guide for physical installation and
connections to power, test trunks, phone
lines, etc.
Required

for cable connections to the Access
Server.
Required
Configure DMU
Internal Database
(CO test head) for
DMU-C or DMU-C
WB
Refer to DigiTest System Users Guide

for details, and DMU Internal
Configuration: page 3-44 of this
document for an overview.
Remember to reset DMU after you make
the changes.
3-94
EMU Installation
Table 3-32.
Item
Status
Explanation
Required
Install DMU RT
(DWU optional) or
DMU Standalone
RT test head
Refer to DigiTest System Users Guide

for physical installation and connections
to power, test trunks, telephone lines, etc.
Required
Configure DMU
Internal Database
for DMU-R or
Standalone
Remote test head
(RMU-S)
Refer to DigiTest System Users Guide.

for details and DMU Internal
Configuration: page 3-44 of this
document for overview.
Configure 5ESS
IOP Port for OE
Retrieval
If you intend to use the OE retrieval

feature, this step is REQUIRED.
Optional
Remember to reset DMU after changes

made.
Refer to the 5ESS IOP port configuration

doc, Installation Guide.
Connect 5ESS
IOP Port to
Access Server
Optional

for cable specifications.
Set Up LoopCare
Trunk Calibration
numbers
Required
The LoopCare calibration lines are used

to determine the distance and resistance
of the CO test trunk and circuit which is
generally standard for all trunks in a trunk
group.
These values can then be subtracted off
each test that is run through a particular
trunk group so that the remaining values
indicate the loop outside of the CO.
Setup SNMP
Network between
LoopCare and
DSLAM.
Optional
Only for Standalone Remote Test Heads

for testing Stinger DSLAMs.
EMU Installation
Table 3-32.
Item
LoopCare ADEF
Database entry
Status
Required
Explanation
ADEF database entries are required to
populate equipment data so that
LoopCare can access and test lines.
Required ADEF entries will vary with the
LoopCare features supported. For
general ADEF information refer to the
Operation, Administration, and
Maintenance (OA&M) Guide.
For general ADEF guidelines needed to
populate basic data for EMU operation,
refer to EMU as CO Test Head: page 3-4
of this document.
Activate and Build Required

LoopCare
Databases
Once ADEF has been populated and

submitted, the LoopCare databases need
to be activated and built through the
LoopCare UIP interface.
Refer to the Operation, Administration,
Test Out
Configuration
3-96
Required
After all setups have been made, and

databases have been populated a
validation should be run to verify all
connections and configurations.
EMU Installation
Reference Documents
Reference Documents
Table 3-33 below lists appropriate documents that provide additional information
that will help your understanding of EMU installation.
Table 3-33.
Reference Documents
DigiTest System User Guide

LoopCare Installation Guide
LoopCare Operation, Administration, and Maintenance
(OA&M) Guide
PortMaster-2 Communications Server Hardware Installation
Guide
Configuration Guide for PortMaster-2 Communications Server
Multitech MT2834BR - Intelligent Data/Fax Rack Mounted
Modem Owners Manual
Comsphere 3800 Series Modems Users Guide (Paradyne)
LoopCare OE Retrieval Feature Description
3-98
EMU Installation
Reference Documents
EMU Administration
Contents
Introduction
4-3
Accessing the Tools
4-4
Introduction
4-4
The HADM Tool
4-5
4-6
4-8
4-10
4-11
DZadmin Access
4-12
4-13
4-14
4-15
Introduction
4-15
4-16
4-17
EMU Administration
Contents (continued)
4-23
Reset a DMU
4-26
4-27
Administering a Standalone RT Testhead with RMU-S admin Utility4-34

4-41
DZadmin Utility
4-42
4-43
4-45
4-46
4-47
4-48
4-49
4-50
Change Port Status
4-51
4-52
4-53
4-54
DZadmin Codes
4-55
4-56

4-2
4-60
4-60
EMU Administration
Introduction
Introduction
Overview
This chapter describes tools and procedures that are used to administer,
maintain, and trouble-shoot EMUs and DMU RT testheads.
The following items are discussed in this chapter:
Human Administration Interface (HADM) - An administrative interface to

the DMU which can be used to view or provision internal DMU data as well
as execute diagnostics.
EMUadmin utility - An LoopCare utility used to administer equipment

specific to DMUs that make up an EMU used as a CO testhead.
RMUadmin utility - An LoopCare utility used to administer equipment status

specific to DMUs as an RT Testhead.
RMU-Sadmin utility - An LoopCare utility to administer equipment and

other items on the Standalone Remote DMU test head.
DZadmin utility - An LoopCare utility used to administer the communication

gateway and also debug problems in the communications interface.
LoopCare SAM Interface - The LoopCare System Administration (SAM)

user interface used to run standard LoopCare administration commands
like trunk calibration.
DMU Diagnostics - A DMU internal diagnostics program used to identify

and debug DMU problems.
EMU Administration
Introduction
Accessing the Tools

Introduction
Overview
This section discusses how to access each of the tools listed above. Table 4-1
lists each tool and how it can be accessed.
Table 4-1. Tools and Access Methods.
Admin/Maintenance
Interface
4-4
Access Method
HADM
From UNIX prompt on LoopCare machine, enter dial via

modem connection
HADM
From UNIX prompt on LoopCare machine, enter nodial

via access server
HADM
craft port access
EMUadmin
from UNIX prompt on LoopCare machine, enter

EMUadmin
RMUadmin
From UNIX prompt on LoopCare machine, enter

RMUadmin (use only when the EMU is serving as an
RT testhead).
RMU-Sadmin
From UNIX prompt on LoopCare machine, enter RMUSadmin.
DZadmin
from UNIX prompt on LoopCare machine, enter

DZadmin
SAM
Use mTRM to invoke SAM mask
Diagnostic
HADM interface
EMU Administration
The HADM Tool
The HADM Tool

Overview
You can use HADM in one of three modes to administer, maintain, and troubleshoot EMUs and DMU RT testheads:
dial utility
nodial utility
Craft port access
EMU Administration

Overview
You can use the dial utility to access HADM when a DMU is dialed up through
Access Server modems.
Use the following procedure for the dial utility:
1.
Login to the LoopCare HP machine as mlt.
2.
Enter the following at the UNIX prompt:

dial <IP Address> <TCP port> <DMU Dialstring>
or
dial <domain address> <TCP port> <DMU Dialstring>
The IP address is the IP address of the access server connecting to the
DMU. You can also use a domain name in place of an IP address. The TCP
port is the TCP ID of the port connected to the access server. The DMU
Dialstring is the telephone number of the Access Server modem.
Example: dial 135.5.138.65 6002 919995551234
Both the IP address and TCP port ID can be located through the LoopCare
ADEF database for the access server that connects to the DMU. The DMU
Dialstring can assembled from different ADEF forms. The dialout digit will
come from the MODEMPOOL serving the DMU. In this case, the dialout
digit is 9. The prefix is found in the DIALGROUP serving the DMU. In this
case the prefix is 1999. The DMU TN is found in the EMU or RMU form for
the specific testhead as the Primary Testhead TN.
3.
Press CARRIAGE RETURN to make certain you are connected to the

DMU. The DMUs password prompt should appear. You are now in HADM.
Follow all on-line directions for using and quitting the utility.
4.
Disconnect from dial by pressing CTRL d.

NOTE:
There are three options that can be used on the command line singly or
jointly with the dial utility. They are - s, - t, and -st.
Use the - s option if you want to "show all". Characters within the range of
printable characters, 0x40 to 0x176, are shown in their usual form. The
CARRIAGE RETURN character is shown as \r and the NEWLINE
character is shown as \n. Other non-printing characters, those with hex
values outside the range 0x40 to 0x176, are shown in their hex form, for
example, the ESCAPE character is shown as 0x33.
Use the - t (strip) option If you want all characters received from the
sending end reduced to 7 bits before "showing" them.
4-6
EMU Administration
Use the - st option if you want to combine the other two, that is, strip the
characters before they are shown.
Examples:
dial 135.5.138.65 6001 2013864686 -st

dial achilles 6001 2013864686 - st
Note: On some menus of the HADM interface an ESC key is required to

exit the display. If you used the dial utility to connect to the HADM interface,
the sequence to send HADM the ESC is to enter it twice (that is ESC ESC).
The first ESC acts as a control character for the dial utility. The second
ESC is sent to the HADM menu as an operating character.
EMU Administration

Overview
You can also use the nodial utility to access HADM when a DMU is directly
connected to an access server or to an E-DMU. You can use nodial to connect the
the E-DMU Ethernet Admin port, but the default password is supervisor.
Procedure
Use the following procedure for the nodial utility:

1.
2.

nodial <IP Address> <TCP port>
or
nodial <domain name> <TCP port>
or
nodial -e <DCN ID> <EMU ID> <trunk>
or
nodial -r <RMU-S Sequence Number>
The IP address is the IP address of the access server connecting to the
DMU. You can also use a domain name in place of an IP address. The TCP
port is the TCP ID of the port connected to the access server.
Examples:
nodial 135.5.138.65 6001

nodial -e 1 800 1
Both the IP address and TCP port ID can be located through the ADEF
database for the access server that connects to the DMU.
3.
Press CARRIAGE RETURN to make certain you are connected to the

DMU. The DMUs password prompt should appear. You are now in HADM.
Follow all on-line directions for using and quitting the utility.
4.
Disconnect from nodial by pressing CTRL d

NOTE:
There are three other options that can be used on the command line singly
or jointly with the nodial utility. They are - s, - t, and -st
Use the - s option if you want to "show all". Characters within the range of
printable characters, 0x40 to 0x176, are shown in their usual form. The
CARRIAGE RETURN character is shown as \r and the NEWLINE
4-8
EMU Administration
character is shown as \n. Other non-printing characters, those with hex

values outside the range 0x40 to 0x176, are shown in their hex form, for
example, the ESCAPE character is shown as 0x33.
Use the - t (strip) option If you want all characters received from the
sending end reduced to 7 bits before "showing" them.
Use the - st option if you want to combine the other two, that is, strip the
characters before they are shown.
Examples:
nodial 135.5.138.65 6001

nodial -e 1 800 1 - st
NOTE:
On some menus of the HADM interface an ESC key is required to exit the
display. If you used the nodial utility to connect to the HADM interface, the
sequence to send HADM the ESC is to enter it twice (that is ESC ESC).
The first ESC acts as a control character for the nodial utility. The second
ESC is sent to the HADM menu as an operating character.
EMU Administration

Overview
Another way to access the HADM interface is through the DMUs craft direct port.
For more details on this option, see the section on Craft Direct Port later in this
chapter or the DigiTest System Users Guide.
You can also connect to the EDMU Ethernet Admin port directly through the EDMU serial port.
4-10
EMU Administration
EMUadmin, RMUadmin and RMUSadmin Access

Overview
These utilities can be accessed from the UNIX prompt on the LoopCare HP
machine and should be used only if the EMU is serving as a CO testhead.
Use the following procedure to access the EMUadmin utility:
1.
2.

EMUadmin or RMUadmin or RMU-Sadmin
Follow the menu options to perform the needed tasks and exit.
EMU Administration
DZadmin Access
DZadmin Access
Overview
You can access DZ admin from the UNIX prompt on the LoopCare HP machine.
Use the following procedure to access DZadmin:
1.
2.

DZadmin
3.
4-12
Follow the menu options to perform the needed tasks and exit.
EMU Administration

Overview
Several LoopCare administrative tasks are performed through the LoopCare SAM
Interface for an EMU application. These include Trunk Calibration and
identification of testable NXXs for an EMU.
LoopCare SAM requests are run through the LoopCare SAM user interface. To
get to the SAM mask you must first invoke an LoopCare user interface. For an
RBOC application this can be done through an ANS bisync terminal or through
whatever custom asynchronous terminal emulator package is currently in use.
For GCM customers the most common way to invoke the LoopCare user interface
is through the mTRM utility. The mTRM utility is an asynchronous terminal
emulator program from which both SAM and TV interfaces can be run.
Once you are on an LoopCare user interface, the SAM mask can be accessed by
executing the following command:
/FOR SAM
When you have entered the SAM Mask, execute the appropriate requests. For
details on the LoopCare SAM Interface and requests, see the Operation,
Administration, and Maintenance (OA&M) Guide.
EMU Administration

Procedure
4-14
Use the HADM interface to access DMU Diagnostics:

1.
Select the Diagnostics option from the HADM main menu.
2.
For more information on accessing DMU diagnostics, see the HADM

sections later in this chapter and the DigiTest System Users Guide.
EMU Administration
Introduction
Introduction
Overview
This section describes the administrative tools and their capabilities available for
administering the EMU and its components.
EMU Administration
Human Administration Interface

(HADM)
Overview
The Tollgrade DMU/DMU+ Human Administration interface (HADM) is used to

view or provision internal DMU data. This interface can also be used to start DMU
diagnostics.
The main menu items on DMU/DMU+ HADM are listed below:
Administration. Covers a wide number of functions, including those listed

below:
Set Clock
Reset DMU/DMU+
Configure Port Trunk Type
Configure Ports
Calibration
View/Set Passwords
Flash Directory
Configure Device Type
Configure Environment
Diagnostics. Run or view DMU diagnostics.
Version. View DMU/DMU+ software version.
Status. View/Change DMU/DMU+ equipment status.
For a detailed discussion of HADM, see the HADM sections later in this chapter
and the DigiTest System Users Guide.
4-16
EMU Administration
Administering a CO Testhead with

EMUadmin
Overview
EMUadmin is a UNIX utility program used to administer the individual DMUs that
make up the EMU, when the EMU is serving as a CO testhead. Internal
configuration data and LoopCare trunk calibration data are some of the items that
can be administered through this interface. These data may be in the LoopCare
database or in files controlled directly by EMUadmin.
EMUadmin requires the presence of an LoopCare group. If no group is running,
the following error message will be displayed:
CANNOT EXECUTE - LMOS/MLT group must be up.
When the LOC2 test request is executed, and the testhead is the Digital
Measurement Unit - Central Office (DMU-C), the error message below will be
displayed. The LOC2 test request requires multiple test trunk access and
measurements and the DMU-C only has one test trunk access.
ILLEGAL TRANSACTION FOR EMU
EMUadmin performs the following functions:
Download
Download
Display EMU data
Change EMU data
Display Status
Change Status
Reset EMU
A download is generally performed when a change has occurred to the individual

DMUs stored values (such as a loss of memory) or to the values stored in the
database. Selection 1 from the initial menu, shown below, is used to connect to
the EMU. The EMU id (the overall ID given to the logical testhead that includes
the individual DMUs) must be given; EMUadmin extract the access information
(access server ID, service name, or DMU TN) from the database and establishes
the connection. If the connection cannot be established with the password found
in the EMU access information, the user is prompted for the password currently
known by the EMU and an attempt is made to connect using this password. If this
succeeds, EMUadmin may only be used to download the DMU, since a change in
the DMU access information requires that the DMU be downloaded.
EMU Administration
Once connected to a DMU, EMUadmin may be used to display or change the

individual DMU status, display or change DMU data, Reset the DMU, or download
the DMU. When these operations are complete the user will disconnect from the
DMU and may quit or continue.
This is the initial menu displayed when EMUadmin is invoked:
Enter selection [0-5]: 1

Enter EMU id: 1386
Enter Trunk Number: 1
calling the testhead, please wait....
The system then displays the following menu and prompt:
If the password for the EMU has changed, the menu prompt will be
4-18
EMU Administration
EMU password may have changed.

Enter password or the <BREAK> key to quit:
The menu displayed when the password has changed is shown below. The only
selections allowed in this case are download, disconnect or quit.
Display and Change

EMU Data
Values for switch parameters, timeouts, and thresholds are kept and may be
changed for every (not each) EMU by EMUadmin. The values are not affected by
the various database setup functions in LoopCare. For these value changes to
become stored in the EMU, a download must be performed.
EMU Administration
The menu to be displayed when option 2 is selected is given below.
If you wish to "change EMU data," selection 3 should be entered on the mask
shown below. If the user is not connected to a particular EMU the changes will be
made globally.
4-20
EMU Administration
The system displays the following data:
The following list describes the meaning and application of each of the above
default EMU timeout values.
login - This is the time allowed for a user to attempt to log in to the EMU. If
no valid password is given by this time, the EMU shall disconnect.
Default: 120 seconds
acctime - This is the amount of time that the EMU shall maintain a No-Test
access when no activity is present in the EMU or after a conditional
disconnect. It is customarily overridden by the timeout in the access
message or the EXTEND_TO request, and is only used when the access
message sets the timeout to zero.
Default: 30 minutes
key0wait - This is the amount of time that the EMU shall await a DTMR "0"
to signify that a callback line has been answered. If this amount of time
elapses without the acknowledgment being heard, the callback line shall be
dropped and a status of CLBK_TO returned to the user.
Default: 50 seconds
tonetime - This is the default amount of time that the EMU shall apply a
tracing tone.
Default: 30 minutes
loopback - This is the default amount of time that a loopback shall be

maintained. All characters typed by the user are automatically looped back
over the data link without EMU processor intervention, suspending all EMU
and normal data-link operations for that period of time.
Default: 2 minutes
datacall - This is the amount of time that an inactive data call shall be
maintained. After this time elapses, the EMU shall perform a conditional
disconnect.
Default: 70 minutes
EMU Administration
acc_wait - This is the amount of time that the EMU shall wait for equipment
to become available before returning a timeout status for the access
request.
Default: 60 seconds
tst_wait - This is the amount of time that the EMU shall wait for equipment
to become available before returning a timeout for a test request.
Default: 60 seconds
The following list describes the meaning of each of the switch values.
ess5_sleep
sleep time delay for a 5ESS switch
busy_d_wait
busy detection wait time delay
oslv_t
open sleeve current for time delay
lslv_t
low sleeve current for time delay
hsa_t
high sleeve current for access time delay
hsd_t
high sleeve current for disconnect time delay
hsd_te5
high sleeve current for disconnect time delay for a

5ESS switch
rg_wait
ring-ground termination wait time for a step-by-step

switch
NOTE:
You should NOT change these switch parameters unless directed to do so
by troubleshooting personnel.
4-22
EMU Administration

Overview
After connecting to the EMU, you have the option of displaying or changing the
EMU status.
EMU Administration
Menu selection 6 displays the status of the EMU equipment and trunks. The last
two columns are the trouble counts and the percentages. They are reset to zero
each time a download is run.
The status of the EMU, any device, or trunk may be set by the user. The new
status is stored in the database. Several statuses may be changed at once by use
of the continuation option.
The Change Status menu (Selection 7) displays the device and trunk code
numbers for change.
Enter selection or <CR> to quit: 11
4-24
EMU Administration
Status options available for the DMU HW are:
The system displays the status options available:

Enter status of DMU trunk:((I)n Service, (O)ut of Service):
There is a continuation option also; the default is 'N':
more? (y/N): n
EMU Administration
Reset a DMU
Reset a DMU
Overview
After connecting to the specific EMU trunk (DMU-C), you perform a reset of the
DMU-C which will drop all connections to that DMU-C.
Menu selection 1 sends a reset to the DMU-C, causing the DMU-C to reboot. All
connections to the DMU-C will be dropped. Since this can take some time, the
following message is displayed:
Awaiting response from EMU. Please wait ..
After successful reset the following status will be displayed:
_EMU_RESET: ADM_OK
4-26
EMU Administration
Administering an RT Testhead with

RMUadmin Utility
Overview
When a DMU is used as a remote testhead, the existing RMUadmin utility may be
used to perform its respective functions.
RMUadmin, a UNIX utility program, is used to administer an RMU. This program
is only available to users in the "baseadm" group. This automatically includes the
logins "base", "mlt", and "mltsup".
Functions
Selection 1 from the initial menu, shown below, is used to connect to the RMU.
The LTS id and the RMU id must be given; RMUadmin will extract the access
information (telephone number and computer password) from the database and
establish the connection. If the connection cannot be established with the
computer password found in the RMU access information, the user is prompted
for the password currently known by the RMU as the CADM password and an
attempt is made to connect using this password. If this succeeds, RMUadmin may
only be used to download the RMU, since a change in the RMU access
information requires a download to bring the RMU up to date.
Once connected to a RMU, RMUadmin may be used to display or change RMU
status, display or change RMU data, or download the RMU. When these
operations are complete the user will disconnect from the RMU and may quit or
continue.
RMUadmin' requires the presence of an MLT group. If no group is running, the
following error message will be displayed:
CANNOT EXECUTE - MLT group must be up and MLT_MAP must be present.
RMUadmin' performs the following functions:
Download
Display Status and Offset
Change Status
Display RMU data
Change RMU data
Reset RMU
Set RMU offset
EMU Administration
The following takes the user through the menu structure, explaining the various
prompts and entries needed with each menu option.
Menus
This is the initial menu displayed when RMUadmin is invoked:
Option 1 Connect to
RMU
Enter LTS id: xxx

Enter RMU id: xxxx
calling the RMU, please wait...
READ
After entering the RMU id and LTS id, the RMU test status, software version,
diagnostics results, alarm status, and the RMU primary and secondary id number
are displayed in the following fashion:
_RMU_STAT: TST_OK
version 1.1 service: AVAILABLE
Diagnostics: PASSED
Alarm = OPEN
Primary id = 12 Secondary id = 6
If the password for the RMU has changed, the menu prompt
will be
RMU password may have changed.
Commands:
8 - Download
9 - Disconnect RMU
4-28
EMU Administration
0 - Quit
Enter selection:
If the RMU password has not changed, the menu to be displayed after entering
the RMU id is as follows:
Commands:
2 - Display RMU data
3 - Change RMU data
4 - Reset RMU
5 - Reset offset for RMU
6 - Display RMU Status and Offset
7 - Change RMU Status
8 - Download
9 - Disconnect RMU
0 - Quit
Enter selection:
changed for every (not each) RMU by RMUadmin. The values are not affected by
the various database setup functions in LoopCare.
For these value changes to become stored in the RMU, a download must be
performed.
Note that if the attempt to connect with the RMU was successful, items 4 through
9 become valid menu items.
Option 2 - Display
RMU Data
The menu displayed when option 2 is selected is as follows:

RMU timeout values:
login
111 sec
dddtime
33 min
key0wait
55 sec
tonetime
33 min
Option 3 - Change
RMU Data
EMU Administration
ringtime
33 sec
loopback
33 min
datacall
30 min
To "change RMU data," option 3 must be selected. If no connection to a particular

RMU has been established, the changes will be made globally. The menu
displayed when option 3 is selected is as follows:
1) login
2) dddtime
3) key0wait
4) tonetime
5) ringtime
6) loopback
7) datacall
8) all
9) defaults
0) quit
The change menu allows the user to change either one timeout value (by entering
the appropriate menu number at the prompt), change all of the values in order
(menu option 8), or reset all timeouts to default values (as shown in the option 8
output below). The prompt for a single timeout <timout_name> appears like so:
Enter <timeout_name> timeout or <CR> for default of
<to_default> secs:
If item 1 were selected from the menu, the following line would be printed:
Enter login timeout or <CR> for default of 120 secs:
If the "all" option (8) is selected, the following prompts will appear in the order
shown:
Enter
Enter
Enter
Enter
Enter
Enter
4-30
login timeout or <CR> for default of 120 secs:

dddtime timeout or <CR> for default of 30 minutes:
key0wait timeout or <CR> for default of 50 secs:
tonetime timeout or <CR> for default of 30 minutes:
ringtime timeout or <CR> for default of 40 seconds
loopback timeout or <CR> for default of 1 min:
EMU Administration
default RMU timeout values.
login - The time allowed for a user to attempt to log in to the RMU. If no
valid password is given by this time, the RMU will disconnect.
dddtime - The number of minutes to maintain a callback line with no activity

or after a conditional disconnect.
Default: 30 minutes
key0wait - The amount of time that the RMU will await a DTMR "0" to
signify that a callback line has been answered. If this amount of time
elapses without the acknowledgment being heard, the callback line will be
Default: 50 seconds
tonetime - The amount of time that the RMU will apply a tracing tone.
Default: 30 minutes
ringtime - The number of seconds that a ringing tone will be applied before
timeout.
Default: 40 seconds
loopback - The amount of time that a loopback will be maintained. All

characters typed by the user are automatically looped back over the data
link without RMU processor intervention, suspending all RMU and normal
data-link operations for that period of time.
Default: 1 minutes
datacall - The amount of time that an inactive data call will be maintained.
After this time elapses, the RMU will perform a conditional disconnect.
Default: 30 minutes
Option 4 - Reset
RMU
The following is displayed after choosing option four:
Option 5 - Set Offset

for RMU
This option lets you change the recorded distance of the Station from the RMU.
The prompt is thus:
Awaiting response time from RMU. Please wait...

Connection Dropped.
Enter offset in feet: Awaiting response from RMU. Please wait....
Option 6 - Display
RMU status and
offset
Option 7 - Change
RMU Status
EMU Administration
Selecting menu option 6 will display the status of the RMU equipment and the
current recorded distance of the Station from the RMU.
RMU STATUS =
FORCED_AVAIL
RMU OFFSET =
555
The status of the RMU may be set by the user. The new status is stored in the
LoopCare database.
Change Status:
AVAILABLE 1
FORCED_AVAIL 2
OUT_OF_SERVICE 3
Select new status for RMU:
Awaiting response from RMU. Please wait...
RMU STATUS = <new_status> <- whatever option you
entered
Option 8 Download
A download should be performed when a change has occurred to the RMU's

stored values (such as a loss of memory), or the values stored in the LoopCare
database have been changed, or the "Change RMU data" option has been used.
Before downloading the service status for the RMU, RMUadmin reads the service
status from the RMU. If the status is AUTO_OOS, the download procedure does
not update the RMU based on the status record, as the RMU may have gone to
AUTO_OOS of its own accord. The "Change Status" option must be used to
change the RMU service status from AUTO_OOS.
The following is RMUadmin's response to option 8:
Download complete
Option 9 Disconnect RMU
4-32
The response to this option is as follows:
EMU Administration
Connection dropped
EMU Administration
Administering a Standalone RT Testhead with RMU-S
Administering a Standalone RT Testhead

with RMU-S admin Utility
Overview
When a DMU is used as a standalone remote testhead, the RMU-Sadmin utility

may be used to perform its respective functions.
RMU-Sadmin, a UNIX utility program, is used to administer an RMU.This program
is only available to users in the "baseadm" group. This automatically includes the
logins "base", "mlt", and "mltsup".
Functions
Selection 1 from the initial menu, shown below, is used to connect to the RMU-S.
The RMU-S Sequence id must be given; RMUadmin will extract the access
information (telephone number and computer password) from the database and
establish the connection. If the connection cannot be established with the
computer password found in the RMU-S access information, the user is prompted
for the password currently known by the RMU-S as the CADM password and an
attempt is made to connect using this password. If this succeeds, RMU-Sadmin
may only be used to download the RMU-S, since a change in the RMU-S access
information requires a download to bring the RMU-S up to date.
Once connected to a RMU-S, RMU-Sadmin may be used to display or change
RMU-S status, display or change RMU-S data, or download the RMU-S. When
these operations are complete the user will disconnect from the RMU-S and may
quit or continue.
RMU-Sadmin requires the presence of an MLT group. If no group is running, the
following error message will be displayed:
CANNOT EXECUTE - MLT group must be up and MLT_MAP must be
present.
RMU-Sadmin performs the following functions:
4-34
Download
Display Status and Offset
Change Status
Display RMU data
Change RMU data
Reset RMU
Set RMU offset
EMU Administration
admin Utility
Menus
The following takes the user through the menu structure, explaining the various
prompts and entries needed with each menu option.
This is the initial menu displayed when RMU-Sadmin is invoked:
RMU-Sadmin Version 1.0
Commands:
1 - Connect to RMU-S
2 - Display RMU-S data
3 - Change RMU-S data
0 - Quit
Enter selection [0-3]:
Option 1 Connect to
RMU
Enter RMU-S Sequence id: xxxx

calling the test head, please wait...
READ
After entering the RMU id and LTS id, the RMU test status, software version,
diagnostics results, alarm status, and the RMU primary and secondary id number
are displayed in the following fashion:
_RMU_STAT: TST_OK
version TO-02.00service: AVAILABLE
Diagnostics: PASSED
Alarm = OPEN
Primary id = 27 Secondary id = 0
If the password for the RMU has changed, the menu prompt
will be
RMU password may have changed.
Commands:
8 - Download
9 - Disconnect RMU-S
0 - Quit
Enter selection:
EMU Administration
If the RMU password has not changed, the menu to be displayed after entering
the RMU id is as follows:
Commands:
2 - Display RMU-S data
3 - Change RMU-S data
4 - Reset RMU-S.
This will drop connection to the RMU-S
5 - Set offset for RMU-S

6 - Display RMU-S Status and offset
7 - Change RMU-S Status
8 - Download
9 - Disconnect RMU-S
0 - Quit
Enter selection:
changed for every (not each) RMU-S by RMU-Sadmin. The values are not
affected by the various database setup functions in LoopCare.
For these value changes to become stored in the RMU-S, a download must be
performed.
Note that if the attempt to connect with the RMU-S was successful, items 4
through 9 become valid menu items.
Option 2 - Display
RMU-S Data
The menu displayed when option 2 is selected is as follows:

RMU timeout values:
4-36
login
111 sec
dddtime
33 min
key0wait
55 sec
tonetime
33 min
ringtime
33 sec
loopback
33 min
datacall
30 min
EMU Administration
admin Utility
Option 3 - Change
RMU-S Data
To "change RMU-S data," option 3 must be selected. If no connection to a

particular RMU-S has been established, the changes will be made globally. The
menu displayed when option 3 is selected is as follows:
1) login
2) dddtime
3) key0wait
4) tonetime
5) ringtime
6) loopback
7) datacall
8) all
9) defaults
0) quit
The change menu allows the user to change either one timeout value (by entering
the appropriate menu number at the prompt), change all of the values in order
(menu option 8), or reset all timeouts to default values (as shown in the option 8
output below). The prompt for a single timeout <timout_name> appears like so:
Enter <timeout_name> timeout or <CR> for default of
<to_default> secs:
If item 1 were selected from the menu, the following line would be printed:
If the "all" option (8) is selected, the following prompts will appear in the order
shown:
Enter dddtime timeout or <CR> for default of 30
minutes:
Enter key0wait timeout or <CR> for default of 50 secs:
Enter tonetime timeout or <CR> for default of 30
minutes:
Enter ringtime timeout or <CR> for default of 40
seconds
Enter loopback timeout or <CR> for default of 1 min:
default RMU timeout values.
EMU Administration
login - The time allowed for a user to attempt to log in to the RMU. If no
valid password is given by this time, the RMU will disconnect.
dddtime - The number of minutes to maintain a callback line with no activity

or after a conditional disconnect.
Default: 30 minutes
key0wait - The amount of time that the RMU will await a DTMR "0" to
signify that a callback line has been answered. If this amount of time
elapses without the acknowledgment being heard, the callback line will be
Default: 50 seconds
tonetime - The amount of time that the RMU will apply a tracing tone.
Default: 30 minutes
ringtime - The number of seconds that a ringing tone will be applied before
timeout.
Default: 40 seconds
loopback - The amount of time that a loopback will be maintained. All

characters typed by the user are automatically looped back over the data
link without RMU processor intervention, suspending all RMU and normal
data-link operations for that period of time.
Default: 1 minutes
datacall - The amount of time that an inactive data call will be maintained.
After this time elapses, the RMU will perform a conditional disconnect.
Default: 30 minutes
Option 4 - Reset
RMU-S. This will
drop connections to
the RMU-S
The following is displayed after choosing option four:
Option 5 - Set Offset

for RMU-S
This option lets you change the recorded distance of the Station from the RMU-S.
The prompt is thus:
Awaiting response time from RMU-S. Please wait...

Connection Dropped.
Enter offset in feet: Awaiting response from RMU-S.

Please wait....
4-38
EMU Administration
admin Utility
Option 6 - Display
RMU-S Status and
offset
Option 7 - Change
RMU-S Status
Selecting menu option 6 will display the status of the RMU-S equipment and the
current recorded distance of the Station from the RMU-S.
RMU STATUS =
FORCED_AVAIL
RMU OFFSET =
555
The status of the RMU-S may be set by the user. The new status is stored in the
LoopCare database.
Change Status:
AVAILABLE
FORCED_AVAIL
1
2
OUT_OF_SERVICE 3
Select new status for RMU:
RMU STATUS =<new_status> <- whatever option you entered
Option 8 Download
A download should be performed when a change has occurred to the RMU-S's

stored values (such as a loss of memory), or the values stored in the LoopCare
database have been changed, or the "Change RMU-S data" option has been
used.
Before downloading the service status for the RMU-S, RMU-Sadmin reads the
service status from the RMU-S. If the status is AUTO_OOS, the download
procedure does not update the RMU based on the status record, as the RMU-S
may have gone to AUTO_OOS of its own accord. The "Change Status" option
must be used to change the RMU-S service status from AUTO_OOS.
The following is RMU-Sadmin's response to option 8:
Download complete
Option 9 Disconnect RMU-S
The response to this option is as follows:
Connection dropped
4-40
EMU Administration
EMU Administration
Administering through the DZadmin

Utility
Overview
DZadmin is a program used in the administration of asynchronous RS-232 ports

that communicate to the EMU and RMU. It is a menu-driven utility that allows
selection of various administrative options.
This section is an overview of the DZadmin system. Sample menus are shown,
along with explanations of each main menu selection. Also examples are given
(where appropriate) to represent output received when selections are made.
The DZadmin Menu, Selections, and Explanations
To invoke the DZadmin utility:
1.
Login as mlt
2.
Enter the following command at the prompt:

DZadmin
The DZadmin utilitys main menu displays.
Error! AutoText entry not defined.
All examples shown in this section will vary from the actual output received, due to
variance in modem types and numbers.
EMU Administration
DZadmin Utility
DZadmin Utility
Overview
Following is a sample of the main menu received upon DZadmin invocation:
Explanations for each of the main menu selections are shown below:
4-42
EMU Administration

Overview
When selection 1 is entered from the main menu, a second level menu will be
displayed:
Example: DZmaster
Table
To view the DZmaster's table, enter 1. Following is an example of the output

received.
*********** DZMASTER ACCESS TABLE ENTRY #0 ************
test unit type
: <UNKNOWN> [-1]
this entry's state
: <UNUSED>
DZ port
: <DYNAMIC
>
current no. of accesses up on this port: <0>

DYNAMIC
reader pid for this port
APPLICABLE>
modem type
: <NOT
: <NOT APPLICABLE>

test unit type
: <UNKNOWN> [-1]
this entry's state
: <UNUSED>
DZ port
: <DYNAMIC
>

DYNAMIC
APPLICABLE>
modem type
: <NOT
: <NOT APPLICABLE>

test unit type
: <UNKNOWN> [-1]
this entry's state
: <UNUSED>
DZ port
: <DYNAMIC
>

DYNAMIC
APPLICABLE>
: <NOT
EMU Administration
modem type
: <NOT APPLICABLE>
test unit type
: <UNKNOWN> [-1]
this entry's state
: <UNUSED>
DZ port
: <DYNAMIC
>

DYNAMIC
APPLICABLE>
modem type
: <NOT
: <NOT APPLICABLE>
NOTE:
<EMU_CNTLER> if an EMU is active on that port.
4-44
EMU Administration

Overview
There are rare occurrences when a DZ access drops, but the access tables are
not cleared. To clear the access tables, select option "2" from the DZadmin main
menu. The following second level menu is displayed.
To clear the DZmaster's table, select option 1. The prompt, "Enter entry no. to be
cleared <0-nnn>, where nnn represents the number of entries to be cleared. Upon
entering a number within the range specified, the message
***** CLEAR REQUEST COMPLETED SUCCESSFULLY *****
is returned. Repeat this process for each access table to be cleared.
EMU Administration

Overview
A virtual channel is defined as the communications path between DZmaster and

LoopCare software modules. The Virtual Channel Table lists the internal software
identifier descriptors, virtual channels, modes and reader/writer pids. To view the
Virtual Channel Table, select option "3" from the DZadmin main menu.
Following is an example of the Virtual Channel Table:
To clear a virtual channel, select option "4" from the DZadmin main menu. The
prompt:
Enter desc no. to be cleared [3-9]: 3
(where 3 - 9 = the valid descriptor entry range). Enter numbers for "x-y" from the
range given. The message is returned:
***** CLEAR REQUEST COMPLETED SUCCESSFULLY *****
4-46
EMU Administration

Overview
Selecting option 5 from the DZadmin main menu and then again at the next
prompt allows viewing of trouble counters for a particular DZ port. Following is an
example of the output received:
EMU Administration
Set DDCMP Error Rate Thresholds for a

Port
Overview
This option provides a means of changing the transmit and receive error
thresholds from the original default of ten percent.
NOTE:
This option works only with local (not over Datakit VCS) modems.
Select number "6" from the DZadmin main menu. Following is a representation of
typical output.
Enter entry no. [0-15; 255, for all ports]: 1
Enter new Receive Error Threshold: 10
Enter new Transmit Error Threshold: 10
OLD RECEIVE ERROR THRESHOLD WAS
10
NEW RECEIVE ERROR THRESHOLD IS
15
OLD TRANSMIT ERROR THRESHOLD WAS 10

NEW TRANSMIT ERROR THRESHOLD IS
4-48
15
EMU Administration

Overview
The Mapping Table lists the link between the ports and virtual channels. It displays
EMUs and the total number of associated accesses. Select option "7" from the
DZadmin main menu to Display the Mapping Table.
Following is an example of the output received.
EMU Administration

Overview
Before using the DZadmin utility to install a new DZmaster, the current DZmaster
must be killed and the new DZmaster must be started.
Procedures
The following are the procedures necessary for installing a new DZmaster:
1.
To terminate the current DZmaster, from the mlt login, enter:

$MLT_UTL/DZKILL
2.
To ensure than no DZmaster is running, enter:

ps -eaf | grep DZmaster
3.
To start the new DZmaster, enter:

nohup $MLT_UTL/DZSTART &
4.
To obtain the new DZmaster pid, enter:

ps -eaf | grep DZmaster
Note the new DZmaster pid. The PPID will be "1".
5.
To invoke the DZadmin utility for DZmaster installation, enter:

DZadmin
6.
Select option "8" from the DZadmin main menu. Enter the new DZmaster
pid at the prompt. An example of the output generated from these
procedures is:
mcr: OLD DZMASTER PID WAS <oldpid>, NEW PID IS <newpid>
mrr: OLD DZMASTER PID WAS <oldpid>, NEW PID IS <newpid>
tserc: OLD DZMASTER PID WAS <oldpid>, NEW PID IS <newpid>
Exit the Program
4-50
Select option 14 from the DZadmin main menu to exit the DZadmin utility.
EMU Administration
Change Port Status
Change Port Status

Overview
DZ ports can have a status of AVAILABLE, FORCED AVAILABLE, or OUT OF

SERVICE.
NOTE:
This option works only with local modems.
Procedure
To change the status of a DZ port, select option "9" from the DZadmin main menu.
Following is an example of a typical Change Port Status transaction.
Enter new entry status:
1) AVAILABLE
2) FORCED AVAILABLE
3) OUT OF SERVICE
Enter selection: 2
OLD PORT STATUS WAS AVAILABLE
NEW PORT STATUS IS
FORCED AVAILABLE
EMU Administration

Overview
Select option 10 from the main menu of DZadmin to display the trouble counters.
Following is an example of the Trouble Counter Report.
***** DZMASTER PORT TROUBLE COUNTERS ENTRY #0 *****
usage count
trouble count
trouble history
00000000
trouble rate threshold :
10%
***** DZMASTER PORT TROUBLE COUNTERS ENTRY #1 *****

usage count
trouble count
trouble history
trouble rate threshold :
00000000
10%
NOTE: This option works only with local modems.
4-52
EMU Administration

Overview
Selecting option 11 from the DZadmin main menu allows the definition of
thresholds at which a port is taken out of service. Following is an example of
possible output generated.
Enter new Trouble Rate Threshold: 15
OLD TROUBLE RATE THRESHOLD WAS
10
NEW TROUBLE RATE THRESHOLD IS
15
NOTE:
This option works only with local (not over Datakit VCS) modems.
EMU Administration
Enabling/Disabling EMU/RMU Access

Retry
Enable EMU/RMU
Access Retry
Select option 12 from the DZadmin main menu to enable DZmaster to retry a
failed access to a EMU or RMU through a different port. The message:
***** ACCESS RETRY/RECOVERY ENABLED *****
is returned.
Disable EMU/RMU
Access Retry
Select option 13 from the DZadmin main menu to disable this feature. The
message:
***** ACCESS RETRY/RECOVERY DISABLED *****
is returned.
4-54
EMU Administration
DZadmin Codes
DZadmin Codes
Overview
The DZadmin codes represent the current state of the test transaction using a
particular DZ connection. A partial list of these codes and the meaning for each
follows:
Codes
1.
TSER_ACC_ERR
When executing an RMU test in conjunction with either an LTS or DCTU,
the LTS/DCTU failed to gain access to the switch. Some possible reasons
for this failure are: office overflow, too many long term accesses on the
LTS/DCTU, all ports were busy, equipment failure or equipment out of
service, or the LTS timed out. LoopCare software should drop the
connection to the RMU.
2.
LTS_NG_RMU
The RMU status is bad for one of the following reasons:
3.
RMU is out of service
RMU has lost its memory and needs a download
RMU has reset
RMU diagnostics or calibration failed
RMU is in alarm state. The corresponding LTS/DCTU access should

be dropped by the LoopCare software.
TSER_BYP_ERR
The LTS/DCTU failed to gain bypass, which connects the RMU to the
customer line. The LTS/DCTU will maintain access to the switch but the
RMU connection will be dropped.
4.
TELNO_ACC
RMU access to the customer telephone failed because the number was
already listed as accessed in the DZ entry table. The RMU connection will
be dropped.
5.
LTSTO
The LTS/DCTU/EMU had a general error while the RMU was waiting for
bypass. The LTS/DCTU/EMU access to the switch and the RMU
connection will be dropped.
6.
KEEP_RMU
The test transaction completed successfully and the RMU connection to
the customer line will be held for subsequent tests.
EMU Administration

Overview
4-56
There are several LoopCare SAM transactions that are applicable to the EMU.
These are:
Change Status (CS) - This request is used to change the availability status
of trunks and of equipment on an EMU, DMU-R or RMU-S. It is used to
take faulty equipment or trunks Out-of-Service and subsequently restore
them for use in loop testing. It is also possible to CHANGE STATUS on the
DMU-C or DMU-R as a unit (for example, take the DMU-C, DMU-R or
RMU-S Out-of-Service directly).
Display Status (DS) - This request is used to display availability status,

trouble counts, and failure rates for connection/access attempts and
devices for a specific EMU/DMU/RMU by entering the existing DS
command on the SAM mask. LoopCare will keep count the number of
times it tried to connect to each EMU/DMU/ RMU, including successes and
failures, for testing or trunk calibration purposes and the number of times it
failed. This would be similar to the equipment and trunk failure and usage
counts. When consecutive connection/access failures exceed eight (8),
LoopCare will consider the EMU/DMU/RMU out-of service.
Configuration Download (DLOAD) - This request sends fresh copies of the

database and text (software) from a Front End to an EMU, DMU or RMU.
This causes the EMU, DMU or RMU to reset. All memory is erased and all
counters are reset to zero before the EMU, DMU or RMU accepts the new
database and text. As a result, all equipment that was in use will be freed
and all accesses to subscribers' lines will be dropped.
DMU/DMU+ Software Download (SWDLD) - This command allows users to

download DMU software to the DMU from SAM
Print DMU Software Download Status (PSWDLD) - This command

retrieves and displays the status of the last DMU download.
Force DMU/DMU+ Software Download (FSWDLD) - This command forces

a software download to the DMU regardless of software version checks.
Abort DMU/DMU+ Software Download (ASWDLD) - This command aborts

a software download to a DMU.
Sanity (SAN) - This command runs real time sanity tests for all devices on
the DMU-R, DMU-C, EMU, or RMU-S. When Sanity runs, diagnostics is
run in real time and results for each DMU and for each DMU device (MU,
TRK, TLK, and WU if equipped for Wideband testing) is displayed/printed.
EMU Sanity (EMUSAN) - This command runs DMU sanity tests on the
DMU-R, DMU-C, EMU, or RMU-S. This request does not initiate
diagnostics testing. The EMUSAN request is a quick sanity check of the
DMU, used to ping each EMU/DMU or to verify theLoopCare to EMU/
DMU communications path.
EMU Administration
DMU Diagnostics
Short Sanity (SSAN) - This command runs Short Sanity on the EMU or
DMU-Rs associated with a specific LTS/EMU. The short sanity report for
DMU-Rs and EMUs will contain the percentage of failed DMU-Cs and/or
DMU-Rs.
Print Sanity (PSAN) - This command is used to display and print the latest
set of stored sanity test results for the previous and latest Sanity Tests for
the DMU-C, DMU-R, EMU, or RMU-S. The PSAN request does not
connect to the DMU or run diagnostics. It just retrieves and displayed/prints
the stored information from the database.
Print Short Sanity (PSSAN) - This request is used to display the latest set
of stored short sanity results for the DMU-C, DMU-R, or EMU.
Print EMU Sanity (PEMUSAN) -This request is used to display the latest
set of stored EMU Sanity results for the EMU, DMU-C, DMU-R, or RMU-S.
Trunk Calibration (TC) - This command is used to calibrate EMU NoTest or

MDF Trunks.
Print Trunk Calibration (PTC) - This request is used to display stored trunk
calibration values for each trunk.
Trunk Diagnostics (TDIAG) - This command provides detailed

measurements on No-Test and MDF trunks. It performs the same testing
sequence as Trunk Calibration (TC), but evaluates the results differently.
Instead of comparing averaged results with historical values and reporting
summary messages, the TDIAG output report presents the detailed test
results for each trunk. trunks (including trunks in good or marginal condition
as well as failing trunks).
Testhead Identification (LTSID) - Identifies all testheads that test a specific

NPANNX. Where a DMU overlays another testhead, both testheads are
listed.
Print NXX Trunk Table (PXT) - This command displays a list of NXXs for a
testhead as well as the NoTest Trunk Groups that test them.
Display User-Defined DC Signature Summaries (DVER) - This command

displays the user-defined VER code/DC signature summaries. It also
enables or disables the Programmable VER code/DC Signature feature.
Change User Defined DC Signature (CVER) - This command allows the

user to change VER codes and DC Signature summaries from default
user-defined VER codes and summaries. The primary purpose for using
this transaction is to recognize distinctive DC signatures that ordinarily
could be mistaken to be faults.
In addition, to the SAN request described above, the DMU provides a diagnostics
program accessible through the HADM interface. Diagnostics are used to analyze
EMU Administration
and correct problems on the DMU hardware. For a detailed discussion of EMU
diagnostics, see the DigiTest System Users Guide.
Terminal Direct
Port Connection
The DMU testhead permits you to connect a PC directly to the LoopCare test port
(DMU Communications Port 1). The terminal direct connection can be used to
download software to the DMU. This capability requires that the communications
port configuration change from LoopCare Direct to Terminal Direct. (see Table 25).
This change is made from the Configure Ports option on the DMU HADM
interfaces Administration Menu. Use the same option to make the parameter
entries in Table 3-2 below. The terminal used for the connection must have the
same parameter values set.
For more details on Terminal Direct Connections, see the DigiTest System Users
Guide.
Table 4-2. Port Configuration Parameters.
Parameter
Craft Direct Port

Connection
Value
Baud Rate
9600
Parity
Data bits
Stop bits
The fuse/alarm card on the DMU enclosure contains two RJ-45 jacks for Craft
Direct Connection (one per DMU - the right-hand jack is assigned to the righthand DMU, the left-hand jack for the left-hand DMU).
A craft person can use the craft port to gain direct access to HADM or other
internal DMU utilities at the DMU site. Tale 3-3 shows the Craft Port configuration
parameters and their values. The craft terminal must be configured to match these
parameter settings.
4-58
EMU Administration
Table 4-3. Craft Port Configuration Parameters.

Parameter
Value
Baud Rate
9600
Parity
Data bits
Stop bits
For more information on the Craft Direct Connection to the DMU, see the DigiTest
System Users Guide.
EMU Administration

Overview
When Sanity tests are performed on a group of DMUs, such as a region, the
number of DMUs that can be tested simultaneously is limited by the size of the
modem pool used to access the DMUs. Requests to DMUs in excess of the
number of modems return the message Resources Unavailable.
Procedure
Use the following procedure to throttle sanity testing on DMUs:

1.
Log into the LoopCare host as mlt.
2.
Use vi to open the /base/config/MGRP.env file.
3.
Adjust the value of the EMUADM_MAX_PER_REQUEST line to the

desired value.
NOTE:
The value of this variable should be set equal to or less than the size of the
smallest modem pool in the system.
4-60
4.
Save the MGRP.env file.
5.
Bounce MGRP.
E-DMU Configuration
Contents
Introduction
5-2
5-5
5-7
Serial Connection Between Master E-DMU and a Serial Device5-9

5-12
E-DMU Configuration
Introduction
Introduction
Overview
This chapter describes the procedures for configuring the E-DMU.

NOTE:
The DMU+ testhead functions exactly like an E-DMU. The LoopCare
administrator does not need to perform any additional procedures when
replacing an E-DMU with a DMU+. LoopCare recognizes a DMU+/DMU+L
when logging into the respective module.
5-2
E-DMU Configuration
Introduction
Configuration of the E-DMU

Use of DMUs
DMUs are used in the following ways.
A set of DMUs may act as test resources for a set of lines served by a
switch. In this case, the set of DMUs is treated as a single Enhanced
Measurement Unit (EMU) and each DMU serves as a port of that EMU.
A single DMU may serve as a DMU-R for one or more Remote Terminals
serving a set of lines from a Remote Terminal site.
A single DMU may serve as an RMU-S for one or more Remote Terminals
serving a set of lines from LTE, such as a DSLAM.
A single DMU-C collocated at a CO may act as a test resource for a set of

lines served by a switch, which is accessed through an NTT or bypassed
by an MDF Trunk.
Configuration of
Modem-Equipped
DMUs
TCP/IP communications with DMUs equipped with modems are mediated via
access server devices. In the Automated Data Element Form (ADEF) interface,
there are tables to represent Access Servers, RMUs, EMUs and RMU-Ss. The
EMU, RMU and RMU-S tables reference entries in the Access Server table,
where the IP addresses and TCP port numbers are stored.
Configuration of EDMUs
An E-DMU provides test unit functionality as well as access server functionality. It

is represented as such in the LoopCare Operations, Administration, and
Maintenance (OA&M) database.
An E-DMU that acts as an RMU-S is represented as an RMU-S.
An E-DMU that acts as an EMU port is represented as an EMU port.
A DMU equipped with a Master Ethernet Option Card (E-DMU) and serving
as an RMU-S is represented in the database as an access server with two
ports, one that provides TCP/IP access to the Master DMU and one that
provides access via the additional serial port.
An E-DMU equipped with an Extender Ethernet Option Card and serving

as an RMU-S is also represented as an additional port on the access
server associated with the Master DMU. That port provides TCP/IP access
to the Extender DMU.
A Master DMU that serves as an EMU port is represented as a two-port

Access Server where one port provides TCP/IP access to that EMU port
and the other port provides access via the additional serial port.
Main Configuration
Considerations
E-DMU Configuration
Introduction
An Extender DMU serving as an EMU port is represented as an additional

port on the access server associated with the Master DMU.
As a DMU-R at a Remote Terminal of a DLC configuration, an E-DMU

works in conjunction with a CO testhead (LTS, DCTU, or an EMU) to
complete DLC tests. LoopCare communicates with the DMU at the RT
through the access server functionality provided by the Ethernet Option
Card.
As a DMU-C, an E-DMU is located in the CO and accesses the switch

through an NTT or bypasses the switch through an MDF Trunk.
As an RMU-S, an E-DMU is located at an RT, where it performs tests

through an LTE, such as an AnyMedia.
The DMU hardware on an E-DMU behaves the same way as a non E-DMU DMU,
with the main difference being that an access server function is incorporated into
the Master Ethernet Option Card.
An E-DMU is configured in much the same way as a DMU described in Chapter 3.
The following configuration steps required for an E-DMU differ from those for a
non-E-DMU DMU.
5-4
Build an Access Server with the TCP/IP address of the Ethernet

connection on the master E-DMU.
Associate the E-DMU(s) with the Access Server built for the master EDMU.
If the E-DMU firmware download feature is to be used, ensure that the

Extnet is associated with one LTE Group or one EMU.
E-DMU Configuration
Replacing Existing DMUs with an EDMU Extnet

Overview
This section describes the tasks and procedures for replacing existing DMUs with
an E-DMU Extnet.
The basic change will be a replacement of DMUs equipped with modem modules
connected to an access server by E-DMUs equipped with Ethernet cards and
incorporating an access server into their architecture.
Routing Tables
When an extender is attached, the routing table on the Master may be modified to
include port numbers for Extender DMU and Ethernet Option Card user
interfaces. New Ethercard Option Cards include a default routing table with
entries for each possible connection target. The default values in the routing table
are listed in Table 5-1.
Table 5-1. Default Routing Table Values for new Ethernet Option Cards
Description
Default TCP PORT ID
Master DMU
6000
Additional Serial Port on the Master DMU
6010
Extender 1 DMU
6100
Extender 1 Serial Port
6110
Extender 2 DMU
6200
6210
Extender 3 DMU
6300
6310
Extender 4 DMU
6400
6410
Extender 5 DMU
6500
6510
Extender 6 DMU
6600
6610
Extender 7 DMU
6700
6710
E-DMU Configuration
Once the routing table is set up, the Extnet is transparent to the user. The user is
responsible only for making sure the Extnet rotary switches on the E-DMUs are
set to correct addresses on each board and that these addresses agree with the
addresses assigned in the routing table.
\
Installation
Follow the instructions in the Supplemental Users Guide for the Ethernet Option
and Ethernet Extender Cards For use with Tollgrades LoopCare DMU and Nortel
DMU for installing the Extnet.
LoopCare
Configuration
The main difference between DMUs and E-DMUs is that E-DMUs incorporate an
access server in their architecture. After replacing DMUs with E-DMUs it is
necessary to modify the configuration on LoopCares OA&M forms relating to
Access Servers and Access Server-related fields on individual testhead screens.
*
Table 5-2. LoopCare ADEF Data Entry

ADEF Form
Access
Server
RMU
or
RMU-S
or
EMU (for a
DMU-C)
Explanation
Build a new Access Server:
Access Server Type - enter E-DMU,.
The fields on the Terminal Server Information Page are

automatically populated with default values. See Table 5-1.
After you complete the Access Server Form, you may view
the Terminal Server Information Page by pressing <F10>.
Access the existing record for the former RMU, RMU-S, or DMU-C,
and make the following changes:
Communication Info - Select Access Server
Access Server ID - enter the ID of the Access Server you created
for the Master E-DMU.
Service Name - press Ctrl-L and select the appropriate Master/
Extender port from the list.
5-6
E-DMU Configuration
Initial Deployment of Master/Extenders

in an Extnet
Overview
This section describes the tasks required to install an E-DMU Extnet at a site.
NOTE:
For replacing existing DMUs with an E-DMU Extnet, see Replacing Existing
DMUs with an E-DMU Extnet: page 5-5.
Routing Tables
When an extender is attached, the routing table on the Master may be modified to
include port numbers for Extender DMU and Ethernet Option Card user
interfaces. New Ethercard Option Cards include a default routing table with
entries for each possible connection target. The default values in the routing table
are listed in Table 5-1.
Installation
Follow the instructions in the Supplemental Users Guide for the Ethernet Option
and Ethernet Extender Cards For use with Tollgrades LoopCare DMU and Nortel
DMU for installing the Extnet.
LoopCare
Configuration
The main difference between DMUs and E-DMUs is that E-DMUs incorporate an
access server in their architecture. The configuration of E-DMUs is similar to that
of DMUs, except for the association of the E-DMU with an Access Server and not
a Modempool. Table 5-3 describes the steps that are different.
E-DMU Configuration

ADEF Form
Access
Server
RMU
or
RMU-S
or
EMU (for a
DMU-C)
Explanation
Build a new Access Server:

automatically populated with default values. See Table 5-1.
After you complete the Access Server Form, you may view
the Terminal Server Information Page by pressing <F10>.
Access the existing record for the RMU, RMU-S, or DMU-C, and
make the following changes:
Communication Info - Select Access Server
Access Server ID - enter the ID of the Access Server you created
for the Master E-DMU.
Service Name - enter the numeric designation for the E-DMU on
the Terminal Server Information Page.
5-8
E-DMU Configuration
Serial Connection Between Master E-DMU and a Serial
Device
Serial Connection Between Master EDMU and a Serial Device

Overview
The interface to an additional serial device supported via the Ethernet Option
Card is used to support an interface for controlling test access with commands
and reporting status with responses to an external device, for example, an
interface to the Telaccord 100/DAU1000 or DMU.
Connection to a
Serial Device
When the serial port is connected to a Telaccord 1000/DAU 1000 or DMU, a

custom cable is required to allow communication between the serial port and the
serial device. Table 5-4 shows the required pin-out connections of the cable.
Table 5-4. Ethernet Option Card Serial Port to Serial Device Cable Wiring
Ethernet Option Card Serial Port
LoopCare
Configuration
Serial Device
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
The following table describes the required steps for configuring the serial port
connection between the master E-DMU and the serial device.
E-DMU Configuration

ADEF Form
Access Server
Explanation
Build a new Access Server, if necessary

automatically populated with default values. See
Table 5-1. After you complete the Access Server Form,
you may view the Terminal Server Information Page by
pressing <F10>.
The default DMU and Serial Port Addresses are displayed on

the Terminal Server Information Page.
LTE
If necessary, build a new Telaccord 1000/DAU1000:
Vendor - select Tollgrade
Model - select Telaccord
Language - automatically becomes TL1 when Telaccord

is selected in the previous field.
LTE Group ID - Select an appropriate value
When done, press <F10> to access a Navigation Menu and

select Communication Information.
Communication
Information
5-10
Comm Mode - Defaults to TCP/IP
Access Server ID - Enter the value for the Access Server

you created for the E-DMU
Service Name - Enter the value from the Terminal Server

Information Page
IP Address - Enter the IP address for the Telaccord 1000/

DAU1000
Press <F6> to access the buttons at the bottom of the

screen and select Save to save your data. Select Exit to
return to the LTE screen.
Press <F10> to access a Navigation Menu and select

Metallic Test Info.
E-DMU Configuration
Device

ADEF Form
Metallic Test
Information
Explanation
Select RMU-Standalone
Enter the RMU-S ID
Enter the RMU-S Seq. No.
E-DMU Configuration
Overview
For the DMU hardware of an E-DMU, the same administrative tools are used as
are described in Chapter 4.
This section confines itself to the LoopCare tools available for administering or
maintaining the Ethernet option card portion of the E-DMU.
E-DMU Firmware
Download
LoopCare provides utilities to download firmware to one Ethernet Option Card or

to a group of cards. These utilities are provided by the System Administration
Mask (SAM) and the System Administration GUI (AdminGUI) and are described in
the Operations, Administration and Maintenance (OA&M) Guide.
For this feature to work correctly with E-DMUs installed in an Extnet, you must
associate all the E-DMUs on the Extnet with a single LTE Group or with a single
EMU, as applicable.
5-12
DigiTest EDGE Components and

Configurations
Contents
Introduction
6-2
DigiTest EDGE
6-3
6-5

Introduction
Introduction
Overview
6-2
This chapter describes the capabilities of the DigiTest EDGE and the components
of the DigiTest EDGE broadband test platform.

DigiTest EDGE
DigiTest EDGE
Introduction
The DigiTest EDGE test platform facilitates the pre-qualification, installation,

validation, and troubleshooting of the local loop in support of broadband services.
It inter-works with broadband edge network equipment such as Digital Subscriber
Line Access Multiplexers (DSLAMs), Next Generation Digital Loop Carrier
Systems (ngDLCs), and Metallic Test Access Units (MTAUs). It may be installed in
a Central Office (CO), branch exchange, or a Remote Terminal (RT), where it can
be used to test the subscriber side of an NGDLC or DSLAM.
The DigiTest EDGE performs essential testing functions to support broadband
delivery by virtue of its location in the network. It is physically co-located with the
access device. For example, the DSLAM may be located in a Central Office (CO)
or at a remote site, while the NGDLC, by definition, is located at a Remote
Terminal (RT).
The DigiTest EDGE is the remote test platform component of Tollgrades
Broadband EDGE solution. Managed by a providers Test Operations Support
System (OSS), such as Tollgrades LoopCare, the DigiTest EDGE qualifies the
broadband edge for the deployed services. Its comprehensive testing suite
includes the ability to identify and locate physical layer faults.
Adherence to
Standards
The DigiTest EDGE is designed for the global environment and satisfies all
relevant U.S. and international telecommunications equipment requirements.
LoopCare and the

DigiTest EDGE
LoopCare is the test operations support system that drives the DigiTest EDGE. It
controls test access and implements all of the tests that are available in the
DigiTest EDGE.
Test Access Devices
The DigiTest EDGEs point of test access is the subscribers side of the loop with
respect to the DSLAM or NGDLC. Due to service provider demand to reduce preloop test access costs, DSLAMs and NGDLCs are increasingly incorporating
Metallic Test Access Units (MTAUs) as the point of access. Application scenarios
that lack an MTAU on the DSLAM or NGDLC must provide a separate test access
device on the subscriber side of the broadband access device, for example, the
TL1 version of the Tollgrade DAU1000 or the TL1 version of the Tollgrade
TelAccord 1000.
LoopCare Test
Analysis
Benefits
Prerequisites

DigiTest EDGE
LoopCare provides a complete voiceband and broadband characterization of the

loop. LoopCare analyzes the voiceband test results and reports any
abnormalities. It uses the broadband noise, bridged tap, load coil, and insertion
loss data to do the following.
Identify type and location of a wide variety of noise disturbers, bridged taps,
and load coils
Accurately predict the data rate for ADSL over SDSL and G.shdsl services
Provide quantitative information on possible improvement of data rate by

removal of bridged taps or the elimination of disturbers
The DigiTest EDGE provides the following benefits.
A single-unit, cost-effective solution for testing broadband services
Design for both International and U.S. environments
Ability to be deployed in CO-based and remote environments to test

through DSLAMs, ngDLCs and MTAUs
Support for all tests needed to completely characterize a loop for

broadband services
Combined with LoopCare, powerful analysis tool that detects faults on the
loop and directs the craft to the right places to repair the problem
Significantly enhanced accuracy of single-ended data rate prediction
DigiTest EDGE Feature
HP UX 11i, for Release 2.2 and above

or
Sun Solaris 8 Platform, for Releases 2.2 and above
or
HP UX 10.20, for Releases 2.5 and above
6-4


Overview
The DigiTest EDGE consists of a mounting shelf and the following plug-ins:
Plug-in
RAC
(Control
Module)
Required or
Optional
Description
Provides all of the external communications Required

interfaces to the DigiTest EDGE. The
DigiTest EDGE has the following ports:
An Ethernet TCP/IP port
4 serial ports that can be used for one

of the following:
An incoming port for an
external access server
A port from the DigiTest EDGE
as an access server to a
DSLAM, ngDLC or MTAU
4 Test Access Pairs (TAPs) that allow

test access to as many as four edge
devices (for example, DSLAMs,
NGDLCs or MTAUs). These TAPs
can also be configured to handle twowire full-split test connections that
permit look-in, look-out, and bridged
access.
LoopCare communicates directly with

DSLAMs to gain test access and to retrieve
operating status and performance
information.
Metallic Test
Module (MTM)
Optional
Provides all of the narrowband testing
functions of the DigiTest EDGE, including
voltage, resistance, capacitance, and
current, narrowband noise, wideband tones,
and most of the broadband testing functions.
The DigiTest EDGE is capable of full
metallic verification of the local loop, that is,
the physical layer.
The combination of an MTM card and an
XMU is not supported.

Plug-in
Single-Ended
Loop
Qualification
(SLQ)
Required or
Optional
Description
Provides precise broadband loop loss
information and length measurements that
help to improve the accuracy of data rate
predictions made by LoopCare.
Optional
The combination of an SLQ card and an

XMU is not supported.
Broadband
Services Unit
(BSU)
Supports xDSL modem emulation.
Optional
This functionality supports end-to-end tests

to the customer's Internet Service Provider
(ISP) or Voice Gateway, as well as
verification of the Digital Subscriber Line
Access Multiplexer (DSLAM) and
customers modems.
The BSU supports two types of DSL Modem
emulator plug-ins:
ADSL
G.SHDSL
These DSL modem emulators can act as
either an ATUR or ATUC, depending on the
test request. See the section on xDSL
Testing Configurations below.
Power Module
Provides the power for the box.
Required
Fan Module
Provides ventilation to cool the internal

components in the chassis.
Required
Filter Module
Filters the cooling air supply drawn into the

DigiTest EDGE chassis by the Fan Module.
Required
ATU-R Modem
Establishes communication to the EDGE

via an ATU-C configured modem in a
DSLAM.
Optional
The ATU-R Modem is part of the RAC card.

See the section on J21 Jumper Setup and
Communication with the EDGE below.
Analog Modem
Card
6-6
This module, located on a daugthercard on

the RAC, is used for direct-dial or leasedline communication mode to the EDGE.
Optional

Plug-in
eXtended
Measurement
Unit
Required or
Optional
Description
The eXtended Measurement Unit includes
all the functionality of the MTM. In addition, it
supports
The CALL, CALLRD, DIAL, MON,

REV, RING, TALK, TT, and XCB
interactive tests.
The Loop Insertion Loss (LIL)

capability.
There can be only one XMU on an EDGE.

If an EDGE has an XMU, remove the MTM
and SLQ cards if present.
xDSL Testing
Configurations
For testing ADSL, ADSL2+ and G.SHDSL, LoopCare supports the following
configurations.
Support
for
ADSL
Annex
A
Testing
Support
for
G.SHDSL
Testing
Support
for
ADSL2+
Testing
Support
for
ADSL2
Testing
Support
for
ADSL2
Annex L
Testing
Support
for
ADSL2
Annex
M
Testing
ADSL
Annex A
Yes
No
No
No
No
No
ADSL2+ -
Yes
No
Yes
Yes
Yes
Yes
Yes
No
No
No
No
ADSL
G.SHDSL Yes
Annex A
Yes
No
No
No
No
ADSL2+ ADSL
Annex A
No
Yes
Yes
Yes
Yes
BSU
Modem
Slot 1
BSU
Modem
Slot 2
G.SHDSL No
Yes

ADSL
ADSL2+
Annex A
J21 Jumper Setup

and Communication
with the EDGE
6-8
No
Yes
Yes
Yes
Yes
ADSL2+ G.SHDSL Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
Yes
No
The setup on the J21 jumper must match the intended method of communication
to the EDGE. Facing the front of the RAC card, the J21 jumper is in the front of the
card just off the left front corner of the ATU-R modem. It has 3 rows of pins with a
jumper across two rows. When the jumper goes across rows 1 and 2, the Ethernet
port on the front of the RAC card can be used to communicate with the RAC.
When the jumper goes across rows 2 and 3, the RAC ATU-R modem is engaged
and you must communicate to the EDGE via that ATU-R modem and the Ethernet
port on the front of the EDGE RAC card is disabled.
DigiTest EDGE Installation and

Configuration
Contents
Introduction
7-2
7-3
7-10
7-24
7-27
7-28
7-32
7-34
Routine Maintenance
7-40
7-41
7-47

Introduction
Introduction
Overview
This chapter describes the procedures required for configuring a DigiTest EDGE
within the LoopCare system.
It covers the following topics:
Basic EDGE access and communication properties
Setup and provisioning of LoopCare and EDGE
Testing configuration and process
This chapter includes high level guidelines for modifying both the physical and
database configuration of the EDGE. For detailed instructions on these
procedures see the DigiTest EDGE Broadband EDGE Test Platform User's
Manual.
7-2

Test Access and Communication

Properties
EDGE as Both Test
Device and Access
Server
The DigiTest EDGE can function as both an access server and a test device. The
four serial ports on EDGE support the access server function.When the EDGE
acts as an access server, its internal access server passes through TL1 or CLI
commands through these serial ports to connected network elements, such as
DSLAMs and ngDLCs, and separate test access devices. Figure 7-1 shows the
EDGE serial ports used in this manner.
The primary function of the EDGE is testing.The EDGE can perform metallic,
wideband and specific networking tests on physical lines through DSLAMs or
ngDLCs. The EDGE's Test Access Ports (TAPs) provide test access. The optional
Broadband Services Unit (BSU) on the EDGE performs the networking test
functions.
Communication
With the EDGE
There are four methods of communicating with the EDGE:
Ethernet IP direct - through the TCP/IP network directly to the Ethernet port
on the EDGE, as shown in Figure 7-1.
In this configuration, connect a cable to the Ethernet port on the front of the
EDGE.
Ethernet through EDGE ATU-R - through the TCP/IP network to the

DSLAM that serves the EDGE, as shown in Figure 7-5.
The DSLAM ATU-C communicates with the EDGE's ATU-R via a particular
access protocol, Bridged IPoA, for example.
In this configuration, connect a pair from the DSLAM to the ATU-R modem
port on the front of the EDGE. Configure the DSLAM to associate the static
IP address of the EDGE with the specific pair that connects the DSLAM to
the EDGE ATU-R modem port.
Ethernet through an external access server - through the TCP/IP network

to an external access server that is directly connected to serial port on the
EDGE, as shown in Figure 7-4
In this configuration, connect a serial port on the access server to one of
the four serial ports on the EDGE.
Direct dial-up or leased-line communication with the RAC cards analog

modem.
The MTM and SLQ cards in the figures below can be replaced by the XMU.

TCP/IP
TCP/IP
LoopCare
Ethernet
Craft
Serial
Port
TL1
Internal
Modem
4 Serial
Ports
TelAccord
MTAU
CM (RAC)
TAP 1
MTM (IMU)
TAP 2
BSO (future)
Fan Card
TAP 3
TAP 4
Power
SLQ
Amulet 200 Phase 2Architecture
Figure 7-1.
7-4
Access
Control
ASAM
7300
DSLAM
LiteSpan
AnyMedia
DLC
DigiTest EDGE Using an Internal Access Server

TCP/IP
TCP/IP
LoopCare
External Modem
Ethernet
Craft
Serial
Port
TL1
Internal
Modem
Access
Control
4 Serial
Ports
TelAccord
MTAU
CM (RAC)
TAP 1
MTM (IMU)
TAP 2
BSO (future)
Fan Card
TAP 3
TAP 4
Power
SLQ
Amulet 200 Phase 2Architecture
Figure 7-2.
ASAM
7300
DSLAM
LiteSpan
AnyMedia
DLC
DigiTest EDGE Using an External Modem
The External Modem is connected to the RAC internal modem by an analog line.
Figure 7-3.
7-6

DigiTest EDGE Using an Internal Access Server

Leased Line
Figure 7-4.
DigiTest EDGE Using a Leased-Line Connection
The Leased Line is connected to the RAC internal modem by a straight cable.

DATA CENTER
Alcatel
AMS
Line
LoopCare
Server
Rec
DB
REPAIR CENTER
Datatek
DT-6061
PCs
Printers
CORBA API
TL1
LAN
LAN
/IP
TCP tions
ica
n
u
m
Com etwork
N
Central Office
Remote Site
DT-4000
LTS
Customer Premises
Router
T, R, S, G
ATU-C
2X-90
MAP
Nortel
DMS-100
MTA
LC
SMA
T, R, I
TAP2
Alcatel
Alcatel
Litespan
COT
EIU
303
GR-
TAP1
Litespan
RT
2-Wire ADSL Line
RS-232
Callback Line
PGTC
MCU
ADLUD4EP
ADLUD4EP
MCU
Dist. Frame
Figure 7-5.
Test Access Port

Configuration
7-8
Splitter
NOTE: Architecture shows LTCN (LTS

TCP/IP Communications Network) used for
communications to the LTS.
DSL Testing Architecture with LiteSpan RT with Communications via

the ADSL Modem on the DigiTest EDGE Control Module
As Figure 7-1, Figure 7-4, and Figure 7-5 illustrate, the Test Access Ports on the
EDGE connect to test ports on access devices. There are eight Test Access Port
(TAP) wires on the EDGE with fixed positions that can form either 4 two wire TAPs
or 2 four wire TAPs. Table 7-1 specifies the association between TAP wire
positions and TAP IDs. See the DigiTest EDGE Broadband EDGE Test Platform
User's Manual for more information on DigiTest EDGE TAPs.

Table 7-1. DigiTest EDGE TAP Wire Configurations

TAP ID
TAP WIRES
TAP 1
1 and 2
TAP 2
3 and 4
TAP 3
5 and 6
TAP 4
7 and 8
TAP GROUP 1
1 and 2 for lookout

3 and 4 for lookin
TAP GROUP 2
5 and 6 for lookout

7 and 8 for lookin

Configuring the EDGE to Work with

LoopCare
Overview
It may be necessary to physically modify the Control Module on the EDGE in

order for the EDGE to inter-work with LoopCare. The method of communication
between LoopCare and the EDGE determine what changes are required. An
internal database on the EDGE stores configuration information related to the
network, ATU-R, serial ports, and BSU card. The Physical Modification of the
EDGE Control Module and Provisioning the EDGE Database sections provide
high level guidelines for the physical and database configuration of the EDGE. For
more detail and diagrams, see the DigiTest EDGE Broadband Test Platform
Users Manual.
Physical
Modification of the
EDGE Control
Module
The following table summarizes the changes to the Control Module required by
each of the three communication modes between LoopCare and the EDGE.
NOTE:
Where J21 pin modifications are required, communication with the EDGE is
not possible without the correct settings.
Table 7-2. Physical Modifications to the EDGE Control Module

Communication Mode
Ethernet IP Direct Connection
Modifications
Place the jumper on the J21 pins in the
Ethernet Front position.
Viewing the front of the Control Module,
the J21 jumper should be on the left
most two columns of pins and the last
column of pins should be uncovered.
Ethernet through EDGE ATU-R
Place the jumper on the J21 pins in the

Ethernet DSL position.
the J21 jumper should be on the rightmost two columns of pins and the first
column of pins on the left should be
uncovered.
7-10

Table 7-2. Physical Modifications to the EDGE Control Module

Communication Mode
Modifications
Direct dial-up or leased-line connection Place the J21 jumper in the Ethernet
to the RAC analog modem.
Front position.
the J21 jumper should be on the left
most two columns of pins and the last
column of pins should be uncovered.
Ethernet through external access
server
Provisioning the
EDGE Database
No modifications are required.

The J21 jumper position is irrelevant.
At this point it is assumed that the EDGE is physically installed and powered and
that all other network elements required to support EDGE communication are in
place.
It is necessary to answer certain questions about the communications modes
used by the EDGE, its physical configuration, and its connections to other
equipment in order to determine how to configure the internal database on the
EDGE. The following table presents configuration guidelines based on these
questions.

Table 7-3. Guidelines for Configuring the EDGE Internal Database

Question
EDGE via Ethernet IP direct method?

If yes, then:
1.
Connect the IP cable from the

network to the Ethernet port on
the front of the EDGE.
2.
EDGE IP address
Gateway IP for EDGE to

DNS IP for EDGE to use

in customer network
Subnet Mask for EDGE to

Go to the EDGE Network

Provisioning section for more
information on how to enter this
data in the EDGE.
7-12
3.
After the network information

has been entered and the EDGE
rebooted attempt to telnet and
login to the EDGE to verify the
communication link is working.
4.

EDGE's serial ports. See the
EDGE Network Provisioning
section for more information.


Question
EDGE via the Ethernet through
external access server method?

If yes, then:
1.
Connect a port on the access

server to a specific serial port on
the EDGE using the appropriate
cable and connectors.
2.
Identify the following information

about the access server:
Type of access server
IP address of the access

server.
Serial port/TCP id used to

communicate to EDGE
Serial port configuration

parameter values
required to communicate
to the EDGE (e.g. baud
rate, parity, bits, stop bits,
etc.).
3.
Configure the access server

database with the data listed
above. Follow the procedures
provided by the access server
vendor.
4.
Configure the EDGE serial port

to be compatible with the access
server port. See the EDGE
Serial Port Provisioning section
for more information.
5.
Telnet and login to the EDGE to

verify that the communication
link is working.
6.

EDGE serial ports. See the


Question
EDGE via the Ethernet through EDGE
ATU-R method?

If yes, then:
1.
Connect the line from the

DSLAM (ATU-C) to the ATU-R
modem port on the front of the
EDGE.
2.
EDGE IP address
Gateway IP for EDGE to

DNS IP for EDGE to use

in customer network
Subnet Mask for EDGE to

See the EDGE Network

information on how to enter this
data in the EDGE.
3.
Provision the EDGE ATU-R to

match the DSLAM ATU-C
configuration.
See the EDGE ATU-R
information on how to provision
the EDGE ATU-R.
7-14
4.
After provisioning the EDGE

ATU-R and network information
and rebooting the EDGE, telnet
and login to the EDGE to verify
that the communication link is
working.
5.

EDGE serial ports. See the


Question
EDGE via the RAC analog modem by
direct dial-up?

If yes, then:
1.
Connect the telephone line to

the RAC internal modem port.
2.
Identify the following

information:
Telephone number used
to connect to the EDGE
analog modem.
The baud rate used to
connect to the EDGE
RAC analog modem.
See the section on EDGE Serial
Port Provisioning for information
on how to enter port data for the
EDGE leased-line connection.
3.

modem for dial-up
communication, use the dial
utility to connect to the EDGE
and log in.
You may also log in to the EDGE and

at the RAC prompt enter the term
com3 command to access the EDGE
analog modem. You can then enter
regular modem commands to send at
commands. The <ESC> key can be
used to break out of this modem
console mode.


Question

If yes, then:
EDGE via the RAC analog modem by a
1. Connect the leased-line cable to
leased-line connections?
the internal modem port.
2.
Identify the baud rate of the

leased line.
See the section on EDGE Serial
Port Provisioning for information
on how to enter port data for the
EDGE leased-line connection.
3.

modem for leased-line
communication, use telnet to
login to the EDGE.
EDGE leased lines typically go through

a leased-line modem off an access
server. Therefore, the telnet connection
will have the IP address of the access
server and the TCP port of the leasedline modem.
Will the EDGE serial ports be
connected to other equipment?
Will the EDGE operate with a BSU

card?
EDGE Craft Port

Interface
If yes, then:
See the EDGE Serial Port Provisioning
If yes, then:
See the EDGE BSU Provisioning
Under certain conditions, the only method of communicating to the EDGE is

through the craft port.
When no Ethernet communication path to the EDGE has been established.
When it is necessary to talk directly to a specific card on the EDGE, for

example, the BSU.
One way to connect to an EDGE craft port is via a direct connection from the
COM1 port on a PC using a program such as Hyperterminal. Table 7-4 specifies
the required craft port communication parameter values for specific EDGE
modules.
7-16

Table 7-4. Craft Port Communication Information

Connected EDGE
Module
Control Module
Metallic Test Module or

BSU
EDGE Network
Provisioning
Craft Port Information

Craft port is a DB9
Female/
Craft port is a 5 pin

connector that requires
a special cable to
connect to it from a PC.
Communication Parameters
Baud = 38400
Parity = N
Bytes = 8
Stop Bits = 1
Flow = XON/XOFF
Baud = 38400
Parity N
Bytes = 8
Stop = Bits 1
Flow = XON/XOFF
Network data for the EDGE is configured in the Control Module database. The
ROUTER command takes you to network data entry mode. Table 7-5 describes
some key network configuration commands that can run in this mode.
Table 7-5. EDGE Network Configuration Commands

EDGE Command
Command Description
DEFAULTIP

EDGE.
GATEWAY

the EDGE.
SUBNET

EDGE.
DNS
Add or change the EDGE's DNS IP

address.
SHOW
Display network data associated with

the EDGE, including its IP address,
gateway address, and subnet mask.

Table 7-5. EDGE Network Configuration Commands

EDGE Command
Command Description
DISPLAY
Display network data specific to the

EDGE serial ports, including their IP
addresses, TCP IDs, timeout values,
and port names.
MODIFY X
Edit network data specific to an EDGE

port.
X = 1 to 6 (port number).
See Table 7-6.
LoopCare requires a specific TCP ID for each EDGE port. Table 7-6 specifies the
required TCP IDs.
Table 7-6. TCP IDs Required By LoopCare for EDGE Serial Ports
Port Number
Port Description
Port TCP ID
EDGE main port, used

by LoopCare
6000
Telnet port
23
Serial port 1
6010
Serial port 2
6020
Serial port 3
6030
Serial port 4
6040
Run the DISPLAY command to verify that each EDGE port is configured with the
primary IP address of the EDGE and the required TCP ID. If this is not the case,
run the MODIFY command to edit the data.
Usually it is necessary to reboot the EDGE to activate network changes. To
reboot, run the REBOOT command on the main level of the EDGE command
menu or power cycle the EDGE.
7-18

EDGE ATU-R
Provisioning
If LoopCare communicates to the EDGE through the EDGE ATU-R modem,

provision the ATU-R in the Control Module database to match the DSLAM
protocol configuration, for example, Bridged IPoA with static addressing. See the
DigiTest EDGE Broadband EDGE Test Platform Users Manual for details.
EDGE Serial Port

Provisioning
Enter port configuration data into the Control Module database.The PORT
command takes you from the main level of the Control Module data entry mode to
the port data entry level.Table 7-7 describes some key commands that can be
entered on the port data entry level. Changes take place immediately without a
reboot of the EDGE.
Table 7-7. EDGE Port Configuration Commands

EDGE Command
Command Description
DISPLAY
Display port data, such as port name,

baud rate, bytes, parity, etc.
CHANGE X
Edit edit port data.

X = 1 to 6 (port number).
See Table 7-6.for a description of each
EDGE port.
Table 7-8 specifies the values for the Name and Port fields that are required for
the EDGE to work with LoopCare.
Table 7-8. EDGE Port Name and Port Field Values

Port Name Field Value
Port Field Value
PORT1
COM4
PORT2
COM5
PORT3
COM6
PORT4
COM7

Table 7-9 provides the settings for a direct serial port connection to a TelAccord or
DAU 1000.
Parameter
Setting
NAME
DSLAM1
PORT
COM4
BAUD
19200
PAR
WORD
STOP
ECHO
OFF
RTS
OFF
CTS
OFF
DTR
OFF
DEV
DTE
CONN
DIRECT
Table 7-10 specifies the settings for a direct serial port connection to an ASAM
7300.
Parameter
7-20
Setting
NAME
DSLAM1
PORT
COM4
BAUD
9600
PAR
WORD
STOP
ECHO
OFF
RTS
ON
CTS
ON
DTR
ON

Parameter
Setting
DEV
DTE
CONN
DIRECT
Table 7-11 specifies the settings for a direct dial and leased line connections
Table 7-11. Settings for a Direct Dial or Leased Line Connection
Parameter
Setting for Direct Dial
Setting for Leased Line
NAME
MODEM
MODEM
PORT
COM3
COM3
BAUD
To be determined, for example, To be determined, for example,

9600
38400
PAR
WORD
STOP
ECHO
OFF
OFF
RTS
OFF
OFF
CTS
ON
ON
DTR
OFF
OFF
DEV
DTE
DTE
CONN
MODEM
LEASED
init string
AT$SB38400EL2&D)&W)
NOTE:
The digits in bold in this
value indicate the baud
rate of the leased line.
Enter the appropriate
value.
init string
For MT56345MI9Z:
ATS0 = 0&L0&D0&W0
For MT56345MI90:
ATS0 = 1L0M0

Table 7-12 specifies the settings for a direct serial port connection to an ASAM
7300.
Parameter
Setting
NAME
DSLAM1
PORT
COM4
BAUD
9600
PAR
WORD
STOP
ECHO
OFF
RTS
ON
CTS
ON
DTR
ON
DEV
DTE
CONN
DIRECT
Table 7-13 indicates the recommended timeout values in minutes for a DigiTest
EDGE in a LoopCare application. Use the MODIFY command to set these values
in DigiTest EDGEs Router Table. For more information, see the DigiTest EDGE
Broadband EDGE Test Platform Users Manual.
Table 7-13. Recommended Timeout Values for the DigiTest EDGE

Port Information
Recommended Timeout
LoopCare (TCP 6000)
120
Telnet (TCP 23)
Serial Port 1 (TCP 6010)
The zero values disable the timeout function for the indicated ports, but the value
of the LoopCare (TCP 6000) port overrides these zero values.
7-22

EDGE BSU
Provisioning
If the EDGE is configured with a BSU card, login to the BSU craft port and verify
the contents of the BSUs router table. The BSU uses the same set of commands
listed in the EDGE Network Provisioning section, for example, ROUTER, SHOW,
and SUBNET. Verify the BSU's router information (for example, IP, Gateway,
subnet). Use the appropriate BSU commands to edit the data.

Configuring LoopCare - System

Configuration
Overview
Several LoopCare system entities must be configured to enable testing with the
EDGE. Others are available for tuning EDGE testing.
Feature File
Table 7-14 lists the LoopCare features related to the EDGE and describes their
role in EDGE testing.Existing customers upgrading from LoopCare release R2.1
must ensure that they obtain the most current feature file. Consult your LoopCare
Customer Support representative.
Table 7-14. LoopCare Features Related to the EDGE

Feature
(192) DIGITEST EDGE
Role
Enables LoopCare testing with EDGE.
(236) Broadband Services (BSU ADSL) Enables LoopCare testing through the
EDGE's BSU module for ADSL,
ADSL2, ADSL2+, and VDSL.
(258) Broadband Services (BSU
G.SHDSL)
Enables the BSU module on the EDGE

to perform G.SHDSL test requests.
(260) ATUR DETECT
Enables LoopCare to detect additional

modem signatures.
(142) WIDEBAND
Enables LoopCare wideband testing.

If the Broadband Services (BSU ADSL)
or Broadband Service (BSU G.SHDSL
feature is on, the WIDEBAND feature is
not required.
(148) DATA RATE
Enables data rate prediction.

Essential only if the EDGE performs
wideband data rate prediction.
(174) OPTIMIZE
Optimizes data rate prediction.

Essential only if the EDGE performs
wideband data rate prediction.
7-24

Installation of the
dmic Module
The dmic module is activated though the MGRP.gdf file. This module enables
LoopCare to access and test through the DigiTest EDGE. A standard entry for the
dmic module in MGRP.gdf should look something like this:
F:$MLT_BIN/dmic
-o,250,-u,1
dmic
See Appendix A in the System Administration Guide (Group Descriptor file for
MGRP) for a complete review of the dmic module setup.
Environmental
Variables
See Appendix A of the System Administration Guide (User Definable Environment

Variables for MGRP.env and M2.env) for a complete review of all environment
variables that are associated with the DigiTest EDGE testing and operation.
custenv
Use the following procedure to set DigiTest EDGE-related variables in the

customer environment.
1.
Login as mlt.
2.
Run custenv.
The Customer Environment page is displayed.
3.
Press the <F10> key.

The Navigation Menu is displayed.
4.
Select the 1.ADDITIONAL CUSTENV INFO option.
5.
Select either option for the Metallic Results Heading field.
6.
Select the Yes value for the Display AC Capacitance Data field.
7.
Select either option for the Filtered Noise Units field.

In the U.S., use C-Message Noise filter and display units of dBrn.
In Europe, use Psophometric Noise filter and display units of dBm.
8.
Press the <F6> key to access the command buttons at the bottom of the
page.
9.
Save changes and exit the custenv utility.
10.
BSU
Bounce MDMN for these changes to take effect for the GUI.
The following procedures assume that the DigitTest EDGE with a BSU card has
been correctly installed and configured to interact with LoopCare and an access
device.

1.
Optionally create between 1 and 10 profiles for BSU testing. See the
section of DSL IP Test Parameters of Chapter 9 of the Operations,
Administration and Maintenance (OA&M) Guide.
2.
On the User Request Configuration form (see the section on User Groups
in Chapter 9.) set the following indicator:
Display BSU - to allow DSL Test Parameters (including profiles) to be
displayed on the Test Circuit Page of the GUI. See Chapter 2 of the Test
User Interfaces Guide.
3.
Indicate the default Profile to be displayed on the Circuit Test Page.
If the Broadband Services (BSU ADSL) or Broadband Services (BSU G.SHDSL)

feature is enabled, testers are now able to submit network specific requests on
the LoopCare GUI.
7-26

Configuring LoopCare - ADEF Data

Entry
Overview
To configure LoopCare to work with an EDGE, it is necessary to configure three

entities, an access server, the EDGE itself, and its connected LTEs. Table 7-15
outlines the configuration process.
Follow ADEF procedures for entering, saving, submitting, and activating data.
Table 7-15. ADEF Configuration Processes for the EDGE

For this Process
See
page 7-28
page 7-32
Configure an LTE Connected to an

EDGE
page 7-34


The process for configuring an access record depends on the mode used by
LoopCare to communicate with the EDGE.
Table 7-16. Access Server Configuration and Communication Modes

Communication Mode
Access Server Configuration
Ethernet through an external access

server
See Configure an External Access

Server for the process of configuring an
external access server.
Ethernet IP direct
See Configure the EDGE as an Access

Server for the process of configuring
the EDGE as an internal access server.
Ethernet through EDGE ATU-R modem See Configure the EDGE as an Access
Server.
Configure an
External Access
Server
7-28
Dialup via analog modem

Server and Dial Group and ModemPool
Setup
Leased line via a RAC analog modem

Server
Use the Access Server ADEF form to configure an external access server. This
form describes the access server and its connections. Table 7-17 specifies the
required data.

Table 7-17. Required ADEF Fields for an External Access Server

Access Server Form Page
Access Server Form - Main page
Required Fields and Values
Access Server ID
User defined
IP address
IP address of the access server
New Access Server ID

Defaults to the Access Server ID
Access Server Type

OTHER
Access Server Form - Terminal Server

page
Service Name
User defined service name
associated with an external
access server port and TCP ID
for a direct connect, leased line,
or a modem pool.
TCP
TCP number associated with the
access server port and server
name
Follow all ADEF procedures for entering, saving, and submitting data on the
Access Server form and activating the database. The next step is to configure the
DigiTest EDGE as an RMU-S. Go to the Configure an EDGE as an RMU-S
section.
Configure the
EDGE as an Access
Server
Use the Access Server ADEF form to configure the EDGE as an access server.
This form describes the EDGE internal access server and its connections.
Table 7-17 specifies the required data.

Table 7-18. Required ADEF Fields for an EDGE Internal Access Server
Access Server Form Page
Access Server Form - Main page
Required Fields and Values
Access Server ID
User defined
IP address
IP address of the EDGE access
server
New Access Server ID

Defaults to value of Access
Server ID
Access Server Type

DigiTest EDGE
Access Server Form - Terminal Server No data entry is required. All fields are
page
automatically populated. However, it is
necessary to navigate the Terminal
Server page to verify the setup. See
Table 7-19.
Table 7-19. Automatically Configured Data for Internal EDGE Access Server
Service Name
TCP IDs
Master
6000
SerialPrt1
6010
SerialPrt2
6020
SerialPrt3
6030
SerialPrt4
6040
The next step is to configure the DigiTest EDGE as an RMU-S. Go to the

Configure an EDGE as an RMU-S section.
Dial Group and

ModemPool Setup
7-30
For information on setting up a Dial Group and a Modem Pool, see the
appropriate sections in Chapter 5 of the OA&M Guide.

NOTE:
For an EDGE using direct dialup via a RAC analog modem, the EDGE
RMU-S form must specify the communication mode as modem dialup. A
Dial Group must be specified also.
The ADEF Dial Group form must be competed. This form identifies the
specific modem pool used to dial the EDGE plus any specific dial digits.
The Modempool form must be completed for the pool specified by the
EDGE Dial Group.


The RMU Standalone Test Head form provides details about the DigiTest EDGE
and its connections.
Table 7-20.
ADEF Data Entry for Configuring an DigiTest EDGE as an RMU-S
ADEF Form
RMU
Standalone
Test Head
Fields
RMU-S ID
User-defined, for example, DigiTest EDGE
Identification
A user-defined designation for the DigiTest EDGE
Communication Info
Select Access Server or Modempool
If Modempool is selected, enter a Dial Group ID.
Offset
This is the distance from the LTE wired to the first TAP. If no
LTE is wired to this TAP, enter the information after you
have wired an LTE to this TAP.
RMU-S Type
You must select DigiTest EDGE.
When you press Enter, a pop-up window is displayed
prompting you for the offsets for TAPs 2 to 4. If no LTE is
wired to a TAP, the value can be left blank and filled in when
an LTE is wired to the respective TAP.
Access Server
Use the drop-down list to select the Access Server ID to be
associated with the DigiTest EDGE.
See Create an Access Server Record: page 7-28.
Service Name
From the drop-down list, select the port on the Access
Server that will communicate with the DigiTest EDGE serial
port.
For a DigiTest EDGE acting as an access server, select the
Master Port.
7-32


Configure an LTE Connected to an

EDGE
Introduction
When an access device is associated with the DigiTest EDGE, the DigiTest EDGE
can be used to test subscriber lines on the access device.
This section describes the ADEF data entry procedures for configuring an access
device as an LTE and associating it with a DigiTest EDGE.
For the DigiTest EDGE there are three types of LTEs:
LTE Form
7-34
LTEs where LoopCare has test access control through the TL1 protocol,
such as a TelAccord, AMAS, ASAM 7300, AFC AccessMAX, ADTRAN TA
1500, ADTRAN TA 3000/TA 3050, ADC 528r, Ciena CN 1000, Zhone
AccessNode, mPhase BBLW, Paradyne GranDSLAM 8820, Tollgrade
MSAS, Entrisphere BLM 1500, Alcatel 7330, Calix C7 or Samsung
AceMAP.
LTEs where LoopCare has test access control through the CLI protocol,
such as a Turnstone CX100 and Hatteras HN4000.
LTEs where LoopCare has test access control through SNMP, such as a
the Zhone MALC.
LTEs where test access control is external, such as an Xpresslink or

Generic. LoopCare supports external test access for the DigiTest EDGE.
This means that test access control is established by an external system,
and LoopCare does not establish the connection to the tested line, but
rather initiates the test without attempting to set up a test access.
LTEs where LoopCare has test access control through a specific message
protocol, such as a Nicotra ITBM Switch Test Access Device.
The LTE form provides details about an LTE to be tested by the DigiTest EDGE.

Table 7-21.
Control
LoopCare ADEF Data Entry for a DSLAM with LoopCare Test Access
ADEF Form
LTE
Data Entry
LTE ID
Unique user-defined identifier for the LTE
For the following fields, see Table 7-22:

Vendor
Model
Language
LTE Group ID
Required
If the LTE Group entered already exists you will be
forwarded to the next field on the LTE form. If the LTE
Group entered does not exist you will be forwarded to the
ADEF LTE GROUP form where you must enter appropriate
data, then save and submit that form.
In/Out Thresh (Ft) Bypassed if the LTE model is LiteSpan
Access type
See Table 7-22.
Press <F10> to access the Navigation Menu.

Select the appropriate option on the Navigation Menu:
Communication Information: page 7-37
Metallic Testing Information: page 7-38
Security Information: page 7-39
Node Metallic Information: page 7-39

Table 7-22. Vendor/Model/Language/Access Type Combinations for DigiTest EDGE

Vendor
ADC
Models
Broadwire528r
Language
TL1
Access Type
Access Server
TCP/IP
ADTRAN
TA 15000/TA
3000/TA 3050
TL1
TCP/IP
AFC
AccessMAX LET TL1
TCP/IP
AFC
AccessMAX RST TL1
Access Server
ALCATEL
ASAM
Access Server
EXT-ACC
LITESPAN
EMS
TCP/IP
ALCATEL
7330
TL1
EMS
CALIX
C7
TL1
Access Server
TCP/IP
CIENA
CN 1000
TL1
Access Server
TCP/IP
ENTRISPHERE BLM 1500
TL1
TCP/IP
Generic
Generic
EXT-ACC
Not applicable
Hatteras
HN4000
CLI
TCP/IP
LUCENT
ANYMEDIA
TL1
TCP/IP
EXT-ACC
N/A
LUCENT
Stinger
SNNPv1
TCP/IP
SNMPv3
EXT-ACC
N/A
MPHASE
BBLW
TL1
Access Server
TCP/IP
7-36

Table 7-22. Vendor/Model/Language/Access Type Combinations for DigiTest EDGE

Vendor
NICOTRA
Models
ITBM
Language
N/A
Access Type
Access Server
TCP/IP
PARADYNE
GranDSLAM
TL1
TCP/IP
SAMSUNG
AceMAP
TL1
TCP/IP
SIEMENS
XPRESSLINK
EXT-ACC
Not applicable
TOLLGRADE
MSAS
TL1
Access Server
TCP/IP
TOLLGRADE
TelAccord
TL1
Access Server
TCP/IP
TURNSTONE
CX100
CLI
Access Server
TCP/IP
Zhone
AccessNode
TL1
EMS
Zhone
MALC
SNMP
TCP/IP
NOTE:
When the Language is EXT-ACC, the Access Type choice is not relevant.
When the Language is Not Applicable, there is no access to the Security
page of the LTE form.
NOTE:
LoopCare uses the Nicotra ITBM messaging protocol to communicate with
the Nicotra ITBM LTE.
Communication
Information
The Communication option on the Navigation Menu is available for most access
devices. The following combination of fields is available:

Table 7-23. Data Entry Guidelines for the Communication Page
If Access Type is
Access Server
EMS
Then Communication
Mode should be
Access Server
EMS
TCP/IP
TCP/IP
Related Data Fields
Access Server ID
Service Name
EMS ID
EMS Port
IP Address
TCP Port for some LTEs,

such as ADC
SNMP Port for some LTEs,

such as Zhone MALC.
See the Wideband Services Configuration Guide for more detail on configuring
this communication information.
Metallic Testing
Information
The Metallic Testing Information page allows you to specify the DigiTest EDGE as
the testhead that tests the lines on the LTE. It is required for all types of LTEs
except for LiteSpan. The following fields are required.
Metallic Testing - Select RMU Standalone
RMU-S ID -Select an DigiTest EDGE testhead.
This page does not apply to:
LItespan
Use the LiteSpan Metallic Information page instead.
AccessMAX LET
This page does apply to the AccessMAX RST.
AccessMAX RST
When performing DSLDIG testing, the AccessMAX RST does not require a
testhead.
Alcatel ASAM 7300

When performing DSLDIG testing, the ASAM 7300 does not require a
testhead.
7-38

Node Metallic
Information
Security
Information
The Node Metallic Information page allows you to specify the configuration of a
Node system with a DigiTest EDGE as the testhead. All configuration data
associating a LiteSpan LTE with an EDGE must be entered on this page. No data
can be entered on the Metallic Testing Information page.
Node Name Id
RMU-S ID
In/Out Threshold
DigiTest TAP No.
The Security Information option on the Navigation Menu is available for LTEs with
the TL1 or CLI language option. The following fields are required in the TL1/CLI
area:
Login
Password

Routine Maintenance
Routine Maintenance
Checking EDGE
Firmware Versions
When a new card is installed on the EDGE
Run diagnostics via the Admin GUI to verify the firmware version of each
card. Compare these versions to the firmware versions listed in the
version.cfg file.
Check the edgeLog.txt for any "Version Mismatch" messages for this
EDGE.
Whenever LoopCare connects to the EDGE, it compares the release
version of the actual EDGE, for example, 6.3, to the release version
specified in the SWDLD.cfg file. If LoopCare finds a mismatch, it logs a
message in the edgeLog.txt file.
7-40
Run a software download if any version mismatch is reported in either the

diagnostics output or the edgeLog.txt file.
Periodically run diagnostics to check the firmware versions.


Typical Testing
Scenario
When a test is initiated by LoopCare to test a DSLAM line served by an EDGE the
test flow takes place:
LoopCare opens communication to the LTE via the designated

communication method (IP direct, Access server, etc.). Once connected
LoopCare requests a test access path be established from the LTE's Test
Access Port to the line under test.
If the communication path to the DSLAM is off an EDGE serial port the
EDGE only acts as a pass through and never directly communicates to the
LTE.
In parallel with the communication to the LTE, LoopCare also establishes a

connection to the EDGE and requests test resources to be reserved on the
EDGE's TAP(s) that connect to the LTE in question. The EDGE's TAPs
should already be physically connected to the LTE's Test Access Ports.
Once all the above connections are made then LoopCare sends a series of
test requests to the EDGE to begin running tests over the TAPs to the line
under test. The results of the tests are passed back to LoopCare by the
EDGE.
Once testing is completed the reverse processes are used to disconnect

from both the DSLAM and the EDGE freeing all resources.
Typically any physical connection to the EDGE from an external access server
should follow the standard RS-232 limits and should be with 50 feet. If low
capacitance cable is used this range may be extended beyond 50 feet. Refer to
manufacturer's specifications for maximum lengths for any particular low
capacitance cables.
Testing With the

BSU
The Broadband Services Unit (BSU) of the EDGE in conjunction with LoopCare
provide Telecommunications services with the ability to quickly isolate broadband
service troubles from a remote location. The test set can be divided into the
following general categories:
Look In- Tests directed from the BSU back towards the DSLAM. In these
tests the BSU emulates an ATU-R and provides test functions like modem
syncing, pinging, ATM loopbacks, etc.
Look Out- Tests directed from the BSU out towards the customer. In these
tests the BSU emulates an ATU-C and provides test functions like modem
syncing and ATM loopbacks.
A typical network architecture for supporting ADSL Annex A services is provided

in Figure Figure 7-6. Here ADSL service is provided via a DSLAM in the Central

Office. On the downstream (toward the customer) side of the DSLAM loops are
connected which ultimately are used to communicate with DSL modems (ATU-Rs)
at the customer premises.
On the upstream (toward the network) side the DSLAM is connected to an ATM
edge switch via a SONET network. The ATM network connects to the ISP and the
Public Internet via an IP Gateway router. The copper loop that is used to provide
DSL service to the customer may also be used to provide voice service (line
sharing). In that case, splitters may be used to screen out the narrowband portion
of the signal from the ATU-C in the DLSAM and the ATU-R at the customer site.
The wideband portion of the signal from the Class 5 switch in the Central office
will also be screened out from the voiceband terminal at the customer site.
POTS Splitter
To
Customer
HPF
To
DSLAM
LPF
SIG
Central Office
DNS
Server
IP Gateway
Router
Application
Server
Public
Internet
Figure 7-6.
Supported LTEs
7-42
SONET
Transport
Network
DSLAM
ATU-C
ATU-C
Splitter
MDF
DHCP
Server
To Voice
Switch
ATM
Switch
ATU-R
Class 5 Switch
LU
LU
Customer Premises
Network Architecture for Providing DSL Service
LoopCare communicates directly with ngDLCs, DSLAMs, with integrated MTAUs,

external MTAUs, and the ADC 528r Splitter. It uses either the terminal server of
the DigiTest EDGE, an external access server or a direct Ethernet access to send
either TL1, CL1 or SNMP messages to gain test access. A list of DSLAMs to
which the EDGE can provide test services, including network, is presented in the
table below:

LTE Model
Type
Method to Communicate to LTE
TelAccord (also
DAU1000)
MTAU
Off DigiTest EDGE serial port (TL1)
Alcatel ASAM
7300
DSLAM with
integrated
MTAU

or
Through IP Ethernet (TL1)
ADC 528r
Splitter
Lucent Stinger
DSLAM with
integrated
MTAU
Through Stinger Ethernet IP only (SNMP)
Lucent AnyMedia ngDLC
Through AMAS Ethernet IP only (TL1)
Alcatel LiteSpan
Off DigiTest EDGE serial port
ngDLC
or
Alcatel 7330
DSLAM

or
Generic (EXT
ACC)
external
access
Not applicable.
ADTRAN TA
1500
DSLAM
Through IP Ethernet
ADTRAN TA
3000/TA 3050
DSLAM
TCP/IP telnet socket to the Enhanced

System Controller Unit (ESCU). The ESCU
supports up to eight TL1 sessions, however,
only one of those sessions can be a test
session for a TA 3000 shelf or shelf cluster.
Primary Controller Unit (PCU)
AFC AccessMAX ngDLC
Off DigiTest EDGE serial port (TL1) for RST

or
Through IP Ethernet (TL1) for LET
NICOTRA ITBM
Similar to a
MTAU
Off DigiTest EDGE serial port or Through IP

Ethernet (ITBM messaging)

LTE Model
Type
Method to Communicate to LTE
Calix C7
BLC

or
Ciena CN 1000
BLC

or
Entrisphere BLM
1500
BLC
Hatteras HN4000 Ethernet

DSLAM

Off DigiTest EDGE serial port (CLI)
or
Through IP Ethernet (CLI)
mPhase BBLW
MTAU/Splitter Off DigiTest EDGE serial port (TL1)

or
Paradyne
GranDSLAM
8820
DSLAM
Samsung
AceMAP
DSLAM
Tollgrade MSAS
MTAU/Splitter Off DigiTest EDGE serial port (TL1)

or
Turnstone CX100 MTAU
Off DigiTest EDGE serial port (CLI)

or
Through IP Ethernet (CLI)
Supported Test
Requests
7-44
Zhone
AccessNode
DLC
Zhone MALC
PLC (Packet
Loop Carrier)
Through IP Ethernet (SNMP)
For test requests supported by EDGE with these LTEs, see Appendix A of the
Wideband Services Configuration Guide.

LoopCare allows network look-out requests for DSLAMs that are testable only by
a 2-wire TAP and those that support 4-wire taps but for some reason are only
configured for 2-wire TAPs.
LoopCare blocks network look-in requests on LTEs that operate only in 2-wire
TAP mode as well as those that are only configured for 2-wire tap operation.
POTS Keep-Alive
Capability
The BSU POTS Keep-Alive capability allows network test requests to be executed
on the subscriber line without disrupting voiceband POTS service. This capability
requires a test access device that provides 2-wire full split test access. LoopCare
currently supports this function on the Alcatel ASAM 7300, the ADC Broadwire
528r Splitter, Nicotra ITBM, Ciena CN 1000, Entrisphere BLM 1500, Tollgrade
MSAS, mPhase BBLW, Alcatel 7330, Samsung AceMAP and Calix C7. POTS
Keep-Alive does not apply to narrowband or wideband metallic test requests.
CAUTION:
When performing tests using the Nicotra ITBM and an EDGE BSU with
POTS Keep-Alive activated, when the tester performs a metallic test, POTS
service is disrupted. Before commencing metallic testing, the tester should
drop access with the X request.
The system administrator can override POTS Keep-alive functionality with the
KEEPALIVE_OVERRIDE environmental variable. See the Appendix B of the
System Administration Guide.
Supported Features
and Functions
The DigiTest EDGE supports the following LoopCare features and functions.
5ESS ISDN Status Verification
ADC BroadWire 528r Splitter
Batch Testing
ADSL, ADSL2, ADSL2+, VDSL and G.SHSDL testing
VoIP Testing
Dial Tone Feature
Fax Unalert for DMU
Loop Length Enhancement
MTU Detection
Opens Reduction

RT Based ADSL Service Testing
Split NPANXX Support
xTU-R Detection
For additional information about these features and functions, see the System
Description.
7-46

Complete Layer 1-7 Testing with a

LiteSpan
The complete Layer 1-7 Testing solution uses the DigiTest EDGE equipped with
the BSU card at the NGDLC RT as an add-on to the physical layer testing
performed using the CO Test Unit and the MCU.
Overview
DATA CENTER
Work
Manager
REPAIR CENTER
Line
LoopCare
Server
Datatek
DT -6061
Rec
PCs
Printers
DB
CORBA API
CORBA API
LAN
LAN
TCP/IP
Communications
Network
Central Office
Customer Premises
Remote Site
DT-4000
LTS
T, R, S, G
Dist. Frame
Callback Line
PGTC
Modem
TAP
2X-90
Alcatel
Nortel
DMS-100
MTA
Alcatel
Litespan
COT
LC
SMA
303
GR-
MCU
T, R, I
Figure 7-7.
Litespan
RT
MCU
RPOTS
NOTE: Architecture shows LTCN (LTS
TCP/IP Communications Network) used for
communications to the LTS.
Complete Layer 1-7 Testing Solution with a LiteSpan
Figure 7-7 illustrates the configuration for Complete Layer 1-7 Testing with a
LiteSpan. The solution also supports the AFC AccessMAX, in which case the
Litespans at the Central Office and the Remote Site would be replaced by AFC
AccessMAX LTEs.
The solution is applicable to NGDLC systems (for example, Alcatel LiteSpan and
AFC AccessMAX) capable of offering combined POTS and ADSL services via a
single port at the RT.
The NGDLC system is currently LoopCare testable via a metallic bypass pair or a
Tollgrade MCU pair.

The DigiTest EDGE with four two-wire TAPs supports up to two NGDLCs (for
example, Alcatel LiteSpan RTs) at a remote site. Even though the DigiTest EDGE
can be connected to two RTs, only one test per EDGE is supported since the
EDGE can only perform one test at a time.
The NGDLC System is deployed in GR-303 mode with contiguous OE Ranges for
each AFC and Alcatel RT.
OE Retrieval for testing by TN is supported for the Lucent 5ESS and Nortel DMS100 Class 5 Switches. OE Retrieval is supported for both the single active
LoopCare Server architecture and the active/active architecture.
Components Used
Testing with a
DigiTest EDGE
with/without an
MTM or XMU
7-48
The solution uses the following components.
Tollgrade DigiTest EDGE test hardware consisting of a Digital EDGE

Test Unit with a Broadband Services Option (BSU) card installed at the RT.
The BSU card is equipped with an ATU-C/R (ADSL Transmission Unit Central Office/Remote) daughtercard.
A TL1 interface from LoopCare to the NGDLC Element Management

System (EMS): This interface is used for sending TL1 messages to the
NGDLC. When testing by TN, this interface is used to map the CRV to the
RT ID and Access IDentifier (AID). Subsequent TL1 messages are used to
obtain status and performance monitoring information for the customer's
ADSL service as well as to control test access for the network tests.
For lines served by Lucent 5ESS switches, a Data Requester interface into
Telcordia's NSDB line-records system. This interface is used by LoopCare
tp retrieve the Originating Equipment (OE) Number for the customer
Telephone Number. The OE is parsed for the GR-303 Call Reference Value
(CRV), which is used to determine the Interface Group and RT ID. This
capability is enabled by checking the Enable NSDB checkbox on the
Switch Communication Information form in OA&M.
For lines served by Nortel DMS-100 switches, a telnet interface into the
Nortel DMS-100 switch, which is used by LoopCare to retrieve the
Originating Equipment (OE) Number for the customer Telephone Number.
The OE is parsed for the GR-303 Call Reference Value (CRV), which is
used to determine the Interface Group and RT ID.
The Switch Remote Terminal form contains a Test Method field. If this field is set
to D, POTS and ADSL testing is performed from the Central Office to a remote
DigiTest EDGE testhead. To perform POTS testing, the EDGE requires an MTM
or XMU. Otherwise, only ADSL testing is performed through the BSU on the
EDGE/

Release 2.7 and higher add a C method. With this setting, testing is divided into
two segments.
POTS testing up to the DSLAM is performed by the CO testhead.
ADSL testing of the ATM or ATU-R is performed from the BSU on the
remote DigiTest EDGE. This does not require an MTM or XMU on the
EDGE, since the EDGE does not perform any metallic tests.
LoopCare supports testing by the C method for the LiteSpan and the AFC
AccessMAX LTEs.
7-50

Contents
Introduction
8-2
8-3
8-4
8-6

Introduction
Introduction
Overview
8-2
This chapter describes the procedures for configuring a HUB as a Central Office
(CO) test head within the LoopCare system.It includes high level guidelines for
modifying both the physical and database configuration of the HUB. For detailed
instructions on HUB procedures see the DigiTest HUB Installation Manual.

The basic physical elements for Hub installation include:
Power
Grounding
Fusing
Peripheral equipment includes:
No Test Trunks
MDF Trunks
Telephone lines for callbacks (3 per HUB)
Trunk calibration line
IP connectivity
For detailed installation instructions see the DigiTest HUB Installation Manual.
The following restrictions and guidelines apply to the installation of equipment in
pluggin slots:
Do not plug a BSU into slot 12.
Insert the first TMU into slot 12. Subequent TMUs can occupy any other
slot.
To maximize the efficiency of the BSU

Do not insert an XMU used to test NTT or MDF trunks to the right of
and adjacent to a BSU.
Do not insert BSUs into adjacent slots.
If you are replacing a DMU installationed in a 5ESS switch remove the

series 650 Ohm resistors in the Tip and Ring conductors.


Introduction
Before LoopCare can test with a HUB, the HUB must be provisioned manually
through its craft port with network data, such as its IP address and gateway. The
HUB must identify its own IP address and the networking elements that it must
use to communicate with LoopCare and the external world.
Craft Port Interface
You need an interface program to communicate to the HUB via its craft port. One
way to connect to an HUB craft port is via a direct connection from the COM1 port
on a PC using a program such as Hyperterminal.
The details of the connectors and setup of Hyperterminal are:
Craft port connector: DB9 female
Baud rate and related information: 38400-N-8-1
Flow control: none
The Craft port connector is on the front of the HUBs SCU card.
Network
Configuration
1.
Log into the craft port via your craft interface program, e.g. Hyperterminal.
The prompt SCU Password: appears
2.
Enter a valid password, such as supervisor.
3.
Select the ROUTER command to display the network routing data area.
4.
Select the appropriate commands to enter network data. The available

commands are:
Table 8-1. HUB Network Configuration Commands

EDGE Command
8-4
Command Description
DEFAULTIP

HUB.
GATEWAY

the HUB.
SUBNET

HUB.

Table 8-1. HUB Network Configuration Commands

EDGE Command
DNS
Command Description
Add or change the HUB's DNS IP
address.
5.
Select the BACK option to go back to the main menu.
6.
Select the REBOOT command to reboot the SCU. Rebooting the SCU
results in a reboot of the entire HUB.
7.
Verify that the network data
8.
Verify that the network data is operational by attempting to login to the HUB
from the outside world. You can use one of the following methods, for
example:
telnet:
Usage (telnet [HUB IP] )
nodial:
Usage (nodial [HUB IP] 6000).
6000 is the TCP port number of the HUB's SCU.
MDF Trunk TAP

Matrix
Configuration
The highest 3 TAP pairs on a TMU in slot 12 (19-20, 21-22 and 23-24) can be
configured in pairs to support MDF testing. The odd numbered TAP is the look-out
TAP and the even numbered TAP is the look-in TAP. The look-out TAP is bridged
to the look-in TAP when the TAPs are in the idle state so that a customer
continues to have service when a test shoe is connected to the line. No external
MDF Trunk Circuit is required, in contrast to MDF trunks connected to an XMU.
To set up the bridged mode on MDF Matrix taps, you must set a physical switch
on the TMU card. The SAM display status command report indicates an improper
switch setting for a TAP pair assigned to an MDF trunk.

Configuring LoopCare - ADEF Data

Entry
After setting up and configuring the HUB, enter data in the LoopCare database.
Table 8-2 lists the required ADEF forms and provides guidelines for data entry.
Table 8-2. HUB ADEF Data Entry

Form
HUB
Page
Main
Guidelines
Enter the following data:
Identification (optional notes)
Region ID- region where HUB is
a member
IP address- IP address of HUB
Host Name- Host name of HUB
associated with IP address by
network DNS server. Enter
either the IP or Host Name, not
both.
Gateway Address- IP of
gateway in network serving HUB
Time Zone- From a drop down
menu select the time zone
appropriate for the HUB's
location
Computer password- Enter
"cadm"
8-6

Table 8-2. HUB ADEF Data Entry

Form
HUB
Page
MTG
MDF
WIRECENTER
MDF TRUNK
NTT
NXXEXK
CABLE
CALL BACK
PREFIX
OVERRIDE
HUB SLOT
EQUIPAGE
Guidelines
Complete the HUB SLOT EQUIPAGE
page first.
Collect data to identify how the HUB
NTT and MDF trunks will be arranged
into trunk groups and how those trunk
groups will be associated with the
NPANNXs the HUB is responsible for
testing.
The Create HUB from LTS and Copy
RMU pages facilitate the conversion
from LTS to HUB by copying the LTS
ADEF test data to the HUB and other
related forms.
COPY HUB FROM For MDF TAP Matrix testing, check the
TMU box on the MTG form. On the
LTS
MDF TRUNK page, use 19, 21, or 23
COPY RMU DATA
as trunk IDs.
USER PAGE
SHARED
CALLBACK
HUB
NTG
HUB
Shared Callback
SWITCH
All pages
REGION
Main
REGION
HUB Admin
The Shared Callback page on Hub is

only for notational purposes so that the
user can identify the specific TNs used
for callbacks on the HUB. It is not
required data and has no impact on any
test function.
The fields on this page pertain to the

HUB alarm server, time server, and
TCP ports LoopCare uses to
communicate to the HUB.
After completing ADEF data entry,
8-8

Submit ADEF forms.
Activate database from the MLT UIP.
Build new Hub tests from the MLT UIP.
Build any new region from the MLT UIP where the HUB has been entered
as a new test head.
Stop and start MGRP if any new test heads or regions added in ADEF.
Download configuration data to HUBs via the SAM DLOAD command.

Digitest

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Digitest

Uploaded by

Copyright:

Available Formats

Consumer Access Solutions

LoopCare Test OSS

Guide to Tollgrade Testheads

ELECTRONIC EMISSION NOTICE

2006, Tollgrade Communications, Inc., All Rights Reserved

Tollgrade Communications, Inc.

Revision Q (p/n 040-0376)

Release 2.15, December, 2006 ii

Guide to Tollgrade Testheads

About this Guide

Organization of This Guide

Digital Measurement Unit

Digital Measurement Unit Plus (DMU+)

Digital Wideband Unit

Wideband Transmission Module (WTM)

Modem Option Card

Ethernet DMU (E-DMU) Option Card

Revision Q (p/n 040-0376)

Digital Measurement Node (DMN)

Digital Wideband Node (DWN)

DigiTest Ethernet DMU (E-DMU)

The Expert Measurement Unit (EMU)

LoopCare Communications Gateway

DMU - CO and RT Applications

DMU Testing Capabilities

Deployment of the DWN

E-DMU - CO and RT Applications

Issue 2.15, December, 2006 -iii

Guide to Tollgrade Testheads

Installation of EMU as CO Test Head

EMU as CO Test Head

Physical Installation of a DMU/DMU+ Test Head

DMU Internal Configuration

DMU+ Internal Configuration

Resetting the DMU/DMU+ after Entering Data

LoopCare Database Configuration

Installation of EMU as Central Office (CO) Wideband Test Head

Physical DMU-W Test Head Installation

DMU-W Internal Configuration

Communication Port Configuration

Resetting the DMU after Entering Data

LoopCare Database Configuration (ADEF)

Installation of a DMU as an RT Test Head

DMU as an RT Test Head

Physical DMU Test Head Installation at an RT

DMU Internal Configuration

Resetting the DMU after Entering Data

Configuring the DMU+

Configuring the DMU+ to Work with LoopCare

LoopCare DMU+ Database Configuration?

Identifying the RMU

Using an RMU to Test EAIU-supported Lines

Installation of a Standalone Remote Test Head

Standalone Remote Test Head

Physical DMU/DMU-W Installation at an LTE

DMU-R Internal Configuration

Resetting the DMU after Entering Data

LoopCare DataBase Configuration

Associating a Standalone Remote Test Head with an LTE(s)

Issue 2.15, December, 2006

Revision Q (p/n 040-0376)

Guide to Tollgrade Testheads

Installation of the DWN