support.dasanzhone.comsupport.dasanzhone.com/support/manuals/docs/68/6800-A2...August 1994 COMSPHERE 6800 Series Network Management System Multiplexer Command Reference Manual Document

You have accessed an older version of aParadyne product document.

Paradyne is no longer a subsidiary ofAT&T. Any reference to AT&T Paradyne isamended to read Paradyne Corporation.

August 1994

COMSPHERE6800 Series

Network Management SystemMultiplexer Command Reference Manual

Document No. 6800-A2-GB32-10

NOTE

This document supports Release 4.2 or greater of 6800 Series NMS.

Paradyne

Printed on recycled paper

Getting Started

To browse the COMSPHERE 6800 Series Network Management System Multoplexer Command Reference Manual: 1. Move the cursor over the bookmark (topics listed to the left of the screen) or a linked area (Chapter/Section titles highlighted in red). The cursor changes into the pointing finger icon. 2. Click to jump to the linked page. The Acrobat Reader program provides a number of the ways to browse a document. For more information, click Help on the Menu bar.

COMSPHERE 6800 Series Network Management System

A August 1994 6800-A2-GB32-10

COMSPHERE6800 Series Network Management SystemMultiplexer Command Reference Manual6800-A2-GB32-10

2nd Edition (August 1994)

Changes and enhancements to the product and to the information herein will be documented and issued as a new release ora Technical Update Memo (TUM) to this manual.

A Reader’s Comments form is provided at the front of this publication and your comments are appreciated. If the form hasbeen removed, address comments to AT&T Paradyne Corporation, Technical Publications, 8545 126th Avenue North, P.O.Box 2826, Largo, Florida, 34649-2826. AT&T Paradyne may use or distribute any of the information supplied, asappropriate, without incurring any obligation whatsoever.

ANALYSIS is a trademark of AT&T.COMSPHERE is a registered trademark of AT&T.DATAPHONE is a registered trademark of AT&T.INFORMIX is a registered trademark of Informix Software, Inc.

COPYRIGHT � 1994 AT&T Paradyne Corporation. All rights reserved.This publication is protected by federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system,or translated into any human or computer language in any form or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third partieswithout the express written permission of AT&T Paradyne Corporation, 8545 126th Avenue North, P.O. Box 2826, Largo, Florida 34649-2826.

AT&T Paradyne Corporation makes no representation or warranties with respect to the contents hereof and specifically disclaims any implied warranties ofmerchantability or fitness for a particular purpose. Further, AT&T Paradyne Corporation reserves the right to revise this publication and to make changes fromtime to time in the contents hereof without obligation of AT&T Paradyne Corporation to notify any person of such revision or changes.

Safety Instructions

B6800-A2-GB32-10 August 1994

Important Safety Instructions

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

2. This product is intended to be used with a three-wire grounding type plug - a plugwhich has a grounding pin. This is a safety feature. Equipment grounding is vital toensure safe operation. Do not defeat the purpose of the grounding type plug bymodifying the plug or using an adaptor.

Prior to installation, use an outlet tester or a voltmeter to check the ac receptacle forthe presence of earth ground. If the receptacle is not properly grounded, theinstallation must not continue until a qualified electrician has corrected the problem.

If a three-wire grounding type power source is not available, consult a qualifiedelectrician to determine another method of grounding the equipment.

3. Slots and openings in the cabinet are provided for ventilation. To ensure reliableoperation of the product and to protect it from overheating, these slots and openingsmust not be blocked or covered.

4. Do not allow anything to rest on the power cord and do not locate the product wherepersons will walk on the power cord.

5. Do not attempt to service this product yourself, as opening or removing covers mayexpose you to dangerous high voltage points or other risks. Refer all servicing toqualified service personnel.

6. General purpose cables are provided with this product. Special cables, which may berequired by the regulatory inspection authority for the installation site, are theresponsibility of the customer.

7. When installed in the final configuration, the product must comply with the applicableSafety Standards and regulatory requirements of the country in which it is installed. Ifnecessary, consult with the appropriate regulatory agencies and inspectionauthorities to ensure compliance.

8. A rare phenomenon can create a voltage potential between the earth grounds of twoor more buildings. If products installed in separate buildings are interconnected , thevoltage potential may cause a hazardous condition. Consult a qualified electricalconsultant to determine whether or not this phenomenon exists and, if necessary,implement corrective action prior to interconnecting the products.

In addition, if the equipment is to be used with telecommunications circuits, take thefollowing precautions:

– Never install telephone wiring during a lightning storm.– Never install telephone jacks in wet locations unless the jack is specifically designed

for wet locations.– Never touch uninsulated telephone wires or terminals unless the telephone line has

been disconnected at the network interface.– Use caution when installing or modifying telephone lines.– Avoid using a telephone (other than a cordless type) during an electrical storm.

There may be a remote risk of electric shock from lightning.– Do not use the telephone to report a gas leak in the vicinity of the leak.


C August 1994 6800-A2-GB32-10

Notices

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

� �� "�� "�� "� � �� "� �� "��

�� "�� !��

�� "� �� "��" �� !� � � ��

i6800-A2-GB32-10 August 1994

Table of Contents

Preface

Objectives and Reader Assumptions v. . . . . . . . . . . . . . . . . . . . . . . . . Related Documents v. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1. Introduction

Overview 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Format for Documenting Commands in This Manual 1-5. . . . . . . . . . . . Command Input Forms 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2. Multiplexer Commands

Overview 2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acquire Channel Groups (accg) 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acquire Logical Links (acll) 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acquire Physical Attributes (acpa) 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . Backup Node Database (bkupnd) 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . Bit Error Rate Test (bert) 2-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Break Channel Connection (brcc) 2-20. . . . . . . . . . . . . . . . . . . . . . . . . . . Break Channel Group Connection (brcgc) 2-22. . . . . . . . . . . . . . . . . . . . Break Logical Link Connection (brllc) 2-24. . . . . . . . . . . . . . . . . . . . . . . Change Channel Configuration (chcc) 2-27. . . . . . . . . . . . . . . . . . . . . . . . Change Channel Group (chcg) 2-46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Channel Module Type (chcmt) 2-54. . . . . . . . . . . . . . . . . . . . . . . Change DS-1 Channel Module Configuration (chdcmc) 2-57. . . . . . . . . . Change Logical Link (chll) 2-59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Multiplexer Component Configuration (chmcc) 2-63. . . . . . . . . Change Network Administration Port Configuration (chnapc) 2-67. . . . . Change Node Configuration Parameters (chncp) 2-70. . . . . . . . . . . . . . . Change Node Connected To System (chncs) 2-82. . . . . . . . . . . . . . . . . . . Change Node Passwords (chnp) 2-84. . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Physical Link Configuration (chplc) 2-85. . . . . . . . . . . . . . . . . . Change Routing Table (chrt) 2-96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Supervisory Data Link Configuration (chsdlc) 2-101. . . . . . . . . . . Channel Group Loopback (cgl) 2-110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Group Performance Report (cgpr) 2-112. . . . . . . . . . . . . . . . . . . . Channel Group Summary (cgs) 2-115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Group Trace (cgt) 2-120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Loopback (cl) 2-123. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Network Loopback (cnl) 2-126. . . . . . . . . . . . . . . . . . . . . . . . . . . Channel State Summary (css) 2-129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


ii August 1994 6800-A2-GB32-10

Channel Summary (cs) 2-133. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel System Test (cst) 2-136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compare Control Processors (ccp) 2-138. . . . . . . . . . . . . . . . . . . . . . . . . . Control Processor Test (cpt) 2-139. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Channel Group (crcg) 2-140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Logical Link (crll) 2-151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DDS Channel Performance And Status (ddscps) 2-155. . . . . . . . . . . . . . . . DDS Channel Trouble Codes (ddsctc) 2-158. . . . . . . . . . . . . . . . . . . . . . . . DDS Signaling Test (ddsst) 2-161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete Channel Group (dlcg) 2-163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete Logical Link (dlll) 2-165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Channel Configuration (dscc) 2-168. . . . . . . . . . . . . . . . . . . . . . . . Display Channel Group (dscg) 2-179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Control Signals (dscs) 2-185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display DS0B Base Channels (dsdbc) 2-189. . . . . . . . . . . . . . . . . . . . . . . . Display DS-1 Channel Module Configuration (dsdcmc) 2-192. . . . . . . . . . Display Logical Link (dsll) 2-194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Multiplexer Component Configuration (dsmcc) 2-197. . . . . . . . . Display Network Administration Port Configuration (dsnapc) 2-201. . . . . Display Node Configuration Parameters (dsncp) 2-204. . . . . . . . . . . . . . . Display Node Connected to System (dsncs) 2-213. . . . . . . . . . . . . . . . . . . Display Physical Link Configuration (dsplc) 2-215. . . . . . . . . . . . . . . . . . Display Routing Table (dsrt) 2-221. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Supervisory Data Link Configuration (dssdlc) 2-223. . . . . . . . . . . Display T1 Interface Status (dstis) 2-228. . . . . . . . . . . . . . . . . . . . . . . . . . . DS0B Channel Summary (dcs) 2-231. . . . . . . . . . . . . . . . . . . . . . . . . . . . . DS0B Performance and Status (dps) 2-234. . . . . . . . . . . . . . . . . . . . . . . . . DS-1 Channel Loopback (dcl) 2-236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DS-1 Channel Module Test (dcmt) 2-238. . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Performance Report (epr) 2-240. . . . . . . . . . . . . . . . . . . . . . . . Facility Errors Report (fer) 2-243. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Facility Performance Report (fpr) 2-246. . . . . . . . . . . . . . . . . . . . . . . . . . . Generate Routing Tables (grt) 2-253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Module Summary (hms) 2-255. . . . . . . . . . . . . . . . . . . . . . . . . . Internal Test (it) 2-259. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Link Summary (lls) 2-261. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Make Channel Connection (mkcc) 2-264. . . . . . . . . . . . . . . . . . . . . . . . . . Make Channel Group Connection (mkcgc) 2-266. . . . . . . . . . . . . . . . . . . . Make Logical Link Connection (mkllc) 2-268. . . . . . . . . . . . . . . . . . . . . . NAP and SDL State Summary (nsss) 2-270. . . . . . . . . . . . . . . . . . . . . . . . Network Paths Summary (nps) 2-273. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Wide Channel Group Summary (nwcgs) 2-277. . . . . . . . . . . . . . Node Errors Report (ner) 2-279. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node State Summary (nss) 2-281. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Link Loopback (pll) 2-286. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Link Module Test (plmt) 2-289. . . . . . . . . . . . . . . . . . . . . . . . . . . Power and Alarm Control Test (pact) 2-291. . . . . . . . . . . . . . . . . . . . . . . . Remote Physical Link Loopback (rpll) 2-292. . . . . . . . . . . . . . . . . . . . . . . Report Diagnostic Status (rds) 2-294. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset Control Processor (rcp) 2-297. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Node Database (rstrnd) 2-298. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Slot Performance Report (tspr) 2-301. . . . . . . . . . . . . . . . . . . . . . . . . Time Slot Summary (tss) 2-304. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSI Module Test (tsimt) 2-308. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice Channel Tone Test (vctt) 2-309. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

iii6800-A2-GB32-10 August 1994

List of Figures

Figure Page

1-1 6800 Series NMS Tasks Menu 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Example of an Input Form 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Example of a Results Form 1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Selecting Fields Listed in Tabular Form 1-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Bit Error Rate Test Input Form (DDS Channels), Page 2 2-16. . . . . . . . . . . . . . . . . . . . 2-2 Change Channel Configuration Time-of-Day Input Form, Page 4 2-31. . . . . . . . . . . . . 2-3 Change Channel Module Type Input Form, Page 2 2-55. . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Change Physical Link Configuration Input Form for 74x Nodes, Page 2 2-86. . . . . . . . 2-5 Change Physical Link Configuration Input Form for a 74x Node, Page 3 2-89. . . . . . . 2-6 Change Physical Link Configuration Input Form for a 74x Node, Page 4 2-91. . . . . . . 2-7 Change Routing Table Input Form, Page 2 2-99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Change SDL Configuration Input Form for a 731, 740, 741, 742 Node, Page 22-102. . 2-9 Change SDL Configuration Input Form for a 745 Node, Page 2 2-104. . . . . . . . . . . . . . 2-10 Change SDL Configuration (Embedded SDL) Form, Page 5 2-105. . . . . . . . . . . . . . . . . 2-11 Change SDL Configuration (Synchronous SDL) Input Form, Page 5 2-107. . . . . . . . . . 2-12 Change SDL Configuration (Synchronous SDL) Input Form, Page 6 2-108. . . . . . . . . . 2-13 Channel Group Performance Report Results Form 2-113. . . . . . . . . . . . . . . . . . . . . . . . . 2-14 Channel Group Summary Results Form, Page 1 2-117. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 Channel Group Trace Results Form, Page 1 2-121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 Channel Network Loopback Results Form 2-128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 Channel State Summary Results Form (731, 740, 741, 742, 74x-56K) 2-130. . . . . . . . . 2-18 Channel Summary Results Form, Page 1 2-134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 Create Channel Group Input Form (non-56K), Page 2 2-142. . . . . . . . . . . . . . . . . . . . . . 2-20 Create Channel Group Input Form, Page 3 2-145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21 Create Channel Group Input Form (Channel Connection Reconfiguration Times),

Page 3 2-146. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 Create Channel Group Input Form (Attribute Requests), Page 4 2-147. . . . . . . . . . . . . . 2-23 Create Channel Group Input Form (Fixed Route Selection), Page 5 2-148. . . . . . . . . . . 2-24 Create Channel Group Input Form (Pass-Through), Page 6 2-149. . . . . . . . . . . . . . . . . . 2-25 Create Logical Link Input Form, Page 1 2-152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26 Create Logical Link Input Form, Page 2 2-154. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27 DDS Channel Performance and Status Results Form, Page 1 2-156. . . . . . . . . . . . . . . . . 2-28 DDS Channel Trouble Codes Input Results Form, Page 1 2-159. . . . . . . . . . . . . . . . . . . 2-29 Display Control Signals Results Form (Channels), Page 1 2-186. . . . . . . . . . . . . . . . . . . 2-30 Display DS0B Base Channels Results Form, Page 1 2-190. . . . . . . . . . . . . . . . . . . . . . . 2-31 Display DS-1 Channel Module Configuration Results Form, Page 1 2-193. . . . . . . . . . . 2-32 Display T1 Interface Status Results Form, Page 1 2-229. . . . . . . . . . . . . . . . . . . . . . . . . 2-33 DS0B Channel Summary Results Form, Page 1 2-232. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34 DS0B Performance and Status Results Form, Page 1 2-235. . . . . . . . . . . . . . . . . . . . . . . 2-35 Equipment Performance Report (74x-56K) Results Form, Page 1 2-242. . . . . . . . . . . . .


iv August 1994 6800-A2-GB32-10

Figure Page

2-36 Facility Errors Report Results Form, Page 1 2-244. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37 Facility Performance Report Input Form, Page 1 2-246. . . . . . . . . . . . . . . . . . . . . . . . . . 2-38 Facility Performance Report Input Form, Page 2 2-248. . . . . . . . . . . . . . . . . . . . . . . . . . 2-39 Facility Performance Report Results Form (Graphic Failed Seconds), Page 22-250. . . . 2-40 Facility Performance Report Results Form (Tabular Report) 2-251. . . . . . . . . . . . . . . . . 2-41 Hardware Module Summary Results Form, Page 1 2-256. . . . . . . . . . . . . . . . . . . . . . . . . 2-42 Logical Link Summary Results Form, Page 1 2-262. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43 NAP/SDL State Summary Results Form, Page 1 2-271. . . . . . . . . . . . . . . . . . . . . . . . . . 2-44 Network Paths Summary Input Form,Page 1 2-274. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45 Network Paths Summary Results Form, Page 2 2-275. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46 Network Paths Summary Results Form, Page 7 2-276. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47 Network Wide Channel Group Summary Results Form, Page1 2-277. . . . . . . . . . . . . . . 2-48 Node Errors Report Results Form, Page 1 2-280. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49 Node State Summary Results Form (731, 740, 741, 742, 74x-56K Nodes), Page 12-282. 2-50 Node State Summary Results Form (745 Nodes), Page 1 2-284. . . . . . . . . . . . . . . . . . . . 2-51 Report Diagnostic Status Results Form, Page 1 2-296. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52 Time Slot Performance Report Results Form, Page 1 2-302. . . . . . . . . . . . . . . . . . . . . . . 2-53 Time Slot Summary Results Form (740, 741, 742, Nodes), Page 1 2-305. . . . . . . . . . . . 2-54 Time Slot Summary Results Form (745), Page 1 2-306. . . . . . . . . . . . . . . . . . . . . . . . . . 2-55 Voice Channel Tone Test 2-310. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of Tables

Table Page

Tone Generation/Tone Measurement Direction 2-312. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

v6800-A2-GB32-10 August 1994

Preface

Objectives and Reader AssumptionsThis manual provides a description of the device commands that can be used only withDATAPHONE� II Series 700 (731/740/741/742/745) ACCULINK� multiplexers.

It is assumed that you are familiar with the operation of these devices, have read the COMSPHERE6800 Series Network Management System User’s/System Administrator‘s Guide and are familiarwith the use of the COMSPHERE 6800 Series Network Management System.

Related Documents

6800-A2-GB21 COMSPHERE 6800 Series Network Management System MultiplexerManagement and Configuration Guide

6800-A2-GB30 COMSPHERE 6800 Series Network Management System CoreCommand Reference Manual

6800-A2-GE26 COMSPHERE 6800 Series Network Management System User’s/SystemAdministrator’s Guide

999-100-231IS DATAPHONE II Series 700 STAT MUX User’s Manual

999-100-234IS DATAPHONE II Series 700 NETWORKER User’s Manual

999-100-237IS DATAPHONE II Series 700-724/735 T-MUX User’s Manual

999-100-289IS DATAPHONE II 740/741 ACCULINK Multiplexer User’s Manual

999-100-227 DATAPHONE II 745 ACCULINK Multiplexer User’s Manual

314-620-152 764 ACCULINK 56/64Kbps Multiplexer AFN User’s Manual


vi August 1994 6800-A2-GB32-10

Ordering Information

To order AT&T Paradyne documentation, please call 1-800-545-2354.

To order AT&T DATAPHONE II documents, please call the AT&T Customer Information Center(CIC) at 1-800-432-6600.

1-16800-A2-GB32-10 August 1994

Introduction

Overview 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6800 Series NMS-Supported Multiplexers 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming Conventions 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Addressing 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Access 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Shortcut for Command Access 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wildcard Characters 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Entries 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Format for Documenting Commands in this Manual 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Input Forms 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Required Fields 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional Fields 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display-only Fields 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carried-over Fields 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Fields on Input Forms – Destination for results and Schedule execution 1-8. . . . . . . . . . . Results Forms 1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Help 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In Menus 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In Forms 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For Screen Input Fields 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OverviewThis chapter provides overview information on using the 6800 Series Network ManagementSystem (NMS) and accessing the multiplexer commands. It also provides a description of thecommand format used in this manual to document each command. This chapter includesinstructions on entering abbreviated versions of options when specifying command executionparameters, and the use of wildcard characters. The common fields (Destination for results andSchedule execution) in the command input forms are defined in detail to eliminate the repetitionof this information for each command.

This manual describes the multiplexer diagnostic commands, the multiplexer configurationcommands, and the commands used to generate multiplexer performance reports. You access thesecommands under Network Control in the Manager task. The multiplexer performance reportscommands can also be accessed from the Performance Reports task. Functionally, the commandsunder the Performance Reports task operate the same as those commands of the same name underNetwork Control in the Manager task.

It is assumed that you are already familiar with the screen functions offered with both thefull-featured 6800 Series NMS workstation and the basic-featured 6800 Series NMS workstation.If you are not familiar with the screen functions provided by the workstations, refer to Chapter 2,Getting Started in the COMSPHERE 6800 Series Network Management System User’s/SystemAdministrator’s Guide for this information.

1


1-2 August 1994 6800-A2-GB32-10

6800 Series NMS-Supported Multiplexers

NMS fully supports the following multiplexer products with alert management, diagnostic testcapabilities, and configuration and control:

The 740, 741, 742 and 745 multiplexer is referred to in this document as the 74x multiplexer.

ACCULINK 731, 740, 741, 742 Multiplexer

The 740, 741, or 742 multiplexer is a time division multiplexer that can combine up to 4channels (for the 731 multiplexer), up to 128 channels (for the 740 multiplexer), up to 40channels (for the 741 multiplexer), and up to 32 channels (for the 742 multiplexer). Thetypes of channels are as follows:

• E-Voice (for 742 multiplexer)

• Voice

• Synchronous Data

• Asynchronous Data

• DS0

• DS1

• DDS

The 740, 741, or 742 is capable of multiplexing any combination of these channel types.

The ACCULINK 731 multiplexer supports 4 synchronous channels only.

These channels are multiplexed into a single digital stream for transmission over a T1 or aFractional T1 digital facility, also referred to as an aggregate link. The 740 canaccommodate an optional redundant aggregate link to serve as a backup should the activelink fail.

ACCULINK 764 Multiplexer

The 764 multiplexer is referred to in this document as a 74x-56K multiplexer.

The 764 multiplexer is a time division multiplexer which can operate at an aggregate linkspeed of 56 or 64 kbps. The standard 64K will support 32 channels. As an option the 764software can be provided in the 740 or 741 chassis. The 764 will support voice, async,and sync data. The 740-56K supports up to 128 channels and the 741-56K supports up to40 channels. The channels on the 764 multiplexer can be terminated on another 764 in apoint-to-point configuration. They also can be terminated on a 731, 740, 741, or 742 T1multiplexer when Fractional T1 services are used to provide a bandwidth connectionbetween the 56K and T1 nodes.

ACCULINK 745 Switching Multiplexer

The 745 multiplexer is an intelligent DS0 switching multiplexer that can switch up to 16 T1 links. The 745 also provides DS1 connections to Digital Access Cross-ConnectSystem (DACS) and Customer Controlled Reconfiguration (CCR) and digital PrivateBranch Exchanges (PBXs), such as the AT&T System 75/85.

Introduction

1-36800-A2-GB32-10 August 1994

NMS provides alert and cut-through support for the following multiplexer products. Tests andcommands are not supported:

DATAPHONE II Series 700 Model 719 NETWORKER

The 719 is a statistical, packet-switching multiplexer that supports up to 32 independentdata channels, 18 network links, or a combination of channels and links. The 719’smultilink capability can also be used to provide alternative supervisory data links (SDLs).

DATAPHONE II Series 700 Model 72x (721/722/723/725) NETWORKER

The 72x is a statistical, packet-switching multiplexer that supports up to 16 channels (forthe 721 multiplexer), up to 32 channels (for the 722 multiplexer), up to 2 nodes at 32channels each (for the 723 multiplexer), and up to 2 nodes at 32 channels or 1 node at 64channels (for the 725 multiplexer).

DATAPHONE II Series 700 Models 724/735 T1 Multiplexers

The 724/735 multiplexers use bit-interleaved time division multiplexing to concentrate upto 128 different channels of data, voice, or compressed video for transmission over 1.544Mbps T1 facilities. The 735 supports over 500 synchronous channel rates, from 1.2 kbpsto 768 kbps.

DATAPHONE II 735 56 kbps Multiplexers

The 735 is a time division, bit-interleaved multiplexer used for high-volume,protocol-independent transmission over 56 kbps lines. The 56 kbps link offers 80 programmable data rates (1.2 kbps to 52.8 kbps). A variety of data channel interfacesincludes RS-232C, CCITT V.35, RS-422, and MIL-STD 188-114.

Naming Conventions

NMS naming conventions enable you to assign a name to a device and to assign a network orcircuit name to a group of logically related devices, such as those devices sharing a commoncustomer, location, or application. You can then reference or test a group of devices, a network, ora circuit by entering a single name. Refer to Appendix C of the COMSPHERE 6800 SeriesNetwork Management System User’s/System Administrator’s Guide for a description of the devicenaming method accepted by NMS.

Device Addressing

Device addressing allows the 6800 Series NMS to communicate with the devices in the network.Refer to Appendix D of the COMSPHERE 6800 Series Network Management SystemUser’s/System Administrator’s Guide for a description of the device addressing methods acceptedby NMS.


1-4 August 1994 6800-A2-GB32-10

Command Access

When you log on to the 6800 Series NMS, the 6800 Series NMS Tasks menu displays (Figure 1-1).

To issue a multiplexer command, select the Manager task. Then, select Network Control . Thesub-menu displays a menu, enabling you to select diagnostic and test commands, configurationcommands, or reports commands. Diagnostic and test commands and configuration commandsalso have sub-menus which offer device-specific selections. Within these selections, you select acommand by either entering the command number or command abbreviation on the enterselection field or selecting the command item with the mouse. For more information on selectingcommands depending on basic-feature or full-feature workstations, refer to the COMSPHERE6800 Series Network Management System User’s/System Administrator’s Guide.

Multiplexer performance reports can be accessed from either the Manager task or the PerformanceReports task.

Figure 1-1. 6800 Series NMS Tasks Menu

Shortcut for Command Access

You can type any command valid for a task window in the enter selection field of any sub-menuwithin that task window and select Enter.

Introduction

1-56800-A2-GB32-10 August 1994

Wildcard Characters

In certain fields, e.g. device address fields, you can enter an asterisk (*) to specify any characterstring. For example, if you wanted to enter a device address for all multiplexer nodes on controlchannel m2, you might

TYPE: m2/*

This would indicate all nodes under control channel m2. For more information on wildcardcharacters, refer to Appendix E of the COMSPHERE 6800 Series Network Management SystemUser’s Manual/System Administrator’s Guide.

Multiple Entries

Multiple entries are permitted in some fields. You must separate each entry with either a comma ora space. These fields are identified in the manual.

Format for Documenting Commands in This ManualEach command documented in this manual begins on a new page.

The format for documenting each command is the same. The command is briefly summarized as toits function, followed by the following information.

Access Level

Identifies the user group access level requested to access the command. NMS commandsare associated with at least one of four default user groups, or access levels. These levelsare, in order of increasing command permission:

• Help Desk

• Data Technician

• Manager

• Administrator

NOTE

In addition to the four default user groups, the NMS SystemAdministrator can create up to 26 other user groups for eachcommand in this manual. It is the responsibility of the NMS SystemAdministrator to inform all the users of their system.

Users must have the appropriate functional access level set in their user profile to executea command. Any command associated with a particular user group can be executed byany user that has equal or greater command permission. Therefore, it is assumed that theSystem Administrator (Administrator level) has access to all commands. If a user does nothave permission to a command, that command is not displayed in the user’s menus. If theuser attempts to request the command on the enter selection field, that request results in amessage indicating that permission is denied. The default access levels for all commandsare listed in Appendix B in the COMSPHERE 6800 Series Network Management SystemUser’s/System Administrator’s Guide.


1-6 August 1994 6800-A2-GB32-10

Abbreviation

Identifies the command as it appears on the command sub-menus. If the commandsub-menus are bypassed by typing the command on the enter selection field, thecommand abbreviation must be entered exactly as shown.

An abbreviation is provided for each command. For some commands, an alternatecommand abbreviation from earlier 6800 Series NMS releases is also recognized byNMS. For such commands, these alternate abbreviations are also listed.

Restrictions

Identifies any limitations associated with the execution of the command, or any additionalinformation concerning command execution that you may need for successful executionof the command.

Routine

Indicates whether or not (yes/no) a command can be placed in a routine. A routine is a setof up to 25 commands that can be grouped together and executed sequentially byspecifying the routine name on the enter selection field. Refer to the COMSPHERE 6800Series Network Management System User’s/System Administrator’s Guide for informationon routines.

Schedule

Identifies whether or not (yes/no) a command can be scheduled for later or repeatedexecution. Refer to the discussion on Schedule execution under the section CommonFields on Input Forms – Destination for results and Schedule execution in this chapter foradditional information on scheduling parameters.

Related Commands

Lists other multiplexer commands that relate to the function executed by this command.

Command Input FormsEvery multiplexer command uses one or more input form pages. The appropriate input form pagesdisplay when you request a command, enabling you to enter input parameters required forexecution of the command.

On input fields where the set of valid inputs is know by the system, a pop-up menu of the validchoices will be available to the user. The pop-up menu title will correspond to the field label of thefield for which the user has invoked help.

On most of the input forms that list valid entry options for a field in a pop-up menu, you are able toabbreviate your entry of the option by typing the first or first few characters of the word touniquely identify that word to the system. For example, in the Destination for results field, thevalid entry options are crt, remote, printer, queue. You only need to enter the first letter of eachword (c, r, p, q, respectively) to uniquely identify that option word from the other listed options.Figure 1-2 is an example of an input form.

Introduction

1-76800-A2-GB32-10 August 1994

Figure 1-2. Example of an Input Form

Required Fields

Certain fields on the input form require that you input the data requested before NMS allows youto execute the command. These fields appear on the input form in a solid box.

Optional Fields

Optional fields do not require you to input data before continuing with the command, eitherbecause this data is not needed by NMS, the data is supplied by the devices via NMS, or (in thecase of sorting selection fields) this field can be ignored in the search. Optional fields appear on theinput form as underlined.

Display-only Fields

Display-only fields display data, but do not allow you to enter new data or change the datadisplayed. These fields appear on the input forms without boxes or underlines.

Carried-over Fields

Carried-over fields display information provided by the user on a previous form of the currentcommand. Carried over fields may be display-only, or in some cases, may allow user input.


1-8 August 1994 6800-A2-GB32-10

Common Fields on Input Forms – Destination for results and Schedule execution

Destination for results

Use this field to specify where NMS should send the results from the commandexecution. Valid options are crt , remote, printer , lp, and queue. Multiple destinationscan be specified.

crt

Causes the command results to display on your workstation screen. You cannotschedule execution of the command for a later time if you specify the destinationas crt ; the command must be executed immediately.

NOTE

When you specify crt , NMS does not allow any other command tobe accessed from the current window until execution of the currentcommand has completed. Certain commands, e.g., tests that takeseveral minutes to execute, or reports that include large volumes ofdata, can take several minutes to complete. In these instances it isrecommended that you send the results of the command to a queueor to a printer, in which case the command will execute in thebackground, allowing you to access and execute other commands.

remote

Sends the results of the command to a remotely located printer. If you specifyremote, a telephone number prompt displays on the screen to enable you tospecify the telephone number of the remote printer or the ATR remote printerport. If a phone number has been included in your user profile (an optional fieldin the user profile), this printer destination becomes the default number. If ahardwired remote printer port is available, the keyword port can be enteredinstead of the phone number.

lp

Sends results to a remote line printer. You are prompted for the name of theremote printer in a field that appears below the destination field.

printer

Sends the results of the command to the local system printer assigned in youruser profile.

queue

Sends the results of the command to one of your own results queues. Commandresults may go to one of three results queues, depending on the task windowfrom which the command was executed.

Introduction

1-96800-A2-GB32-10 August 1994

Schedule execution

This option enables you to direct the system to execute commands and routinesautomatically at selected times or repeatedly at regular intervals. Valid options are now,delayed, weekly, and monthly.

now

Causes the command to be executed immediately. If you enter crt in theDestination for results field, you must enter now in the Schedule executionfield.

delayed

Causes the command to be executed at a future time. When you enter delayed inthe Schedule execution field, the following additional fields are displayed:

Date(s)

The command executes on the date(s) specified in this field. You canenter as many dates as will fit in the field. Separate all dates withcommas or spaces. Valid entries are today, today+nn, last, mm/dd/yy,mm/dd, dd

Where: today = Execute today.

today + nn = Execute nn number of daysfrom today.

last = Execute on the last day of themonth.

mm/dd/yy = Execute on the specified month,day and year.

mm/dd = Execute on the specified monthand day; the year defaults to thecurrent year.

dd = Execute on the specified day;the month and year default tothe current month and year.

Time(s)

The command executes at the time specified in this field.

Valid entries are hh:mm, hh:mmam or pm, hh-hh:mm, and all:mm

Where: hh:mm = Execute at the 24-hour timespecified.

hh:mmamorhh:mm pm

= Execute at the 12-hour timespecified with an am or pmdesignation.

hh-hh:mm = Execute every hour within thetime range specified, at thespecified minute

all:mm = Execute every hour at thespecified minute.


1-10 August 1994 6800-A2-GB32-10

weekly

Causes the command to execute on a weekly basis. When you enter weekly inthe Schedule execution field, the following additional fields are displayed:

Day(s) of the week

Enter the day(s) of the week when the command is to execute. Validentries are

ƒ• The days of the week in abbreviated form, e.g., sun, mon, tue, wed, thu, fri, sat. Multiple entries are allowed separated by commas or spaces.

ƒ• A range of days separated by a dash, e.g., sun–thu.

ƒ• The keyword all for all days of the week.

Time(s)

Enter the time(s) the command is to execute for each day specified. Fortime(s) entry parameters, refer to the Time(s) field explanation fordelayed command execution.

Last date

Enter the stop date for command execution. If you leave this field blankthe command will execute indefinitely on a weekly basis. If the last dateoccurs before the first scheduled date, the user is not allowed to enterthat date.

For data format, refer to the Date(s) field explanation for delayedcommand execution. (The today value is not valid for theTrouble/Inventory Reports and Trouble Tracking tasks.)

monthly

The command executes on a monthly basis. When you enter monthly into theSchedule execution field, the following additional fields are displayed:

Day(s) of the month

Enter the day(s) of the month when this command is to execute. Validentries are

ƒ• Multiple days. The numbers must be separated by commas or spaces, e.g., 1,4,7,10.

ƒ• A range of days, e.g., 8–15.

ƒ• The word last to execute the command on the last day of the current month.

ƒ• The word all to execute the command each day of the current month.

Introduction

1-116800-A2-GB32-10 August 1994

Time(s)

Enter the time(s) the command is to execute for each day specified. Fortime(s) format, refer to the Time(s) field explanation for delayedcommand execution.

Last Date

Enter the stop date for execution of the command. If you leave this fieldblank, the command will execute on a monthly basis indefinitely. If thelast date occurs before the first scheduled date, the user is not allowed toenter that date.

For date entry parameters refer to the Date(s) field explanation fordelayed command execution. The today value is not valid for theTrouble/Inventory Reports and Trouble Tracking tasks.

Results Forms

Each multiplexer command is associated with one or more results forms. Depending on thecommand issued, the results form(s) can display a success or failure message for commandexecution, reflect the changes made as a result of the command execution, or display detailedinformation. A results form trailer message indicates start and stop times for command execution.Figure 1-3 shows an example of a results form.

Figure 1-3. Example of a Results Form


1-12 August 1994 6800-A2-GB32-10

HelpNMS provides several help features to assist you in command input and execution. Help isavailable on all screens by selecting Help(F1). This function key displays a pop-up Help screen,explaining the function keys and how to invoke the Help feature. On the 6800 Series NMS Taskmenu, it defines the Task menu screen functions: Tasks, Windows, Logoff, Refresh, and NewMail.Help features within the tasks can be accessed as follows.

In Menus

General help for a task can be obtained from within any menu by selecting the ? icon on the taskwindow title bar from the full-feature workstation. From a basic-feature workstation, type the keysequence ESC ?

In Forms

All forms (both input and output forms) have associated form help text. Form help is accessedfrom a full-feature workstation by selecting the? icon on the task window title bar. From abasic-feature workstation, type the key sequence ESC ?

Form help includes a general description of the form currently displayed. The form help text forinput forms also includes general descriptions of how to enter input, how to access field help, andthe types of field help available (selectable menu vs. field help text).

For Screen Input Fields

Within forms, field Help menus or text messages are accessed by selecting field labels with themouse from a full-feature workstation (or typing ?). From a basic-feature workstation, type a ? inthe input field. The cursor must be positioned on the field for which help is needed. For tabularfields, the column label should be selected. Refer to Figure 1-4 to clarify selecting fields listed intabular form.

Introduction

1-136800-A2-GB32-10 August 1994

Figure 1-4. Selecting Fields Listed in Tabular Form

Each field that accepts user input has associated field help. Depending on the type of field (eitherfixed parameter or variable parameter [i.e., a value within a range of values]), field help is either aselectable menu of valid field entries, or a text message which describes the valid input format(s)or entries.

2-16800-A2-GB32-10 August 1994

Multiplexer CommandsOverview 2-2��. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acquire Channel Groups (accg) 2-3 �. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acquire Logical Links (acll) 2-6 �. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acquire Physical Attributes (acpa) 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Node Database (bkupnd) 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bit Error Rate Test (bert) 2-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Break Channel Connection (brcc) 2-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Break Channel Group Connection (brcgc) 2-22. . . . . . . . . . . . . . . . . . . . . . . . . . . Break Logical Link Connection (brllc) 2-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Channel Configuration (chcc) 2-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Channel Group (chcg) 2-46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Channel Module Type (chcmt) 2-54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change DS-1 Channel Module Configuration (chdcmc) 2-57. . . . . . . . . . . . . . . . Change Logical Link (chll) 2-59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Multiplexer Component Configuration (chmcc) 2-63. . . . . . . . . . . . . . . . Change Network Administration Port Configuration (chnapc) 2-67. . . . . . . . . . . Change Node Configuration Parameters (chncp) 2-70. . . . . . . . . . . . . . . . . . . . . . Change Node Connected to System (chncs) 2-82. . . . . . . . . . . . . . . . . . . . . . . . . . Change Node Passwords (chnp) 2-84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Physical Link Configuration (chplc) 2-85. . . . . . . . . . . . . . . . . . . . . . . . . Change Routing Table (chrt) 2-96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Supervisory Data Link Configuration (chsdlc) 2-101. . . . . . . . . . . . . . . . . Channel Group Loopback (cgl) 2-110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Group Performance Report (cgpr) 2-112. . . . . . . . . . . . . . . . . . . . . . . . . . Channel Group Summary (cgs) 2-115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Group Trace (cgt) 2-120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Loopback (cl) 2-123. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Network Loopback (cnl) 2-126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel State Summary (css) 2-129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Summary (cs) 2-133. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel System Test (cst) 2-136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compare Control Processors (ccp) 2-138. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Processor Test (cpt) 2-139. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Channel Group (crcg) 2-140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Logical Link (crll) 2-151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DDS Channel Performance and Status (ddscps) 2-155. . . . . . . . . . . . . . . . . . . . . . . DDS Channel Trouble Codes (ddsctc) 2-158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DDS Signaling Test (ddsst) 2-161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete Channel Group (dlcg) 2-163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete Logical Link (dlll) 2-165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Channel Configuration (dscc) 2-168. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Channel Group (dscg) 2-179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Control Signals (dscs) 2-185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display DS0B Base Channels (dsdbc) 2-189. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display DS-1 Channel Module Configuration (dsdcmc) 2-192. . . . . . . . . . . . . . . . Display Logical Link (dsll) 2-194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Multiplexer Component Configuration (dsmcc) 2-197. . . . . . . . . . . . . . . . Display Network Administration Port Configuration (dsnapc) 2-201. . . . . . . . . . . Display Node Configuration Parameters (dsncp) 2-204. . . . . . . . . . . . . . . . . . . . . . Display Node Connected to System (dsncs) 2-213. . . . . . . . . . . . . . . . . . . . . . . . . .

2


2-2 August 1994 6800-A2-GB32-10

Display Physical Link Configuration (dsplc) 2-215. . . . . . . . . . . . . . . . . . . . . . . . . Display Routing Table (dsrt) 2-221. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Supervisory Data Link Configuration (dssdlc) 2-223. . . . . . . . . . . . . . . . . Display T1 Interface Status (dstis) 2-228. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DS0B Channel Summary (dcs) 2-231. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DS0B Performance and Status (dps) 2-234. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DS-1 Channel Loopback (dcl) 2-236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DS-1 Channel Module Test (dcmt) 2-238. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Performance Report (epr) 2-240. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Facility Errors Report (fer) 2-243. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Facility Performance Report (fpr) 2-246. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generate Routing Tables (grt) 2-253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Module Summary (hms) 2-255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal Test (it) 2-259. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Link Summary (lls) 2-261. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Make Channel Connection (mkcc) 2-264. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Make Channel Group Connection (mkcgc) 2-266. . . . . . . . . . . . . . . . . . . . . . . . . . Make Logical Link Connection (mkllc) 2-268. . . . . . . . . . . . . . . . . . . . . . . . . . . . . NAP and SDL State Summary (nsss) 2-270. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Paths Summary (nps) 2-273. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Wide Channel Group Summary (nwcgs) 2-277. . . . . . . . . . . . . . . . . . . . . Node Errors Report (ner) 2-279. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node State Summary (nss) 2-281. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Link Loopback (pll) 2-286. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Link Module Test (plmt) 2-289. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power and Alarm Control Test (pact) 2-291. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Physical Link Loopback (rpll) 2-292. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Diagnostic Status (rds) 2-294. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset Control Processor (rcp) 2-297. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Node Database (rstrnd) 2-298. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Slot Performance Report (tspr) 2-301. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Slot Summary (tss) 2-304. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSI Module Test (tsimt) 2-308. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice Channel Tone Test (vctt) 2-309. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OverviewThis chapter provides descriptions of the input and results forms for NMS multiplexer commands.

Multiplexer Commands

2-36800-A2-GB32-10 August 1994

Acquire Channel Groups (accg)Use the accg command to upload channel group configuration data (channel group names, channelgroup endpoints, channel group routing choices, channel group routing specifications, and attributerouting specifications) from the network to the 6800 Series NMS database.

This command is typically used when the NMS is being installed or restored after a failure, orwhen the channel group table needs to be recovered because of a failure at the NMS for an existingACCULINK� multiplexer network. It is also used when channel groups have been created,deleted, or modified using the terminal interface to the multiplexer nodes.

NOTE

If there is channel group information already stored in the NMSdatabase when you execute this command, that information isreplaced by the current channel group information obtained from thenetwork.

The data is stored in an INFORMIX� table. Previous data is over-written and replaced wheneverthis command is successfully executed. If the command fails due to some network orcommunications problem, the previous data remains in the table along with any channel group thathas successfully loaded.

Typically, a user executes this command in one of two applications.

• With an existing ACCULINK network, the 6800 Series NMS is installed, restored after afailure, or the channel group table needs to be recovered because of some type of failure.

• With an existing ACCULINK network, the user has created, deleted, or modified channelgroup configurations through the terminal interfaces to the multiplexers. Normally, the userwould be expected to use the 6800’s commands to configure channel groups. Here the NMSsynchronizes the modifications with its internal channel group table. If the user bypasses theNMS commands and uses the multiplexer terminal to configure channel groups, NMS willnot receive the modification information and its channel group table will becomeinconsistent with the multiplexer network data.

The channel group data stored by the NMS is used by the NMS as input or reference in thefollowing commands: Break Channel Group Connection (brcgc), Channel Group Loopback (cgl),Channel Group Performance Report (cgpr), Channel Group Summary (cgs), Channel Group Trace (cgt), Change Channel Group (chcg), Create Channel Group (crcg), Delete Channel Group (dlcg), Display Channel Group (dscg), Make Channel Group Connection (mkcgc), andNetwork Wide Channel Group Summary (nwcgs).

For a complete description of the Destination for Results and Schedule execution fields, refer toChapter 1, Introduction.

Access Level: Manager

Abbreviation: accg

Restrictions: Users must have network access permission to the entire multiplexer network in order to execute this command.

Routine: Yes

Schedule: Yes


2-4 August 1994 6800-A2-GB32-10

Related Command: Change Channel Group (chcg)Channel Group Summary (cgs)Create Channel Group (crcg)Delete Channel Group (dlcg)Display Channel Group (dscg)Network Wide Channel Group Summary (nwcgs)

Acquire Channel Groups Input Form

The field on the Acquire Channel Groups input form is as follows.

Node (Required Field) [31 chars, no default]

Enter the node(s) for which you want to acquire the channel groups. Multiple nodes canbe entered, separated by commas or spaces. The keyword all can be entered to signify allnodes. Nodes can be specified by using the device name, device address, serial number(ser-xxxxxxxxxxxx) or node number. Network names (net-xxxxxxxxxxxxxxx) can beentered. Circuit names can also be entered (cir-xxxxxxxxxxxxxxxxxxxxxxxxx). Wildcardcharacters can be used anywhere within the node specification. Only 731, 74x, 74x-56K,and 745 nodes are allowed; all such nodes must have device profiles. When the keywordall is entered, the command will acquire channel groups only for these allowed nodes(i.e., 731, 74x, 74x-56K, 745).

The following warning message will appear:

WARNING: If two channel groups exist with the same name in the network, pleasedelete/change one before continuing with this command. If this is not done,inconsistencies between the system and the network will occur after this commandhas executed.

The first pair of nodes that returns the channel group name will be stored by the NMS. You areunable to access the channel group from the second (or more) pair using NMS commands. You canuse the Channel Group Summary (cgs) command to find the inconsistencies mentioned above.

Acquire Channel Groups Results Form

The fields on the Acquire Channel Group results form are described as follows.

Chnl Grp

The name of each channel group acquired by this command.

Endpoints

The node numbers of the channel group endpoints of the acquired channel group.


2-56800-A2-GB32-10 August 1994

Route

The type of configured routing of the channel group: automatic or fixed. For eachconfigured fixed route choice, the fixed route is displayed, node-by-node and link-by-link,if node/link routing has been used. Logical links are designated by the prefix LL in frontof the link number.

NOTE

The 74x-56K channel groups only display endpoints. Routes are notdisplayed.

Acquire Channel Groups Input Form

The Acquire Channel Groups input form does not require data input for command execution. Thefollowing warning message will appear:

WARNING: If two channel groups exist with the same name in the network, pleasedelete/change one before continuing with this command. If this is not done,inconsistencies between the system and the network will occur after this commandhas executed.

The first pair of nodes that returns the channel group name will be stored by the NMS. You areunable to access the channel group from the second (or more) pair using NMS commands. You canuse the Channel Group Summary (cgs) command to find the inconsistencies mentioned above.

Acquire Channel Groups Results Form

The fields on the Acquire Channel Group results form are described as follows.

Chnl Grp

The name of each channel group acquired by this command.

Endpoints

The node numbers of the channel group endpoints of the acquired channel group.

Route

The type of configured routing of the channel group: automatic or fixed. For eachconfigured fixed route choice, the fixed route is displayed, node-by-node and link-by-link, if node/link routing has been used. Logical links are designated by the prefix LLin front of the link number.

NOTE

The 740-56K channel groups only display endpoints. Routes are notdisplayed.


2-6 August 1994 6800-A2-GB32-10

Acquire Logical Links (acll)Use the acll command to upload logical link configuration data (logical link numbers, endpointnodes, endpoint links, endpoint time slots, logical link capacities, logical link connection states)from the ACCULINK network to the 6800 Series NMS.

This command is typically used when the NMS is being installed or restored after a failure, orwhen the logical link table needs to be recovered because of a failure at the NMS for an existingACCULINK multiplexer. It is also used when logical links have been created, deleted, or modifiedusing the terminal interface to the multiplexer node.

NOTE

If there is logical link information already stored in the NMSdatabase when you execute this command, that information will bereplaced by the current logical link information. The successfulcompletion of the command is verified before the table is over-written. If a failure occurs, the previous data is restored to the table.

The data is stored in an INFORMIX table. Previous data is over-written and replaced wheneverthis command is successfully executed. If the command fails due to some network orcommunications problem, the previous data remains in the table.

Typically, a user executes this command in one of two applications.

• With an existing ACCULINK network, the 6800 Series NMS is installed, restored after afailure, or the logical link table needs to be recovered because of some type of failure.

• With an existing ACCULINK network, the user has created, deleted, or modified logicallink configurations through the terminal interfaces to the multiplexers. Normally, the userwould be expected to use the 6800’s commands to configure logical links. Here the NMSsynchronizes the modifications with its internal logical link table. If the user bypasses theNMS commands and uses the multiplexer terminal to interface logical links, NMS will notreceive the modification information and its logical link table will become inconsistent withthe multiplexer network data.

The physical links associated with each logical link acquired from the network must have a facilityprofile in the NMS. Be sure to create facility profiles for all T1 links in your network beforeexecuting this command.

The logical link data stored by the NMS is used by the NMS as input or reference in the followingcommands: Break Logical Link Connection (brllc), Change Channel Group (chcg), ChangeLogical Link (chll), Create Channel Group (crcg), Create Logical Link (crll) , Delete Logical Link (dlll) , Display Logical Link (dsll), Logical Link Summary (lls), Make Logical LinkConnection (mkllc), and Network Paths Summary (nps).


2-76800-A2-GB32-10 August 1994

For a complete description of the Destination for results and Schedule execution fields, refer toChapter 1, Introduction.


Abbreviation: acll

Restrictions: None

Routine: Yes

Schedule: Yes

Related Command: Change Channel Group (chcg)Change Logical Link (chll)Create Channel Group (crcg)Create Logical Link (crll)Delete Logical Link (dlll)Display Logical Link (dsll)Logical Link Summary (lls)Network Paths Summary (nps)

Acquire Logical Links Input Form

The field on the Acquire Logical Links input field is as follows.

Node(s) (Required field) [31 chars, no default]

Enter the node(s) for which you wish to acquire the logical links. Multiple nodes can beentered, separated by commas or spaces. The keyword all can be entered to signify allnodes. Nodes can be specified by using the device name, device address, serial number(ser-xxxxxxxxxxxx) or node number. Network names (net-xxxxxxxxxxxxxxx) can beentered. Circuit names can also be entered (cir-xxxxxxxxxxxxxxxxxxxxxxxxx). Wildcardcharacters can be used anywhere within the node specification. Only 74x nodes of featurepackages 3.x.x or 4.x.x are permitted. All such nodes must have device profiles.


2-8 August 1994 6800-A2-GB32-10

Acquire Logical Links Results Form

The fields on the Acquire Logical Links results form are as follows.

Logical link number

The number of the logical link, always preceded by LL .

Logical Link name

The name of the logical link. This is only available if the logical link had beencreated/updated with a name from the NMS commands. This is always prefixed with ll- .

Capacity

The capacity of the logical link in number of time slots.

Current state

The current connection state of the logical link.

Configured state

The configured connection state of the logical link.

Endpoint 1 node/link

The node number and link number of the node and link at one end of the logical link.

Time slots

The numbers of the time slots allocated to the logical link, or all if all 24 time slots on thephysical link are allocated to the logical link.

Endpoint 2 node/link

The node number and link number of the node and link at the other end of the logical link.

Time slots

The numbers of the time slots allocated to the logical link, or all if all 24 time slots on thephysical link are allocated to the logical link.


2-96800-A2-GB32-10 August 1994

Acquire Physical Attributes (acpa)Use the acpa command to upload physical attribute configuration data (physical attribute states forknown links) from the ACCULINK network to the 6800 Series NMS.

The user can request that physical attribute configuration from one or more nodes in the networkbe uploaded.

This command is used when the NMS is being installed or restored after a failure, or when thephysical attribute table needs to be recovered because of a failure at the NMS for an existingACCULINK multiplexer network. It is also used when physical attributes have been created,deleted, or modified using the terminal interface to the multiplexer nodes.

NOTE

If there is physical attribute information already stored in the NMSdatabase when you execute this command, that information isreplaced by the current physical attribute information. Thesuccessful completion of the command is verified before the table isover-written. If a failure occurs, the previous data is restored to thetable.

Typically, a user would execute this command in one of two applications:

• With an existing ACCULINK network, the 6800 Series NMS is being installed, restoredafter a failure, or the physical attribute table needs to be recovered because of some type offailure.

• With an existing ACCULINK network, the user has created, deleted, or modified physicalattribute configurations by changing physical (T1) link configurations through the terminalinterfaces to the multiplexers. Normally, the user would be expected to use the 6800 SeriesNMS to configure physical links. Here the NMS synchronizes the modifications with itsinternal physical attributes table. If the user bypasses the NMS and uses the multiplexerterminal to configure the physical attributes, NMS does not receive the modificationinformation and its physical attributes table becomes inconsistent with the network.

The physical attribute data stored by the NMS is used by the NMS as input or reference in thefollowing commands: Logical Link Summary (lls), Display Physical Link Configuration (dsplc),Change Physical Link Configuration (chplc), Display Logical Link (dsll), Change Logical Link (chll), and Create Logical Link (crll) .


2-10 August 1994 6800-A2-GB32-10



Abbreviation: acpa

Restrictions: None

Routine: Yes

Schedule: Yes

Related Command: Acquire Logical Links (acll)Change Logical Link (chll)Change Physical Link Configuration (chplc)Create Logical Link (crll)Display Logical Link (dsll)Logical Link Summary (lls)

Acquire Physical Attributes Input Form

The fields on the Acquire Physical Attributes input form are as follows.


Enter the node for acquiring physical attributes. Multiple nodes can be entered, separatedby commas or spaces. The keyword all can be entered to signify all nodes. Nodes can bespecified by using the device name, device address, serial number (ser-xxxxxxxxxxxx) ornode number. Network names (net-xxxxxxxxxxxxxxx) can be entered. Circuit names(cir-xxxxxxxxxxxxxxxxxxxxxxxxx). Wildcard characters can be used anywhere withinthe node specification. Only 74x nodes of feature packages 3.x.x or 4.x.x are permitted.All such nodes must have device profiles.

Acquire Physical Attributes Results Form

The fields for each node and link on the Acquire Physical Attributes results form are as follows.

Physical Attribute

The physical attribute’s numbers and names. For each link shown, all six physicalattribute numbers and names are listed. The attribute names are obtained from the NMSdatabase, as previously set by the user with the Change Node Configuration Parameters(chncp) command.

State

The active or inactive status of the physical attribute. The states can be changed by theuser when configuring the physical link with the Change Physical Link Configuration(chplc) command.


2-116800-A2-GB32-10 August 1994

Backup Node Database (bkupnd)Use the bkupnd command to archive one or more configuration databases from ACCULINKnetwork nodes to tape on the COMSPHERE 6800 Series NMS.

NOTE

Only currently available nodes with device profiles can be backedup using this command.

Typically, a user would execute this command periodically to take a snapshot of the configurationdata residing in the EEROM database on the node. The data retrieved can then be used duringdisaster recovery to restore a node database to its last known state. For information on how torestore a node database, see the rstrnd command.

Prior to running this command, a blank or reusable tape cartridge must be present in the tape driveof the host NMS processor. For more information regarding the use of tapes and tape drives, seeyour system documentation.

WARNING

An existing archive on the tape will be overwritten uponsuccessful completion of this command.


Abbreviation: bkupnd

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Restore Node Database (rstrnd)


2-12 August 1994 6800-A2-GB32-10

Backup Node Database Input Form

The fields on the Backup Node Database input form are as follows.

Node (Required field) [31 chars, no default]

Enter the node(s) you want to back up. Multiple nodes can be entered, but must beseparated by commas or spaces. Wildcards are permitted. The keyword all can be enteredto signify all nodes. Nodes can also be specified in any of the following ways:

• Node number

• Node name

• Node address

• Serial number (of the node, as found in the device profile for the node, in thisformat: ser-xxxxxxxxxxxx)

• Circuit name (in this format: cir-xxxxxxxxxxxxxxxxxxxxxxxxx)

• Network name (in this format: net-xxxxxxxxxxxxxxx)

Priority Level (Required field) [6 chars, default=LOW]

Enter a priority level for this command. The possible choices are HIGH , MEDIUM , andLOW. The priority level acts as a multiplier for a pacing interval used during the nodedatabase retrieval process. A priority level of HIGH disables any pacing, MEDIUM usesthe current pacing interval, and LOW will use twice the current pacing interval. Thedefault pacing interval is set at 2 seconds. This value may be changed via thePACING_INTERVAL environment variable.

Following the input of the above two fields, the NMS will query the network to determine if thespecified nodes can be backed up. This process can take up to several minutes depending on thenumber of nodes entered. Subsequently, the Destination for results and Schedule execution fieldsare displayed. For a complete description of these fields, refer to Chapter 1, Introduction.


2-136800-A2-GB32-10 August 1994

Backup Node Database Results Form

The fields on the Backup Node Database results form are as follows.

Node

The node identifier.

Status

The results of the backup operation: SUCCESSFUL or UNSUCCESSFUL.

Date/Time

The date and time the node was backed up.

Elapsed Time

The elapsed time it took to backup the node.

NOTE

The above information will be repeated for each node specified inthe Backup Node Database input form. The number of result pageswill vary depending on the number of nodes specified.


2-14 August 1994 6800-A2-GB32-10

Bit Error Rate Test (bert)(Disruptive)

Use the bert command to place a designated channel endpoint into a loopback state and send a testbit-block through the loop, checking for errors during the transmission. In some cases, bothendpoints may be put into loopback.

The effect of this test is to measure the overall performance of the transmission path of anACCULINK multiplexer’s connected channels and the hardware associated with the channelendpoints.

This test must be executed in three separate operations.

• Start the test. The NMS will put the channel endpoints out-of-service and into loopback andstart the bit-block transmission.

• Report the intermediate results during test execution (optional).

• Stop the test. The NMS will place the channel endpoints back into normal operation andreport results.

This test can be directed to any connected voice, data, DDS, or DS0 channel on a 731, 740, 741,742 or 74x-56K multiplexer, or to any DS0 channel on a 745 recognized by the NMS as a channelendpoint (on a T1 link connected to other).

For a complete description of the Destination for results and Schedule execution fields, refer toChapter1, Introduction.

NOTE

The channel will be taken out-of-service while the bert is runningand placed back in-service when finished. Permission checking ispresent to ensure that the user has the appropriate commandpermission level to take the channel out-of-service before runningthe test. If the user does not have permission to execute theChange Channel Configuration (chcc) command and the designatedchannel is currently in-service, the bert will not run.

Access Level: Help Desk, Data Technician, Manager

Abbreviation: bert

Restrictions: You cannot run a bit error rate test on a channel if one of the other channels on the same channel module is already running a bit error rate test or is in a loopback state. This can be checked by running the Report Diagnostic Status (rds) command.

For synchronous data channels, you must first disable the rate adaption option using the Change Channel Configuration (chcc) command. Refer to the Change Channel Configuration (chcc) command for more information on the rate adaption option.


2-156800-A2-GB32-10 August 1994

Routine: Yes

Schedule: Yes

Related Command: Channel Loopback (cl)Channel System Test (cst)Internal Test (it)Modem Bit Error Rate Test (mbert)

Bit Error Rate Test Input Forms

There are three input forms associated with the Bit Error Rate Test. The initial form enables you toidentify the node and channel for which the BERT will be executed. The second input form ischannel-type dependent. For all channel types with the exception of DDS, the second input formdisplays. For DDS channel types a third input form displays.

The fields on the Bit Error Rate Test initial input form are described as follows.


Enter the node on whose channel the bert will run Only a single node and 731, 740, 741,742, 745, and 74x-56k nodes with device profiles can be entered. The user can enter thenode number, node name, or node device address (m2/node number).

Channel (Required field) [7 chars, no default]

Enter the channel number for the bert. Only a single channel number can be entered. Thechannel number must meet one of the following validation criteria.

731 0 to 3

740 0 to 127, XtsY, where X is 0 to 127 (multiples of 8 only), Y is 1 to24

741 0 to 39 XtsY, where X is 0, 8, 16, 24, 32, Y is 1 to 24

742 0 to 31, XtsY, where X is 0, 8, 16, 24, Y is 1 to 24

740-56K 0 to 127

741-56K 0 to 39

745 XtsY, where X is 0 to 15, Y is 1 to 24

For a voice or data channel, enter the channel number. For a DS0 channel on a740/741/742, enter the channel in the format XtsY, where X is the base channel numberand Y is the time slot. For DS0 channels on a 745, enter the channel in the format XtsY,where X is the link number and Y is the time slot.

If the identified channel is in a stub channel group, the following two additional fields will bedisplayed on the Bit Error Rate Test input form. These fields provide remote channel endpointinformation to the NMS, which enables the NMS to place both endpoints into loopback andinitiate/stop the bert.

Destination node (Required field) [15 chars, no default]

Enter the node of the remote channel endpoint. The Destination node field definition isidentical to the Node field definition listed above.


2-16 August 1994 6800-A2-GB32-10

Destination channel (Required field) [7 chars, no default]

Enter the channel of the remote channel endpoint. The Destination channel fielddefinition is identical to the Channel field definition listed above.

The field on the Bit Error Rate Test (non-DDS) input form is as follows.

Bert state (Required field) [14 chars, no default]

Enter start to initiate the bert test. (The bert runs continuously until it is stopped.)

Enter stop to terminate the bert test.

Enter report results to display the bert test results.

A sample Bit Error Rate Input Form (DDS Channels) is shown in Figure 2-1.

Figure 2-1. Bit Error Rate Test Input Form (DDS Channels), Page 2


2-176800-A2-GB32-10 August 1994

The fields on the Bit Error Rate Test input form are as follows.

Channel type

The display-only field that indicates the type of DDS channel. The two possible typesdisplayed are DDS-ocu and DDS-dsu, depending on the type of DDS channel interfacecard.

Bert state (Required field) [14 chars, no default]

This field controls the bert test.

Enter start to initiate the bert test. (The bert runs continuously until it is stopped).

Enter stop to terminate the bert test.

Enter report results to display the bert test results.

Direction [7 chars, no default]

Enter the direction of the loopback for the bert.

network

The bit pattern exits from the multiplexer on the network T1 side to remoteequipment, causing the remote equipment to revert to the loopback state.

loop

The bit pattern exits from the multiplexer on the DDS channel side to remoteequipment, causing the remote equipment to revert to the loopback state.

Type

Enter where to loopback the data.

pure

This test sends a fixed bit pattern (511 CCIPT) for the bert without looping theremote end, so the user must configure external equipment to either terminate thebert pattern or to loopback the local/remote end. All other bert types arenon-latching and do not require external test equipment to do the loopback.

ocu

This test loops back at the OCU port.

dsu

This test loops back at the DSU interface of the attached DSU/CSU.

csu

This test loops back at the CSU interface of the attached DSU/CSU.


2-18 August 1994 6800-A2-GB32-10

NOTE

For an ocu-dp channel, loop side loopbacks are all done at the DDSchannel module. Selecting any of the three non-pure loopback typesallows you to do this. If the designated channel is currentlyin-service, the NMS automatically takes the channel out-of-servicebefore initiating the loopback, provided the user has permission forthe Change Channel Configuration (chcc) command.

Bit Error Rate Test Results Form

The top of the Bit Error Rate Test results form shows information on the channel for which yourequested the bit error rate test.

The fields on the Bit Error Rate Test results form are as follows.

Bert state

The requested state of the bit error rate test.

Bit error rate

The measured bit error rate, expressed as the number of errors counted since thebeginning of the test, along with the total numbers of bits transmitted through the test.

Synch loss

This field displays if you entered report results or stop in the Bert state field. TheSynch loss field indicates one of the following.

active

The synch loss error condition is active for DDS channels.

not active

The synch loss error condition is not active for DDS channels.

not applicable

This field is not applicable for all other channels.


2-196800-A2-GB32-10 August 1994

Data fault

This field displays if you entered report results or stop in the Bert state field. The Datafault field indicates one of the following.

active

The data fault error condition is active for DDS channels.

not active

The data fault error condition is not active for DDS channels.

not applicable


Out of lock

This field displays if you entered reports results or stop in the Bert state field. The Outof lock field indicates one of the following.

active

The out-of-lock error condition is active for DDS channels.

not active

The out-of-lock error condition is not active for DDS channels.

not applicable



2-20 August 1994 6800-A2-GB32-10

Break Channel Connection (brcc)(Disruptive)

Use the brcc command to break the connection between the endpoints of two ACCULINKmultiplexer channels. (This command is not valid for Synchronous Supervisory Data Linkchannels.) When you break the channel connection, channel group bandwidth for the channel isdeallocated. You must break a channel connection to:

• Change some of the parameters of the channel configuration using the Change ChannelConfiguration (chcc) command.

• Assign a channel to a different channel group using the Change Channel Configuration(chcc) command.

• Take a DS1 channel module out-of-service with the Change DS-1 Channel ModuleConfiguration (chdcmc) command.

• Change the channel module type with the Change Channel Module Type (chcmt) command.


NOTE

The Channel State Summary (css) command can be used to list allchannels on a node or link with their current connection state. TheChannel Summary (cs) command can be used to list all channels ina channel group with their current connection state.

Access Level: Data Technician, Manager

Abbreviation: brcc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Command: Channel State Summary (css)Channel Summary (cs)


2-216800-A2-GB32-10 August 1994

Break Channel Connection Input Form

The fields on the Break Channel Connection input form are described as follows.


Enter the node whose channel connection will be broken. Only a single node and 731,740, 741, 742, 745, or 74x-56K nodes that have device profiles can be entered. The usercan enter the node number, node name, or node device address (m2/node number).


Enter the channel number for which the connection should be broken. Only a singlechannel number can be entered. The channel number must meet one of the followingvalidation criteria, depending on the type of node.

731 0 to 3

740 0 to 127, XtsY, where X is 0 to 127 (multiples of 8 only), Y is 1 to 24

741 0 to 39, XtsY, where X is 0, 8, 16, 24, 32, Y is 1 to 24

740-56K 0 to 127

741-56K 0 to 39


For a voice or data channel, enter the channel number. For a DS0 channel on a 740/741,enter the channel in the format XtsY, where X is the base channel number and Y is thetime slot. For DS0 channels on a 745, enter the channel in the format XtsY, where X is thelink number and Y is the time slot.

Break Channel Connection Results Form

The Break Channel Connection results form displays the nodes and channels for which theconnection was broken. It also displays a message indicating whether the connection break wassuccessful and the start and completion time of the transaction.


2-22 August 1994 6800-A2-GB32-10

Break Channel Group Connection (brcgc)(Disruptive)

Use the brcgc command to break the connection for a channel group. When you break theconnection, T1 bandwidth for the channel group is deallocated.

The channel group connection must be broken in order to:

• Change some of the parameters of the channel group configuration with the Change ChannelGroup (chcg) command.

• Delete a channel group with the Delete Channel Group (dlcg) command.

• Manually force a reroute of the channel group. Breaking the channel group connection, thenissuing a Make Channel Group Connection (mkcgc) command causes the nodes to attempt toreroute the channel group over its First choice route, if available.

Breaking a channel group connection will cause all the channels in the channel group to go into thechannel group disconnected state, disrupting those channels.


NOTE

The Channel Group Summary (cgs) command can be used to list allchannel groups defined at a node with their current connectionstate.


Abbreviation: brcgc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Channel Group Summary (cgs)

Make Channel Group Connection (mkcgc)

Break Channel Group Connection Input Form.

The field on the Break Channel Group Connection input form is as follows.

Channel group (Required field) [9 chars, no default]

Enter the name of the channel group to be disconnected. Only a single channel group canbe entered.


2-236800-A2-GB32-10 August 1994

Break Channel Group Connection (non-56K) Results Form

The Break Channel Group Connection results forms for the non-56K and the 56K are very similar.The fields on the non-56K results form are described as follows.

Channel group

The name of the channel group being disconnected.

Endpoint node numbers

The endpoint node numbers of the channel group being disconnected.

Endpoint node names

The endpoint node names and model numbers of the channel group being disconnected.

The following are for non-56K only.

First choice route

The requested routing type for the first choice (fixed, automatic).

Second choice route

The requested routing type for the second choice (fixed, automatic, none).

Third choice route

The requested routing type for the third choice (automatic, none).

First fixed route

The first fixed route, if the First choice route type was fixed. The string NID# means thechannel group route enters a foreign network (e.g., a DACS) at that point in its route.

Second fixed route

The fixed route, if the Second choice route type was fixed. The string NID# means thechannel group enters a foreign network (e.g., a DACS) at that point in its route.


2-24 August 1994 6800-A2-GB32-10

Break Logical Link Connection (brllc)(Disruptive)

Use the brllc command to break the connection for a logical link. The T1 bandwidth for the logicallink is deallocated when the logical link connection is broken.

Any channel group that is currently routed over the logical link must be idled (disconnected)before the logical link connection can be broken. This command automatically breaks such channelgroup connections, after a confirmation from the user, if the user has functional user grouppermission for the brcgc command. If the user does not have permission, the brllc will not execute.

The logical link connection must be broken in order to:

• Change some of the parameters of the logical link configuration with the Change LogicalLink (chll) command.

• Delete a logical link with the Delete Logical Link (dlll) command.

NOTE

The Logical Link Summary (lls) command can be used to list alllogical links defined at a node with their current connection state.



Abbreviation: brllc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Logical Link Summary (lls)Make Logical Link Connection (mkllc)


2-256800-A2-GB32-10 August 1994

Break Logical Link Connection Input Form

The fields on the Break Logical Link Connection input form are as follows.


Enter the node where the logical link(s) is to be broken. Only a single node and nodenumbers and node names for 74x nodes of feature packages 3.x.x or 4.x.x are allowed. Allsuch nodes must have device profiles. The user can also enter the node device address(m2/node number).

Logical Link(s) (Required field) [37 chars, no default]

Enter the logical link(s) whose connections will be broken. Logical links can be enteredby typing in the logical link number or logical link name. If the number is entered, it mustbe preceded by the string LL . If the name is entered, it must be preceded by the string ll- .Multiple entries are permitted, separated by spaces or commas. The wildcard character *is permitted. The keyword all is permitted to designate all logical links at the given nodalendpoint. Only logical links that are known to the NMS (in its database) are permitted.

If there are connected channel groups on the designated logical link(s), a confirmer messagedisplays, warning the user that the channel group connections will be broken if the logical linkrequest is executed. This will disrupt all network traffic carried in those channel groups. The usercan then decide to continue the transaction or cancel the break request. If the user cancels the breakrequest, no connection changes are made, regardless of how many break requests were made.

The confirmer message is displayed only if the user has access permission for the Break ChannelGroup Connection (brcgc) command. If the user does not have such permission, a permission formis displayed.

Break Logical Link Connection Results Form

The fields on the Break Logical Link Connection results form are described as follows.

Logical link number

The number of the logical link requested to be broken.

Logical link name

The name of the logical link requested to be broken.

Endpoint 1 node

The node number of one of the endpoints of the logical link.

Endpoint 2 node

The node number of the other endpoint of the logical link.

A series of possible messages may be included with the results.


2-26 August 1994 6800-A2-GB32-10

Channel group ccccccccc was successfully broken

This message is displayed if a channel group was automatically broken by the NMS aspart of this command. A separate message for each broken channel group is displayed.

Channel group cccccccc could not be broken

This message is displayed if a connected channel group on the designated logical linkcould not be broken. The logical link break request will also fail in this case.

NMS database was updated to match the node database

This message is displayed if a mismatch was discovered between the logical linkconfiguration data in the NMS and that in the node. The database was updated to matchthe data in the node.

Logical link does not exist at node

This message is displayed if the logical link definition does not exist at the node. Thedisconnect request will fail.

Logical link was successfully broken

This message is displayed if the logical link connection break request is successfullyachieved.

Logical link could not be broken

This message is displayed if the logical link connection break request failed.

Logical link connection is already broken

This message is displayed if it is determined that the connection state of the logical link isalready broken.


2-276800-A2-GB32-10 August 1994

Change Channel Configuration (chcc)Use the chcc command to define and configure channels on 731, 74x, and 74x-56K multiplexers.

If the channel is currently configured, this command is also used to change its configuration.

When configuring a new channel, two endpoints (node and channel) must be specified, exceptwhere one of the following situations occurs:

• The channel is connected to a non-Series 700 device.

• A synchronous data channel is being configured as an SDL and placed in a stub channelgroup.

NOTE

With the feature package 3.x.x multiplexer, this is no longernecessary. Synchronous data channel SDLs can be configuredwithout using a channel group. The Change Supervisory Data LinkConfiguration (chsdlc) command must be used to configure thesechannels.

• There is no SDL to the other endpoint.

To configure these single-endpoint channels, the keyword none is entered in the second endpointNode/Channel fields.

When reconfiguring an existing channel, only one endpoint need be identified. The other endpointis obtained from the channel group configuration data in the NMS database.

The input forms for this command are dependent on the type of channel being configured.

For more information on the Destination for results and Schedule execution fields, refer toChapter 1, Introduction.


Abbreviation: chcc

Restrictions: The channel group in which a channel will be placed must be created before it can be assigned to the channel.

Routine: Yes

Schedule: Yes

Related Commands: None

This command has many forms, depending on the type of channel endpoints being configured.Note that, if configuring a channel with two endpoints, the forms are two-sided forms, with thechannel configuration of one endpoint on the left side and the other endpoint on the right side.When configuring a channel with two endpoints where both endpoints have the same channel type,the fields are labeled identically for both sides of the form. When configuring a channel with twoendpoints where the channel types are different at each endpoint, the validations are different onthe two sides of the form. In some cases, a form is shown with only a single side because of thevery different nature of that endpoint. When configuring a channel with a single endpoint, asingle-sided form is used.


2-28 August 1994 6800-A2-GB32-10

Change Channel Configuration Input Form, Page 1

The fields on the Change Channel Configuration input form are as follows.


Enter the node whose channel will be configured. Only a single node and 731, 74x, and74x-56K nodes with device profiles can be entered. The user can enter the node name,node number, or node device address (m2/node number). The keyword none must enteredin the right-handed Node field to configure a channel with no remote endpoint.


Enter the channel number for the channel being configured. Only a single channel numbercan be entered. The channel number must meet one of the following validation criteria,depending on the type of node.

731 0 to 3

740 0 to 127, XtsY, where X is 0 to 127 (multiples of 8 only),

Y is 1 to 24



740-56K 0 to 127

741-56K 0 to 39

742-56K 0 to 31


For a voice or data channel, enter the channel number. For a DS0 channel on a 740/741/742, enterthe channel in the format XtsY, where X is the base channel number and Y is the time slot. ForDS0 channels on a 745, enter the channel in the format XtsY, where X is the link number and Y isthe time slot.


2-296800-A2-GB32-10 August 1994

Only one endpoint is required. If the channel is currently assigned to a channel group, the secondendpoint information is retrieved from the channel group information. If the channel is new, theuser must enter the desired node/channel for the remote endpoint, except in the case of thefollowing situations:

• The channel is connected to a non-Series 700 device.

• A synchronous data channel is being configured as an SDL and placed in a stub channelgroup.

NOTE

With the feature package 3.x.x multiplexer, this is no longernecessary. Synchronous data channel SDLs can be configuredwithout using a channel group. The Change Supervisory Data LinkConfiguration (chsdlc) command must be used to configure thesechannels.

• The channel is assigned to a stub channel group.

• There is no SDL to the other endpoint.

The NMS obtains the configuration and current connection states of both channel endpoints. Thefollowing three checks are immediately done on the information, resulting in three possibleconfirmer/error situations.

1. The channel is currently configured as a synchronous SDL channel, and either the SDLstate is active or the channel state is active. Both states must be out-of-service in order forthe channel to be reconfigured as a non-SDL channel. This is an error situation. The usermust cancel the command at this point. The SDL and channel states are changed with theChange Supervisory Data Link Configuration (chsdlc) command.

2. The channel is currently configured as a synchronous SDL channel, and the SDL state andchannel state are out-of-service. The user gets a warning message here, stating that thechannel will be reconfigured as a non-SDL channel. The user must confirm thecontinuation of the command.

3. If either channel is in a connected state, the user must confirm the continuation of thecommand, since the channel connection will be automatically broken by the NMS.

If the user selects Cancel, the command forms are closed and the user returned to the last menu.Otherwise, the user can select Continue to proceed.

If the user does not have access permission for the brcc command, and the channel state isconnected, the user is not permitted to continue.


2-30 August 1994 6800-A2-GB32-10



Current destination [12 chars]

This display-only field indicates the currently configured destination node and channel ofeach channel endpoint. The node and channel are identified with the format Nnnn Cnnnwhere Nnnn indicates node number nnn, and Cnnn indicates channel number nnn. If thechannel is being configured for the first time, both destinations are listed with a ?.

Current connection state

This display-only field indicates the current connection state of the channel. Possiblevalues are connected, time-of-day disconnected, cg-disconnected, idle, anddisconnected.

Requested state (Required field) [9 chars, default = idle]

The user can request the final state of the channel after the configuration change hascompleted. A pop-up menu displays the selections connected or idle. The user must havefunctional access permission for the mkcc to set this field to connected. If the user selectsconnected, a mkcc command will be automatically executed as part of the change request.

Channel type [12 chars]

This display-only field shows the type of channel being configured. It is determined bythe channel module type (see the Change Channel Module Type (chcmt) command).Possible values are synch.data, asynch.data, lbr-voice, e-voice, voice, DS0, DDS-dsu,DDS-ocu, synch-DS0 group, or DS-0 group.


This field specifies the channel group used for the channel. The channel group must bethe same for both endpoints. The channel group must already exist. Fornetwork-compatible channel groups, only 64 kbps robbed-bit voice, Nx64 kbpssynchronous data, with active clear channel, and Nx56 kbps synchronous data channelscan be assigned.


2-316800-A2-GB32-10 August 1994



Connection condition (Required field) [11 chars, default = permanent]

This field sets the connection condition for the channel. Both endpoints must be set to thesame condition. Possible values are permanent and time-of-day, available with a pop-upmenu. The permanent value sets the channel to be connected 24 hours per day. Thetime-of-day value sets the channel to be connected only at specified times of the day.These times are set in the configuration of the designated channel group (either thechannel group is a time-of-day channel group, or the channel connection times arespecified in the channel group configuration).

Service state (Required field) [14 chars, default = active]

This field sets the service state for the channel. A pop-up menu displays the selectionsactive and out-of-service.

Change Channel Configuration Time-of-Day Input Form, Page 4

A sample Change Channel Configuration Time-of-Day input form is shown in Figure 2-2.

Figure 2-2. Change Channel Configuration Time-of-Day Input Form, Page 4

This form is used to configure time-of-day parameters. Up to four time-of-day set points may beshown, depending on what was configured for the channel group. These fields are only displayedwhen the make set points for the channel group and the connection condition is set to time-of-day.If not, the form is displayed with the message time-of-day configuration not applicable.


2-32 August 1994 6800-A2-GB32-10


Time

This display-only column shows the times of the day the channel connection will bechanged, as defined in the Channel Group configuration. The times are shown in hh:mmmilitary time format.

State (Required field)

For each reconfiguration time, the user must specify the connection state for the channel.Both endpoints must match. A pop-up menu displays the selections connect anddisconnect.

Voice rate (Required field) [7 chars, no default]

This field only appears if the user selected the connection state connect. (Time-of-dayrate changes for DDS channels are not applicable.) The user must then choose the voicerate for the channel for that connection period. A pop-up menu displays the selections 24 kbps, 32 kbps, and 64 kbps for all nodes except 74x-56K nodes. For these nodes, thepop-up lists 24 kbps and 32 kbps. A maximum of 2 different voice rates can beconfigured. For lbr-voice channels, the pop-up lists 8kbps and 16kbps.

Change Channel Configuration Voice Channel Input Form, Page 5

The Voice rate field does not appear for the time-of-day channel when the connection conditionfield is configured as time-of-day.


Voice rate (Required field) [5 chars, no default]

Shows the voice rate for the channel. Both endpoints must match. A pop-up menudisplays the selections 24000, 32000, or 64000 for all nodes except 74x-56K nodes. Thesenodes have a pop-up menu with the entries 24000, 32000.

E output signal (Required field) [10 chars, no default]

This field sets the E output signal type. A voice channel uses E&M Type 1 side signalingand always receives the remote M lead transitions. Both channel endpoints must match. Apop-up menu displays the following selections.

• in-band A/B – This signaling option allocates 800 bps of channel groupbandwidth for A and B signaling bit transmission.

• active – This option forces the local E lead control signal active.

• background – This option forces the channel to transmit the remote M leadtransitions over the SDL to the local’s E lead, without extra bandwidth allocationon the channel group. This option is not permitted if the channel group isnetwork-compatible. This type of signaling may not work with certain PBXtrunk formats (e.g., Delay Dial, Wink Start).

• inactive – This option forces the local E lead control signal inactive.


2-336800-A2-GB32-10 August 1994

• in-bandA – This option forces the channel to transmit the remote M leadwithout any extra voice channel bandwidth. A channel group bandwidth of 400 bps is required for signaling. This option is not permitted if the channelgroup is network-compatible.

• robbed-bit – This option forces the channel to use robbed-bit signaling. Withthis type of signaling, the least significant bits of selected DS1 frames from thevoice data are used for E&M transitions in both directions. This entry does notappear in the pop-up menu for 74x-56K node channels.

Analog signal level (Required field) [9 chars, no default]

Enter the voice channel transmit and receive levels at the channel interface. A pop-upmenu displays the selections 0/0-TLP and -16/7-TLP. The first choice is usuallyapplicable for PBX interfaces, while the latter is applicable to transmission equipment.Both channel endpoints must match.

2dB via net loss (Required field) [8 chars, no default]

This field can be used to enable or disable a 2 dB output signal via net loss (attenuation).Enabling this signal reduces echo caused by 2-wire to 4-wire conversion points ortransmission delays. A pop-up menu displays the selections active and inactive. Bothchannel endpoints must match.

Signal conditioning - E lead (Required field) [8 chars, no default]

This field is used to force the E lead active or inactive. During a disconnection (eitherintentionally caused, or caused by a failure of the link or channel group), the E lead goesinactive for 3 seconds. If this field sets the E lead active, the E lead is forced active tobusy-out the trunk during an alarm/disconnect condition. If this field sets the E leadinactive, the E lead is forced inactive to prevent an incoming call from ringingcontinuously after a disconnect. A pop-up menu displays the selections active andinactive. Both channel endpoints must match.

Change Channel Configuration Expanded Voice Channel Input Form, Page 5

The fields on the Change Channel Configuration Expanded Voice Channel input form are asfollows.

Voice rate

Shows the voice rate for the channel. Both endpoints must match. A pop-up menudisplays the selections 24000, 32000, or 64000 for all nodes except 74x-56K nodes. Thesenodes have a pop-up menu with the entries 24000, 32000.

Analog signal level

This field is displayed for expanded voice channels. Only the adjustable value is used forthe 4343B-FXS and 4343C-FXO. For 4343D-E&M interface types, valid values are0/0-TLP, -16/7-TLP, and adjustable.


2-34 August 1994 6800-A2-GB32-10

2dB via net loss


Signal conditioning - E lead

This field is used to force the E lead active or inactive. During a disconnection (eitherintentionally caused, or caused by a failure of the link or channel group), the E lead goesinactive for 3 seconds. If this field sets the E lead active, the E lead will be forced activeto busy-out the trunk during an alarm/disconnect condition. If this field sets the E leadinactive, the E lead will be forced inactive to prevent an incoming call from ringingcontinuously after a disconnect.

Change Channel Configuration Expanded Voice Channel Input Form, Page 6

The fields on the Change Channel Configuration Expanded Voice Channel input form are asfollows.

Signal options

When configuring a remote channel, the local and remote field values must match. Validvalues, when the interface type is 4343D-E&M, are:

• in-bandA, E-lead

• in-band A/B, E-lead

• robbed-bit, E-lead

• background, E-lead

• active, E-lead

• inactive, E-lead

When the interface type is 4343B-FXS or 4343C-FX0, the valid entries are:

• in-band A, FX

• in-band A/B, FX

• robbed-bit, FX

• background, FX

• forced-A0/B0, FX


• forced A1/B0, FX



2-356800-A2-GB32-10 August 1994

Signal Mode

This field is displayed when the interface type is 4343B-FXS or 4343C-FX0. The menuvalues, when the interface type is 4343B-FXS and both endpoints are expanded voice,are:

• STD-FXS-loop

• STD-FXS-grnd

• IEC-TRNK-loop

• IEC-TRNK-grnd

• IEC-TRNK-loop/rev-bat

• IEC-TRNK-grnd/rev-bat

• IEC-TRNK-wink/loop

• IEC-TRNK-wink/grnd

• IEC-TRNK-wink/loop/rev-bat

• IEC-TRNK-wink/grnd/rev-bat

• 6131A-FXS-loop

• 6131A-FXS-grnd

• 6131A-FXS-loop/rev-bat

• PLARD

Voice coding

When configuring a remote channel, the local and remote values must match. Menuvalues for the 4343B-FXS, 4343C-FXO, and 4343D-E&M interface types are mu-law,and a-law.

Adj. receive TLP (dBm)

For interface types 4343B-FXS and 4343C-FXO, a valid TLP value is in the range of–12.0 through 0.0 in 0.1 increments. For interface type 4343D-E&M a valid TLP value isin the range of –16.0 through 8.5 in 0.1 increments.

Adj. transmit TLP (dBm)

For interface types 4343B-FXS and 343C-FXO, a valid TLP value is in the range of –3.0through 9.0 in 0.1 increments. For interface type 4343D-E&M a valid TLP value is in therange –17.5 through 14.5 in 0.1 increments.


2-36 August 1994 6800-A2-GB32-10

Ringing

This field is displayed when the interface type is 4343B-FXS. When the Signal Modefield is 6131A-FXS-loop, 6131A-FXS-grnd, 6131A-FXS-loop/rev-bat or PLARD, thevalid values are continuous and interrupted.

When the Signal Mode field is any of the IEC options, the valid values are interruptedand inactive.

When the Signal Mode field is STD-FXS-loop or STD-FXS-grnd, the valid value iscontinuous.

Ringback

This field is displayed when the interface type is 4343B-FXS. When the Signal Modefield is STD-FXS-loop or STD-FXS-grnd, the valid value is inactive.

When the Signal Mode field is PLARD, the valid value is active.

When the Signal Mode field is any value other than STD-FXS-loop or STD-FXS-grnd,valid values are active and inactive.

Change Channel Configuration Low Bit-Rate Voice Channel Input Form, Page 5

The Voice rate field does not appear for the time-of-day channel when the connection conditionfield is configured as time-of-day.

The fields on the Change Channel Configuration Low Bit-Rate Voice Channel input form are asfollows.

Voice rate

A pop-up menu displays the selections 8000 and 16000.

Analog signal level

Enter the transmit and receive levels at the channel interface. This field is displayed forlow bit-rate voice channels. Only the adjustable value is used for the 4343B-FXS and4343C-FXO. For 4343D-E&M interface types, valid values are 0/0-TLP, -16/7-TLP, andadjustable.

2dB via net loss



2-376800-A2-GB32-10 August 1994

Change Channel Configuration Low Bit-Rate Voice Channel Input Form, Page 6

The fields on the Change Channel Configuration Low Bit-Rate Voice Channel input form are asfollows.

Signal options

When configuring a remote channel, the local and remote field values must match. Whenthe interface type is 4343D-E&M, the valid entries are:

• in-bandA, E-lead

• in-band A/B, E-lead

• background, E-lead

• active, E-lead

• inactive, E-lead

• embedded, E-lead

When the interface type is 4343B-FXS or 4343C-FXO, the valid entries are:

• in-band A, FX

• in-band A/B, FX

• background, FX





• embedded, FX

Signal Mode

This field is displayed when the interface type is 4343B-FXS or 4343C-FXO. When theinterface type is 4343B-FXS and both endpoints are low bit-rate voice, the menu valuesare:

• STD-FXS-loop

• STD-FXS-grnd

• 6131A-FXS-loop

• 6131A-FXS-grnd

• 6131A-FXS-loop/rev-bat

• PLARD

Voice coding

When configuring a remote channel, the local and remote values must match. Menuvalues for the 4343B-FXS, 4343C-FXO, and 4343D-E&M interface types are mu-lawand a-law.


2-38 August 1994 6800-A2-GB32-10

Adj. receive TLP (dBm)

For interface types 4343B-FXS and 4343C-FXO, a valid TLP value is in the range of–12.0 through 0.0 in 0.1 increments. For interface type 4343D-E&M, a valid TLP value isin the range of –16.0 through 8.5 in 0.1 increments.

Adj. transmit TLP (dBm)

For interface types 4343B-FXS and 4343C-FXO, a valid TLP value is in the range of –3.0through 9.0 in 0.1 increments. For interface type 4343D-E&M, a valid TLP value is in therange –17.5 through 14.5 in 0.1 increments.

Ringing

This field is displayed when the interface type is 4343B-FXS. When the Signal Modefield is 6131A-FXS-loop, 6131A-FXS-grnd, 6131A-FXS-loop/rev-bat or PLARD, thevalid values are continuous and interrupted.

When the Signal Mode field is any of the IEC options, the valid values are interruptedand inactive.

When the Signal Mode field is STD-FXS-loop or STD-FXS-grnd, the valid value iscontinuous.

Ringback

This field is displayed when the interface type is 4343B-FXS. When the Signal Modefield is STD-FXS-loop or STD-FXS-grnd, the valid value is inactive.

When the Signal Mode field is PLARD, the valid value is active.

When the Signal Mode field is any value other than STD-FXS-loop or STD-FXS-grnd,the valid values are active and inactive.

Change Channel Configuration Synchronous Channel Input Form, Page 5

This form is only shown for synchronous channels. It is Page 3 for permanent synchronous/enhanced synchronous channels and Page 4 for time-of-day synchronous/enhanced synchronouschannels.


Data rate (Required field)

Enter the data rate for the channel. The rate can be any value from 1200 bps through1.536 Mbps, rounded to the nearest 2 kbps increment. The 74x-56K nodes have amaximum data rate of 62800 bps. The user must enter a numerical value, followed by theunits designation of bps, kbps, or mbps. Both endpoints must match.

Transmit clock (Required field)

Enter the source of the transmit clock. A pop-up menu displays the selections internaland external. The internal value configures the channel to generate the clock sourcefrom the channel interface module. The external value configures the channel to obtainits clocking from an external source. The channel endpoints can use different clockingsources.


2-396800-A2-GB32-10 August 1994

Receive clock (Required field)

Enter the source of the receive clock. A pop-up menu displays the selections internal andexternal. The internal value configures the channel to generate the clock source from thechannel interface module. The external value configures the channel to obtain itsclocking from an external source. The channel endpoints can use different clockingsources.

Rate adaption (Required field)

Enter whether rate adaption will be used on the channel. A pop-up menu displays theselections active and inactive. For some data rates, rate adaption must be inactive. Anerror is returned from the multiplexer in these cases.

Non-network compatible (Required field) [8 chars, default = active]

Input to this field is allowed only when Rate adaption is inactive and the Data rate is 56kbps or a multiple of 56 kbps. It configures the channel to be network-compatible, if thefield is set to inactive. In this case, it is possible to terminate the channel on non-74xequipment. The channel will be allocated to a full DS0. If the field is set to active, thechannel can only be terminated on 74x equipment. A pop-up menu displays the selectionsactive and inactive.

Restricted clear channel (Required field) [8 chars, default = inactive]

Input to this field is allowed only when Rate adaption is inactive and the Data rate is aninteger multiple of 64 kbps. It configures the channel to be a restricted clear channel if setto active. If active, the channel is treated as meeting the minimum 1’s densityrequirements and will not require additional bandwidth within its channel group. Ifinactive, the channel is treated as not meeting the minimum 1’s density requirements andadditional bandwidth may be required. A pop-up menu provides the selections active andinactive.

Change Channel Configuration Synchronous Channel Input Form, Page 6

This form is Page 6 for synchronous channels. The RTS Delay field only appears for enhancedsynchronous channels. Enhanced synchronous channels are channels for which the front channelcard is the 84-4340 and the rear card is the 84-4341X.

The Non-network compatible field only appears for synchronous/enhanced synchronous channelswith data rates of 56 kbps, where Rate Adaption has been set inactive.


RTS/DCD, BO/RI, DRS/DSR, and DTR/CTS (Required fields) [10 chars, no default]

These fields are used to set the options for the mapped pairs of control signal leads. Bothendpoints must match for all of the leads. For each pair of leads, a pop-up menu displaysthe following selections.

• in-band – The control signal lead will be transmitted with the channel group.This requires an extra 400 bps to 64 kbps of channel group bandwidth per lead.The amount is set in the In-band speed field at the bottom of the form. Thisoption is not in the menu for the DRS/DSR lead, when the 2 channel endpointsare both at 740/741 nodes.


2-40 August 1994 6800-A2-GB32-10

• background – The control signal lead will be transmitted in the background viathe SDL. No extra channel group bandwidth is necessary since the leads are sentin time Slot 1 with the SDL.

• active – The local output control signal will be forced active.

• inactive – The local output control signal will be forced inactive.

Local RTS/CTS delay [8 chars, no default]

This field specifies the length of the propagation delay between the RTS and CTS leadson a synchronous data channel. This field is not applicable when an option has beenselected for DTR/CTS and will not be displayed in this case. For synchronous channels, apop-up menu displays the selections 0-msec, 28-msec, 65-msec, 101-msec, 138-msec,and inactive. For enhanced synchronous channels, there is no pop-up menu. The integervalues from 0 to 255 and the character string inactive are the permitted entries.

In-band speed [7 chars, no default]

This field only appears on the form if in-band was selected for the control signal leads. Itconfigures the amount of bandwidth necessary to accommodate those leads. Data ratesfrom 400 bps to 64 kbps are permitted, always rounded to the nearest multiple of 400. Anexception exists for 74x-56K node channels, where the maximum is 32 kbps.

RTS delay (Required field) [9 chars, default = automatic]

This field only appears on the form for enhanced synchronous channel types. It specifiesthe length of the active-to-inactive transition delay of the RTS signal. Integer values from0 to 255 milliseconds are entered, or the keyword automatic, to have the delayautomatically calculated to the maximum possible throughput delay for the given datarate.

Change Channel Configuration Asynchronous Channel Input Form, Page 4

This form is only shown for asynchronous channels. The Data rate field does not appear on thisform for time-of-day asynchronous channels.


INPUT OUTPUT

This display-only field shows the remote channel endpoint and the local channelendpoint, in the format NxxxCyyy where xxx is the node number and yyy is the channelnumber.

Data rate (Required field) [8 chars, no default]

Specifies the data rate for the channel. A pop-up menu displays the selections 300bps,1200bps, 2400bps, 4800bps, 9600bps, and 19200bps. Both endpoints must match.


2-416800-A2-GB32-10 August 1994

RTS/DCD, BO/RI, DRS/DSR (Required fields) [10 chars, no default]and DTR/CTS (Not required)

These fields are used to set the options for the mapped pairs of control signal leads. Bothendpoints must match for all of the leads. For each pair of leads, a pop-up menu displaysthe following selections.

• in-band – The control signal lead will be transmitted with the channel group.This will require an extra 400 bps to 64 kbps of channel group bandwidth perlead. The amount is set in the In-band speed field at the bottom of the form.This option is not in the menu for the DRS/DSR lead, when the 2 channelendpoints are both at 740/741 nodes.

• background – The control signal lead will be transmitted in the background viathe SDL. No extra channel group bandwidth is necessary since the leads are sentin time Slot 1 with the SDL.



Local RTS/CTS delay [8 chars, no default]

This field specifies the length of the propagation delay between the RTS and CTS leadson a synchronous data channel. This field is not applicable when an option has beenselected for DTR/CTS and will not be displayed in this case. A pop-up menu displays theselections 0-msec, 28-msec, 65-msec, 101-msec, 138-msec, inactive.

In-band speed [7 chars, no default]

This field only appears on the form if in-band was selected for the control signal leads. Itconfigures the amount of bandwidth necessary to accommodate those leads. Data ratesfrom 400 bps to 64 kbps are permitted, always rounded to the nearest multiple of 400. Anexception is for 74x-56K nodes, where the maximum is 32 kbps.

Information/Stop bits (Required fields) [3 chars, no default]

Sets the number of information bits and stop bits for each character. The data is entered inthe format X/Y, where X is the number of information bits (data plus parity) and Y is thenumber of stop bits. A pop-up menu displays the selections 7/2, 8/1, 8/2, 9/1, 9/2. Bothendpoints must match.

Change Channel Configuration Input Form, DS0 Channel, Page 5

This form is Page 5 of the input forms, when configuring a DS0 channel.


Data rate

This display-only field always displays the value 64000bps. For DS0 group channels, thisfield displays the number of timeslots.


2-42 August 1994 6800-A2-GB32-10

Signaling format (Required field) [13 chars, no default]

Specifies the signaling format for the channel. The channel endpoints must match. Apop-up menu displays the following selections.

• active – Signaling bits sent to external devices are forced active.

• clear-channel – No signal realignment or signal conditioning is generated duringerror or alarm states on the channel.

• inactive – Signaling bits sent to external devices are forced inactive.

• in-bandA – The DS0 channel connects to a voice channel that does not supportrobbed-bit signaling. During alarm conditions, the DS0 channel will usedstandard E&M signal conditioning (E lead active). An extra 400 bps ofbandwidth must be allocated for the A bit.

• in-bandA/B – (This item only appears for ADPCM DS0 channels). The DS0channel extracts the signaling bits from the external device and allocates 800 bpsof channel group bandwidth to transfer the signaling bits.

• robbed-bit – The A/B signaling bits (A/B/C/D for ESF) from selected frames ofexternal input will be extracted and reinserted into the aggregate link’s A/Bsignaling bits. (This entry does not appear in the pop-up menu for 74x-56Knodes.)

Trunk conditioning (Required field) [10 chars, no default]

This field only appears on input forms for ADPCM DS0 channels for which the signalingformat was in-bandA/B. A pop-up menu displays the selections E&M , FXO-loop,FXS-loop, FXO-ground, FXS-ground, ringdown, PLAR, and the hexadecimal codesfrom 00 to ff .

Time Slots

For DS0-group channels, specifies the time slots of the channel. Separate them withcommas or provide a range of channels or a combination of the two. For regular DS0channels, leave this field blank.


2-436800-A2-GB32-10 August 1994

Change Channel Configuration Input Form, DDS-dsu Channels, Page 5

This form is Page 5 of the input form, when configuring a permanent DDS-dsu channel.


Transmit clock (Required field)

Enter the source of the transmit clock. A pop-up menu displays the selections internaland external. The internal value configures the channel to generate the clock sourcefrom the channel interface module. The external value configures the channel to obtainits clocking from an external device. The channel endpoints can use different clockingsources.

Receive clock (Required field)

Enter the source of the receive clock. A pop-up menu displays the selections internal andexternal. The internal value configures the channel to generate the clock source from thechannel interface module. The external value configures the channel to obtain itsclocking from an external device. The channel endpoints can use different clockingsources.

RTS Control Signal (Required field)

Enter the RTS signal that should be monitored. A pop-up menu displays the selectionsmonitored and assumed active. If assumed active is selected, the RTS signal will appearin the active state.

Format (Required field)

Enter the type of DS0 signal needed for the channel. A pop-up menu displays theselections DS0A, DS0B base, and DS0B subrate.

Rate (Required field)

Specifies the data rate, in bps, for the DDS-ocu channels. A pop-up menu displays theselections 2400, 4800, 9600, and 19200.

The next set of input fields will differ depending on the values of the format field. See DS0A,DS0B, and DS0B subrate configuration forms.

Change Channel Configuration Input Form, DDS-ocu Channels, Page 5

This form is Page 5 of the input forms, when configuring a DDS-ocu channel.


Secondary channel (Required field)

Specifies whether a secondary channel is active for the diagnostic connection between thetwo DSUs. A pop-up menu displays provides the selections active and inactive.


2-44 August 1994 6800-A2-GB32-10

Format (Required field)

Specifies the type of DS0 signal needed for the channel. A pop-up menu displays theselections DS0A, DS0B base, DS0B subrate, SW56K, and E-SW56K.

The next set of input fields will differ depending on the value of the format field. See DS0A,DS0B, and DS0B subrate configuration forms.

Change Channel Configuration Input Form, DDS Channels Configured for DS0A Formats,Page 5

This form is Page 5 of the input form, when configuring a DDS channel with DS0A format.

The field on the Change Channel Configuration input form is as follows.


Specifies the data rate, in bps, for the DS0A signal. A pop-up menu displays theselections 2400, 4800, 9600, 56000, and 64000. The 64000 bps entry does not appear inthe menu if the channel was configured with an active secondary channel.

Change Channel Configuration Input Form, DDS Channels Configured for DS0B Format,Page 5

This form is Page 5 of the input form, when configuring a DDS channel configured for DS0Bformat.



Specifies the data rate, in bps, for the base channel. A pop-up menu displays theselections 2400, 4800, 9600, and 19200.

Number of subrate channels (Required fields)

This field specifies the number of subrate channels to be used within the DS0B time slot.The range is dependent on the subrate selected. A pop-up menu displays the selections 5,10, and 20. Use 5 when the highest subrate will be 9600 or 19200 bps. Use 10 should beused when the highest subrate will be 4800 bps, and use 20 when the highest subrate willbe 2400 bps.

Subrate channel (Required fields)

Specifies the subrate channel that is to be used within the DS0B time slot. An entry of 0disconnects the subrate channel from the base channel. A pop-up menu displays theselections 0 and 1 to 20. The channel number must be less than or equal to the number ofsubrate channels specified.


2-456800-A2-GB32-10 August 1994

Change Channel Configuration Input Form, DDS Channels Configured for DS0B SubrateFormat, Page 5

This form is Page 5 of the input form, when configuring a DDS channel configured for DS0Bsubrate format.



Specifies the data rate, in bps, for the subrate channel. A pop-up menu displays theselections 2400, 4800, 9600, and 19200.

Base channel (Required field)

Specifies the channel number that corresponds to the configured DS0B base channel. Thechannel number can be a value from 0 to 127 for 740 nodes, 0 to 39 for 741 nodes.

Subrate channel (Required field)

Specifies the subrate channel that is to be used within the DS0B time slot. An entry of 0disconnects the subrate channel from the base channel. A pop-up menu displays thenumerical selections 0 and 1 to 20.

Change Channel Configuration Input Form, DDS Channels Configured for SW56K or E-SW56KFormat, Page 5

This form is Page 5 of the input form, when configuring a DDS channel configured for SW56K orE-SW56K format.


Rate

Specifies the data rate, in bps, for the channel. The rate field is display-only and alwaysdisplays a value of 56000 bps.

Maintenance mode (Required field)

Enter whether or not to configure the maintenance mode for Switched 56K channels. Apop-up menu displays the selections required and not required. The default value forSW56K is required. The default value for E-SW56K is not required.

Change Channel Configuration Results Form

The first page of the results information indicates the overall outcome of the configuration change,and, if necessary, the outcome of any change in connection state. The succeeding pages redisplaythe input forms.


2-46 August 1994 6800-A2-GB32-10

Change Channel Group (chcg)Use the chcg command to change the parameters and configuration of a channel group. Thechannel group must be idle before any of the parameters can be changed. This will beautomatically done if the user has permission for the Break Channel Group Connection (brcgc)command. All parameters can be changed except for the channel endpoints. If the endpoints are tobe changed, the channel group must be deleted, then a new one with the proper endpoints created.

For a complete description of the Destination for results and Schedule execution fields, refer toChapter 1, Introduction. For an example of input and results forms, refer to the Create ChannelGroup (crcg) command.

Access Level: Manager:

Abbreviation: chcg

Restrictions: The channel group must be idle.

Routine: Yes

Schedule: Yes

Related Commands: Break Channel Group Connection (brcgc)Channel Group Summary (cgs)Create Channel Group (crcg)Delete Channel Group (dlcg)Display Channel Group (dscg)

Change Channel Group Input Form

The fields on the Change Channel Group input form are as follows.

Channel Group (Required field) [9 chars, no default]

Enter the name of the channel group to be changed. Only a single channel group can beentered. If the user’s channel group is not in the NMS channel group table, an AcquireChannel Group (accg) or Create Channel Group (crcg) command should be run to correctthe database before this command can be executed for that channel group.

The following forms will differ, based on the type of channel group endpoints.

Change Channel Group Input Form (56K Node), Page 1

This form is used when at least one endpoint of the channel group is a 74x-56K node.


Endpoint nodes

This is a display-only field that specifies the two endpoint nodes by node number for thechannel group. The endpoints cannot be changed with this command. The channel groupmust be deleted, then recreated with the proper endpoints.

Capacity (Required field) [9 chars, default = 54800 bps]

Specifies the current capacity of the channel group. For 74x-56K node channel groups, apop-up menu provides the selections 54800 bps, 56000 bps, 62800 bps, and 64000 bps.


2-476800-A2-GB32-10 August 1994


Displays the reconfiguration condition option for the channel group. If the user wants tochange this, a pop-up menu provides the selections permanent and time-of-day.Selecting time-of-day configures the channel group to connect/ disconnect at preset timesof the day. Additional information for the times and connection states will be requested onan additional page of the form.

Current Connection state

This display-only field specifies the current condition state for the channel group, asknown by the node. The possible values are as follows.

• connected – T1 bandwidth is allocated to the channel group.

• idle – No bandwidth is allocated to the channel group.

• disconnected – Channel group has been disconnected.

• disc-ioc – Channel group was disconnected due to an IOC failure.

• disc-tod – Channel group was disconnected due to time-of-day configurationchanges.

Requested connection state (Required field) [10 chars, default = connect]

This field specifies the state the channel group should be placed in after the successfulcompletion of the configuration change request. A pop-up menu provides the selectionsconnect or disconnect. If the user selects connect, a Make Channel Group Connection(mkcgc) request will be automatically sent to the node upon completion of theconfiguration change. If the user selects disconnect, the channel group will be left in itsdisconnected state after completion of the configuration change.

Network compatible

This field is display-only for 74x-56K node channel groups and is set to no. The 74x-56Knode channel groups are always non-network compatible.

Serial synchronous time slot (Required field) [2 chars, no default]

Specifies the time slot for the channel group if one endpoint of the channel group is a731/740/741/742 and the other endpoint is a 74x-56K node. A pop-up menu provides thenumerical selections 1 to 24. If both endpoints are 74x-56K nodes, this field does notappear.


2-48 August 1994 6800-A2-GB32-10

Change Channel Group Input Form (non-56K Node), Page 1

This form is used when neither endpoint of the channel group is a 74x-56K node.


1st choice route (Required field) [9 chars, default = automatic]

A channel group can be automatically routed through the network, or the route can bedefined by the user. This field displays the current routing type designated as the firstchoice for the route. If the user wants to change it, a pop-up menu provides the choicesautomatic and fixed. If fixed is selected, a First fixed route will have to be specified bythe user on a succeeding page of the form.

Capacity (Required field) [9 chars, no default]

This field displays the amount of bandwidth allocated to the channel group. If the userwants to change it, the capacity can be specified with the number of time slots (n ts) orwith the bandwidth in kbps (n kbps). Capacities must meet one of the following criteria.

• Must be in the format n ts where n is 1 to 24.

• Must be in the format n kbps where n is:

1. multiple of 64

2. (multiple of 64) + 32, 96 <= n <= 1504

3. (multiple of 64) + 48, 112 <= n <= 1520

4. (multiple of 64) + 56, 56 <= n <= 1528

2nd choice route (Required field) [9 chars, no default]

If the 1st choice route was fixed and the route fails, the multiplexer will attempt toreroute the channel group to the 2nd choice route. The 2nd choice can be automatic orfixed, as provided by the pop-up menu. If fixed is selected, a Second fixed route willhave to specified by the user. If automatic was selected for the 1st choice route, this fieldis display-only and shows the value none.

Priority (Required field) [6 chars, default = normal]

Specifies the routing priority for the channel group. A pop-up menu provides thefollowing selections.

• high – The channel group has the ability to preempt a low priority channel groupif it needs the bandwidth allocated to that channel group. A high priority channelgroup cannot be preempted by any other channel group.

• low – The channel group can be preempted by a high priority channel group. Alow priority channel group cannot preempt any channel group.

• normal – The channel group cannot be preempted by any other channel group,nor can it preempt any channel group.


2-496800-A2-GB32-10 August 1994

3rd choice route (Required field) [9 chars, no default]

If the 2nd choice route was fixed, and the channel group was on the 2nd choice route andfailed, the multiplexer will attempt to reroute the channel group according to the 3rdchoice route selection. A pop-up menu provides the selections automatic and none. Ifnone is specified, no re-routing, based upon failure of a fixed 2nd choice route, will beattempted. If the 1st choice route or 2nd choice route fields were set to automatic ornone, this field is display-only with the value none.


Specifies the reconfiguration condition option for the channel group. A pop-up menuprovides the selections permanent and time-of-day. Selecting time-of-day configuresthe channel group to connect/disconnect at preset times of the day. Additional informationfor the times and connection states will be requested on an additional page of the form.

Robbed bit signaling (Required field) [8 chars, no default]

Specifies whether voice channels using robbed bit signaling will be assigned to thischannel group. A pop-up menu provides the selections active and inactive. Extrabandwidth will be required for the channel group, if this field is set to active.

Trunk conditioning (Required field) [10 chars, no default]

If voice channels will be assigned to this channel group, the type of trunk conditioningused by the originating PBX must be specified. The field only appears when the Robbedbit signaling field was set to active. A pop-up menu provides the selections E&M,FXO-loop, FXS-loop, FXO-ground, FXS-ground, Ringdown, PLAR, and thehexadecimal codes from 00 to ff .

Network compatible (Required field) [3 chars, no default]

Specifies whether the channel group will be configured as network compatible.Network-compatible channel groups are exact integral multiples of DS0s. Networkcompatible channel groups may only contain the following types of channels: 64 kbpsrobbed-bit voice, 64 kbps DS0, and 56 kbps synchronous data. Several networkcompatible channels can be assigned to a network compatible channel group, but theymust all be of the same type. A pop-up menu provides the selections yes and no.

IOC reroute timer (Required field) [8 chars, default = 0]

This field specifies the IOC Reroute Integration time for the channel group. This is thetime for the node to delay before rerouting a channel group based on channel groupsynchronization loss. A pop-up menu provides the numerical selections 0 to 60 seconds,and the keyword active to disable the feature. This field will only appear on forms whereboth endpoints are feature packages 3.x.x/4.x.x nodes and for which the channel group inNOT network compatible.


2-50 August 1994 6800-A2-GB32-10

B8ZS (Required field) [3 chars, no default]

Specifies whether B8ZS coding is to be used for the channel group. If B8ZS is not used,ZCS (Zero Code Suppression) will be used, and an additional 8 kbps of overheadbandwidth will be taken up by the ZCS coding and not be available for user data. Thepop-up menu provides the selections yes and no.

This field only appears on the form when both endpoints of the channel group arepre-feature packages 3.x.x/4.x.x nodes. Otherwise, the Clear Channel attribute in theattributes section of the Channel Group’s configuration is used to configure B8ZS.


This display-only field specifies the current connection state of the channel group, asknown by the node. The possible values are as follows.





Trouble code (Required field) [15 chars, no default]

For channel groups with 74x nodal endpoints, the trouble code is used to send in the link’stime slot instead of data, should a T1 failure occur. A pop-up menu provides theselections trb , mux-out-of-sync, and the hexadecimal codes from 00 to ff .

Requested Connection state (Required field) [12 chars, default = connected]

Specifies the desired connection state for the channel group after it has been changed. Apop-up menu provides the selections connect and disconnect. If the user selects connect,the NMS will issue a Make Channel Group Connection (mkcgc) request to the node afterthe configuration change has completed.

Change Channel Group Input Form (Channel Group Reconfiguration Times), Page 2


Reconfiguration time (Required field) [5 chars, no default]

Specifies the time that the channel group should be connected or disconnected fortime-of-day operation. The time is specified in hh:mm format, military time.

Connection state (Required field) [10 chars, no default]

Specifies the connection state for the channel group at the designated reconfigurationtime. A pop-up menu provides the selections disconnect or connect.


2-516800-A2-GB32-10 August 1994

Change Channel Group Input Form (Channel Connection Reconfiguration Times),Page 2

The field on the Change Channel Group input field is as follows.

Reconfiguration time [5 chars, no default]

Specifies the reconfiguration time for channel groups that are permanently connected.This is used for time-of-day channels that are in the channel group, as specified in theChange Channel Configuration (chcc) command. The time is specified in hh:mm militarytime format.

Change Channel Group Input Form (Attribute Requests), Page 3

This form only appears for channel groups terminating on at least one feature packages 3.x.x/4.x.xnode and which are not 74x-56K channel groups.

The field on the Change Channel Group input form is as follows.

attribute request values [7 chars, default = ignore]

For each physical and logical attribute, the attribute request can be specified for thechannel group. A pop-up menu provides the following selections.

• require – The channel group can only take routes that satisfy this attribute.

• prefer – The channel group will be routed over routes that satisfy this attributebefore selecting an alternate route that may not.

• avoid – The channel group will not be routed over any path that satisfies thisattribute.

• ignore – The channel group will ignore this attribute for routing purposes.

For the Clear Channel attribute, the only values in the menu will be require and ignore.This field indicates whether the channel group must be routed over Clear Channelfacilities. If require is selected, the channel group will only be routed over ACAMI orB8ZS links. If ignore is selected the channel group will route over all types of links, butClear Channel facilities will be tried last in any automatic route selection process.

Change Channel Group Input Form (Fixed Route Selection), Page 4

This form appears if fixed was selected for the 1st choice route field. The Second fixed routefrom portion (that field and below) of the form appears if fixed was selected for the 2nd choiceroute field.


First fixed route from

This display-only field shows the beginning node in the route; that is the first endpointnode of the channel group.


2-52 August 1994 6800-A2-GB32-10

Next route element (Required field) [15 chars, no default]

This is the data-entry field for specifying the route. The user selects the next element inthe route path by entering it into this field. Once entered and accepted, this entry willappear in the Route field above it as the next item in the path. The next element is thenspecified by selecting/entering another element in this Next route element field. Routingelements can be node numbers, node names, or NIDxx to indicate foreign networks NID1through NID 50. Logical links (numbers or names) can optionally be entered onlyfollowing a node (number or name) and must be preceded by a slash (/). A pop-up menuprovides the possible selections for each next element, based on information in the facilityprofile and logical link database. Entries in the menu meet the attribute requirementsentered previously.

Route

This displays the channel group fixed route as it is built by entering items in the fielddirectly above it. Optionally, the user can edit the displayed route by typing the changes(over-writing) in the proper positions, or you can clear this field and re-enter the routesequentially from the Next route element above . The user should enter the string NIDxxto indicate the entry of the channel group route into a foreign network. The NIDxxspecifies the foreign network ID. These IDs are specified in the facility profiles for the T1links connecting the nodes to foreign networks. Nodes are entered by using their nodenumbers. Logical links must use their logical link numbers (LLnnnnn).

Second fixed route from

See First fixed route from .

Next route element

See above.

Route

See above.


2-536800-A2-GB32-10 August 1994

Change Channel Group Input Form (Pass-Through), Page 5

This form shows the fixed time slot assignment for the 1st fixed route. The 2nd fixed route formwill be similar. This form only appears when the channel group is a pass-through channel group(from a 745 endpoint to a foreign network, without using logical links). There are two sets of thesefields for each NIDxx in each fixed route and one set for each side of each NID.


Node

This display-only field shows the node number of a node adjacent to a NID in the fixedroute for the channel group.

Link

This display-only field shows the link number at the above node for a physical T1 linkconnected to a NID in the fixed route for the channel group. For 740/741 nodes, the fieldis always blank.

Time slots (Required field) [37 chars, no default]

This field specifies the fixed time slot assignment for the channel group on the above link.Time slots can be specified by separating them with commas or spaces, and using ranges.

Change Channel Group Results Form, Page 1

The Change Channel Group results forms redisplays the input forms.


2-54 August 1994 6800-A2-GB32-10

Change Channel Module Type (chcmt)Use the chcmt command to change the type of a channel to match either the installed hardwaremodule or the desired channel type. For example, when an ACCULINK 740 multiplexer is shippedfrom the factory, all of its channel modules are configured, by default, as voice modules. Once thechannel modules are properly installed, the configuration database at the node needs to be changedto match the installed modules.

NOTE

Refer to the Hardware Module Summary (hms) command for a listof the channel modules as they are equipped.

When you execute the Change Channel Module Type (chcmt) command, you can instruct the NMSto match the node configuration database to the equipped module types. Optionally, you canoverride this by setting each individual channel module configuration manually through the fieldsof this command’s form.

For a complete description of the Destination for results and Scheduled execution fields, refer toChapter 1, Introduction.


Abbreviation: chcmt

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change DS-1 Channel Module Configuration (chdcmc)Hardware Module Summary (hms)

Change Channel Module Type Input Form, Page 2

A sample Change Channel Module Type input form is shown in Figure 2-3.


2-556800-A2-GB32-10 August 1994

Figure 2-3. Change Channel Module Type Input Form, Page 2

The fields on the Change Channel Module Type input form are described as follows.


Enter the node whose channel module types are to be displayed/changed. Only a singlenode and 740, 741, 742, and 74x-56K nodes with device profiles can be entered. The usercan enter the node name, node number, or node device address (m2/number).

Change all modules to match hardware (Required field) [3 chars, default = no]

Enter whether the NMS should update the channel module types stored in the node’sconfiguration database to match the equipped channel modules. Selecting yes instructs theNMS to compare the displayed module types from the node’s database with the equippedconfigurations and update the node’s configuration database with the equipped types (asshown in the INSTALLED FRONT MODULE and INSTALLED REAR MODULEcolumn). Selecting no permits the user to set the types to any desired value in theConfigured Type column.

MAIN SHELF POS and EXPANSION SHELF POS

This display-only field shows the channel module shelf positions for each channelmodule. The label is MAIN SHELF POS for the pages displaying the channel moduleson the main shelf and EXPANSION SHELF POS for the pages displaying the channelmodules on the optional expansion shelf.

MODULE NUMBER

This display-only field shows the channel module numbers for each channel module.


2-56 August 1994 6800-A2-GB32-10

CHANNELS

This display-only field shows the range of channels for each shelf position/channelmodule.

CONFIGURED TYPE [7 chars, no default]

This field displays and sets the configured channel type stored in the node database.Selections are e-voice for expanded voice channels, lbr-voice for low bit-rate voicechannels, voice for voice channels, synch for synchronous channels, asynch forasynchronous channels, DS-0 for DS0 channels, DDS-dsu for DDS-DSU channels, andDDS-ocu for DDS-OCU channels.

HARDWARE INSTALLED FRONT

This display-only field shows the actual hardware module installed in the front of theshelf. The possible values are e-voice channel, voice channel, synch channel, asynchchannel, DS-1 channel, DDS channel, vre-voice channel, lbr-voice channel, andSW56K DDS channel.

HARDWARE INSTALLED REAR

This display-only field shows the actual hardware installed in the rear of the shelf. Thepossible values are RS-232 for RS-232 data interface modules, RS-422 forRS-422/Mil-188 data interface modules, V.35 for V.35 data interface modules, E&M Plusint. for expanded voice interface modules, E&M for E&M voice interface modules, FXSinterface for FXS interface modules, FXO interface for FX0 interface modules, DS-1channel int for DS1 channel interface modules, DDS-ocu interface for OCU data portinterface modules, unknown to indicate that a model is present on the shelf, but the CPUdoes not recognize its type, and blank to indicate that no module is present on the shelf orthe module is not communicating with the CPU.

Change Channel Module Type Results Form

The Change Channel Module Type results form is identical to the input form.


2-576800-A2-GB32-10 August 1994

Change DS-1 Channel Module Configuration (chdcmc)Use the chdcmc command to configure the DS1 channel module of a 740, 741, or 742 multiplexer.



Abbreviation: chdcmc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Display DS-1 Channel Module Configuration (dsdcmc)

If the chdcmc command is issued to change the Service state field to inactive for a node that has acurrent Service state of all active DS0 channels, a confirmer box will display prior to commandexecution warning the user that all DS0 channels on the module will become out-of-service. Theuser is then able to confirm or cancel the command transaction.

Change DS-1 Channel Module Configuration Input Form

The fields on the Change DS-1 Channel Module Configuration input form are as follows.


Enter the node whose DS1 channel module is to be changed. Only a single node and 740,741, or 742 nodes with device profiles can be entered. The user can enter the nodenumber, node name, or node device address (m2/node number).

DS-1 channel (Required field) [3 chars, no default]

Enter the DS1 channel number for the module. A pop-up menu provides a list of validDS1 channel numbers. For 740 nodes, valid DS1 channel numbers are the multiples of 8from 0 to 120. For 741 nodes, valid DS1 channel numbers are 0, 8, 16, 24, 32. For 742nodes, valid DS1 channel numbers are 0, 8, 16, 24.

Format (Required field) [3 chars, default = ESF]

Specify the desired T1 framing to be used by this module. A pop-up menu is available,providing the values D4 and ESF.

Line encoding (Required field) [4 chars, default = B8ZS]

Specify the bit stuffing or line-encoding format to be used by this module for the T1. Apop-up menu is available, providing the values B8ZS and ZCS. The user should select theappropriate encoding to match the incoming DS1 channel.

Service state (Required field) [14 chars, default = active]

Specify the service state of the module. A pop-up menu will be available, providing thevalues active and out-of-service. The user can toggle the service state of the module byselecting the appropriate state.


2-58 August 1994 6800-A2-GB32-10

Change DS-1 Channel Module Configuration Results Form

The Change DS-1 Channel Module Configuration results form redisplays the input form.


2-596800-A2-GB32-10 August 1994

Change Logical Link (chll)Use the chll command to change the configuration of an existing logical link.

The logical link and all channel groups routed over it must be idled (disconnected) before anyconfiguration changes can be made. The NMS breaks the logical link connection and all itschannel group connections automatically upon user confirmation. The user must have thenecessary permissions for the Break Logical Link Connection (brllc) and Break Channel GroupConnection (brcgc) commands for this automatic action to take place.

For a complete description of the Destination for results and Schedule execution fields, refer toChapter 1, Introduction. For an example of input and results forms, refer to the Create LogicalLink (crll) command.


Abbreviation: chll

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Break Channel Group Connection (brcgc)Break Logical Link Connection (brllc)Create Logical Link (crll)Delete Logical Link (dlll)Display Logical Link (dsll)Logical Link Summary (lls)Make Logical Link Connection (mkllc)Make Channel Group Connection (mkcgc)

Change Logical Link Input Form

The fields on the Change Logical Link input form are as follows.


Enter the node whose logical link will be changed. Only a single node and node numbersand node names for 74x nodes of feature packages 3.x.x or 4.x.x are allowed. All suchnodes must have device profiles. The user can also enter the node device address(m2/node number).

Logical link (Required field) [18 chars, no default]

Enter the logical link that will be changed. Only a single logical link can be entered, and apop-up menu is available. The pop-up menu provides the list of logical link numbers andnames that are currently in the database for the given node. Logical link numbers must beentered in the format LL nnnn, logical link names must be entered in the formatll -ccccccccccccccc.

After this page has been completed, the NMS checks the configuration of the designated logicallink by querying the designated multiplexer node. If the NMS information does not match, NMSupdates its database and informs the user that this was done.


2-60 August 1994 6800-A2-GB32-10

NMS also checks the connection state of the logical link and its channel groups. If either thelogical link is connected, or any channel groups on it are connected, a confirmer box is displayedto the user, per the following form.

Change Logical Link Input Form (Confirmer)

If there are connected channel groups on the designated logical link, or if only the logical link isconnected, a confirmer message is displayed warning the user that these channel groups and thelogical link connection will be broken if the change logical link request is executed. The user canchoose to continue, or cancel the change request. If the user cancels, no connection changes aremade.

This confirmer message is only displayed if the user has functional access permission for the BreakChannel Group Connection (brcgc) and/or Break Logical Link Connection (brllc) commands. Ifthe user does not have such permission, a permission form displays.

Change Logical Link Input Form, Page 2

This form is displayed if there was a database inconsistency between the NMS and one of theendpoints of the logical link. It informs the user that the NMS has now been synchronized.

The following pages display the current configuration of the logical link and permit the user tochange it as desired.


The fields on the Change Logical Link input form are as follows.

Logical link number

This display-only field shows the logical link number of the logical link currently beingchanged.

Logical link name [18 chars, alphanumeric only, no default]

The user may assign a name for the logical link. This name must be unique in the NMS.Logical link names must always begin with the special prefix ll- . Lowercasealphanumeric characters are allowed. The first character after the ll- must be inalphabetical order.

Node [15 chars, no default)

These fields display the nodes at each end (Endpoint 1 and Endpoint 2) of the logical link.The first endpoint is the same as the one entered on the first page and cannot be changed.The second endpoint is the node at the remote end of the logical link. The node number isdisplayed. The node can be changed by entering a new node number or node name. Onlynode names and node numbers for 74x nodes of feature packages 3.x.x or 4.x.x (exceptfor the node at the other endpoint) can be entered. All such nodes must have deviceprofiles. The user may also enter the node device address (m2/node number).


2-616800-A2-GB32-10 August 1994

Link [2 chars, no default]

The user must enter the link number for the nodes at each end (endpoint 1 and endpoint 2)of the logical link. A pop-up menu is available with the link numbers 0 to 15 for a 745node. This field does not appear on the form for a 740, 741, or 742 node and the space isleft blank.

Time slots [44 chars, no default]

The user must identify the time slots to be used for the logical link at each endpoint. Oneor more time slots can be entered separated by spaces or commas. A range of time slotscan be entered by using a hyphen (-) between two time slot numbers.

Capacity [9 chars]

This display-only field specifies the capacity for the logical link. After the user enters thetime slot values, this field is calculated and the appropriate capacity displayed, in units ofkbps.

Actual connection state

This display-only field shows the current connection state of the logical link.

Requested connection state [12 chars, default = connected]

The user can request a connection state for the logical link. A pop-up menu displays theselections connect and disconnect. If connect is selected, the NMS will automaticallyattempt a Make Logical Link Connection (mkllc) command after the configuration changehas completed. Any channel groups broken previously will not be automaticallyreconnected.

Robbed bit signaling [8 chars, no default]

This field enables and disables robbed bit signaling at both endpoints of the logical link.The field will not be shown on the form if both physical links at each endpoint are notconnected to other (i.e., connected to non-74x devices). A pop-up menu provides theselections active and inactive.


2-62 August 1994 6800-A2-GB32-10


This field displays the physical attributes for the logical link that are inherited from its physicallinks, and allows the user to configure the desired states for the logical attributes of the logical link.

For the physical attributes, the attribute number, name, and state are displayed. If two states appearfor a particular attribute, the two physical links of the logical link are in a mismatch state for theattribute.

The only input field on this form is for the state of each logical attribute (attribute numbers 7 to12). The attribute numbers and names are display-only and are retrieved from the database, asdefined by the Change Node Configuration Parameters (chncp) command. For each logicalattribute state, a pop-up menu displays the selections active and inactive.

Both endpoints of the logical link will be configured with the same state.

Change Logical Link Results Form

The fields on the Change Logical Link results form are as follows:

Logical link number

The number of the logical link being changed.

Logical link name

The name of the logical link being changed.

Endpoint 1 node


Endpoint 2 node


The remaining results pages are identical to the input form displays (Pages 3–5). For a list ofpossible messages, refer to the Break Logical Link Connection (brllc) command.


2-636800-A2-GB32-10 August 1994

Change Multiplexer Component Configuration (chmcc)Use the chmcc command to set the service state of the CPU(s) in a 740, 741, or 74x-56Kmultiplexer and indicate if an expansion shelf is configured. For 745 nodes, the service state of theCPU(s) and TSI modules can be set and the clock source parameters can be configured.



Abbreviation: chmcc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Display Multiplexer Component Configuration (dsmcc)

Change Multiplexer Component Configuration Input Form, Page 1

The field on the Change Multiplexer Component Configuration input form is as follows.


Enter the node identity. Only a single node and 74x and 74x-56K nodes with deviceprofiles can be entered. Enter the node name, node number, or node address (m2/nodenumber).

Change Multiplexer Component Configuration (740, 741, 74x-56K) Input Form

The fields on the Change Multiplexer Component Configuration input form are as follows.

CPU 0 assignment (Required field) [14 chars, default = active]

This field sets the service state of CPU 0. A pop-up menu is available with the selectionsactive, standby, and out-of-service. The active value configures CPU 0 as the activeprocessor for the node. If the service state is changed from one of the other states toactive, the node verifies the operation of the CPU before making it active. If it is notsuccessful, an error message appears. The standby value configures CPU 0 as ready totake over operation from CPU 1 should CPU 1 fail. If the service state is changed fromthe out-of-service state to standby, the node verifies the operation of the CPU beforemaking it standby. If not successful, an error message appears. The out-of-service valuetakes the CPU out-of-service, enabling the diagnostics test Control Processor Test (cpt) tobe run.

CPU 1 assignment (Required field) [14 chars, no default]

This field sets the service state of CPU 1. This field does not appear for non-redundantchassis nodes. A pop-up menu is available with the selections active, standby, andout-of-service, with the same meanings as for the CPU 0 assignment field. If the CPU 1module is not installed, the value not equipped is displayed, and the field is display-only.


2-64 August 1994 6800-A2-GB32-10

Expansion shelf (Required field) [7 chars, no default]

This field configures the node for an expansion shelf. A pop-up menu is available with theselections present and absent. The present value is used to configure the node for anexpansion shelf. The absent value is used to indicate the lack of an expansion shelf.

Clock [10 chars, no default]

This field indicates the source of clocking for the node. A pop-up menu displays thefollowing selections.

Internal.

Clocking is provided by an internal oscillator.

External

Clocking is provided by an external device connected to the external clockconnector on the aggregate link module.

Derived

Clocking is derived from the aggregate link.

Facility

Clocking is derived from the V.35 interface on the 74x-56K node.

NOTE

External and Derived are not valid choices for 74x-56K nodes.

Change Multiplexer Component Configuration (745) Input Form, Page 1


CPU 0 assignment (Required field) [14 chars, default = active]

See CPU 0 assignment above.

CPU 1 assignment (Required field) [14 chars, no default]

This field sets the service state of CPU 1. A pop-up menu is available with the selectionsactive, standby, and out-of-service. The active value configures CPU 0 as the activeprocessor for the node. The field is display-only and shows the value not equipped if theredundant CPU module is not installed.


2-656800-A2-GB32-10 August 1994

TSI 0 assignment (Required field) [14 chars, default = active]

This field sets the service state of TSI module 0. A pop-up menu is available with theselections active, standby, and out-of-service. The active value configures TSI module 0as the active module for TSI switching. If the service state is changed from one of theother states to active, the node verifies the operation of the module before making itactive. If successful, the service state is switched to active. If it is not successful, an errormessage appears. The standby value configures the TSI module 0 as ready to take overoperation from TSI module 1 should TSI module 1 fail. If the service state is changedfrom the out-of-service state to standby, the node verifies the operation of the TSImodule before making it standby. If not successful, an error message appears. Theout-of-service value takes the TSI module out-of-service, enabling the diagnostic test TSIModule Test (tsimt) to be run on it.

TSI 1 assignment (Required field) [14 chars, no default]

See TSI 0 assignment above.

Change Multiplexer Component Configuration (745) Input Form, Page 2


TSI clock (Required field) [8 chars, no default]

This field is used to define the type of clock used by the TSI. A pop-up menu is displayedwith the following selections.

• internal – The clock source is an internal oscillator.

• external – The clock source is an external device attached to the clock connectoron the external clock interface module.

• derived – The clock is derived from the incoming T1 bit stream.

External clock source (Required field) [5 chars, no default]

This field is used to specify the source of the external clock, if external was the selectionfor the TSI clock field. A pop-up menu is displayed with the following selections.

• Ref 0 – The external clock source is an external bipolar interface clock.

• Ref 1 – The external clock is an external bipolar interface clock with a backup.

• Ref 2 – The external clock is an external RS-422/V.35 interface clock source.

Ref 2 speed (Required field) [10 chars, no default]

This field is used to specify the speed of the RS-422/V.35 interface clock source if thatsource was specified as an external clock source in the External clock source field. Itdoes not appear on the form otherwise. A pop-up menu is available with the selections2.048 Mbps, 1.544 Mbps, 64 Kbps, 56 Kbps.


2-66 August 1994 6800-A2-GB32-10

Primary DS-1 module (Required field) [3 chars, no default]

This field is used to specify the speed of the DS1 module number used as the primaryclock source if the clock source is derived. A pop-up menu is displayed with selectionsfor the possible DS1 module numbers 0 to 15. This field only appears on the form ifderived was the selected TSI clock source.

Fallback 1 DS-1 module (Required field) [3 chars, no default]

This field is used to specify the DS1 module number as the first backup if the primarymodule fails. A pop-up menu is available with selections for the possible DS1 modulenumbers 0 to 15. This field only appears on the form if derived was the selected TSIclock source.

Fallback 2 DS-1 module (Required field) [3 chars, no default]

This field is used to specify the DS1 module number used as the second backup if the firstfallback and the primary module fail. A pop-up menu is available with selections for thepossible DS1 module numbers 0 to 15. This field only appears on the form if derived wasthe selected TSI clock source.


2-676800-A2-GB32-10 August 1994

Change Network Administration Port Configuration (chnapc)Use the chnapc command to configure the Network Administration Ports (NAPs) on themultiplexers. The NAPs can be configured for supervisory, event log printer, or SDL use.

Changes to the NAP configuration (between SDL and non-SDL use) may require that routingtables and/or facility profiles be updated. These updates are done with the Change Routing Table (chrt) or Generate Routing Table (grt) commands and the Create Facility Profile (crfp) orEdit Facility Profile (edfp) commands.



Abbreviation: chnapc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Display NAP Configuration (dsnapc)

Change Network Administration Port Configuration Input Form, Page 1

The fields on the Change Network Administration Port Configuration input form are as follows.

Node (Required field) [15 chars, no default)

Enter a single node identity. Only 731, 74x, and 74x-56K nodes with correspondingdevice profiles can be entered. The user can enter the node name, node number, or nodedevice address (m2/node number).

NAP (Required field) [1 char, no default]

Enter the NAP that is being configured. A pop-up menu is available with the two NAPnumbers, 1 and 2.

NAP type (Required field) [17 chars, no default]

After the NAP number has been entered, this field appears with the current configurationtype of the designated type. If the user wishes to change the type, a pop-up menu displaysthe following.

• supervisory – The NAP is connected to a terminal or to an external systems porton the 6800 Series NMS (for cut-through from the NMS to the multiplexerterminal interface).

• event log printer – The NAP is connected to a printer for the logging of eventlog messages.

• SDL – The NAP is configured as a gateway to a synchronous data link (to thenode itself) or to another node so that it can be used to provide SDL connectivity.When the NAP is configured as an SDL NAP, it is referred to as either SDL 101(NAP 1) or SDL 102 (NAP 2).


2-68 August 1994 6800-A2-GB32-10

Change Network Administration Port Configuration Input Form (Supervisory/Event Log),Page 1


Baud rate (Required field) [9 chars, default = 9600 bps]

Specifies the baud rate for the port. A pop-up menu provides the selections: 50 bps, 75 bps, 110 bps, 134.5 bps, 150 bps, 200 bps, 300 bps, 600 bps, 1200 bps, 1800 bps,2400 bps, 4800 bps, 9600 bps, and auto. The auto choice configures the port toautomatically adapt to input rates of 300, 1200, 2400, 4800, or 9600 bps.

Flow control (Required field) [8 chars, default = XON/XOFF]

Configure the flow control options on the NAP. A pop-up menu displays the following.

• XON/XOFF – The transmit-on and transmit-off characters are used for flowcontrol.

• CTS/DTR – The node drops the CTS (clear-to-send) signal to stop datatransmission from the terminal/NMS. The terminal/NMS drops the DTR(data-terminal-ready) signal to stop the data transmission from the node.

• none – The node does not respond to or invoke flow control on the NAP.

Change Network Administration Port Configuration Input Form (Supervisory/Event Log),Page 2


Modem controls (Required field) [17 chars, no default]

Specify how the asynchronous NAP should treat its modem control signals. A pop-upmenu displays the following selections.

• DCE-local – The modem controls are processed locally; no end-to-end signalmapping is required. The NAP is considered active when the DTR or RTS signalis active. This is the recommended connection method.

• DCE-assume-active – The NAP is assumed to be active at all times. Only theTD, RD, and SG leads need to be connected. This entry is not permitted if autowas selected for the Baud rate.

• DIM/DOM – Stands for dial-in/dial-out modem. This control allows incomingcalls to be answered and outgoing calls to be placed. The node performs the localhandshake with the attached modem.

• DIM/DOM-secure – This control helps to prevent unauthorized access to thenetwork by using the DIM/DOM control and causing the modem to go on-hookfor all disconnects.

Parity (Required field) [7 chars, no default]

Defines the parity for the NAP. A pop-up menu provides the selections odd, even,ignored, and none.


2-696800-A2-GB32-10 August 1994

Number of data bits (Required field) [1 char, no default]

Defines the number of data bits, not including the parity bit. A pop-up menu provides theselections 7 and 8.

Number of stop bits (Required field) [3 chars, no default]

Defines the number of stop bits. A pop-up menu provides the selections 1, 1.5, and 2.

Change Network Administration Port Configuration Input Form (SDL), Page 1


Data rate (Required field) [9 chars, no default]

Set the speed of the NAP port. A pop-up menu displays the selections 1200 bps, 2400 bps, 4800 bps, 9600 bps, 19200 bps, 32000 bps.

Transmit clock (Required field) [8 chars, default = internal]

Defines the type of transmit clock. A pop-up menu displays the selections internal andexternal.

Receive clock (Required field) [8 chars, default = internal]

Defines the type of receive clock. A pop-up menu displays the selections internal andexternal.

Satellite (Required field) [8 chars, default = inactive]

Indicates if the SDL connection is over a satellite hop. A pop-up menu displays theselections active and inactive.

Change Network Administration Port Configuration Results Form

The Change Network Administration Port Configuration results form redisplays the input form. Inaddition, one of the following messages may appear with the following results.

This change may require running the Create Facility Profile (crfp) and GenerateRouting Table (grt) commands to update the link and routing information.

This message appears if the NAP was reconfigured to/from an SDL type, and there is no existingfacility profile for the NAP endpoint.

The facility profile for fac-ccccccccccccccc indicates that NAP n is configured for afacility type of type. Check the profile and update if necessary.

This message appears if the NAP was changed from a non-SDL configuration to an SDLconfiguration, and the facility profile indicates it is a non-SDL NAP.

The facility profile for fac-ccccccccccccccc indicates that NAP nnn is configured fora facility type of SDL. Check the profile and update it if necessary.

This message appears if the NAP was changed from an SDL configuration to a non-SDLconfiguration, and the facility profile indicates it is an SDL NAP.


2-70 August 1994 6800-A2-GB32-10

Change Node Configuration Parameters (chncp)Use the chncp command to configure node parameters for one or more nodes. The parameters thatcan be configured are as follows.

• Node date/time

• Performance data reporting

• Event logs

• Message logs

• Alarm severity reporting

• Attribute names

You normally execute this command after installing or initializing your ACCULINK multiplexernetwork or nodes in the network. You also execute this command if you changed the event nodefor the NMS with the Change Node Connected to System (chncs) command, to configure the eventlog 2 destination for all nodes to the newly changed node connected to the NMS.



Abbreviation: chncpAlternates: chpdr, incp, chmlc, chasrc, chelprc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change Node Connected to System (chncs)Display Node Configuration Parameters (dsncp)

Change Node Configuration Parameters Input Form, Page 1

The fields on the Change Node Configuration Parameters input form are as follows.


Enter the appropriate nodes to change configuration parameters. Multiple nodes can beentered, separated by commas or spaces. You can enter the keyword all to signify allnodes. Specify nodes by using the device name, device address, serial number(ser-xxxxxxxxxx) or node number. You can enter network names (netxxxxxxxxxxxxxxx),or circuit names (cir-xxxxxxxxxxxxxxxxxxxxxxxxx). You can use wildcard charactersanywhere within the node specification. The nodes must be 731, 74x, or 74x-56K nodeswith device profiles.

Depending on the user’s entries in the Node(s) field, the ensuing forms differ. Onlyparameters relevant to the selected nodes appear on the forms.


2-716800-A2-GB32-10 August 1994

Change Node Configuration Parameters Input Form, Page 1

Page 1 of the Change Node Configuration Parameters form displays the possible sets of parametersthat can be set with this command. Select yes for each of the following sets of parameters that youwish to configure for the specified node(s). Additional forms relevant to each selected set will thenbe displayed.


Set node(s) to NMS date/time (Required field) [3 chars, default = no]

Indicates whether the node’s date and time should be changed. A pop-up menu isavailable with entries yes and no. If yes is selected, the NMS date and time will bedownloaded to the node.

NOTE

When you change the Set node(s) to NMS date/time from theChange Node Configuration Parameters (chncp) command, boththe network and local date and time are reset to the time in theNMS.

Set performance reporting parameters (Required field) [3 chars, default = no]

Indicates whether you want to change the node’s performance data reporting parametersA pop-up menu is available with entries yes and no. If yes is selected, and only a singlenode is selected from the first page, a subsequent form displays the node’s currentparameters, enabling you to update and download them to the node. If multiple nodes areentered, forms with system defaults display, permitting you to change and download thesevalues to all the selected nodes. These parameters control the statistical reporting intervalsfor performance statistics, and let you reset facility performance statistics counters andother data counters.

Configure event log 1 (Required field) [3 chars, default = no]

Indicates whether you want to change the node’s event log 1 configuration. A pop-upmenu is available with entries yes and no. If yes is selected, and only a single node isselected from the first page, a subsequent form displays the node’s current parameters,enabling you to update and download them to the node. If multiple nodes are entered,forms with system defaults display, permitting you to change and download these valuesto all the selected nodes. These parameters control the destination for the first event logand which multiplexer alarms and events are sent to that destination.

Configure event log 2 (Required field)

Indicates whether you want to change the node’s event log 2 configuration. A pop-upmenu is available with entries yes and no. If yes is selected, and only a single node isselected from the first page, a subsequent form displays the node’s current parameters,enabling you to update and download them to the node. If multiple nodes are entered,forms with system defaults display, permitting you to change and download these valuesto all the selected nodes. These parameters control which multiplexer alarms and eventsare reported to the NMS via the asynchronous event reporting mechanism.


2-72 August 1994 6800-A2-GB32-10

Configure event log 3 (Required field)

Indicates whether you want to change the node’s event log 3 configuration. A pop-upmenu is available with entries yes and no. If yes is selected, and only a single node isselected from the first page, a subsequent form displays the node’s current parameters,enabling you to update and download them to the node. If multiple nodes are entered,forms with system defaults display, permitting you to change and download these valuesto all the selected nodes. The third event log configuration allows you to specify thedestination for this log and to indicate which multiplexer alarms and events are to be sentto this destination. This entry is only applicable to nodes of feature packages 3.x.x/4.x.x.

Configure message log (Required field)

Indicates whether you want to change the node’s message log configuration. A pop-upmenu is available with entries yes and no. If yes is selected, and only a single node isselected from the first page, a subsequent form displays the node’s current parameters,enabling to update and download them to the node. If multiple nodes are entered, formswith system defaults display, permitting you to change and download these values to allthe selected nodes. These parameters control the storage and display of messages in thenode’s message log. You can only access these messages from the node’s terminalinterface.

Configure alarm severity reporting (Required field)

Indicates whether you want to change the node’s alarm severity reporting configuration.A pop-up selection menu is available with entries yes and no. If yes is selected, and only asingle node is selected from the first page, a subsequent form display the node’s currentparameters, enabling you to update and download them to the node. If multiple nodes areentered, forms with system defaults display, permitting you to change and download thesevalues to all the selected nodes. These parameters control the alarm relays that activate themajor/minor LEDs on the node’s front bezels and the relays that active the audible alarmon the node. This entry is not applicable to nodes with 741 chassis.

Configure attribute names (Required field)

Indicates whether you want to download the current NMS attribute names to the selectednode(s). A pop-up menu is available with entries yes and no. If yes is selected, and only asingle node is selected from the first page, a subsequent form displays to show the currentattribute names defined at the node, and the names defined at the NMS. You can thendownload the NMS names to the node. If multiple nodes are selected, the names definedat the NMS display and you can choose to download them to the selected nodes. Thisentry is only applicable to nodes of feature packages 3.x.x/4.x.x.

NOTE

You can only change the NMS attribute names if you selected all forthe Node(s) field. You can then select yes in this field and downloadthe changed name(s) to all nodes, if desired.


2-736800-A2-GB32-10 August 1994

Change Node Configuration Parameters Performance DataReporting (Multiple Nodes) Input Form

The fields on the Change Node Configuration Parameters Performance Data Reporting input formare as follows.

Data report and reset interval (Required field) [5 chars, default = 00:00]

Indicates the time interval for accumulating performance statistics at a node. The statisticsregisters are reset at the end of the time interval. If the statistics are being reported, theyare sent as events at the end of each time interval. Values are entered in the formathh:mm, where hh is 0 to 23 and represents hours, and mm is 00 to 59 and representsminutes. The minimum interval is 10 minutes.

Reset facility performance data registers (Required field) [3 chars, default = no]

Indicates whether the facility performance data registers are reset when this command isexecuted. A pop-up menu is available with the entries yes and no. If yes is selected, theregisters for facility performance statistics are reset. The facility performance statistics arethe ones reported by the Facility Performance Report (fpr) and Time Slot PerformanceReport (tspr) commands.

Reset other data registers (Required field) [3 chars, default = no]

Indicates whether the data registers (other than the facility performance statistics) arereset when this command is executed. A pop-up menu is available with the entries yes andno. If yes is selected, these registers are reset. These statistics are the ones reported by theChannel Group Performance Report (cgpr), Facility Errors Report (fer), Node ErrorsReport (ner), and Equipment Performance Report (epr) commands.

There are three forms used to configure event logs 1, 2, and 3. They are all similar in display andcontent and are described below.

Event log node (Required field) (event logs 1 or 3)

For event log1 or 3, indicate the node number or name of the multiplexer to which aterminal or event log printer is connected for the display/printing of the events. Enter onlya single node. Only node numbers or node names for 731, 74x, 74x-56K, and 719 nodeswith corresponding device profiles can be entered. The user can also enter the nodedevice address (m2/node number).

Group (Required field) (event logs 1 or 3)

Enter the NAP (Network Administration Port) number for the port number to which aterminal or printer is connected, and which is configured as an event log printer NAPtype, for the display/printing of the events. For 719 nodes, the group number for the portshould be entered, since 719 nodes do not have NAPs. A pop-up menu is available withthe entries 1 and 2 for 731, 74x, and 74x-56K nodes, and the numerical entries 0 to 63 for719 nodes.


2-74 August 1994 6800-A2-GB32-10

Node connected to system (event log 2 only)

This display-only field shows the node number of the multiplexer whose NAP port isconfigured as event datagram and connected to the mux event port on the 6800 SeriesNMS. This connection was configured through the terminal information of themultiplexer and through the Change Node Connected to System (chncs) command.

Group (event log 2 only)

This display-only fields shows the NAP number of the NAP configured as eventdatagram and connected to the mux event port on the 6800 Series NMS from the nodeindicated in the previous field. If the node was a 719/72x NETWORKER, this Group isthe 719/72x NETWORKER’s group number (since the 719/72x does not have a NetworkAdministration Port).

NOTE

In the descriptions below, event log destination refers to the NMSwhen you are configuring event log 2, and to the event logdestination when you are configuring either event log 1 or 3.

Configuration status (Required field) [8 chars, default = active]

Shows whether configuration status alarms and events should be sent to the event logdestination via the asynchronous event reporting mechanism. A pop-up menu provides theselections active and inactive. Selecting active sends these alarms and events to the eventlog destination.

Facility alarms (Required field) [8 chars, default = active]

Shows whether facility alarms and events should be sent to the event log destination viathe asynchronous event reporting mechanism. A pop-up menu provides the selectionsactive and inactive. Selecting active sends these alarms and events to the event logdestination. If you selected inactive for event log 2 here, you will be asked to confirmyour selection, since this category of alarms represents serious network problems thatshould be reported to the NMS.

Node alarms (Required field) [8 chars, default = active]

Shows whether node alarms and events should be sent to the event log destination via theasynchronous event reporting mechanism. A pop-up menu provides the selections activeand inactive. Selecting active sends these alarms and events to the event log destination.If you selected inactive for event log 2 here, you will be asked to confirm your selection,since this category of alarms represents serious network problems that should be reportedto the NMS.

Node errors (Required field) [8 chars, default = active]

Shows whether node error alarms and events should be sent to the event log destinationvia the asynchronous event reporting mechanism. A pop-up menu provides the selectionsactive and inactive. Selecting active sends these alarms and events to the event logdestination.


2-756800-A2-GB32-10 August 1994

System status (Required field) [8 chars, default = active]

Shows whether system status alarms and events should be sent to the event log destinationvia the asynchronous event reporting mechanism. A pop-up menu displays the selectionsactive and inactive. Selecting active sends these alarms and events to the event logdestination.

Statistics (Required field) [8 chars, default = inactive]

Shows whether statistics events should be sent to the event log destination via theasynchronous event reporting mechanism. A pop-up menu provides the selections activeand inactive. Selecting active send these events to the event log destination.

Network call status (Required field) [8 chars, default = active]

Shows whether network call status alarms and events should be sent to the event logdestination via the asynchronous event reporting mechanism. A pop-up menu provides theselections active and inactive. Selecting active sends these alarms and events to the eventlog destination.

Channel group accounting (Required field) [8 chars, default = active]

Shows whether channel group accounting events should be sent to the event logdestination via the asynchronous event reporting mechanism. A pop-up menu provides theselections active and inactive. Selecting active sends these events to the event logdestination.

Change Node Configuration Parameters Message Log Parameters Input Form, Page 5

The fields on the Change Node Configuration Parameters Message Log Parameters input form areas follows.

Message display (Required field) [10 chars, default = once]

Shows whether or not the messages in the node(s) message log should be deleted as youread them, or only when the log reaches capacity. A pop-up menu displays the selectionsonce and persistent. Selecting once configures the node to delete each message as it isread.

Configuration status (Required field) [8 chars, default = active]

Shows whether configuration status alarms and events should be sent to the node’smessage log. A pop-up menu displays the selections active and inactive. Selecting activestores these alarms and events in the node’s message log.

Facility alarms (Required field) [98 chars, default = active]

Shows whether facility alarms and events should be sent to the node’s message log. Apop-up menu displays the selections active and inactive. Selecting active stores thesealarms and events in the node’s message log.


2-76 August 1994 6800-A2-GB32-10

Node alarms (Required field) [8 chars, default = active]

Shows whether node alarms and events should be sent to the node’s message log. Apop-up menu displays the selections active and inactive. Selecting active stores thesealarms and events in the node’s message log.

Node errors (Required field) [8 chars, default = active]

Shows whether node error alarms and events should be sent to the node’s message log. Apop-up menu displays the selections active and inactive. Selecting active stores thesealarms and events in the node’s message log.

System status (Required field) [8 chars, default = active]

Shows whether system status alarms and events should be sent to the node’s message log.A pop-up menu displays the selections active and inactive. Selecting active stores thesealarms and events in the node’s message log.

Statistics (Required field) [8 chars, default = active]

Shows whether statistics events should be sent to the node’s message log. A pop-up menuprovides the selections active and inactive. Selecting active stores these events in thenode’s message log.

Network call status (Required field) [8 chars, default = active]

Shows whether network call status alarms and events should be sent to the node’smessage log. A pop-up menu displays the selections active and inactive. Selecting activestores these alarms and events in the node’s message log.

Channel group accounting (Required field) [8 chars, default = active]

Shows whether channel group accounting events should be sent to the node’s messagelog. A pop-up menu displays the selections active and inactive. Selecting active storesthese alarms in the node’s message log.


2-776800-A2-GB32-10 August 1994

Change Node Configuration Parameters Alarm Severity Reporting Input Form, Page 6

A series of alarm severity reporting parameters will appear. For all the fields in these forms, apop-up menu displays the following selections.

• audible – Enable only the audible alarm at the multiplexer for this class of alarms.

• major – Enable only the Major Alarm LEDs and rear-panel relays at the multiplexer for thisclass of alarms.

• minor – Enable only the Minor Alarm LEDs and rear-panel relays at the multiplexer for thisclass of alarms.

• audible,major – Enable both the audible alarm and the Major Alarm LEDs (Minor AlarmLEDs are disabled).

• audible,minor – Enable both the audible alarm and the Minor Alarm LEDs (Major AlarmLEDs are disabled).

• major,minor – Enable both the Major and Minor Alarm LEDs (Audible alarm is disabled).

• audible,major,minor – Enable the audible alarm and the Major and Minor Alarm LEDs.

• none – Do not enable any alarm at the multiplexer.

• The error message returned for all of these fields is:

Please choose one of: audible, major, minor, audible,major, audible,minor,major,minor , audible,major,minor, none

Active link out-of-service (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate anout-of-service condition for the active T1 link.

Active link maintenance (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate amaintenance-level condition for the active T1 link.

Standby link out-of-service (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate anout-of-service condition for the standby T1 link.

Standby link maintenance (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate amaintenance-level condition for the standby T1 link.

DS-1 interface channel out-of-service (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate anout-of-service condition for a DS1 Channel Interface module on a 740, 741, or 742.

DS-1 interface channel maintenance (Required field) [19 chars. default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate amaintenance-level condition for a DS1 Channel Interface module on a 740, 741, or 742.


2-78 August 1994 6800-A2-GB32-10

Channel group out-of-service (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate aloss of channel group synchronization at a 740, 741, or 742 node.

Serial synchronous framing loss (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate aloss of synchronization in 740, 741, or 742 time slots that are terminating at 74x-56Knodes.

Active link hardware (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate anout-of-service condition for the 56K aggregate link on a 74x-56K node.

Active link loss of signal (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate aDCD or carrier loss on the 56K aggregate link on a 74x-56K node.

Active link DSU disconnect (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate thatthe DSU is not connected on the 56K aggregate link because DSR is not being received ata 74x-56K node.

Active link framing loss (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate aloss of synchronization with the 74x-56K’s remote node.

Standby link hardware (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate anout-of-service condition for the standby 56K aggregate link on a 74x-56K node.

Standby link loss of signal (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate aDCD or carrier loss on the standby 56K aggregate link on a 74x-56K node.

Standby link DSU disconnect (Required field) [19 chars, default = major]

Select the combination of alarm reporting methods at the multiplexer node to indicate thatthe DSU is not connected on the 56K standby link because DSR is not being received by a74x-56K node.


2-796800-A2-GB32-10 August 1994

For each field, the following node alarm selections are available in a pop-up menu.

Control processor module failure (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate afailure of the control processor.

Power module failure (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate thefailure of a power module.

SDL timeout (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate thefailure of an SDL connection.

Channel group routing failure (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate thefailure of a channel group to route.

Logical link configuration mismatch (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate amismatch at the logical link configuration at a node and the one at the other end of thelogical link.

Aggregate link module failure (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate thefailure of the aggregate link module at a 731, 740, 741, 742 or 74x-56K node.

Aggregate T1 link loss of clock (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate aloss of clock on the 740 aggregate link.

Aggregate (56K) link loss of transmit clock (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate aloss of transmit clock on a 74x-56K node’s aggregate link.

Aggregate (56K) link loss of receive clock (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate aloss of receive clock on the 74x-56K node’s aggregate link.

Channel module failure (Required field) [19 chars, default = minor]

Selects the combination of alarm reporting methods at the multiplexer node to indicate thefailure of a channel module on the 731, 740, 741, 742 or a 74x-56K node.


2-80 August 1994 6800-A2-GB32-10

TSI module failure (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate thefailure of a TSI module at a 745 node.

TSI clock out-of-limits (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate anout-of-limits condition with a TSI clock at a 745 node.

TSI clock out-of-range (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate anout-of-range condition with a TSI clock at a 745 node.

Single TSI clock reference failure (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate thefailure of a single TSI clock reference at a 745 node.

All TSI clock reference failure (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate thefailure of all the TSI clock references at the 745 node.

DS-1 module failure (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate thefailure of a DS1 module at a 745 node.

PC Bus Failure (Required field) [19 chars, default = minor]

Select the combination of alarm reporting methods at the multiplexer node to indicate thefailure of the PC bus at a 745 node.

Change Node Configuration Parameters Attribute Names (Single Nodes), Page 8

This form displays when the Configure attribute names item was selected from the first page ofthe command.

The 6800 Series NMS requires that the set of 12 attribute names be consistently defined across allnodes in the network. This ensures consistent use of the names for channel group routing. Thisform shows the NMS values for the six physical and six logical attributes.

When a single node was selected for the command, NMS checks the values of the names at thegiven node. If any names are inconsistent with those at the node, they are so indicated on this form,as above for attributes 1 and 6, where attribute 1 has the name attr1cccc in NMS and diff1xxxx atthe node, and attribute 6 has the name attr6cccc in NMS and diff6xxxx at the node with ** to theleft and right of the inconsistent name.

If multiple nodes (but not all) were selected for this command and you choose yes for theDownload to node(s) option on this form, NMS checks for inconsistent names at the given nodesand downloads the database-known names shown above to those nodes to correct theinconsistencies when this command executes.


2-816800-A2-GB32-10 August 1994

If you selected all for the Node(s) field on the first page of this command, you can edit theattribute names appearing on this form. For each of the 12 attributes, the user may enter a 1- to9-character name for the attribute. Names can consist of the lowercase alphabetic characters andthe numbers 0 to 9, but must begin with a letter. The 12 names must be unique. The default foreach attribute is attrn where n is the attribute number.


Download to nodes (Required field)

When the command is executed, you can request that the node be updated to match theNMS for the names. However, note that the NMS must break any channel groupconnections that are using the attributes that will be changed before the nodes will acceptthe download request. The user will be required to have permission for the Break ChannelGroup Connection (brcgc) command and confirm the channel group break.

You cannot change the NMS values for attribute names unless you selected all nodes forthe chncp command. You must select all nodes to change a name, as the change must bedownloaded to all nodes.

The user must request the attributes to be downloaded by specifying yes in this field.Having this option permits the user to view the attribute names without requiring a changeto be made. This field accepts the values yes and no.

Update request (Required field) (Only if all nodes is selected)

If desired, the attribute names can be changed only in the NMS database and notdownloaded to all nodes in the network. This option should be selected if the user is notgoing to configure and use attribute routing from the terminal interface of the nodes. Apop-up menu displays the selections database only, network, and no change. Ifdatabase only is selected, no effect is made to currently connected channel groups. Ifnetwork is selected, the necessary channel groups are disconnected and the new namesdownloaded to the specified nodes. If no change is selected, neither the database nor thenodes is updated.

Change Node Configuration Parameters Results Form

The first page of the Change Node Configuration Parameters results form displays the node(s)selected for the command and an overall results summary. The overall results summary indicateshow many nodes were in the selection request and how many nodes successfully sent theconfiguration changes. If a node did not successfully receive the changes, a detailed description ofthe failure is added. If attribute names were downloaded to nodes, a list of channel groups that hadto be disconnected is provided. If the command was directed to a single node, a one-line messageis displayed on this page.

‘‘Configuration parameters successfully sent to node nnn”

or

‘‘Configuration parameters could not be sent to the node - Node in control access”.

The succeeding pages of the results forms redisplay the requested parameter changes, as shown onthe input forms.


2-82 August 1994 6800-A2-GB32-10

Change Node Connected To System (chncs)Use the chncs command to specify the multiplexer nodes that are directly connected to the 6800Series NMS’s multiplexer event port interface and multiplexer command port interface. Theseinterfaces are used, respectively, to transmit alarms and events asynchronously to the NMS and tosend or receive command requests and results between the NMS and the multiplexer nodes.

The node connected to the event port interface must have its NAP configured as an eventdatagram type. This can only be done through the terminal interface. See Chapter 2 of theCOMSPHERE 6800 Series Network Management System Multiplexer Management andConfiguration Guide for further information.

The node connected to the command port interface must have its NAP configured as an eventdatagram type. This can also only be done through the terminal interface. See Chapter 2 of theCOMSPHERE 6800 Series Network Management System Multiplexer Management andConfiguration Guide for further information.

The third interface between the NMS and the multiplexer network is the cut-through interface.The NMS does not need to keep a record of the node number of this multiplexer, so it is notrequested by this command.

The port configurations of the NMS for the three multiplexer network interfaces are configured atinstallation and can be viewed through the Edit Port Configuration (edpc) and Display PortConfiguration (dspc) commands.

The node connected to the event port interface is the node that is displayed in the Change NodeConfiguration Parameters (chncp) command when the user is configuring the multiplexers’ eventlog 2.



Abbreviation: chncs

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change Node Configuration Parameters (chncp)Display Node Connected to System (dsncs)Edit Port Configuration (epc)


2-836800-A2-GB32-10 August 1994

Change Node Connected to System Input Form

The fields on the Change Node Connected to System input form are as follows.

(Event Log Interface:) Node (Required field) [15 chars, no default]

Enter the node that is connected to the NMS’s event port. Only 731, 74x, 74x-56K, and719 nodes with device profiles can be entered. The user can enter the node name, nodenumber, or node device address (m2/node number).

(Event Log Interface:) Group (Required field) [2 chars, no default]

If the node above is a 74x or 74x-56K node, the Group number entered should be theNAP number of the NAP configured as an event datagram type and connected to theNMS’s event port. A pop-up menu is available with the possible NAP numbers of 1 and 2.If the node above is a 719 node, the Group number entered should be the number of thegroup that contains the 719 channel connected to the NMS’s event port. A pop-up menu isavailable with the possible group numbers of 0 to 63.

(Command Language Interface:) Node (Required field) [15 chars, no default]

Enter the node that is connected to the NMS’s command language port. only 731, 74x and74x-56K nodes with device profiles can be entered. The user can enter the node name,node number, or node device address (m2/node number).

Change Node Connected to System Results Form

The Change Node Connected to System results form redisplays the input form.


2-84 August 1994 6800-A2-GB32-10

Change Node Passwords (chnp)Use the chnp command to identify, for the NMS, the Level 1 password that has been set for all themultiplexer nodes in the network. The NMS must know this password in order to communicate(send tests/commands) to the nodes.

To set the Level 1 password at each node, you must use the terminal interface at each node. Thiscan be done via the cut-through interface at NMS, or by using an attached terminal at a node.



Abbreviation: chnp

Restrictions: None

Routine: No

Schedule: No


Change Node Passwords Input Form

The field on the Change Node Passwords input form is described as follows.

Password (Required field) [20 chars, no default]

Enter the Level 1 password, as known by all the multiplexers in the network. Thepassword is up to 20 alphanumeric characters, case-sensitive.

Change Node Passwords Results Form

The Change Node Passwords results form redisplays the input form.


2-856800-A2-GB32-10 August 1994

Change Physical Link Configuration (chplc)Use the chplc command to configure the T1 links of a 731, 74x, or 74x-56K node.

All the parameters of the link are configured with this command, including clocking, redundancy,line encoding, physical attributes, and alarm integration time.

This command also can be used to change the service state of the links and the service state of a745’s DS1 modules.

You can configure both links on a T1 facility with this command, or you can configure a singlelink at a time. The NMS will verify that the configurations of the links on each end of the T1facility are compatible. You can bypass this verification if necessary.

Under certain circumstances (applicable only when a 740 node is connected to a 745 node),execution of a chplc command to a specified node(s) will cause NMS to lose communications withthat node(s). In these situations, the system will display a confirmer box prior to commandexecution advising the user of the potential loss of communications between the node(s) and theNMS. The user then confirms the configuration activity or cancels the transaction as appropriate.



Abbreviation: chplcAlternate: chtlc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Display Physical Link Configuration (dsplc)

Change Physical Link Configuration Input Form, Page 1

The fields on the Change Physical Link Configuration input form are as follows.

Facility name (fac–) [15 chars, no default]

Enter the facility name, as found in the facility profile tables, to specify the link(s) to beconfigured. If the facility name is entered, the node and link information will bedetermined from the facility profile data. Alternatively, you can enter the node and linkinformation for one end of the facility.


Enter the node and link instead of a facility name. For the node, any 731, 74x , or74x-56K node with a device profile can be entered. The user can enter the node number,node name, or node device address (m2/node number).


2-86 August 1994 6800-A2-GB32-10

Link (Required field) [2 chars, no default]

Enter the link to be configured. A pop-up menu is available. If the node was a 731, 740,741, 742, or 74x-56K node, the field is automatically populated with the number 0, andthat is the only entry in the menu list. If the node was a 745, the menu will contain thevalues 0 to 15. Once the user enters a node and link number, the NMS will look for amatching facility profile. If one is found, the facility name will be populated (or changed)on the form.

The forms of this command will differ, based on:

• If the links are T1 or 56K/64K links.

• The feature packages of the nodes.

• The type of node to which the links are configured as connected.

• The fields that appear on the various following forms.

Change Physical Link Configuration Input Form for 74x Nodes, Page 2

A sample Change Physical Link Configuration input form for 74x nodes is shown in Figure 2-4.

Figure 2-4. Change Physical Link Configuration Input Form for 74x Nodes, Page 2


2-876800-A2-GB32-10 August 1994

The fields on the Change Physical Link Configuration input form for 74x nodes are as follows.

Connected to (Required field) [10 chars, no default]

Shows whether the link is connected to other or to a Series 700 device. A pop-up menu isavailable providing these two selections. Use other when the link is connected to aforeign network or non-series 700 node.

Link redundancy (Required field) [6 chars, default = single]

Configure the link redundancy type for the link. A pop-up menu selection is availablewith the selections dual, single and none if the link is a 745 link, and dual and single ifthe link is a 740/741/742 link.

• dual – configures the link for dual link redundancy. (For 740 nodes, two T1aggregate link modules are connected to two separate T1 lines. For 745 nodes,two DS1 modules are connected to two separate T1 lines.)

• single – For 740 nodes, single configures the link for single link redundancy(two aggregate link modules are connected to a single line) or for no redundancy(a single aggregate link module is connected to a single aggregate link). Thedifference is that for no redundancy, the user leaves the Link1 fields blank. Fortrue single link redundancy, the Link1 fields should be populated. Since 741 and742 nodes do not support single link redundancy, this is the only way toconfigure these.

• none – For 745 nodes, none configures the link for no redundancy (a single DS1module is connected to a single T1 line). This choice is not applicable/ supportedby the 731, 740, 741, and 742 nodes. Choose single in those cases.

Redundant DS-1 module [2 chars, no default]

Shows the module number of the redundant DS-1 module of a 745, if dual or single wasselected for the link redundancy field. A pop-up menu displays the numerical selections0 to 15.

Link 0 state (Required field) [14 chars, default = active]

Sets the state of aggregate link 0 on a 731, 740, 741, or 742 node. A pop-up menuprovides the following selections:

• active – Aggregate link 0 is in system operation.

• standby – Aggregate link 0 is ready to take over system operation fromaggregate link 1, if necessary.

• out-of-service – Aggregate link 0 is not in service, permitting diagnostics to berun.

If the module was not equipped, this field is display-only and shows the value notequipped.


2-88 August 1994 6800-A2-GB32-10

Primary module state (Required field) [14 chars, default = active]

Sets the state of the primary DS1 module on a 745 link. A pop-up menu provides thefollowing selections:

• active – The primary module is in system operation.

• standby – The primary module is ready to take over system operation from thestandby module, if necessary.

• out-of-service – The primary module is not in service, permitting diagnostics tobe run on it.

Link 1 state [14 chars, default = standby]

Sets the state of aggregate link 1 on a 740 node. A pop-up menu provides the followingselections:




If the module is not present, this field is display-only and shows the value not equipped.

Redundant module state [14 chars, default = standby]

Sets the state of the redundant DS-1 module on a 745 link. This field is optional if nonewas selected for the Link redundancy field. Otherwise, it is required. A pop-up menuprovides the following selections:

• active – The redundant module is in system operation.

• standby – The redundant module is ready to take over system operation from theprimary module, if necessary.

• out-of-service – The redundant module is not in service, permitting diagnosticsto be run.

Format (Required field) [3 chars, default = ESF]

Specifies the framing format of the physical link. A pop-up menu provides the selectionsD4 and ESF.

Clock (Required field) [8 chars, no default]

Sets the link’s clock source. A pop-up menu provides the following selections:

• internal – provides clock from the module’s internal oscillator.

• external – provides clock from an external device connected to the clockconnector on the aggregate link interface module.

• derived – provides clock from the incoming T1 bit stream.


2-896800-A2-GB32-10 August 1994

CRC6 state (Required field) [8 chars, default = active]

Shows whether there is error checking on the data as it passes through the 745 node.Select active or inactive.

Red alarm integration time (Required field) [3 chars, default = 2.8 secs]

Sets the number of seconds to delay before the multiplexer initiates a red alarm levelalarm for the T1 link due to loss of synchronization. This field accepts values in seconds,from 2.8 to 60.

Reroute trigger delay (Required field) [4 chars, default = 0]

Sets the number of seconds to delay before the multiplexer triggers a re-route request tochannel groups because of the failure of the T1 link. Values in the range 0 to 3600seconds are accepted. The keyword infinite can be entered to indicate that the channelgroup should never re-route because of this condition.

Change Physical Link Configuration Input Form for a 74x Node, Page 3

A sample Change Physical Link Configuration input form for a 74x node is shown in Figure 2-5.

Figure 2-5. Change Physical Link Configuration Input Form for a 74x Node, Page 3


2-90 August 1994 6800-A2-GB32-10

The fields on the Change Physical Link Configuration input form for a 74x node are as follows.

Line encoding (Required field) [5 chars, default = B8ZS]

Configures the method of bit stuffing to be used on the T1 link. A pop-up menu providesthe following selections.

• ACAMI – Alternate Channel Alternate Mark Inversion is a line-encodingscheme that permits clear channel data to be transmitted over a ZCS-coded line.

• B8ZS – Bipolar 8 Zeroes Substitution is a line-encoding scheme that allowsclear channel data to be transmitted over a T1 line.

• ZCS – Zero Code Suppression is a line-encoding scheme that uses 8 kbps ofbandwidth to force the T1 data to meet the T1 line’s 1’s density requirement.

Number of clear time slots (Required field) [2 chars, no default]

If ACAMI was selected for the Line encoding field, this field appears requiring the userto specify the number of time slots needed for the ACAMI application (clear channels). Apop-up menu is available with the numerical entries 1 to 12. There are a number ofrestrictions on this value that will be checked by the multiplexer when it receives theconfiguration change request. See the COMSPHERE 6800 Series Network ManagementSystem Multiplexer Management and Configuration Guide for further information.

Timeslots (Required field) [30 chars, no default]

For 731, 740, 741, and 742 links that carry channel groups that terminate on a 74x-56Knode, the time slots that will be used for these channel groups must be configured asserial synchronous time slots on the 731, 740, 741, or 742 link. This field specifies thelist of such time slots. The time slots are indicated by specifying individual time slots,separated by spaces or commas, or a range of time slots.

Framing loss integration (Required field) [4 chars, no default]

If the 740/741 link has time slots that are used to carry a channel group terminating at a74x-56K node, this field specifies the framing loss integration time for these 56K/64Kserial synchronous time slots. This integration time represents the amount of time thenode must have lost synchronization before the resynchronization algorithm begins.Values in the range 0.1 to 10.0 seconds are accepted.

Alarm threshold (Required field) [8 chars, no default]

If the 740/741 link has time slots that are used to carry a channel group terminating at a74x-56K node, this field specifies the framing loss alarm threshold time for these56K/64K serial synchronous time slots. This threshold time represents the time a nodemust have lost synchronization before generating a framing loss alarm. Values in therange 0.1 to 120.0 seconds are accepted. The keyword disable can be entered to disablethis alarm reporting.


2-916800-A2-GB32-10 August 1994

Change Physical Link Configuration Input Form for a 74x Node, Page 4

A sample Change Physical Link Configuration input form for a 74x node is shown in Figure 2-6.

Figure 2-6. Change Physical Link Configuration Input Form for a 74x Node, Page 4

The fields on the Change Physical Link Configuration input form for a 74x node are as follows.

PHYSICAL ATTRIBUTES (Required field)

For each of the 6 physical attributes, these fields set the attribute to active or inactive, asprovided by a pop-up menu. The Clear Channel attribute is display-only, and isdetermined by the value of the Line encoding field. A value of B8ZS will set the ClearChannel attribute to active for the T1 link. All attributes are set to inactive as a default.

Action (Required field) [13 chars, default = update]

Shows whether the link should be configured. With both links of a facility on one form,NMS validates the specified configuration to ensure that consistency, where necessary, ismaintained between the two links on the facility. In some cases, it may be desirable ornecessary to violate this validation. In these cases, it is possible to configure only one endof the facility by specifying that the other end not be updated. This is also useful if theuser is only changing the configuration of one link. To prevent the configuration frombeing sent to a link, or to turn off the validation protection between the two links, enter donot update for the appropriate link. A pop-up menu provides the two selections updateand do not update for this field.


2-92 August 1994 6800-A2-GB32-10

Change Physical Link Configuration Input Form for 74x-56K Nodes, Page 2

The fields on the Change Physical Link Configuration input form for 74x-56K nodes are asfollows:

Speed (Required field) [6 chars, no default]

Sets the speed (rate) of the aggregate link. A pop-up menu provides the selections56Kbps and 64Kbps.

Connect to (Required field) [10 chars, no default]

Shows the type of node at which the link terminates. A pop-up menu provides theselections T1/E1 and non-T1/E1.

Link Redundancy (Required field) [6 chars, no default]

Configures the link redundancy type for the link. A pop-up menu selection provides theselections dual and single.

• dual – Configures the link for dual link redundancy. (Two aggregate linkmodules are connected to two separate 56K/64K lines.)

• single – Configures the link for single link redundancy (two aggregate linkmodules are connected to a single line) or for no redundancy (a single aggregatelink module is connected to a single aggregate link). The difference is that for noredundancy, the user leaves the Link1 fields blank. For true single linkredundancy, the Link1 fields should be populated.

Link 0 state (Required field) [14 chars, default = active]

Sets the state of aggregate link 0 on a 74x-56K node. A pop-up menu provides thefollowing selections.




If the module was not equipped, this field is display-only and shows the value notequipped.

Link 1 State (Required field) [14 chars, default = standby]

Sets the state of aggregate link 1 on a 740–56K node. A pop-up menu provides thefollowing selections:




If the module is not present, this field is display-only and shows the value not equipped.


2-936800-A2-GB32-10 August 1994

Link 0 receive clock (Required field) [8 chars, no default]

Sets the receive clock source of aggregate link 0. The receive clock cannot be configuredas “facility” at both endpoints or the data does not pass error-free. For a V.35 or V.11interface type, any combination of receive and transmit clocking options at one endpointare valid. For a DSU interface type, the receive and transmit clocking options at anendpoint must match. A pop-up menu provides the following selections:

• internal – Provides clock from the module’s internal oscillator.

• facility – Provides clock from the incoming bit stream.

Link 1 receive clock (Required field) [8 chars, no default]

Sets the receive clock source of aggregate link 1. The receive clock cannot be configuredas “facility” at both endputs or the data will not pass error-free. For a V.35 or V.11interface type, any combination of receive and transmit clocking options at one endpointare valid. For a DSU interface type, the receive and transmit clocking options at anendpoint must match. A pop-up menu provides the following selections:



Link 0 transmit clock (Required field) [8 chars, no default]

Sets the transmit clock source of aggregate link 0. For a V.35 or V.11 interface type, anycombination of receive and transmit clocking options at one endpoint are valid. For aDSU interface type, the receive and transmit clocking options at an endpoint must match.A pop-up menu provides the following selections:



Link 1 transmit clock (Required field) [8 chars, no default]

Sets the transmit clock source of aggregate link 1. For a V.35 or V.11 interface type, anycombination of receive and transmit clocking options at one endpoint are valid. For aDSU interface type, the receive and transmit clocking options at an endpoint must match.A pop-up menu provides the following selections:




2-94 August 1994 6800-A2-GB32-10

Change Physical Link Configuration Input Form for 74x-56K Nodes, Page 3

The fields on the Change Physical Link Configuration input form for 74x-56K Nodes are asfollows:

Link 0 interface type (Required field) [4 chars, no default]

Sets the interface type of aggregate link 0. The configured interface type must match theinstalled hardware. A pop-up menu provides the selections V.35, V.11, DSU.

Link 1 interface type (Required field) [4 chars, no default]

Sets the interface type of aggregate link 1. The configured interface type must match theinstalled hardware. A pop-up menu provides the selections V.35, V.11, DSU.

Link 0 sealing current (Required field) [9 chars, no default]

Specifies whether or not to source sealing current to the loop for aggregate link 0. Thisfield is displayed only if the interface type is DSU. A pop-up menu provides theselections terminate, source.

Link 1 sealing current (Required field) [9 chars, no default]

Specifies whether or not to source sealing current to the loop for aggregate link 1. Thisfield is displayed only if the interface type is DSU. A pop-up menu provides theselections terminate, source.

Framing loss integration (Required field) [4 chars, no default]

Specifies the amount of time the node must have lost synchronization before theresynchronization algorithm begins. Values in the range 0.1 to 10.0 seconds in 0.1 secondincrements are accepted.

Alarm threshold (Required field) [8 chars, no default]

Specifies the time a node must have lost synchronization before generating a framing lossalarm. Values in the range 0.1 to 120.0 seconds are accepted. The keyword disable can beentered to disable this alarm reporting.

Loopback timeout (Required field) [2 chars, no default]

Sets a timeout value for menu-invoked loopbacks. After the specified time period suchloopbacks will be automatically turned off. A value of 0 disables the loopback timeoutfeature. Otherwise, values in the range 1 to 60 minutes are acceptable in 1 minuteincrements.


2-956800-A2-GB32-10 August 1994

Action (Required field) [13 chars, default = update]

Shows whether the link should be configured. With both links of a facility on one form,NMS validates the specified configuration to ensure that consistency, where necessary, ismaintained between the two links on the facility. In some cases, it may be desirable ornecessary to violate this validation. In these cases, it is possible to configure only one endof the facility by specifying that the other end not be updated. This is also useful if theuser is only changing the configuration of one link. To prevent the configuration frombeing sent to a link, or to turn off the validation protection between the two links, enter donot update for the appropriate link. A pop-up menu provides the two selections updateand do not update for this field.

Change Physical Link Configuration Results Form

The Change Physical Link Configuration results form redisplays the input forms.


2-96 August 1994 6800-A2-GB32-10

Change Routing Table (chrt)(Disruptive)

Use the chrt command to update the routing tables for one or more nodes. Routing table entriesfrom a node are uploaded to the NMS, where they can be edited, added to, or deleted. The changesare then downloaded to all desired nodes.

NOTE

You may also use the Manage Routing Table Utility to do the samefunctions provided in this command. See the COMSPHERE 6800Network Management System Multiplexer Management andConfiguration Guide.

A routing table is maintained at each multiplexer node to specify an ordered set of links or logicallinks that can be used to reach a destination node. The links specified are the next links in the routeneeded to arrive at that destination, as opposed to the entire path to reach that destination. Therouting tables are used by the nodes to determine how to route user and supervisory data.

The routing table consists of one routing table entry per specified nodal destination (up to 249) inthe network. The NMS provides the capability to generate default entries for the routing table.Each entry is a comma-delimited list of link numbers (either physical or logical). The node triesthe first link in the list when attempting to reach the given destination. If the attempt fails on thatlink, the next one tries. Link alarms are ignored during the attempts to reach a destination. That is,the node does not check first for existing alarms before attempting to use a link in the table.

Changes to routing tables can be made to:

• Change the link ordering priority within each destination entry

• Add or delete links for particular destination entries

• Add or delete destination entries

Updates to the routing tables should be made when:

• Nodes are added/deleted to/from the network

• Links or logical links are added/deleted/to/from the network

• Endpoints of links or logical links are changed

• SDL connectivity is changed within the network

• The Generate Routing Table (grt) command can also be used to create and/or change routingtables in the above situations. The difference is that the grt command automatically createsrouting tables at the specified nodes, based on NMS algorithms for link ordering. Thesealgorithms assume only embedded SDL connections (one per physical link) and so may notaccurately reflect the network routing topology.


2-976800-A2-GB32-10 August 1994



Abbreviation: chrt

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Display Routing Table (dsrt)Generate Routing Tables (grt)

Change Routing Table Input Forms

There are two input forms associated with the chrt command. The initial input form enables you toidentify the source node for the table that is to be accessed for changing purposes, the destinationnode(s) for which specific table entries are to be changed, and the target node(s) to which theedited routing table will be downloaded.

The NMS retrieves the information as specified from the source node and displays the informationfor editing on the second input form (Figure 2-7). When complete, the routing tables will then bedownloaded to all target nodes.

The fields on the Change Routing Table input form are as follows.

Source node (Required field) [15 chars, no default]

Enter the node whose routing table is to be accessed for changes. The routing table forthis node is retrieved from the node and becomes available for editing. Only a single nodeand 731, 74x, and 74x-56K nodes that have device profiles can be entered. The user canenter the node name, node number, or node device address (m2/node number).

NOTE

The keyword none can also be entered if a new routing table isgoing to be created and downloaded to the target nodes. If none isentered, none will be the only permitted entry in the Destinationnode(s) field.


2-98 August 1994 6800-A2-GB32-10

Destination node(s) (Required field) [31 chars, default = all]

Enter the destination entries that are to be changed in the routing table. Multipledestinations can be specified. Each destination is entered by providing the node number ornode name of the destination. Each entry must be separated from another by a comma orspace. The keyword all can be used to specify that all destination entries in the routingtable are to be changed. To request the default routing entry for updating, use thekeyword default as one of the nodal entries. Wildcard characters, network names, andcircuit names can also be used to specify a group of destination nodes. Only 731, 74x, and74x-56K nodes with device profiles can be entered.

NOTE

If none is entered for the Source node , none is the onlypermissible entry in this field, as a new routing table is to becreated.

Target node(s) (Required field) [31 chars, no default]

Enter the nodes whose routing tables will be updated to reflect the changes to thespecified destination nodes that you request. Any additions to the routing table that youmake are also sent to the target nodes. All other destination entries are left alone.

NOTE

Target nodes must be the same type/model as the source node.


2-996800-A2-GB32-10 August 1994

Change Routing Table Input Form, Page 2

A sample Change Routing Table input form is shown in Figure 2-7.

Figure 2-7. Change Routing Table Input Form, Page 2

The fields on the Change Routing Table input form are as follows.

Destination (Required field)

This form lets the user update a single destination entry at a time. The desired destinationmust be entered in this field. A pop-up menu provides a list of the destination nodenumbers corresponding to the destination nodes that were entered from the first page ofthe command. The destination node numbers for the current routing table entries form thesource node are indicated in the pop-up menu with the node number followed by anasterisk (* ) (e.g., 112* ). The remaining entries are destination nodes that have a deviceprofile but no current routing entries at the source node.

Once the destination entry is selected, the Links field is populated with the currentrouting table entry for that destination. If no entry existed, the Links field remains blank.


2-100 August 1994 6800-A2-GB32-10

Links [4 lines/70 chars per line, no default]

This field specifies the ordered set of links to be tried to reach the given destination nodefrom the target node. Links can be either physical links, logical links, or external SDLs.Each entry must be separated by a comma or space. Physical links can be in the range 0 to15 for a 745 node. Logical links are specified by the prefix LL , followed by the logicallink number in the range 0 to 9999. External SDLs are either 101 or 102.

To change the link specification, select the destination and then type over the links to becorrected.

To delete an entry, select the destination and then enter ClrFld in the Links entry.

To add an entry, select the destination and then enter the desired link entries. (The Linksfield should be blank.)

If a destination needs to be changed, added, or deleted that was not entered on the first page of theform, the command must be completed or canceled, and restarted to enter the desired destination.

After every change, select a new destination in the Destination field. Once F2(Go) is selected, allchanges made are sent to the destination nodes specified.

Change Routing Table Results Form

The following messages may appear in the results display, if the command was unsuccessful.

Node in control mode

There is no node connected to the NMS’ command language port

Unable to get node connected to the NMS’ command language port

Route table is full

Active data base error at node’s CPU


2-1016800-A2-GB32-10 August 1994

Change Supervisory Data Link Configuration (chsdlc)Use the chsdlc command to configure embedded SDLs and synchronous SDLs.

This command displays a list of all time slots on a particular T1 link, with their currentconfiguration. The user can select a time slot, then display/change its SDL configuration. Certainlimitations apply, depending on the current link or node configuration.

The user can execute this command to take an SDL in or out-of-service.

NOTE

A message displays warning the user of the possibility that SDLconnectivity to one or more nodes can be severed by executing thiscommand.

Synchronous SDLs can be reconfigured as normal data channels by first taking the SDLout-of-service with this command, then reconfiguring the channel as desired with the ChangeChannel Configuration (chcc) command. A synchronous SDL can be configured by putting theSDL into service and configuring it with this chsdlc command.



Abbreviation: chsdlc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change Channel Configuration (chcc)Display Supervisory Data Link Configuration (dssdlc)

Change Supervisory Data Link Configuration Input Form, Page 1

The field on the Change Supervisory Data Link input form is as follows.


Enter the node identity. Only a single node and node numbers and node names for 731,74x, and 74x-56K nodes that have corresponding device profiles can be entered. The usercan enter the node device address (m2/node number).


2-102 August 1994 6800-A2-GB32-10

If the node is a 745 node, the Link field appears as follows.

Change Supervisory Data Link Configuration Input Form (745 link)

The field on the Change Supervisory Data Link Configuration input form is as follows.


Enter the link number on which the SDL is going to be configured or changed. Only asingle link can be entered. A pop-up selection list for 745 nodes displays the integers 0 to15.

Change Supervisory Data Link Configuration Input Form (731, 740, 741, 742), Page 2

A sample Change SDL Configuration input form (731, 740, 741, 742) is shown in Figure 2-8.

Figure 2-8. Change SDL Configuration Input Form for a 731, 740, 741, 742 Node, Page 2

Page 2 of the input form displays the first 10 time slots on the T1 link, with their configurations.Pages 3 and 4 display similar information for time slots 11 to 20 and 21 to 24, respectively. Thesepages correspond to the results normally returned from a Time Slot Summary (tss) commandrequest. Figure 2-8 shows the form for a 731, 740, 741, or 742 node. Figure 2-9 shows the form fora 745 node. This page is not displayed for 74x-56K nodes, as there is only a single time slot forsuch a node.


2-1036800-A2-GB32-10 August 1994

The fields on the Change Supervisory Data Link Configuration input form for a 731, 740, 741, or742 node are as follows.

Time slot selection

This field lists each time slot (1 to 24) on the T1 link, along with a selection request of yesor no. The user selects a single time slot for SDL configuration changes by changing thedesired time slot selection value to yes. Only one time slot may be selected; all other timeslot selection fields will become uneditable. If additional time slots need to bereconfigured for SDLs, the command should be re-initiated.

Channel Group

This display-only field shows the channel group, if any, currently allocated to the timeslot. A blank implies that no channel group is allocated to the time slot. SynchronousSDLs do not require channel groups.

Ser Synch

This display-only field indicates if the time slot is currently configured as a serialsynchronous time slot, connecting the 731, 740, 741, or 742 time slot to a 74x-56K node.If the time slot needs to be reconfigured for this application, the Change Physical LinkConfiguration (chplc) command must be used.

Time Slot Format

Once the user selects a time slot (by changing the Time Slot Selection field for theselected time slot to the value yes), the Format field can be edited, allowing the user tochange the time slot to one of the formats in the following list.

• emb SDL – The time slot is currently carrying an embedded SDL-only oneembedded SDL can be configured per T1 link.

• synch SDL – The time slot is currently carrying a synchronous SDL. Multiplesynchronous SDLs can be configured on a T1 link. (Not valid for 745s.)

• filler – The time slot is being used for ACAMI filler byte data. Adjacent timeslots are carrying clear channel data. Filler time slots cannot be configured forembedded or synchronous SDLs. If this time slot needs to be reconfigured withrespect to ACAMI, the Change Physical Link Configuration (chplc) commandmust be used.

• none – The time slot is not configured for any of the above formats.

You can only change this field if its current value is none. If the current value is embSDL, it cannot be changed to synch SDL unless the embedded SDL state is changed toout-of-service first. The same is true when changing a time slot from synchronous SDLformat to embedded SDL format. Then you can change it to synch SDL or emb SDL (ifthere is no other embedded SDL). To change the format from embedded SDL orsynchronous SDL, you must first take the SDL out-of-service. To do this, first selectTime slot, then change the SDL state on the next form. You can now re-initiate thecommand. The format will now be none and you can change it to the desired one.


2-104 August 1994 6800-A2-GB32-10

Synch SDL Channel

This display-only field indicates the channel number being used for the synchronousSDL, if the time slot is configured for this type of SDL.

Once the user selects a time slot (by changing the Time Slot Selection field for theselected time slot to the value yes), and the Format is selected or set at synch SDL, theSynch SDL Channel field can be edited, allowing the user to change or select thechannel to be configured as a synchronous SDL channel. The channel number enteredmust be a valid synchronous data channel installed on the node. An error message will bedisplayed if the channel number is not valid.

Logical Link

This display-only field indicates the logical link number allocated to this time slot.

A sample Change SDL Configuration input form (745) is shown in Figure 2-9.

Figure 2-9. Change SDL Configuration Input Form for a 745 Node, Page 2

The fields on the Change Supervisory Data Link Configuration Input Form for a 745 node are asfollows.

Endpoints

This display-only field shows the node numbers of the endpoints of the channel group onthe time slot.

DS-0 Endpoint /Channel

If the time slot is a DS0 channel endpoint, the destination node and channel numbers aredisplayed in this column for the DS0 channel.


2-1056800-A2-GB32-10 August 1994

Cross-Connect

If the time slot is cross-connected to another time slot on the 745 node, the link and timeslot to which it is cross-connected is displayed here. It is shown in the format XtsY, whereX is the link number and Y is the time slot number.

State

This display-only field shows the service state of the time slot. One of the followingvalues is shown.

• active – The time slot is allocated to a channel group and is active.

• oos – The time slot is allocated to a channel group but is out-of-service.

• idle – The time slot is not allocated to a channel group.

• test port – The time slot is currently being used for a test.

When finished with the format configuration and time slot selection, press F2(Go) and thenext page of the input form appears. For 74x-56K nodes, this is the second page of theinput form, since no time slot summary is produced. For 731, 740, 741, and 742 nodes,either the embedded SDL form or the synchronous SDL is displayed, depending on theconfiguration change selected on the first page. For 74x-56K and 745 nodes, theembedded SDL form is always displayed, since these nodes do not support synchronousSDLs.

Change Supervisory Data Link Configuration (Embedded SDL) SDL for 745 Node Input Form,Page 5, or 74x-56K Node Input Form, Page 2

A sample Change Supervisory Data Link Configuration input form is for embedded SDL shown inFigure 2-10.

Figure 2-10. Change SDL Configuration (Embedded SDL) Form, Page 5


2-106 August 1994 6800-A2-GB32-10

The fields on the Change Supervisory Data Link Configuration input form are as follows.

SDL state [14 chars, default = active]

This field is used to control the state of the embedded SDL. A pop-up menu displays theselection active and out-of-service. If the user changes an active SDL to out-of-service,a confirmation box is displayed with the message:

Taking the embedded SDL out-of-service may sever all NMScommunication with the node, unless alternate SDL paths exist. Pleaseverify before you continue.

Time slot

This display-only field shows the selected time slot. For 74x-56K nodes, this fielddisplays not applicable.

Satellite

This field is used to show if the SDL is being routed over a satellite hop, making the useof additional delay parameters necessary. Enter active or inactive.

SDL rate

This field is used to set the speed of the embedded SDL. Valid entries are dependent onthe node and time slot configuration. For pre-feature packages 3.x.x/4.x.x nodes, no speedselection is possible and the field is display-only with the speed set at 32000 bps. Forfeature package 4.x.x 745 nodes, the selection list has the values 32000 bps, 16000 bps,and 8000 bps. For feature packages 3.x.x 740/741 nodes, where the time slot is serialsynchronous, the field is display-only with the speed set at 1200 bps. For all other timeslots on feature package 3.x.x 740/741 nodes, the selection list has the values 32000 bps,16000 bps, and 8000 bps. For 74x-56K nodes, the field is display-only with the speed setat 1200 bps.

Connected to

Shows whether the link is connected to other or to a Series 700 device.

Remote node

This field is display-only and shows the number of the node connected to the given nodevia the active embedded SDL. This information comes from the facility profile for thegiven link. If the node/link information is not correct, cancel this command and update thefacility profile for the link and connectivity before proceeding.

Remote link

This field is initially display-only and shows the link number of the node connected to thegiven node via the active embedded SDL. This information is obtained from the facilityprofile for the given link. Normally, the facility profile should be up-to-date and accurate,so the user will not have to edit this field. When it can be edited, acceptable values are thelink numbers 0 to 15.


2-1076800-A2-GB32-10 August 1994

Change Supervisory Data Link Configuration (Synchronous SDL) Input Form, Page 5

A sample Change SDL Configuration (Synchronous SDL) input form is shown in Figure 2-11.

Figure 2-11. Change SDL Configuration (Synchronous SDL) Input Form, Page 5

The fields on the Change Supervisory Data Link Configuration input form are described asfollows.

Time slot

This display-only field shows the selected time slot.

SDL rate

This field is used to set the speed of the synchronous SDL. A pop-up menu is availablewith the selections 32000 bps, 16000 bps, and 8000 bps. If the time slot was a serialsynchronous time slot, the value 1200 bps is a display-only field and cannot be changed.The SDL state must be configured to out-of-service before reconfiguring the SDL rate.

SDL state

This field is used to control the state of synchronous SDL. A pop-up menu allowsselection of either active or out-of-service. If the user changes an active SDL toout-of-service, a confirmation box is displayed.


2-108 August 1994 6800-A2-GB32-10

Channel state

This field is used to control the state of the channel used for the synchronous SDL. Apop-up menu allows selection of either active or out-of-service.

Synchronous channel configuration information for the synchronous SDL is entered on the nextpage of the form.

Change Supervisory Data Link Configuration (Synchronous SDL) Input Form, Page 6

A sample Change SDL Configuration (Synchronous SDL) input form is shown in Figure 2-12.

Figure 2-12. Change SDL Configuration (Synchronous SDL) Input Form, Page 6

The fields on the Change Supervisory Data Link Configuration input form are as follows.

Transmit clock

This field is used to set the source for the transmit clock for the synchronous SDLchannel. A pop-up menu is available with the selections internal and external. Useinternal to generate the clock source from the channel interface module of themultiplexer node. Use external to generate the clock source from an external device.

Receive clock

This field is used to set the source for the receive clock for the synchronous SDL channel.A pop-up menu is available with the selections internal and external. Use internal togenerate the clock source from the channel interface module of the multiplexer node. Useexternal to generate the clock source from an external device.


2-1096800-A2-GB32-10 August 1994

RTS/DCD

This field is used to set the option for the RTS/DCD control lead on the synchronous SDLchannel. A pop-up menu is available with the selections active or inactive. Use active toforce the local output control signal into active. Use inactive to force the local outputcontrol signal into inactive.

BO/RI

This field is used to set the option for the BO/RI control lead on the synchronous SDLchannel. A pop-up menu is available with the selections active or inactive. Use active toforce the local output control signal into active. Use inactive to force the local outputcontrol signal into inactive.

DRS/DSR

This field is used to set the option for the DRS/DSR control lead on the synchronous SDLchannel. A pop-up menu is available with the selections active or inactive. Use active toforce the local output control signal into active. Use inactive to force the local outputcontrol signal into inactive.

DTR/CTS

This field is used to set the option for the DTR/CTS control lead on the synchronous SDLchannel. A pop-up menu is available with the selections active or inactive. Use active isused to force the local output control signal into active. Use inactive to force the localoutput control signal into inactive.

Change Supervisory Data Link Configuration Results Form

The Change Supervisory Data Link Configuration results form redisplays the input forms, exceptfor the time slot summary page.


2-110 August 1994 6800-A2-GB32-10

Channel Group Loopback (cgl)Use the cgl command to start and stop the loopbacks of channel groups at 745 nodes. The loopbackloops back all the time slots used by the specified channel group over a specified link of the 745 node.

NOTE

If the designated channel group carries an external (NAP) SDL, thediagnostic connectivity of the network could be interrupted by thisloopback, and termination of the loopback will not be possible fromthe NMS. This happens if no alternate path for SDLs over the T1link is present for the path taken by the channel group.



Abbreviation: cgl

Restrictions: Internal (channel groups with both endpoints on the same 745 node) channel groups cannot be looped back.

Routine: Yes

Schedule: Yes


Channel Group Loopback Input Form

The fields on the Channel Group Loopback input form are as follows.

Node (Required field)

Enter the 745 node over which the channel group is looped back. Only a single node and745 nodes with device profiles can be entered. The user can enter the node name, nodenumber, or node device address (m2/node number).

Channel Group (Required field)

Enter the name of the channel group to be looped back. Only channel groups that areknown to the NMS, except 745 internal channel groups and channel groups that terminateat 74x-56K nodes, can be entered.

Link (Required field)

Enter the link number on the 745 over which the channel group will be looped back. Apop-up menu displays the numerical entries 0 to 15.


2-1116800-A2-GB32-10 August 1994

Loopback state

Shows whether the loopback is to started or stopped. A pop-up menu displays theselections start and stop.

After this form has been completed, the NMS provides a confirmer message warning the user thatSDL connectivity may be severed by this loopback if the channel group contains an external NAPSDL, and there is no alternate SDL connectivity to the nodes connecting the link over which theloopback will be run. If this happens, the user will be unable to stop the loopback remotely.

Channel Group Loopback Results Form

The Channel Group Loopback results form indicates whether the loopback was started or stoppedsuccessfully.


2-112 August 1994 6800-A2-GB32-10

Channel Group Performance Report (cgpr)Use the cgpr command to get a report on the performance of a channel group at a node. The reportprovides the number of failed seconds and errored seconds for the channel group synchronizationbits.

Network compatible channel groups do not report this data since they do not containsynchronization bits.

Performance data is only updated when a channel group is connected.


NOTE

This command is not applicable to channel groups terminating ontwo 756 nodes. Channel groups that are routed from 756 nodes to740 or 741 nodes can be included by measuring the performance ofthe channel group at the 740 or 741 termination only.


Abbreviation: cgpr

Restrictions: None

Routine: Yes

Schedule: Yes


Channel Group Performance Report Input Form

The field on the Channel Group Performance Report input form is as follows.


Enter the 731, 740, 741, or 742 node for the channel group performance report. Only 731,740, 741, or 742 nodes with corresponding device profiles can be entered. The user mayenter the node name, node number, or node device address (m2/node number).


2-1136800-A2-GB32-10 August 1994

Channel Group Performance Report Results Form

A sample Channel Group Performance Report results form is shown in Figure 2-13.

Figure 2-13. Channel Group Performance Report Results Form

The fields on the Channel Group Performance Report results form are as follows.

Data reset interval

The rate at which the statistics registers at the node are reset. This rate is configured withthe Change Node Configuration Parameters (chncp) command and its Set PerformanceReporting Parameters section.

Time since data last reset

The time elapsed since the last reset of the statistics register.

Channel Group

The name of each non-network compatible connected channel group that is terminated atthis node.


2-114 August 1994 6800-A2-GB32-10

Errored Seconds

The number of errored seconds measured on the channel group since the last statisticsregister reset.

Failed Seconds

The number of failed seconds measured on the channel group since the last statisticsregister reset.

NOTE

The statistics registers at a node for channel group failed anderrored seconds are large enough to accommodate 65,535 errors. Ifthe register overflows (a value exceeding 65,535 errors), themessage register overflow displays in place of a numeric value.


2-1156800-A2-GB32-10 August 1994

Channel Group Summary (cgs)Use the cgs command to obtain a summary of channel groups at a multiplexer node. Theinformation provided in the summary includes the channel group endpoints, capacity, routingchoices, current route, and attribute routing selections.

Channel groups for the report can be selected based on their current connection state and/orconnection condition.



Abbreviation: cgs

Restrictions: None

Routine: Yes

Schedule: Yes


Channel Group Summary Input Form

The fields on the Channel Group Summary input form are as follows.


Enter the node for the channel group summary. Only a single node can be entered. Only731, 74x, or 74x-56K node numbers and node names that have corresponding deviceprofiles, can be entered. The user can enter the node device address (m2/node number).

Connection condition (Required field) [9 chars, default = all]

The summary report can be restricted based on the configured connection condition of thechannel groups. A pop-up menu displays the following selections.

permanent

Shows only channel groups with a permanent connection condition.

tod

Shows only channel groups with a time-of-day connection condition.

all

Shows all channel groups, regardless of connection condition.


2-116 August 1994 6800-A2-GB32-10

Connection state(s) (Required field) [10 chars, default = all]

The summary report can be restricted based on the current connection state of the channelgroups. A pop-up menu displays the following selections.

cnnct

Shows only channel groups that have bandwidth allocated to them.

dist

Shows only channel groups that are in a disconnected state.

idle

Shows only channel groups that have no bandwidth allocated to them.

cnnct/disc

Shows all channel groups except those that are idle.

cnnct/idle

Shows all channel groups except those that are disconnected.

disc/idle

Shows all channel groups except those that are connected.

cnnct-ch2/3

Shows in a one-line-per-channel-group format only those channel groups thathave second or third choice of bandwidth allocated to them.

cnnct-ch2/3+

Shows in a four-lines-per-channel-group format only those channel groups thathave second or third choice of bandwidth allocated to them.

all

Shows all channel groups, regardless of connection state.

Time (Required field) [7 chars, default = current]

Specifies that the report summarize the channel groups and their status as of a particulartime of day. The default value is current and represents the current time. To specify anyother time, enter the hours and minutes in the military time format hh:mm.


2-1176800-A2-GB32-10 August 1994

Channel Group Summary Results Form, Page 1

A sample Channel Group Summary results form is shown in Figure 2-14.

Figure 2-14. Channel Group Summary Results Form, Page 1

On this results form, the top area shows the information that you entered on the input form. Theremainder of the fields are as follows.

Channel group

The name of the channel group.

Endpoints

The endpoint node numbers of the channel group.

Capacity

The capacity of the channel group (in time slots).


2-118 August 1994 6800-A2-GB32-10

Priority

The priority of a channel group. The possible values are as follows.

high

The channel group has the ability to preempt low priority channel groups and itcannot be preempted by other channel groups.

normal

The channel group cannot preempt other channel groups and it cannot bepreempted by other channel groups.

low

The channel group cannot preempt other channel groups, but it can be preemptedby high priority channel groups.

Conn. condition

The configured connection condition of the channel group. Possible values arepermanent or time-of-day.

Conn. state

The connection state of the channel group. Possible values are idle, cnnct, disc, anddisc-IOC. The disc-IOC value means that the channel group was disconnected due to afailure of an IOC (Inter-Office Channel) and has not yet been able to reroute andreconnect.

Route

The current route choice, type, and route of the channel group is displayed. Routingchoices can be first , second, or third . Routing types can be fixed or auto. The route is alist of the current route of the channel group, including the node numbers, logical links,physical links, and any foreign network devices (e.g., DACs).

Channels

The channels assigned to this channel group.

Attributes

A list of the 13 routing attributes (physical, logical, and clear channel) and the requestvalue for those attributes as configured for the channel group. The request values can berequire, avoid, ignore, and prefer. Only applicable to 74x multiplexers with featurepackage 3.x.x or 4.x.x or later.


2-1196800-A2-GB32-10 August 1994

Channel Group Summary Results Form, Last Page

In addition, the results may indicate one of the following conditions.

1. Warning: channel group ccccccccc with endpoints nnn and nnn is multiply defined,conflicts with endpoints nnn and nnn.

This message informs you that a channel group name is used for two or more channelgroups in your network. This may create inconsistencies. You should delete multipleinstances. You must do this through the multiplexer terminal interface since NMS will onlypermit you to delete the single instance in its database.

2. Warning: ccccccccc exists at Node nnn, but is unknown to the NMS.

The named channel group must be added to the NMS database. Do this by executing eitheraccg or crcg.

3. Warning: Channel group ccccccccc definition at node conflicts with NMS database.NMS has endpoints nnn and nnn.

This message is pointing out a mismatch condition between the network and NMS.Execute accg, dscg, or chcg to the channel group to correct the condition.


2-120 August 1994 6800-A2-GB32-10

Channel Group Trace (cgt)Use the cgt command to see the current route of a connected channel group. If the route is optimal,the links and time slots that carry the channel group and the available bandwidth per hop areprovided in the output. An optimal route is one with the least possible number of hops.



Abbreviation: cgt

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Channel Group Summary (cgs)Create Channel Group (crcg)Display Channel Group (dscg)Time Slot Summary (tss)

Channel Group Trace Input Form

The field on the Channel Group Trace input form is as follows.

Channel group (Required field)

Enter the channel group name whose route will be traced. The channel group must beknown to the NMS.


2-1216800-A2-GB32-10 August 1994

Channel Group Trace Results Form, Page 1

A sample Channel Group Trace results form is shown in Figure 2-15.

Figure 2-15. Channel Group Trace Results Form, Page 1

The fields on the Channel Group Trace results form are as follows.

Channel group

The channel group name that you entered.


The endpoint node numbers of the channel group.

Endpoint node names

The endpoint node names of the channel group.

Selected route choice

The route choice selected for this channel group. Possible values are first , second, andthird .

Optimal number of hops

The number of hops in the optimal route (shortest possible number of hops). Inter-DACS(network) hops are not counted.


2-122 August 1994 6800-A2-GB32-10

Actual number of hops

The number of hops taken by the channel group route.

Route type

The type of route currently selected for this channel group. Possible values are fixed andautomatic.

For each Series 700 node in the path of the channel group, the node name, node number, physicallink number, logical link number (if applicable), and logical link name (if applicable) aredisplayed, along with a representation of the 24 time slots on the physical link. For each time sloton the link, a code is used to display the current usage of the time slot.

c

The time slot is allocated to the designated channel group.

l

The time slot is not allocated to the designated channel group, but is allocated tothe same logical link as the channel group.

x

The time slot is not allocated to the designated channel group, nor to the samelogical link, but it is allocated to another channel group or SDL.

blank

The time slot is free.

If the adjacent element in the trace to a Series 700 node is a non-Series 700 element, the fieldEntry to foreign network is displayed, without a time slot summary. The Network ID (NIDxx) isgiven, showing that the channel group enters a foreign network (e.g., DACS) at that point in itspath. If it exits the network, the next Series 700 node in the path follows.

Channel Group Trace Results Form (Serial Synchronous Channel Group), Page 1

This form is displayed when the designated channel group is a 74x-56K serial synchronouschannel group. There is no routing information for such channel groups, nor time slot summaryinformation. The time slot allocated from a 731, 740, 741, or 742 link is displayed in the fieldlabeled Serial synch time slot. This field is not shown if the channel group’s endpoints are both74x-56K nodes.


2-1236800-A2-GB32-10 August 1994

Channel Loopback (cl)(Disruptive)

Use the cl command to start and stop loopbacks of multiplexer channels. The following loopbacksare supported.

• Local loopback on 731, 740, 741, 742, and 74x-56K voice channels.

• Local loopback on 731, 740, 741, 742, and 74x-56K data channels.

• Local loopback of 740, 741, and 742 DDS channels.

• Internal loopback of DS0 channels on a 740, 741, or 742 DS1 channel module.

• Loopback at the time slot interchange (TSI) of DS0 channels on a 745 DS1 module.

• Loopback of DS0 channels on a 745 DS1 module.

• Loopback of DS0-group channels on a 745 DS1 module.

For data channel modules, multiple channels can be put into simultaneous loopback. However, forvoice and DS1 channel modules, only one channel per module can be looped back at any one time.

NOTE

Permission checking is present to ensure that the user has theappropriate command permission levels to take the channelout-of-service before running the test. If the user does not havepermission to execute the Change Channel Configuration (chcc)command and the designated channel is currently in service, the clwill not run.



Abbreviation: cl

Restrictions: For voice and DS1 channel modules, only one channel per module can be looped back at a time.

Routine: Yes

Schedule: Yes



2-124 August 1994 6800-A2-GB32-10

Channel Loopback Input Form

The fields on the Channel Loopback input form are as follows.


Enter the node on which the channel will be looped back. Only a single node and 731,74x, and 74x-56K nodes with device profiles can be entered. The user can enter the nodename, node number, or node device address (m2/node number).

Channel (Required field)

Enter the channel number for the channel to be looped back. Only a single channelnumber can be entered. The channel number must meet one of the following validationcriteria, depending on the type of node.

731 0 to 3


Y is 1 to 24



740-56k 0 to 127

741-56k 0 to 39

742-56k 0 to 31


For a voice or data channel, enter the channel number. For a DS0 channel on a740/741/742 enter the channel in the format XtsY, where X is the base channel numberand Y is the time slot. For DS0 channels on a 745, enter the channel in the format XtsY,where X is the link number and Y is the time slot.

Loopback state (Required field) [5 chars, no default]

Enter whether to start or stop the loopback state. A pop-up menu displays the selectionsstart and stop.

Loopback location (Required field for 745)

Enter the location of the loopback. A pop-up menu displays the selections TSI and DS-1.

Loopback type (Required field for 745)

Enter the type of loopback. If the loopback location is DS-1, a pop-up menu displays theselections internal and external. If the Loopback location is TSI, the pop-up menudisplays the selections DS-0 and DS-0 group.

Line (Required field only appears if node is a 745 and if Loopback type is DS-0 group)

Enter the line for loopback; values are 0 through 15.


2-1256800-A2-GB32-10 August 1994

Restore service state to active (Field only appears when loopback state is stop)

Specify whether or not the service state of the channel being tested should be restored toactive. Enter yes if you want to restore the channel to an active state, or no, if you want toleave the channel out-of-service.

Channel Loopback Results Form (Permission)

If the designated channel is currently in-service, the NMS automatically takes the channelout-of-service before initiating the loopback, provided the user has permission for the ChangeChannel Configuration (chcc) command. If the user does not have permission, a permission form isdisplayed.

Channel Loopback Results Form

The fields on the Channel Loopback results form are described as follows.

Channel

The number of the channel.

Channel type

The type of channel: asynch.data, synch.data, voice, e-voice, lbr-voice, DS-0,DDS-ocu, or DDS-dsu.

Loopback state

The loopback state is start or stop.

Loopback location (745 only)

The location of the loopback: TSI or DS-1.

Loopback type (745 only)

If the loopback location is DS-1, the type of loopback: internal or external. If theLoopback location is TSI, the type of loopback is DS-0 or DS-0 group.

Line (745 and if loopback type is DS-0 group)

The line identifier, a value from 0 through 15.

Restore service state to active (Only if loopback state is stop)

Shows whether the service state of the channel is restored to an active state: yes or no.

If the command was not executed successfully, an error message displays. If the command wasexecuted successfully, the following message displays:

Command was successfully executed


2-126 August 1994 6800-A2-GB32-10

Channel Network Loopback (cnl)(Disruptive)

Use the cnl command to start and stop network loopbacks of multiplexer DDS channels. Thefollowing loopbacks are supported.

• Loopback of the DDS channel at the DDS-OCU channel interface card.

• Loopback of the DDS channel at the attached DSU-CSU interface.

• Loopback of the DDS channel at the attached DSU-DSU interface.

NOTE

Permission checking is present to ensure that the user has theappropriate command permission level to take the channelout-of-service before running the test. If the user does not havepermission to execute the Change Channel Configuration (chcc)command and the designated channel is currently in service, the cnlwill not run.



Abbreviation: cnl

Restrictions: None

Routine: Yes

Schedule: Yes


Channel Network Loopback Input Form

The fields on the Channel Network Loopback input form are as follows.


Enter the node on which the channel will be looped back. Only a single node and740/741/742 nodes with device profiles can be entered. The user can enter node number,node name, or node device address (m2/node number).


2-1276800-A2-GB32-10 August 1994


Enter the channel number for the channel you want to be looped back. Only a singlechannel number can be entered. The channel number must meet one of the followingvalidation criteria, depending on the type of node.

740 0 to 127

741 0 to 39

742 0 to 31

Network loopback type (Required field) [3 chars, no default]

Enter the type of network loopback for the given channel. A pop-up menu displays theselections ocu, dsu, and csu. See the previous page for definitions of the selections.

Network loopback state (Required field) [5 chars, no default]

Enter whether the loopback is to be started or stopped. A pop-up menu displays theselections start and stop.

Channel Network Loopback Input Form (Permission)

If the designated channel is currently in service, the NMS automatically takes the channelout-of-service before initiating the loopback, provided the user has permission for the ChangeChannel Configuration (chcc) command. If the user does not have permission, a permission form isdisplayed.

The user must cancel the command at this point.

Channel Network Loopback Results Form

If the command was not executed successfully, an error message displays. If the command wasexecuted successfully, the following message displays:

Command was successfully executed


2-128 August 1994 6800-A2-GB32-10

Figure 2-16 shows a sample Channel Network Loopback results form.

Figure 2-16. Channel Network Loopback Results Form


2-1296800-A2-GB32-10 August 1994

Channel State Summary (css)Use the css command to see the current connection, service, and diagnostic states of the channelson a multiplexer node. The results of this command will also indicate if the channel is being usedas an ACAMI filler byte channel.



Abbreviation: css

Restrictions: When executing the css command for a 745, only DS0 channels on links connected to other can be included.

Routine: Yes

Schedule: Yes


Channel State Summary Input Form

The fields on the Channel State Summary input form are as follows.


Enter the node for which the summary is requested. Only a single node 731, 74x, and74x-56K nodes with corresponding device profiles can be entered. The user can enter thenode name, node number, or node device address (m2/node number).


Enter the link number for the node. A pop-up menu displays the selection 0 to 15, if thenode is a 745. Otherwise the only value is 0.


2-130 August 1994 6800-A2-GB32-10

Channel State Summary Results Form (731, 740, 741, 742, 74x-56K)

A sample Channel State Summary results form is shown in Figure 2-17.

Figure 2-17. Channel State Summary Results Form (731, 740, 741, 742, 74x-56K)

The fields on the Channel State Summary results form are as follows.

Module

The channel module number. If the channel module was a DS1 channel module, theheading displays as DS-1 CHANNEL MODULE.

NOTE

The results form for the 731 node shows only module 0.

Equipped

Shows whether the slot in the multiplexer cabinet is equipped for the channel module.

Channel

Shows the number of the channel.


2-1316800-A2-GB32-10 August 1994

Connection state

The current connection state of the channel. Possible values are the following:

cnnct

The channel is connected and has allocated bandwidth.

disc

The channel is either time-of-day disconnected or the channel group isdisconnected or idle.

idle

The channel has no allocated bandwidth.

filler

An additional service state can be reported for 745 DS0 channels. If the channelis an ACAMI filler byte channel, filler is displayed.

?

The slot is not equipped and the connection state is not idle. This state occurswhen the channel has been configured, but the hardware has not been installed.

Service state

Shows the current service state for the channel. Possible values are the following:

actv

The channel is currently operating in data mode.

loops

The channel is out-of-service. Diagnostics can be run on an out-of-servicechannel.

test

The channel is currently being used as a test port.


2-132 August 1994 6800-A2-GB32-10

Diagnostic state

The current diagnostic state of the channel. Possible values are the following:

loop

The channel is in the loopback state.

bert

A bit error rate test is being run.

lp/bt

The channel is in loopback and a bit error rate test is being run.

voice

The voice test is active (valid for 742 multiplexers).

Channel State Summary Results Form (745), Page 1

The fields on the Channel State Summary results form are as follows.

Channel

The time slot for the DS1 module.

Connection State

An additional service state can be reported for 745 DS0 channels. If the channel is anACAMI filler byte channel, filler is displayed.


2-1336800-A2-GB32-10 August 1994

Channel Summary (cs)Use the cs command to provide a summary report of the channels in a channel group terminatingon a 731, 740, 741, 742, or 74x-56K multiplexer node. The summary provides information on thechannel endpoints, type, data rate, connection condition, connection state, and service state.



Abbreviation: cs

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: DS0B Channel Summary (dcs)

Channel Summary Input Form

The fields on the Channel Summary input form are as follows.


Enter the node for the channel summary. Only a single node and 731, 740, 741, 742, and74x-56K nodes with corresponding device profiles can be entered. The user can enter thenode name, node number, or node device address (m2/node number).


Enter the channel group for the channel summary. Only a single channel group can beentered. Only those channel groups in the NMS channel group table that terminate on731, 740, 741, or 742 nodes are permitted.

Channel type(s) (Required field)

The summary can be restricted to channels of certain types. Any combination of channeltypes can be entered, separated by spaces or commas. For the 731 node the only typepossible is synch. Possible types for 740 or 741 nodes are synch, asynch, voice, DS-0,DDS-ocu, DDS-dsu, or all. For 742 nodes, possible types are synch, asynch, voice,DS-0, DDS-ocu, DDS-dsu, e-voice, or all. For 74x-56K nodes, possible types are synch,asynch, voice, or all.

Connection condition(s) (Required field)

The summary report can be restricted based on the configured connection condition of thechannels. A pop-up menu displays the following selections.

• all – The connection condition is ignored for the selection.

• permanent – Only the channels configured with a connection condition type ofpermanent are included in the summary.

• tod – Only the channels configured with a connection condition type oftime-of-day are included in the summary.


2-134 August 1994 6800-A2-GB32-10

Connection state(s) (Required field)

The summary report can be restricted based on the current connection states of thechannels. Any combination of connection states can be entered, separated by commas orspaces. Possible states are as follows.

• cnnct – Those channels that currently have allocated bandwidth are be includedin the summary.

• cg-disc – Those channels that currently are disconnected because the channelgroup is disconnected are included in the summary.

• tod-disc – Those channels that are currently disconnected because their currentreconfiguration time has put them in that state are included in the summary.

• idle – Those channels that are currently idle (have no allocated bandwidth) areincluded in the summary.

• all – All channels, regardless of their connection state, are included in thesummary.

Time (Required field)

You can specify that the report summarize the channels and their status as of a certaintime of day. The default value is current and represents the current time. To specify anyother time, enter the hours and minutes in the format hh:mm, military time.

Channel Summary Results Form, Page 1

A sample Channel Summary results form is shown in Figure 2-18.

Figure 2-18. Channel Summary Results Form, Page 1


2-1356800-A2-GB32-10 August 1994

The fields on the Channel Summary results form are as follows.

Channel

The channel number.

Type

The channel type.

Dest. Node

The node number of the channel’s destination endpoint.

Dest. Channel

The channel number of the channel’s destination endpoint node.

Rate

The rate of the channel.

Connect Cond.

The connection condition of the channel at the specified time.

Connect State

The connection state of the channel at the specified time.

Service State

The service state of the channel at the specified time. Possible values are oos(out-of-service) and active.

If the channel is a DS0B base channel, DS0A channel, SW56K, or E-SW56K, an indication isgiven in the last column of DS0B, DS0A, SW56K, or E-SW56K. DS0B subrate channels are notincluded in the summary, and can be obtained by using the DS0B Channel Summary (dcs)command.


2-136 August 1994 6800-A2-GB32-10

Channel System Test (cst) (Disruptive)

Use the cst command to test the end-to-end transmission path of a channel and its associatedhardware. This command performs a hardware diagnostic test on the local channel endpoint, putsboth channel endpoints into local loopback, and tests the data path by transmitting ten 8-bitcharacters through both channel endpoints and counting the errors. The loopbacks areautomatically released when the test is finished.

The channel must be connected before this test can be run. Channels that are currently in loopbackor bert states cannot be tested. The user cannot run a cst on a channel if any other channel on thesame channel module is currently in a loopback state. Channels on SDM modules have the testbit-pattern transmitted only through the remote channel endpoint.

For a complete description of the Destination for results and Schedule execution field, refer toChapter 1, Introduction.

NOTE

The channel must be taken out-of-service. Permission checking ispresent to ensure that the user has the appropriate commandpermission level to take the channel out-of-service before runningthe test. If the user does not have permission to execute theChange Channel Configuration (chcc) command and the designatedchannel is currently in service, the cst will not run.


Abbreviation: cst

Restrictions: You cannot run a channel system test on a channel if one of the otherchannels on the same channel module is already running a channel system test or is in a loopbackstate. This can be checked by running the Report Diagnostic Status (rds) command.

For synchronous data channels, you must first disable the rate adaptation option using the ChangeChannel Configuration (chcc) command. Refer to the Change Channel Configuration (chcc)command for more information on the rate adaption option.

Routine: Yes

Schedule: Yes



2-1376800-A2-GB32-10 August 1994

Channel System Test Input Form

The fields on the Channel System Test input form are as follows.


Only a single device and 731, 74x, and 74x-56K nodes with device profiles can beentered. The user can enter the node number, the node name, or the node device address(m2/node number).


Enter the channel number for the channel to be tested. Only a single channel can beentered. The channel number must meet one of the following validation criteria,depending on the type of node.

731 0 to 3

740 0 to 127, XtsY, where X is 0 to 127 (multiples of 8 only),Y is 1 to 24



740-56K 0 to 127

741-56K 0 to 39

745 XtsY, where X is 0 to 15, y is 1 to 24

For a voice or data channel, enter the channel number. For a DS0 channel on a 740/741,enter the channel in the format XtsY, where X is the base channel number and Y is thetime slot. For DS0 channels on a 745, enter the channel in the format XtsY, where X is thelink number and Y is the time slot.

If the designated channel is currently in service, the NMS automatically takes the channelout-of-service before initiating the loopback, provided the user has permission for theChange Channel Configuration (chcc) command. If the user does not permission, apermission form is displayed.

The user must cancel the command at this point.

Channel System Test Results Form

This form displays whether the Channel System Test has passed or failed.


2-138 August 1994 6800-A2-GB32-10

Compare Control Processors (ccp)Use the ccp command to compare the configuration of a multiplexer’s active and redundant controlprocessors. This command can also be used to correct any inconsistency between theconfigurations.



Abbreviation: ccp

Restrictions: None

Routine: Yes

Schedule: Yes


Compare Control Processors Input Form

The fields on the Compare Control Processors input form are as follows.


Enter the node for which the comparison or configuration update should be done. Only asingle node and 740, 745, and 74x-56K nodes that have corresponding device profiles canbe entered. The user may enter the node name, node number, or node device address(m2/node number). (This is applicable to all redundant chassis nodes.)

Action (Required field) [7 chars, default = copy]

Specifies whether the configurations of the two processors should be compared orwhether the redundant processor’s configuration should be updated by copying theconfiguration of the active processor. A pop-up menu displays the selections compareand copy.

Compare Control Processors Results Form

The outcome of the compare or copy is expressed as pass, fail or aborted. If the comparisonaborts or fails, an error message displays the reason for the abort. Fail indicates that theconfigurations are different.


2-1396800-A2-GB32-10 August 1994

Control Processor Test (cpt)Use the cpt command to initiate and execute a series of hardware diagnostic tests on the standbycontrol processor of a multiplexer.



Abbreviation: cpt

Restrictions: None

Routine: Yes

Schedule: Yes


Control Processor Test Input Form

The fields on the Control Processor Test input form are as follows.

Node (Required field-only applicable to redundant chassis nodes) [15 chars, no default]

Enter the node on which the test will be run. Only a single node and 740, 745, and74x-56K nodes that have corresponding device profiles can be entered. The user can enterthe (740 chassis) node number, node name, or node address (m2/node number).

Control processor (Required field) [1 char, default = 0]

Enter the control processor to be tested. A pop-up menu displays the selections 0 or 1.

Control Processor Test Results Form

The outcome of the Control Processor Test is expressed as pass, fail, or aborted.

If the test aborts or fails, an error message displays that explains the reason for the abort or failure.


2-140 August 1994 6800-A2-GB32-10

Create Channel Group (crcg)Use the crcg command defines the parameters and configuration of a new channel group.



Abbreviation: crcg

Restrictions: A maximum of 48 channel groups definitions per 731/740/741/742 and 74x-56K nodes is permitted. A maximum of 192 channel groups definitions per 745 node is permitted.

Routine: Yes

Schedule: Yes

Related Commands: Break Channel Group Connection (brcgc)Change Channel Group (chcg)Channel Group Summary (cgs)Delete Channel Group (dlcg)Display Channel Group (dscg)

Create Channel Group Input Form, Page 1

The fields on the Create Channel Group input form are as follows.


Specifies the 9 character channel group name for the new channel group. This name mustbe unique in the network. The name must begin with an alphabetic character. Lowercasealphabetic and numeric characters are permitted for the remaining 8 characters.

Endpoint nodes (Required field) [15 chars, no default]

Specifies the two endpoint nodes for the channel group. Only node numbers and nodenames for 731, Create Channel Group Input Form (Pass-Through), Page 674x, and74x-56K nodes that have device profiles are allowed. The user can also enter a deviceaddress (m2/node number).

The following forms will differ, based on the type of channel group endpoints.


2-1416800-A2-GB32-10 August 1994

Create Channel Group Input Form (74x-56K Node), Page 1

This form is used when at least one endpoint of the channel group is a 74x-56K node. The fields onthis input form are as follows.

Capacity (Required field) [9 chars, default = 54800 bps]

Specifies the capacity of the channel group. For 74x-56K node channel groups, a pop-upmenu provides the selections 54800 bps, 56000 bps, 62800 bps, and 64000 bps.


Specifies the reconfiguration condition option for the channel group. A pop-up menuprovides the selections permanent and time-of-day. Selecting time-of-day configuresthe channel group to connect/disconnect at preset times of the day – additionalinformation for the times and connection states will be requested on an additional page ofthe form.

Current Connection state

This display-only field indicates that the to-be-created channel group is currently in theidle state.

Requested connection state (Required field) [10 chars, default = connect]

Specifies the state the channel group should be placed in after the successful completionof the create request. A pop-up menu provides the selections connect and disconnect. Ifthe user selects connect, a Make Channel Group Connection request will automatically besent to the node upon completion of the create request. If the user selects disconnect, thechannel group will be left in its disconnected or idle state after completion of the createrequest.

Network compatible

This field is display-only for 74x-56K node channel groups and is set to no. The 74x-56Knode channel groups are always non-network compatible.

Serial synchronous time slot (Required field) [2 chars, no default]

Specifies the time slot for the channel group, if one endpoint of the channel group is a731, 740, 741, or 742 and the other endpoint is a 74x-56K node. A pop-up menu providesthe numerical selections 1 to 24. If both endpoints are 74x-56K nodes, this field does notappear on the form.


2-142 August 1994 6800-A2-GB32-10

Create Channel Group Input Form (non-56K Node), Page 2

A sample Create Channel Group input form is shown in Figure 2-19.

Figure 2-19. Create Channel Group Input Form (non-56K), Page 2

This form is used when neither endpoint of the channel group is a 74x-56K node.


First choice route (Required field) [9 chars, default = automatic]

A channel group can be automatically routed through the network, or the route can bedefined by the user. A pop-up menu provides the choices automatic and fixed. If fixed isselected, a First fixed route will have to be specified by the user on a succeeding page ofthe form.


2-1436800-A2-GB32-10 August 1994

Capacity (Required field) [9 chars, no default]

Specifies the amount of bandwidth to be allocated to the channel group. Entries canspecify either the number of time slots (n ts) or the bandwidth in kbps (n kbps). Capacitiesmust be meet one of the following criteria.

• Must be in the format n ts where n is 1 to 24.

• Must be in the format n kbps where n is:

1. multiple of 64

2. multiple of 64) + 32, 96 <= n <= 1504

3. (multiple of 64) + 48, 112 <= n <= 1520

4. 0 or (multiple of 64) + 56, 56 <= n <= 1528

5. (multiple of 64) + 56 <=n 0 to 24

Second choice route [9 chars, no default]

If the 1st choice route was fixed and the route fails, the multiplexer will attempt to reroutethe channel group to the 2nd choice route. The second choice can be automatic or fixed,as provided by the pop-up menu. If fixed is selected, a Second fixed route will have tospecified by the user. If automatic was selected for the 1st choice route, this field isdisplay-only and shows the value none.

Priority (Required field) [6 chars, default = normal]

Specifies the routing priority for the channel group. A pop-up menu provides thefollowing selections.




Third choice route [9 chars, no default]

If the 2nd choice route was fixed, and the channel group was on the 2nd choice routeand the route fails, the multiplexer would attempt to reroute the channel group accordingto the 3rd choice route selection. A pop-up menu provides the selections automatic andnone. If none is specified, no re-routing, based upon failure of a fixed 2nd choice route,will be attempted. If the 1st choice route or 2nd choice route fields were set toautomatic or none, this field is display-only with the value none.


Specifies the reconfiguration condition option for the channel group. A pop-up menuprovides the selections permanent and time-of-day. Selecting time-of-day configuresthe channel group to connect/disconnect at preset times of the day – additionalinformation for the times and connection states will be requested on an additional page ofthe form.


2-144 August 1994 6800-A2-GB32-10

Robbed-bit signaling (Required field) [8 chars, no default]

Specifies whether voice channels using robbed bit signaling will be assigned to thischannel group. A pop-up menu provides the selections active and inactive. Extra channelgroup bandwidth will be required, if this field is set to active.

Trunk Conditioning (Required field) [10 chars, no default]

If voice channels will be assigned to this channel group, the type of trunk conditioningused by the originating PBX must be specified. The field only appears when Robbed bitsignaling is active. A pop-up menu provides the selections E&M , FXO-loop, FXS-loop,FXO-ground, FXS-ground, Ringdown, PLAR , and hexadecimal codes from 00 to ff .

Network compatible (Required field) [3 chars, no default]

Specifies whether the channel group will be configured as network compatible. Networkcompatible channel groups are exactly integral multiples of DS0s. Network compatiblechannel groups may only contain the following types of channel types: 64 kbps robbed bitvoice, 64 kbps DS0, and 56 kbps synchronous data. Several network compatible channelscan be assigned to a network compatible channel group, but they must all be of the sametype. A pop-up menu provides the selections yes and no.

IOC reroute timer (Required field) [8 chars, default = 0]

This field specifies the IOC Reroute Integration time for the channel group. This time isthe time for the node to delay before rerouting a channel group based on channel groupsynchronization loss. A pop-up menu provides the numerical selections 0 to 60 seconds,and the keyword inactive to disable the feature. This field will only appear on formswhere both endpoints are feature packages 3.x.x/4.x.x nodes and for which the channelgroup is NOT network compatible.

B8ZS optimization (Required field) [3 chars, no default]

Specifies whether B8ZS coding is to be used for the channel group. If B8ZS is not used,ZCS (Zero Code Suppression) will be used, and an additional 8 kbps of overheadbandwidth will be taken up by the ZCS coding and not be available for user data. Thepop-up menu provides the selections yes and no. This field only appears on the formwhen both endpoints of the channel group are pre-feature packages 3.x.x/4.x.x nodes.Otherwise, the Clear Channel attribute in the attributes section of this command is usedto configure B8ZS.

Trouble code (Required field) [15 chars, no default]

For channel groups with 74x nodal endpoints, the trouble code is used to send in the link’stime slot instead of data, should a T1 failure occur. A pop-up menu provides theselections trb , mux-out-of-sync, and the hexadecimal codes from 00 to ff .

Requested connection state (Required field) [12 chars, default = ‘‘connected”]

Specifies the desired connection state for the channel group, after it has been created. Apop-up menu provides the selections connect and disconnect. Select connect and theNMS will issue a Make Channel Group Connection request to the node after the createrequest has completed.


2-1456800-A2-GB32-10 August 1994

Create Channel Group Input Form, (Channel Group Reconfiguration Times), Page 3


Figure 2-20. Create Channel Group Input Form, Page 3


Reconfiguration time (Required field) [5 chars, no default]

Specifies the time that the channel group should be connected or disconnected fortime-of-day operation. The time is specified in hh:mm format, military time.

Connection state (Required field) [10 chars, no default]

Specifies the connection state for the channel group at the designated reconfigurationtime. A pop-up menu provides the selections disconnect or connect.


2-146 August 1994 6800-A2-GB32-10

Create Channel Group Input Form (Channel Connection Reconfiguration Times), Page 3


Figure 2-21. Create Channel Group Input Form (Channel Connection Reconfiguration Times), Page 3

The field on the Create Channel Group input form is as follows.

Reconfiguration time [5 chars, no default]

Specifies the reconfiguration times for channel groups that are permanently connected.This is used for time-of-day channels that are in the channel group, as specified in theChange Channel Configuration (chcc) command. The time is specified in hh:mm format,military time.


2-1476800-A2-GB32-10 August 1994

Create Channel Group Input Form (Attribute Requests), Page 4

A sample Create Channel Group input form (attribute requests) is shown in Figure 2-22.

Figure 2-22. Create Channel Group Input Form (Attribute Requests), Page 4

This form only appears when at least one endpoint of the channel group is a new (feature packages3.x.x/4.x.x) node, and the channel group is not a 74x-56K channel group.

attribute request values [7 chars, default = ignore]

For each physical and logical attribute, the attribute request can be specified for thechannel group. A pop-up menu provides the following selections.


• prefer – The channel group will be routed over routes that satisfy this attribute,before selecting an alternate route that may not.



For the Clear Channel attribute, the only values in the menu will be require and ignore.This field indicates whether the channel group must be routed over Clear Channelfacilities. If require is selected, the channel group will only be routed over ACAMI orB8ZS links. If ignore is selected, the channel group will route over all types of links, butclear channel facilities will be tried last in any automatic route selection process.


2-148 August 1994 6800-A2-GB32-10

Create Channel Group Input Form (Fixed Route Selection), Page 5


Figure 2-23. Create Channel Group Input Form (Fixed Route Selection), Page 5

This form appears if fixed was selected for the 1st choice route field. The bottom half of this formappears if fixed was selected for the 2nd choice route field.



This display-only field shows the beginning node in the route — the endpoint node of thechannel group.

Next route element (Required field) [15 chars, no default]

This is the data-entry field for specifying the route. The user selects the next element inthe route path by entering it into this field. Once entered and accepted, this entry willappear in the Route field, as the next item in the path. The next element is then specifiedby selecting/entering another element in this Next route element field. Routing elementscan be node numbers, node names, logical link numbers, logical link names, or NIDxx tospecify entry into a foreign network (NIDxx). A pop-up menu provides the possibleselections for each next element, based on information in the facility profile database.Entries in the menu meet the attribute requirements entered previously.


2-1496800-A2-GB32-10 August 1994

Route

This displays the channel group fixed route, as it is built by entering items in the fielddirectly below it. Optionally, the user can type in the entire route by entering the nodeand/or logical link numbers directly into this field. The user should enter the string NIDxxto indicate the entry of the channel group route into a foreign network. The NIDxxspecifies the foreign network ID – these IDs are specified in the facility profiles for the T1links connecting the nodes to foreign networks. Nodes are entered using their nodenumbers, logical links must use their logical link numbers (LLnnnnn).


See First fixed route from.

Route

See above.

Next route element

See above.

Create Channel Group Input Form (Pass-Through), Page 6


Figure 2-24. Create Channel Group Input Form (Pass-Through), Page 6


2-150 August 1994 6800-A2-GB32-10

This form only appears when the user is configuring a pass-through channel group (channel groupfrom a 745 endpoint node to a foreign network, without using logical links). There are two sets ofthese fields fir each NIDxx in each fixed route and one set for each side of each NID.

Node

This display-only field shows the node number of a node adjacent to a NID in the fixedroute for the channel group.

Link

This display-only field shows the link number at the node above for a physical T1 linkconnected to a NID in the fixed route for the channel group. For 740/741 nodes, the fieldis always blank.

Time slots [44 chars, no default]


Create Channel Group Results Form

The Create Channel Group results form redisplays the input form, with a success or failuremessage.


2-1516800-A2-GB32-10 August 1994

Create Logical Link (crll)Use the crll command to create a logical link.

A logical link defines a fixed time slot path between two ACCULINK nodes.

The logical link is normally used to specify an alternate path between two nodes through anintervening network of foreign (DACS) devices. Logical links can be incorporated into noderouting tables and channel group routes, allowing channel groups to be automatically re-routedover alternate logical link paths.



Abbreviation: crll

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Break Logical Link Connection (brllc)Change Logical Link (chll)Delete Logical Link (dlll)Display Logical Link (dsll)Logical Link Summary (lls)Make Logical Link Connection (mkllc)


2-152 August 1994 6800-A2-GB32-10

Create Logical Link Input Form, Page 1

A sample Create Logical Link input form is shown in Figure 2-25.

Figure 2-25. Create Logical Link Input Form , Page 1

Logical link number (Required field)

The user must specify the number of the logical link to be created. This number is uniqueat a node. Different nodes can re-use the number for other logical links. Logical linknumbers must always begin with the special prefix LL . Logical link numbers must be inthe range 0 to 9999.

Logical link name (Required field)

The user may assign a name for the logical link. This name is unique in the NMS. Logicallink names must be prefixed with ll- and may only contain lowercase alphabetic andnumeric characters. The name must begin with an alphabetic character.


Enter the node at each end (endpoint 1 and endpoint 2) of the logical link. Only the nodenames and node numbers for 74x nodes of feature packages 3.x.x or 4.x.x can be entered.All such nodes must have device profiles. The user may also enter the node deviceaddress (m2/node number).


2-1536800-A2-GB32-10 August 1994


Enter the physical link number for the nodes at each end (endpoint 1 and endpoint 2) ofthe logical link. A pop-up menu displays the link numbers 0 to 15 for a 745 node. Thisfield does not appear on the form for 740, 741, or 742 nodes and the space is left blank.

Time slots (Required field)

Enter the time slots to be used for the logical link at each endpoint. One or more timeslots can be entered separated by spaces or commas. A range of time slots can be enteredby using a hyphen (-) between two time slot numbers. The order of the time slots isirrelevant.

If different time slots are entered for non-adjacent endpoints, the system displays aconfirmer box advising the user that both nodes are connected to a Series 700 node andasks the user to verify the use of the logical link in this situation.

Capacity

This display-only field specifies the capacity for the logical link, and is determined fromthe number of entered time slots. It is always displayed in units of kbps, with kbps beingdisplayed on the form (e.g., 64 kbps).

Connection state (Required field)

The user can request a connection state for the logical link, after it has been successfullycreated. A pop-up menu displays the selections connect and disconnect. If connect isselected, the NMS will automatically issue a mkllc command after the create request hascompleted.

Robbed bit signaling (Required field)

This field enables and disables robbed bit signaling at both endpoints of the logical link.The field is not be shown on the form if both physical links at each endpoint are notconnected to other (i.e., connected to non-74x devices). A pop-up menu displays theselections active and inactive.


2-154 August 1994 6800-A2-GB32-10

Create Logical Link Input Form, Page 2

A sample Create Logical Link input form is shown in Figure 2-26.

Figure 2-26. Create Logical Link Input Form , Page 2

This field displays the physical attributes for the logical link that are inherited from its physicallinks, and allows the user to configure the desired states for the logical attributes of the logical link.

For the physical attributes, the attribute number, name, and state are displayed. If two states appearfor a particular attribute, the two physical links of the logical link are in a mismatch state for theattribute.

The only input field on this form is for the state of each logical attribute (attribute numbers 7 to12). The attribute numbers and names are display-only and are retrieved from the database, asdefined by the Change Node Configuration Parameters (chncp) command. For each logicalattribute state, a pop-up menu displays the selections active and inactive. Both endpoints of thelogical link will be configured with the same state.

Create Logical Link Results Form

A success or failure message is displayed on the first page of the results form. The next pages areredisplays of the input forms.


2-1556800-A2-GB32-10 August 1994

DDS Channel Performance and Status (ddscps)Use the ddscps command to summarize DDS channel performance and status information. Thesummary includes network errored seconds, loop errored seconds, loop side signal losses, and loopside signal status for each DDS-OCU channel at a 740, 741, or 742 node.



Abbreviation: ddscps

Restrictions: Only applicable to DDS-OCU channels, not DDS-DSU channels.

Routine: Yes

Schedule: Yes


DDS Channel Performance and Status Input Form

The field on the DDS Channel Performance and Status input field is as follows.


Enter the node for the channel performance report. Only a single node and 740, 741, or742 nodes with corresponding device profiles can be entered. The user can enter the nodenumber, node name, or node device address (m2/node number).


2-156 August 1994 6800-A2-GB32-10

DDS Channel Performance and Status Results Form, Page 1

A sample DDS Channel Performance and Status results form is shown in Figure 2-27.

Figure 2-27. DDS Channel Performance and Status Results Form , Page 1

The fields on the DDS Channel Performance and Status results form are as follows.

Elapsed time since last reset

The amount of time since the statistics registers were last reset.

Format

The channel format (type): DSOA, DSOB base, DS0B subrate, and SW56K.

Channel

The channel number.

Network Errored Seconds

The number of errored seconds on the network side of the DDS channel.

Loop Errored Seconds

The number of errored seconds on the loop side of the DDS channel.


2-1576800-A2-GB32-10 August 1994

Loop Sig. Losses

The number of times that the signal has gone into a loss state on the loop side of the DDSchannel.

Loop Side Sig. Status

The value Signal loss indicates that a Loss of Signal condition persisted for 2 seconds ormore on the loop side of the DDS channel. The value present indicates that a valid signalis present.

SW56K Call Status

The call status of all configured SW56K DDS channels. Possible values are connected,outgoing, incoming, disconnected, inactive, alarm, not equipped, or maint.mode.

NOTE

A value of 65,535 is the maximum value held by the statisticsregisters.


2-158 August 1994 6800-A2-GB32-10

DDS Channel Trouble Codes (ddsctc)Use the ddsctc command to summarize the key control codes received from the network on eachDDS channel at a node.



Abbreviation: ddsctc

Restrictions: None

Routine: Yes

Schedule: Yes


DDS Channel Trouble Codes Input Form

The field on the DDS Channel Trouble Codes input form is as follows.


Enter the node for the channel trouble codes summary report. Only a single node and 740or 741 nodes with corresponding device profiles can be entered. The user can enter thenode name, node number, or node device address (m2/node number).


2-1596800-A2-GB32-10 August 1994

DDS Channel Trouble Codes Results Form

A sample DDS Channel Trouble Codes results form is shown in Figure 2-28.

Figure 2-28. DDS Channel Trouble Codes Input Results Form , Page 1

The fields on the DDS Channel Trouble Codes results form are as follows.

Channel

The channel number and type – DS0A, DS0B base, DS0B subrate.

Multiplexer Out of Sync

The number of out-of-synch codes received from the network.

Abnormal station

The number of abnormal station codes received from the network.

Test

The number of test codes received from the network.

Unassigned Mux Condition

The number of unassigned condition codes received from the network.


2-160 August 1994 6800-A2-GB32-10

DS0B Out of Sync

The number of out-of-synch DS0B codes received from the network.

NOTE

A value of 65,535 is the maximum value held by the statisticsregisters.


2-1616800-A2-GB32-10 August 1994

DDS Signaling Test (ddsst)Use the ddsst command to perform the DDS signaling test. This test verifies the connection fromthe multiplexer to the SW56K DSU/CSU device or from the multiplexer to the switched network.Combined, these two tests verify proper end-to-end call setup between the DSU/CSU and theswitched network.



Abbreviation: ddsst

Restrictions: Only applicable to SW56K DDS-OCU channels, not DDS-DSU channels.

Routine: Yes

Schedule: Yes


DDS Signaling Test Input Form

The fields on the DDS Signaling Test input form are as follows.


Enter the node for the signaling test. Only a single node and 740, 741, or 742 nodes withcorresponding device profiles can be entered. The user can enter the node number, nodename, or node device address (m2/node number).


Enter the channel number for a SW56K DDS-OCU channel.

Direction (Required field)

Specifies the direction of the signaling test. A pop-up menu displays the values: networkand DSU/CSU. If you select network, the test will verify the connection from themultiplexer to the switched network (i.e., the central office switch). If you selectDSU/CSU, the test will verify the connection from the multiplexer to the SW56KDSU/CSU device. Combined, these two tests verify proper end-to-end call setup betweenthe DSU/CSU and the switched network.


2-162 August 1994 6800-A2-GB32-10

DDS Signaling Test Results Form, Page 1

The fields on the DDS Signaling Test results form are as follows.

Channel

The channel number.

Direction

The direction of the signaling test: network or DSU/CSU.

Test result

The result of this test: pass, fail , error , or warning.


2-1636800-A2-GB32-10 August 1994

Delete Channel Group (dlcg)Use the dlcg command to delete a channel group from the network and from the NMS database.

All channels in the channel group must be idle before it can be deleted. The channel group mustalso be idle.

To make the channels idle, execute the Break Channel Connection (brcc) command to eachchannel in the channel group. The channels assigned to the channel group can be shown using theChannel Summary (cs) command. To idle the channel group, use the Break Channel GroupConnection (brcgc) command.



Abbreviation: dlcg

Restrictions: None

Routine: Yes

Schedule: Yes

Related Command: Break Channel Connection (brcc)Break Channel Group Connection (brcgc)Channel Summary (cs)

Delete Channel Group Input Form

The field on the Delete Channel Group input form is as follows.


Enter the channel group to be deleted. Only a single channel group can be entered.

Delete Channel Group Results Form, Page 1

Displays the channel group that has been deleted.


2-164 August 1994 6800-A2-GB32-10

Delete Channel Group (non-56K) Results Form, Page 2

The fields on the Delete Channel Group (non-56K) results form are as follows.


The endpoint node numbers of the channel group being disconnected.

Endpoint node names

The endpoint node names and model numbers of the channel group being disconnected.

First choice route

The requested routing type for the first choice (fixed, automatic).

Second choice route

The requested routing type for the second choice (fixed, automatic, or none).

Third choice route

The requested routing type for the third choice (automatic, none).

First fixed route

The fixed route, if the First choice route type was fixed.

Second fixed route

The fixed route, if the Second choice route type was fixed.


2-1656800-A2-GB32-10 August 1994

Delete Logical Link (dlll)Use the dlll command to delete logical link(s) from the network and from the NMS database.

The logical links and all channel groups routed over the logical links must be idled (disconnected)before any deletions or changes can be made. The NMS breaks the logical link connections and alltheir channel group connections automatically, upon user confirmation. The user must have thenecessary permissions for the Break Logical Link Connection (brllc) and Break Channel GroupConnection (brcgc) commands for this automatic action to take place.



Abbreviation: dlll

Restrictions: None

Routine: Yes

Schedule: Yes

Related Command: Break Logical Link Connection (brllc)Change Logical Link (chll)Create Logical Link (crll)Display Logical Link (dsll)Logical Link Summary (lls)Make Logical Link Connection (mkllc)

Delete Logical Link Input Form

The fields on the Delete Logical Link input form are as follows.

Node

Enter the node whose logical link(s) will be deleted. Only a single node and nodenumbers and node names for 74x nodes of feature packages 3.x.x or 4.x.x can be entered.All such nodes must have device profiles. The user can enter the node device address(m2/node number).


2-166 August 1994 6800-A2-GB32-10

Logical link(s) (Required field)

Enter the logical link(s) that will be deleted. Logical links can be entered by typing in thelogical link numbers or logical link names. If numbers are entered, they must be precededby the string LL . If names are entered, they must be preceded by the string ll- . Multipleentries are permitted, separated by spaces or commas. The wildcard character (*) ispermitted. The keyword all is permitted, to designate all logical links at the specifiednodal endpoint. Only those logical links that are known to the NMS (in the database) canbe entered or specified.

After this page has been completed, NMS checks the configuration of the designated logical linksby querying the designated multiplexer node. If the NMS information does not match, NMS flagsthe database for possible updating. If the deletion is not successful, it informs the user that this wasdone.

NMS also checks the connection state of the logical links and their channel groups. If either thelogical links are connected, or any channel groups on them are connected, a confirmer message isdisplayed to the user.

Delete Logical Link Input Form (Confirmer)

If there are connected channel groups on the designated logical link(s), or if only the logical link(s)is connected, a confirmer message is displayed warning the user that these channel groups and thelogical link connections will be broken if the delete logical link request is executed. The user canchoose to continue or cancel the change request. If the user cancels, no connection changes aremade.

This confirmer message is only displayed if the user has functional access permission for the BreakChannel Group Connection (brcgc) and/or Break Logical Link Connection (brllc) commands. Ifthe user does not have permission, a permission form is displayed.

Delete Logical Link Results Form

The first pages of the Delete Logical Link results form list, for each logical link delete request,messages related to the outcome of the request.

The fields on the Delete Logical Link results form are as follows.

Logical link number

The number of the logical link being deleted.

Logical link name

The name of the logical link being deleted.

Endpoint 1 node



2-1676800-A2-GB32-10 August 1994

Endpoint 2 node


A series of possible messages is as follows.

Channel group ccccccccc could not be broken

This message is displayed if a channel group was automatically broken by the NMS as part of thiscommand. A separate message for each broken channel is displayed.

Channel group cccccccc could not be broken

This message is displayed if a mismatch was discovered between the logical link configurationdata in the NMS and that in the node, and the logical link delete request was unsuccessful. Thedatabase was updated to match the data in the node.

Logical link was successfully broken

This message is displayed if the logical link connection was successfully broken.

Logical link could not be broken

This message is displayed if the logical link connection break request failed.

Logical link was successfully deleted at Node nnn

This message is displayed if the logical link was successfully deleted at the node. For a successfuldeletion, the link must be deleted at both of its nodal endpoints.

Database was updated

This message is displayed to indicate that the logical link was removed from the NMS database.


2-168 August 1994 6800-A2-GB32-10

Display Channel Configuration (dscc)Use the dscc command to display the configuration of channels on 731, 74x, and 74x-56Kmultiplexers.

Only one endpoint of the channel need be identified. The other (if it exists) will be obtained fromthe configuration data of the specified node.

The results forms for this command are dependent on the type of channel being displayed.

For a complete description of the Destination for results and Schedule execution fields, refer toChapter 1, Introduction. For an example of input and results forms, refer to the Change ChannelConfiguration (chcc) command.

Access Level: Help Desk, Data Technician,Manager

Abbreviation: dscc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Command: Change Channel Configuration (chcc)

This command has many forms, depending on the type of channel endpoints being displayed. Notethat, if displaying a channel with two endpoints, the forms are two-sided forms, with the channelconfiguration of one endpoint on the left side and the other endpoint on the right side. Whendisplaying a channel with two endpoints where both endpoints have the same channel type, thefields will be identical for both sides of the form. When displaying a channel with two endpointswhere the channel types are different at each endpoint, the forms may be one- or two-sided,depending on the type of fields being displayed on the form. When displaying a single endpointchannel, only the left side of the form is used.

Display Channel Configuration Input Form, Page 1

The fields on the Display Channel Configuration input form are as follows.


Enter the node whose channel configuration will be displayed. Only a single node and731, 74x, and 74x-56K nodes with device profiles can be entered. The user can enter thenode name, node number, or node device address (m2/node number).


2-1696800-A2-GB32-10 August 1994


Enter the number of the channel whose configuration is to be displayed. Only a singlechannel number can be entered. The channel number must meet one of the followingvalidation criteria, depending on the type of node.

731 0 to 3

740 0 to 127, XtsY, where X is 0 to 127 (multiples of 8 only), Y is 1 to 24



740-56K 0 to 127

741-56K 0 to 39

742-56K 0 to 31



Display Channel Configuration Results Form, Page 1

The fields on the Display Channel Configuration results form are as follows.

Current destination

Shows the currently configured destination node and channel of each channel endpoint.The node and channel are identified with the format Nnnn Cnnn where Nnnn indicatesnode number nnn, and Cnnn indicates channel number nnn. If the channel is not yetconfigured, both destinations will be listed with a ?.


Shows the current connection state of the channel. Possible values are connected,time-of-day disconnected, cg-disconnected, Idle, and disconnected.

Channel type

Shows the type of channel being configured. It is determined by the channel module type.(See the Change Channel Module Type (chcmt) command.) Possible values are synch.data, asynch.data, e-voice, lbr-voice, voice, DS-0, DDS-dsu, DDS-ocu, synch-DS0group, DS0 group.

Channel group

This field specifies the channel group used for the channel.


2-170 August 1994 6800-A2-GB32-10

Connection condition

This field specifies the connection condition for the channel. Possible values arepermanent and time-of-day. Use permanent to set the channel to be connected 24 hours per day. Use time-of-day to set the channel to be connected only at specifiedtimes of the day. These times are set in the configuration of the designated channel group.

Service state

This field sets the service state for the channel. Possible values are active andout-of-service.

Display Channel Configuration Results Form (Voice Channels only), Page 2

This form displays time-of-day parameters for voice channels.


Time

This column shows the times of the day the channel connection will be changed, asdefined in the Channel Group configuration. The times are shown in hh:mm military timeformat.

State

For each reconfiguration time, this specifies the connection state for the channel. Possiblevalues are connect and disconnect.

Rate

This field only appears if the previous field was connect. The voice rate for the channelfor that connection period is shown. Time-of-day rate changes for DDS channels are notapplicable.

Display Channel Configuration Results Form (Voice Channel), Page 3

The Voice rate field does not appear for a time-of-day channel when the connection condition fieldis configured as time-of-day.


Voice rate

Shows the voice rate for the channel.


2-1716800-A2-GB32-10 August 1994

E output signal

This field sets the E output signal type. A voice channel uses E&M Type 1 side signalingand always receives the remote M lead transitions. Possible values are as follows.

• in-band A/B – This signaling option allocates 800 bps of channel groupbandwidth for A and B signaling bit transmission.

• active – This option forces the local E lead control signal active.

• background – This options the channel to transmit the remote M lead transitionsover the SDL to the local’s E lead, without extra bandwidth allocation on thechannel group.

• inactive – This option forces the local E lead control signal inactive.

• in-bandA – This options the channel to transmit the remote M lead without anyextra voice channel bandwidth. A channel group bandwidth of 400 bps will berequired for signaling.

• robbed-bit – This options the channel to use robbed-bit signaling. With this typeof signaling the least significant bits of selected DS1 frames from the voice dataare used for E&M transitions in both directions.

• embedded – This option is similar to A/B in-band signaling. No extrabandwidth, however, is needed for the control signals. This option applies tolbr-voice only.

Analog signal level

Specifies the voice channel transmit and receive levels at the channel interface. Possiblevalues are 0/0-TLP and –16/7-TLP. The first choice is usually applicable for PBXinterfaces, while the latter is applicable to transmission equipment.

2dB via net loss

This field enables or disables a 2 dB output signal via net loss (attenuation). Enabling thissignal reduces echo caused by 2-wire to 4-wire conversion points or transmission delays.

Signal conditioning – E lead

This field is used to force the E lead active or inactive. During a disconnection (eitherintentionally caused, or caused by a failure of the link or channel group), the E lead goesinactive for 3 seconds. If this field sets the E lead active, the E lead will be forced activeto busy-out the trunk during an alarm/disconnect condition. If this field sets the E leadinactive, the E lead will be forced inactive to prevent an incoming call from ringingcontinuously after a disconnect.

Echo Cancellation

This field enables or disables echo cancellation. This field appears for lbr-voice only.


2-172 August 1994 6800-A2-GB32-10

Display Channel Configuration Results Form, Synchronous Channel, Page 3

This form is Page 3 of the results form when displaying a synchronous channel. For thetime-of-day synchronous channel, the field on this page labeled Data rate will not appear.


Data rate

Specifies the data rate for the channel. The rate is rounded to the nearest 2 kbpsincrement.

Transmit clock

Specifies the source of the transmit clock. Possible values are internal and external. Theinternal value configures the channel to generate the clock source from the channelinterface module. The external value configures the channel to obtain its clocking froman external source.

Receive clock

Specifies the source of the receive clock. Possible values are internal and external. Theinternal value configures the channel to generate the clock source from the channelinterface module. The external value configures the channel to obtain its clocking froman external source.

Rate adaption

Specifies whether rate adaption will be used on the channel. Possible values are activeand inactive.

Non-network compatible

This field only appears when Rate adaption is inactive and the Data rate is 56 kbps. Itconfigures the channel to be network-compatible, if the field is set to inactive. In thiscase, it will be possible to terminate the channel on non-74x equipment. The channel willbe allocated to a full DS0. If the field is set to active, the channel can only be terminatedon 74x equipment.

Restricted clear channel

This field only appears when Rate adaption is inactive and the Data rate is an integermultiple of 64 kbps. It configures the channel to be a restricted clear channel if set toactive. If active, the channel is treated as meeting the minimum 1’s density requirementsand will not require additional bandwidth within its channel group for data encoding. Ifinactive, the channel is treated as not meeting the minimum 1’s density requirements andadditional bandwidth may be required for data encoding.


2-1736800-A2-GB32-10 August 1994

Display Channel Configuration Results Form, Synchronous Channels, Page 4

This form is only shown for synchronous channels.


INPUT OUTPUT

This field shows the remote channel endpoint and the local channel endpoint, in theformat NxxxCyyy where xxx is the node number and yyy is the channel number.

RTS/DCD, BO/RI, DRS/DSR, and DTR/CTS

These fields are used to set the options for the mapped pairs of control signal leads.Possible values are as follows.

• in-band – The control signal lead will be transmitted with the channel group.This will require an extra 400 bps to 64 kbps of channel group bandwidth perlead. The amount is set in the In-band speed field at the bottom of the form.

• background – The control signal lead will be transmitted in the background viathe SDL. No extra channel group bandwidth is necessary since the leads are sentin time slot 1 with the SDL.



Local RTS/CTS delay

This field specifies the length of the propagation delay between the RTS and CTS leadson a synchronous data channel. This field is not applicable when an option has beenselected for DTR/CTS and will not be displayed in this case.

In-band speed

This field only appears on the form if in-band was selected for the control signal leads. Itconfigures the amount of bandwidth necessary to accommodate those leads.

RTS delay

This field only appears on the form for enhanced synchronous channel types. It specifiesthe length of the active-to-inactive transition delay of the RTS signal.


2-174 August 1994 6800-A2-GB32-10

Display Channel Configuration Results Form, Asynchronous Channels, Page 4

This form is only shown for asynchronous channels.

The fields on the Display Channel Configuration results forms are as follows.

INPUT OUTPUT

This field shows the remote channel endpoint and the local channel endpoint in the formatNxxxCyyy, where xxx is the node number and yyy is the channel number.

Data rate

Specifies the data rate for the channel.

RTS/DCD, BO/RI, DRS/DSR, and DTR/CTS

These fields are used to set the options for the mapped pairs of control signal leads. Foreach pair of leads, the following values are possible.

• in-band – The control signal lead will be transmitted with the channel group.This will require an extra 400 bps to 64 kbps of channel group bandwidth perlead. The amount is set in the In-band speed field at the bottom of the form.

• background – The control signal lead will be transmitted in the background viathe SDL. No extra channel group bandwidth is necessary since the leads are sentin time slot 1 with the SDL.



Local RTS/CTS delay

This field specifies the length of the propagation delay between the RTS and CTS leadson a synchronous data channel.

In-band speed

This field only appears on the form if in-band was selected for the control signal leads. Itconfigures the amount of bandwidth necessary to accommodate those leads.

Information/Stop bits

Sets the number of information bits and stop bits for each character. The data is shown inthe format X/Y, where X is the number of information bits (data plus parity) and Y is thenumber of stop bits. Possible values are 7/2, 8/1, 8/2, 9/1, 9/2.


2-1756800-A2-GB32-10 August 1994

Display Channel Configuration Results Form, DS0 Channels, Page 3

This form is Page 3 of the results screens when displaying a DS0 channel.


Data rate

This field always displays the value 64000bps.

Signaling format

Specifies the signaling format for the channel. Possible values are as follows.

• active – Signaling bits sent to external devices are forced active.

• clear-channel – No signal realignment or signal conditioning is generated duringerror or alarm states on the channel.

• inactive – Signaling bits sent to external devices are forced inactive.

• in-bandA – The DS0 channel connects to a voice channel that does not supportrobbed-bit signaling; during alarm conditions, the DS0 channel will usedstandard E&M signal conditioning (E lead active); an extra 400 bps ofbandwidth must be allocated for the A bit.

• in-bandA/B – (This item only appears for ADPCM DS0 channels); the DS0channel extracts the signaling bits from the external device and allocates 800 bpsof channel group bandwidth to transfer the signaling bits.

• robbed-bit – The A/B signaling bits (A/B/C/D for ESF) from selected frames ofexternal input will be extracted and reinserted into the aggregate link’s A/Bsignaling bits.

Trunk conditioning

This field only appears on forms for ADPCM DS-0 channels configured with a signalingformat of in-bandA/B. Possible values are E&M , FXO-loop, FXS-loop, FXO-ground,FXS-ground, ringdown, PLAR, and the hexadecimal codes from 00 to ff .

Time Slots

This field appears only for DS) group channels. The timeslots of the channel are specifiedby separating them with a comma, by providing a range of channels, or a combination ofthe two.


2-176 August 1994 6800-A2-GB32-10

Display Channel Configuration Results Form, DDS-dsu Channels, Page 5

This form is Page 5 of the results screens when displaying a DDS-dsu channel.


Transmit clock

Specifies the source of the transmit clock. Possible values are internal and external. Theinternal value configures the channel to generate the clock source from the channelinterface module. The external value configures the channel to obtain its clocking froman external device. The channel endpoints can use different clocking sources.

Receive clock

Specifies the source of the receive clock. Possible values are internal and external. Theinternal value configures the channel to generate the clock source from the channelinterface module. The external value configures the channel to obtain its clocking froman external device. The channel endpoints can use different clocking sources.

RTS Control Signal

Specifies whether the RTS signal should be monitored. Possible values are monitoredand assumed active. If assumed active is selected, the RTS signal will appear in theactive state.

Format

Specifies the type of DS0 signal needed for the channel. Possible values are DS0A, DS0Bbase, and DS0B subrate.

The next set of results fields will differ depending on the value of the format field. See the DS0A,DS0B, and DS0B subrate configuration forms.

Rate

Specifies the data rate, in bps, for the DDS signal. A pop-up menu displays the selections2400, 4800, 9600, 56000, and 64000.


2-1776800-A2-GB32-10 August 1994

Display Channel Configuration Results Form, DDS-ocu Channels, Page 3

This form is Page 3 of the results screens when displaying a DDS-ocu channel.


Secondary channel

Specifies whether a secondary channel is active for the diagnostic connection between thetwo DSUs. Possible values are active and inactive.

Format

Specifies the type of DS0 signal needed for the channel. Possible values are DS0A, DS0Bbase, DS0B subrate, SW56K, or E-SW56K.

The next set of results fields will differ depending on the value of the format field. See DS0A,DS0B, and DS0B subrate configuration forms.

Display Channel Configuration Results Form, DDS Channels, Page 4

This form is Page 4 of the results screens when displaying a DDS channel with DS0A format.

The field on the Display Channel Configuration results form is as follows.

Rate

Specifies the data rate, in bps, for the DS0A signal. Possible values are 2400, 4800, 9600,56000, and 64000.

Display Channel Configuration Results Form, DDS Channels, Page 3

This form is Page 3 of the results screens when displaying a DDS channel configured for DS0Bformat.


Rate

Specifies the data rate, in bps, for the DS0B base signal. Possible values are 2400, 4800,9600, and 19200.

Number of subrate channels

This field specifies the number of subrate channels to be used within the DS0B time slot.The range is dependent on the subrate selected.

Subrate channel

Specifies the subrate channel that is to be used within the DS0B time slot. An entry of 0disconnects the subrate channel from the base channel.


2-178 August 1994 6800-A2-GB32-10

Display Channel Configuration Results Form, DDS Channels, Page 3, Configured for DS0BSubrate Format

This form is Page 3 of the results screens when displaying a DDS channel configured for DS0Bsubrate format.


Rate

Specifies the data rate, in bps, for the DS0B base signal.

Base channel

Specifies the channel number that corresponds to the configured DS0B base channel.

Subrate channel

Specifies the subrate channel that is to be used within the DS0B time slot. An entry of 0disconnects the subrate channel from the base channel.

Display Channel Configuration Results Form, DDS Channels, Page 3, Configured for SW56Kor E-SW56K Format

This form is Page 3 of the results screens when displaying a DDS channel configured for SW56Kor E-SW56K format.


Rate

Shows the data rate, in bps, for the channel. This display-only field always displays avalue of 56000 bps.

Maintenance mode

Specifies whether or not the maintenance mode is configured for Switched 56K channels.Possible values are required and not required.


2-1796800-A2-GB32-10 August 1994

Display Channel Group (dscg)Use the dscg command displays the configuration and parameters of a channel group.

For a complete description of the Destination for results and Schedule execution fields, refer toChapter 1, Introduction. For an example of input and results forms, refer to the Create ChannelGroup (crcg) command.

Access Level: Help Desk, Data Technician,Manager

Abbreviation: dscg

Restrictions: None

Routine: Yes

Schedule: Yes

Related Command: Change Channel Group (chcg)Channel Group Summary (cgs)Create Channel Group (crcg)Delete Channel Group (dlcg)

Display Channel Group Input Form

The field on the Display Channel Group input form is as follows.


The user should enter the name of the channel group to be displayed. Only a singlechannel group can be entered. If the user’s channel group is not in the table an AcquireChannel Group (accg) or Create Channel Group (crcg) command should be run to correctthe database before this command can be executed for that channel group.

The following results forms will differ, based on the type of channel group endpoints.

Display Channel Group Results Form 74x-56K (56K Node), Page 1

This results form is used when at least one endpoint of the channel group is a 74x-56K node.

The fields on the Display Channel Group results form are as follows.

Endpoint nodes

This specifies the two endpoint nodes by node number for the channel group.

Capacity

Specifies the current capacity of the channel group, in bps.


2-180 August 1994 6800-A2-GB32-10

Connection state

This display-only field specifies the current connection state for the channel group. Thepossible values are as follows.







Displays the reconfiguration condition option for the channel group. If the user wants tochange this, a pop-up menu provides the selections permanent and time-of-day.Selecting time-of-day configures the channel group to connect/disconnect at preset timesof the day. Additional information for the times and connection states will be requested onan additional page of the form.

Restricted to network compatible

This field is always set to no for 74x-56K node channel groups. The 74x-56K nodechannel groups are always non-network compatible.

Serial synchronous time slot

Specifies the time slot for the channel group, if one endpoint of the channel group is a740, 741, or 742 and the other endpoint is a 74x-56K node.

Display Channel Group Results Form (non-56K node), Page 1

The Display Channel Group results form is used when neither endpoint of the channel group is a74x-56K node.

1st choice route

A channel group can be automatically routed through the network, or the route can bedefined by the user. This field displays the current routing type designated as the firstchoice for the route. Possible values are automatic and fixed.

Capacity

This field displays the amount of bandwidth allocated to the channel group, in either timeslots (nn ts), or kbps (nnnn kbps).

2nd choice route

Displays the 2nd choice routing type, if the 1st choice was fixed. If the 1st choice routewas fixed and the route fails, the multiplexer will attempt to reroute the channel group tothe 2nd choice route. Possible values are automatic, fixed, and none.


2-1816800-A2-GB32-10 August 1994

Priority

Displays the routing priority for the channel group. Possible values are as follows.




3rd choice route

Displays the 3rd choice routing type, if the 2nd choice routing type was fixed. If the 2ndchoice route was fixed, and the channel group was on the 2nd choice route and failed, themultiplexer would attempt to reroute the channel group according to the 3rd choice routeselection. Possible values are automatic and none.


Displays the reconfiguration condition option for the channel group. If the user wants tochange this, a pop-up menu provides the selections permanent and time-of-day.Selecting time-of-day configures the channel group to connect/disconnect at preset timesof the day. Additional information for the times and connection states will be requested onan additional page of the form.

Robbed bit signaling

Displays whether voice channels using robbed bit signaling will be assigned to thischannel group. Possible values are active and inactive.

Trunk conditioning

If voice channels will be assigned to this channel group, the type of trunk conditioningused by the originating PBX is displayed. Possible values are E&M , FXO-loop,FXS-loop, FXO-ground, FXS-ground, Ringdown, PLAR, and the hexadecimal codesfrom 00 to ff . This field only appears when Robbed bit signaling is active.

Network compatible

Indicates whether the channel group will be configured as network compatible. Networkcompatible channel groups are integral multiples of DS0s. Network compatible channelgroups may only contain the following types of channels: 64 kbps robbed-bit voice, 64 kbps DS0, and 56 kbps synchronous data. Several network compatible channels can beassigned to a network compatible channel group, but they must all be of the same type.Possible values are yes and no.


2-182 August 1994 6800-A2-GB32-10

IOC reroute timer

This field specifies the IOC Reroute Integration time for the channel group. This time isthe time for the node to delay before rerouting a channel group based on time slotsynchronization loss. Time is displayed in seconds, with the keyword inactive indicatingthe feature is disabled. This field will only appear on forms where both endpoints arefeature packages 3.x.x/4.x.x nodes and for which the channel group is NOT networkcompatible.

B8ZS

Specifies whether B8ZS coding is to be used for the channel group. If B8ZS is not used,ZCS (Zero Code Suppression) will be used, and an additional 8 kbps of overheadbandwidth will be taken up by the ZCS coding and not be available for user data. Possiblevalues are yes and no. This field only appears on the form when both endpoints of thechannel group are pre-feature packages 3.x.x/4.x.x nodes. Otherwise, the Clear Channelattribute in the attributes section of the Channel Group display is used to display theB8ZS configuration.


This display-only field specifies the current connection state for the channel group. Thepossible values are as follows.






Trouble code

For channel groups with 74x nodal endpoints, the trouble code is used to send in the link’stime slot instead of data, should a T1 failure occur. Possible values are trb ,mux-out-of-sync, and the hexadecimal codes from 00 to ff .

Display Channel Group Results Form (All Nodes), Page 2, (Channel Group ReconfigurationTimes)


Reconfiguration time

Specifies the times that the channel group should be connected or disconnected fortime-of-day operation. The time is specified in hh:mm format, military time.

Connection state

Specifies the connection state for the channel group at the designated reconfigurationtimes. Possible values are connect and disconnect.


2-1836800-A2-GB32-10 August 1994

Display Channel Group Results Form (Permanent Channel Groups), Page 2, (ChannelConnection Reconfiguration Times)

The field on the Display Channel Group results form is as follows.

Reconfiguration time(s)

Specifies the reconfiguration time(s) for channel groups that are permanently connected.This is used for time-of-day channels that are in the channel group, as specified in theChange Channel Configuration (chcc) command. The time is specified in hh:mm format,military time.

Display Channel Group Results Form, Page 3, (Attribute Requests)

This form only appears for channel groups terminating on at least one feature packages 3.x.x/4.x.xnode. It does not appear for serial synchronous channel groups (those terminating on a 74x-56Knode).

The field on the Display Channel Group results form is as follows.

attribute request values

For each physical and logical attribute, the attribute request is specified for the channelgroup. Possible values are as follows.


• prefer – The channel group will be routed over routes that satisfy this attribute,before selecting an alternate route that may not.



Display Channel Group Results Form (non-56K Nodes), Page 4

This form appears if the 1st choice route field was fixed. The lower half of the form appears whenthe 2nd choice route field is fixed.



This field shows the beginning node in the route – the endpoint node of the channelgroup.

Route

This field displays the channel group fixed route, node by node, link by link. Thekeyword NIDxx indicates the entry of the channel group into a foreign network. TheNIDxx specifies the foreign network ID. These IDs are specified in the facility profilesfor the T1 links connecting the nodes to foreign networks.


2-184 August 1994 6800-A2-GB32-10


See First fixed route from .

Route

See above.

Display Channel Group Results Form, Page 5, (Pass-Through)

This form shows the fixed time slot assignment for the 1st fixed route. The 2nd fixed route formwould be similar. This form only appears when the channel group is a pass-through channel group(from a 745 endpoint to a foreign network, without using logical links). There are two sets of thesefields for each NIDxx in each fixed route and one set for each side of each NID.


Node

This field shows the node number of a node adjacent to a NID in the fixed route for thechannel group.

Link

This field shows the link number at the above node for a physical T1 link connected to aNID in the fixed route for the channel group. For 731, 740, 741, or 742 nodes, the field isalways blank.

Time slots



2-1856800-A2-GB32-10 August 1994

Display Control Signals (dscs)Use the dscs command to display the current states of the control signals on 731, 740, 741, or 742 channels, 745 DS0 channels, 74x-56K channels, and 74x-56K aggregate links.



Abbreviation: dscs Alternate: dsccs

Restrictions: None

Routine: Yes

Schedule: Yes


Display Control Signals Input Form

The first page of the form is identical for all nodes. If a 74x-56K node is entered, the form changesto the to 74x-56K input form.

The fields on the Display Control Signals input form are as follows.


Enter the node for the control signal states. Only a single node and 731, 740, 741, 742,745, and 74x-56K nodes with device profiles can be entered. The user can enter the nodenumber, node name, or node device address (m2/node number).


Enter the channel number for the control signal states. Only a single channel number canbe entered. The channel number must meet one of the following validation criteria,depending on the type of node.

731 0 to 3


Y is 1 to 24 741



740-56K 0 to 127

741-56K 0 to 39




2-186 August 1994 6800-A2-GB32-10

Display Control Signals Input Form (74x-56K)

This page is displayed if the node is 74x-56K node. The user must select either an aggregate linkor a channel, but not both.

The field on the Display Control Signals input form is as follows, along with the two previousfields.

Aggregate link (Required field)

Enter the link number for the desired control signals states. A pop-up menu displays theselections 0 and 1.

Display Control Signals Results Form (Channels)

A sample Display Control Signals results form is shown in Figure 2-29.

Figure 2-29. Display Control Signals Results Form (Channels), Page 1


2-1876800-A2-GB32-10 August 1994

The fields on the Display Control Signals input form are as follows.

Input

The input control signal. Possible values are as follows.

RTS – Request-to-Send.

BO – Busy Out.

DRS – Data Rate Selector.

DTR – Data Terminal Ready.

A – Signaling bit for DS0 channels.

B – B signaling bit for DS0 channels.

C – C signaling bit for DS0 channels, extended superframe.

D – D signaling bit for DS0 channels, extended superframe.

M lead – voice channel control lead.

State

The input control signal state. Possible values are as follows.

active – The signal is active and can change in response to the output signal.

inactive – The signal is inactive and can change in response to the output signal.

forced active – The signal is always active.

forced inactive – The signal is always inactive.

not applicable – The state does not apply to this signal.

Output

The output control signal. Possible values are as follows.

DCD – Data Carrier Detect.

RI – Ring Indicator.

DSR – Data Set Ready.

CTS – Clear-to-Send.

A – Signaling bit for DS0 channels.

B – B signaling bit for DS0 channels.

C – C signaling bit for DS0 channels, extended superframe.

D – D signaling bit for DS0 channels, extended superframe.

E lead – E lead for voice channels.


2-188 August 1994 6800-A2-GB32-10

State

The output control signal state. Possible values are as follows.

active – The signal is active and can change in response to the input signal.

inactive – The signal is inactive and can change in response to the input signal.

forced active – The signal is always active.

forced inactive – The signal is always inactive.

not applicable – The state is not applicable to this signal.

Display Control Signals results form (56K Aggregate Link Interface)

The fields on the Display Control Signals results form are as follows.

Input

The input control signal. Possible values are as follows.

RTS – Request-to-Send.

DRS – Data Rate Selector.

DTR – Data Terminal Ready.

State

The input control signal state. Possible values are as follows.

active – The input signal is active and can change in response to the output signal.

inactive – The input signal is inactive and can change in response to the output signal.

Output

The output control signal. Possible values are as follows.

DCD – Data Carrier Detect.

DSR – Data Set Ready.

CTS – Clear-to-Send.

State

The output control signal state. Possible values are as follows.

active – The output signal is active and can change in response to the input signal.

inactive – The output signal is inactive and can change in response to the input signal.


2-1896800-A2-GB32-10 August 1994

Display DS0B Base Channels (dsdbc)Use the dsdbc command to provide a summary list of the configured DS0B base channels on a740, 741, or 742 multiplexer.



Abbreviation : dsdbc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: DDS Channel Performance and Status (ddscps)DDS Channel Trouble Code (ddsctc)DS0B Channel Summary (dcs)DS0B Performance and Status (dps)

Display DS0B Base Channels Input Form

The field on the Display DS0B Base Channels input form is as follows.


Enter the node for which the list of DS0B base channels is desired. Only a single nodeand 740, 741, or 742 nodes with corresponding device profiles can be entered. The usercan enter the node name, node number, or node device address (m2/node number).


2-190 August 1994 6800-A2-GB32-10

Display DS0B Base Channels Results Form, Page 1

A sample Display DS0B Base Channels results form is shown in Figure 2-30.

Figure 2-30. Display DS0B Base Channels Results Form, Page 1

The fields on the Display DS0B Base Channels results form are as follows.

Channel

The DS0B base channel number.

# Subrate Channels

The number of subrate channels associated with the DS0B base channel.

Destination Node

The node number of the channel’s destination node.

Destination Channel

The channel number of the channel’s destination channel.


2-1916800-A2-GB32-10 August 1994

Channel Group

The name of the channel group assigned to the DS0B Base channel. The value unknowndisplays if the channel belongs to a channel group that is not in the NMS database.

Connection

The connection state of the DS0B base channel. Possible values are make or break.


2-192 August 1994 6800-A2-GB32-10

Display DS-1 Channel Module Configuration (dsdcmc)Use the dsdcmc command to display the configuration of the DS-1 Channel Module of a 740, 741,or 742 multiplexer.



Abbreviation : dsdcmc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change DS-1 Channel Module Configuration (chdcmc)

Display DS-1 Channel Module Configuration Input Form

The fields on the Display DS1 Channel Module Configuration input form are as follows.

Node

Enter the node whose DS1 channel module is to be displayed. Only a single node and740, 741, or 742 nodes with device profiles can be entered. The user can enter the nodenumber, node name, or node device address (m2/node number).

DS-1 channel

Enter the DS1 channel number for the module. A pop-up menu displays a list of validDS1 channel numbers. For 740 nodes, valid DS1 channel numbers are the multiples of 8from 0 to 120. For 741 nodes, valid DS1 channel numbers are 0, 8, 16, 24, and 32 . For742 nodes, valid DS1 channel numbers are 0, 8, 16, 24.


2-1936800-A2-GB32-10 August 1994

Display DS-1 Channel Module Configuration Results Form, Page 1

A sample Display DS-1 Channel Module Configuration results form is shown in Figure 2-31.

Figure 2-31. Display DS-1 Channel Module Configuration Results Form, Page 1

The fields on the Display DS1 Channel Module Configuration results form are as follows.

Channel

The DS-1 channel designated on Page 1 of the input form.

Format

The T1 framing to be used by this module. Possible values are D4 and ESF.

Bit stuffing

The bit stuffing format to be used by this module for the T1. Possible values are B8ZSand ZCS.

Service state

The service state of the module. Possible values are active and out-of-service.


2-194 August 1994 6800-A2-GB32-10

Display Logical Link (dsll)Use the dsll command to display the configuration of an existing logical link, as stored in theNMS.

NOTE

If the NMS discovers a discrepancy between the logical linkconfiguration data stored in either endpoint node and the datastored in the NMS database, NMS automatically updates thedatabase to reflect the node(s) configuration and provides amessage informing the user of this event.

For a complete description of the Destination for results and Schedule execution, refer toChapter 1, Introduction. For an example of input and results forms, refer to the Create LogicalLink (crll) command.


Abbreviation: dsll

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Break Logical Link Connection (brllc)Change Logical Link (chll)Create Logical Link (crll)Delete Logical Link (dlll)Logical Link Summary (lls)Make Logical Link Connection (mkllc)

Display Logical Link Input Form

The fields on the Display Logical Link input form are as follows.


Enter the node whose logical link is to be displayed. Only a single node and nodenumbers and node names for 74x nodes of feature packages 3.x.x or 4.x.x can be entered.All such nodes must have device profiles. The user can also enter the node device address(m2/node number).

Logical Link (Required field)

Enter the logical link that will be displayed. Only a single logical link can be entered. Apop-up menu provides the list of logical link names and numbers that are currently in thedatabase for the given node.


2-1956800-A2-GB32-10 August 1994

Display Logical Link Results Form, Page 1

This first page only appears if the command was unsuccessful or if there is a mismatch conditionbetween the NMS and the nodes. In case of a mismatch, the NMS shows that its database has beenupdated to accurately reflect the configuration of the logical link stored at each nodal endpoint.


The fields on the Display Logical Link results form are as follows.

Logical link number

This field shows the logical link number of the logical link.

Logical link name

This field shows the user-assigned logical link name.

Node

These fields display the node numbers of the nodes at each end (endpoint 1 and endpoint2) of the logical link.

Link

These fields display the physical link number for the logical link at each nodal endpoint.

Time slots

These fields specify the time slots assigned for the logical link at each endpoint. One ormore time slots can be shown separated by spaces or commas. A range of time slots isshown by using a hyphen (-) between two time slot numbers.

Capacity

This field specifies the capacity for the logical link, in kbps.


This field shows the current connection state of the logical link.

Robbed bit signaling

This field shows the state of the robbed bit signaling feature (active, inactive) at bothendpoints of the logical link.


2-196 August 1994 6800-A2-GB32-10


These fields display the physical and logical attributes for the logical link. Physical attributes areinherited from the physical link; logical attributes were assigned to the logical link during itsconfiguration.

For the physical and logical attributes, the attribute number, name, and state are displayed. If twostates appear for a particular attribute, the two physical endpoints of the logical link show differentstates for the attribute. It is recommended that the user correct this by executing the ChangeLogical Link (chll) command to set both endpoints to the same value.


2-1976800-A2-GB32-10 August 1994

Display Multiplexer Component Configuration (dsmcc)Use the dsmcc command to display the service state of the CPU(s) in a 731, 740, 741, 742, or74x-56K multiplexer and the configuration of the expansion shelf. For 745 nodes, the service stateof the CPU(s) and TSI modules can be displayed, as well as the clock source parameters.



Abbreviation: dsmcc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change Multiplexer Component Configuration (chmcc)

Display Multiplexer Component Configuration Input Form, Page 1

The field on the Display Multiplexer Component Configuration input form is as follows.


Enter the node identity. Only a single node and 731, 74x, and 74x-56K nodes with deviceprofiles can be entered. The user can enter the node name, node number, or node deviceaddress (m2/node number).

If the designated node is a 731, 740, 741, 742, or 74x-56K node, the following results form isdisplayed.

Display Multiplexer Component Configuration (731, 740, 741, 742, 756) Results Form, Page 1

The fields on the Display Multiplexer Component Configuration results form are as follows.

CPU 0 assignment

This field displays the service state of CPU 0. Possible states are active, standby andout-of-service. The value active shows that CPU 0 is the active processor for the node.The value standby shows that CPU 0 is ready to take over operation from CPU 1 shouldCPU 1 fail. The value out-of-service shows the CPU is out-of-service, allowing theControl Processor Test (cpt) to be run.

CPU 1 assignment

This field displays the service state of CPU 1. Possible states are active, standby, andout-of-service, with the same definitions as for the CPU 0 assignment field. The valuenot equipped is displayed if the redundant CPU is not installed. The field is not displayedfor 741 and 741-56K nodes.


2-198 August 1994 6800-A2-GB32-10

Expansion shelf

This field shows whether or not the node is configured with an expansion shelf. Possiblevalues are present and absent. The value present is used to show that the node has anexpansion shelf; absent is used to show the lack of an expansion shelf.

Clock

This field indicates the source of clocking for the node. A pop-up menu displays thefollowing selections.

Internal

Clocking is provided by an internal oscillator.

External

Clocking is provided by an external device connected to the external clockconnector on the aggregate link module.

Derived

Clocking is derived from the aggregate link.

Facility

Clocking is derived from the V.35 interface on the 74x-56K node.

NOTE

External and Derived are not valid choices for 74x-56K nodes.

If the designated node is a 745 node, the following results forms appear.

Display Multiplexer Component Configuration (745) Results Form, Page 1


CPU 0 assignment

This field shows the service state of CPU 0. The possible values are active, standby, andout-of-service. The value active shows that CPU 0 is the active processor for the node.The value standby shows that CPU 0 is ready to take over operation from CPU 1 shouldCPU 1 fail. The value out-of-service shows that the CPU is out-of-service, allowing theControl Processor Test (cpt) to be run.

CPU 1 assignment

This field shows the service state of CPU 1. Possible values are active, standby, andout-of-service, with the same definitions as the CPU 0 assignment field. The value notequipped is displayed if a redundant CPU is not installed.


2-1996800-A2-GB32-10 August 1994

TSI 0 assignment

This field shows the service state of TSI module 0. Possible values are active, standby,and out-of-service. The value active shows that TSI module 0 is the active module forTSI switching. The value standby shows that TSI module 0 is ready to take overoperation from TSI module 1 should TSI module 1 fail. The value out-of-service showsthat the TSI module is out-of-service, allowing the TSI Module Test (tsimt) to be run.

TSI 1 assignment

This field shows the service state of TSI module 1. Possible values are active, standby,and out-of-service, with the same definitions as for the TSI 0 assignment field. Thevalue not equipped is displayed if a redundant TSI module is not installed.

Display Multiplexer Component Configuration (745) Results Form, Page 2


TSI clock

This field shows the type of clock used on the TSI. Possible values are as follows.

• internal – The clock source is an internal oscillator.

• external – The clock source is an external device attached to the clock connectoron the external clock interface module.


External clock source

This field displays the source of the external clock, if external was the selection for theTSI clock field. Otherwise, the field is not shown. Possible values are as follows.

• Ref 0 – The external clock source is an external bipolar interface clock.

• Ref 1 – The external clock is an external bipolar interface clock with a backup.

• Ref 2 – The external clock is an external RS-422/V.35 interface clock source.

Ref 2 speed

This field specifies the speed of the RS-422/V.35 interface clock source, if that source wasspecified as an external clock source in the External clock source field. Otherwise, thefield is not shown. Possible values are 2.048 Mbps, 1.544 Mbps, 64 Kbps, 56 Kbps.

Primary DS-1 module

This field shows the DS1 module number used as the primary clock source if the clocksource is derived. Otherwise, the field is not shown.


2-200 August 1994 6800-A2-GB32-10

Fallback 1 DS-1 module

This field displays the DS1 module number used as the first backup if the primary modulefails. Otherwise, the field is not shown.

Fallback 2 DS-1 module

This field displays the DS1 module number used as the second backup if the first fallbackand primary module fail. Otherwise, the field is not shown.


2-2016800-A2-GB32-10 August 1994

Display Network Administration Port Configuration (dsnapc)Use the dsnapc command to display the configuration of the Network Administration Ports(NAPs) on the multiplexers. The NAPs can be configured for supervisory, event log printer, orSDL use.



Abbreviation: dsnapc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change Network Administration Port Configuration (chnapc)

Display Network Administration Port Configuration Input Form, Page 1

The field on the Display Network Administration Port Configuration input form is as follows.


Enter the node identity. Only a single 731, 74x, or 74x-56K node with device profiles canbe entered. The user can enter the node name, node number, or node device address(m2/node number).

NAP (Required field)

Enter the NAP number, 1 or 2.

Display Network Administration Port Configuration Results Form (Supervisory/Event Log),Page 1

This form is displayed if the NAP type is either supervisory or event log printer. For asupervisory NAP, the NAP is connected to a terminal or to an external system port on the 6800NMS (for cut-through from the NMS to the multiplexer terminal interface). For the event logprinter , the NAP is connected to a printer for the logging of event log messages.

The fields on the Display Network Administration Port Configuration results form are as follows.

Baud rate

This field specifies the baud rate at which the port will run. Possible values are 50 bps, 75 bps, 110 bps, 134.5 bps, 150 bps, 200 bps, 300 bps, 600 bps, 1200 bps, 1800 bps, 2400 bps, 4800 bps, 9600 bps, and auto. The auto choice configures the port toautomatically adapt to input rates of 300, 1200, 2400, 4800, or 9600 bps.


2-202 August 1994 6800-A2-GB32-10

Flow control

This field configures the flow control options on the NAP. Possible values are as follows.

• none – The node does not respond to or invoke flow control on the NAP.

• XON/XOFF – The transmit-on and transmit-off characters are used for flowcontrol.

• CTS/DTR – The node drops the CTS (clear-to-send) signal to stop datatransmission from the terminal/NMS. The terminal/NMS drops the DTR (dataterminal ready) signal to stop the data transmission from the node.

Display Network Administration Port Configuration Results Form (Supervisory/Event Log),Page 2

The fields on the Display Network Administration Port Configuration results form are as follows.

Modem controls

This field determines how the asynchronous NAP treats its modem control signals. Thepossible values are as follows.

• DCE–local – The modem controls are processed locally; no end-to-end signalmapping is required. The NAP is considered active when the DTR or RTS signalis active. This is the recommended connection method.

• DCE-assume-active – The NAP is assumed to be active at all times. Only theTD, RD, and SG leads need to be connected.

• DIM/DOM – The acronym for dial-in/dial-out modem. This control allowsincoming calls to be answered and outgoing calls to be placed. The nodeperforms the local handshake with the attached modem.

• DIM/DOM-secure – This control helps to prevent unauthorized access to thenetwork by using the DIM/DOM control and causing the modem to go on-hookfor all disconnects.

Parity

This field defines the parity for the NAP. Possible values are none, odd, even, andignored.

Number of data bits

This field defines the number of data bits, not including the parity bit. Possible values are7 and 8.

Number of stop bits

This field defines the number of stop bits. Possible values are 1, 1.5, and 2.


2-2036800-A2-GB32-10 August 1994

Display Network Administration Port Configuration Results Form (SDL), Page 1

The fields on the Display Network Administration Port Configuration output form are as follows.

NAP type (SDL)

The NAP is configured as a gateway to a synchronous data link (to the node itself) so thatit can be used to provide SDL connectivity. When the NAP is configured as an SDL NAP,it is referred to as either SDL 101 (NAP 1) or SDL 102 (NAP 2).

Data rate

The speed of the NAP port is set with this field. Possible values are 1200 bps, 2400 bps,4800 bps, 9600 bps, 19200 bps, and 32000 bps.

Transmit clock

This field defines the type of transmit clock. Possible values are internal and external.

Receive clock

This field defines the type of receive clock. Possible values are internal and external.

Satellite

This field indicates if the SDL connection is over a satellite hop. Possible values areactive and inactive.


2-204 August 1994 6800-A2-GB32-10

Display Node Configuration Parameters (dsncp)Use the dsncp command to display node parameters for a single node. The parameters that can bedisplayed are as follows.

• Node date/time

• Performance data reporting

• Event logs

• Message logs

• Alarm severity reporting

• Attribute names

For a complete description of the Destination for results and Schedule execution fields, refer toChapter 1, Introduction. For an example of input and results forms, refer to the Change NodeConfiguration Parameters (chncp).


Abbreviation: dsncp Alternates: dspdr, dsmlc, dsasrc, dselprc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change Node Configuration Parameters (chncp)Display Node Connected to System (dsncp)

Display Node Configuration Parameters Input Form

The field on the Display Node Configuration Parameters input form is as follows.


Enter the node for displaying configuration parameters. Only a single node and nodenumbers and node numbers of 731, 74x, and 74x-56K nodes with device profiles can beentered. The user can also to enter the node device address (m2/node number).

Depending on the user’s entry in the Node field, the following forms will differ.


2-2056800-A2-GB32-10 August 1994

Display Node Configuration Parameters Input Form

Page 1 of the dsncp form displays the possible sets of parameters that can be displayed with thiscommand. Select yes for each set that you wish to view in detail.

The fields on the Display Node Configuration Parameters input form are as follows. (All fields aredefined in this document. However, some may not be shown for the selected node.)

Node date and time (Required field) [3 chars, default = no]

Indicates whether the node’s date and time should be displayed. A pop-up menu isavailable with entries yes and no.

Performance reporting parameters (Required field) [3 chars, default = no]

Indicates whether the node’s performance data reporting parameters should be displayed.A pop-up menu is available with entries yes and no.

Event log 1 configuration (Required field) [3 chars, default = no]

Indicates whether the node’s event log 1 configuration should be displayed. A pop-upmenu is available with entries yes and no.

Event log 2 configuration (Required field)

Indicates whether the node’s event log 2 configuration should be displayed. A pop-upmenu is available with entries yes and no.

Event log 3 configuration (Required field)

Indicates whether the node’s third event log configuration should be displayed. A pop-upmenu is available with entries yes and no.

Message log configuration (Required field)

Indicates whether the node’s message log configuration information should be displayed.A pop-up menu is available with entries yes and no.

Alarm severity reporting (Required field)

Indicates whether the node’s alarm severity reporting configuration should be displayed.A pop-up menu is available with entries yes and no.

Attribute names configuration (Required field)

Indicates whether the current attribute names of the selected node should be displayed. Apop-up menu is available with entries yes and no.


2-206 August 1994 6800-A2-GB32-10

Display Node Configuration Parameters Node Date and Time Results Form, Page 1

This form is used when the Node date and time parameters are selected from the first page.

The fields on the Display Node Configuration Parameters Node Date and Time results form are asfollows.

Node network date and time

Shows the current date and time set for the node, synchronized with all other nodes andthe NMS. This is a neutral time (meaning no time zone).

Node local date and time

Shows the current date and time set for the node, maintained locally at the node. This timewill have an assigned time zone.

NOTE

When you change the Node date and time from the Change NodeConfiguration Parameters (chncp) command, both the network andlocal date and time are reset to the time in the NMS.

Display Node Configuration Parameters Performance Data Reporting Results Form, Page 2

This form is used when the Performance Data Reporting parameters were selected from the firstpage.

The field on the Display Node Configuration Parameters Performance Data Reporting results formis as follows.

Data report and reset interval

Shows the time interval over which the statistics registers at the node will beaccumulated. They are reset at the end of the time interval. Events, if configured to bereported, are reported at the end of the time interval.

Display Node Configuration Parameters Event Log Parameters Results Forms, Pages 3, 4, 5

There are three forms used to display the configurations of event logs 1, 2, and 3. They are allsimilar in display and content and are described here.

Event log node (event log 1 or 3)

For the given event log, indicates the node number of the multiplexer to which a terminalor event log printer is connected for the display/printing of the events.

• Group (event log 1 or 3)

Shows the NAP (Network Administration Port) number for the port number to which aterminal or printer is connected, and which is configured as an event log printer NAPtype, for the display/printing of the events. For 719/72x nodes, the group number for theport is displayed, since 719/72x nodes do not have NAPs.


2-2076800-A2-GB32-10 August 1994

Node connected to system (event log 2 only)

This field indicates the node number of the multiplexer whose NAP port is configured asevent datagram and connected to the mux event port on the 6800 Series NMS. Thisconnection was configured through the Change Node Connected to System (chncs)command and the terminal interface of the multiplexer.

Group (event log 2 only)

This field indicates the NAP number of the NAP configured as event datagram andconnected to the mux event port on the 6800 Series NMS from the node indicated in theprevious field. If the node was a 719/72x NETWORKER, this Group is the 719/72xNETWORKER’s group number (since the 719/72x does not have a NetworkAdministration Port).

NOTE

In the descriptions below, event log destination refers to the NMS,when event log 2 is displayed, and to the event log nodedestination when event log 1 or 3 is displayed.

Configuration status

Shows whether configuration status alarms and events will be sent to the event logdestination via the asynchronous event reporting mechanism.

Facility alarms

Shows whether facility alarms and events will be sent to the event log destination via theasynchronous event reporting mechanism.

Node alarms

Shows whether node alarms and events will be sent to the event log destination via theasynchronous event reporting mechanism.

Node errors

Shows whether node error alarms and events will be sent to the event log destination viathe asynchronous event reporting mechanism.

System status

Shows whether system status alarms and events will be sent to the event log destinationvia the asynchronous event reporting mechanism.

Statistics

Shows whether statistics events will be sent to the event log destination via theasynchronous event reporting mechanism.


2-208 August 1994 6800-A2-GB32-10

Network call status

Shows whether network call status alarms and events will be sent to the event logdestination via the asynchronous event reporting mechanism.

Channel group accounting

Shows whether channel group accounting events will be sent to the event log destinationvia the asynchronous event reporting mechanism.

Display Node Configuration Parameters Message Log Parameters Results Form, Page 5

This form is used when the Message log configuration parameters are selected from the first page.

The fields on the Display Node Configuration Parameters Message Log Parameters results formare as follows.

Message display

Shows whether or not the messages in the node(s) message log will be deleted as you readthem (once), or only when the log reaches capacity (persistent).

Configuration status

Shows whether configuration status alarms and events will be sent to the node’s messagelog.

Facility alarms

Shows whether facility alarms and events will be sent to the node’s message log.

Node alarms

Shows whether node alarms and events will be sent to the node’s message log.

Node errors

Shows whether node error alarms and events will be sent to the node’s message log.

System status

Shows whether system status alarms and events will be sent to the node’s message log.

Statistics

Shows whether statistics events will be sent to the node’s message log.

Network call status

Shows whether network call status alarms and events will be sent to the node’s messagelog.


2-2096800-A2-GB32-10 August 1994

Channel group accounting

Shows whether channel group accounting events will be sent to the node’s message log.

Display Node Configuration Parameters Alarm Severity Reporting Parameters Results Form

This form is used when the Alarm Severity Reporting parameters were selected from the firstpage. For all the results fields described below, the following results are possible.

• audible – Enable only the audible alarm at the multiplexer for this class of alarms.

• major – Enable only the Major Alarm LEDs and rear-panel relays at the multiplexer for thisclass of alarms.

• minor – Enable only the Minor Alarm LEDs and rear-panel relays at the multiplexer for thisclass of alarms.

• audible, major – Enable both the audible alarm and the Major Alarm LEDs (Minor AlarmLEDs are disabled).

• audible, minor – Enable both the audible alarm and the Minor Alarm LEDs (Major AlarmLEDs are disabled).

• major, minor – Enable both the Major and Minor Alarm LEDs (Audible alarm is disabled).

• audible, major, minor – Enable the audible alarm and the Major and Minor Alarm LEDs.

• none – Do not enable any alarm at the multiplexer.

The following are possible facility alarm types for T1 links.

Active link out-of-service

Displays the combination of alarm reporting methods at the multiplexer node to indicatean out-of-service condition for the active link.

Active link maintenance

Displays the combination of alarm reporting methods at the multiplexer node to indicate amaintenance-level condition for the active link.

Standby link out-of-service

Displays the combination of alarm reporting methods at the multiplexer node to indicatean out-of-service condition for the standby link.

Standby link maintenance

Displays the combination of alarm reporting methods at the multiplexer node to indicate amaintenance-level condition for the standby link.

DS-1 interface channel out-of-service

Displays the combination of alarm reporting methods at the multiplexer node to indicatean out-of-service condition for a DS1 Channel Interface module on a 740.


2-210 August 1994 6800-A2-GB32-10

DS-1 interface channel maintenance

Displays the combination of alarm reporting methods at the multiplexer node to indicate amaintenance-level condition for a DS1 Channel Interface module on a 740.

Channel group out-of-service

Displays the combination of alarm reporting methods at the multiplexer node to indicate aloss of channel group synchronization at a 740 node.

Serial synchronous framing loss

Displays the combination of alarm reporting methods at the multiplexer node to indicate aloss of synchronization in 740 time slots that are terminating at 74x-56K nodes.

The following are possible facility alarm types for 56K links.

Active link hardware

Displays the combination of alarm reporting methods at the multiplexer node to indicatean out-of-service condition for the 56K aggregate link on the 74x-56K node.

Active link loss of signal

Displays the combination of alarm reporting methods at the multiplexer node to indicate aDCD or carrier loss on the 56K aggregate link on the 74x-56K node.

Active link DSU disconnect

Displays the combination of alarm reporting methods at the multiplexer node to indicatethat the DSU is not connected on the 56K aggregate link because DSR is not beingreceived at the 74x-56K node.

Active link framing loss

Displays the combination of alarm reporting methods at the multiplexer node to indicate aloss of synchronization with the 74x-56K’s remote node.

Standby link hardware

Displays the combination of alarm reporting methods at the multiplexer node to indicatean out-of-service condition for the standby 56K aggregate link on a 74x-56K node.

Standby link loss of signal

Displays the combination of alarm reporting methods at the multiplexer node to indicate aDCD or carrier loss on the standby 56K aggregate link on the 74x-56K node.

Standby link DSU disconnect

Displays the combination of alarm reporting methods at the multiplexer node to indicatethat the DSU is not connected on the 56K standby link because DSR is not being receivedby the 74x-56K node.


2-2116800-A2-GB32-10 August 1994

The following are possible node alarms.

Control processor module failure

Displays the combination of alarm reporting methods at the multiplexer node to indicate afailure of the control processor.

Power module failure

Displays the combination of alarm reporting methods at the multiplexer node to indicate afailure of a power module.

SDL timeout

Displays the combination of alarm reporting methods at the multiplexer node to indicatethe failure of an SDL connection.

Channel group routing failure

Displays the combination of alarm reporting methods at the multiplexer node to indicatethe failure of a channel group to route.

Logical link configuration mismatch

Displays the combination of alarm reporting methods at the multiplexer node to indicate amismatch between the logical link configuration at a node and the one at the other end ofthe logical link.

Aggregate link module failure

Displays the combination of alarm reporting methods at the multiplexer node to indicatethe failure of the aggregate link module at a 740 or 74x-56K node.

Aggregate T1 link loss of clock

Displays the combination of alarm reporting methods at the multiplexer node to indicate aloss of clock on the 740 aggregate link.

Aggregate link loss of transmit clock

Displays the combination of alarm reporting methods at the multiplexer node to indicate aloss of transmit clock on the 74x-56K node’s aggregate link.

Aggregate link loss of receive clock

Displays the combination of alarm reporting methods at the multiplexer node to indicate aloss of receive clock on the 74x-56K node’s aggregate link.

Channel module failure

Displays the combination of alarm reporting methods at the multiplexer node to indicatethe failure of a channel module on the 740 or 74x-56K node.


2-212 August 1994 6800-A2-GB32-10

TSI module failure

Displays the combination of alarm reporting methods at the multiplexer node to indicatethe failure of a TSI module at a 745 node.

TSI clock out-of-limits

Displays the combination of alarm reporting methods at the multiplexer node to indicatean out-of-limits condition with a TSI clock at a 745 node.

TSI clock out-of-range

Displays the combination of alarm reporting methods at the multiplexer node to indicatean out-of-range condition with a TSI clock at a 745 node.

Single TSI clock reference failure

Displays the combination of alarm reporting methods at the multiplexer node to indicatethe failure of a single TSI clock reference at a 745 node.

All TSI clock reference failure

Displays the combination of alarm reporting methods at the multiplexer node to indicatethe failure of all the TSI clock references at the 745 node.

DS-1 module failure

Displays the combination of alarm reporting methods at the multiplexer node to indicatethe failure of a DS1 module at a 745 node.

PC Bus Failure

Displays the combination of alarm reporting methods at the multiplexer node to indicatethe failure of the PC Bus at a 745 node.

Display Node Configuration Parameters Attribute Names Results Form, Page 8

This form is displayed when the Attribute names configuration item was selected from the firstpage of the command.

This form shows the NMS values for the six physical and six logical attributes. When the form isdisplayed, NMS checks the values of the names at the given node. If any names are inconsistentwith those at the node, they are indicated by displaying the differing node value with ** to the leftand right.


2-2136800-A2-GB32-10 August 1994

Display Node Connected to System (dsncs)Use the dsncs command to list the multiplexer nodes that are directly connected to the 6800 SeriesNMS’s multiplexer event port interface and multiplexer command port interface. These interfacesare used, respectively, to transmit alarms and events asynchronously to the NMS and to send orreceive command requests and results between the NMS and the multiplexer nodes.

The node connected to the event port interface must have its NAP configured as event datagramtype. This can only be done through the terminal interface of the node. See Chapter 2 of theCOMSPHERE 6800 Series Network Management System Multiplexer Management andConfiguration Guide for further information.

The node connected to the command port interface must have its NAP configured as eventdatagram type. This can only be done through the T1 link of a node. See Chapter 2 of theCOMSPHERE 6800 Series Network Management System Multiplexer Management andConfiguration Guide for further information.

The third interface between the NMS and the multiplexer network is the cut-through interface.The NMS does not need to keep a record of the node number of this multiplexer, so it is notdisplayed by this command.

The port configurations of the NMS for the three multiplexer network interfaces are configured atinstallation and can be viewed through the Edit Port Configuration (edpc) and Display PortConfiguration (dspc) commands.

The node connected to the event port is the node that is displayed in the Change NodeConfiguration Parameter (chncp) command when the user is configuring the multiplexer event log 1.



Abbreviation: dsncs

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change Node Connected to System (chncs)Display Node Configuration Parameters (dsncp)Display Port Configuration (dspc)

Display Node Connected to System Input Form

The input form for this command only displays the Destination for results and Scheduleexecution fields.


2-214 August 1994 6800-A2-GB32-10

Display Node Connected to System Results Form

The fields on the Display Node Connected to System results form are as follows.

(Event Log Interface:) Node

Shows the node that is connected to the NMS’s event port.

(Event Log Interface:) Group

If the node above is 74x or 74x-56K node, the Group number displayed is the NAPnumber of the NAP configured as an event datagram type and connected to the NMS’sevent port. If the node above is a 719/72x node, the Group number displayed is thenumber of the group that contains the 719/72x channel connected to the NMS’s eventport.

(Command Language Interface:) Node

Shows the node that is connected to the NMS’s command language port.


2-2156800-A2-GB32-10 August 1994

Display Physical Link Configuration (dsplc)Use the dsplc command to display the configuration of the T1 links of a 731, 74x, or a 74x-56Knode.

All the parameters of the link are displayed with this command, including, redundancy, lineencoding, physical attributes, and alarming options.

This command also can be used to display the service state of the links and the service state of a745’s DS1 modules.

You can display both links on a T1 facility with this command.

For a complete description of the Destination for results and Schedule execution fields, refer toChapter 1, Introduction. For an example of input and results forms, refer to the Change PhysicalLink Configuration (chplc) command.


Abbreviation: dsplc Alternate: dstlc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change Physical Link Configuration (chplc)

Display Physical Link Configuration Input Form, Page 1

The fields on the Display Link Configuration input form are as follows.

Facility name (fac-) [15 chars, no default]

The facility name, as found in the facility profile tables, can be used to specify the link(s)to be displayed. If the facility name is entered, the node and link information will bedetermined from the facility profile data. If the node and link information is entered, thefacility name will be determined, if a facility profile has been created for that link.Uppercase characters entered here are converted to lowercase.


Enter the node and link instead of a facility. For the node, all 731, 74x, and 74x-56Knodes with device profiles can be entered. The user can enter the node number, nodename, or node device address (m2/node number).


This field identifies the link to be displayed. A pop-up menu is available. If the node wasa 731, 740, 741, 742, or 74x-56K node, the field is automatically populated with thenumber 0, and that is the only entry in the menu list. If the node was a 745, the menu listwill contain the values 0 to 15. Once the user enters a node and link number, the NMSwill look for a matching facility profile. If one is found, the facility name will bepopulated (or changed) on the form.


2-216 August 1994 6800-A2-GB32-10

The following results forms will differ, based on:

• If the links are T1 or 56K/64K links.

• The feature package of the nodes.

• The type of node to which the links are configured as connected.

Display Physical Link Configuration Results Form (731, 740, 741, 742, or 745 Nodes), Page 1

The fields on the Display Physical link Configuration results form are as follows.

Node/link

Shows the node number and link number of the nodes at each end of the facility.

Model

Shows the model number of the nodes at each end of the facility.

Connected to

Indicates whether the link is connected to other or to a series 700 device. Other meansthe link is connected to a foreign (non-Series 700) network.

Link redundancy

Displays the link redundancy type for the link. Possible values are as follows.

• dual – Configures the link for dual link redundancy. (For 740-chassis nodes, twoT1 aggregate link modules are connected to two separate T1 lines. For 745 nodes, two DS1 modules are connected to two separate T1 lines.)

• single – Configures the link for single link redundancy. (For 740 nodes, two T1 aggregate link modules are connected to a single T1 line. For 745 nodes, twoDS1 modules are connected to a single T1 line.) Single can also mean noredundancy for 741 and 742-chassis nodes. If the Link 0 state field displaysnot equipped, there is no redundancy for that link.

• none – For 731, 742, and 745 nodes, none configures the link for no redundancy.(A single DS1 module is connected to a single T1 line.)

• infinite – Indicates the channel group should never re-route due to thiscondition.

Redundant DS-1

Shows the module number of the redundant DS1 module, if dual or single was selectedfor the link redundancy field.

Link 0 state

Displays the state of aggregate link 0 on a 731, 740, 741, or 742 node.


2-2176800-A2-GB32-10 August 1994

Primary module state

Displays the state of the primary DS1 module on a 745 link.

Link 1 state

Displays the state of aggregate link 1 on a 740 node.

Redundant module state

Displays the state of the redundant DS1 module on a 745 link.

Format

Specifies the framing format of the T1 link. Possible values are D4 and ESF.

CRC6 state

Shows whether there is error checking on the data as it passes through the 745 node.

Red alarm integration time

Displays the number of seconds to delay before the multiplexer will initiate a red alarmlevel alarm for the T1 link due to loss of synchronization.

Reroute delay trigger

Displays the number of seconds to delay before the multiplexer will trigger a re-routerequest to channel groups because of the failure of the T1 link.

Display Physical Link Configuration Results Form (74x Nodes), Page 2

This form is used for the second page of the configuration.

The fields on the Display Physical Link Configuration results form are as follows.

Line encoding

Displays the method of bit stuffing to be used on the T1 link. Possible values are asfollows.

• ACAMI – Alternate Channel Alternate Mark Inversion is a line-encodingscheme that permits clear channel data to be transmitted over a ZCS-coded line.

• B8ZS – Bipolar 8 Zeroes Substitution is a line-encoding scheme that allowsclear channel data to be transmitted over a T1 line.

• ZCS – Zero Code Suppression is a line-encoding scheme that uses 8 kbps ofbandwidth to force the T1 data to meet the T1 line’s 1’s density requirement.

Number of clear time slots

If ACAMI was configured for the Line encoding field, this field appears displaying thenumber of time slots needed for the ACAMI application (clear channels).


2-218 August 1994 6800-A2-GB32-10

The following pertains to 56K/64K serial synchronous applications.

Time slots

For 740 links that carry channel groups that will terminate on a 74x-56K node, the timeslots that will be used for these channel groups must be configured as serial synchronoustime slots on the 740 link. This field specifies the list of such time slots. The time slots areindicated by specifying individual time slots, separated by spaces or commas, or a rangeof time slots.

Framing loss integration

If the 740 link has time slots that are used to carry a channel group terminating at a74x-56K node, this field specifies the framing loss integration time for these 56K/64Kserial synchronous time slots. This integration time represents the amount of time thenode must have lost synchronization before the resynchronization algorithm begins.

Alarm threshold

If the 740 link has time slots that are used to carry a channel group terminating at a74x-56K node, this field specifies the framing loss alarm threshold time for these56K/64K serial synchronous time slots. This threshold time represents the time a nodemust have lost synchronization before generating a framing loss alarm. The keyworddisable indicates that the feature is turned off.

Display Physical Link Configuration Results Form (74x Nodes), Page 3

This form is the third page of the configuration form.

The field on the Display Physical Link Configuration results form is as follows.

PHYSICAL ATTRIBUTES

For each of the 6 physical attributes, these fields set the attribute to active or inactive, asprovided by a pop-up menu selection. The Clear Channel attribute is display-only, and isdetermined by the value of the Line encoding field. A value of B8ZS will set the ClearChannel attribute to active for the T1 link. All attributes are set to inactive as a default.

Display Physical Link Configuration Results Form (74x-56K Nodes), Page 1

The fields on the Display Physical Link Configuration results form for 74x-56K nodes are asfollows.

Node/link

Shows the node number and link number of the nodes at each end of the facility.

Model

Shows the model number of the nodes at each end of the facility.


2-2196800-A2-GB32-10 August 1994

Speed

Shows the speed (rate) of the aggregate link. Possible values are 56Kbps and 64Kbps.

Connect to

Shows the type of node at which the aggregate link terminates. Possible values are:

• T1/E1 – Terminates at a time slot of a 740 node.

• non-T1/E1 – Terminates at another 74x-56K node.

Link Redundancy

Displays the link redundancy type for the link. Possible values are:

• dual – For 740-chassis nodes, dual configures the link for dual link redundancy.(Two aggregate link modules are connected to two separate lines.)

• single – Configures the link for single link redundancy. (Two aggregate linkmodules are connected to a single line.) Single can also mean no redundancyfor 741 and 742-chassis nodes. If the Link 0 state field displays not equipped,there is no redundancy for that link.

Link 0 state

Displays the state of aggregate link 0 on a 74x-56K node.

Link 1 state

Displays the state of aggregate link 1 on a 74x-56K node.

Link 0 receive clock

Displays the receive clock source of aggregate link 0. Possible values are:



Link 1 receive clock

Displays the receive clock source of aggregate link 1. Possible values are:



Link 0 transmit clock

Displays the transmit clock source of aggregate link 0. Possible values are:




2-220 August 1994 6800-A2-GB32-10

Link 1 transmit clock

Displays the transmit clock source of aggregate link 1. Possible values are:



Display Physical Link Configuration Results Form (74x-56K nodes), Page 2

The fields on the Display Physical Link Configuration results form for 74x-56K nodes are asfollows.

Link 0 interface type

Displays the interface type of aggregate link 0. Possible values are V.35, V.11, DSU.

Link 1 interface type

Displays the interface type of aggregate link 1. Possible values are V.35, V.11, DSU.

Link 0 sealing current

Displays whether or not to source sealing current to the loop for aggregate link 0. Thisfield is only displayed if the interface type is DSU. Possible values are terminate andsource.

Link 1 sealing current

Displays whether or not to source sealing current to the loop for aggregate link 1. Thisfield is only displayed if the interface type is DSU. Possible values are terminate andsource.

Framing loss integration

This integration time represents the amount of time the node must have lostsynchronization before the resynchronization algorithm begins.

Alarm threshold

This threshold time represents the time a node must have lost synchronization beforegenerating a framing loss alarm. The keyword disable indicates that the feature is turnedoff.

Loopback timeout

Displays a timeout value for menu-invoked loopbacks. After the specified time period, theloopbacks will be turned off. A value of 0 disables the loopback timeout feature.Otherwise, values can be between 1 and 60 minutes, in 1 minute increments.


2-2216800-A2-GB32-10 August 1994

Display Routing Table (dsrt)Use the dsrt command to display part or all of the routing table for a specified node.

NOTE

You may also use the Manage Routing Table Utility to do the samefunctions provided in this command. See the COMSPHERE 6800Network Management System Multiplexer Management andConfiguration Guide.

A routing table is maintained at each multiplexer node to specify an ordered set of links or logicallinks that can be used to reach any specified destination node. The links specified are the next linksin the route to arrive at that destination, as opposed to the entire path to reach that destination. Therouting tables are used to determine how to route both user and supervisory data.

The routing table consists of one routing table entry per specified nodal destination (up to 249) inthe network. The NMS provides the capability to generate default entries for the routing table.Each entry uses a comma-delimited list of link numbers (either physical or logical). The node triesthe first link in the list when attempting to reach the given destination. If the attempt fails on thatlink, the next one tries. Link alarms are ignored during the attempts to reach a destination. That is,the node does not check first for existing alarms before attempting to use a link in the table.

For a complete description of the Destination for results and Schedule execution fields, refer toChapter 1, Introduction. For an example of input and results forms, refer to the Change RoutingTable (chrt) command.

Access Level: Help Desk, Data Technician, System Administrator

Abbreviation: dsrt

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change Routing Table (chrt)Generate Routing Table (grt)Channel Group Summary (cgs)Channel Group Trace (cgt)Time Slot Summary (tss)


2-222 August 1994 6800-A2-GB32-10

Display Routing Table Input Form

The fields on the Display Routing Table input form are as follows.


Enter the node whose routing table you want to display. Only a single node and a 731,74x, or 74x-56K node can be entered. All such nodes must have a device profiles. Theuser may also enter the node name, node number, or node device address (m2/nodenumber).

Destination node(s) (Required field)

A subset of the routing table can be displayed by restricting the display of the table toonly those entries for specific destination nodes. Multiple destinations can be specified byproviding the node number or node name of each destination. Each entry must beseparated from another by a comma or space. The keyword all can be used to specify thatthe complete routing table for the node is to be displayed. To request the default routingentry for display, use the keyword default as one of the nodal entries. (The default entryis used by the node when a destination is requested for which no routing table entryexists.) Wildcard characters, device addresses, network names, circuit names can also beused to specify a group of destination nodes. Nodes must have device profiles.

Display Routing Table Results Form

The fields on this results form are described as follows.

Destination node

The node numbers of the destination nodes requested from the input form. Nodes musthave device profiles.

Links

The ordered list of physical links, logical links, and external SDLs that can be used by thenode to route traffic to the destination node.


2-2236800-A2-GB32-10 August 1994

Display Supervisory Data Link Configuration (dssdlc)Use the dssdlc command to display the configuration of embedded SDLs and synchronous SDLs.

This command displays a list of all time slots on a particular T1 link, with their currentconfiguration. The user can select a time slot, then display its SDL configuration, if applicable.

For a complete description of the Destination for results and Schedule execution fields, refer toChapter 1, Introduction. For an example of input and results forms, refer to the ChangeSupervisory Data Link Configuration (chsdlc) command.


Abbreviation: dsesdlcAlternate: dssdlc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change SDL Configuration (chsdlc)Display Channel Configuration (dscc)

Display Supervisory Data Link Configuration Input Form, Page 1

The fields on the Display Supervisory Data Link input form are as follows.


Enter the node identity. Only a single node and node numbers and node names for 731,74x, and 74x-56K nodes that have corresponding device profiles can be entered. The usercan enter the node device address (m2/node number).

If the node is a 745 node, the Link field appears.


Enter the link number on which the SDL is going to be displayed. Only a single link canbe entered. A pop-up menu for 745 nodes displays the integers 0 to 15.


2-224 August 1994 6800-A2-GB32-10

Display Supervisory Data Link Configuration Input Form, Page 2

The second page of the input form displays the first 10 time slots on the T1 link, with their SDLconfigurations. Pages 3 and 4 display similar information for time slots 11 to 20 and 21 to 24,respectively. These pages correspond to the results normally returned from a Time Slot Summary(tss) command request. The form for a 745 node follows. This page is not displayed for 74x-56Knodes, as there is only a single time slot for such a node.

The fields on the Display Supervisory Data Link Configuration input form are as follows.

Time Slot Selection

This field lists each time slot (1 to 24) on the T1 link, along with a selection request of yesor no. The user selects a single time slot for SDL configuration display by changing thedesired time slot selection value to yes. A pop-up menu displays with the selections yesand no. Only one time slot may be selected. (All other time slot selection fields willbecome uneditable.) If additional time slots need to be displayed for SDLs, the commandshould be re-initiated. The default value for each time slot is no.

Channel Group

This display-only field shows the channel group, if any, currently allocated to the timeslot. A blank implies that no channel group is allocated to the time slot.

Ser Synch

This display-only field shows if the time slot is currently configured as a serialsynchronous time slot, connecting the 731, 740, 741, or 742 time slot to a 74x-56K node.If the time slot needs to be reconfigured, the Change Physical Link Configuration (chplc)command must be used.

Time Slot Format

This display-only fields shows the current configuration for the time slot. The possiblevalues are the following.

• emb SDL – The time slot is currently carrying an embedded SDL, Only oneembedded SDL can be configured per T1 link.

• synch – The time slot is currently carrying a synchronous SDL (not valid for745s).

• filler – The time slot is being used for ACAMI filler byte data. Adjacent timeslots are carrying clear channel data. Filler time slots cannot be configured forembedded or synchronous SDLs. If this time slot needs to be reconfigured withrespect to ACAMI, the Change Physical Link Configuration (chplc) commandmust be used.


When configuring a synchronous SDL, all channel groups on the link must be idle. Youcan only change this field if its current value is none. If the current value is emb SDL, itcannot be changed to synch SDL unless the embedded SDL state is changed toout-of-service first. The same is true when changing a time slot from synch SDL formatto emb SDL format.


2-2256800-A2-GB32-10 August 1994

Synch SDL Channel

This display-only field shows the channel number being used for the synchronous SDL, ifthe time slot is configured for this type of SDL.

Once the user selects a time slot (by changing the Time Slot Selection field for theselected time slot to the value yes, and the Format is selected or set at synch SDL, theSynch SDL Channel field can be edited, allowing the user to change to select the channelto be configured as a synchronous SDL channel. The channel number entered must be avalid synchronous channel installed on the node. An error message will be displayed if itis not valid.

Logical Link

This display-only field shows the logical link allocated to this time slot.

Additional fields displayed for a 745 node are as follows.

Endpoints

This display-only field shows the node numbers of the endpoints of the channel group onthe time slot.

DS-0 Endpoint Node/Channel


Cross-Connect

If the time slot is cross-connected to another time slot on the 745 node, the link and timeslot to which it is cross-connected is displayed here. It is shown in the format XtsY, whereX is the link number and Y is the time slot number.

State

This display-only field shows the service state of the time slot. One of the followingvalues is shown.





Once the user selects an SDL time slot to display by selecting yes in the Time Slot Selection field,the user presses F2(Go) and the results form appears. For 74x-56K nodes, this first step ofselecting a time slot is omitted, since only one time slot exists. For other nodes, either theembedded SDL form is displayed or the synchronous SDL form is displayed, depending on theSDL configuration.


2-226 August 1994 6800-A2-GB32-10

Display Supervisory Data Link Configuration (Embedded SDL) Results Form, Page 1

The fields on the Display Supervisory Data Link Configuration results form are as follows.

SDL state

This field is used to display the state of the embedded SDL, either active orout-of-service.

Time slot

This display-only field shows the selected time slot. This field shows the node number ofthe node connected to the given node via the SDL.

Satellite

This field is used to show if the SDL is being routed over a satellite hop, making the useof additional delay parameters necessary.

SDL rate

This field is used to display the speed of the embedded SDL.

Remote node

This field shows the node number of the node connected to the given node via the SDL.

Remote link

This field shows the link number of the node connected to the given node via the SDL.

Display Supervisory Data Link Configuration (Synchronous SDL) Results Form, Page 1

The fields on the Display Supervisory Data Link Configuration results form are as follows.

Time slot

This display-only field shows the selected time slot.

SDL rate

This field is used to display the speed of the synchronous SDL.

SDL state

This field is used to display the state of the synchronous SDL, either active orout-of-service.

Channel state

This field is used to display the state of the channel being used for the synchronous SDL,either active or out-of-service.


2-2276800-A2-GB32-10 August 1994

More configuration information for the synchronous SDL is displayed on the next page of theresults form.

Transmit Clock

This field is used to display the source for the transmit clock for the synchronous SDLchannel, either internal or external.

Receive Clock

This field is used to display the source for the receive clock for the synchronous SDLchannel, either internal or external.

RTS/DCD

This field is used to display the option for the RTS/DCD control lead on the synchronousSDL channel, either active or inactive.

BO/RI

This field is used to display the option for the BO/RI control lead on the synchronousSDL channel, either active or inactive.

DRS/DSR

This field is used to display the option for the DRS/DSR control lead on the synchronousSDL channel, either active or inactive.

DTR/CTS

This field is used to display the option for the DTR/CTS control lead on the synchronousSDL channel, either active or inactive.


2-228 August 1994 6800-A2-GB32-10

Display T1 Interface Status (dstis)Use the dstis command to display the current status of 731, 740, 741, or 742 aggregate linkinterface modules and 745 DS1 interface modules.



Abbreviation: dstis

Restrictions: None

Routine: Yes

Schedule: Yes


Display T1 Interface Status Input Form

The fields on the Display T1 Interface Status input form are as follows.


Enter the node identity. Only a single node and 731, 74x nodes that have correspondingdevice profiles can be entered. The user can enter the node name, node number, or nodedevice address (m2/node number).


Enter the link number whose interface status will be obtained. Only a single link can beentered. A pop-up menu displays the numerical list 0 and 1 for 740 nodes, 0 for 731, 741,and 742 nodes and 0 to 15 for 745 nodes.


2-2296800-A2-GB32-10 August 1994

Display T1 Interface Status Results Form, Page 1

A sample Display T1 Interface Status results form is shown in Figure 2-32.

Figure 2-32. Display T1 Interface Status Results Form, Page 1

The fields on the Display T1 Interface Status results form are as follows.

Module type

Displays either aggregate link interface for 731, 740, 741, or 742 nodes or DS-1interface for 745 nodes.

Keep alive pattern

Possible values are unframed all 1’s, framed all 1’s, and regenerative line loopback.

Span power status

Shows if the interface module derives its power from the facility. Possible values areactive and inactive.

Test jack state

Shows if a test jack is in use. Possible values are no inserted data and inserted data.


2-230 August 1994 6800-A2-GB32-10

Interface type

Indicates whether the interface module is an intra-office type or a CSU. Possible valuesare as follows.

• intra-office – The interface module is an intra-office module.

• CSU – The interface module is a CSU.

Line length

The length of the cable connecting the interface module to the T1 cable. For CSUinterfaces, the length is shown as 0–1000, 1001–2000, or 2001–4000. For intra-officeinterfaces, the length is shown as 0–85, 86–400, or 401–655.


2-2316800-A2-GB32-10 August 1994

DS0B Channel Summary (dcs)Use the dcs command to summarize the DDS subrate channels for a DS0B base channel.



Abbreviation: dcs

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: DDS Channel Performance and Status (ddscps)DDS Channel Trouble Codes (ddsctc)Display DS0B Base Channel (dsdbc)DS0B Performance and Status (dps)

DS0B Channel Summary Input Form

The fields on the DS0B Channel Summary input form are as follows.


Enter the node identity. Only a single node and 740, 741, or 742 nodes that havecorresponding device profiles can be entered. The user can enter the node name, nodenumber, or node device address (m2/node number).

DS0B channel (Required field)

Enter one of the DDS channels that is to be included in the summary. Any of the subratechannels, or the base channel can be entered. Channels must be in the ranges shownbelow.

740 0 to 127

741 0 to 39

742 0 to 31


2-232 August 1994 6800-A2-GB32-10

DS0B Channel Summary Results Form

A sample DS0B Channel Summary results form is shown in Figure 2-33.

Figure 2-33. DS0B Channel Summary Results Form, Page 1

The fields on the DS0B Channel Summary results form are as follows.

Base channel

The channel number of the DDS channel that is configured as the DS0B base channel.

# subrate channels

The number of subrate channels associated with the DS0B base channel.

Connection

The connection state of the DS0B base channel. Possible values are make or break.

Dest node

The node number of the remote channel endpoint.

Dest channel

The channel number of the remote channel endpoint.

Channel group

The channel group assigned for the DS0B base channel.


2-2336800-A2-GB32-10 August 1994

Subrate

The subrate numbers associated with the DS0B base channel.

Channel

The channels numbers of each subrate channel.

Type

The type of DDS channel. Possible values are dsu and ocu.

Data rate

The speed of the DDS subrate channel.

Secondary channel

Indicates whether there is a configured secondary channel for the subrate channel.Possible values are active and inactive.

Channels without connected subrates follow at the end of the display.


2-234 August 1994 6800-A2-GB32-10

DS0B Performance and Status (dps)Use the dps command to summarize the performance statistics for DS0B channels at a node.



Abbreviation: dps

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: DDS Channel Performance and Status (ddscps)DDS Channel Trouble Codes (ddstc)Display DS0B Base Channel (dsdbc)DS0B Channel Summary (dcs)

DS0B Performance and Status Input Form

The field on the DS0B Performance and Status input form is as follows.


Enter the node identity. Only a single node and 740 or 741 nodes that have correspondingdevice profiles can be entered. The user can enter the node name, node number, or nodedevice address (m2/node number).


2-2356800-A2-GB32-10 August 1994

DS0B Performance and Status Results Form, Page 1

A sample DS0B Performance and Status results form is shown in Figure 2-34.

Figure 2-34. DS0B Performance and Status Results Form, Page 1

The fields on the DS0B Performance and Status results form are as follows.

Elapsed time since last reset

The amount of time since the statistics registers were last reset. If there are no DS0Bchannels at the node, a system message will display indicating this, and the field willremain blank.

DS0B #

The channel number of the DDS channel that is configured as the DS0B channel.

Errored seconds

The number of seconds in which the DS0B was out-of-frame.

Framing Losses

The number of times the DS0B framing made a transition from in-frame to out-of-frame.

Framing Status

The value alarm active indicates that a continuous DS0B out-of-frame condition hasexisted for at least 4 seconds. The value in frame indicates that the DS0B is in frame.


2-236 August 1994 6800-A2-GB32-10

DS-1 Channel Loopback (dcl)Use the dcl command to put a DS1 channel module on a 740, 741, or 742 node into internalloopback or to release the module from loopback.

If the user has permission for the Change DS-1 Channel Module Configuration (chdcmc)command, the NMS will automatically take the DS1 channel module out-of-service, in order toplace the module into loopback. This has the effect of putting all the DS0 channels on the moduleout-of-service. When the loopback is released, the DS0 channel module is placed back into serviceand the DS0 channels remain out-of-service. The user must execute the Change ChannelConfiguration (chcc) command to place them back into service.



Abbreviation: dcl

Restrictions: None

Routine: Yes

Schedule: Yes


DS-1 Channel Loopback Input Form, Page 1

The fields on the DS-1 Channel Loopback input form are as follows.


Enter the node whose DS1 channel module is to be looped back (or released fromloopback). Only a single node and 740, 741, or 742 nodes with device profiles can beentered. The user can enter the node number, node name, or node device address(m2/node number).

DS-1 base channel (Required field)

Enter the DS1 base channel number for the module. A pop-up menu displays a list ofvalid DS1 channel numbers. For 740 nodes, valid DS1 channel numbers are the multiplesof 8 from 0 to 120. For 741 nodes, valid DS1 channel numbers are 0, 8, 16, 24, 32. For742 nodes, valid DS1 channel numbers are 0, 8, 16, 24.

Loopback state (Required field)

Shows whether the loopback is to be started or stopped. A pop-up menu displays theentries start and stop.


2-2376800-A2-GB32-10 August 1994

DS-1 Channel Loopback Input Form (Confirmer), Page 1

This form is displayed if there are active DS0 channels on the specified module, and the user haspermission to execute the Change DS-1 Channel Module Configuration (chdcmc) command. If theuser does not have permission, the following form is displayed.

DS-1 Channel Loopback Input Form (Permission), Page 1

The user must cancel the command in this situation.

DS-1 Channel Loopback Results Form

The DS-1 Channel Loopback results form displays a success or failure message.


2-238 August 1994 6800-A2-GB32-10

DS-1 Channel Module Test (dcmt)Use the (dcmt) command to test the DS1 channel module hardware on a 740, 741, or 742.

If the user has permission for the Change DS-1 Channel Module Configuration (chdcmc)command, this command automatically takes the DS0 channels on the specified moduleout-of-service, in order to place the module into loopback. When the test is complete, the DS1channel module is placed back into service, and the DS0 channels remain out-of-service. The usermust execute the Change Channel Configuration (chcc) command to place them back into service.



Abbreviation: dcmt

Restrictions: None

Routine: Yes

Schedule: Yes


DS-1 Channel Module Test Input Form

The fields on the DS-1 Channel Module Test input form are as follows.


Enter the node whose DS1 channel module hardware is to be tested. Only a single nodeand 740, 741, or 742 nodes with device profiles can be entered. The user can enter thenode number, the node name, or the node device address (m2/node number).

DS-1 base channel (Required field)

Enter the DS1 base channel number for the module. A pop-up menu displays a list ofvalid DS1 channel numbers. For 740 nodes, valid DS1 channel numbers are the multiplesof 8 from 0 to 120. For 741 nodes, valid DS1 channel numbers are 0, 8, 16, 24, 32. For742 nodes, valid DS1 channel numbers are 0, 8, 16, 24.


2-2396800-A2-GB32-10 August 1994

DS-1 Channel Module Test Input Form (Confirmer), Page 1

This form is displayed if there are active DS0 channels on the specified module, and the user haspermission to execute the Change DS-1 Channel Module Configuration (chdcmc) command. If theuser does not have permission, the following form is displayed.

DS-1 Channel Module Test Input Form (Permission), Page 1


DS-1 Channel Module Test Results Form, Page 1

The DS-1 Channel Module Test results forms displays a success or error message.


2-240 August 1994 6800-A2-GB32-10

Equipment Performance Report (epr)Use the epr command to summarize the performance of the equipment of a multiplexer node.


Access Level: Help Desk, Data Technician, Manager, System Administrator

Abbreviation: epr

Restrictions: None

Routine: Yes

Schedule: Yes


Equipment Performance Report Input Form

The field on the Equipment Performance Report input form is as follows.


Enter the node identity. Only a single node and 731, 74x, and 74x-56K nodes that havecorresponding device profiles can be entered. The user can enter the node name, nodenumber, or node device address (m2/node number).

Equipment Performance Report Results (731, 740, 741, 742) Form, Page 1

The fields on the Equipment Performance Report results form are as follows.

Data reset interval

The rate at which the statistics registers are reset. This interval is configured within thePerformance Data Reporting parameters of the Change Node Configuration Parameters(chncp) command.


The time elapsed since the last reset of the statistics registers.

Equipment

The equipment on which alarms are reported.


2-2416800-A2-GB32-10 August 1994

Number of Alarms

The number of alarms that have occurred since the statistics registers were last reset aredisplayed for each equipment category. The equipment categories for the 731, 740, 741,or 742 nodes are as follows.

• Control processor 0 failure – The alarms on the CPU 0.

• Control processor 1 failure – The alarms on the CPU 1.

• Aggregate link 0 failure – The alarms on the aggregate link 0.

• Aggregate link 1 failure – The alarms on the aggregate link 1.

• Aggregate link 0 loss of clock – Loss of clock alarms on aggregate link 0.

• Aggregate link 0 loss of receive clock – Transmit link 1 receive transmit;applicable only to 74x-56K.

• Aggregate link 1 loss of clock – Loss of clock alarms on aggregate link 0.

• Power module failure – The alarms on the power modules.

• Channel module failure – The alarms on the channel modules.

NOTE

The statistics registers at a node for equipment alarms are largeenough to accommodate 65,535 errors. If the statistics registersoverflow (a value exceeding 65,535 errors), the following messageis displayed in place of a numeric value:

register overflow


2-242 August 1994 6800-A2-GB32-10

Equipment Performance Report (74x-56K) Results Form, Page 1

A sample Equipment Performance Report results form is shown in Figure 2-35.

Figure 2-35. Equipment Performance Report (74x-56K) Results Form, Page 1

Equipment Performance Report (745) Results Form, Page 1

The equipment categories for 745 nodes are as follows.

• TSI 0 failure – The alarms on the TSI module 0.

• TSI 1 failure – The alarms on the TSI module 1.

• Single TSI clock reference failure –The alarms that occur on a single TSI clock reference.

• All TSI clock reference failure – The alarms that occur, simultaneously, on all TSI clockreferences.

• TSI clock out of limits –The out-of-limits alarms on the TSI clocks.

• TSI clock out of range – The out-of-range alarms on the TSI clocks.

Additional equipment categories for the 745 nodes that appear on the second page are as follows.

• DS-1 module failure – The alarms on the DS-1 modules.

• Current number of failed DS-1 modules – The current number of DS1 modules in analarm condition.

• PC bus 0 failure – The alarms on the PC buses.

• PC bus 1 failure – The alarms on the PC buses.


2-2436800-A2-GB32-10 August 1994

Facility Errors Report (fer)Use the fer command to summarize the facility error statistics stored at the multiplexer for aspecified aggregate link, T1 link, or DS1 channel.



Abbreviation: fer

Restrictions: None

Routine: Yes

Schedule: Yes


Facility Errors Report Input Form

The fields on the Facility Errors Report input form are as follows.


Enter the node whose facility errors are to be obtained. Only a single node 731 and 74x nodes with device profiles can be entered. The user can enter the node number, nodename, or node device address (m2/node number).


Enter the aggregate link or T1 link number. Only a single link can be entered and apop-up menu displays the selections 0 for 731, 741, and 742 nodes, 0 and 1 for 740 nodes,and 0 through 15 for a 745.

DS-1 base channel

This field only appears on the form if the node is a 740, 741, or 742 node. The user canrequest a report on a DS1 channel, but cannot simultaneously request a report on both anaggregate link and a DS1 channel. Only a single channel can be entered. A pop-up menudisplays with a list of valid DS1 channel numbers. For 740 nodes, valid DS1 channelnumbers are the multiples of 8 from 0 to 120. For 741 nodes, valid DS1 channel numbersare 0, 8, 16, 24, 32. For 742 nodes, valid DS1 channel numbers are 0, 8, 16, 24.


2-244 August 1994 6800-A2-GB32-10

Facility Errors Report Results Form, Page 1

A sample Facility Errors Report results form is shown in Figure 2-36.

Figure 2-36. Facility Errors Report Results Form, Page 1

The fields on the Facility Errors Report results form are as follows.

Link

The link number of the facility requested for the report. If a DS1 base channel has beenselected, the label reads DS-1 channel and provides the base channel number selectedfrom the input form.

Data reset interval

The rate at which the statistics registers are reset. This interval is configured with thePerformance Data Reporting parameters of the Change Node Configuration Parameters (chncp) command.

Time since last reset

The time elapsed since the statistics registers were reset.


2-2456800-A2-GB32-10 August 1994

Error types

The category of facility errors that are counted.

Number of Errors

The number of errors that have occurred for each error type since the last registers werereset.

NOTE

The statistics registers at a node for facility errors are large enoughto accommodate 65,535 errors. If the statistics registers overflow (avalue exceeding 65,535 errors), the following message appears inplace of a numeric value:

Register overflow


2-246 August 1994 6800-A2-GB32-10

Facility Performance Report (fpr)Use the fpr command to summarize the performance of a T1 facility over the last 24 hours, basedon the statistics kept at the node. The report can display the results in either graphical bar chartformat, or tabular format.



Abbreviation: fpr

Restrictions: None

Routine: Yes

Schedule: Yes


Facility Performance Report Input Form, Page 1

A sample Facility Performance Report input form is shown Figure 2-37.

Figure 2-37. Facility Performance Report Input Form, Page 1


2-2476800-A2-GB32-10 August 1994

The fields on the Facility Performance Report field are as follows.


Enter the node whose facility performance is to be obtained. Only a single node and 731,74x, and 74x-56K nodes with device profiles can be entered. The user can enter the nodenumber, node name, or node device address (m2/node number).


Enter the aggregate link number or T1 link number. Only a single link can be entered, Apop-up menu displays the selections 0 for 731, 741, and 742 nodes, 0 and 1 for 740 nodes,and the numerical entries 0 to 15 for 745 nodes.

DS-1 base channel (Required field) [3 chars, no default]

This field only appears on the form if the node was a 740, 741, or 742 node. The user canrequest a report on a DS1 channel, but cannot simultaneously request a report on both anaggregate link and a DS1 channel. Only a single channel can be entered. A pop-up menudisplays a list of valid DS1 channel numbers. For 740 nodes, valid DS1 channel numbersare the multiples of 8 from 0 to 120. For 741 nodes, valid DS1 channel numbers are 0, 8,16, 24, 32. For 742 nodes, valid DS1 channel numbers are 0, 8, 16, 24.

Data reporting interval (Required field) [5 chars, default = 01:00]

Shows the granularity of the report. Intervals of 15 minutes to 24 hours can be specified.The node stores the latest 24 hours of data. The number of intervals in 24 hours of thelength you specify determines the number of data points retrieved by this command. Forexample, if 24 hours is the selected reporting interval, only one interval would beretrieved. If 1 hour is the selected value, 24 intervals of data would be retrieved. A pop-upmenu displays all possible 15-minute intervals from 00:15 to 24:00.

Type of results (Required field) [7 chars, default = tabular]

Selects the type of output results. A pop-up menu displays the selections graphic andtabular. If graphic is selected, the tabular results are also produced.


2-248 August 1994 6800-A2-GB32-10

Facility Performance Report Input Form (Graphics), Page 2

A sample Facility Performance Report input form (graphics) is shown in Figure 2-38.

Figure 2-38. Facility Performance Report Input Form, Page 2

The fields on the Facility Performance Report input form are as follows.

Graph title (Required field) [49 chars, no default]

Provides for a user-defined title to appear just below the command name in the results.

Y-axis operation (Required field) [7 chars, default = total]

Shows whether the bar chart should use the total number of errors as the heights of thebars, or the percent of the total number as the heights. A pop-up menu displays the entriestotal and percent.

Graph type (Required field) [8 chars, default = both]

Determines what errors will be included in the graph. A pop-up menu displays thefollowing selections.

• errored – One bar chart showing the number of errored seconds.

• failed – One bar chart showing the number of failed seconds.

• both – Two separate charts, one for errored seconds, and one for failed seconds.


2-2496800-A2-GB32-10 August 1994

Y-Axis Scale Values (Required field)

These entries specify scale values for the Y-axis of the chart. They are optional. Thesystem automatically calculates them appropriately unless values are supplied to overridethis.

Maximum value

Specifies the maximum number of errors for the Y-axis, if total was selected forthe Y-axis operation. If percent was selected, the maximum is always 100%.

Minimum value

Shows the minimum number of errors for the Y-axis, if total was selected for theY-axis operation. If percent was selected, the minimum is always 0%.

Interval size

Determines the interval sizes of the Y-axis. This field is only applicable if noentries were made in the Maximum value field. If a Maximum value wasselected, the interval size is either one-tenth of the difference between theMaximum and Minimum values, or one-tenth of the Maximum value (if noMinimum value was specified). If the Y-axis operation was percent, this fieldonly accepts intervals between 1 and 10.

Bar Thresholds

The bar chart displays bars in three color sections, denoting normal (green), marginal(yellow), and unacceptable (red) levels of errors. These levels can be set by specifying thethreshold for the bar to be displayed in red or yellow. The default thresholds are set todivide the Y-axis into three equal areas. Default threshold values are not displayed, but arecomputed at the time of execution.

Red

Determines the total number or percentage of errors at which the bar is displayedin red to indicate an unacceptable threshold of errors.

Yellow

Determines the total number or percentage of errors at which the bar is displayedin yellow to indicate a marginal threshold of errors. The yellow threshold mustbe less than the red threshold.

Change threshold color

Specifies whether the bars are displayed in black, with the threshold colors in thebackground, or displayed in the threshold colors, with a black background. Thebackground threshold colors are more suited to a screen display of the results,while the foreground threshold colors are more suited to a printed display. Apop-up menu displays the selections background and foreground.


2-250 August 1994 6800-A2-GB32-10

Facility Performance Report Results Form (Graphic Errored Seconds), Page 1

The Facility Performance Report results form displays the errored seconds in a bar chart.

Facility Performance Report Results Form (Graphic Failed Seconds), Page 2

A sample bar chart for failed seconds is shown in Figure 2-39.

Figure 2-39. Facility Performance Report Results Form (Graphic Failed Seconds), Page 2

Facility Performance Report Results Form (Graphic Errored Seconds), Page 3

This form displays the tabular results that generated the bar chart for errored seconds on Page 1.

Facility Performance Report Results Form (Graphic Failed Seconds), Page 4

This form displays the tabular results that generated the bar chart for failed seconds on Page 2.


2-2516800-A2-GB32-10 August 1994

Facility Performance Report Results Form (Tabular Report)

A sample Facility Performance Report results form (tabular report) is shown in Figure 2-40.

Figure 2-40. Facility Performance Report Results Form (Tabular Report)

The form above is the first page that is displayed when a tabular report is selected and the last pagewhen a graphical report is selected.

The fields on the Facility Performance Report results form are as follows.

Current 15 min interval

The number of errored or failed seconds for the most current 15-minute interval.

Last 24 hour interval

The number of errored or failed seconds for the last 24 hours.

Number of seconds in current 15 min interval

The number of seconds passed in the current 15-minute interval.

Number of valid 15 min intervals

This value should normally be 96, since the most recent interval overwrites the oldest.However, if the node has been reset, this value can be less than 96.


2-252 August 1994 6800-A2-GB32-10

Signal state

Shows the current state of the facility. Possible values are clear, showing that 10consecutive seconds of data have been processed with no severely errored seconds, andfailed, showing that 10 consecutive severely errored seconds have occurred.

A severely errored seconds is a second with 320 or more Extended SuperFrame (ESF)error events and/or an Out of Frame state.

Bit Error rate

The number of bits in error per 1000 bits transmitted.


2-2536800-A2-GB32-10 August 1994

Generate Routing Tables (grt)(Disruptive)

Use the grt command to have the system automatically create and download routing tables to thenodes in the network. The routing tables are constructed using a minimum hop algorithm, based onthe device and facility profiles in the NMS.

Generally this command should be used when:

• Initializing a new multiplexer network

• Adding a new node to the network

• Making significant changes to network connectivity

NOTE

You may also use the Manage Routing Table Utility to do the samefunctions provided in this command. See the COMSPHERE 6800 Network Management System Multiplexer Management andConfiguration Guide.

Some limitations exist with the NMS algorithm used to generate the routing tables. In particular,SDL connectivity is not always optimally represented by the automatically generated routingtables. The routing tables should be examined after this command has completed for possibleperformance tuning. For SDL connectivity, the NMS assumes that each physical link has oneembedded SDL. NAP SDLs are also accommodated and the remote endpoint is included in therouting table. However, this method does not necessarily result in a optimally-prioritized routingtable. Users should take this into account and review the routing tables for optimal performance.


NOTE

Before the system executes the grt command, a message displayswarning you that the command may take a long time to execute,and that its execution may temporarily affect the performance of thesupervisory network interconnecting the multiplexers. Try to run thiscommand when other supervisory traffic on the network is low.


Abbreviation: grt

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change Routing Table (chrt)Display Routing Table (dsrt)


2-254 August 1994 6800-A2-GB32-10

Generate Routing Tables Input Form

The field on the Generate Routing Tables input form is described as follows.

Node(s) (Required field)

Enter a node number or node name, a sequence of node numbers or node names, a rangeof node numbers, or all. Multiple nodes can be entered, separated by spaces or commas.The keyword all can be entered to signify all nodes. Nodes can be specified by using thedevice name, device address, serial number (ser-xxxxxxxx), or node number. Networknames (net-xxxxxxxxxxxxxx) can be entered, as can circuit names(cir-xxxxxxxxxxxxxxxxxxxxxxxxx). Wildcard characters can be used anywhere withinthe node specification. The nodes must have a device profile and must be a 731, 74x, or74x-56K node.

Generate Routing Tables Results Form

The results form shows each node for which routing tables were automatically generated.

If 719 nodes are in the network, routing information for these nodes are incorporated into therouting tables for the 731 and 74x nodes, as appropriate. The number of 719 NETWORKERsincluded is displayed in the results.

If failures occur in downloading a table to a specified node, the routing table is not downloaded tothat respective node and a list of these nodes and reasons for the failure are listed in the results.


2-2556800-A2-GB32-10 August 1994

Hardware Module Summary (hms)Use the hms command to display a list of the modules that are currently installed in a 731, 74x, or74x-56K node. Front and rear modules and modules in the optional expansion shelf are listed.



Abbreviation: hms

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Change Channel Module Type (chcmt)

Hardware Module Summary Input Form

The field on the Hardware Module Summary input form is as follows.


Enter the identity of the node whose hardware module summary is to be displayed. Only asingle node and 731, 74x, and 74x-56K nodes that have corresponding device profiles canbe entered. The user can enter the node name, node number, or node device address(m2/node number).


2-256 August 1994 6800-A2-GB32-10

Hardware Module Summary Results Form, Page 1

A sample Hardware Module Summary results form is shown in Figure 2-41.

Figure 2-41. Hardware Module Summary Results Form, Page 1

Additional pages are displayed, with up to 12 shelf positions per page.


2-2576800-A2-GB32-10 August 1994

The fields on the Hardware Module Summary results form are described as follows.

Main Shelf Position

This field shows the shelf position (slot number) for each module.

Front Module Type

This field shows the type of front module installed in the indicated shelf position. Possiblefront module types are as follows.

• synch channel – Synchronous data channel module.

• asynch channel – Asynchronous data channel module.

• voice channel – Voice channel module.

• e-voice channel – Expanded voice channel module.

• lbr-voice channel – Low bit-rate voice channel module.

• vre-voice channel – Variable rate expanded voice channel module.

• aggregate link – Aggregate link module.

• DS-1 channel – DS1 channel module. If this module is listed, the next slot isnormally blank, unless the DS1 is equipped with an ADPCM childboard. If so,ADPCM is listed in the next shelf position to indicate this board.

• DS-1 link – DS1 link module.

• TSI – Time slot interchange module.

• DDS channel – DDS channel module.

• SW56K DDS channel – Switched 56K DDS channel module.

• control processor – Control processor (CPU) module.

• unknown – Module is present on the shelf, but the CPU cannot recognize itstype.

• blank – No module is present on the shelf or the module is not communicatingwith the CPU.

Hardware version

Shows the hardware version number of the listed module.

Firmware version

Shows the firmware version number of the listed module.


2-258 August 1994 6800-A2-GB32-10

Rear Module Type

Shows the type of rear module that may be installed in the given shelf position.

• RS-232 – RS-232 data interface module.

• RS-422 – RS-422/Mil-188 data interface module.

• V.35 – V.35 data interface module.

• E&M plus int. – E&M voice interface module.

• FXO interface card – FXO voice interface module.

• FXS interface card – FXS voice interface module.

• DS-1 channel int – DS1 channel interface module.

• agg link/CSU – Aggregate link interface module.

• 56/64K interface – 56 or 64 kbps link interface module.

• 56/64K DSU – 56 of 64 kbps link interface module.

• bus expansion – Expansion shelf control signal module.

• ext clock int – External clock interface module.

• DS-1 link/CSU – DS1 link interface module.

• DDS ocu interface – OCU data port interface.

• serial I/O int – Serial I/O interface module.

• auto CPU switch – Automatic CPU switch module.

• unknown – A module is present on the shelf, but the CPU does not recognize itstype.

• blank – No module is present on the shelf or the module is not communicatingwith the CPU.

Rear Hardware version

Shows the rear module’s hardware version number.

Rear Firmware version

Shows the rear module’s firmware version number. This field is only displayed for74x-56K nodes.

Certain modules take up two shelf positions. In these cases, the second shelf position displays ahyphen (-) in the Module Type row.


2-2596800-A2-GB32-10 August 1994

Internal Test (it)Use the it command to execute a diagnostic test on the channel module hardware to check thecircuitry of a channel endpoint and its channel module. The presence of the channel interfacemodule is verified.



Abbreviation: it

Restrictions: The test cannot be run on voice or DS0 channels if other channels on the module are in loopback or bert states.

Routine: Yes

Schedule: Yes


Internal Test Input Form, Page 1

The fields on the Internal Test input form are as follows.


Enter the node on whose channel the diagnostics will be run. Only a single node 731, 74x,and 74x-56K nodes with device profiles can be entered. The user can enter the nodename, node number, or node device address (m2/node number).


Enter the channel number for the test. Only a single channel number can be entered. Thechannel number must meet one of the following validation criteria, depending on the typeof node.

731 0 to 3

740 0 to 127, XtsY, where X is 0 to 127 (multiples of 8only),

Y is 1 to 24



740-56K 0 to 127

741-56K 0 to 39

742-56K 0 to 31



2-260 August 1994 6800-A2-GB32-10

For a voice or data channel, enter the channel number. For a DS0 channel on a 740, 741,or 742, enter the channel in the format XtsY, where X is the base channel number and Y isthe time slot. For DS0 channels on a 745, enter the channel in the format XtsY, where X isthe link number and Y is the time slot.

Internal Test Input Form (Permission Message), Page 1


Internal Test Results Form

The fields on the Internal Test results form are as follows.

Channel

The channel number on which the test was initiated.

Channel type

The type of channel on which the test was initiated. Possible values are asynch. data,synch. data, lbr-voice, e-voice, voice, DS-0, DDS-dsu, and DDS-ocu.

Test outcome

Indicates whether the test passed, failed, or was aborted.


2-2616800-A2-GB32-10 August 1994

Logical Link Summary (lls)Use the lls command to provide a summary listing of configured logical links, as known to theNMS database. The list can be selected by nodes, logical link connection state, and attributes.Information provided in the summary, per logical link, includes the nodal endpoints, time slots,capacity, SDLs, and channel groups.

For example, a list of all logical links at node xxx that possess the logical attribute attr8 and thephysical attribute attr1 can be obtained. Another example would be a list of all logical links in thenetwork that are currently connected.



Abbreviation: lls

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Display Logical Link (dsll)

Logical Link Summary Input Form

The fields on the Logical Link Summary input form are as follows.

Node(s) (Required field)

Enter the node(s) for the logical link summaries. Multiple nodes can be entered, separatedby commas or spaces. The keyword all can be entered to signify all nodes. Nodes can bespecified by using the device name, device address, serial number (ser-xxxxxxxxxx) ornode number. Network names (net-xxxxxxxxxxxxxxx) can be entered, as can circuitnames (cir-xxxxxxxxxxxxxxxxxxxxxxxxx). Wildcard characters can be used anywherewithin the node specification. The nodes can only be 74x nodes of feature packages 3.x.xor 4.x.x. All such nodes must have device profiles.

Connection state (Required field)

Restrict the logical links to those in the connected or disconnected state. A pop-up menudisplays the selections connected, disconnected, and all.

Attribute (Required field)

Restrict the logical links to those that have a specific attribute indicated as active. Apop-up menu displays the 13 currently-defined attribute names and the keyword all. Onlyone attribute name can be selected.


2-262 August 1994 6800-A2-GB32-10

Logical Link Summary Results Form, Page 1

A sample Logical Link Summary results form is shown in Figure 2-42.

Figure 2-42. Logical Link Summary Results Form, Page 1

For each logical link at the specified node(s), the following information is displayed.

NOTE

If both nodal endpoints of a logical link are specified, the logical linkinformation displays separately for each node’s summary.

The fields on the Logical Link Summary results form are as follows.

Logical link number

The number of the logical link.

Logical link name

The name of the logical link.

Remote node

The node number of the node at the other end of the logical link.


2-2636800-A2-GB32-10 August 1994

Link

The link number at the specified node for the logical link.

Remote link

The link number at the remote node for the logical link.

Time slots

The time slots assigned to the logical link at both the local node and the remote node.

Capacity

The capacity, in time slots, of the logical link.

Current state

The current connection state of the logical link (connected or disconnected).

Configured state

The configured connection state of the logical link (connected or disconnected).

SDL channel

If a synchronous SDL channel is configured on the logical link, the channel number isgiven here.

SDL time slot

If a synchronous SDL channel or embedded SDL is configured on the logical link, thetime slot number is given here.

SDL rate

If a synchronous SDL channel or embedded SDL is configured on the logical link, therate of the SDL, in bps, is given here.

Channel groups

The list of currently connected channel groups on the logical link is provided.


2-264 August 1994 6800-A2-GB32-10

Make Channel Connection (mkcc)Use the mkcc command to make the connection for an ACCULINK channel. The channel groupbandwidth for the channel is allocated when the channel connection is made.

The Channel State Summary (css) command can be used to list all channels on a node or link withtheir current connection state. The Channel Summary (cs) command can be used to list all channelsin a channel group with their current connection state.

If one of the channel endpoints is currently connected to another channel when this command isexecuted, it will fail. You must break the channel connection for that endpoint first. A warningmessage is issued before the command is executed indicating this. You can still schedule thecommand for later execution, assuming that, at the time of execution, the other channel connectionhas been broken. This command is not valid for synchronous Supervisory Data Link channels.



Abbreviation: mkcc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Break Channel Connection (brcc)Channel State Summary (css)Channel Summary (cs)

Make Channel Connection Input Form

The fields on the Make Channel Connection input form are as follows.


Enter the node whose channel connection will be made. Only a single node can beentered. Only 731, 74x, or 74x-56K nodes with device profiles can be entered. The usercan enter the node number, node name, or node device address (m2/node number).


2-2656800-A2-GB32-10 August 1994


Enter the channel number for which the connection should be made. Only a singlechannel number can be entered. The channel number must meet one of the followingvalidation criteria, depending on the type of node.

731 0 to 3


Y is 1 to 24



740-56K 0 to 127

741-56K 0 to 39

742-56K 0 to 31



Make Channel Connection Results Form

The fields in the Make Channel Connection results field are as follows.

Node

The node name of the channel endpoint.

Channel

The channel number being connected.

Result

A message indicating the command result and warnings, if any.


2-266 August 1994 6800-A2-GB32-10

Make Channel Group Connection (mkcgc)Use the mkcgc command to make the connection for a channel group. The T1 bandwidth for thechannel group is allocated when the channel group connection is made.

The Channel Group Summary (cgs) command can be used to list all channel groups defined at anode with their current connection state.



Abbreviation: mkcgc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Break Channel Group Connection (brcgc)Channel Group Summary (cgs)

Make Channel Group Connection Input Form

The field on the Make Channel Group Connection input form is as follows.


Enter the channel group whose connection will be made. Only a single channel group canbe entered.

Make Channel Group Connection (non-56K) Results Form

The fields on the Make Channel Group Connection results form are as follows.

Channel group

The name of the channel group being connected.


The endpoint node numbers of the channel group being connected.

Endpoint node names

The endpoint node names and model numbers of the channel group being connected.

First choice route

The requested routing type for the first choice (fixed or automatic).

Second choice route

The requested routing type for the second choice (fixed, automatic, or none).


2-2676800-A2-GB32-10 August 1994

Third choice route

The requested routing type for the third choice (automatic or none).

First fixed route

The fixed route, if the First choice route type was fixed. The string NIDxx implies thechannel group route entered foreign network NIDxx at that point (e.g., DACS).

Second fixed route

The fixed route, if the Second choice route type was fixed. The string NIDxx implies thechannel group route entered a foreign network NIDxx at that point (e.g., DACS).

Selected route choice

The route choice used for the channel group.

NOTE

Channel groups with 74x-56K endpoints will not display the routingfields, as these are not applicable to them.


2-268 August 1994 6800-A2-GB32-10

Make Logical Link Connection (mkllc)Use the mkllc command to make the connection for a logical link. The T1 bandwidth for thelogical link is allocated when the logical link connection is made.

The logical link connection must be made in order to connect a channel group whose routetraverses across the logical link.

The Logical Link Summary (lls) command can be used to list all logical links defined at a nodewith their current connection state.

For a complete description of the Destination for results and Schedule execution fields, refer toChapter 1, Introduction


Abbreviation: mkllc

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Break Logical Link Connection (brllc)Logical Link Summary (lls)

Make Logical Link Connection Input Form

The fields on the Make Logical Link Connection input form are as follows.


Enter the node where the logical link(s) will be made. Only a single node and nodenumbers and node names for 74x nodes of feature packages 3.x.x or 4.x.x can be entered.All such nodes must have device profiles. The user can also enter the node device address(m2/node number).

Logical Link(s) (Required field)

Enter the logical link(s) that will be made. Logical links can be entered by typing in thelogical link number or logical link name. If the name is entered, it must be preceded bythe string ll- . If the number is entered, it must be preceded by the string LL . Multipleentries are permitted, separated by spaces or commas. The wildcard character (*) ispermitted. The keyword all is permitted to designate all logical links at the given nodalendpoint. Only logical links that are known to the NMS (in its database) are permitted.


2-2696800-A2-GB32-10 August 1994

Make Logical Link Connection Results Form

The fields on the Make Logical Link Connection results form are as follows.

Logical link number

The number of the logical link requested to be connected.

Logical link name

The name of the logical link requested to be connected.

Endpoint 1 node


Endpoint 2 node


A series of possible messages is as follows.

NMS database was updated to match the node database

This message is displayed if a mismatch was discovered between the logical linkconfiguration data in the NMS and that in the node. The database was updated to matchthe data in the node.

Logical link already connected

This message is displayed if the logical link was connected at the time of the connectionrequest.

Logical link does not exist at node

This message is displayed if the logical link definition does not exist at the node. Theconnect request will fail.

Logical link was successfully connected

This message is displayed if the logical link connection request is successfully achieved.

Logical link could not be connected

This message is displayed if the logical link connection request failed.


2-270 August 1994 6800-A2-GB32-10

NAP and SDL State Summary (nsss)Use the nsss command to display the configurations and connection states of NAPs and embeddedSDLs of a multiplexer node.



Abbreviation: nsss

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Display Supervisory Data Link Configuration (dssdlc)

NAP/SDL State Summary Input Form

The field on the NAP/SDL State Summary input form is as follows.

Node

Enter the node whose NAP/SDL summary is to be displayed. Only a single node and 731,74x, and 74x-56K nodes that have corresponding device profiles can be entered. The usercan enter the node name, node number, or node device address (m2/node number).


2-2716800-A2-GB32-10 August 1994

NAP/SDL State Summary Results Form, Page 1

A sample NAP/SDL Summary results form is shown in Figure 2-43.

Figure 2-43. NAP/SDL State Summary Results Form, Page 1

The fields on the NAP/SDL State Summary results form are as follows.

NAP/SDL

Shows the NAP number or embedded SDL number. All nodes have NAPs 0 and 1. The731, 740, 741, 742, 740-56K, and 741-56K nodes have SDL 0 only. The 745 nodes haveSDLs 0 to 15.

Configuration

Shows the configuration type of the NAP. SDLs are always shown with the value notapplicable. Possible configuration types for NAPs are as follows.

• event log printer – The NAP is connected to a device that logs received eventlog messages.

• supervisory port – The NAP is connected to a terminal for menu and/orcommand interactions.

• event datagram port – The NAP is connected to an intelligent asynchronousdevice (e.g., the NMS) that can transmit and receive datagrams.

• supervisory data link – The NAP is connected to a 719/72x link or anotherNAP for SDL transmission.


2-272 August 1994 6800-A2-GB32-10

State

Shows the connection state of the NAP or SDL. For SDLs, the possible states are asfollows.

• normal – The SDL is in normal operation.

• inactive – The link is operational, but the device (remote) has not identifieditself as a 74x node.

• out-of-service – The link is out-of-service.

• down – The link is not in operation due to facility, hardware, or configurationerrors or problems.

• not equipped – The link hardware is not installed.

For NAPs, the possible states are as follows.

• disconnected – The modem controls are inactive.

• ready – The destination point can be dialed, when the NAP is configured as asupervisory port.

• connected – The channel is connected to a remote endpoint.

Connected to

Indicates the remote endpoint for the embedded or external SDL. This field will alwaysbe blank for non-SDL NAPs. The model number, node number, and node name aredisplayed for the remote end of the SDL. The value other is displayed if the remote end isnot a 74x node.


2-2736800-A2-GB32-10 August 1994

Network Paths Summary (nps)Use the nps command to determine up to nine shortest paths (with ten hops or less) between twospecified ACCULINK nodes. Attribute requests can be included to restrict the paths to only thoseroutes meeting the attribute requirements. Logical links are included in paths between two featurepackages 3.x.x/4.x.x nodes.

The shortest paths found will be displayed, the number of which is specified by the user. Theactual number of paths displayed may be less than the specified number of paths.


Access Level: Help Desk, Data Technician, Manager, System Administrator

Abbreviation: nps

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Create Facility Profile (crfp)Edit Facility Profile (efp)List Facility Profile (lsfp)Time Slot Summary (tss)

Network Paths Summary Input Form, Page 1

The fields on the Network Paths Summary input form are as follows.

Source Node (Required field)

Enter the source node for which the path summary is to be determined. Only a single nodeand 731, 74x, and 74x-56K nodes can be entered. All such nodes must have deviceprofiles. The user may also enter the node name, node number, or the device address(m2/node number).

Destination Node (Required field)

Enter the destination node for which the path summary is to be determined. Only a singlenode and 731, 74x, and 74x-56K nodes with device profiles can be entered. The user canenter the node name, node number, or the node device address (m2/node number).

Number of paths

Enter the number of paths to be found between the source and destination nodes. Thenumber of paths can be from 1 through 9. The default is 9.


2-274 August 1994 6800-A2-GB32-10

Network Paths Summary Input Form, Page 1

A sample Network Paths Summary input form is shown in Figure 2-44.

Figure 2-44. Network Paths Summary Input Form,Page 1

For each attribute, the following request can be made.

• active – Select paths that satisfy this attribute.

• inactive – Select paths that do not possess this attribute.

• blank – Ignore this attribute in doing the paths summary.

The default is blank for each attribute. The value not applicable will display if attribute routing isnot available for the nodes.


2-2756800-A2-GB32-10 August 1994

Network Paths Summary Results Form, Page 2

A sample Networks Paths Summary results form is shown in Figure 2-45.

Figure 2-45. Network Paths Summary Results Form, Page 2

The paths are listed by each node in each path, with the shortest path first. Foreign networks (e.g.,DACS) are indicated by the Network ID (e.g., NIDxx). The number of paths that are listed is basedupon the specified number of paths to be found.

Subsequent pages follow listing, for each path, the node numbers, physical link numbers, andlogical link numbers in each hop. An example is shown in the following form.


2-276 August 1994 6800-A2-GB32-10

Network Paths Summary Results Form, Page 7

A sample Network Paths Summary results form is shown in Figure 2-46.

Figure 2-46. Network Paths Summary Results Form, Page 7

For each path, the hop-by-hop listing shows the node number and physical link number for eachSeries 700 node. Logical link numbers that are defined for the hop are listed.


2-2776800-A2-GB32-10 August 1994

Network Wide Channel Group Summary (nwcgs)Use the nwcgs command to list all channel groups in the network, as known to the NMS from itschannel group table.

Channel groups are added to the NMS table if they are created from the NMS or acquired throughthe Acquire Channel Group (accg) command.

For a complete description of the Destination for results and Schedule execution, refer toChapter 1, Introduction.


Abbreviation: nwcgs

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Acquire Channel Groups (accg)

Channel Group Summary (cgs)

Display Channel Group (dscg)

There is no input form for this command, other than the standard Schedule execution andDestination for results fields.

Network Wide Channel Group Summary Results Form, Page 1

A sample Network Wide Channel Group Summary results form is shown in Figure 2-47.

Figure 2-47. Network Wide Channel Group Summary Results Form, Page 1


2-278 August 1994 6800-A2-GB32-10

The fields on the Network Wide Channel Group Summary results form are as follows.

Channel Group

The name of the channel group.

Endpoint Node Numbers

The node numbers of the channel group endpoints.

Endpoint Node Names

The device names of the channel group endpoints.


2-2796800-A2-GB32-10 August 1994

Node Errors Report (ner)Use the ner command to display the number of node errors detected at a multiplexer node.


NOTE

For feature packages 3.x.x/4.x.x 74x and 74x-56K nodes, thefirst-in, first-out error count is always on the active aggregate link.


Abbreviation: ner

Restrictions: None

Routine: Yes

Schedule: Yes


Node Errors Report Input Form

The field on the Node Errors Report input form is as follows.

Node

Enter the node whose errors will be reported. Only a single node and 731, 74x, and74x-56K nodes that have corresponding device profiles can be entered. The user can enterthe node name, node number, or node device address (m2/node number).


2-280 August 1994 6800-A2-GB32-10

Node Errors Report Results Form, Page 1

A sample Node Errors Report results form is shown in Figure 2-48.

Figure 2-48. Node Errors Report Results Form, Page 1

The fields on the Node Errors Report results form are as follows.

Error Type

The type of error.

Number of Errors

The number of errors of the given type.

The Aggregate Link FIFO Error and Aggregate Link Bit Map Error types are not displayed inthe results form for 745 nodes.


2-2816800-A2-GB32-10 August 1994

Node State Summary (nss)Use the nss command to display the current state of the CPU, clock source, clocking referencesand aggregate link or TSI modules at a node.



Abbreviation: nss

Restrictions: None

Routine: Yes

Schedule: Yes


Node State Summary Input Form

The field on the Node State Summary input form is as follows.


Enter the node whose module and CPU states will be reported. Only a single node and731, 74x, and 74x-56K nodes that have corresponding device profiles can be entered. Theuser can enter the node name, node number, or node device address (m2/node number).


2-282 August 1994 6800-A2-GB32-10

Node State Summary Results Form (731, 740, 741, 742, 74x-56K Nodes), Page 1

A sample Node State Summary results form (731, 740, 741, 742, 756K nodes) form is shown inFigure 2-49.

Figure 2-49. Node State Summary Results Form (731, 740, 741, 742, 74x-56K Nodes), Page 1

The fields on the Node State Summary results form are as follows.

State

The connection state of the aggregate link modules. Possible values are as follows.

• active – The module is ready to interface to an external device.

• standby – The module is ready to take over operation from the active module, ifnecessary.

• out-of-service – The module is not in service. Diagnostics can be run on it.

• not equipped – The module is not present.

Format

The framing format on the aggregate link module. Possible values are D4, ESF, and V.35.The 74x–56K nodes are always formatted for V.35.


2-2836800-A2-GB32-10 August 1994

Clock

The current clock source on the module. Possible values are as follows.

• internal – The clock is generated by an internal oscillator.

• external – The clock is supplied by an external device connected to the clockconnector located on the interface module.


• facility – For 74x-56K nodes only, indicates the clock is obtained from the V.35interface leads.

Redundancy

The node redundancy type. Possible values are as follows.

• none – A second aggregate link module has not been equipped. This value isalways displayed for 731, 741, 742, and 741-56K nodes.

• single – Two aggregate link modules are connected to a single aggregate linkfacility via a Y cable. Only one module can be active at a time.

• dual – Two aggregate link modules are connected to separate aggregate linkfacilities. The standby module maintains framing and density.

Available Capacity

Shows the percentage of aggregate link bandwidth that is unused. This includesbandwidth that has been assigned to channel groups, but not allocated to channels.

State

The state of the CPUs. Possible values are as follows.

• active – The CPU is performing system operation for the multiplexer.

• standby – The CPU is ready to take over system operation for the multiplexer.

• out-of-service – The CPU is not in service and diagnostics can be run on it.

CPU Switch Module

If CPU redundancy is being used, the CPU switch module is used to switch control fromthe active CPU to the standby. This field indicates whether this switch module isequipped or not equipped.


2-284 August 1994 6800-A2-GB32-10

Node State Summary Results Form (745 Nodes), Page 1

A sample Node State Summary results form (745 nodes) is shown in Figure 2-50.

Figure 2-50. Node State Summary Results Form (745 Nodes), Page 1

The fields on the Node State Summary results form for TSI 0 and TSI 1 are as follows.

State

The connection state of the TSI modules. Possible values are as follows.

• active – The module is currently switching the DS0s between T1 links.

• standby – The module is ready to take over operation from the active module, ifnecessary.

• out-of-service – The module is not in service. Diagnostics can be run on it.

Clock

The current source for clocking. Possible values are as follows.

• internal – Clocking is obtained from the internal oscillator of the active TSI.

• external (#) – Clocking is from an external device. The numeric value (#)indicates whether the external reference is Ref 0 (a bipolar T1 interface) or Ref 2(the RS-422/V.35 clock interface).

• derived (#) – Clocking is derived from the T1 bit stream. One main T1 clock isassigned, and two fallback T1s. The numeric value (#) indicates the main T1 linkfrom which the clock is derived (link number). Otherwise, this field will displaynone.


2-2856800-A2-GB32-10 August 1994

• holdover – Indicates that there has been a clock reference failure, in which casethe clock system retains its last valid reference frequency.

• none – Indicates no clock source.

Ref 0 termination and Ref 1 termination

The switch condition for the Ref 0 and Ref 1 terminations. Possible values are as follows.

• active – The Ref 0/1 clock is being used.

• inactive – The Ref 0/1 clock is not being used.

• not equipped – The node is not equipped with an external clock source.

Node State Summary Results Form (745 Nodes), Page 2

The fields on the Node State Summary results form for the Control Processors are as follows.

State

The state of the CPUs. Possible values are as follows.

• active – The CPU is performing system operation for the multiplexer.

• standby – The CPU is ready to take over system operation for the multiplexer.

• out-of-service – The CPU is not in service and diagnostics can be run on it.

CPU switch module

If CPU redundancy is being used, the CPU switch module is used to switch control fromthe active CPU to the standby. This field indicates whether this switch module isequipped or not equipped.


2-286 August 1994 6800-A2-GB32-10

Physical Link Loopback (pll)Use the pll command to toggle the physical link of a multiplexer (T1 or 56K) in and out of theloopback states as follows.

• External aggregate link loopbacks (731, 740, 741, or 742)

• Internal aggregate link loopbacks (731, 740, 741, or 742)

• Simultaneous internal or external aggregate link loopbacks (74x-56K)

• External DS1 loopbacks (745)

• Internal DS1 loopbacks (745)

• External CSU loopbacks (731, 740, 741, 742, or 745)

• Internal CSU loopbacks (731, 740, 741, 742, or 745)



Abbreviation: pllAlternate: tll

Restrictions: None

Routine: Yes

Schedule: Yes


Physical Link Loopback Input Form

The fields on the Physical Link Loopback input form are as follows.


Enter the node whose physical link will be toggled in or out of loopback. Only a singlenode and 74x and 74x-56K nodes with device profiles can be entered. The user can enterthe node number, node name, or node device address (m2/node number).


Enter the link that will be toggled in or out of loopback. A pop-up menu displays theselections 0 for 731, 741, 742, and 741-56K nodes, 0 and 1 for 740 and 740-56K nodes,and the numerical values 0 to 15 for 745 nodes.


2-2876800-A2-GB32-10 August 1994

Loopback type (optional for 745s)

Enter the type of loopback to be toggled. A pop-up menu is available, with the entriesdetermined by the following types of node.

ext-csu

For 731, 740, 741, or 742 nodes, this loopback loops the T1 aggregate link signalback out from within the aggregate link interface’s integral CSU. The modulecontinues to transmit data toward the channels while in loopback. For 745 nodes,this loopback loops the DS1 signal back out from within the DS1 link interface’sintegral CSU. Trunk conditioning is applied toward the cross-connected DS0while in loopback. This type of loopback does not appear in the menu for74x-56K nodes.

int-csu

For 731, 740, 741, or 742 nodes, this loopback loops the T1 aggregate link signaltoward the channels from within the aggregate link interface’s integral CSU. TheCSU continues to transmit toward the T1 aggregate link while in loopback. For745 nodes, this loopback loops the DS1 signal toward the TSI from within theDS1 interface module’s integral CSU. The CSU continues to transmit toward theT1 line while in loopback, but cannot receive. This type of loopback does notappear in the menu for 74x-56K nodes.

ext-agg

For 731, 740, 741, or 742 nodes, this loopback loops the T1 aggregate link signalback toward the T1 aggregate link from within the aggregate link interface onthe 740 or 741 side of the CSU. Data continues to be transmitted toward thechannels.

int-agg

For 731, 740, 741, or 742 nodes, this loopback loops the T1 aggregate link signaltoward the channels from a point within the aggregate link interface. For nodesequipped with CSUs, the alarm indication signal is transmitted toward the T1aggregate link.

int-ext

For 74x-56K nodes, this entry is display-only, as it is the only type of loopbackpossible for the 56K aggregate links. This loopback is a simultaneous internaland external loopback on the aggregate link interface card. While in loopback,synchronization will be lost between the specified 74x-56K node and a remote740 or 741 node to which it is connected.

ext-ds1

For 745 nodes, the loopback loops the DS1 signal back toward the T1 line fromwithin the DS1 link module, on the 745 side of the CSU. Trunk conditioningcontinues to be applied toward the cross-connected DS0.


2-288 August 1994 6800-A2-GB32-10

int-ds1

For 745 nodes, this loopback loops the DS1 signal toward the TSI from a pointwithin the DS1 link module. The alarm indication signal is transmitted towardthe T1 line.

Transparent bit stuffing

This field only appears on the form when the designated node is a 745. It is used tospecify whether transparent bit stuffing will be activated or deactivated. A pop-up menuprovides the selections yes and no.

Loopback state (Required field except for 745)

Enter whether the loopback is to be started or stopped. A pop-up menu displays theselections start and stop.

Up to 3 possible confirmer messages are displayed, depending on the following situations.

• If the user selected int-ext for the Loopback type field, a confirmer is given, warning theuser that synchronization will be lost between the 74x-56K node and its remote 740 or 741 node.

• If the link to be looped back is the clocking source for the node, a confirmer is given,warning the user that the node is clocked by the facility to be looped back and that clockingwill be lost.

• Since placing the T1 link into loopback may sever the only SDL connectivity for the node, aconfirmer is always displayed warning the user of this possibility.

The confirmers are always given in the order shown above. If any one is canceled, the entirecommand is canceled.

Physical Link Loopback Results Form

The field on the Physical Link Loopback results form is as follows.

Module type

Indicates the type of module used in the loopback. Possible values are aggregate linkinterface or DS-1.


2-2896800-A2-GB32-10 August 1994

Physical Link Module Test (plmt)(Disruptive)

Use the plmt command to execute a diagnostic test on the aggregate link module of a 731, 740,741, 742, 740-56K, or 741-56K multiplexer. It also executes diagnostic tests to the DS1 module ofa 745 multiplexer.

When the test is directed to a 740 or 740-56K multiplexer with redundant aggregate link modules,the test also tests the circuitry used to switch between the active and standby modules. This test isdisruptive to normal operations, as the active module is taken out\Nof\Nservice to run thediagnostics. The standby takes over, but a service disruption occurs during the switch.

Permission checking is done to ensure that the user has permission for the chplc command if thelink is in service when the test is requested. The user is also asked to confirm the continuation ofthe test if the link must be taken out-of-service.



Abbreviation: plmtAlternate: tlmt

Restrictions: None

Routine: Yes

Schedule: Yes


Physical Link Module Test Input Form, Page 1

The fields on the Physical Link Module Test form are as follows.


Enter the node on whose link the diagnostics will be run. Only a single node and 74x and756 nodes with device profiles can be entered. The user can enter the node number, nodename, or node device address (m2/node number).


Enter the link number for the test. Only a single link number can be entered. A pop-upmenu displays the value 0 for 731, 741, 742 and 741-56K nodes, 0 and 1 for 740 and740-56K nodes, and the numerical values 0 to 15 for 745 nodes.

When the user executes this transaction to initiate the test, the NMS checks the service state of thelink to which it is directed. If the link is active, the NMS then checks to verify that the userrequesting the test has functional access privileges for the Change Physical Link Configuration(chplc) command. If the user has permission, NMS asks the user to confirm that the test should berun, given that service is disrupted. If the user does not have permission, the NMS displays amessage informing the user that the test cannot be executed.


2-290 August 1994 6800-A2-GB32-10

Physical Link Module Test Results Form

The fields on the Physical Link Module Test results form are as follows.

Link

The link on which the test was initiated.

Module type

The type of module on which the test was initiated. Possible values are aggregate linkand DS-1.

Test outcome

Shows whether the test passed, failed, or aborted.


2-2916800-A2-GB32-10 August 1994

Power and Alarm Control Test (pact)Use the pact command to initiate a series of diagnostic tests on a multiplexer’s power and alarmcontrol modules. Both the main and expansion shelf modules are tested.



Abbreviation: pact

Restrictions: None

Routine: Yes

Schedule: Yes


Power and Alarm Control Test Input Form

The field on the Power and Alarm Control Test input form is as follows.


Enter the node whose power and alarm modules will be tested. Only a single node and74x and 74x-56K nodes that have corresponding device profiles can be entered. The usercan enter the node name, node number, or node device address (m2/node number). This isnot applicable to 740, 741, and 742 chassis multiplexers.

Power and Alarm Control Test Results Form

Possible test outcomes are pass, fail, and abort. (This is not applicable to 741 or 741-56K nodes.)


2-292 August 1994 6800-A2-GB32-10

Remote Physical Link Loopback (rpll)Use the rpll command to activate and deactivate the external CSU loopback at the remote end of aT1 facility from the local end.

External CSU loopbacks for 731, 740, 741, and 742 nodes loop back the DS1 signal that is comingtoward the multiplexer to the facility. The incoming signal is passed through to the multiplexer.Loopbacks for 745 nodes loop back the DS1 signal that is coming toward the 745 to the facility.The incoming signal is passed to the TSI, but is not switched. Instead, trunk conditioning is appliedto the DS0s of channel groups using the looped CSU.

A confirmer message has been implemented to allow the user to confirm or cancel the loopback,after receiving a standard warning that the loopback could sever SDL connectivity (if an SDL isrouted over the specified link). A confirmer message is also implemented if the remote link isproviding clocking for its node.



Abbreviation: rpllAlternate: rtll

Restrictions: None

Routine: Yes

Schedule: Yes


Remote Physical Link Loopback Input Form

The fields on the Remote Physical Link Loopback input form are as follows.


Enter the node whose T1 link will be placed into external loopback. Only a single nodeand 74x nodes that have device profiles can be entered. The user can enter the nodenumber, node name, or node device address (m2/node number).


Enter the link that will be placed into external loopback. A pop-up menu displaysselections 0 for 731, 741, and 742 nodes, 0 and 1 for 740 nodes, and the numerical values0 to 15 for 745 nodes.


2-2936800-A2-GB32-10 August 1994

Loopback type (Required field)

Enter whether the loopback is to be initiated by selecting loop-up or terminated byselecting loop-down from the pop-up menu.

Up to two confirmers may be displayed. The first confirmer is displayed if the link specified iscurrently used for clocking for its node. The following message is displayed.

Warning: the specified currently provides clocking for the node. You will looseclocking if you continue with this command.

The second confirmer is always displayed, with the following message.

Warning: enabling a loopback at a node may sever SDL communication with thatnode, if no alternate SDL paths exist. Please verify before you continue with thiscommand.

Remote Physical Link Loopback Results Form

The fields on the Remote Physical Link Loopback results form are as follows.

Module type

Shows the type of module used in the loopback. The possible values are aggregate linkinterface, DS-1 interface, or the device name of the non-Series 700 device on the remoteend.

Link

Shows the link number of the link that is looped back.


2-294 August 1994 6800-A2-GB32-10

Report Diagnostic Status (rds)Use the rds command to summarize the current diagnostic status of channels, channel modules,aggregate link modules, and DS1 modules.

All the possible diagnostics that can be applied to the specified module or channel are listed alongwith their current state for that module or channel.



Abbreviation: rds

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Bit Error Rate Test (bert)Channel Loopback (cl)Physical Link Loopback (pll)Remote Physical Link Loopback (rpll)

Report Diagnostic Status Input Form

The fields on the Report Diagnostic Status input form are as follows.


Enter the node on whose channel the diagnostics will be displayed. Only a single nodeand 731, 74x and 74x-56K nodes with device profiles can be entered. The user can enterthe node number, the node name, or the node device address (m2/node number).


2-2956800-A2-GB32-10 August 1994

In the following fields, either a Channel number or Link number may be specified, but not both.

Channel (optional)

Enter the channel number for the summary. Only a single channel number can be entered.The channel number must meet one of the following validation criteria, depending on thetype of node.

731 0 to 3

740 0 to 127, XtsY, where X is 0 to 127 (multiples of 8 only),Y is 1 to 24



740-56K 0 to 127

741-56K 0 to 39



Link (optional)

If the user wants the diagnostic summary of an aggregate link module of T1 link module,the link number should be entered. A pop-up menu displays the selections 0 for 731, 741,742, and 741-56K nodes, 0 and 1 for 740 and 740-56K nodes, and 0 to 15 for 745 nodes.


2-296 August 1994 6800-A2-GB32-10

Report Diagnostic Status Results Form, Page 1

A sample Report Diagnostic Status results form is shown in Figure 2-51.

Figure 2-51. Report Diagnostic Status Results Form, Page 1

The fields on the Report Diagnostic Status results form are as follows.

Module type

The type of channel module. The possible values are asynch data, synch data, voice,DS-0, DDS-dsu, DDS-ocu, DS-1 channel, or AGL .

Diagnostic

The type of diagnostic. The possible values are local loopback, BERT, loopback at TSI,or external CSU loopback.

State

Shows whether the specified diagnostic is active or inactive.


2-2976800-A2-GB32-10 August 1994

Reset Control Processor (rcp)(Disruptive)

Use the rcp command to reset a multiplexer’s control processor. This is equivalent to pressing theRESET button on the serial I/O interface module.


CAUTION

This command is extremely disruptive to normal operations. Aconfirmation is required from the user when executing thiscommand, after a warning is displayed.


Abbreviation: rcp

Restrictions: None

Routine: Yes

Schedule: Yes


Reset Control Processor Input Form

The field on the Reset Control Processor input form is as follows.


Enter the node whose processor is to be reset. Only a single node and 74x and 74x-56Knodes with device profiles can be entered. The user can enter the node number, nodename, or node device address (m2/node number).

Reset Control Processor Results Form

A command was successfully executed message does not appear for this command, since thecommand can take a long time to execute.


2-298 August 1994 6800-A2-GB32-10

Restore Node Database (rstrnd)(Disruptive)

Use the rstrnd command to restore one or more EEROM configuration databases to ACCULINKnetwork nodes from tape on the COMSPHERE 6800 Series NMS.

NOTE

Only currently available nodes with device profiles can be restoredusing this command.

Typically, a user would execute this command in conjunction with the bkupnd command to restorea node configuration database to its last known state during disaster recovery. For information onhow to back up a node database, see the bkupnd command.

Prior to running this command, a tape cartridge created using the bkupnd command must bepresent in the tape drive of the host NMS processor. For more information regarding the use oftapes and tape drives, see your system documentation.

WARNING

The nodes that are successfully restored will automaticallyreset following transmission of the node database.


Abbreviation: rstrnd

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Backup Node Database (bkupnd)


2-2996800-A2-GB32-10 August 1994

Restore Node Database Input Form

The fields on the Restore Node Database input form are as follows.


Enter the node(s) you want to restore. Multiple nodes can be entered, but must beseparated by commas or spaces. Wildcards are permitted. The keyword all can be enteredto signify all nodes.

NOTE

Care must be taken using the all parameter. Restoring a node’sdatabase causes the node to be reset, cutting communications for aperiod of time to that node and to all other nodes whose linksoriginate there. That loss of communication causes attempts torestore databases to those downline nodes to fail.

Nodes can also be specified in any of the following ways:

• Node number

• Node name

• Node address

• Serial number (of the node, as found in the device profile for the node, in thisformat: ser-xxxxxxxxxxxx)

• Circuit name (in this format: cir-xxxxxxxxxxxxxxxxxxxxxxxxx)

• Network name (in this format: net-xxxxxxxxxxxxxxx)

Priority Level (Required field) [6 chars, default=LOW]

Enter a priority level for this command. The possible choices are HIGH , MEDIUM , andLOW. The priority level acts as a multiplier for a pacing interval used during thetransmission of the node database. A priority level of HIGH disables any pacing,MEDIUM uses the current pacing interval, and LOW will use twice the current pacinginterval. The default pacing interval is set at 2 seconds. This value may be changed via thePACING_INTERVAL environment variable.

Following the input of the above two fields, the NMS will query the network to determine if thespecified nodes can be restored. This process can take up to several minutes depending on thenumber of nodes entered. Subsequently, the Destination for results and Schedule execution fieldsare displayed. For a complete description of these fields, refer to Chapter 1, Introduction.


2-300 August 1994 6800-A2-GB32-10

Restore Node Database Results Form

The fields on the Restore Node Database results form are as follows.

Node

The node identifier.

Status

The results of the restore operation: SUCCESSFUL or UNSUCCESSFUL.

Date/Time

The date and time the node was restored.

Elapsed Time

The elapsed time it took to restore the node.

NOTE

The above information will be repeated for each node specified inthe Restore Node Database input form. The number of result pageswill vary depending on the number of nodes specified.


2-3016800-A2-GB32-10 August 1994

Time Slot Performance Report (tspr)Use the tspr command to report on the performance of 740, 741, or 742 serial synchronous timeslots. These are the time slots that are connected from a 740, 741, or 742 node to a 74x-56K node,carrying 56K serial synchronous channel groups.

This report provides the number of failed seconds and errored seconds for the time slotsynchronization bits.



Abbreviation: tspr

Restrictions: None

Routine: Yes

Schedule: Yes


Time Slot Performance Report Input Form

The field on the Time Slot Performance Report input form is as follows.


Enter the 740, 741, or 742 node for which a time performance report is desired. Only asingle node and only 740, 741, or 742 feature package 3.x.x nodes that havecorresponding device profiles can be entered. The user can enter the node name, nodenumber, or node device address (m2/node number).


2-302 August 1994 6800-A2-GB32-10

Time Slot Performance Report Results Form, Page 1

A sample Time Slot Performance Report results form is shown in Figure 2-52.

Figure 2-52. Time Slot Performance Report Results Form, Page 1

The fields on the results form are described as follows.

Data reset interval

The rate at which the statistics registers at the node are reset. This rate is configured withthe Change Node Configuration Parameters (chncp) command and its Performance DataReporting section.


The elapsed time since the statistics registers were last reset.

Time Slot

The number of each time slot at the specified 740, 741, or 742 node that is configured as aserial synchronous time slot (connected to a 74x-56K node).

Errored Seconds

The number of errored seconds measured on this time slot since the last statistics registerreset.


2-3036800-A2-GB32-10 August 1994

Failed Seconds

The number of failed seconds measured on this time slot since the last statistics registerreset.

NOTE

If the statistics registers overflow their maximum capacity of 65,535errors, the message register overflow returns in place of the errorvalues.


2-304 August 1994 6800-A2-GB32-10

Time Slot Summary (tss)Use the tss command to display a list of the time slots on a specified link. Channel groups, SDLs,logical links, and cross-connect information is included for each time slot.



Abbreviation: tss

Restrictions: None

Routine: Yes

Schedule: Yes

Related Commands: Display Supervisory Data Link Configuration (dssdlc)

Time Slot Summary Input Form, Page 1

The fields on the Time Slot Summary input form are as follows.


Enter the node identity. Only a single node and node numbers and node names for 74x nodes that have corresponding device profiles can be entered. The user can enter thenode device address (m2/node number).

Time slot(s) (Required field)

Enter the desired time slots to be included in the summary. The values 1 to 24 can beentered, or the keyword all. Multiple entries should be separated by commas or spaces. Arange can be entered, using a hyphen (-).

If the node was a 745 node, the Link field appears on the form as follows.

Time Slot Summary Input Form (745 link), Page 1

The field on the Time Slot Summary input form is as follows.


Enter the link number. Only a single link can be entered. A pop-up menu displays with theintegers 0 to 15.


2-3056800-A2-GB32-10 August 1994

Time Slot Summary Results Form (740, 741, 742 Nodes), Page 1

A sample Time Slot Summary results form is shown in Figure 2-53.

Figure 2-53. Time Slot Summary Results Form (740, 741, 742, Nodes), Page 1

The first page of the results form displays a maximum of the first 10 time slots selected for theT1 link, with their SDL configuration. Pages 3 and 4 display similar information for the next (up to 14) time slots. The figure above shows the form for a 740, 741, or 742 node. The form for a 745 node follows. The command is not applicable for 74x-56K nodes.

The fields on the Time Slot Summary results form are as follows.

Time Slot

The time slot numbers.

Channel Group

The channel group, if any, currently allocated to the time slot. A blank implies that nochannel group is allocated to the time slot. Synchronous SDLs do not require channelgroups.

Ser Synch

Shows if the time slot is currently configured as a serial synchronous time slot,connecting the 740, 741, or 742 time slot to a 74x-56K node.


2-306 August 1994 6800-A2-GB32-10

Format

Shows the current configuration for the time slot. Possible values are as follows.

• emb SDL – The time slot is currently carrying an embedded SDL. Only oneembedded SDL can be configured per T1 link.

• synch SDL – The time slot is currently carrying a synchronous SDL. Multiplesynchronous SDLs can be configured on a T1 link.

• ACAMI – The time slot is being used for ACAMI filler byte data. Adjacent timeslots are carrying clear channel data. ACAMI time slots cannot be configured forembedded or synchronous Supervisory Data Links.


Synch SDL Channel

Shows the channel number being used for the synchronous SDL, if the time slot isconfigured for this type of SDL.

Logical Link

Shows the logical link allocated to this time slot.

Time Slot Summary Results Form (745), Page 1

A Time Slot Summary results form (745) is shown in Figure 2-54.

Figure 2-54. Time Slot Summary Results Form (745), Page 1


2-3076800-A2-GB32-10 August 1994

Additional fields for a 745 node are as follows.

Endpoints

Shows the node numbers of the endpoints of the channel group on the time slot.

DS-0 Endpoint Node/Channel


Cross-Connect

If the time slot is cross-connected to another time slot on the 745, the link and time slot towhich it is cross-connected is displayed here. It is shown in the format XtsY, where X isthe link number and Y is the time slot number.

State(s)

Shows the service state of the time slot. One of the following values is shown.






2-308 August 1994 6800-A2-GB32-10

TSI Module Test (tsimt)Use the tsimt command to execute a diagnostic test on the TSI module of a 745 node. An activeTSI module is be placed out-of-service in order to run the test.



Abbreviation: tsimt

Restrictions: None

Routine: Yes

Schedule: Yes


TSI Module Test Input Form

The fields on the TSI Module Test input form are as follows.


Enter the node on whose TSI module the diagnostics will be run. Only a single node and745 nodes with device profiles can be entered. The user can enter the node number, nodename, or node device address (m2/node number).

TSI (Required field)

Enter the module number for the test. Only a single module number can be entered. Apop-up menu displays the values 0 and 1.

When the user executes this transaction to initiate the test, the NMS checks the service state of themodule to which it is directed. If the module is active, the NMS then checks to verify that the userrequesting the test has functional access privileges for the Change Multiplexer ComponentConfiguration (chmcc) command. If the user has permission, NMS asks the user to confirm that thetest should be run, as service will be disrupted. If the user does not have permission, the NMSdisplays a message informing the user that the test cannot be executed.

TSI Module Test Results Form

The field on the TSI Module Test results form is as follows.

Test outcome

Shows whether the test passed, failed, or was aborted.


2-3096800-A2-GB32-10 August 1994

Voice Channel Tone Test (vctt)(Disruptive)

Use the vctt command to place a designated channel endpoint through the loop or network,checking for errors during transmission. In some cases, both endpoints may be put into loopback.

This test must be executed in three separate operations.

• Start the test. The NMS will put the channel endpoints out-of-service and into loopback.

• Report the results during test execution (optional).

• Stop the test. The NMS will place the channel endpoints back into normal operation and thereport results.

This test can be directed to any expanded voice (e-voice) or lbr-voice channel.


NOTE

The channel will be taken out-of-service while the vctt is running andplaced back in-service when finished. Permission checking ispresent to ensure that the user has the appropriate commandpermission level to take the channel out-of-service before runningthe test. If the user does not have permission to execute theChange Channel Configuration (chcc) command and the designatedchannel is currently in-service, the vctt will not run.


Abbreviation: vctt

Restrictions: You cannot run a voice channel tone test if one of the other channels on the same channel module is already running a voice channel tone test or is in loopback state. This can be checked by running the Report Diagnostic Status (rds) command.

Routine: Yes

Schedule: Yes

Related Commands: Bit Error Rate Test (bert)

Voice Channel Tone Test Input Forms

There are five input forms associated with the Voice Channel Tone Test.


2-310 August 1994 6800-A2-GB32-10

Voice Channel Tone Test Input Form, Page 1

The fields on the Voice Channel Tone Test input form are as follows.


Enter the node on whose channel the expanded voice tests will be run. Only a single nodecan be entered. Only 742 nodes with device profiles can be entered. The user can enter thenode number, node name, or node device address (m2/node number).


Enter the channel number to run the vctt. Only a single channel number can be entered.The channel number must meet the following criteria.



The fields on the Voice Channel Tone Test input form (Figure 2-55) are as follows.

VCTT state (Required field) [14 chars, no default]

Enter start to initiate the vctt test.

Enter stop to terminate the vctt test.

Enter report results to display the vctt test results.

If either of the above two options are chosen, the Voice Channel Tone Test results formwill automatically be displayed.

Figure 2-55. Voice Channel Tone Test


2-3116800-A2-GB32-10 August 1994



Test type (Required field) [12 chars, no default]

This field controls the expanded voice diagnostics test. The possible values are as follows.

tone test

This will run a tone generation and measurement test.

dict (Dial in connection test)

This connection test will help check the PBX circuit by simulating a remote endanswer to a local seizure. There are no test results displayed.

ringing test

This will cause an 18-second ringing signal to be generated each time this test isselected. There are no test results displayed. The ringing test is only valid forexpanded voice cards with FXS interface cards.

tone/dict

This is the combination of running the tone test with the dial-in connection test.

tone/ringing

This is the combination of running the tone test with the ringing test.



Tone generation [25 chars, default = ‘‘tone measurement only”]

The following fields only appear if a tone test is previous field. The possible values are asfollows.

Sine wave active

This option generates a 1020 Hz signal.

Digital milliwatt active

This option is the standard test tone which is a 1000 Hz signal.

Tone measurement only

This option will rely on whatever tone is currently applied externally to thecircuit.


2-312 August 1994 6800-A2-GB32-10

Forced FX Signal State [15 chars, no default]

Forces the FSX or FX0 channel to an off-hook, on-hook or inactive condition.

Loopback direction [19 chars, no default]

Determines what direction the tone is being sent and at what point it is measured. Table 2-1 represents the relationship between Tone Generation and Tone MeasurementDirection.

Table 2-1Tone Generation/Tone Measurement Direction

Active Loopback Tone Generation Direction Tone Measurement Direction

None Towards Loop From Network

T1 Side Towards Loop From Loop

I Side Towards Network From Network

T1/I Side Towards Network From Loop



Tone Generation Direction

This display-only field shows the direction the tone is generated towards in the circuit andis only displayed when the tone test is selected.

Towards loop

Occurs when the Interface side Loopback is inactive.

Towards network

Occurs when the Interface side Loopback is active.

Tone Measurement Direction

This display-only field shows the direction in the circuit from which the tone will bemeasured.

From loop

Occurs when the T1 side Loopback is active.

From network

Occurs when the T1 side Loopback is inactive.


2-3136800-A2-GB32-10 August 1994

Voice Channel Tone Test Results Form

The fields on the Voice Channel Tone Test results form are identical to those on the Voice ChannelTone Test input form with the addition of the following.

Level (dBm)

This field displays the level of the received tone.

Frequency (Hz)

This field displays the frequency of the received tone.


2-314 August 1994 6800-A2-GB32-10

This page intentionally left blank.