Lucent Technologies DACS II Specification sheet

Copyright © 2000 Lucent Technologies
All Rights Reserved
Printed in U.S.A.
365-353-255
Issue 2.0
April 2000
DACS II
Release 8.2.6, MML
Feature Guide

Copyright 2000 Lucent Technologies
All Rights Reserved
Printed in U.S.A
This material is protected by the copyright and trade secret laws of the United States and other countries. It
may not be reproduced, distributed or altered in any fashion by any entity (either internal or external to Lucent
Technologies), except in accordance with applicable agreements, contracts, or licensing, without the express
written consent of the Customer Training and Information Products organization and the business
management owner of the material.
Notice
Every effort was made to ensure that the information in this document was complete and accurate at the time
of printing. However, information is subject to change.
Mandatory Information
Security Statement
In rare instances, unauthorized individuals make connections to the telecommunications network through
the use of remote access features. In such event, applicable tariffs require that the customer pay all network
charges for traffic. Lucent Technologies cannot be responsible for such charges, and will not make any
allowance or give any credit for charges that result from unauthorized access.
Trademarks
5ESS and SLC®is a registered trademark of Lucent Technologies.
COMMON LANGUAGE is a registered trademark and CLEI, CLLI, CLCI, and CLFI are trademarks of Bell
Communications Research, Inc.
American Express is a registered trademark of American Express Company.
MasterCard is a registered trademark of mastercard International Inc.
Visa is a registered trademark of VISA International Service Association.
Documentation Ordering Information
The ordering number for this document is 365-353-255. To order this document, call the Lucent Technologies
Customer Information Center in Indianapolis, Indiana, on 1-888-582-3688. For more ordering information,
refer to “How to Order Documentation” in the section “About this Document.”
Customer Assistance and Technical Support
Lucent Technologies provides technical assistance 24 hours a day, seven days a week. For technical
assistance within the United States, call 1-800-225-RTAC. For technical assistance in Europe, call the
Netherlands Technical Support Organization (TSO) at 31-3587-1555. For technical assistance in the Far
East, call the Singapore TSO at 65-241-0880. If your country of origin provides local technical support,
please contact them directly.
Documentation Support Telephone Number
Lucent Technologies provides a telephone number for you to report errors or to ask questions about
the information in this document (i.e., for permission to reproduce or distribute). The support telephone
numbers are:
Outside the United States - 1-317-322-6847
Inside the United States - 1-800-645-6759
Acknowledgements
This document was developed by the Lucent Technologies Customer Training and Information Products
Organization.

How Are We Doing?
Title:
Identification No.: Issue No.: Date:
Lucent Technologies welcomes your feedback on this Customer Information Product (CIP). Your
comments can be of great value in helping us improve our CIPs.
1. Please rate the effectiveness of this CIP in the following areas:
2. Please check the ways you feel we could improve this CIP.
❒Improve the overview/introduction ❒Make it more concise/brief
❒Improve the table of contents ❒Add more step-by-step procedures/tutorials
❒Improve the organization ❒Add more troubleshooting information
❒Include more figures ❒Make it less technical
❒Add more examples ❒Add more/better quick reference aids
❒Add more detail ❒Improve the index
Please provide details for the suggested improvement.
3. What did you like most about this CIP?
4. Feel free to write any comments below or on an attached sheet.
If we may contact you concerning your comments, please complete the following:
Name: Telephone Number:
Company/Organization: Date:
Address:
When you have completed this form, please fold, tape and return to address on back
or Fax to: 732 949 5000.
Excellent Good Fair Poor Not Applicable
Ease of Use //////////////////
Clarity //////////////////
Completeness //////////////////
Accuracy //////////////////
Organization //////////////////
Appearance //////////////////
Examples
Illustrations
Overall Satisifaction //////////////////
DACS II Release 8.2.6, MML, Feature Guide
365-353-255 Issue 2.0 April 2000

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES
BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO. 1999 GREENSBORO, NC
POSTAGE WILL BE PAID BY ADDRESSEE
-
----------------------------------------------------------- Do Not Cut — Fold Here And Tape ---------------------------------------------------------------------
DOCUMENTATION SERVICES
2400 Reynolda Road
Winston-Salem, NC 27199-2029

Contents
Issue 2.0 April 2000 v
365-353-255
DACS II Operation and Maintenance Manual
1 Release 8.2.6 Features 1-1
■Background 1-3
■Remote Loopback Feature 1-4
■GT 1.1: Activating a Remote Loopback Test 1-6
■GT 1.2: Deactivating a Remote Loopback Test 1-7
■RAI Alarm Suppression Feature 1-8
■GT 1.3: Changing the Delay for DS3 Alarm Messages 1-9
■GT 1.4: Querying the Delay for DS3 Alarm Messages 1-10
2 Release 8.2.6 Commands and Messages 2-1
GL Glossary GL-1
IN Index IN-1

Contents
vi Issue 2.0 Issue 2.0April 2000
365-353-255
DACS II Operation and Maintenance Manual

Issue 2.0 April 2000 1-1
1
Release 8.2.6 Features 1
Contents
■Background 1-3
Introduction 1-3
Objectives 1-3
Related tasks 1-3
Related information 1-3
■Remote Loopback Feature 1-4
Overview 1-4
Remote Loopback Operation 1-4
Remote Loopback Process 1-5
■GT 1.1: Activating a Remote Loopback Test 1-6
When to use 1-6
Before you begin 1-6
Related Tasks 1-6
Task 1-6
(Continued on next page)

1-2 Issue 2.0 April 2000
365-353-255
DACS II Operation and Maintenance Manual
Release 8.2.6 Features
Contents
■GT 1.2: Deactivating a Remote Loopback Test 1-7
When to use 1-7
Before you begin 1-7
Related Tasks 1-7
Task 1-7
■RAI Alarm Suppression Feature 1-8
Overview 1-8
Alarm Suppression Operation 1-8
■GT 1.3: Changing the Delay for DS3 Alarm Messages 1-9
When to use 1-9
Related Tasks 1-9
Task 1-9
■GT 1.4: Querying the Delay for DS3 Alarm Messages 1-10
When to use 1-10
Related Tasks 1-10
Task 1-10

Issue 2.0 April 2000 1-3
365-353-255
DACS II Operation and Maintenance Manual
Release 8.2.6 Features
Background
Introduction This chapter describes the DACS II features incorporated into Release 8.2.6. The
two features included in this release are:
■Remote Loopback - the looping of individual DS1/E1 tributaries embedded
in an HDS3 signal for path maintenance and troubleshooting.
■RAI Alarm Suppression - the suppression of RAI alarm messages
generated by the individual DS1/E1 tributaries embedded in an HDS3
signal in response to a DS3 “yellow alarm” (RAI).
Objectives This chapter provides information to perform the following:
1. Understand the Remote Loopback process
2. Perform the Remote Loopback test
3. Understand RAI Alarm Suppression operation
4. Change the DS3 alarm reporting delay
5. Retrieve a report listing the DS3 alarm reporting delay.
Related tasks For related tasks, refer to the following tasks in this chapter:
■Activating a Remote Loopback Test GT 1.1
■Deactivating a Remote Loopback Test GT 1.2
■Changing the Delay for DS3 Alarm Messages GT 1.3
■Querying the Delay for DS3 Alarm Messages GT 1.4
Related
information For related information, refer to the:
■ DACS II Operation and Maintenance Manual Release 8.2.3
■ DACS II Command and Message Manual Release 8.2.3
■ DACS II Software Release Description Release 8.2.6.

1-4 Issue 2.0 April 2000
365-353-255
DACS II Operation and Maintenance Manual
Release 8.2.6 Features
Remote Loopback Feature
Overview The Remote Loopback feature provides a way to loopback the signals for
individual DS1/E1 tributaries in a hybrid DS3 signal. This functionality can
be used to verify the operation of each section (multiplexers and facility) of
a data path.
The HMXR circuit pack, located in the HDS3 unit, can perform both the local and
remote multiplexer functions regardless of its position in the network. It is capable
of sending a remote Loopback signal to a remote multiplexer, and it can loopback
a specified DS1/E1 signal to a remote loopback request from a remote multiplexer.
Remote Loopback
Operation The activation of a loopback signal at the local multiplexer (the DACS II KCR8
HMXR circuit pack) will cause a DS1/EI facility to loopback at the remote
multiplexer (far end equipment). A test signal is applied to the local multiplexer.
This test signal is compared to the signal sent to the local multiplexer by the
remote multiplexer. If differences are detected between the two signals, then the
cause of the fault lies with either the remote multiplexer, the local multiplexer, or
the facility between them. If no differences are detected, then both multiplexers
and the facility between them are operating normally.

Issue 2.0 April 2000 1-5
365-353-255
DACS II Operation and Maintenance Manual
Release 8.2.6 Features
Remote Loopback Feature (Continued)
Remote Loopback
Process The following process, illustrated in Figure 1-1, is used to set up the Remote
Loopback test:
1. The local multiplexer activates the Remote Loopback signal.
2. The remote multiplexer detects the loopback signal.
3. The remote multiplexer activates the loopback.
4. A test signal is sent through the local multiplexer and over the specified
DS1/E1 tributary. This signal will be sent back towards the local multiplexer.
5. The looped back test signal is received by the local multiplexer and a
comparison is made between the sent and received signals to determine
the condition of each multiplexer and facility between them.
Figure 1-1. Remote Loopback Process
MUX
DEMUX
MUX
DEMUX
Downstream
U
p
stream
DS3 Facilit
y
E-1 or DS1
DSX
1 Activate Loo
p
back Si
g
nal
2 Detect Loo
p
back Si
g
nal
3 Activate Loo
p
back
4 Send Test Si
g
nal
MUX = Multi
p
lexer
DEMUX = Demulti
p
lexer
KCR8 HMXR Remote Multi
p
lexer
DSX = DS1 or E-1 tributar
y
of H
y
brid DS3 si
g
nal
5 Receive Test Si
g
nal
//
IFTU
NPC
Local Multi
p
lexer (DACS II)
.
.
E-1
or
DS1
.
DSX
//
.
AIS

1-6 Issue 2.0 April 2000
365-353-255
DACS II Operation and Maintenance Manual
Release 8.2.6 Features
GT 1.1: Activating a Remote Loopback
Test
When to use Use this task to activate a remote loopback test for DS1/E1 tributaries within a
Hybrid DS3 signal. A test signal is sent from the local multiplexer to the remote
multiplexer, and looped back to the local multiplexer to check the multiplexers
at both ends and the facility between them.
Before you begin The DS1/E1 NPC under test should be grown and restored.
Related Tasks For related tasks, refer to GT 1.2: Deactivating a Remote Loopback Test.
Task To activate a remote loopback, enter the following command:
OPR-LPBK-{T1|E1}::npcNo.::loop:locn;
Where:
Stop! End of Task.
OPR-LPBK-{T1|E1} Operate loopback for a:
T1 1.544 Mb/s signal
E1 2.048 Mb/s signal
loop Loopback type:
loop Explanation
LINE
Line
npcNo. NPC number
locn Loopback location:
locn Explanation
FEND
Far-end

Issue 2.0 April 2000 1-7
365-353-255
DACS II Operation and Maintenance Manual
Release 8.2.6 Features
GT 1.2: Deactivating a Remote
Loopback Test
When to use Use this task to deactivate a remote loopback test.
Before you begin You must have an existing remote loopback test in progress.
Related Tasks For related tasks, refer to GT 1.1: Activating a Remote Loopback Test.
Task To deactivate a remote loopback, enter the following command:
RLS-LPBK-{T1|E1}::npcNo.::loop:locn;
Where:
Stop! End of Task.
RLS-LPBK-{T1|E1} Release loopback for a:
T1 1.544 Mb/s signal
E1 2.048 Mb/s signal
loop Loopback type:
loop Explanation
LINE
Line
npcNo. NPC number
locn Loopback location:
locn Explanation
FEND
Far-end

1-8 Issue 2.0 April 2000
365-353-255
DACS II Operation and Maintenance Manual
Release 8.2.6 Features
RAI Alarm Suppression Feature
Overview The Remote Alarm Indicator (RAI) Alarm Suppression feature provides a way of
suppressing the individual DS1/E1 tributary alarms when a DS3 “Yellow Alarm” is
detected by the DS3 HMXR card. These individual alarm messages add no new
information and quite frequently overload the system with redundant messages.
A DS3 failure message is typically sufficient.
With this added functionality, the HMXR suppresses individual DS1/E1 alarm
messa
g
es when an
y
of the followin
g
DS3 failures are detected:
■Loss of Signal (LOS)
■Loss of Frame (LOF)
■Excessive Bit Error Rate (BER)
■Alarm Indication Signal (AIS or IDLE)
■RAI.
Alarm
Suppression
Operation
When a DS3 failure is detected, the HDS3U will issue the alarm message and an
subsequent idle message for the DS3 itself. DS1/E1 messages (PBA, CGA, and
performance monitoring threshold messages) created as a result of the DS3
failure are always suppressed.
DS1/E1 messages will be issued if a DS1/E1 remains in alarm after the DS3 is
idled and was not in alarm previous to the DS3 going in alarm. In this case, the
DS1/E1 failure most likely is a result of something other than the DS3.

Issue 2.0 April 2000 1-9
365-353-255
DACS II Operation and Maintenance Manual
Release 8.2.6 Features
GT 1.3: Changing the Delay for DS3
Alarm Messages
When to use Use this task to change the delay (alarm activate integration) time for issuing
DS3 alarms. This delay is the duration between the onset of the DS3 failure and
the time when the alarm is displayed.
This command can be completed even if the HDS3U is unequipped or
Out-of-Service.
NOTE:
This command can only be performed by the Frame Administrator or by a
user with Frame Administration privileges.
NOTE:
This command sets the DS3 alarm delay for the entire frame.
Related Tasks For related tasks, refer to:
■GT 1.4: Querying the Delay for DS3 Alarm Messages
Task To change the delay time of DS3 alarm message reporting, enter the following
command:
ED-PRMTR-T3::::DS3ALMDLY:[x]x;
Where:
Stop! End of Task.
ED-PRMTR-T3 Change
DS3ALMDLY Delay time for DS3 alarm message output
[x]x Delay time; any whole number between 2 and 10
seconds. Default: 10 seconds

1-10 Issue 2.0 April 2000
365-353-255
DACS II Operation and Maintenance Manual
Release 8.2.6 Features
GT 1.4: Querying the Delay for DS3
Alarm Messages
When to use Use this task to request the DS3 alarm delay time.
Related Tasks For related tasks, refer to:
■GT 1.3: Changing the Delay for DS3 Alarm Messages.
Task To query the DS3 alarm delay time, enter the following command:
RTRV-ALM-T3::::DS3ALM;
Where:
Stop! End of Task.
RTRV-ALM-T3 Retrieve alarm information
DS3ALM DS3 alarm delay time

Issue 2.0 April 2000 2-1
2
Release 8.2.6 Commandsand
Messages 2
Contents
■OPR,LPBK,T1,E1,LOCN 2-3
■RLS,LPBK,NPC,LOCN 2-13
■RTRV,STATE,EQPT,NPC,LPBK 2-17

2-2 Issue 2.0 April 2000
365-353-255
DACS II Operation and Maintenance Manual
Release 8.2.6 Commands and Messages

DACS II/Rel 8.2.6 April 2000 2-3
DACS II/Rel 8.2.6
MML
OPR,LPBK,T1,E1,LOCN
26141
FACILITY LOOPBACK ACTIVATE
MML
26141
OPR,LPBK,T1,E1,LOCN
Explanation of
Command For DA and TA type NPCs
ANSI (American National Standards Institute) T1.403 is a DS1
interfacespecification, which among other things, specifies the use of the4kb/s
ESF data link for network maintenance. The data link is usedto communicate
between network elements which transport the DS1 facility.
This command is used to initiate near-end (at the DACS II) and far-end (at the
terminal on the other end of the DS1 facility) loopbacks for ESF formatted facilities
as defined by ANSI T1.403.
DACS II will execute a near-end payload loopback by transmitting the received
information bits of each frame back onto the DS1 facility. The framing bit position
is regenerated by DACS II during a payload loopback.
DACS II will also send payload and line loopback commands on the ESF data link
to far-end equipment, ordering the equipment on the other end of the DS1 facility
to execute the respective loopbacks.
For TE and TH type NPCs on HDS3Us
This command can be used to request DS1 or E1 line loopbacks toward the
facility (toward a remote multiplexer) (LOCN NEND), as well as remote line
loopbacks (from a remote multiplexer) toward the HMXR (LOCN FEND) for
all TE and TH type NPCs provisioned on HMXRs (KCR8s) within a Hybrid DS3U.
LOCN FEND loopbacks will only work if the far end multiplexer is equipped for
Remote Loopbak functionality, and additionally, is provisioned to allow Remote
Loopback requests.
Note that the command for LOCN FEND loopback will complete whether or not
the far-end equipment is capable of or permits Remote Loopback requests.
This set of loopbacks (for TE and TH types) employs the "C bits" (stuff bits") within
the M12 frame of the DS3 signal, unlike the DA and TA type loopbacks which use
the ESF datalink to send the Loop Up and Loop Down requests.

2-4 DACS II/Rel 8.2.6 April 2000
DACS II/Rel 8.2.6
MML
OPR,LPBK,T1,E1,LOCN
26141
Line loopbacks for TE type NPCs provisioned on MXR/EMXR circuit packs
(KCR1s/KCR5s), even though provisioned within a Hybrid DS3U, are not
supported.
An E1 or DS1 line loopback on an HDS3U will be activated without regard to
whether a DS3 loopback is already active. If a DS3 line loopback is active (see
command I.26161), the DS1 or E1 line loopback will have no effect until the DS3
line loopback is removed.
If a DS3 equipment loopback is active, the DS1 or E1 (LOCN NEND) line
loopback will be operating, but it results in a circular transmission path for the DS1
or E1, which is most likely undesirable.
If a loopback is active another loopback request to the same NPC will be denied.
Local and far-end loopbacks are dropped during a system reset or a system
reboot.
Command Nonhierarchical
[I.26141]
OPR-LPBK-T1:[<xy>]:[s]abc:[ww]:loop[t]:locn;
The following applies to E1 circuits multiplexed within a Hybrid DS3
only:
[I.26141]
OPR-LPBK-E1:[<xy>]:[s]abc:[ww]:loop[t]:locn;
Hierarchical
[I.26141]
OPR-LPBK-T1:[<xy>]:uv-m-np:[ww]:loop[t]:locn;
The following applies to E1 circuits multiplexed within a Hybrid DS3
only:
[I.26141]
OPR-LPBK-E1:[<xy>]:uv-m-np:[ww]:loop[t]:locn;