NextEDGE Multiservices Access System Technical Reference

Transcription

NextEDGEt
Multiservices Access System
TECHNICAL REFERENCE
Document No. 9191-A2-GH30-00
June 1999
Preliminary Draft
Copyright E 1999 Paradyne Corporation
All rights reserved.
Printed in U.S.A.
Notice
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 parties without the
express written permission of Paradyne Corporation, 8545 126th Ave. N., Largo, FL 33773.
Paradyne Corporation makes no representation or warranties with respect to the contents hereof and specifically
disclaims any implied warranties of merchantability or fitness for a particular purpose. Further, Paradyne Corporation
reserves the right to revise this publication and to make changes from time to time in the contents hereof without
obligation of Paradyne Corporation to notify any person of such revision or changes.
Changes and enhancements to the product and to the information herein will be documented and issued as a new
release to this manual.
Warranty, Sales, Service, and Training Information
Contact your local sales representative, service representative, or distributor directly for any help needed. For
additional information concerning warranty, sales, service, repair, installation, documentation, training, distributor
locations, or Paradyne worldwide office locations, use one of the following methods:
H Internet: Visit the Paradyne World Wide Web site at www.paradyne.com. (Be sure to register your warranty
there. Select Service & Support → Warranty Registration.)
H Telephone: Call our automated system to receive current information by fax or to speak with a company
representative.
— Within the U.S.A., call 1-800-870-2221
— Outside the U.S.A., call 1-727-530-2340
Document Feedback
We welcome your comments and suggestions about this document. Please mail them to Technical Publications,
Paradyne Corporation, 8545 126th Ave. N., Largo, FL 33773, or send e-mail to [email protected]. Include
the number and title of this document in your correspondence. Please include your name and phone number if you
are willing to provide additional clarification.
Trademarks
All products and services mentioned herein are the trademarks, service marks, registered trademarks or registered
service marks of their respective owners.
Patent Notification
NextEDGE FrameSaver SLV products are protected by U.S. Patents: 5,550,700 and 5,654,966. Other patents are
pending.
A
DRAFT — June 1999
9191-A2-GH30-00
Contents
About This Guide
H Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
H Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
H Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
1
The NextEDGE System
H An Overview of the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Common NextEDGE System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FrameSaver-Specific Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T1 TDM-Specific Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H The OpenLane Management Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenLane 5.0 Service Level Management Solution . . . . . . . . . . . . . .
OpenLane DCE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H NetScout Manager Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NetScout Probes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
Management Control
H FrameSaver Management Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local Management Control for a FrameSaver NAM . . . . . . . . . . . . . .
End-to-End Management Control for a FrameSaver NAM . . . . . . . . .
H T1 TDM Management Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local Management Control for a T1 TDM NAM . . . . . . . . . . . . . . . . . .
End-to-End T1 TDM Management Control . . . . . . . . . . . . . . . . . . . . . .
3
1-1
1-3
1-5
1-8
1-10
1-10
1-11
1-12
1-12
2-1
2-5
2-9
2-13
2-13
2-16
Typical Applications
H Typical FrameSaver Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
High Speed Data Using Port-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
SLV Frame Relay Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
SLV Frame Relay Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Multinational FrameSaver Application . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Mixing FrameSaver Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Using Auto-Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Back-to-Back Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
H Typical T1 TDM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
T1 TDM NAM with High Speed Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
DRAFT — June 1999
i
Contents
4
User Interface and Basic Operation
H Logging On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
H Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
H Screen Work Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
H Navigating the Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Keyboard Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Selecting from a Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Switching Between Screen Work Areas . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Selecting a Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Entering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
5
Using the OpenLane NMS
H The OpenLane Advantage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Using an OpenLane NMS Application . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
H Installation and Setup of DCE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
H Installation and Setup of Performance Wizard . . . . . . . . . . . . . . . . . . . . . . . 5-2
Installing and Starting OpenLane Performance Wizard . . . . . . . . . . . 5-3
Adding FrameSaver SLV Units to Your Network . . . . . . . . . . . . . . . . . 5-4
Setting Up for Collection of Historical Data . . . . . . . . . . . . . . . . . . . . . . 5-5
Accessing NetScout Manager Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Creating PVC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Setting Frame and Burst Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Getting Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
H Viewing OpenLane Performance Wizard Graphs . . . . . . . . . . . . . . . . . . . . 5-10
Frame Relay Access Channel Aggregated Summary . . . . . . . . . . . . . 5-11
Frame Relay Physical Link Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
PVC Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Frame Relay DLCI Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
PVC Data Delivery Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
H Creating OpenLane Service Level Management (SLM) Reports . . . . . . . 5-24
Web Browsers Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Installation and Setup of SLM Reports . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Displaying the Log-in Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Reports Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Viewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
ii
DRAFT — June 1999
Contents
6
Using NetScout Manager Plus
H The NetScout Advantage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Minimum Hardware Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Minimum Software Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using a NetScout Manager Plus NMS Application . . . . . . . . . . . . . . .
H Installing NetScout Manager Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Configuring NetScout Manager Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Get Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding FrameSaver SLV Units to the NetScout Manager
Plus Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying Domains and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Correcting Domains and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding SLV Alarms Using a Template . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding SLV Alarms Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating History Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the User-Defined History Files . . . . . . . . . . . . . . . . . . . . . . . .
Monitoring a DLCI’s History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitoring the Agent Using NetScout Manager Plus . . . . . . . . . . . . .
Statistical Windows Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
6-1
6-2
6-3
6-4
6-4
6-4
6-5
6-6
6-7
6-8
6-10
6-11
6-14
6-16
6-17
6-19
6-22
6-23
Concord’s Network Health
H Installation and Setup of Network Health . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discovering NextEDGE and FrameSaver Elements . . . . . . . . . . . . . .
Configuring the Discovered Elements . . . . . . . . . . . . . . . . . . . . . . . . . .
Grouping Elements for Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generating Reports for a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Viewing Network Health Charts and Tables . . . . . . . . . . . . . . . . . . . . . . . . .
About Service Level Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About the At-a-Glance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About Trend Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printed Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Reports Applicable to Frame Relay Products . . . . . . . . . . . . . . . . . . . . . . .
Exceptions Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Leaders Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Elements Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supplemental Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Executive Service Level Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IT Manager Service Level Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customer Service Level Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
At-a-Glance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Trend Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT — June 1999
7-2
7-3
7-4
7-5
7-6
7-7
7-8
7-8
7-8
7-8
7-9
7-9
7-10
7-11
7-12
7-13
7-14
7-15
7-16
7-18
7-20
iii
Contents
8
Configuration
H Setting Up the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Considerations When Setting Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Selecting a Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Minimal Configuration Before Deploying Remote Units . . . . . . . . . . . 8-5
Entering and Displaying System Information . . . . . . . . . . . . . . . . . . . . 8-5
A Word About Hot Swapping Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
H Setting Up Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
H Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Configuration Option Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Accessing and Displaying Configuration Options . . . . . . . . . . . . . . . . 8-9
Changing Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Saving Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
H Setting Up Auto-Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
H Setting Up the Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Entering Modem Directory Phone Numbers . . . . . . . . . . . . . . . . . . . . . 8-14
Configuring Dial-In Access to the Menu-Driven User Interface . . . . . 8-15
Configuring Automatic Dial-Out to Send SNMP Traps . . . . . . . . . . . . 8-16
H Setting Up an ISDN DBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
H Setting Up Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
H Setting Up So the Router Can Receive RIP . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
H Setting Up Service Provider Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
H Setting Up for Back-to-Back Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Changing Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
H Configuring the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
H Configuring System Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Configuring System Frame Relay and LMI Options . . . . . . . . . . . . . . 8-23
Configuring Service Level Verification Options . . . . . . . . . . . . . . . . . . . 8-25
Configuring General System Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
H Setting Up Each Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
Configuring the T1 Network Interface Physical Options . . . . . . . . . . . 8-29
Configuring the DSX-1 Interface Physical Options . . . . . . . . . . . . . . . 8-32
Configuring Data Port Physical Options . . . . . . . . . . . . . . . . . . . . . . . . 8-34
H Assigning Time Slots/Cross Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
Movement Between Assignment Screens . . . . . . . . . . . . . . . . . . . . . . . 8-38
Assigning DSX-1 Time Slots to the Network Interface . . . . . . . . . . . . 8-39
DSX-1 Signaling Assignments and Trunk Conditioning . . . . . . . . . . . 8-41
Clearing Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-44
H Configuring Frame Relay LMI for an Interface . . . . . . . . . . . . . . . . . . . . . . . 8-44
iv
DRAFT — June 1999
Contents
H Configuring DLCI Records for Each Interface . . . . . . . . . . . . . . . . . . . . . . . 8-48
H Configuring PVC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-53
H Setting Up Management and Communication Options . . . . . . . . . . . . . . . 8-56
Configuring Node IP Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-56
Configuring Management PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-59
Configuring General SNMP Management . . . . . . . . . . . . . . . . . . . . . . . 8-63
Configuring Telnet and/or FTP Session Support . . . . . . . . . . . . . . . . . 8-64
Configuring SNMP NMS Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-67
Configuring SNMP Traps and Trap Dial-Out . . . . . . . . . . . . . . . . . . . . . 8-68
Configuring the Communication Port . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-72
Configuring the Modem Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-77
Configuring the COM Port to Support an External Modem . . . . . . . . 8-81
9
Security and Logins
H Limiting Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
H Controlling Asynchronous Terminal Access . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
H Controlling Telnet or FTP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Limiting Telnet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Limiting FTP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Limiting Telnet or FTP Access Over the TS Management Link . . . . . 9-6
H Controlling SNMP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Disabling SNMP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Assigning SNMP Community Names and Access Levels . . . . . . . . . 9-8
Limiting SNMP Access Through IP Addresses . . . . . . . . . . . . . . . . . . 9-9
H Controlling Dial-In Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
H Controlling ISDN Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
ISDN Call Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Disabling ISDN Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
H Creating a Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
H Modifying a Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
H Deleting a Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
DRAFT — June 1999
v
Contents
10 Operation and Maintenance
H Displaying System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
H Viewing LEDs and Control Leads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
H Device Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
H Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
System and Test Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Self-Test Results Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Health and Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Test Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Network LMI-Reported DLCIs Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
PVC Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Time Slot Assignment Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
H Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Clearing Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
Service Level Verification Performance Statistics . . . . . . . . . . . . . . . . 10-28
DLCI Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Frame Relay Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
ESF Line Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
H Maintaining Modem Call Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38
Displaying or Changing Modem Call Directories . . . . . . . . . . . . . . . . . 10-38
H FTP File Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39
Upgrading System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-41
Determining Whether a Download Is Completed . . . . . . . . . . . . . . . . . 10-42
Changing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42
Transferring Collected Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-43
vi
DRAFT — June 1999
Contents
11
Dial Backup Modules
H Dial Backup Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Backing Up to the Primary Destination Node . . . . . . . . . . . . . . . . . . . . 11-4
Backing Up to the Nearest Neighbor Node . . . . . . . . . . . . . . . . . . . . . . 11-6
H Our Philosophy on Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
About the Automatic Backup Feature . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Considerations When Setting Up Dial Backup . . . . . . . . . . . . . . . . . . . 11-8
Before Starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
H Setting Up Dial Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Configuring the ISDN DBM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Setting Up ISDN Link Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
Manually Creating Alternate DLCIs on ISDN Links at the
Central Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18
Manually Adding Alternate Destinations . . . . . . . . . . . . . . . . . . . . . . . . 11-18
Setting Up Automatic Backup Configuration . . . . . . . . . . . . . . . . . . . . . 11-23
Setting the Criteria for Automatic Backup . . . . . . . . . . . . . . . . . . . . . . . 11-25
Configuring the DBM Interface to Send SNMP Traps . . . . . . . . . . . . . 11-26
H DBM Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-27
Displaying Information About the DBM . . . . . . . . . . . . . . . . . . . . . . . . . 11-27
Viewing DBM LEDs and Control Leads . . . . . . . . . . . . . . . . . . . . . . . . . 11-28
Manually Forcing Backup (Disruptive) . . . . . . . . . . . . . . . . . . . . . . . . . . 11-30
Manually Placing a Call (Nondisruptive) . . . . . . . . . . . . . . . . . . . . . . . . 11-31
Verifying the ISDN Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-32
Verifying That Backup Can Take Place . . . . . . . . . . . . . . . . . . . . . . . . . 11-33
Upgrading ISDN BRI DBM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-34
H DBM Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-35
DBM Health and Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-35
DBM Test Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-38
PVC Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-39
DBM Interface Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-40
H DBM Call Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-48
Clearing DBM Call Performance Statistics . . . . . . . . . . . . . . . . . . . . . . 11-48
H DBM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-49
ISDN DBM Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-51
H DBM Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-52
ISDN PVC Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-53
DRAFT — June 1999
vii
Contents
12 Application Modules
H APM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
H Typical APM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
High Speed Data Using Port-2 or a Synchronous Data APM . . . . . . 12-5
High Speed Data and E&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
High Speed Data and APL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
High Speed Data, FXS, and E&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
High Speed Data and Drop & Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Off-Premises Extension (OPX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Direct Inward Dial (DID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Video Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Consolidated T1 Access of DDS Circuits . . . . . . . . . . . . . . . . . . . . . . . 12-11
H Displaying APM Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
H Viewing APM LEDs and Control Leads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
OCU-DP APM LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Voice APM LED Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15
Synchronous Data APM LED Descriptions . . . . . . . . . . . . . . . . . . . . . . 12-15
H Displaying System and Test Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
APM Health and Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
APM Test Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19
H Viewing Voice APM Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
H Viewing Cross Connect Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Displaying Network Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Displaying DSX-1 Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26
Displaying Port Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28
H Viewing APM Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-29
Statistics That Can Be Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-29
H Hot Swapping APMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-30
APM Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-30
APM Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31
H T1 TDM ASCII Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31
Automatic Dialing Out When an Alarm Occurs . . . . . . . . . . . . . . . . . . . 12-37
H FrameSaver APM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-39
H Configuring APM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-40
Configuring Synchronous Data APM Ports . . . . . . . . . . . . . . . . . . . . . . 12-40
Configuring FXS Voice APM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-48
Configuring FXO Voice APM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-52
Configuring E&M Voice APM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-55
Configuring OCU-DP APM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-57
viii
DRAFT — June 1999
Contents
H Assigning Cross Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-58
Assigning Voice Ports to DSX-1 or Network Interface Time Slots . . . 12-61
Assigning Synchronous Data Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-61
Assigning OCU-DP Data Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-62
Clearing Port Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-63
H APM Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-64
H Voice Port Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-65
Digital Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-66
Analog Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-66
Line Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-67
Send Test Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-67
Force and Monitor Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-68
H OCU-DP Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-70
Sending a Latching Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-70
Starting/Stopping Other Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-70
H OCU-DP Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-71
DDS CSU/DSU Latching/Nonlatching Loopback . . . . . . . . . . . . . . . . . 12-72
Latching Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-72
OCU Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-73
DS-0 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-73
Line Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-74
Data Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-74
DRAFT — June 1999
ix
Contents
13 Troubleshooting
H Problem Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
H Resetting the Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Resetting the Unit from the Control Menu . . . . . . . . . . . . . . . . . . . . . . . 13-3
Resetting the Unit By Cycling the Power . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Restoring Communication with a Misconfigured Unit . . . . . . . . . . . . . 13-4
H Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
H Troubleshooting Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Device Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Frame Relay PVC Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
H Tests Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13
H Test Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
Changing the Test Timeout from OpenLane Diagnostic Wizard . . . . 13-15
H Starting and Stopping a Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16
Starting and Stopping a Test from an OpenLane Application . . . . . . 13-17
Aborting All Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
H Determining Test Status and Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
H PVC Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
PVC Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Send Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
Monitor Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21
H Physical Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
Line Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23
Repeater Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24
Send Line Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
Sending and Monitoring Pattern Tests . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26
DTE Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28
DTE Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-29
Data Channel Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-30
Send V. 54 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-31
Send FT1 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-32
H IP Ping Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33
H Lamp Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-35
H LMI Packet Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-36
x
DRAFT — June 1999
Contents
A
Menu Hierarchy
H Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
B
IP Addressing
H Selecting an IP Addressing Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
If You Have a FrameSaver NAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
If You Have a T1 TDM NAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
H NextEDGE FrameSaver System IP Addressing . . . . . . . . . . . . . . . . . . . . . B-3
Customer Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Service Provider Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Joint Customer and Service Provider Management . . . . . . . . . . . . . . B-7
Frame Relay IP Addressing Scheme Examples . . . . . . . . . . . . . . . . . B-8
H NextEDGE T1 TDM IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
Direct Management Links to Remote T1 TDM Systems . . . . . . . . . . . B-14
Routing to Remote T1 TDM Systems on the Same Subnet . . . . . . . . B-15
Routing to Remote T1 TDM Systems Using Different Subnets . . . . . B-16
Routing to Remote T1 TDM Systems Using Routers . . . . . . . . . . . . . B-17
Assigning T1 TDM System IP Addresses and Subnet Masks . . . . . . B-18
C
SNMP MIBs and Traps, and RMON Alarm Defaults
H MIB Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
H Downloading MIBs and SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
H Standards Compliance for SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Trap: warmStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Trap: authenticationFailure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Traps: linkUp and linkDown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Traps: enterprise-Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8
Traps: RMON-Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
H RMON Alarm and Event Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
Event Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
Rising Event Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16
Physical Interface Alarm Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16
Static Frame Relay Interface Alarm Defaults . . . . . . . . . . . . . . . . . . . . C-17
Dynamic Frame Relay Interface Alarm Defaults . . . . . . . . . . . . . . . . . C-19
DLCI Alarm Defaults – Paradyne Area . . . . . . . . . . . . . . . . . . . . . . . . . C-20
Static DLCI Alarm Defaults – NetScout Area . . . . . . . . . . . . . . . . . . . . C-21
Dynamic DLCI Alarm Defaults – NetScout Area . . . . . . . . . . . . . . . . . C-22
H Object ID Cross-Reference (Numeric Order) . . . . . . . . . . . . . . . . . . . . . . . . C-23
DRAFT — June 1999
xi
Contents
D
Cables, Connectors, and Pin Assignments
H Rear Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FrameSaver NAM’s Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T1 TDM NAM Rear Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H COM Port Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FrameSaver NAM’s Communication Port . . . . . . . . . . . . . . . . . . . . . . .
T1 TDM NAM’s Communication Port . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Converter and Adapter Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COM Port-to-PC Cable (3100-F2-550) . . . . . . . . . . . . . . . . . . . . . . . . .
COM Port-to-Terminal Cable (3100-F2-540) . . . . . . . . . . . . . . . . . . . . .
COM Port-to-Modem Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gender Adapter/Changer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H DTE Port Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FrameSaver NAM’s DTE Port Connectors . . . . . . . . . . . . . . . . . . . . . .
T1 TDM NAM’s DTE Port Connectors . . . . . . . . . . . . . . . . . . . . . . . . . .
EIA-530A-to-V.35 DTE Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EIA-530A-to-RS-449 DTE Adapter Cable . . . . . . . . . . . . . . . . . . . . . . .
EIA-530A-to-X.21 DTE Adapter Cable . . . . . . . . . . . . . . . . . . . . . . . . . .
Standard V.35 Straight-through Cable . . . . . . . . . . . . . . . . . . . . . . . . . .
Standard V.35 Crossover Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H FrameSaver NAM’s DSX-1 Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DSX-1 Adapter (9008-F1-560) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H T1 TDM Nam’sDSX-1 Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Network Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H T1 Line Interface Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T1 Network Cable (3100-F1-500) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Canadian T1 Line Interface Cable (3100-F1-510) . . . . . . . . . . . . . . . .
T1 Mass Termination Cable (907-F1-500) . . . . . . . . . . . . . . . . . . . . . . .
H FrameSaver NAM’s Modem Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H FrameSaver NAM’s ISDN DBM Connector . . . . . . . . . . . . . . . . . . . . . . . . .
H Synchronous Data APM Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Voice APM Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FXO/FXS Voice APM Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E&M Voice APM Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APM Extension Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H OCU Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OCU Port Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E
Technical Specifications
F
Equipment List
D-3
D-3
D-3
D-4
D-4
D-4
D-5
D-6
D-6
D-7
D-7
D-8
D-8
D-9
D-10
D-12
D-13
D-14
D-14
D-15
D-15
D-16
D-16
D-16
D-17
D-17
D-18
D-19
D-19
D-20
D-21
D-21
D-22
D-24
D-34
D-34
H Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
H Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-6
Index
xii
DRAFT — June 1999
About This Guide
Purpose and Intended Audience
This document contains information needed to properly set up, configure, and
verify operation of the NextEDGE 9192 Multiservices Access (MSA) system that
goes into a 2-slot housing and the NextEDGE 9195 MSA system that goes into a
5-slot housing. The NextEDGE 9192/9195 MSA system incorporates FrameSaver
Service Level Verifier (SLV) functionality. It is intended for system designers,
engineers, administrators, and operators.
You must be familiar with the functional operation of digital data communications
equipment and frame relay networks.
Document Organization
9191-A2-GH30-00
Section
Description
Chapter 1
The NextEDGE System. Describes the MSA solution and
lists the features.
Chapter 2
Management Control. Describes how you establish a
management link and configure end-to-end management
control.
Chapter 3
Typical Applications. Shows typical applications of the
NextEDGE unit in a frame relay network.
Chapter 4
User Interface and Basic Operation. Shows how to
navigate the menu-driven user interface.
Chapter 5
Using the OpenLane NMS. Identifies the key features of
OpenLane NMS applications and describes setup and
applicable windows. Also includes service-level
management reports information.
Chapter 6
Using NetScout Manager Plus. Identifies the key features
of the NetScout Manager Plus application and the
minimum hardware and software required to run the
applications. Also, describes setup and related windows.
DRAFT — June 1999
xiii
About This Guide
xiv
Section
Description
Chapter 7
Using Concord’s Network Health. Identifies the key
features of the Network Health NMS application and the
Chapter 8
Configuration. Provides instructions for setting up the unit,
including how to enter system information, instructions for
configuring the unit, along with full descriptions of each
option and possible settings.
Chapter 9
Security and Logins. Provides procedures for controlling
access to the NextEDGE system.
Chapter 10
Operation and Maintenance. Provides information for
startup and monitoring the unit, dialing out to send SNMP
traps, maintaining call directories, downloading, and
resetting the NextEDGE unit.
Displaying System Information. Provides procedures to
display unit identification information, and to display and
interpret status and statistical information.
Chapter 11
Dial Backup Modules. Provides information about optional
ISDN BRI and PRI DBMs.
Chapter 13
Application Modules. Provides information about optional
voice, synchronous data, and OCU-DP APMs.
Chapter 13
Troubleshooting. Provides troubleshooting and test
procedures for both the menu-driven user interface and an
NMS.
Chapter 5
Using the OpenLane NMS. Identifies the key features of
OpenLane NMS applications and describes setup and
applicable windows. Also includes service-level
management reports information.
Chapter 6
Using NetScout Manager Plus. Identifies the key features
of the NetScout Manager Plus application and the
Chapter 7
Using Concord’s Network Health. Identifies the key
features of the Network Health NMS application and the
Appendix A
Menu Hierarchy. Contains a graphical representation of
how the user interface screens are organized.
Appendix B
IP Addressing. Provides guidelines for selecting an IP
addressing scheme and shows examples of typical
schemes with subnet masks assigned.
DRAFT — June 1999
9191-A2-GH30-00
About This Guide
Section
Description
Appendix C
SNMP MIBs, SNMP Standards Compliance for Traps, and
RMON Alarm Defaults. Includes a list of supported SNMP
MIBs, describes the unit’s compliance with SNMP format
standards and with its special operational trap features,
and describes the RMON-specific alarm and event
defaults.
Appendix D
Cables, Connectors, and Pin Assignments. Identifies
cables used with the access unit and provides pin
assignments for them, along with those of the
connectors/interfaces.
Appendix E
Technical Specifications.
Appendix F
Equipment List.
Index
Lists key terms, acronyms, concepts, and sections.
A glossary is provided on the Paradyne Web site at www.paradyne.com, which
includes acronyms and terms used in this manual. Select Library → Technical
Manuals → Technical Glossary.
9191-A2-GH30-00
DRAFT — June 1999
xv
About This Guide
Product-Related Documents
Document Number
Document Title
Paradyne NextEDGE Documentation:
9000-A2-GN14
2-Slot and 5-Slot Housing Wall Mounting Kit
Installation Instructions
9000-A2-GN15
2-Slot Housing Installation Instructions
9000-A2-GN16
5-Slot Housing with AC Power Supply Installation
Instructions
9000-A2-GN17
5-Slot Housing and 9000 Series Access Carrier AC
Power Supply Installation Instructions
9000-A2-GN1B
DC Power Supply for 5-Slot Housing Installation
Instructions
9000-A2-GN1C
5-Slot Housing with DC Power Supply Installation
Instructions
9000-A2-GN1H
NextEDGE Network Access Module (NAM)
9000-A2-GX42
Affidavit Requirements for Connection to Digital
Service
9109-A2-GN10
9109 Sync Data Application Module (APM)
9109-A2-GN11
9109 E&M Analog Voice Application Module (APM)
9109-A2-GN12
9109 FXS Analog Voice Application Module (APM)
9109-A2-GN14
9109 FXO Analog Voice Application Module (APM)
9109-A2-GN15
9109 OCU-DP Analog Voice Application Module
(APM) Installation Instructions
9195-A2-GL10
NextEDGE 9192/9195 Multiservices Access System
Quick Reference
Paradyne OpenLane NMS Documentation:
xvi
7700-A2-GB23
OpenLane DCE Manager for HP OpenView for
Windows User’s Guide
7800-A2-GB26
OpenLane DCE Manager User’s Guide
7800-A2-GB28
OpenLane Performance Wizard User’s Guide
DRAFT — June 1999
9191-A2-GH30-00
About This Guide
Document Number
Document Title
NetScout Documentation:
2930-170
NetScout Probe User Guide
2930-610
NetScout Manager/Plus User Guide
2930-620
NetScout Manager/Plus & NetScout Server
Administrator Guide
2930-788
NetScout Manager Plus Set Up & Installation Guide
Concord Communications Documentation:
09-10010-005
Network Health User Guide
09-10020-005
Network Health Installation Guide
09-10050-002
Network Health – Traffic Accountant Reports Guide
09-10070-001
Network Health Reports Guide
Contact your sales or service representative to order product documentation.
Complete Paradyne documentation for this product is available at
www.paradyne.com. Select Library → Technical Manuals.
To request a paper copy of this manual:
H
Within the U.S.A., call 1-800-PARADYNE (1-800-727-2396)
H
Outside the U.S.A., call 1-727-530-8623
Paradyne documents are also available on the World Wide Web at:
http://www.paradyne.com
Select Service & Support → Technical Manuals
9191-A2-GH30-00
DRAFT — June 1999
xvii
About This Guide
This page intentionally left blank.
xviii
DRAFT — June 1999
9191-A2-GH30-00
The NextEDGE System
1
This chapter includes the following:
H
An Overview of the System
H
Common NextEDGE System Features on page 1-3.
— FrameSaver-Specific Features on page 1-5.
— T1 TDM-Specific Features on page 1-8.
H
The OpenLane Management Solution on page 1-10.
— OpenLane 5.0 Service Level Management Solution on page 1-10.
— OpenLane DCE Manager on page 1-11.
H
NetScout Manager Plus on page 1-12.
— NetScout Probes on page 1-12.
An Overview of the System
The NextEDGEt Multiservices Access (MSA) System is a completely modular
approach to handling voice, video, fax, and data, including frame relay
performance monitoring and service level management.The system consists of a
Network Access Module (NAM) to terminate the circuit(s) from the service
provider, and a variety of Applications Modules (APMs). Listed below are the
NAMs and options for the NextEDGE System.
NAMS:
9191-A2-GH30-00
H
FrameSaver SLV 9191 NAM
H
Single T1 TDM 9161 NAM
H
Dual T1 TDM 9261 NAM
DRAFT — June 1999
1-1
The NextEDGE System
Optional APMS:
H
FXO APM
H
FXS APM
H
E&M APM
H
Synchronous Data APM – Four ports
H
OCU-DP APM – Two or six port versions
Other optional features:
H
Either a 2-slot or 5-slot housing
H
A 14-slot housing (if you have a T1 TDM 9261 NAM)
H
ISDN BRI or PRI DBM (when used with FrameSaver SLV NAM)
H
OpenLaner Management applications
— OpenLane 5.0
— OpenLane DCE Manager
NextEDGE FrameSaver SLV NAM. The FrameSaver SLV NAM provides all the
functionality of a service-level managed FrameSaver Service Level Verifier (SLV)
unit. It collects and stores physical, frame relay, and protocol statistics that can be
accessed in real time for troubleshooting or retrieved on a network-wide basis at
a scheduled time for historical report processing. It also has unique PVC
multiplexing capability that permits multiple data streams to share a single PVC.
Combine this NAM with other NextEDGE application modules and you have a
flexible, modular multiservices access system for analog/digital voice, video, fax,
and other data applications. ISDN Dial backup capability is also available. See
Common NextEDGE NAM Features on page 1-3 and FrameSaver-Specific
Features on page 1-5 for more about this NextEDGE FrameSaver NAM.
T1 TDM NAM. A NextEDGE T1 Time Division Multiplexer (TDM) NAM functions
as an FT1/T1 multiplexer, providing connectivity between the T1 network and a
high-speed DTEs for a full-featured T1 access solution for analog and digital
voice, video, and data. It is the interface between your customer premises
equipment and a T1 network. These NAMs can be installed in a 9000 Series
Access Carrier, as well as a 2-slot or 5-slot housing. Up to 14 T1 TDM NAMs can
be installed in the 14-slot access carrier. See Common NextEDGE NAM Features
on page 1-3 and T1 TDM-Specific NAM Features on page 1-8 for more about
this NextEDGE T1 TDM NAM.
For additional information:
1-2
H
See Chapter 3, Typical Applications, to see how to implement the NextEDGE
system in your network.
H
See Chapter 5, Using the OpenLane NMS, for OpenLane reports and other
information.
DRAFT — June 1999
9191-A2-GH30-00
The NextEDGE System
H
See Chapter 6, Using NetScout Manager Plus, for additional NetScout
Performance Plus information.
H
See Chapter 7, Concord’s Network Health, for Network Health reports that
apply to NextEDGE frame systems and FrameSaver SLV units.
Common NextEDGE System Features
The NextEDGE features that are common to both the FrameSaver and the
T1 TDM NAMs are listed below:
H
Choice of Multislot Housings. Provides the flexibility of using either a 2-slot
or 5-slot housing. The 2-slot housing is populated with a NextEDGE Frame or
T1 TDM NAM and one of the multiservices APMs. The 5-slot housing is
populated with a NextEDGE Frame or T1 TDM NAM and up to four
multiservices APMs, which can be installed in any combination.
— The 2-slot housing holds one NAM and one APM.
— The 5-slot housing holds one NAM and up to four APMs, allowing
expansion capability as your network needs grow.
A redundant load-sharing ac or dc power supply can also be ordered for
this housing.
H
Modular Design. Any NAM or APM can be physically removed from one
housing and moved to another. In addition, modular design provides
upgradability (e.g., you can start with a 2-slot housing, and move the NAM
and APM to a 5-slot housing at a later date).
H
Multiservices APMs. Provides optional multiservices Application Modules
that are common to both the NextEDGE Frame and T1 TDM systems. As
additional DTE or voice ports are needed for your network applications,
APMs can be added. The following APMs are available:
— Synchronous Data APM – Adds four additional data ports. Each port can
be set for V.35, RS-530A, RS-449, or X.21 operation.
— FXO voice APM – Supports voice traffic and the FXO, FXODN, FXODN
with Wink, and DPT operation modes. This APM passes Caller ID
information when supplied by the network, and supports up to eight ports.
— FXS voice APMs – Supports voice traffic and the FXS, FXSDN, FXSDN
with Wink, and DPO operation modes. This APM provides its own
– 48 Vdc battery and low-frequency AC ringing power, and supports up to
eight ports.
— E&M voice APM – Supports both voice and analog private line (APL)
modem traffic. This APM provides its own – 48 Vdc battery power, and
contains eight ports.
— OCU-DP APM – Supports aggregation of multiple DDS circuits onto a
single T1 lline and video conferencing. This APM is available in either a
2-port or 6-port model.
9191-A2-GH30-00
DRAFT — June 1999
1-3
The NextEDGE System
H
Hot Swapping. Provides the ability to insert and remove NAMs and APMs
without powering-off the system, and without having to reconfigure the cards
each time they are moved.
H
Menu-Driven User Interface. Provides an easy to use, menu-driven
interface to locally or remotely configure, manage, maintain, and access the
system’s extensive diagnostic capability.
H
Standards-Based Protocol Support. Supports PPP and SLIP link-layer
protocols for connection to an external SNMP (Simple Network Management
Protocol) manager or network device via the COM port, or modem port
(Frame NAM only).
H
SNMP Management Capability. Provides network management via an
external Simple Network Management Protocol management system using
industry-standard and Paradyne-specific MIB (Management Information
Base) objects.
H
IP Management Connectivity. Supports management connectivity within an
IP (Internet Protocol) network for up to 300 IP routes to provide IP routing for
SNMP, Telnet, and FTP messages without requiring direct connections.
H
Extensive Monitoring Capability. Provides status information to monitor
and evaluate the system’s and network’s operation via the Status menu,
performance statistics, LEDs and control leads.
H
Extensive Statistics Gathering. Provides a complete view of the network’s
and an interface’s performance through the statistical data collected.
Performance statistics assist in monitoring and fault isolation, and in
determining the duration of a condition or event.
H
Extensive Testing Capability. Provides a variety of tests to identify and
diagnose device, network, and other problems.
H
Security. Provides multiple levels of security to prevent unauthorized access
to the system, which include requiring logins, disabling a remote access
method, specifying community names and access types, and authorizing
NMS IP addresses and access type.
H
Configuration Upload/Download and Software Download Capability.
Provides quick transfer of configuration options to and from nodes and
software downloads while the unit is running using a standard file transfer
protocol (FTP). Two software loads can be stored.
H
DSX-1 Drop/Insert Port. Allows DTEs/PBXs that support the DS1 signal
format to share the T1 network with other high-speed equipment.
H
Two Customer-Specified Configuration Storage Areas. Allows quick
switching of the system’s configuration.
H
Optional Wall-Mount Bracket. Allows one 5-slot, or up to two 2-slot
housings to be mounted on a wall.
For NAM-specific features, see the following:
1-4
H
FrameSaver NAM – See the features on page 1-5.
H
T1 TDM NAM – See the features on page 1-8.
DRAFT — June 1999
9191-A2-GH30-00
The NextEDGE System
FrameSaver-Specific Features
With the FrameSaver NAM installed, the NextEDGE System provides
service-level management features and performance monitoring capabilities
for frame relay applications along with other voice, video, fax, and non-frame
relay data traffic.
The FrameSaver NAM provides the following features:
H
Optional ISDN Backup. Provides automatic initiation of backup for data
through the ISDN (Integrated Services Digital Network) via an alternate route
when network or access line failures occur, and automatic restoration when
service returns to normal. Alarm generation and call security are also
supported when an ISDN BRI or PRI DBM (Basic Rate Interface or Primary
Rate Dial Backup Interface Dial Backup Module) is installed.
— ISDN BRI DBM permits backup over up to two B-channels.
— ISDN PRI DBM permits backup over up to 23 B-channels.
H
Integral Modem. Provides an internal 14.4 kbps modem to support dialing in
to the system for out-of-band management and automatic dialing out of
SNMP traps.
H
Interoperability with FrameSaver Units. Operates with FrameSaver
9120/9620s; FrameSaver SLV 9124/9624s, 9126/9128s, the international
9820-C/9820s, and other NextEDGE FrameSaver systems.
H
Network Management Support. Operates and is compatible with
OpenLane, NetScout, and Concord Communications products.
H
Frame Relay Aware. Supports diagnostic and network management features
over the frame relay network using the Annex-A, Annex-D, and Standard UNI
(User Network Interface) LMI management protocol. The NextEDGE
FrameSaver system’s frame relay capability also supports:
— Inband management channels over the frame relay network using
dedicated PVCs.
— Unique nondisruptive diagnostics.
— CIR monitoring on a PVC basis.
— Multiple PVCs on an interface.
— Multiplexing management PVCs with user data PVCs.
— Multiplexing multiple PVCs going to the same location onto a single
network PVC.
H
9191-A2-GH30-00
Router-Independence. Unique diagnostics, performance monitoring,
PVC-based in-band network management, and SNMP connectivity is not
dependent upon external routers, cables, or LAN adapters.
DRAFT — June 1999
1-5
The NextEDGE System
H
Inverse ARP and Standard RIP Support. Provides Inverse ARP (Address
Resolution Protocol) support so the frame relay router at one end of a
management PVC can acquire the IP address of a FrameSaver unit at the
other end of the PVC. Standard RIP (Routing Information Protocol) allows the
router to automatically learn the routes to all FrameSaver units connected to
that FrameSaver unit.
H
Intelligent Service Level Verification. Provides Quality of Service (or QoS)
features for determining whether service level agreements (SLAs) are being
met and whether the network or the customer’s data is the cause of missed
SLAs. Actual service level agreement parameters and thresholds for service
level verification can be configured.
H
TruePut Technology. Using Frame Delivery Ratios (FDR) and Data Delivery
Ratios (DDR), throughput (both within and above CIR) can be measured
precisely, eliminating inaccuracies due to averaging. These ratios are
available through OpenLane Performance Wizard’s service level
management reports.
H
Auto-Configuration. Provides the following automatic configuration features:
— Frame Relay Discovery – For automatic discovery of network DLCIs and
configuration of a data port DLCI, the PVC connection, and a
management PVC, which is multiplexed with user data DLCIs.
— Time Slot Discovery – For automatic discovery of network time slots and
configuration of corresponding time slots in the system.
— LMI Protocol Discovery – For automatic configuration of the protocol
being used by the network.
— Backup Configuration – For automatic configuration of an alternate route
and DLCI for automatically created PVCs when an ISDN DBM is
installed. When the automatic backup feature is enabled, backup and
restoration occur automatically.
H
RMON-Based User History Statistics Gathering. Provides a complete
view of the network’s and a data port’s performance through the statistical
data collected: SLV, DLCI, frame relay, and DBM call statistics.
All the data collected for a specified interval is stored in a bucket. Two default
intervals are used: 15 minutes and one day. Using these intervals, the system
can collect, display, and store 24 hours of 15-minute buckets (96 buckets)
and five 24-hour data buckets simultaneously, providing up to five days of
daily statistical totals. These intervals can be changed using the NetScout
Manager Plus application.
1-6
H
User-Selectable Ranges for Frame and Burst Sizes. Provides user
configurability for statistical data collection using OpenLane DCE Manager to
set upper and lower limits for data collection. The accumulated data is used
for graphs and reports, and to trigger alarms.
H
Standards-Based Protocol Support. Supports the three standard LMI
protocols for communication over the frame relay interface, as well as the two
link-layer protocols for connection to an external SNMP manager or network
device via the COM or modem port.
DRAFT — June 1999
9191-A2-GH30-00
The NextEDGE System
H
Multinational Support. For multinational applications, teaming international
FrameSaver SLV units with North American-based NextEDGE FrameSaver
systems and FrameSaver SLV units provides a complete global frame relay
management solution.
H
Extensive Testing Capability. Provides a variety of tests to identify and
diagnose device, network, and PVC problems with continuous and
nondisruptive background latency testing, unique nondisruptive frame relay
diagnostics for troubleshooting and testing DLCIs, and local/remote line
speed reporting to identify rate mismatches.
The following are provided:
— DLCI tests: PVC loopback, send/monior pattern, and connectivity. All
are nondisruptive to data when between NextEDGE and FrameSaver
devices.
— Physical interface tests: various local and remote loopbacks, and
send/monitor pattern tests. For voice APMs, test tones and force/monitor
signaling are also provided.
— IP PING and Self-test.
These tests can be commanded from the system’s menu-driven user
interface, OpenLane Performance Wizard’s Diagnostic Wizard, and
OpenLane DCE Manager (using SNMP MIB test commands). The IP PING
and self-test cannot be run using DCE Manager.
9191-A2-GH30-00
H
Dedicated Troubleshooting PVC. Provides a troubleshooting management
link that helps service providers isolate problems within their network. This
feature can be configured.
H
LMI Packet Capture. Provides a way to upload data that has been captured
in a trace file so the data can be uploaded and transferred to a Network
Associates Sniffer for analysis.
H
Dual Flash Memory. Allows software upgrades while the system is up and
running. Two software loads can be stored, to be implemented at the user’s
discretion.
H
Back-to-Back Operation. Allows two NextEDGE/FrameSaver units to be
connected via a network crossover cable so a point-to-point configuration
simulating a leased line environment can be simulated.
H
Multiple DTE Ports. Provides two data ports that have standard connectors.
Port-1 is dedicated to frame relay data, but Port-2 can be configured for
frame relay or synchronous data. Additional ports can be added when a
Synchronous Data APM is added to the system.
H
DSX-1 Drop/Insert Port. Allows DTEs/PBXs that support the DS1 signal
format to share the T1 network with other high-speed equipment so that voice
traffic can share the same local access circuit as the frame relay data.
DRAFT — June 1999
1-7
The NextEDGE System
T1 TDM-Specific Features
The T1 TDM 9161 and 9261 NAMs offer the following features:
H
Additional Multislot Housing. This NAM can be used in three housings:
2-slot housing, 5-slot housing, and the 14-slot access carrier. Only T1 TDM
NAMs can be used in the 14-slot housing, which holds up to 14 single or dual
T1 TDM NAMs, allowing expansion capability as your network needs grow.
H
Additional Multiservices APM. In addition to supporting sychronous data,
FXO, FXS, E&M, and OCU-DP APMs, the Dual T1 TDM NAM supports a
Dual DSX APM that adds two additional DSX ports to the system. At this
time, only the Dual T1 TDM NAM (9261) supports this APM.
H
Multiple Management Paths. Provides multiple methods for sending/
receiving management data.
— Embedded Data Link (EDL). Provides a path for management data over
a performance channel between two nodes. The performance channel
uses 8 Kbps of bandwidth, and is embedded in the synchronous data
channel. If you choose this method, you must have a synchronous data
port.
— Direct Data Link (DDL). Provides a path between two nodes over the
T1/FT1 link itself, embedding the management data in the T1 bundle.
The management data always uses 1 DS0 (64 Kbps).
— Facility Data Link (FDL). Provides the management path over the FDL of
the DS1 extended superframe (ESF). Using this method does not use
any customer data bandwidth, but requires end-to-end connectivity. If you
select this method, you may need to work with your service provider to
ensure that ESF framing is used and the required FDL management path
exists end-to-end.
— COM Port. Provides a physical path over the communications
port/interface for local user interface access or network IP connectivity
data management.
1-8
H
DSX-1 Drop and Insert port(s) allows DTEs/PBXs that support the DS1
signal format to share the T1 network with other high-speed equipment. One
DSX-1 port is provided on the 9161 T1 NAM. The DSX APM (for use with the
9261 T1 NAM) provides two drop/insert ports.
H
Alarm and Fault Condition Indication. Provides the capability of attaching
a terminal or printer to display/print alarm messages. Alarms or traps that are
generated include: power supply, loss of signal, out of frame, alarm indication
signal, excessive error rate, primary and secondary clock failure, yellow
alarm signal received, misconfiguration, and APM failure.
DRAFT — June 1999
9191-A2-GH30-00
The NextEDGE System
H
Extensive Statistics Gathering. Provides a complete view of the network’s
and each data port’s performance through the statistical data collected from
those interfaces to assist in determining the duration of a condition or event.
— A total of 96 intervals (24 hours) of user and Telco statistical data is kept,
seven per screen page, over a 24 hour period, in 15-minute intervals.
— A total of 32 intervals (8 hours) of Synchronous Data Port statistical data
is kept, over an 8 hour period, in 15-minute intervals.
— Quick and easy access to any of the 96 sets of statistics is provided by
selecting a specific interval or occurrence timeframe. (Specifying an
occurrence timeframe is useful when you know about what time a
specific event occurred.)
— You can select a set of statistics to display at the following times:
following an event, preceding an event, immediately preceding and
following an event, or only those statistics that occurred at or after the
event that is the specified interval or time.
— Statistics collected measure or count the following: errored, unavailable,
severely errored, and bursty errored seconds, as well as controlled slip
seconds and loss-of-frame counts. In addition, yellow alarm, loss of
signal, excessive error rate, frame-synchronization bit error, and
line-code violation counts are kept for each 15-minute interval.
— The worst interval for each statistic is provided as an additional aid in
selecting statistical information surrounding trouble spots.
H
Extensive Testing Capability. Provides the capability to maintain the T1
TDM NAM and diagnose device and network problems via:
— Menu-Driven User Interface. Accessed using an async (or other
VT100-compatible) terminal, PC emulation, or Telnet, provides T1
network, DSX-1, sync data port, voice port, and device (lamp) tests.
Loopbacks that can be selected for an interface include: line, payload,
repeater, remote line, DTE, DTE payload (V.54 loop 3), data channel,
remote data channel (V.54 loop 2 or FT1), V.54, digital, and analog.
Pattern Tests that can be selected for an interface include: QRSS,
all zeros, all ones, 1-in-8 (T1 interface only), 3-in-24 (T1 interface only),
63, 511, 2047, 215-1, 220-1, and 2-byte (user defined).
Tone and signal tests can also be selected for voice APMs.
— SNMP MIB Object Test Commands. Supports the same testing capability
as the user interface. Paradyne MIBs can be downloaded from our World
Wide Web site. See page A of this manual for our Web site address.
H
9191-A2-GH30-00
Test Jacks for Monitoring and Troubleshooting. Provides T1 network and
DSX-1 monitoring, as well as break-in testing using external test equipment,
in addition to the standard NextEDGE monitoring and testing capability. The
test jacks are on the NAM’s faceplate. If the NAM is installed in a 2-slot or
5-slot housing, you need to remove the housing’s bezel to access them.
DRAFT — June 1999
1-9
The NextEDGE System
The OpenLane Management Solution
NextEDGE systems are managed by Paradyne’s preeminent OpenLane network
management solution for Unix or Windows-based systems. The OpenLane
solution consists of the following applications:
H
OpenLane 5.0
H
DCE Manager
OpenLane 5.0 Service Level Management Solution
The NextEDGE FrameSaver sustem is managed by Paradyne’s preeminent
OpenLane 5.0 NMS service level management solution, an advanced,
standards-based performance monitoring and management application that
provides unique network control and reporting mechanisms.
Some of its features include:
H
Real-time Performance Monitoring. Provides exact performance
measurement details (not averages, which can skew performance results) of
service level agreement (SLA) parameters – latency, availability, and frame
delivery ratios (which includes accurate measurements of dropped frames
transmitted above or within CIR (Committed Information Rate).
H
Historical SLV Reporting. Provides service level management historical
reports so frame relay SLAs can be verified. Produces daily, weekly, and
monthly SLV reports.
H
Multi-tiered Data Base Architecture. Provides state-of-the-industry,
standards-based, multi-tiered data base architecture for a highly distributive
framework that can be scaled to any network, from micro-networks to
ultra-large, mega-networks.
H
Web-based Access and Management. Provides anytime, anywhere access to
this information via a WEB browser for:
— SLV reporting.
— Device selection and enhanced navigation.
— End-to-end Health and Status browsing.
— Configuration viewing.
— Firmware maintenance scheduling and download management.
1-10
DRAFT — June 1999
9191-A2-GH30-00
The NextEDGE System
H
Diagnostic Troubleshooting. Provides an extremely easy to use tool for
performing tests, with loopback and PVC testing for FrameSaver devices, to
maximize network availability, minimizing downtime.
H
Automatic Topology Maps. Provides automatic device discovery and
end-to-end PVC discovery and configuration to eliminate or minimize manual
configuration and operator intervention.
H
SNMP Support. Supports any SNMP platform for device discovery, trap and
alarm processing, and manual submaps.
OpenLane 5.0 can be used alone or in conjunction with OpenLane DCE Manager
applications. Being standards-based, OpenLane 5.0 can also be used with other
management applications like HP OpenView or IBM’s NetView.
OpenLane DCE Manager
This application is a powerful management system that runs from an
HP OpenView console, and provides a real-time view of network and device
statuses.
Some of its features include:
9191-A2-GH30-00
H
Plug-and-play device discovery, full awareness of PVCs for FrameSaver
NAMs, and database-level integration into HP OpenView.
H
Device identification and access to detailed health and status, alarms, tests,
etc., information.
H
Diagnostic tests. For FrameSaver NAMs, Level 1 and 2 physical and logical
frame relay monitoring and diagnostics (loopbacks) are provided.
H
Enhanced SNMP trap processing to ensure that network trap icons reflect the
alarm on the device.
H
Real-time graphical representations of the device and all its interfaces.
H
Device configuration.
H
Telnet access to devices.
DRAFT — June 1999
1-11
The NextEDGE System
NetScout Manager Plus
This application supports the NextEDGE FrameSaver SLV system and
FrameSaver SLV units, as well as NetScout Probes, with complete LAN and
WAN traffic analysis and monitoring functions. NetScout Manager Plus provides
the following features for NextEDGE FrameSaver SLV systems and FrameSaver
SLV units:
H
Configurable thresholds for RMON 1 (Remote Monitoring, Version 1) alarms
and events.
H
Performance monitoring using collected RMON 2 (Version 2) data.
— Protocol Directory and Distribution functionality allows NextEDGE/
FrameSaver devices to measure up to eleven network-layer protocols
and report the amount of traffic generated by each.
— IP Top Talkers and Listeners reporting identifies the devices using
network bandwidth for traffic and protocol analysis. The network’s top six
users are identified.
— User History buckets to collect performance statistics from NextEDGE/
FrameSaver devices. Up to 900 samples can be stored in 15-minute
buckets, with 96 buckets in a 24-hour period, for up to five days worth of
data.
NetScout Probes
Optional standalone NetScout Probes can be used with NextEDGE/FrameSaver
devices at sites where full 7-layer monitoring, an unlimited number of protocols,
and advanced frame capture and decode capabilities are desired.
When a NetScout Probe is installed, it provides monitoring and protocol analysis
for Layers 2 through 7, while the NextEDGE/FrameSaver device provides for
Layers 1 through 3. When combined with NetScout Manager Plus, capacity
planning using baselining and trend reporting, as well as application analysis and
utilization, are provided.
1-12
DRAFT — June 1999
9191-A2-GH30-00
Management Control
2
This chapter contains customer end user and service provider management
overviews, followed by the steps needed to provide local and remote
management connectivity to the NextEDGE system.
There are two main sections, one applying when a FrameSaver NAM is installed
and the other applying when a T1 TDM NAM is installed.
H
For FrameSaver Management Control, see page 2-1.
H
For a T1 TDM Management Control, see page 2-13.
For either system, you need to select and configure:
H
A method of local management connectivity for the system.
H
A method for end-to-end management connectivity across the network.
H
An IP addressing scheme that fits the local and end-to-end management
connectivity methods.
FrameSaver Management Control
Examples illustrating various frame relay network configurations are included in
this section. These examples include:
H
End User Management Overview on page 2-2.
H
Service Provider Management Overview on page 2-3.
H
Using the TS Management Link on page 2-5.
For local management control, see page 2-5. Methods for establishing local
management control include:
9191-A2-GH30-00
H
Creating a Management PVC Between the Router and Unit Via the DTE Port
on page 2-6.
H
Creating a Separate Mangement Link Via the COM Port on page 2-7.
H
Creating a Mangement Link Via the Modem Port on page 2-8.
DRAFT — June 1999
2-1
Management Control
For remote management control, see page 2-9. Methods for establishing remote
H
End-to-End Management Control Using PVC Multiplexing (EDLCI) on
page 2-9.
H
End-to-End Management Control Using a Dedicated PVC on page 2-9.
H
Transparent Remote Management Control Using RFC 1490 Routers on
page 2-9.
See Appendix B, IP Addressing, for additional information and IP addressing
scheme examples.
End User Management Overview
The optimal method for managing an end-user network is shown in the example
below. Using this method saves PVC charges because management data is
multiplexed with user data using a single PVC.
By accessing the remote units in-band, the remote systems are not
router-dependent so trouble isolation is easier when there are LAN outages.
Customer
NMS
Standard Local PVC
Central
Site
Frame
Relay
Network
Frame
Relay
Router
NextEDGE
System
Customer
Branch 2
Customer
Branch 1
Frame
Relay
Router
PVCs Containing
Multiplexed Management
EDLCIs and
Customer Data
NextEDGE
System
NextEDGE
System
Frame
Relay
Router
99-16389
Physical Connection
PVC Connection (Using EDLCIs)
PVC Connection (Using Standard DLCIs)
For details configuring in-band management links to the central and remote site
NextEDGE systems, see Configuring Management PVCs in Chapter 8,
Configuration.
2-2
DRAFT — June 1999
9191-A2-GH30-00
Management Control
Service Provider Management Overview
In the service provider example below, the service provider’s management data is
multiplexed with the user data using EDLCIs traveling between the customer’s
central site and the customer branches.
A dedicated PVC is configured from the customer’s central site to the service
provider’s network control center, so the customer’s entire network can be
managed from the service provider’s network operation/control center using a
single PVC. This dedicated PVC carries only management data; no user data is
carried.
Service
Provider
NMS
Customer
NMS
Network
Operation
Center
Frame
Central
Site
Frame
Relay
Switch
Frame
Relay
Router
NextEDGE
System
Relay
Switch
Frame
Relay
Switch
Frame
Relay
Switch
Customer
Branch 2
Customer
Branch 1
Frame
Relay
Router
NextEDGE
System
Frame
Relay
Router
NextEDGE
System
Physical Connection
PVC Connection (Using Standard Non-multiplexed DLCI)
99-16500
The service provider’s diagnostic capabilities are greatly enhanced using this
topology. Service provider troubleshooting and management of the customer’s
network is completely independent of the customer’s routers. In addition, PVC
Loopbacks and Pattern tests can be performed without disrupting user data.
9191-A2-GH30-00
DRAFT — June 1999
2-3
Management Control
Using the TS Management Link
Using this feature, a service provider can specify a management link on the
FrameSaver NAM’s network interface so he has the ability to troubleshoot (TS)
device problems. Typically, this link is configured on an as needed basis.
When a TS Access Management Link is selected, the following capabilities are
available to any user via the link:
H
FTP or Telnet access to where the selected management link resides is
provided:
— Without the need of a login, regardless of the current settings for the
Telnet and FTP Login Required options.
— Regardless of a DLCI’s or frame relay link’s status.
H
DLCI status alarms for the DLCI on which the management link resides are
not displayed so the user’s normal DLCI monitoring is not interfered with
while the service provider is troubleshooting the problem.
Customer
NMS
Service
Provider
NMS
Central
Site
Frame
Relay
Switch
Frame
Relay
Router
NextEDGE
System
Network
Operation
Center
Frame
Relay
Switch
Frame
Relay
Switch
Frame
Relay
Switch
Customer
Branch 2
Customer
Branch 1
Frame
Relay
Router
NextEDGE
System
Frame
Relay
Router
NextEDGE
System
Physical Connection
PVC Connection (Using Standard Non-multiplexed DLCI)
99-16387
At lease one dedicated Management PVC must be defined for the network
interface, and only a standard DLCI can be used for its associated DLCI.
This feature can be disabled by the user by changing the TS Management Link
setting back to None. The security level for this link can also be changed to
limit access.
2-4
DRAFT — June 1999
9191-A2-GH30-00
Management Control
Local Management Control for a FrameSaver NAM
Local management methods are typically used at the central site or at large
regional sites, where the NextEDGE system is colocated with the NMS. This is
illustrated in the End User Management Overview on page 2-2.
Local management is accomplished through the following methods:
H
DTE port configured with a frame relay management PVC, with the router
providing RFC 1490 or Cisco encapsulation of the IP traffic.
H
COM port configured as a terminal for access to the menu-driven user
interface using a VT-100 asynchronous terminal or compatible terminal or
PC.
H
COM port connected to the manager or router for an IP management link
using either PPP or SLIP as the link layer.
H
COM port connected to an external LAN adapter for Ethernet connectivity for
an IP management link.
When managing a FrameSaver system locally, you can establish a management
link by:
9191-A2-GH30-00
H
Creating a Management DLCI Between the Router and the System Via a
DTE Port on page 2-6.
H
Creating a Separate Management Link Via the COM Port on page 2-7.
H
Creating a Management Link Via the Modem Port on page 2-7.
DRAFT — June 1999
2-5
Management Control
Creating a Management PVC Between the Router and System
Via the DTE Port
The following configuration shows the management connection using an
RFC 1490-compliant or Cisco frame relay IP router connected to the FrameSaver
system’s user data port.
As shown below, in-band management is accomplished through the dedicated
PVC between the frame relay router or FRAD and the system.
Management Data
Customer Data
Frame Relay
RFC 1490
IP Router
NextEDGE
System
WAN Link
DCE
Port
DTE
Port
NET
Port
• 2 Configured PVCs
– 1 for Management Data
– 1 for Customer Data
• 1 Cable
Frame
Relay
Network
Physical Connection
PVC Connection
99-16460
In this configuration, the system depends on the router for management
connectivity. User data PVCs share the same port as the management PVC.
No additional cables need to be purchased.
The system provides Inverse ARP and Standard RIP Version 1 support for the
router being used for management. Using these features, which is the preferred
method, the router can automatically learn the IP addresses of all FrameSaver
devices at the other end of a management PVC so these routes do not have to
be manually entered.
If not using the Inverse ARP and Standard RIP feature to access remote sites,
map or subinterface statements must be added to the central site router to
ensure that management traffic destined for the remote site is routed to the
central site NextEDGE system. Once traffic gets to the central site NextEDGE
system, it is rerouted to the appropriate remote site NextEDGE systems.
For remote FrameSaver 9124 and 9624 units running a software release prior to
1.2, and for all remote FrameSaver 9120 and 9620 units, the central site system
will not report IP addresses of the older units via standard RIP. For older units,
routing statements must be added to the central-site router so these units can be
reached.
See the Primary Link RIP option in Table NO TAG, Management PVC Options, in
Chapter 8, Configuration, for additional Inverse ARP and Standard RIP
information.
2-6
DRAFT — June 1999
9191-A2-GH30-00
Management Control
Creating a Separate Management Link Via the COM Port
A dedicated PVC can be configured to carry user data over the user data port,
while management data is carried over the COM port. The illustration below
shows a management link connected to the COM port for local access to a
non-RFC 1490 router. The router must have an asynchronous interface running
PPP or SLIP link-layer protocol.
When the COM port is configured as the IP management link, the menu-driven
user interface is accessible via Telnet. Once the interface is configured, it
operates like an IP interface so it can be PINGed, used for SNMP, Traps, FTP,
and Telnet. Although not shown in the illustration below, an external LAN adapter
can be connected to the COM port to provide Ethernet connectivity.
User Data
Frame Relay
Router or
Terminal Server
(Non-RFC 1490)
DCE
Port
Serial
Port
User
Data
Port
COM
Port
NextEDGE
System
WAN Link
Network
Port
Frame
Relay
Network
Management Data
Physical Connection
• 2 Cables
– 1 for User Data
PVC Connection
99-16461
The Communication Port options should be configured for a separate
(out-of-band) management link:
Main Menu→ Configuration→ Management and Communication→
Communication Port
NOTE:
When Port Use is set to Net Link on the Communication Port, the RIP option
must be disabled (set to None).
See Table 8-17, Communication Port Options, in Chapter 8, Configuration, for
information about the Communication Port options. See Table 8-14, Telnet and
FTP Session Options for information about the Telnet options.
9191-A2-GH30-00
DRAFT — June 1999
2-7
Management Control
Creating a Management Link Via the Modem Port
The FrameSaver system can be managed remotely through its internal modem.
Simple
ASCII
Interface
NextEDGE
System
WAN Link
Frame
Relay
Network
Modem
Port
Async or
VT100
Terminal
-or-
External
Modem
SNMP
NMS
VT100 Emulation
and Telnet, FTP, or
NMS using SNMP
PSTN
99-16462
Using this out-of-band example, the remote device can dial-in to gain access to
the menu-driven user interface, provided that the options configured for the
calling device match the options configured for the system’s modem port.
Modem Port configuration options are selected from the Management and
Communication menu:
Main Menu → Configuration → Management and Communication →
Modem Port
The following configuration options must be set:
H
Port Use must be set to Net Link for Telnet access.
H
Port Use must be set to Terminal for asynchronous or VT-100 terminal
access.
H
Dial-In Access must be enabled.
H
Link Protocol must be set to PPP or SLIP for Telnet access.
H
IP Addresses and Subnet Masks must be specified for Telnet access.
See Table 8-18, Modem Port Options, in in Chapter 8, Configuration, for
information about these options.
See Setting Up the Internal Modem in Configuration, for additional setup
information.
2-8
DRAFT — June 1999
9191-A2-GH30-00
Management Control
End-to-End Management Control for a FrameSaver NAM
End-to-end management control methods are typically used for accessing remote
site units that are not colocated with the NMS.
Remote management is accomplished via the following methods:
H
Merging or multiplexing management data with user data, and transferring
the information over a specified network PVC.
H
Dedicated frame relay PVC between NextEDGE systems at each end of the
circuit for in-band management. This is required when communicating with
non-FrameSaver equipment.
H
Management PVCs configured between DTE ports and RFC 1490-compliant
or Cisco encapsulation routers at one or both ends of the circuit to route
management and user data through the same port to the routers.
H
Modem port configured for Terminal use for remote access to the
menu-driven asynchronous user interface.
H
Modem port remotely connected to the manager for an IP management link
using either PPP or SLIP as the link layer.
When managing the FrameSaver system remotely, you can establish a
management link across the network in one of three ways. You can:
9191-A2-GH30-00
H
Use a shared PVC (embedded DLCI).
H
Use a dedicated PVC.
H
Use RFC 1490 routers for transparent management control.
DRAFT — June 1999
2-9
Management Control
End-to-End Management Control Using PVC Multiplexing (EDLCI)
This is the preferred method for accessing remote site units that are not
co-located with the NMS.
In the configuration below, the FrameSaver system’s management data is
multiplexed with user data onto a single PVC, sharing the same PVC – source
DLCI 20-to-destination DLCI 60. There is one configured PVC through the
network – a shared PVC for management and user data.
NextEDGE
System A
DLCI 20
Management
Data
NextEDGE
System B
Management and
User Data
Frame
Relay
Network
DLCI 60
User
Data
Frame
Relay
Router
Physical Connection
PVC Connection
(Using Shared PVC)
Frame
Relay
Router
99-16463
Using the Inverse ARP and Standard RIP features, the preferred method, the
router can automatically learn the IP address of all FrameSaver systems at the
other end of a management PVC. If not using these features, map or subinterface
statements must be added to the central site router to ensure that management
traffic is routed appropriately.
If desired, higher priority may be given to DLCIs carrying user data. When
configuring an embedded DLCI ( EDLCI) for management data, the DE (discard
eligible) bit may be set. When there is traffic congestion, the network first discards
the management data since it is already marked discard eligible.
information.
2-10
DRAFT — June 1999
9191-A2-GH30-00
Management Control
End-to-End Management Control Using a Dedicated PVC
Management control through a dedicated PVC is typically used by service
providers to provide a single point of access (i.e., a standard, nonmultiplexed
PVC), usually to the customer’s central site unit, to manage the customer’s
network. See Service Provider Management Overview on page 2-3 for a typical
service provider configuration.
Nonmultiplexed DLCIs must be used when in-band management communication
is desired between any non-NextEDGE or non-FrameSaver unit and the
NextEDGE system.
Central
Site
NextEDGE
System A
Remote
Site
Management
Data
DLCI 60
Network
Operation
Center
Router
Frame
Relay
Network
Non-FrameSaver
Unit B
DLCI 20
Physical Connection
PVC Connection
(Using Dedicated PVC)
Frame
Relay
Router
99-16464
As shown in the example, in-band management is accomplished through the
dedicated PVC between the two units. Management data for non-NextEDGE
system B (at the remote site) goes to NextEDGE system A first (at the central
site), which then routes it into the dedicated PVC between the two units. Only
management data is carried over the PVC – source DLCI 60-to-destination
DLCI 20.
If the priority of a dedicated management PVC is set to High, it could interfere
with traffic from Port-2 if the load on the management PVC is high. In general,
higher priority traffic should be connected to Port-1.
Using the Inverse ARP and Standard RIP features, the preferred method, the
NOC router can automatically learn the IP address of the NextEDGE system at
the other end of a management PVC. If not using these features to access
remote sites, or for older FrameSaver 9124 and 9624 (pre-1.2) or 9120 and 9620
units, map or subinterface statements for those units must be added to the
central site router for management traffic to be routed to the central site
NextEDGE system so it can be rerouted to the appropriate remote site
NextEDGE systems.
information.
9191-A2-GH30-00
DRAFT — June 1999
2-11
Management Control
Transparent Remote Management Control Using RFC 1490 Routers
NextEDGE System A can be managed locally via in-band management channels
using a frame relay PVC that is configured on its user data port. When managing
System B remotely, System A does not route IP traffic to System B. Instead, IP
traffic is transparently passed through System B as part of user data. The router
then routes the management data back to System B on the dedicated
management PVC that is configured between the system’s router and the user
data port.
1 PVC
SNMP NMS
NextEDGE
System A
NextEDGE
System B
Frame
Relay
Network
WAN
Link
VT100
Emulation
and Telnet or
NMS using
SNMP
WAN
Link
1 Cable
1 PVC
Frame
Relay
RFC 1490
Router A
Physical Connection
1 Cable
2 PVCs
Frame
Relay
RFC 1490
Router B
PVC Connection
99-16388
The configuration above shows both local and remote management across the
network. Management data is being routed from frame relay Router A to IP
Router B, then redirected by the router to NextEDGE System B. Both
management and user data are carried over the same PVC; a separate,
dedicated management PVC is not required.
NOTE:
This is not an optimum method due to router-dependency at the remote site,
which can make fault isolation more difficult when there is a LAN or router
failure.
2-12
DRAFT — June 1999
9191-A2-GH30-00
Management Control
T1 TDM Management Control
Examples illustrating various T1 TDM network configurations are included in this
section.
For local management control, see page 2-15. Methods for establishing local
H
Creating a Management Link through the COM Port on page 2-14.
H
Configuring an External Device (Connected to the COM Port) on page 2-15.
For remote management control, see page 2-16. Methods for establishing remote
H
End-to-End Management Control Using the ESF EDL on page 2-16.
H
End-to-End Management Control Using an EDL on page 2-17.
See Appendix B, IP Addressing, for additional information and IP addressing
scheme examples.
Local Management Control for a T1 TDM NAM
When managing a T1 TDM NAM locally, you can establish a management link
by:
9191-A2-GH30-00
H
Creating a Management Link through the COM Port on page 2-14.
H
Configuring an External Device (Connected to the COM Port) on page 2-15.
DRAFT — June 1999
2-13
Management Control
Creating a Management Link through the COM Port
When the COM port is configured as the IP management link (Net Link), the user
interface is also accessible via Telnet. Although not shown in the illustration
below, a LAN adapter can be connected to the COM port to provide Ethernet or
Token Ring connectivity, or an asynchronous terminal (or other VT100-compatible
interface) can be directly connected to the COM port, as well.
Customer Data
DTE
Port
DCE
Port
NextEDGE
System
WAN Link
Router
COM
Port
AUX
Port
NET
Port
T1
Network
Management Data
Physical Connection
• 2 Cables
– 1 or more for Customer Data
Customer Data
99-16465
The configuration options below show what should be configured for a
management link. These configuration options are configured from the user
interface based upon the Port Type selected, Asynchronous or Synchronous.
Menu selection sequence:
Main Menu→ Configuration→ User Interface→ Communication Port
Port Use Set to Net Link and
Port Type Set to Asynchronous
Port Use Set to Net Link and
Port Type Set to Synchronous
— Data Rate (Kbps)
— Clock
— Character Length
— Data Rate (Kbps)
— Parity
— Stop Bits
— Ignore Control Leads
See Table NO TAG, Communication Port Options, in Chapter 9, Configuration.
When the communication (COM ) port is configured as the IP management link,
the menu-driven interface is accessible through Telnet. When this is the case, you
also need to enable Telnet session configuration options.
Main Menu→ Configuration→ User Interface→ Telnet/FTP Session
2-14
DRAFT — June 1999
9191-A2-GH30-00
Management Control
An IP address and a subnet mask must have been assigned.
Main Menu→ Configuration→ Management and Communication
See Table 5-12, Telnet/FTP Session Options, in Chapter 9, Configuration.
In addition, if you want to access the configuration files (upload, download), or
download new firmware files to the T1 TDM NAM, you must set the FTP Session
configuration option to Enable.
Configuring an External Device (Connected to the COM Port )
A T1 TDM NAM can be managed remotely by connecting an external device like
a modem or PAD ( packet assembly/disassembly) facility to the COM port.
NextEDGE
System
Simple
ASCII
Interface
WAN Link
T1
Network
Async or
VT100
Terminal
COM
Port
External
Modem
External
Modem
-or-
SNMP
NMS
VT100 Emulation
and Telnet or
NMS using SNMP
PSTN
99-16466
Using this out-of-band example, configure call processing using the following
pertinent configuration options, configured from the user interface.
Main Menu→ Configuration→ User Interface→ External Device (COM Port)
— External Device Commands
— Dial-In Access
— Port Usage
See Table 5-11, External Device (COM Port) Options, in Chapter 9, Configuration.
9191-A2-GH30-00
DRAFT — June 1999
2-15
Management Control
End-to-End T1 TDM Management Control
When managing the T1 TDM NAM remotely, you can establish a management
link across the network by:
H
Using the Facility Data Link (FDL) for a point-to-point ESF T1 link.
H
Using an Embedded Data Link (EDL) associated with a synchronous data
port.
H
Using a Direct Data Link (DDL).
End-to-End Management Control Using the ESF FDL
You can configure the NextEDGE system with a T1 TDM NAM to use FDL as a
management link if it isavailable for a point-to-point ESF T1 link, where FDL is
end-to-end.
NextEDGE
System B
NextEDGE
System A
LAN
T1
Network
NMS
Physical Connection
FDL
99-16467
As shown in the example, in-band management is accomplished through the FDL
between the two NextEDGE systems with T1 TDM NAMs. Management data for
T1 TDM systems goes to T1 TDM System A, which then routes it into the FDL
between the two systems. This example assumes that the NMS (or Host) that is
attempting to access System B is attached (using SLIP or PPP) via the COM port
on System A.
Set the Management Link configuration option to FDL.
Main Menu→ Configuration→ Network Interface
2-16
DRAFT — June 1999
9191-A2-GH30-00
Management Control
End-to-End Management Control Using an EDL
In the configuration below, the T1 TDM NAM’s management data is multiplexed
with customer data by taking 8 kbps of the allocated data on a synchronous data
port to use as the EDL. There is one configured EDL through the network to each
system, which is a shared circuit for management and customer data.
NextEDGE
System C
NextEDGE
System A
Port y
Cluster
Controller
NextEDGE
System B
T1
Network
Port 1
Port 2
FEP
Router
Port x
Physical Connection
Router
EDL
99-16468
9191-A2-GH30-00
DRAFT — June 1999
2-17
Management Control
2-18
DRAFT — June 1999
9191-A2-GH30-00
3
This chapter provides illustrations showing how the NextEDGE system can be
used in your network. It includes the following applications:
H
Typical FrameSaver Applications on page.
— High-Speed Data Using Port-2 on page.
— SLV Frame Relay Access on page.
— SLV Frame Relay Monitoring on page.
— Multinational FrameSaver Application on page.
— Mixing FrameSaver Devices on page.
— Using Auto-Configuration on page.
— Back-to-Back Operation on page.
H
Typical T1 TDM Applications on page.
— T1 TDM NAM with High Speed Data on page.
9191-A2-GH30-00
DRAFT — June 1999
3-1
Typical FrameSaver Applications
The following sections show typical applications of the NextEDGE system with
a FrameSaver NAM. For additional FrameSaver applications, see Chapter 11,
Dial Backup Modules and Chapter 11, Application Modules.
High Speed Data Using Port-2
The NextEDGE system supports high speed data over two ports. Frame relay
router traffic is on Port-1, while TDM traffic can be on Port-2. Port-2 can be
configured for either frame relay or synchronous data. The illustration below
shows both a router and mainframe application.
Data moving through the front-end processor (FEP) and the cluster controller is
heritage data that is not available on the LAN. Because the NextEDGE unit
provides two data ports, router-based data can easily be added to the network
without disrupting existing network operations.
Cluster
Controller
FEP
Terminal
Router
Router
T1 Access
Unit
T1 Access
Unit
Mainframe
496-15189
The data rates available to the two applications can be easily changed. This
allows the router connection to increase in speed. For the mainframe application,
it also allows the FEP-based data’s rate to be reduced as the amount of data
transmitted on this route declines naturally over time.
Additional synchronous data ports are supported when the Sync Data APM is
installed with the NextEDGE unit (see Chapter 11, Application Modules, for
additional information about the flexibility of the NextEDGE system).
3-2
DRAFT — June 1999
9191-A2-GH30-00
SLV Frame Relay Access
Typical RMON applications include a:
H
FrameSaver SLV units with RMON capability at central and remote sites; a
FrameSaver 9128 at the central site and FrameSaver 9126s at remote sites.
H
Full NetScout RMON probes used with FrameSaver 9128 units at central and
regional sites, and using FrameSaver 9126 units at remote sites (see
page 3-7).
The SLV application shown below provides RMON capability at the central site
and remote sites. This capability provides Physical, Frame Relay, and Network
layer protocol statistical buckets for remote troubleshooting and frame relay SLV
monitoring.
Central
Site
Paradyne OpenLane
and NetScout
NMS Applications
Remote
Sites
Frame
Relay
Router
FrameSaver
9126
Unit
Frame
Relay
Router
Frame
Relay
Network
Frame
Relay
Router
FrameSaver
9128
Unit
FrameSaver
9126
Unit
FrameSaver
9128
Unit
Frame
Relay
Router
98-15874a
When the FrameSaver unit detects a failure, the unit proactively notifies the
management station so the management station can actively monitor network
conditions.
9191-A2-GH30-00
DRAFT — June 1999
3-3
OpenLane Performance Wizard provides service providers or commercial end
users and their customers with SLV reports through the World Wide Web. The
NOC’s (network operation center’s) OpenLane management system must have
access to the frame relay network, so the system needs to be inside the network
service provider’s protective firewall. The SLV Reports Web server, which is
outside the firewall, enables communication with the customer Web browser and
authenticates customer logins for access to SLV data. This is shown in the
example below.
SLV Reports
Web Server
Central
Site
Firewall
Web
Browser
Frame
Relay
Router
Remote
Sites
NOC NMS
with OpenLane
Performance
Wizard Application
Frame
Relay
Switch
NextEDGE
System
Frame
Relay
Router
Frame
Relay
Switch
Frame Relay
Network
NOC = Network Operation Center
FrameSaver
Unit
Frame
Relay
Router
NextEDGE
System
Frame
Relay
Router
FrameSaver
Unit
99-16267
3-4
DRAFT — June 1999
9191-A2-GH30-00
SLV Frame Relay Monitoring
NextEDGE endpoints provide SLV intelligence and visibility for international
NTU-terminated lines. Typical applications include:
H
FrameSaver SLV 9820-C unit at the central site, where E1 access speeds are
required.
H
FrameSaver SLV 9820 units at the remote sites, where 64/128 kbps access
speeds are required.
The SLV (Service Level Verifier) application shown below provides RMON
(remote monitoring) capability at the central and remote sites.
Central
Site
Paradyne OpenLane
and NetScout
NMS Applications
NTU
Frame
Relay
Router
Remote
Sites
Frame
Relay
Router
FrameSaver
9820
Unit
Frame
Relay
Router
NTU
Frame
Relay
Network
FrameSaver
9820-C
Unit
NTU
NTU
FrameSaver
9820
Unit
FrameSaver
9820
Unit
Frame
Relay
Router
99-16266
When the FrameSaver unit detects a failure, the unit proactively notifies the
management station so the management station can actively monitor network
conditions.
With FrameSaver SLV units in a network, the service provider can offer its
customers the following services:
9191-A2-GH30-00
H
Higher quality service
H
Quick installation
H
Quick problem resolution
H
SLAs backed by accurate (not averaged) measurements
H
Web-based reporting
DRAFT — June 1999
3-5
Multinational FrameSaver Application
For multinational applications, teaming FrameSaver 9820-C and 9820 units with
North American-based FrameSaver SLV units provides a complete, end-to-end,
global frame relay management solution for a company’s international locations.
North American-based multinational companies are used to intelligent diagnostic
and service-level verification features in their frame relay networks, and they
realize that these same features are needed at their international locations as
well if the company is to continue expanding globally.
The illustration below shows a multinational application.
Customer
NMS
North American
Location
World-Wide
Location
NTU
Frame
Relay
Router
FrameSaver
SLV 9124
Unit
North
American
Frame
Relay
Network
World-Wide
Frame
Relay
Network
FrameSaver Frame
SLV 9820-C Relay
Router
Unit
NTU
Frame
Relay
Router
FrameSaver
SLV 9128
Unit
FrameSaver
SLV 9820
Unit
Frame
Relay
Router
99-16285
Customer access to SLV data is through a standard Netscape or Microsoft Web
browser. The customer’s profile, which contains the login information and
specifies the device IP addresses that the customer is authorized to view,
prevents unauthorized access to the SLV data. The customer enters the URL for
the customer’s subdirectory, enters the appropriate login, and selects a report.
See Creating OpenLane Service Level Management Reports in Chapter 5, Using
the OpenLane NMS, for information about these reports.
3-6
DRAFT — June 1999
9191-A2-GH30-00
If LAN or application layer probing or packet capture capability is desired, a
NetScout probe can be used with a FrameSaver 9128 at the central site.
In the example below, a FrameSaver 9128 is connected to NetScout’s probe,
which is using NetScout’s NMS application to provide full Layer 1 – 7 probe
capability at the central or regional site.
Central
Site
NetScout
NMS
Application
Frame
Relay
Network
NetScout
Probe
Frame
Relay
Router
FrameSaver
9128
Unit
Remote
Sites
Frame
Relay
Router
FrameSaver
9124
Unit
Frame
Relay
Router
FrameSaver
9126
Unit
Frame
Relay
Router
FrameSaver
9128
Unit
98-15873a
Diagnostic and statistical information is continuously collected every 15 minutes
for 24 hours by the FrameSaver SLV units, with daily totals for up to 5 days. This
information continues to be collected, even when frequent communication with
the management station is not possible or desired due to bandwidth restrictions
or network outages. As a result, the NMS application does not have to use
networking bandwidth and CPU time to repeatedly query the remote FrameSaver
unit for information, reducing network load and maximizing use of the information
collected.
FrameSaver units can also respond to multiple managers, and each manager
can pick and choose from the information collected, selecting and collecting only
the information that is important to them through internal thresholds in the
NetScout NMS.
9191-A2-GH30-00
DRAFT — June 1999
3-7
Mixing FrameSaver Devices
Deciding which frame relay FrameSaver unit is needed at a central or remote site
is a matter of evaluating the site’s traffic volume and the number of sites that
need to be backed up when there is a failure.
A large central site’s requirement for high-speed and high-volume, and multiple
site backup capability, indicates the need for a FrameSaver 9128 unit at this site.
Connecting a RMON probe to the FrameSaver unit and using NMS application
software that supports RMON MIBs will provide full remote monitoring capability
at the site.
In addition, not all remote sites need to have the same frame relay FrameSaver
unit. They can have:
H
All FrameSaver 9126 units at the remote sites.
H
FrameSaver 9128 units at some remote sites and FrameSaver 9126s and
FrameSaver 9x24s at others.
H
FrameSaver 9128, 9126, and 9x24 units at remote sites where RMON is
desired or needed, and FrameSaver 9x20s at others.
NOTE:
The additional capabilities provided by NextEDGE and FrameSaver SLV
units include:
— Intelligent latency and delivery verification.
— TruePut data delivery.
— RMON data collection and SLV reporting.
— Configurable alarm thresholds and custom history buckets.
— Interoperability with NetScout applications.
As a result, mixing SLV and non-SLV units is not recommended even
though FrameSaver SLV units support non-SLV FrameSaver units.
3-8
DRAFT — June 1999
9191-A2-GH30-00
Using All 9126 FrameSaver Units at Remote Sites
One of the most common and practical applications for frame relay FrameSaver
units is to use a FrameSaver 9128 unit at the central site and FrameSaver 9126
units at most remote sites.
The example below shows this application.
H
At the central site, the FrameSaver 9128 supports up to 120 remote sites. In
typical applications, a multiplexed PVC is expected from each remote unit
containing a PVC from the data port, plus a PVC for management.
H
At remote sites, two DLCIs from each FrameSaver unit are aggregated onto
one PVC going through the frame relay network to the central site. Each
unit’s multiplexed PVC contains one DLCI from its data port and one DLCI for
management.
Frame
Relay
Network
Customer
NMS
FrameSaver
9126
Unit
FT1
Network
256K T1
Central
Site
FR
FrameSaver
9126
Unit
256K T1
T1
768K
Frame
Relay
Router
FR
FrameSaver
9128
Unit
Frame
Relay
Router
PVCs
256K T1 FrameSaver
9126
Unit
FR = Frame Relay
Physical Connection
PVC Connection
Frame
Relay
Router
FR
Frame
Relay
Router
98-15871a
This PVC multiplexing is a patented method that provides the ability to multiplex
frame relay frames coming from multiple DLCIs onto a single DLCI, sharing a
single PVC connection.
9191-A2-GH30-00
DRAFT — June 1999
3-9
Mixing FrameSaver Units at Remote Sites
Not all remote sites need to be equipped the same. For example, there can be all
FrameSaver 9126 units at the remote sites, or there can be a mix of FrameSaver
SLV products.
The example that follows illustrates this. It shows two remote sites providing both
data and voice service and supporting remote monitoring, one using a
FrameSaver 9126 and the other using a FrameSaver 9124. The other remote site
provides data-only service using a FrameSaver 9624.
PBX
FT1
Network
NetScout
NMS
Network-Based
Voice Service
Central
Site
T1
768K
Frame
Relay
Router
FrameSaver
9126 Unit
FR
Port 1
256K T1
256K T1
FrameSaver
9124 Unit
FR
FrameSaver
9128 Unit
PVCs
PBX
DSX-1
56K DDS
DSX-1
Frame
Relay
Network
FR = Frame Relay
Physical Connection
Frame
Relay
Router
PBX
DSX-1
Frame
Relay
Router
FrameSaver
9624 Unit
FR
Frame
Relay
Router
98-15872a
PVC Connection
The remote site shown as a 9120 unit can be a 9128, as shown in the SLV Frame
Relay Access on page 3-3, which is the recommended network configuration.
3-10
DRAFT — June 1999
9191-A2-GH30-00
PVC Multiplexing and Port Aggregation Features
When FrameSaver units are at each end of the circuit, the FrameSaver unit
provides the ability to multiplex the data of multiple DLCIs onto a single network
DLCI. This feature is referred to as PVC multiplexing. PVC multiplexing allows
PVC diagnostic tests to be run without disrupting data.
In addition, the NextEDGE unit allows two ports to share a single frame relay link.
This feature is called port aggregation. Since only one physical network
connection is required, this feature reduces port charges.
Both multiplexing and port aggregation use the following network configuration.
The example shows frame relay data coming in over Port-1 (or Port-1 and
Port-2), with the frames being multiplexed onto a single network connection.
PVCs are aggregated in the same manner.
SNMP
NMS
User
Data
FrameSaver
Unit
FR
Frame
Relay
Router
FR
NTU
Frame
Relay
Network
NTU
FrameSaver
Unit
FR
Management
Data
Management
Data
PVCs Contain
Multiplexed
Management
EDLCIs and
User Data
FR
Frame
Relay
Router
Physical Connection
PVC Connection
FR = Frame Relay
99-16283
This sharing of PVCs (i.e., multiplexing user DLCIs with management
data/frames with user data/frames) is a proprietary method that is patented.
When using this method:
H
The first EDLCI, EDLCI 0, is used for the Port-1 data, and no overhead is
associated with the multiplexing for EDLCI 0. Subsequent DLCIs have two
bytes of overhead associated with them.
H
Another EDLCI, EDLCI 1, is used for Port-2 data.
H
A diagnostic EDLCI, which is transparent to the user, is also created on each
multiplexed DLCI on the network data port. This allows nondisruptive PVC
diagnostic tests to be run, as well as end-to-end communication of network
latency, topology, and data delivery information.
H
A management EDLCI, EDLCI 2, is created to route management data
through the network data port. This allows for nondisruptive multiplexing of
management data with user data and provides router-independent
management of remote units.
To use this feature, the network DLCI Type must be Multiplexed.
9191-A2-GH30-00
DRAFT — June 1999
3-11
Using Auto-Configuration
When the Frame Relay Discovery feature is used, DLCI configuration and PVC
connection occur automatically. Based upon the network LMI status response
message, the FrameSaver unit “discovers” network DLCIs and captures the
network’s CIR (committed information rate), provided the network switch supports
this feature (e.g., Stratacom switch DLCI, plus CIR). Network and Port interface
DLCIs with the same number are created and connected automatically.
All automatically configured network DLCIs are multiplexed, allowing for the
creation of a management diagnostic EDLCI (embedded DLCI) being created.
When management data is multiplexed with user data, two EDLCIs are created
from the network DLCI, one matching DLCI for user data on Port-1, and another
one for management (Mgmt) information.
PVCs configured to non-Paradyne units should not be multiplexed because only
FrameSaver models currently support PVC multiplexing and PVC diagnostics.
However, when the unit at the other end is not a FrameSaver unit, PVC
diagnostic tests and SLV communication between FrameSaver units are
disruptive to user data.
The following illustrations show the DLCI records and PVC connections created
when a particular Frame Relay Discovery Mode is selected. The tables show the
automatic configuration that takes place within the FrameSaver unit.
Refer to Setting Up Auto-Configuration in Chapter 11, Setup, for additional
information.
This example shows the 1-port management application (1MPort).
NextEDGE System
NextEDGE
FrameSaver
DTE
TMTM
DLCI 201
SLV
DLCI 201
K
O
NET Port
9191
Port 1
Frame
Relay
Network
M
AL
T
TS
P
BK
M
AL
SIG
F
O
O
DSX/PRI
Contains 1 EDLCI:
– Port-1
F
O
O
NETWORK
SIG
Network Side
of LMI
M
AL
K
2-O
3-12
K
PVC Connection
1-O
PORT
Physical Connection
User Side
of LMI
99-16397
FR Discovery
Mode Selection
Source
Interface
Source
DLCI
Primary
Primary
Primary
Destination
Destination Destination
Interface/Link DLCI
EDLCI
One port with
Management
(1MPort)
Port-1
DLCI 201
Network
Internal
Mgmt201
DRAFT — June 1999
DLCI 201
EDLCI 0
EDLCI 2
9191-A2-GH30-00
The following example shows the 1-port, nonmanagement configuration (1Port).
NextEDGE
FrameSaver
NextEDGE
System
Mgmt 201
TMTM
DTE
SLV
DLCI 201
DLCI 201
K
O
9191
M
AL
NET Port
T
TS
Port 1
P
BK
F
O
O
M
AL
NETWORK
SIG
F
O
O
DSX/PRI
SIG
Network Side
of LMI
M
AL
K
K
1-O 2-O
PORT
User Side
of LMI
Physical Connection
PVC Connection
Frame
Relay
Network
Contains 2 EDLCIs:
– Port-1
– Management (Mgmt)
99-16398
FR Discovery
Mode Selection
Source
Interface
Source
DLCI
Primary
Primary
Primary
Destination
Interface/Link DLCI
EDLCI
One port with
No Management
(1Port)
Port-1
DLCI 201
Network
DLCI 201
EDLCI 0
The following example shows the 2-port management configuration (2MPort).
NextEDGE
System
DTEs
NextEDGE
FrameSaver
DLCI 201
Mgmt 201
TMTM
SLV
Port 1
DLCI 201
DLCI 201
K
O
M
AL
P
BK
F
O
O
M
AL
NETWORK
SIG
F
O
O
DSX/PRI
SIG
M
AL
K
1-O
2-O
PORT
K
Physical Connection
PVC Connection
9191-A2-GH30-00
NET Port
T
TS
Network Side
of LMI
9191
Port 2
Frame
Relay
Network
User Side
of LMI
Contains 3 EDLCIs:
– Port-1
– Port-2
– Management (Mgmt)
99-16396
FR Discovery
Mode Selection
Source
Interface
Source
DLCI
Primary
Primary
Primary
Destination
Interface/Link DLCI
EDLCI
Two ports with
Management
(2MPort)
Port-1
DLCI 201
Network (NET)
Port-2
DLCI 201
EDLCI 1
Internal
Mgmt201
EDLCI 2
DRAFT — June 1999
DLCI 201
EDLCI 0
3-13
Back-to-Back Operation
Back-to-back operation can be achieved by connecting two FrameSaver units
using a network crossover cable, as in a test bench setup or a point-to-point
configuration using a leased line. This configuration is useful for private frame
relay networks, or for demonstrations when a frame relay circuit is not available.
This feature is for dry copper applications only, when there are no frame relay
switches at either end.
This configuration is shown in the illustration below.
T1 Crossover
Cable
Frame
Relay
Router
NextEDGE
System
NextEDGE
System
Frame
Relay
Router
99-16395
Using this feature, only one FrameSaver unit must be configured for
Back-to-Back operation so it presents the network side of the UNI to the other
unit. The other FrameSaver unit must be configured for Standard operation,
which is the setting for normal operation.
See Setting Up Units for Back-to-Back Operation in Chapter 10, Operation and
Maintenance, for additional information.
3-14
DRAFT — June 1999
9191-A2-GH30-00
Typical T1 TDM Applications
The following example shows a typical application of the NextEDGE system with
a T1 TDM NAM. For additional T1 TDM applications, see Chapter 11, Application
Modules.
T1 TDM NAM with High Speed Data
This T1 TDM NAM application supports two ports of high-speed data. The
following diagram depicts a router and a mainframe.
Cluster
Controller
FEP
Terminal
Port-2
FR
Router
FR
Port-1
NextEDGE
System
Port-2
FR
Port-1
NextEDGE
System
FR
Router
FR = Frame Relay
Mainframe
99-16375
The data moving through the FEP and the cluster controller is heritage data that
is not available on the LAN. Because the T1 TDM NAM has two data ports, the
router-based data can easily be added to the network without disrupting the
existing network operations.
allows the router connection to increase in speed. It also allows the FEP-based
data to reduce its data rate as the amount of data transmitted on this route
declines naturally over time.
Additional data ports can be added using a 4-port Synchronous Data APM.
9191-A2-GH30-00
DRAFT — June 1999
3-15
3-16
DRAFT — June 1999
9191-A2-GH30-00
User Interface and
Basic Operation
4
This chapter tells you how to access, use, and navigate the menu-driven user
interface. It includes the following information:
H
Logging On on page 4-2.
H
Main Menu on page 4-5.
H
Screen Work Areas on page 4-6.
H
Navigating the Screens on page 4-7.
— Keyboard Keys on page 4-7.
— Function Keys on page 4-8.
— Selecting from a Menu on page 4-9.
— Switching Between Screen Work Areas on page 4-9.
— Selecting a Field on page 4-10.
— Entering Information on page 4-10.
What appears on the screens depends on:
9191-A2-GH30-00
H
Current configuration – How your network is currently configured.
H
Security access level – The security level set by the system administrator
for each user.
H
Data selection criteria – What you entered in previous screens.
DRAFT — June 1999
4-1
Logging On
Start a session using one of the following methods:
H
Telnet session over the COM port or modem port via:
— An in-band management channel through the frame relay network.
— A local in-band management channel configured on the DTE port
between the NextEDGE system and the router.
H
Dial-in connection using the internal modem.
H
Direct terminal connection over the COM port.
When logging on, the menu-driven user interface screen is blank. Press Enter to
activate the interface. One of the following occurs:
H
If no security was set up or security was disabled, the Main Menu screen
appears (see page 4-5). You can begin your session.
H
If security was set up and is enabled, you are prompted for a login. Enter
your login ID and password.
When the user interface has been idle, a session is automatically ended and the
screen goes blank when the unit times out. Press Enter to reactivate the
interface.
4-2
DRAFT — June 1999
9191-A2-GH30-00
" Procedure
To log in when security is being enforced:
1. Enter your assigned Login ID and press Enter.
2. Enter your Password and press Enter.
— Valid characters – All printable ASCII characters
— Number of characters – Up to 10 characters can be entered in the
Login ID and Password fields
— Case-sensitive – Yes
An asterisk ( *) appears in the password field for each character entered.
If your login was . . .
Then the . . .
Valid
Main Menu appears (see page 4-5).
Begin your session.
Invalid
Message, Invalid Password, is displayed on line 24,
and the Login screen is redisplayed.
After three unsuccessful attempts:
– A Telnet session is closed.
– The User Interface Idle screen appears for a
directly-connected terminal.
– The internal modem connection is disconnected.
– An SNMP trap is generated.
Access is denied.
See your system administrator to verify your login
(Login ID/ Password combination).
9191-A2-GH30-00
DRAFT — June 1999
4-3
If two sessions are already active. Wait and try again.
H
If attempting to access the unit through Telnet, the local Telnet client process
returns a Connection refused: message at the bottom of the screen.
H
If attempting to access the unit over the COM port or modem port, not via
Telnet, the User Interface Already In Use screen is redisplayed.
The type of connection (Telnet Connection, Direct COM Port Connection, or
Direct Modem Port Connection) for each current user is identified, along with
the user’s login ID.
" Procedure
To end the session:
1. Press Ctrl-a to switch to the function keys area of the screen.
2. Type e ( Exit) and press Enter.
— For a COM port-connected terminal, the session is ended.
— For a modem port-connected terminal, the session is ended and the
modem is disconnected.
— For a Telnet connection, the session is closed and, if no other Telnet or
FTP session is occurring over the connection, the modem is
disconnected.
If ending a session from the Configuration branch, see Saving Configuration
Options in Chapter 8, Configuration.
4-4
DRAFT — June 1999
9191-A2-GH30-00
Main Menu
Entry to all of the NextEDGE system’s tasks begins at the Main Menu, which has
five menus or branches. The Access Level at the top of the screen only appears
when security has been set up.
ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ
main
Device Name: Node A
Slot: 1 Type: T1 FR NAM
Access Level: 1
PARADYNE 9191
04/26/1999 23:32
MAIN MENU
Status
Test
Configuration
Auto-Configuration
Control
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Ctrl-a to access these functions
Exit
Select . . .
To . . .
Status
View diagnostic tests, interfaces, PVC connections, and
statistics.
Also, to display LEDs and NextEDGE system identity
information.
Test
Select and cancel test for the NextEDGE system’s interfaces.
Configuration
Display and edit the configuration options.
Auto-Configuration
Configure basic access unit setup automatically based upon a
selected application.
Automatically populate network and data port DLCI
configuration options with numeric settings.
Control
Control the async user interface for call directories, device
naming, login administration, and selecting software releases.
Also, to initiate a power-on reset of the NextEDGE system.
See Appendix A, Menu Hierarchy, for a pictorial view of the menu hierarchy,
which represents the organization of the NextEDGE system’s menus and
screens.
9191-A2-GH30-00
DRAFT — June 1999
4-5
Screen Work Areas
There are two user work areas:
H
Screen area – Where you input information into fields.
H
Function keys area – Where you perform specific screen functions.
Below is a sample configuration screen for a FrameSaver NAM.
Model Number
Menu Path
Device
Name
Screen
Area
Function
Keys Area
Date and Time
main /config/port/physical
Device Name: Node A
Slot: 1 Type: T1 FR NAM
PARADYNE 9195
04/26/1998 23:32
DATA PORT PHYSICAL OPTIONS
Port Status:
Port Use:
Port Type:
Port Base Rate (Kbps):
Invert Transmit Clock
Transmit Clock Source:
Invert Transmit Clock:
Monitor DTR:
Monitor RTS (Control):
Port (DTE) Initiated Loopbacks:
PORT 1
Enable
Synchronous Data
V.35
Nx64
Disable
Internal
Disable
Enable
Enable
Disable
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Exit
Ctrl-a to access these functions, ESC for previous menu
MainMenu
Save
Copy
Message Area
Screen Format
Description
Menu Path
Menu selections made to reach the current screen.
Device Name
Customer-assigned identification of the NextEDGE
system.
9191, 9161, or 9261
NextEDGE system’s model number.
Screen Area
Selection, display, and input fields for monitoring and
maintaining the NextEDGE system.
Function Keys Area
Specific functions that can be performed by pressing
a specified key, then pressing Enter.
Message Area
System-related information and valid settings for
input fields in the lower left corner.
System and Test Status messages in the lower right
corner.
4-6
DRAFT — June 1999
9191-A2-GH30-00
Navigating the Screens
You can navigate the screens by:
H
Using keyboard keys.
H
Switching between the two screen work areas using function keys.
Keyboard Keys
Use the following keyboard keys to navigate within the screen area:
9191-A2-GH30-00
Press . . .
To . . .
Ctrl-a
Move cursor between the screen area and the
screen function keys area.
Esc
Return to the previous screen.
Right Arrow (on same screen row), or
Tab (on any screen row)
Move cursor to the next field.
Left Arrow (on same screen row), or
Ctrl-k
Move cursor to the previous field.
Backspace
Move cursor one position to the left or to the
last character of the previous field.
Spacebar
Select the next valid value for the field.
Delete (Del)
Delete character that the cursor is on.
Up Arrow or Ctrl-u
Move cursor up one field within a column on the
same screen.
Down Arrow or Ctrl-d
Move cursor down one field within a column on
the same screen.
Right Arrow or Ctrl-f
Move cursor one character to the right if in edit
mode.
Left Arrow or Ctrl-b
Move cursor one character to the left if in edit
mode.
Ctrl-l
Redraw the screen display, clearing information
typed in but not yet entered.
Enter (Return)
Accept entry or display valid options on the last
row of the screen when pressed before entering
data or after entering invalid data.
DRAFT — June 1999
4-7
Function Keys
All function keys (located in the lower part of the screen; see the example on
page 4-6) operate the same way throughout the screens. They are not
case-sensitive, so upper- or lowercase letters can be used interchangeably.
These keys use the following conventions:
4-8
Select . . .
For the screen
And press Enter to . . .
function . . .
M or m
MainMenu
Return to the Main Menu screen.
E or e
Exit
Terminate the async terminal session.
N or n
New
Enter new data.
O or o
Modify
Modify existing data.
L or l
De l ete
Delete data.
S or s
Save
Save information.
R or r
Refresh
Update screen with current information.
C or c
ClrStats
Clear network performance statistics and refresh the
screen.
U or u
PgUp
Display the previous page.
D or d
PgDn
Display the next page.
DRAFT — June 1999
9191-A2-GH30-00
Selecting from a Menu
" Procedure
To select from a menu:
1. Tab or press the down arrow key to position the cursor on a menu selection,
or press the up arrow key to move the cursor to the bottom of the menu list.
Each menu selection is highlighted as you press the key to move the cursor
from position to position.
2. Press Enter. The selected menu or screen appears.
" Procedure
To return to a previous screen, use either of the following methods:
H
Press the Escape (Esc) key until you reach the desired screen.
H
Switch to the function keys area of the screen, and select MainMenu.
Switching Between Screen Work Areas
Use Ctrl-a to switch between screen areas (see page 4-6).
" Procedure
To switch to the function keys area:
1. Press Ctrl-a to switch from the screen area to the function keys area.
2. Select either the function’s designated (underlined) character or
Tab to the desired function key.
3. Press Enter. The function is performed.
To return to the screen area, press Ctrl-a again.
9191-A2-GH30-00
DRAFT — June 1999
4-9
Selecting a Field
Once you reach the desired menu or screen, select a field to view or change, or
issue a command.
Press the Tab or right arrow key to move the cursor from one field to another. The
current setting or value appears to the right of the field.
Entering Information
You can enter information in one of three ways. Select the field, then:
H
Manually type in (enter) the field value or command.
Example:
Entering bjk as a user’s Login ID on the Administer Logins screen ( from the
Control menu/branch ).
H
Type in the first letter(s) of a field value or command, using the unit’s
character-matching feature.
Example:
When configuring a port’s physical characteristics with the Port (DTE)
Initiated Loopbacks configuration option/field selected ( possible settings
include Disable, Local, DTPLB, DCLB, and Both ), entering d or D displays
the first value starting with d – Disable. In this example, entering dt or DT
would display DTPLB as the selection.
H
Switch to the function keys area and select or enter a designated
function key.
Example:
To save a configuration option change, select Save. S or s is the designated
function key.
If a field is blank and the Message area displays valid selections, press the
spacebar; the first valid setting for the field appears. Continue pressing the
spacebar to scroll through other possible settings.
4-10
DRAFT — June 1999
9191-A2-GH30-00
5
This chapter includes:
H
OpenLane Management features.
H
Installation and Setup of the OpenLane DCE Manager and Performance
Wizard on page 5-2.
H
Viewing OpenLane Performance Wizard Graphs specific to FrameSaver SLV
data collection and display on page 5-10.
H
Creating OpenLane Service Level Management (SLM) Reports on
page 5-24.
The OpenLane Advantage
OpenLane Management features:
H
Nondisruptive tests from OpenLane NMSs
H
Layers 1, 2 and 3 monitoring
H
Real-time and historical focus
H
Diagnostic focus
— Alarm and operational status monitoring
— WAN errors and congestion monitoring
— Nondisruptive network integrity checks and latency tests
— Capacity analysis
— Throughput utilization
— Data delivery and congestion analysis
— Patent pending PVC Data Delivery Analysis
H
9191-A2-GH30-00
Service level accounting and quality of service verification
DRAFT — June 1999
5-1
Using an OpenLane NMS Application
For additional information about accessing and managing the FrameSaver SLV
unit through OpenLane DCE Manager and OpenLane Performance Wizard, and
for hardware and software requirements necessary to support these applications
refer to the:
H
OpenLane DCE Manager User’s Guide to help you set up and configure
devices and their interfaces; and monitor, operate, and perform diagnostic
testing using the Unix-based management application.
H
OpenLane DCE Manager for HP OpenView for Windows User’s Guide to
help you set up and configure devices and their interfaces; and monitor,
operate, and perform diagnostic testing using the Windows-based
management application.
H
OpenLane Performance Wizard User’s Guide to query devices for both real
time and historical data, and to display graphs.
Installation and Setup of DCE Manager
OpenLane DCE Manager is used in conjunction with HP OpenView or NetView,
and if performance graphs are wanted, used with OpenLane Performance
Wizard, as well.
When adding FrameSaver SLV units to your network, follow the procedures
provided in the appropriate DCE Manager User’s Guide:
H
Install the OpenLane DCE Manager for Unix or Windows software and open
the application as specified in the applicable User’s Guide.
H
Use the Autodiscovery feature to discover the new FrameSaver SLV units.
Refer to the appropriate User’s Guide for installation and setup, and information
about accessing and managing the FrameSaver SLV unit through OpenLane
DCE Manager:
H
OpenLane DCE Manager User’s Guide
H
OpenLane DCE Manager for HP OpenView for Windows User’s Guide
Installation and Setup of Performance Wizard
Performance Wizard can be used alone, or it can be invoked from an HP
OpenView or NetView window. To use this application:
5-2
H
Install the OpenLane Performance Wizard software and open the application.
H
Add frame relay agents to the Device Explorer, unless using DCE Manager.
H
Set up historical data collection.
DRAFT — June 1999
9191-A2-GH30-00
Installing and Starting OpenLane Performance Wizard
Installation instructions are located in the OpenLane Performance Wizard
User’s Guide. Open the application by following the instructions contained in
Getting Started with the Performance Wizard. Depending upon your platform, see
one of the following procedures:
H
Installing on Solaris, HP-UX, and AIX
H
Installing on Windows NT or Windows 95
The OpenLane Performance Wizard Device Explorer window opens. This window
has three columns of information:
H
End Point – Shows the devices in the network and their interfaces.
H
Connection – Shows the PVC connections.
H
Historical Collection – Shows whether historical data is being collected for
the interface or PVC.
Based upon the item that is highlighted, appropriate graph selection buttons
appear near the bottom of the window. Once a graph window is open, other
graphs can be launched from the graph selections under the menu bar.
Notice the green icon at the bottom of the window. Move the cursor over the icon
and the status message says Historical Daemon Running. If the Historical
Daemon is not running, a red circle with a slash through it overlays the icon.
9191-A2-GH30-00
DRAFT — June 1999
5-3
Adding FrameSaver SLV Units to Your Network
Use either one of these procedures to add FrameSaver SLV units to your
network.
" Procedure
To add an SLV unit from HP OpenView or NetView:
1. Use the HP OpenView or NetView autodiscovery feature to create submaps
and discover an SLV unit.
2. Click on the submap containing the SLV unit, then click on the icon for
the unit.
3. Use the following HP OpenView menu selection sequence to access
Performance Wizard Device Explorer:
Windows: Control → Performance Wizard → Device Explorer
Unix: Performance → Performance Wizard → Device Explorer
The OpenLane Performance Wizard Device Explorer window opens so you
can change or verify the Community Name and view the graphs.
Refer to your DCE Manager User’s Guide for additional information.
" Procedure
To add an SLV unit from Performance Wizard Device Explorer:
1. Select New Device... from the File menu. The New Device dialog box opens.
2. Enter the unit’s IP address or IP hostname in the Device Name field.
3. Change the Community Name, if necessary.
4. Select the OK button. The New Device dialog box closes and the unit’s IP
address or IP hostname appears in the Device Explorer device display area.
Refer to Populating the Device Display Area in Chapter 2, Using the Device
Explorer, of the OpenLane Performance Wizard User’s Guide for additional
information.
5-4
DRAFT — June 1999
9191-A2-GH30-00
Setting Up for Collection of Historical Data
" Procedure
To specify collection of historical data:
1. Select an interface or PVC so it is highlighted.
2. Click the right mouse button and select Historical Collection... from the menu.
The following dialog box opens.
3. Change the frequency of samples to be taken and the unit of time to be used
for each of the graphical views.
4. Click on the Active box for the graphical views wanted so a checkmark
appears in the box.
5. Select the Test button to verify that the data collection parameters are
correct. OK should appear in the message area.
6. Select the OK button. The Edit Historical Collection dialog box closes, and an
OK appears under the Historical Collection column for the interface or PVC
selected, and for the device.
7. Click on Action at the menu bar, and select Start Historical Daemon if it is not
currently running. Check the lower right corner of the Device Explorer window
to see whether Historical Daemon is running (see the example on
page 5-3).
9191-A2-GH30-00
DRAFT — June 1999
5-5
Accessing NetScout Manager Plus
A direct link to the NetScout Manager Plus application is provided by OpenLane
Performance Wizard. Use this feature to launch NetScout reports.
" Procedure
To access the NetScout Manager Plus main window:
1. Select Start NetScout Manager from the Action menu.
The NetScout Manager Plus main window appears.
2. Select the FrameRelay radio button from the agent type selection bar (on the
left side of the window).
Applicable icons appear on the right side of the main window.
Refer to Launching NSM in Chapter 3 of the NetScout Manager/Plus & NetScout
Server Administrator Guide for information about how to start reports.
5-6
DRAFT — June 1999
9191-A2-GH30-00
Creating PVC Connections
Port-1 PVC definitions need to be created between two endpoints in the network.
Network PVCs were automatically created when the unit is discovered.
" Procedure
To create PVC definitions:
1. From Device Explorer, select a device’s DLCI so it is highlighted.
2. Click the right mouse button and select Connection... from the menu. The
Edit Connection dialog box opens, with the network collapsed.
3. Expand the remote network device in the device display area so that its
DLCIs are shown.
4. Select the appropriate DLCI so it is highlighted.
The selected DLCI numbers appear in the Connection Name field for both
ends of the connection, which can be edited for a more meaningful name.
5. Select the Connect button. The Edit Connection dialog box closes and the
PVC appears under the Connection column for the devices at both ends of
the connection.
Repeat the procedure until all Port-1 DLCI connections have been defined.
9191-A2-GH30-00
DRAFT — June 1999
5-7
Setting Frame and Burst Ranges
You can configure frame size and burst upper limits to:
H
Match service level agreement parameters.
H
Identify problem areas.
H
Display the Frame Burst Breakdown graph.
H
Assist in troubleshooting.
H
Match the site’s traffic patterns.
" Procedure
To set frame and burst range parameters:
1. From Device Explorer, select a device’s DLCI so it is highlighted.
2. Select Configure Device... from the Edit menu.
The Configure Device dialog box opens to the Frame Ranges tab, with the
Burst Ranges tab in the background.
3. Select the Burst Ranges tab to bring it to the forefront if you want to set Burst
Range Upper Limits.
The procedure for setting the frame size and burst upper limits is the same.
5-8
DRAFT — June 1999
9191-A2-GH30-00
4. Select a row in the box below the Frame Size Range Upper Limit (Octets) or
Burst Range Upper Limit (Octets) heading so it is highlighted, and the
selected value appears in the Edit box.
NOTE:
If you change frame size ranges, the frame size distribution cannot be
displayed by the NetScout Manager. Performance Wizard is
recommended for display.
5. Change the Upper Limit value, and select the Apply button.
If you change the upper limit, the numbers under the Frame Size Range
Upper Limit (Octets) heading are re-sorted going from lowest to the highest.
When editing Upper Limits, you cannot:
— Enter letters or characters; only numbers are permitted.
— Have duplicate numbers; each range limit must be unique.
— Enter a number lower than the lowest limit shown, or higher than the
highest limit, which is all 9s (e.g., 9999999).
6. Continue Steps 3 through 5 until all desired edit changes have been made,
then select the Set button. The changed settings become the new Upper
Limits.
Getting Error Messages
Error messages may appear in the messages area at the bottom of the window to
indicate when there is a problem (e.g., Unable to set table. SNMP Error: No
such name). When this type of error occurs, you need to resynchronize with the
FrameSaver unit.
" Procedure
To resynchronize:
1. Leave the current view and return to the Device Explorer main window.
2. Select Device Sync... from the File menu.
3. Return to the view where the error message appeared. The error message
should be gone.
If the error message is not cleared, see the OpenLane Performance Wizard
User’s Guide, or the Help feature, for additional information.
9191-A2-GH30-00
DRAFT — June 1999
5-9
Viewing OpenLane Performance Wizard Graphs
The following OpenLane Performance Wizard graphs support FrameSaver SLV
units, integrating the new service level verifier capability provided by FrameSaver
SLV units into Device Explorer:
H
Frame Relay Access Channel Aggregated Summary – Capacity,
Throughput, and Heaviest Users – Output
H
Frame Relay Physical Link Integrity – Throughput, Errored Frames, LMI
Signaling Errors, and Unknown Protocol Frames
H
PVC Throughput – Transmit and Receive
H
Frame Relay DLCI Congestion – Capacity, Throughput, and Congestion
H
PVC Data Delivery Analysis – Transmit Bit Burst Analysis As % CIR, Round
Trip Network Latency, End-to-End Data Delivery Success, and Transmit
Frame Size Distribution
Status and error messages appear in the messages area at the bottom of
Performance Wizard windows. If an error message appears, try and
resynchronize with the FrameSaver unit.
The following sections show and discuss the frame relay windows that can be
accessed when monitoring a FrameSaver SLV unit.
Refer to the OpenLane Performance Wizard User’s Guide, or the Help feature,
for additional information.
5-10
DRAFT — June 1999
9191-A2-GH30-00
Frame Relay Access Channel Aggregated Summary
For a complete view of an interface’s traffic, this graph summary brings together
the information needed to determine how well an interface’s, or link’s, capability is
being utilized.
Correlate the time at which a problem occurred to the following graphs.
9191-A2-GH30-00
H
Capacity – Shows what percent of the physical link is being used. A
measurement is provided for both incoming and outgoing data. The
percentage is based upon line speed.
H
Throughput – Shows the actual volume of data in kilobits per second for
both incoming and outgoing data over a physical link. The line speed is also
shown so you can easily see when the link’s physical capacity is about to be
exceeded.
DRAFT — June 1999
5-11
H
Heaviest Users – Output – Shows which DLCIs are generating the most
traffic over the frame relay link. Up to three high-volume DLCIs can be
shown.
This information can be viewed in two forms:
— Graph – The data shown for each DLCI is a percent of the line speed
over time. Up to three high-volume DLCIs can be shown.
— Pie Chart – The data shown for each DLCI is a percent of the total output
per the most recent snapshot.
NOTE:
Position the cursor over a particular DLCI within the graph and press the
right mouse button to display a menu which includes the DLCI’s exact %
of Capacity. In the pie chart, the % of Capacity for the unused portion is
also shown.
If errors occurred when transmitted data bursts exceeded line capacity, looking at
the Heaviest Users should indicate the DLCI(s) most responsible for the problem.
Once identified, PVCs generating the greatest amount of traffic can be examined
further.
" Procedure
To immediately launch PVC graphs:
1. From within a Heaviest Users graph or pie chart, position the cursor over a
DLCI segment.
2. Press the right mouse button to display the menu.
3. Select either the PVC Throughput or PVC Congestion graph, or PVC Analysis
if viewing the aggregated summary for the network interface. See one of the
following:
— PVC Throughput for end-to-end connectivity between units at both ends
of the PVC, and to see the types of errors that are being recorded by
each unit.
— PVC Congestion for if the PVC is exceeding its contracted CIR and
whether it is causing network congestion.
— PVC Analysis for a more complete view of network traffic. Only appears
for a network interface.
5-12
DRAFT — June 1999
9191-A2-GH30-00
Frame Relay Physical Link Integrity
Use this grouping of graphs to relate actual throughput on the frame relay link to
the types of errors that are occurring. It can also be used to verify that the
network is operational and traffic is flowing normally.
9191-A2-GH30-00
DRAFT — June 1999
5-13
H
Throughput – Shows the actual volume of data in frames per second for
both incoming and outgoing data over a physical link. The line speed is also
shown so you can easily see when the link’s physical capacity is about to be
exceeded.
H
Errored Frames – Shows a count of errored or discarded frames over a
physical link for both incoming and outgoing data.
H
LMI Signaling Errors
— Only displayed if the Frame Relay on Data Port 1 interface was selected.
This is an errors-per-second count for each type of error detected:
Reliability Errors, Protocol Errors, and Channel Inactives.
— Unknown Protocol Frames shows the number of unknown protocol errors
received on the link.
If Frame Relay for Data Port 1 was selected, compare LMI Signaling Protocol
Errors against the Unknown Protocol Frames graph to see how many of the LMI
errors were due to wrong protocol being used.
See Frame Relay Performance Statistics in Chapter 11, Displaying System
Information, for additional information.
5-14
DRAFT — June 1999
9191-A2-GH30-00
H
Unknown Protocol Frames – Shows the number of frames per second that
were counted when the unit could not recognize the protocol used in the
packet.
See Chapter 11, Displaying System Information, for additional information on
these types of errors.
9191-A2-GH30-00
DRAFT — June 1999
5-15
H
Errored Seconds – Shows the percentage of time during which a Severely
Errored Seconds or Bursty Errored Seconds condition existed, calculated on
the percent of the time interval shown.
H
Transmission Errors – Shows the percentage of time during which an
Unavailable Seconds or Controlled Slip Seconds condition existed, calculated
on the percent of the time interval shown.
See Chapter 11, Displaying System Information, for information on these types of
errors.
PVC Throughput
Congestion and CIR issues are clearly identified by this window.
Using this window, you can determine end-to-end performance for a PVC. The
lines into the cloud change based upon the upper right radio button selected: Tx,
Rx, or Both directions. The radio buttons refer to the input and output of the
device.
Link Status next to each device indicate the link’s current status. Each device is
identified using a connection name, DLCI name, and DLCI number.
The Throughput graphs for each device shows the input and/or output for each
device. Lines are shown for CIR, physical link speed, and input and output in bits
per second.
5-16
DRAFT — June 1999
9191-A2-GH30-00
Variables that could appear in the panes below each graph include:
Variable Displayed
Indication
Frames Sent above CIR
Number of transmitted frames that exceeded the
contracted CIR.
Frames Sent within CIR
Number of transmitted frames that complied
with CIR.
Frames Sent marked DE
Transmit data on a management PVC is marked
discard eligible, so the network can discard the
lower-priority frame when there is congestion.
Frames discarded by the network
Number of transmitted frames that were
dropped.
Bytes Sent above CIR
Number of transmitted bytes over the contracted
CIR.
Bytes Sent within CIR
Number of transmitted bytes within or under the
contracted CIR.
Bytes discarded by the network
Number of transmitted bytes actually lost.
BECNs Received
Backward explicit congestion notification
(BECN) has been sent by the network, warning
that outbound frames may encounter congestion
and may be dropped.
BECNs seconds
Duration over which BECNs were received.
FECNs Received
Forward explicit congestion notification (FECN)
has been sent by the network, warning that
inbound frames may encounter congestion and
may be dropped.
FECNs seconds
Duration over which FECNs were received.
Congested seconds
Duration over which BECNs and FECNs were
received.
BECNs and FECNs indicate network congestion issues. Frames marked DE
indicate that the DLCI is partly responsible for the network congestion; the DLCI
has exceeded its contracted CIR.
When congestion is detected on the network, select the Congestion button under
the menu bar to verify whether the DLCI is the cause for the problem.
See Chapter 11, Displaying System Information, for additional information on
these types of errors.
9191-A2-GH30-00
DRAFT — June 1999
5-17
Frame Relay DLCI Congestion
Although used primarily for capacity planning and CIR negotiations, this group of
graphs can be used to assess whether a DLCI is contributing to network
congestion.
5-18
DRAFT — June 1999
9191-A2-GH30-00
H
Capacity – Shows how a DLCI’s capacity is being used for both incoming
and outgoing data. When the DLCI’s allocated bandwidth is underutilized, it is
time to renegotiate CIR and excess burst size agreements.
The DLCI’s capacity is calculated based upon its data rate and CIR, which is
provided in two graph views:
— % of Port Speed Capacity – Shows capacity calculated based upon the
FrameSaver unit’s data rate.
— % of CIR Capacity – Shows capacity calculated based upon the
FrameSaver unit’s CIR.
Compare how CIR and Line Speed on the graphs compare to the CIR and
Line Speed that had been configured, seen near the top of the window. The
percentages calculated are based upon those values.
When zero CIR has been configured, the speed of the link’s capacity is used
in the calculations instead of the speed of the DLCI’s allocated capacity.
These graphs are used primarily for capacity planning or in CIR negotiations.
H
Throughput – Shows the actual volume of data in kilobits per second for
both incoming and outgoing data over a frame relay PVC. Throughput only
appears when the port is connected to the frame relay network. CIR is also
shown so you can easily see when CIR is being exceeded.
When the DLCI is exceeding CIR, trying to deliver more data than was
contracted for, check the Round Trip Network Latency and End-to-End Data
Delivery graphs on the PVC Data Delivery Analysis window to verify that the
DLCI is the cause of apparent network problems.
H
Congestion – Helps determine the degree of traffic congestion on the
network, and the reason some frames may have been discarded by the
network.
The number of BECNs counted over time are shown. The network sends
BECNs as a warning that outbound frames may encounter congestion and
may be dropped.
When looking at these graphs, the % of Port Speed Capacity, % of CIR Capacity,
and Throughput line graph patterns should be essentially the same. The only
difference should be the scale values along the left side of each graph, based
upon the measurement being shown.
9191-A2-GH30-00
DRAFT — June 1999
5-19
PVC Data Delivery Analysis
For a more complete view of network traffic, this graph summary brings together
the information needed to determine the cause of frame relay lost packets and/or
excessive network latency. A patent is pending on this graphical report.
Network service providers can use this screen to help determine whether their
network or the customer’s data was the cause for a missed service level
agreement (SLA).
You can view the Transmit Burst Analysis As % CIR and End-to-End Data
Delivery Success graphs in either Bits or Frames by changing the radio button
selection. In this example, the Frames radio button was selected.
5-20
H
If Bits is selected, the Transmit Burst Analysis As % CIR graph is measured
in Total Mbps Tx, and the End-to-End Data Delivery Success graph is
measured in Total Kbps Tx.
H
If Frames is selected, both the Transmit Burst Analysis As % CIR and
End-to-End Data Delivery Success graphs are measured in Total Frames Tx.
DRAFT — June 1999
9191-A2-GH30-00
In most cases, transmission characteristics of the customer’s data rather than the
network is the cause of apparent network problems. This summary allows you to
determine the following:
H
Overutilization of the network, trying to deliver amounts of data well over CIR.
H
Data frames that are too large or small.
H
More packets are being sent than the receiving node can receive due to
differences in physical circuit capacity.
Any of these will cause the network switch’s egress queue to fill, increasing
latency and data loss.
H
Transmit Bit Burst Analysis As % CIR – Shows network utilization bursting
details to aid in determining the cause of frame relay lost packets and/or
excessive network latency. Tx Bit Burst Analysis is measured in megabits and
shows the exact distribution of transmitted data in relation to the DLCI’s CIR
and excess burst size.
The color displayed indicates whether the DLCI is or is coming close to
exceeding its purchased CIR and excess burst size.
Color
% of CIR
Indication
Blue
Less than or
equal to 99 %
Packets are within CIR.
Gold
100 –199 %
Packets are at or over CIR.
Pink
200 – 299 %
Packets are two times greater than the
contracted CIR.
Aqua
300 – 399 %
Packets are three times greater than the
contracted CIR.
Yellow
More than 399 %
Packets are four times greater than the
contracted CIR.
When zero CIR has been configured, the percentage breakdowns are based
on link speed instead of CIR.
If utilization is consistently under 50 % of CIR, the CIR contracted for should
be downgraded. If over 100 %, the DLCI may be ready for its CIR to be
upgraded.
When a DLCI is overutilizing the network, compare the Tx Bit Burst Analysis
graph against the following graphs to determine the cause:
— End-to-End Data Delivery Success to see if frames are being dropped.
— Round Trip Network Latency to see if the bursting is impacting latency.
9191-A2-GH30-00
DRAFT — June 1999
5-21
H
Round Trip Network Latency – Shows how fast the network is moving
traffic. Latency is the amount of time it takes a frame relay frame to travel
from one CPE end point to another and back. The times at which an average
of the frame relay frames are calculated is shown along the bottom, while the
delay is shown in milliseconds.
Any excessive spikes or increases in latency should be investigated further. It
could indicate a network problem, or it could indicate that the DLCI is
oversubscribed, exceeding CIR, and is sending frames that are filling up the
network switch’s egress queue, delaying network traffic.
To determine the exact cause of the delay, compare the Round Trip Network
Latency graph against the following graphs to determine the cause:
— Transmit Bit Burst Analysis As % CIR to see distribution of transmitted
data in relation to the DLCI’s CIR.
— Transmit Frame Size Distribution to see the size of the packets that were
transmitted.
H
End-to-End Data Delivery Success – Shows the exact number of bits that
were successfully delivered, as well as those that did not get delivered to the
end point node for a selected DLCI.
Data Delivery Success is measured in kilobits over time. The color displayed
indicates whether data are being delivered.
Color
Indication
Green
Data that has been delivered successfully.
Red
Data that has been dropped by the network.
Blue
CIR contracted.
Gold
Local line speed.
Pink
Remote line speed.
When frames are being dropped, compare this graph against the following
graphs to determine the cause:
— Transmit Bit Burst Analysis As % CIR to see distribution of transmitted
data in relation to the DLCI’s CIR.
— Transmit Frame Size Distribution to see the size of the packets that were
transmitted.
5-22
DRAFT — June 1999
9191-A2-GH30-00
H
Transmit Frame Size Distribution – Various service level agreement
parameters may be based on frame size, which may contribute to latency
and frames being lost. This graph shows the size of the packets being
transmitted, so you can compare frame size to your service level agreement.
Transmit Frame Size Distribution is measured over time in percent of all
transmitted packets within each of the following ranges:
Color
Packet Size in Bytes
Blue
Less than or equal to 127
Gold
128 – 255
Pink
256 – 511
Aqua
512 –1023
Yellow
More than or equal to 1024
Compare this graph with the following graphs:
— End-to-End Data Delivery Success to see if frames are being dropped.
— Round Trip Network Latency to see if frame size is impacting latency.
9191-A2-GH30-00
DRAFT — June 1999
5-23
Creating OpenLane
Service Level Management (SLM) Reports
The OpenLane SLM Reports (part of Performance Wizard) enables network
administrators of FrameSaver SLV devices to provide securely partitioned access
for their users to create and view reports, via the World Wide Web, that pertain
only to their portion of the frame relay network. These reports include a summary
of overall network performance, as well as detailed statistics on a per PVC basis
of network latency, availability, and frame delivery success rate (throughput) for
accurate service level agreement verification. This measurement of throughput
uses the Paradyne proprietary TruePut technology which precisely measures
both within and above CIR, eliminating inaccuracies due to averaging. Reports
are also available for physical inventory of the network’s device names, locations,
serials numbers, DLCIs, and port speeds.
Network performance data is gathered from all FrameSaver SLV RMON-2 user
history buckets at configurable intervals for 24 hours, allowing for offline or after
hours retrieval of all needed report data. Also, the FrameSaver SLV units can be
polled in real time for online troubleshooting and performance monitoring. All
devices must first be added to the OpenLane Device Explorer database.
Web Browsers Supported
Users interact with the system via a web browser. The following are
recommended:
H
Netscape Communicator 4.04 or higher
H
Microsoft Internet Explorer 4.0
The SLM Reports have been tested with the Apache web server, although other
web servers may work as well, including web servers that use Secure Socket
Layer (SSL) for data encryption. Be aware that encryption greatly slows the
throughput of the system. If the Apache web server is not installed, refer to the
Apache web site at http://www.apache.org for installation instructions.
5-24
DRAFT — June 1999
9191-A2-GH30-00
Installation and Setup of SLM Reports
Refer to the OpenLane Performance Wizard User’s Guide for installation and
operation instructions for the Performance Wizard, and follow the instructions
applicable to your network platform.
All of these reports can be seen online as well as provided on printed reports.
Displaying the Log-in Screen
The SLM Reports package is available for both network administrators and
customers via the web. You define the URL to access the SLM Reports, based on
where you have located the SLM server directories, e.g., x/OpenLane/index.html
Upon entering the URL of the server, a login screen appears. The following
screens differ, depending on whether you are
H
Administering customer profiles and data collection as the network
administrator, or
H
Viewing selected reports as a customer.
Enter your customer ID, then enter your User ID and Password in the pop-up
window.
Reports Administration
As the network administrator, you have the ability to perform the following
functions:
9191-A2-GH30-00
H
Create, modify and delete customer profiles. Customer profiles contain
information such as the customer’s name, account number, address
(including e-mail), phone number, a contact name, and any additional
comments. Customer profiles also contain the customer’s access level (either
reports-only or administrative). Via customer profiles, you determine which
web server users have access to what FrameSaver SLV devices for the SLM
Reports.
H
Modify authorized user logins. Determine which web server users are
authorized to log in as the customer listed in the profile.
H
Modify assigned devices. Determine which FrameSaver SLV devices in the
network the customer listed in the profile can access.
H
Administer data collection. Enable data collection on devices that have
already been added to the OpenLane Device Explorer database. For data
collection, a 12-hour window is recommended. Any data collection errors
causing a delay of over 24 hours will result in a loss of data.
DRAFT — June 1999
5-25
Viewing Reports
As a web user with a customer profile defined by your network administrator, you
have the ability to view reports for the FrameSaver SLV devices assigned to you.
Upon entering your customer ID, your User ID and Password in the pop-up
window, the FrameSaver SLV Reports window displays, giving you the
opportunity to select one the reports.
For specific information on SLM Reports, refer to the SLM Reports online help,
which contains detailed information consisting of a description and typical uses
for each report. An example is also provided to show how a company could use
the information provided by this powerful tool.
5-26
DRAFT — June 1999
9191-A2-GH30-00
6
This chapter includes:
H
Significant features of NetScout Manager Plus.
H
Hardware and software needed if you want to get these features.
H
Installation and setup of NetScout Manager Plus software.
H
Configuration of NetScout Manager Plus.
Release 5.5 of the NetScout Manager Plus software, due out later this year, will
provide FrameSaver SLV-specific support.
The NetScout Advantage
NetScout Manager Plus features:
H
Large central site location: Layers 2 through 7 monitoring,
Remote Probe location: Layers 1 through 3 monitoring
H
RMON1 and RMON2 customization
H
Flexible, customized, drill-down tool set
H
Historical and real time analysis and reporting
H
LAN, WAN, and switched LAN support
H
Protocol analysis
H
Threshold alarming
H
Web access
H
Familiar interface (almost identical to both Motif and Windows environments)
H
Integrates with other management systems
See the sections that follow to make sure you have the necessary hardware and
software to support this application.
9191-A2-GH30-00
DRAFT — June 1999
6-1
Minimum Hardware Required
Minimum hardware requirements for each NetScout NMS application are listed in
the table below.
Management Platform
System Hardware Needed
H Sun SPARC station or compatible station,
with minimum free disk space:
– For monitoring: 120 MB
– For reporting: 703 MB
H HP 9000, Series 700 or
NCR Unix SVR4, with
minimum free disk space:
H IBM RS/6000, with minimum free disk space:
H Fujitsu DS/90 Unix SVR4, with
minimum free disk space:
H Digital Alpha, with minimum free disk space:
H Minimum RAM:
H CD-ROM drive
NetScout Manager Plus for Windows
H IBM or IBM-compatible PC or
Windows NT workstation, 4.0 or higher
H Minimum RAM:
H Minimum free disk space:
H Super VGA (800 x 600 resolution) or higher,
with 256 colors
H CD-ROM drive
6-2
DRAFT — June 1999
9191-A2-GH30-00
Minimum Software Required
See the table below to determine whether you need to order additional software
to support FrameSaver SLV units.
Management Platforms
System Software Needed
H Sun SPARC or compatible station:
– SunOS 4.1.3, or
Solaris 2.5.1 or higher, with
OpenWindows 3.3, and if not using Motif,
SunOS Patch #100444-x, or
Motif Window Manager, using Motif 1.2.4
and X11R5 libraries
H HP 9000, Series 700:
– HP-UX 10.1, with
– Motif 1.2 and X11R5 libraries (included
with HP-UX)
H IBM RS/6000:
– AIX 4.2, with NetView for AIX 4.2
– Motif 1.2.4 and X11R5 libraries
H NCR Unix SVR4 5.3.2 – No additional
software required.
H Fujitsu DS/90 Unix SVR4 5.3.2:
– OSF/Motif 1.2 and X11R5 libraries
H Digital Alpha:
– Digital UNIX for Alpha 3.0 or higher
NetScout Manager Plus for Windows
H Microsoft Windows 95 for an IBM or
IBM-compatible PC
or
Windows NT 4.0
H Microsoft SQL Server, 6.5 or higher, and
32 Bit SQL Client if using Trend Reporter to
log and retrieve data
9191-A2-GH30-00
DRAFT — June 1999
6-3
Using a NetScout Manager Plus NMS Application
For additional information about accessing and managing the FrameSaver SLV
unit through NetScout Manager Plus, refer to the:
H
NetScout Manager/Plus User Guide to help you install the application,
monitor traffic, and diagnose emerging problems on network segments.
H
NetScout Manager/Plus & NetScout Server Administrator Guide to help you
configure agents, remote servers, and report templates using the various
NetScout products.
H
NetScout Probe User Guide to help you install and configure NetScout Probe
on network segments you want to monitor, as shown in SLV Frame Relay
Access in Chapter 3, Typical Applications.
Installing NetScout Manager Plus
Installation instructions are located in Chapter 2 of the NetScout Manager/Plus &
NetScout Server Administrator Guide. Depending upon your platform, see either:
H
Installing NSS/NSM/NSM+ Unix Version
H
Installing NSS/NSM/NSM+ Windows Version
Configuring NetScout Manager Plus
For the NetScout Manager Plus main window to appear, make sure your
environment is set up exactly as specified in your NetScout Readme file. You will
need to:
6-4
H
Copy the OpenLane Performance Wizard directory to a user directory.
H
Add frame relay agents to the NetScout Manager.
H
Configure agent properties.
H
Verify and correct domains and groups.
H
Monitor the agent and DLCIs.
DRAFT — June 1999
9191-A2-GH30-00
Before You Get Started
Before getting started, you need to copy some OpenLane Performance Wizard
directories to a NetScout Manager Plus user directory. Performance Wizard
provides these directories as a starting point for loading new alarms and creating
history files. A template of alarms and values for configuring alarms and several
templates for creating history files specific to the FrameSaver unit are available.
The Performance Wizard paradyne directories include the following:
H
Properties: paradyne.fsd file found in PerfWiz/netscout/alarms/directory.
H
Alarms: slvtemplate.fct file found in PerfWiz/netscout/alarms/directory.
H
User history: pd*.udh files found in PerfWiz/netscout/userHistory/directory.
These files should be moved to $NSHOME/usr so they can be used.
See Adding SLV Alarms Using a Template on page 6-10 and Creating History
Files on page 6-16 for additional information.
9191-A2-GH30-00
DRAFT — June 1999
6-5
Adding FrameSaver SLV Units to the NetScout Manager Plus Network
" Procedure
1. Bring up the NetScout Manager Plus main window.
2. Select the FrameRelay radio button from the agent type selection bar (on the
left side of the window).
A list of configured frame relay agents appear in the list box below the
Name and IP Address headings. If this is a new NetScout Manager Plus
installation, the list box below the selection bar is blank since no agents are
configured yet.
3. Select the Admin radio button from the application selection bar (to the far
right of the screen). Applicable configuration and administration icons appear
in the box below the application bar.
4. Click on the Config Manager icon to open the Configuration Manager main
window.
5. Select the Add... button (down the center of the screen).
6. Minimally, enter the following:
— Agent name
— IP address
— Properties File: Select paradyne.
7. Select the OK button at the bottom of the screen to add the agent, discover
its DLCIs, and return to the Configuration Manager main window.
The frame relay agent just entered appears in the agent list box, with its
DLCIs in the DLCI list box at the bottom of the screen.
8. Select the Test button (fourth button down, center of the screen) to make sure
you can communicate with the agent.
Refer to Adding Frame Relay Agents in Chapter 5 of the NetScout Manager/Plus
& NetScout Server Administrator Guide for additional information.
6-6
DRAFT — June 1999
9191-A2-GH30-00
Verifying Domains and Groups
" Procedure
1. From the NetScout Manager Plus main window, with the FrameRelay and
Admin radio buttons still selected, click on the Config Manager icon to open
the Configuration Manager main window.
2. Verify that only FrameSaver SLV-supported domains appear listed in the
Domain column. FrameSaver SLV-supported domains include:
— ATALK
— IPX
— RMON
— DECNET
— NETB
— SNA
— IP
— NET~
— VINES
— IPV6
— OSI
3. Verify that:
— S (statistics collection) appears for each domain listed in the Group
column.
— H (hosts) appears for the IP domain only.
— Dashes occupy all other positions under the Group column.
— Zeros appear under the Samples and Interval SH and LH columns.
— Dashes appear under all Logging columns: Stat, Host, Conv.
4. If all these requirements are met, no further action is required. Close the
Configuration Manager window.
If all these requirements are not met, a FrameSaver SLV-supported domain
needs to be added, or if an unsupported domain needs to be deleted, the
Properties File must be edited.
9191-A2-GH30-00
DRAFT — June 1999
6-7
Correcting Domains and Groups
Properties need to be edited when not using the Paradyne-provided file and
when:
H
An unsupported domain needs to be deleted.
H
A missing domain needs to be added.
H
Groups, Samples, Interval, and Logging are not configured as specified in
Step 3 of Verifying Domains and Groups on page 6-7.
" Procedure
1. Select the the Property... button (down the center of the Configuration
Manager main window). The Property Editor window opens.
2. To delete an unsupported domain, click on the domain from the Domains list,
then select the Delete button.
The Are you sure? prompt appears. Select Yes. The unsupported domain
disappears from the list.
3. To add a FrameSaver SLV-supported domain or correct property settings,
select the Edit... button (to the right of the Domain section of the Property
Editor window). The Edit Domain window opens.
6-8
DRAFT — June 1999
9191-A2-GH30-00
4. Click on the domain from the Domains list and configure the following:
Property
Description
Setting
Groups Stats (S)
Statistics collection
Enabled for all domains.
Hosts (H)
Level 3 information
(network)
Enabled for IP domain only.
Disabled for all other
domains.
Conversations (C)
Protocols being used
Disabled for all domains.
Event logging
Disabled for all domains and
groups.
Logging
5. Select the OK (button at the bottom of the screen) to apply the changes.
Refer to Configuring Domains in Properties Files in Chapter 5 of the NetScout
Manager/Plus & NetScout Server Administrator Guide for additional information.
9191-A2-GH30-00
DRAFT — June 1999
6-9
Adding SLV Alarms Using a Template
Once DLCIs have been discovered, SLV alarms should be configured and
assigned to each DLCI. Paradyne provides a template for configuring alarms.
DLCI alarms can be configured manually, but using the Paradyne alarm defaults
template greatly reduces configuration time.
The following alarms are configured for each DLCI included in the Paradyne MIB:
— Frames Sent (SLVFramesSnt)
— Rx DLCI Utilization (SLVrxDLCIUtil)
— Tx CIR Utilization (SLVTxCIRUtil)
— Frames Sent Above CIR
(SLVFramesTxAbvCIR)
— Tx DLCI Utilization (SLVTxDLCIUtil)
— Average Latency (AverageLatency)
— Frames Received (SLVFramesRec)
— Current Latency (CurrentLatency)
These alarms and current values can be found in $NSHOME/usr/slvtemplate.fct,
which is used as a starting point for loading new alarms. This file can be copied
and edited so the alarm threshold values match service level agreement values.
The copied .fct file can then be used to replicate alarm threshold values for all
DLCIs on the unit using the eztrap utility. All .fct files must be in $NSHOME/usr.
To configure alarms manually, see Adding SLV Alarms Manually on page 6-14.
NOTE:
Perl must be installed in your system to use the eztrap utility in the procedure
below. If you have an NT system, please install Perl before proceeding.
" Procedure
1. Open a terminal window and go to $NSHOME/usr.
2. Type eztrap -i filename.fct -o agentname.fct agentname and press Return
to run the eztrap utility to create alarm threshold values across all DLCIs for
the copied .fct file.
The message eztrap done appears when the .fct file is transferred.
the Configuration Manager main window (see the window on page 6-7).
4. Edit any alarm values that need to be changed.
5. Select the Install button (down the center of the Configuration Manager
main window) to load alarms for the unit. This may take some time, so
please be patient.
See Editing Alarms on page 6-11 if any default settings need to be changed.
6-10
DRAFT — June 1999
9191-A2-GH30-00
Editing Alarms
" Procedure
2. Select the Custom radio button from the Properties File area (in the upper
right of the window), then Property... (down the center of the screen).
The Custom Property Editor window opens.
3. Select a frame relay device, then select the DLCI to have its alarms edited.
9191-A2-GH30-00
DRAFT — June 1999
6-11
The Custom Property Editor window opens.
5. Select a DLCI from the Trap list, and select the Edit... button (to the right of
the list).
The Edit Trap window opens.
6-12
DRAFT — June 1999
9191-A2-GH30-00
6. Edit any trap defaults that may be required. See Step 4 on page 6-15 for field
settings you may want to change.
7. Select the OK (button at the bottom of the screen) to apply your changes.
The window closes and the Configuration Manager main window reappears.
8. Select the Install button (down the center of the Configuration Manager main
window) to apply your changes.
Refer to Editing Alarms in Chapter 8 of the NetScout Manager/Plus & NetScout
Server Administrator Guide to change alarm thresholds.
9191-A2-GH30-00
DRAFT — June 1999
6-13
Adding SLV Alarms Manually
Once DLCIs have been discovered, SLV alarms should be defined and assigned
to each DLCI.
When configuring alarms manually, every alarm must be configured for each
DLCI; that is, if there are eight alarms and 20 DLCIs, 160 trap configurations
must be created (8 x 20). For this reason, it is recommended that the Paradyne
defaults be used. Follow the procedure below to configure alarms manually.
To load Paradyne default settings for alarms, follow the procedure on page 6-10.
" Procedure
The Custom Property Editor window opens (see the window on page 6-11).
3. Select a DLCI from the Trap list, and select the Add... button (to the right of
the list). The Add Trap window opens.
6-14
DRAFT — June 1999
9191-A2-GH30-00
4. Click on the ... button to the right of indicated fields for a drop-down list from
which selections can be made. Minimally, configure the following fields:
Field
Select or Enter . . .
Domain
User Defined
DLCI
DLCI number for trap being assigned
Stats Type
PARADYNE
Trap Variable
Trap variable to be configured.
Key1
Key2
DLCI number (same as DLCI above)
Type
Absolute or Delta radio button 1
Rising, Falling, or Both radio button 2
Threshold
Value that will trigger a trap.
1
2
Latency MIB variables should be Absolute; all others should be Delta.
Generally, Rising is selected.
5. Select the OK (button at the bottom of the screen) to add this alarm.
6. Repeat Steps 3 through 5 until all traps are configured for all DLCIs.
Refer to Chapter 8, Configuring Alarms, of the NetScout Manager/Plus &
NetScout Server Administrator Guide for additional information.
9191-A2-GH30-00
DRAFT — June 1999
6-15
Creating History Files
Up to 14 additional user history tables can be created in the FrameSaver unit for
each interface. An interface is a specific DLCI or the entire frame relay interface.
A table must be created for each DLCI or frame relay link to be monitored.
Additional user history tables are created using the command-line prompt in
NetScout Manager Plus to load a file that contains the OIDs (Object IDs) to be
monitored into the unit.
Paradyne provides several useful examples, including three files containing a
complete set of OIDs appropriate to the interface to be monitored: one for a
DLCI, one for a frame relay link, and one containing system type OIDs. Any of
these files can be used as a template when creating customized history files
specific to the FrameSaver unit.
These files have a pdn*.udh (user-defined history) format and are found in the
PerfWiz/netscout/userHistory directory. The userHistory files should be moved to
$NSHOME/usr so they can be used.
A separate *.udh file must be created and loaded for each DLCI or link that will be
monitored before a customized user history table can be loaded. Use a text editor
to create these *.udh files by:
H
Copying one of the interface-specific files (DLCI or link) and editing it using
one of the examples provided as a guide.
H
Copying one of the examples provided and editing the extensions to fit the
FrameSaver unit.
! WARNING:
Two user history table files are already configured and installed in the
unit, UserHistory1 and UserHistory2. These files must not be modified.
Paradyne uses these two tables to keep SLV data for reports.
It is always a good idea to rediscover agents and their DLCIs before starting to be
sure your agent and DLCI lists are current. To rediscover agents and their DLCIs,
select the Learn button on the NetScout Manager Plus main window (the
FrameRelay and Admin radio buttons still selected).
6-16
DRAFT — June 1999
9191-A2-GH30-00
" Procedure
1. Open a terminal window and go to $NSHOME/usr.
2. Copy an example or interface-specific file to a new file that contains the user
history table number.
3. Open the new file using a text editor.
4. Edit the new file, as needed.
Refer to Creating .UDH Files in Chapter 28, Using Custom History, of the
NetScout Manager Plus User Guide for additional information.
Installing the User-Defined History Files
Once the user-defined history files have been created, the files need to be
installed. History files are installed from the command-line prompt in NetScout
Manager Plus. Should the FrameSaver unit be reset, these files will need to be
reinstalled. The command used to install a new user history table is located in
$NSHOME/bin.
! WARNING:
Do not use user_history_table_1 or 2. UserHistory1 and UserHistory2
are the default user history files used to keep SLV data for reports.
Editing either of these files will destroy SLV reporting capability.
9191-A2-GH30-00
DRAFT — June 1999
6-17
" Procedure
1. Type dvuhist -f agentname user_history_ table_ number config
number_of_buckets interval download_ file.udh to load user-defined
history files for the frame relay link.
Example:
dvuhist -f Dallas51 3 config 30 60 Dallas51k.udh
The interval must be entered in seconds.
2. Type dvuhist -f “agentname DLCI_ number”
user_history_ table_ number config number_of_buckets interval
download_ file.udh to load user-defined history files for a specific DLCI.
Example:
dvuhist -f “Dallas51 301” 3 config 30 60 Dallas301.udh
The same user history table number can be used for both the link and DLCI.
For these examples, user history table number 3 will appear as UserHistory3
on the History List.
See Step 5 in Monitoring a DLCI’s User History Data on page 6-19 to verify that
the user-defined history files have been loaded.
Refer to installing .UDH Files in Chapter 28, Using Custom History, of the
NetScout Manager Plus User Guide for additional information.
6-18
DRAFT — June 1999
9191-A2-GH30-00
Monitoring a DLCI’s History Data
Once the monitoring variables have been defined, a problem DLCI can
monitored.
" Procedure
To monitor user history data:
1. From the NetScout Manager Plus main window, with the FrameRelay radio
button still selected, select the Traffic radio button.
The appropriate icons appear.
2. Highlight an agent in the agent list box so that its DLCIs appear in the DLCI
list box (under the agent list box).
3. Highlight the DLCI to be monitored.
4. Click on the Custom History icon. The NetScout Custom History window
opens.
Adjust the size of the window so the entire report is shown.
5. Select History List from the View menu. The History List window opens.
The newly defined user history variables should appear on this list.
9191-A2-GH30-00
DRAFT — June 1999
6-19
6. Highlight the desired set of user history variables, and select the OK button.
Data is gathered based upon the configured user history variables. This may
take some time, so please be patient.
7. Select 2D or 3D Bar from the Format menu, if desired (3D Bar is shown).
6-20
DRAFT — June 1999
9191-A2-GH30-00
Using the 2D or 3D Bar to view the user history data collected, you can click
on a particular bar and get an expanded view of the data.
8. Click anywhere on this window to return to the previous window view (see
Step 7 on page 6-20).
Refer to Launching User History and Understanding Custom History Display in
Chapter 28, Using Custom History, of the NetScout Manager Plus User Guide for
additional information.
9191-A2-GH30-00
DRAFT — June 1999
6-21
Monitoring the Agent Using NetScout Manager Plus
Once the FrameSaver SLV agent has been added to NetScout Manager Plus,
select either the Traffic or Protocol radio button to monitor the newly added agent,
or one of its DLCIs.
NOTE:
Only the Traffic and Protocol radio buttons on the application selection bar
are supported for FrameSaver SLV agents.
The procedure below describes how to monitor an agent’s traffic. The procedure
is the same for protocol monitoring, but you may be prompted to select a Domain
Group as well as an agent or DLCI.
" Procedure
1. Select the Traffic radio button to monitor the newly added agent, or one of its
DLCIs.
2. Highlight an agent in the agent list box so that its DLCIs appear in the DLCI
list box (under the agent list box).
3. If you want to monitor one of the agent’s DLCIs, highlight the DLCI to be
monitored.
4. Click on an applicable icon. The selected graphical report should open.
Traffic icons that would be of particular interest are Traffic Monitor and
Domain History. In the example below, the Domain History icon was selected,
which is actually a real-time report.
6-22
DRAFT — June 1999
9191-A2-GH30-00
NOTE:
If Size Distribution is the selected View and distribution size has been
changed via OpenLane Performance Wizard, the values shown for the
distribution will not be accurate. Only default size distributions are tracked.
Statistical Windows Supported
Not all icons that appear on the NetScout Manager Plus main window are
supported for FrameSaver units. For example, All Convs (conversations) and
TopNConv icons appear when the Protocol radio button is selected, but
conversations are not supported.
Of the icons that appear on the NetScout Manager Plus main window, the
following are supported:
Traffic Statistics
Protocol Statistics
Traffic Monitor
Protocol Monitor
Segment Zoom
Protocol Zoom
Segment Details 1
TopNTalkers
Domain History 1
All Talkers
1
Size distribution statistics are provided for a DLCI only, not a link. If a link is selected,
all size distribution statistics on the table or graph will be zero.
When a DLCI is selected, the first and last size distribution statistics are ignored for
FrameSaver units and the statistics for those buckets appear in the next valid bucket
(i.e., bucket size <64 and 64 statistics appear in the 65..127 bucket, and >1518
statistics appear in the 1024..1518 bucket).
Conversations and Long-Term and Short-Term Histories are not supported in this
release. As a result, no data will appear on windows that include these panes.
9191-A2-GH30-00
DRAFT — June 1999
6-23
6-24
DRAFT — June 1999
9191-A2-GH30-00
7
NextEDGE and FrameSaver devices are compatible with Concord
Communication’s Network Health software. In addition, Network Health has
released the first in a series of software modules that integrates
NextEDGE/FrameSaver SLV enhanced performance statistics into its reporting
package (see the At-a-Glance report on page 7-19). To get this report, you need
Network Health R4.01 or higher.
This chapter includes Network Health information as it relates to NextEDGE and
FrameSaver SLV products.
H
Installation and Setup of Network Health and reports on page 7-2.
H
Viewing Network Health Charts and Tables on page 7-7.
H
Reports Applicable to Frame Relay Products on page 7-9.
For additional information about installing, accessing, and managing the
NextEDGE or FrameSaver SLV device through Concord’s Network Health, and
for information about applicable reports, refer to:
9191-A2-GH30-00
H
Network Health Installation Guide to help you install the application.
H
Network Health User Guide to help you get started using the application.
H
Network Health Reports Guide to help you understand and use Frame Relay
reports.
H
Network Health – Traffic Accountant Reports Guide to help you understand
and use Traffic Accountant reports.
DRAFT — June 1999
7-1
Installation and Setup of Network Health
Refer to the Network Health Installation Guide for installation instructions, and
follow the instructions applicable to your network platform.
Each Network Health application provides a different set of functions, called a
module. Each module used requires a separate license to gain access to those
features and functions. Make sure that you license the Poller application so you
can poll SLV devices and collect data.
Before starting the installation:
H
Verify the amount of disk and swap space required for your network.
H
Make sure that your operating system is appropriately configured.
H
Have user account information ready so you can access licensed
applications.
To use this application:
1. Install the Concord Network Health software and open the application.
2. Enter license information from the Network Health License Information form
so specific Network Health applications can be used.
3. Discover network elements, devices, and interfaces in the network (see
page 7-3).
4. Configure the Network Health applications, then save them (see page 7-4).
5. Organize elements into groups for reporting purposes (see page) 7-5).
6. Set up and run reports (see page 7-6).
Setup and operation information is contained in the Network Health User Guide.
The sections that follow address only the minimal procedural steps needed once
you have access to the applications.
See the Network Health User and Reports Guides for additional startup
information and a full discussion of the application’s features and how to use
them.
7-2
DRAFT — June 1999
9191-A2-GH30-00
Discovering NextEDGE and FrameSaver Elements
Once licenses are entered to provide access to the applications, the Discover
dialog box opens. Use this dialog box to search for SLV devices in your network
and discover their DLCIs. Saving the results creates definitions in the Poller
Configuration, which are used to poll the devices.
IP addresses and the Community String (Community Names in the NextEDGE or
FrameSaver device) must be entered for Network Health to find the SLV devices
on the network and discover their elements. Elements are resources that can be
polled (e.g., LAN/WAN interfaces, frame relay circuits, routers, and servers).
The two types of elements that can be polled are:
H
Statistics elements – Provide counters and other gauges for information
gathered about your network for statistical and trend analysis.
H
Conversation elements – Provide RMON2 and similar data for information
gathered about network traffic between nodes.
" Procedure
To find SLV device elements in your network:
1. Select the LAN/WAN radio button to specify the element type to be found.
Network Health treats frame relay element discovery as a WAN element type.
2. Enter the IP Addresses of the SLV devices to be located, and the Community
String (Community Name in the NextEDGE or SLV device). The Community
String is case-sensitive.
3. Select the Discover button.
The Discover dialog box closes and the Discovering dialog box opens,
showing the results of the discovery process.
A message indicates the number of elements discovered and the number of
existing elements updated when the discovery process is complete.
Depending upon the number of devices entered, it could take anywhere from
a few minutes to an hour, or longer, depending upon the size of your network,
to discover all elements in the network.
See Discovering Elements in the Network Health User Guide for additional
information and how to schedule automatic element discovery updates to the
database.
9191-A2-GH30-00
DRAFT — June 1999
7-3
Configuring the Discovered Elements
Network Health sets the speed for discovered elements when it polls the device
for the first time. For a NextEDGE or FrameSaver SLV device, the speed set
would be the device’s CIR. No additional configuration should be required.
However, you should verify that all appropriate information has been retrieved.
If an SLV device does not have CIR configured, or it is not configured correctly,
Network Health sets the device’s CIR to 0 kbps. For this reason, you should
reconfigure the device’s CIR before Network Health polls it. If 0 kbps is the speed
setting, you will need to edit the device’s CIR from Network Health.
Additional information that can be edited includes:
H
Element name
H
Community string
H
Polling status and rates
H
SNMP index for the interface
H
Agent type
H
Desciption information
See Discovering Elements in the Network Health User Guide for additional
information.
" Procedure
To change the CIR for NextEDGE or FrameSaver SLV device elements from
Network Health:
1. Select the Edit Before Saving button at the bottom of the Discovering
dialog box once the discovery process is completed.
The Poller Configuration window opens.
2. Double-click on the first element discovered. The Modify Element dialog box
opens.
3. In the Speed box, select the Override radio button and enter the CIR for the
device in the text box.
Letters k and m can be used as shortcuts (e.g., enter 56 k for 56 kilobits
per second, or 16 m for 16 Mbits per second).
7-4
DRAFT — June 1999
9191-A2-GH30-00
4. Apply your changes:
— Select the Apply/Next button to save your change and bring up the next
element to be edited. Continue until all newly discovered frame relay
elements have been modified before selecting the OK button.
— Select the the OK button.
The Modify Element dialog box closes.
5. Select the OK button at the bottom of the Poller Configuration window.
The modified elements are saved to the database, and the devices are
polled. Allow Network Health to continue polling for about a half an hour to
allow time for data to be gathered before running any reports.
Grouping Elements for Reports
Once the discovery process is completed and required changes are made, the
newly discovered elements (DLCIs) should be organized into a group for Health
reporting. Grouping makes for easier monitoring and management of similar node
types (e.g., all SLV elements). Once grouped, you can then run reports on all
DLCIs in the network, as well as reports on individual DLCIs.
" Procedure
To group elements:
1. From the console, select Edit Groups from the Reports menu. The Add
Groups dialog box opens.
2. Enter a name in the Group Name field. Up to 64 characters can be entered.
A through Z, a through z, 0 through 9, dashes (–), periods (.), and underscores
( _ ) can be used. No spaces can be included, and the word All cannot be used.
3. Select the WAN radio button (above the Available Elements list).
4. Highlight all the DLCIs listed on the Available Elements list, or select specific
DLCIs, then select the left arrow button.
The highlighted DLCIs move from the Available Elements list to the
Group Members list.
5. Select the OK button when all appropriate DLCIs have been moved to the
Group Members list.
The Add Groups dialog box closes and the newly created group appears on
the Groups dialog box.
See Managing Groups and Group Lists in the Network Health Reports Guide for
additional information. It also tells you how to customize reports.
9191-A2-GH30-00
DRAFT — June 1999
7-5
Generating Reports for a Group
Once Network Health has had sufficient time to gather data from the polled DLCIs
and the DLCIs have been grouped, you can start generating reports. The
following are defined when specifying a report:
H
Report to be run
H
Group
H
Daily, a specific day(s) of the week, weekly, or monthly report
H
Destination of the report
NOTE:
Not all reports can be ordered or scheduled on a monthly basis. See the
Network Health Reports Guide to determine what reports can be generated
on a monthly basis.
" Procedure
To run a Health report:
1. From the console, select Run from the Reports menu, then Health Reports.
The Run Health Report dialog box opens.
2. In the Report section, select a report from the drop-down list.
3. In the Subject section, select WAN from the drop-down list.
4. From the drop-down list next to Group, select the newly created group.
5. In the Time Range section, specify the day to be included on the report.
6. In the Output section, select either the Screen or Printer radio button. A check
mark will appear in the selected box.
7. Select the OK button to run the selected report.
The Generating Report window opens, showing the report’s progress. The
window closes when the report screen comes up or the report is printed.
See Running Reports from the Console in the Network Health Reports Guide for
additional information. It also tells you how to schedule automatic report
generation.
7-6
DRAFT — June 1999
9191-A2-GH30-00
Viewing Network Health Charts and Tables
Network Health already supports the service level verifier capability provided by
NetScout probes, NextEDGE SLVs, and FrameSaver SLVs.
The following frame relay reports support frame relay and NextEDGE and
FrameSaver SLV products.
Report
Description
Page
Exceptions Reports
Provide summary and detail information that
identifies DLCIs with the highest incidence of
errors, high bandwidth utilization, and trends.
7-9
Summary Reports
Provide summary information for the network,
volume and error leaders, and DLCI traffic.
—
H Network Summary
Provides an overall view of the network.
7-10
Identifies DLCIs having the highest volume and
errors.
7-11
Compares DLCI traffic with volume and the
baseline, bandwidth utilization, and errors.
7-12
Supplemental Report
Shows DLCI availability and latency.
7-13
Service Level Reports
Provide summary information for a group list for a
longer reporting period than other reports.
—
H Executive Service Level
Provides service level information for an
enterprise.
7-14
Provides service level information for various
groups.
7-15
Provides service level information for customers.
7-16
At-a-Glance Reports
Provides consolidated DLCI and network
performance information onto a single page.
—
H At-a-Glance Report
Consolidates bandwidth utilization, network traffic,
events occurring over the reporting period, and
availability and latency levels information.
7-18
Report
H Leaders Summary
Report
H Elements Summary
Report
Report
H IT Manager Service
Level Report
H Customer Service Level
Report
H Paradyne SLV Plus
At-a-Glance Report
Trend Reports
9191-A2-GH30-00
Consolidates transmit burst analysis, network
latency, dropped frames, frame size distribution,
and availability information.
Performs trend analysis on up to ten specified
variables for DLCIs.
DRAFT — June 1999
7-19
7-20
7-7
About Service Level Reports
For long-term analysis and reporting, you will want to license the Service Level
Reports application. This application analyzes data collected over months, or by
quarters, and provides service level information about an enterprise, a region,
department, or business process. Executive, IT Manager, and Customer Service
Level reports are provided.
Using these reports, you can measure service performance against goals and
agreements. Ranges for service level goals can be set for up to five variables:
availability, bandwidth, bytes, health exceptions, and latency. These ranges need
to be set before reports are scheduled.
About the At-a-Glance Reports
At-a-Glance Reports consolidate various important DLCI and network
performance indicators onto a single page. Up to ten DLCIs can be included in an
At-a-Glance Report.
Using the report on page 7-18, you can compare a DLCI’s volume with the
network’s performance over a specified period of time. Ranges for service level
goals can be set for up to five variables: availability, bandwidth, bytes, health
exceptions, and latency. These ranges need to be set before reports are
scheduled.
Using the report on page 7-19, all the enhanced network statistics that only a
NextEDGE or SLV device can accurately collect is provided so you can truly
monitor the health of the frame relay network and see the effects of the
customer’s utilization on network efficiency.
About Trend Reports
By specifying specific variables like bandwidth, trend analysis can be performed
and shown on Trend Reports. Up to ten variables for a DLCI, or ten DLCIs on one
variable can be generated on a single trend report. Information can be presented
in a line graph, pie chart, bar chart, or table format. Any amount of time can be
specified for the reporting period.
These reports can help identify the reasons a DLCI has acquired a poor Health
Index rating. See the Exceptions Report on page 7-9 for information about
Health Index ratings.
Printed Reports
All of the charts and tables seen online can also be provided on printed reports.
The following pages show an example of a printed LAN/WAN Health Report.
7-8
DRAFT — June 1999
9191-A2-GH30-00
Reports Applicable to Frame Relay Products
This section identifies the Network Health reports that apply to NextEDGE and
FrameSaver SLV products, summarizes relevant information, and tells you how to
use the reports.
NOTE:
Network Health provides information with each chart or table, generally
referred to as a report. Click on the hyperlink (Explanation of...) for an
explanation of the report and its features. You can also refer to the Network
Health Reports Guide.
Exceptions Reports
These reports identify those DLCIs that have exceeded a specified number of
accumulated exception points. It is a good idea to run this report daily so that
DLCIs having the most problems can be attended to first. DLCIs contained on this
report need immediate attention.
If a DLCI suddenly shows up on these reports, check whether any new
equipment has been added to the network and whether it is properly
configured. If its configuration is correct, the equipment could be faulty.
9191-A2-GH30-00
DRAFT — June 1999
7-9
Network Summary Report
This set of charts and the table provides a summary of the frame relay network.
Use this report for planning and to predict when a DLCI might run into problems
7-10
DRAFT — June 1999
9191-A2-GH30-00
Leaders Summary Report
The following chart and tables list the ten highest-volume DLCIs. High traffic
volume may be increasing latency, and the high Health Index rating indicates
problems. It is a good idea to run these reports daily so a norm can be
established. The same DLCIs should appear. Use this chart and table to alert you
to possible problems. Problems to look for include:
— A normally high-volume DLCI is dropped from the list.
— A new DLCI appears on the list. Check Element Summaries
— A DLCI has a high Health Index rating, but low volume.
— Significant differences between a DLCI’s average and peak Health Index
rating.
9191-A2-GH30-00
DRAFT — June 1999
7-11
Elements Summary Report
Use this report for DLCI detail information and comparison. Several views of
these charts are available. Use this chart to identify DLCIs with above or below
average volume, and investigate. When there are any significant changes,
investigate the cause.
7-12
DRAFT — June 1999
9191-A2-GH30-00
Supplemental Report
The information shown in this report is also on other Health reports. However,
these charts show more than ten DLCIs at a time so you have a broader view of
the service provided by the network.
9191-A2-GH30-00
DRAFT — June 1999
7-13
Executive Service Level Report
This report summarizes service level performance for an enterprise on a single
page. Use this report to assess whether IT service levels are meeting availability
and service goals.
7-14
DRAFT — June 1999
9191-A2-GH30-00
IT Manager Service Level Report
Using this report, you can compare service level performance of various groups.
The report summarizes service levels for a group of DLCIs, along with details on
individual DLCIs within that group.
9191-A2-GH30-00
DRAFT — June 1999
7-15
Customer Service Level Report
This report is used to provide service level information to service customers to
help them determine optimum service levels needed based upon their own traffic
data, as well as provide documented evidence for increasing CIR. It combines
daily volume, daily Health exceptions, bandwidth distribution, average Health
Index ratings and availability for each DLCI onto a single page.
(The rest of this report is on the next page.)
7-16
DRAFT — June 1999
9191-A2-GH30-00
See LAN/WAN Service Customer Report in the Network Health Reports Guide for
information about this report.
9191-A2-GH30-00
DRAFT — June 1999
7-17
At-a-Glance Reports
These reports consolidate a frame relay circuit’s performance over a specified
period onto single page summaries. Use this report to compare the DLCI’s
volume and utilization to the network performance indicators.
7-18
DRAFT — June 1999
9191-A2-GH30-00
The At-a-Glance report below is the first Network Health report to integrate
the NextEDGE and FrameSaver SLV’s unique monitoring capabilities, using the
device’s SLV-enhanced network statistics.
A FrameSaver SLV Report is shown here.
9191-A2-GH30-00
DRAFT — June 1999
7-19
Trend Reports
Variables other than bandwidth can be selected for a trend report (e.g., burst
octets); however, a bandwidth trend report (shown here) should be generated
when investigating problems that appear on:
H
Exceptions Reports (see page 7-9)
H
Supplemental Report (see page 7-13)
H
Health Reports
You can specify total bandwidth (both incoming and outgoing data), only incoming
data bandwidth, or only outgoing data bandwidth. The trend report calculates the
bandwidth for the data based upon the data rate and the amount of data in bytes.
Use trend reports to view individual variables for DLCIs having a high Health
Index rating to help locate which variable is causing a problem leading to a
DLCI’s poor Health Index rating. For additional information about trend reports,
see LAN/WAN Trend Reports in the Network Health Reports Guide.
7-20
DRAFT — June 1999
9191-A2-GH30-00
Configuration
8
This chapter provides basic setup information and identifies how each set of
configuration options is accessed, describes each option, and each option’s
possible settings.
H
Setting Up the System on page 8-4.
— Considerations When Setting Up on page 8-4.
— Selecting a Management Interface on page 8-4.
— Minimal Configuration Before Deploying Remote Units on page 8-5.
— Entering and Displaying System Information on page 8-5.
— A Word About Hot Swapping Cards on page 8-6.
H
Basic Configuration on page 8-7.
— Configuration Option Areas on page 8-7.
— Accessing and Displaying Configuration Options on page 8-9.
— Changing Configuration Options on page 8-9.
— Saving Configuration Options on page 8-10.
H
Setting Up Auto-Configuration on page 8-11.
H
Setting Up the Modem on page 8-14.
— Entering Modem Directory Phone Numbers on page 8-14.
— Configuring Dial-In Access to the Menu-Driven User Interface on
page 8-15.
— Configuring Automatic Dial-Out to Send SNMP Traps on page 8-16.
9191-A2-GH30-00
H
Setting Up Management on page 8-18.
H
Setting Up So the Router Can Receive RIP on page 8-19.
H
Setting Up Service Provider Connectivity on page 8-20.
H
Setting Up for Back-to-Back Operation on page 8-21.
DRAFT — June 1999
8-1
Configuration
H
Assigning Time Slots/Cross Connections on page 8-38.
— Assigning Frame Relay Time Slots to the Network Interface on
page 8-38.
— Assigning DSX-1 Time Slots to the Network Interface on page 8-39.
— DSX-1 Signaling Assignments and Trunk Conditioning on page 8-41.
H
Configuring the System on page 8-22. The following configuration option
tables are included in this chapter:
— Table 8-1. System Frame Relay and LMI Options on page 8-23.
— Table 8-2. Service Level Verification Options on page 8-25.
— Table 8-3. General System Options on page 8-26.
— Table 8-4. T1 Network Physical Options on page 8-29.
— Table 8-5. DSX-1 Physical Options on page 8-32.
— Table 8-6. Data Ports Physical Options on page 8-34.
— Table 8-8. Frame Relay and LMI Options on page 8-44.
— Table 8-9. DLCI Record Options on page 8-51.
— Table 8-10. PVC Connection Options on page 8-53.
— Table 8-11. Node IP Options on page 8-57.
— Table 8-12. Management PVC Options on page 8-60.
— Table 8-13. General SNMP Management Options on page 8-63.
— Table 8-14. Telnet and FTP Session Options on page 8-65.
— Table 8-15. SNMP NMS Security Options on page 8-67.
— Table 8-16. SNMP Traps and Trap Dial-Out Options on page 8-68.
— Table 8-17. Communication Port Options on page 8-72.
— Table 8-18. Modem Port Options on page 8-77.
8-2
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Setting Up the System
When configuring the system:
You need to . . .
See . . .
1. Configure the overall system
options.
Configuring System Options on page 8-23.
2. Set up node IP information.
Configuring Node IP Information on page 8-57.
3. Configure physical interfaces.
Setting Up Each Physical Interface on page 8-29.
Configuring the Communication Port on page 8-72,
and RIP.
Setting Up the Modem Port on page 8-13 and
Configuring the Modem Port on page 8-77.
4. Change Auto-Configuration, if
necessary.
Setting Up Auto-Configuration on page 8-11.
5. Configure frame relay LMI for
interfaces.
Configuring Frame Relay LMI for Interfaces on
page 8-44.
6. Create DLCI Records for
interfaces.
Configuring DLCI Records for Each Interface on
page 8-51.
7. Configure PVC connections.
Configuring PVC Connections on page 8-53.
8. Create a management PVC.
Configuring Management PVCs on page 8-59.
Setting Up So the Router Can Receive RIP on
page 8-19.
9. Set up access and
management.
Configuring General SNMP Management on
page 8-63.
Configuring Telnet and/or FTP Session Support on
page 8-65.
Configuring SNMP Traps and Trap Dial-Out on
page 8-68.
9191-A2-GH30-00
DRAFT — June 1999
8-3
Configuration
Considerations When Setting Up
We recommend that you decide how to configure the system before actually
configuring it.
When setting up the system, you need to:
H
Arrange for T1 service.
H
Determine where PVCs will be required in your network. Refer to Chapter 3,
Typical Applications, for assistance.
H
Determine whether you will be using the Auto-Configuration feature. If an
ISDN DBM is installed, see About the Automatic Backup Feature in
Chapter 11, Dial Backup Modules,for additional information.
H
Determine whether you want SNMP traps generated, and how you would like
them communicated to the management system.
H
Decide how you want to manage this unit within the context of your network,
and choose a management configuration:
— Locally, via a PVC between the system and a router attached to its DTE
port.
— Locally, through the COM port.
— Remotely, through dedicated or multiplexed PVCs.
— Remotely, from a remote terminal via a modem or Telnet connection.
H
If managing the system through an SNMP NMS or Telnet session, select an
IP addressing scheme. See Chapter 2, Management Control, for different
management alternatives. See Appendix B, IP Addressing, for sample IP
addressing schemes.
H
Plan your T1 time slot assignments.
Selecting a Management Interface
The system can be managed using one of the following management interfaces:
H
Asynchronous terminal access to the menu-driven user interface –
Over the system’s COM port or modem port for configuration and control.
An asynchronous terminal is required for initial setup so external
management can be enabled and the modem can be configured.
8-4
H
Telnet access to the menu-driven user interface – Over the system’s
COM port, modem port, through an in-band management channel (PVC), or
over the COM port using a LAN adapter.
H
SNMP – Over the system’s, modem port, through an in-band management
channel (PVC), or over the COM port using a LAN adapter.
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Minimal Configuration Before Deploying Remote Units
At a minimum, the following configuration options must be set before deploying a
a system to a remote site:
H
Node IP Address
H
Node Subnet Mask
See Configuring Node IP Information on page 8-56 for these options.
Entering and Displaying System Information
Use the Device Name screen to name the system, and to change or display the
general SNMP system name, location, and contact for the unit. Use this screen to
set the date and time for the system, as well.
" Procedure
1. Follow this menu selection sequence:
Main Menu → Control → System Information
2. Move the cursor to the field ( Tab to the field, or press the arrow keys ) where
you want to add or change information.
The following information is available for viewing. Use the right and left arrow
keys to scroll additional text into view.
If the selection is . . .
Enter the . . .
Device Name
Unique name for device identification of up to
20 characters.
System Name
SNMP system name; can be up to 255 characters.
System Location
System’s physical location; can be up to 255 characters.
System Contact
Name and how to contact the system person; can be up to
255 characters.
Date
Current date in the month/day/year format (mm/dd/yyyy).
Time
Current time in the hours:minutes format (hh:mm).
NOTE:
To clear existing information, place the cursor in the Clear field ( Tab to
the Clear field ) and press Enter.
3. Save your entries.
9191-A2-GH30-00
DRAFT — June 1999
8-5
Configuration
A Word About Hot Swapping Cards
NextEDGE system NAMs and APMs can be removed from their housing without
powering off the system, and without having to reconfigure the cards each time
they are moved.
H
NAM Insertion/Removal. The NAM can be removed without powering off
the system; however, all system functionality is lost when it is removed.
When removed and inserted into another housing, the NAM applies its
configuration from the previous housing to its current housing.
— If the NAM is moved from a 2-slot housing to a 5-slot housing, the
operator can use the configuration of the APM in Slot 02 of the previous
housing. APMs in Slots 03 – 05 will be configured with the factory default
settings.
— If the NAM is moved from a 5-slot housing to a 2-slot, or moved to a
14-slot housing (T1 Mux NAM only), the factory default configuration
options are loaded.
H
APM Insertion/Removal. An APM’s configuration travels with the NAM.
The NAM senses when an APM has been inserted or removed and
automatically makes appropriate changes to screens, configuration options,
and MIB objects.
— When an APM is inserted in a previously unassigned slot, the system
configures the APM using the factory default configuration.
— When the same type of APM is inserted into a previously assigned slot,
the system uses the configuration for the APM that previously occupied
the slot so the APM does not have to be reconfigured.
— When another type of APM is inserted into a previously assigned slot, an
alarm and trap are generated for the slot. If accepted, the factory default
configuration is loaded for the new APM type. If rejected, the new APM is
ignored and the previous configuration is retained.
8-6
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Setting Up Logins
Login setup information is in Chapter 9, Security and Logins.
Basic Configuration
Configuration option settings determine how the NextEDGE system operates.
The system can be configured using:
H
Menu-driven user interface via a direct connection or Telnet session.
H
DCE Manager
The following sections tell you about the Configuration features and how to
change configuration options.
Configuration Option Areas
The system arrives with configured factory default settings, which are located in
the Factory Default configuration option area. You can find the default settings for
configuration options in the:
H
Quick Reference
H
Configuration option tables in this chapter.
If the factory default settings do not support your network’s configuration, you can
customize them to better suit your application.
9191-A2-GH30-00
DRAFT — June 1999
8-7
Configuration
" Procedure
To change configuration option settings:
1. Access and display configuration options and their settings.
2. Change the settings, as needed.
3. Save the changes to one of three configuration option areas.
Four configuration option storage areas are available.
Configuration Option Area
Description
Current Configuration
The currently active set of configuration options.
Customer Configuration 1
An alternate set of configuration options that the
customer can set up and store for future use.
Customer Configuration 2
Another alternate set of configuration options that
the customer can set up and store for future use.
Default Factory Configuration
A read-only configuration area containing the
factory default set of configuration options.
You can load and edit default factory configuration
settings, but you can only save those changes to
the Current, Customer 1, or Customer 2
configuration option areas.
The Current, Customer 1, and Customer 2
configuration option areas are identical to the
Default Factory Configuration until modified by the
customer.
NOTE:
— Only Security Access Level 1 users can change configuration options.
— Security Access Level 2 users can only view configuration options and
run tests.
— Security Access Level 3 users can only view configuration options; they
cannot change configuration options or run tests.
8-8
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Accessing and Displaying Configuration Options
To access and display configuration options, load (copy) the applicable
configuration option set into the edit area.
" Procedure
To load a configuration option set into the configuration edit area:
Main Menu → Configuration
The Load Configuration From: menu appears.
2. Select the configuration option area you want to load and press Return
(Current Configuration, Customer Configuration 1, Customer Configuration 2,
or Default Factory Configuration).
The selected configuration option set is loaded into the configuration edit
area and the Configuration Edit/Display screen appears.
NOTE:
Loading a configuration with many DLCIs from a unit’s Customer
Configuration 1 or 2 option area may take time. Allow a minute or more for
the file to be loaded.
Changing Configuration Options
" Procedure
To change configuration option settings:
1. From the Configuration Edit/Display screen, select the configuration option
set you want to view or make changes to and press Enter.
2. Select the configuration options applicable to your network, and make
appropriate changes to the setting(s).
When creating new PVC connections or management PVCs, some
configuration options will be blank. For a valid setting to appear, Tab to the
configuration option and press the spacebar.
3. Repeat Steps 1 and 2 until all changes are complete.
9191-A2-GH30-00
DRAFT — June 1999
8-9
Configuration
Saving Configuration Options
When all changes to the configuration options are complete, use the Save
function key to save configuration option changes to either the Current,
Customer 1, or Customer 2 Configuration areas.
To save the configuration option changes from:
H
DCE Manager for Windows – Click on the Set button at the bottom of the file
folder where the change was made.
H
DCE Manager for Unix – Click on the Apply button at the bottom of the
window where the change was made.
H
Menu-Driven User Interface – Select the Save function key. The procedure is
described below.
" Procedure
To save configuration changes from the menu-driven user interface:
1. Press Ctrl-a to switch to the screen’s function keys area.
2. Type s or S (Save) and press Enter. The Save Configuration To menu
appears.
NOTE:
If you try to exit the Configuration menu without saving changes, a Save
Configuration screen appears requiring a Yes or No response.
— If you select No, the Main Menu screen reappears and the changes
are not saved.
— If you select Yes, the Save Configuration To screen appears.
3. Select the configuration option area where you want to save the changes to
(usually Current Configuration) and press Return.
When the Save is complete, Command Complete appears in the message
area at the bottom of the screen.
NOTE:
There are other methods of changing configurations, like SNMP and
auto-configuration. Since multiple sessions can be active at the same
time, the last change made overwrites any previous or current changes
being made. For instance:
— Saving your configuration changes would cause configuration
changes made via another method to be lost.
— If you are making changes and someone else makes changes and
saves them, your changes would be lost.
8-10
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Setting Up Auto-Configuration
The auto-configuration feature allows you to select a method of automatic
configuration and connection of DLCIs within the system.
When Frame Relay Discovery is selected, the system “discovers” network
DLCIs from the network LMI status response message (see the procedure on
page 8-12). It configures a network data port DLCI, required user data port DLCI,
and automatically connects them to create a PVC.
Automatically configured network DLCIs are multiplexed, and each automatically
configured user data port DLCI carries the same DLCI Number as its
corresponding network DLCI. These are the same DLCI numbers that would
have been available had the unit not been inserted in the link between your
equipment and the network.
Frame Relay Discovery mode defaults to 1MPort (management DLCIs
multiplexed with user data DLCIs on Port-1, which creates two embedded DLCIs
(EDLCIs) – one EDLCI for Port user data, and another EDLCI for management
data. When LMI is active on the network data port and PVC status information
(with provisioned DLCI numbers) is next received from the network, the system
automatically saves the settings listed in the table on pageNO TAG to the Current
Configuration area.
NOTE:
Local Management PVCs (e.g., PVCs between a router and the system’s
user data port) must be configured manually.
Auto-Configuration Screen Example
main/auto-configuration
Device Name: Node A
PARADYNE 9191
1/26/1998 23:32
AUTO-CONFIGURATION
Frame Relay Discovery Mode:
Automatic Backup Configuration:
1MPort
Enable
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Exit
MainMenu
Save
Automatic Backup Configuration only appears when an ISDN DBM is installed.
See About the Automatic Backup Feature in Chapter 11, Dial Backup Modules, to
learn more about this feature.
9191-A2-GH30-00
DRAFT — June 1999
8-11
Configuration
" Procedure
To change a Frame Relay Discovery Mode:
Main Menu → Auto-Configuration → Frame Relay Discovery Mode
2. Select a Frame Relay Discovery mode:
Discovery Mode
Application Description
1MPort
H Auto-configuration is enabled on Port-1.
(default)
H A multiplexed network DLCI containing two EDLCIs is
configured for Port-1user data and for management
data.
H A PVC connection is configured between the network
and port DLCIs.
H A management PVC is configured on the network
interface.
1Port
H Auto-configuration is enabled on Port-1.
H A multiplexed network DLCI is configured for Port-1user
data.
H A PVC connection is configured between the network
and port DLCIs.
H No management PVC is configured.
2MPorts
H Auto-configuration is enabled on both Port-1 and
Port-2.
H A multiplexed network DLCI containing three EDLCIs is
configured for Port-1user data, Port-2user data, and for
management data.
H PVC connections are configured between the network
and port DLCIs.
H A management PVC is configured on the network
interface.
NetOnly
H Auto-configuration of a network DLCI only; no Port-1
DLCI or PVC connections are configured.
Disable
H No frame relay discovery or automatic configuration
takes place.
The unit will be configured manually.
3. Save your selection, and respond Yes to the Saving will cause
Auto-Configuration to Update and Restart. Are you sure?
prompt.
8-12
DRAFT — June 1999
9191-A2-GH30-00
Configuration
4. Respond to the Delete All DLCIs and PVC Connections? prompt.
— If Yes is selected, all discovered and manually configured DLCI records
and PVC connections are cleared, except for the management PVC
between a data port and router. This is so communication with the
system remains.
— If No is selected, no previously discovered or manually configured DLCIs
or PVC connections are removed and newly discovered DLCIs will be
configured according to the new discovery mode.
5. Go to the Configuration menu and change any node-specific configuration
options that may be needed.
Setting Up the Modem
The system has an internal modem for dial in access to the menu-driven user
interface when the system goes down and for dialing out when an SNMP trap is
generated. The modem is already set up for dial-in access.
To set up the modem, you need to:
1. Set up Modem Directory phone numbers.
2. Configure or change dial-in access to the system (see page 8-15).
3. Configure trap dial-out (see page 8-16).
9191-A2-GH30-00
DRAFT — June 1999
8-13
Configuration
Entering Modem Directory Phone Numbers
Phone numbers must be entered into the directories before the modem can
dial out.
" Procedure
Main Menu → Control → Modem Call Directories
2. Press the spacebar until the desired Directory Number appears (A or 1– 5).
Set up the A (Alarm) directory as the primary directory. You can also set up
an alternate directory. Press Return and the cursor is moved to the Directory
Phone Number field.
3. Enter the phone number for the remote unit that this system will dial.
Use valid characters only:
Enter . . .
For . . .
ASCII text
Entering the phone number.
Space,
underscore ( _ ), and
dash (–)
Readability characters.
Comma ( , )
Readability character for a 2-second pause.
B
Blind dialing.
P
Pulse dialing.
T
one dialing.
W
Wait for dial tone.
See Configuring SNMP Traps and Trap Dial-Out on page 8-68 for trap and alarm
information.
8-14
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Configuring Dial-In Access to the Menu-Driven User Interface
The modem port is already configured for asynchronous terminal access and
dial-in access; these are the default settings.
" Procedure
To configure dial-in access via the modem port:
1. Select Modem Port.
Modem Port
2. Minimally, change:
— Port Use to Net Link for IP network connectivity (SNMP, Telnet, FTP, or
trap dial-out).
— Assign an IP Address and Subnet Mask to the port if it is different from
the node’s.
— Change Link Protocol to SLIP, if necessary. PPP is the default setting.
3. Save your change(s).
For additional information about controlling dial-in access, see Controlling Dial-In
Access in Chapter 9, Security and Logins.
9191-A2-GH30-00
DRAFT — June 1999
8-15
Configuration
Configuring Automatic Dial-Out to Send SNMP Traps
For generated SNMP traps to initiate a call, a modem port connection must be
established.
" Procedure
To configure dial-out of SNMP traps:
1. Select Modem Port.
Modem Port
2. Configure the following:
— Disable Dial-In Access if only trap dial-out is wanted.
— Set Port Use to Net Link. See Table 8-18, Modem Port Options, on
page 8-77 when configuring the modem port. Save any change(s).
3. Select SNMP Traps.
Management and Communication → SNMP Traps
4. Configure the following:
— Enable SNMP Traps, Trap Dial-Out to enable automatic call initiation (dial
out) to send an SNMP trap message, and Call Retry to hold the trap if the
call cannot be completed.
— Assign SNMP Trap Managers, and specify the IP address of the NMS
that traps will be sent to when dialing out.
— Select Modem as the Destination and select the desired SNMP trap
categories.
— Specify whether to disconnect immediately after dialing out traps, or
to allow a manual disconnect to occur (a connection remains until
manually disconnected).
You can also set the delay time and specify an alternate dial-out
directory, if desired.
5. Save your changes.
See Configuring SNMP Traps and Trap Dial-Out on page 8-68 when configuring
SNMP traps.
8-16
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Setting Up an ISDN DBM
See Chapter 11, Dial Backup Modules, for this information.
9191-A2-GH30-00
DRAFT — June 1999
8-17
Configuration
Setting Up Management
For remote sites, only SNMP management needs to be set up. For the central
site, local management between the unit and the router must be set up along with
SNMP management.
" Procedure
To set up SNMP management:
1. Select General SNMP Management.
Configuration → Management and Communication →
General SNMP Management
2. Minimally, set Name 1 Access to Read/Write.
" Procedure
To set up local management at the central site unit:
1. Create a DLCI for the data port.
Main Menu → Configuration → Data Ports → DLCI Records
2. Select Management PVC.
Configuration → Management and Communication → Management PVC
3. Make the DLCI Record a management DLCI to create a Management PVC.
Minimally, enter the following options for each of the DLCI Records created:
— Name for the management DLCI
— Special and the IP Address for the interface if it is different from the Node
IP Address
— Primary Link for this DLCI (i.e., the DLCI’s primary destination interface)
— Primary DLCI (i.e., the DLCI number at the other end of the PVC)
8-18
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Setting Up So the Router Can Receive RIP
Using the system’s standard routing Information protocol (RIP) feature, routing
information is passed to the router over the management PVC, so the router can
learn routes to NextEDGE frame systems or FrameSaver SLV units and their
routers.
" Procedure
1. Configure the port’s router to receive RIP.
For example, if using a Cisco router, configure config-t, router RIP,
int serialx, IP RIP Receive version 1, then ctl-z WR.
2. Create a Standard DLCI for the data port (see Configuring DLCI Records for
Each Interface on page 8-48).
Main Menu → Configuration → Data Ports → DLCI Records
3. Change it to a Management PVC (see Configuring Management PVCs
on page 8-59).
4. Make sure that Node IP Information has been set up (see Configuring Node
IP Information on page 8-11).
5. Set Primary Link RIP to Standard_Out.
6. Save your configuration.
9191-A2-GH30-00
DRAFT — June 1999
8-19
Configuration
Setting Up Service Provider Connectivity
If management needs to be set up between a service provider’s customer and its
network operations center (NOC), a non-multiplexed DLCI must be configured to
carry management data between the customer’s central site and the NOC
console. This requires that a frame relay discovered DLCI needs to be modified.
This is because all auto-configured network DLCIs are configured as multiplexed
DLCIs.
" Procedure
To set up NOC management:
1. Select DLCI Records on the network interface:
Configuration → Network → DLCI Records
2. Select Modify. The Modify DLCI Record for DLCI Number? prompt
appears.
3. Select the DLCI that will be used by pressing the spacebar until the correct
DLCI number appears, then select it.
4. Change the DLCI Type from Multiplexed to Standard.
The DLCI in connections. Update DLCI usage as follows:
prompt appears.
5. Select the Delete EDLCI Connections and Make a Mgmt Only
PVC option.
6. Select Yes at the prompt.
PVC connections for the selected DLCI are broken, the Port-1 DLCI mapped
to this network DLCI and the embedded management DLCI (EDLCI) are
deleted, and the selected DLCI will be reconfigured as a management PVC
using the Node IP Address.
8-20
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Setting Up for Back-to-Back Operation
Using this special feature, you can set up two NextEDGE systems that are
connected back-to-back without frame relay switches between them, as in a test
bench setup.
This configuration is shown in the illustration below.
T1 Crossover
Cable
Frame
Relay
Router
NextEDGE
System
NextEDGE
System
Frame
Relay
Router
99-16395
Changing Operating Mode
When setting up back-to-back operation:
H
One unit must be configured for Standard operation, which is the setting for
normal operation.
H
The other unit must be configured for Back-to-Back operation so it presents
the network side of the UNI.
Only one of the units will have its operating mode changed.
" Procedure
To set up back-to-back operation:
1. On the unit to be configured for Back-to-Back operation, manually configure
DLCIs; DLCIs should be configured before connecting the two units.
2. Access the Change Operating Mode screen.
Main Menu → Control → Change Operating Mode
The Change Operating Mode screen appears, with two modes:
3. Select Back-to-Back Operation, and type y ( Yes) at the Are you sure?
prompt.
4. Press Ctrl-a and Save the change.
" Procedure
To return the unit to normal operation:
1. Return to the Change Operating Mode screen and switch the Operating
Mode back to Standard.
2. Respond Yes to the prompt and save the change. The units can be
reconnected to a standard frame relay network.
9191-A2-GH30-00
DRAFT — June 1999
8-21
Configuration
Configuring the System
Configuration option settings determine how the NextEDGE system operates.
The system can be configured using:
H
Menu-driven user interface via a direct connection or Telnet session.
H
DCE Manager for partial configuration, based upon the following platforms:
— HP OpenView Network Node Manager (Unix)
— HP OpenView for WorkGroup Node Manager for Windows
— IBM NetView/AIX
Changing the Auto-Configuration setting can also change the unit’s configuration.
See Setting Up Auto-Configuration on page 8-11, and Setting Up Automatic
Backup Configuration in Chapter 11, Dial Backup Modules, for additional
information.
Configuring System Options
Select System to set the following options:
8-22
H
System Frame Relay and LMI Options (see below)
H
Service Level Verification Options on page 8-25.
H
General System Options on page 8-26.
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Configuring System Frame Relay and LMI Options
Select Frame Relay and LMI to display or change the Frame Relay and LMI
options for the system (see Table 8-1). Follow this menu selection sequence:
Main Menu → Configuration → System→ Frame Relay and LMI
Table 8-1. System Frame Relay and LMI Options (1 of 3)
LMI Behavior
Possible Settings: Independent,
Net1-FR1_Follows_Port-1,
Net1-FR1_Follows_Port-2,
Port-1_Follows_Net1-FR1,
Port-2_Follows_Net1-FR1,
All_Ports_Follow_Net1-FR1,
Port-1_Codependent_with_Net1-FR1,
Port-2_Codependent_with_Net1-FR1
Default Setting: Independent
Configures the device to allow the state of the LMI to be passed from one interface to
another, determining how the unit will handle a change in the LMI state. Sometimes
referred to as LMI pass-through.
NOTE:
LMI Behavior cannot be changed while Auto Backup is enabled (see Auto
Backup Criteria Options in Chapter 11, Dial Backup Modules). A warning
message appears at the bottom of the screen if auto backup is enabled.
First, disable Auto Backup, and then change LMI Behavior.
Independent – Handles the LMI state of each interface separately so that the LMI state
of one interface has no effect on the LMI state of another interface. Provides LMI
Spoofing. This is the recommended setting when backup is configured, and for Network
Service Providers (NSPs).
Net1-FR1_Follows_Port-1 – Brings LMI down on the network interface when LMI on
Port-1 goes down, disabling the network interface and deasserting its control leads.
When LMI on Port-1 comes back up, the network interface is reenabled. The LMI state
on the network interface has no effect on the LMI state on Port-1. That is, the network
interface’s LMI follows Port-1’s LMI. Used at central sites, this setting is useful when the
remote site router on the other end of the PVC connection can initiate recovery via a
redundant central site when there is a catastrophic central-site LAN or router failure. Not
recommended for NSPs.
Net1-FR1_Follows_Port-2 – Reacts like the Net1-FR1_Follows_Port-1 selection, but
for Port-2 instead.
Port-1_Follows_Net1-FR1 – Brings LMI down on Port-1 when LMI on the network
interface goes down, disabling Port 1 and deasserting its control leads. When LMI on the
network interface comes back up, Port-1 is reenabled and its control leads are
reasserted. The LMI state on Port-1 has no effect on the LMI state on the network
interface. That is, Port-1’s LMI follows the network interface’s LMI. This setting is useful
if the router connected to Port-1 is used to initiate recovery when network failures are
detected.
Port-2_Follows_Net1-FR1 – Reacts like the Port-1_Follows_Net1-FR1 selection, but
for Port-2 instead.
9191-A2-GH30-00
DRAFT — June 1999
8-23
Configuration
LMI Behavior
(Cont’d)
All_Ports_Follow_Net1-FR1 – Brings LMI down on all user data ports when LMI on the
network interface goes down, disabling all ports and deasserting their control leads.
Allows LMI to come back up and reenables the ports when LMI comes up on the
network. That is, LMI on each port follows the network interface’s LMI. The state of LMI
on the port will not affect the state of LMI on the network interface.
Port-1_Codependent_with_Net1-FR1 – Brings LMI down on the network interface
when LMI on Port-1 goes down (or LMI down on Port-1 when LMI on the network
interface goes down), and allows LMI to come back up when LMI comes back on both
interfaces. That is, the LMI state for one interface is dependent on the other. Use this
setting when backup is through the router instead of the unit. It is not recommended
since it makes fault isolation more difficult.
Port-2_Codependent_with_Net1-FR1 – Reacts like the
Port-1_Codependent_with_Net1-FR1 selection, but for Port-2 instead. The state of LMI
on the network interface will not affect the state of LMI on Port-1.
LMI Error Event (N2)
Possible Settings: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Default Setting: 3
Configures the LMI-defined N2 parameter, which sets the number of errors that can
occur on the LMI link before an error is reported. Applies to both the user and network
sides of the UNI.
1 – 10 – Specifies the maximum number of errors.
LMI Clearing Event (N3)
Default Setting: 1
Configures the LMI-defined N3 parameter, which sets the number of error-free
messages that must be received before clearing an error event. Applies to both the user
and network sides of the UNI.
1 – 10 – Specifies how many error-free messages it will take to clear the error event.
LMI Status Enquiry (N1)
Possible Settings: 1, 2, 3, 4, . . . 255
Default Setting: 6
Configures the LMI-defined N1 parameter, which sets the number of status enquiry
polling cycles that the user side of the LMI initiates before a full status enquiry is
initiated. Applies to only the user side of the UNI.
1 – 255 – Specifies the number of status enquiry polling cycles that can be initiated.
LMI Heartbeat (T1)
Possible Settings: 5, 10, 15, 20, 25, 30
Default Setting: 10
Configures the LMI-defined T1 parameter, which sets the number of seconds between
the initiation of status enquiry messages on the user side of the LMI. Applies to only the
user side of the UNI.
5 – 30 – Specifies the number of seconds between the initiation of status enquiry
messages in increments of 5.
8-24
DRAFT — June 1999
9191-A2-GH30-00
Configuration
LMI Inbound Heartbeat (T2)
Default Setting: 15
Configures the LMI-defined T2 parameter, which sets the number of seconds between
the receipt of status enquiry messages on the network side of the LMI. Applies to only
the network side of the UNI.
5 – 30 – Specifies the number of seconds between the receipt of status enquiry
LMI N4 Measurement Period (T3)
Default Setting: 20
Configures the LMI-defined T3 parameter, which is the time interval (in seconds) that the
Network side of the LMI uses to measure the maximum status enquiry messages
received (N4) from the User side.
5 – 30 – Specifies the interval of time in increments of 5.
Configuring Service Level Verification Options
Select Service Level Verification to display or change the Service Level
Verification (SLV) System configuration options (see Table 8-2). Follow this menu
selection sequence:
Main Menu → Configuration → System → Service Level Verification
Table 8-2. Service Level Verification Options
SLV Sample Interval (secs)
Possible Settings: 15 – 3600
Default Setting: 60
Sets the inband communications interval between NextEDGE and FrameSaver SLV
units. Inband communications are used to pass frames that calculate latency, as well as
transmission success and other SLV information.
15 – 3600 – Sets the SLV Sample Interval (secs) period in seconds.
SLV Delivery Ratio
Possible Settings: Enable, Disable
Default Setting: Disable
Determines whether communication of Frame and Data Delivery Ratios (FDR/DDR)
between NextEDGE and FrameSaver units is enabled. To use this capability, both ends
of all PVCs must be NextEDGE or FrameSaver SLV units. If some of the units are
FrameSaver 9124s or 9624s, they must be running software version 1.2 or higher.
Enable – An extra byte for FDR/DDR statistics collection is included with each frame.
These statistics are used to determine the amount of data dropped by the network. (Be
aware that increasing bandwidth used for SLV communications reduces bandwidth
available for user data).
Disable – Extra byte is not included.
9191-A2-GH30-00
DRAFT — June 1999
8-25
Configuration
Table 8-2. Service Level Verification Options
DLCI Down on SLV Timeout
Available Settings: Enable, Disable
Determines whether missed SLV packets will be monitored along with the LMI status to
determine the status of PVC connections to remote NextEDGE or FrameSaver devices.
NOTE:
This option only applies to multiplexed DLCIs.
Enable – After the configured threshold for missed SLV packets has been exceeded, an
alarm and SNMP trap are generated, a Health and Status message created, and the
DLCI’s status turns Inactive. If an ISDN DBM is installed and an alternate destination is
configured for this DLCI, backup is initiated.
Disable – Missed SLV communications will not be monitored.
SLV Timeout Error Event Threshold
Available Settings: 1, 2, 3, 4 . . . 20
Default Setting: 3
Specifies the number of consecutively missed SLV commnications that willl be received
before an SLV Timeout Error Event is declared.
1– 20 – Sets the limit for these error events.
SLV Timeout Clearing Event Threshold
Available Settings: 1, 2, 3, 4 . . . 20
Default Setting: 1
Specifies the number of consecutive SLV communications that must be received before
the SLV Timeout Error Event is cleared.
1– 20 – Sets the limit for the clearing event.
Configuring General System Options
Select General to display or change the general system configuration options
(see Table 8-3). Follow this menu selection sequence:
Main Menu → Configuration → System → General
Table 8-3. General System Options
Test Timeout
Default Setting: Enable
Determines whether or not loopback and pattern tests have a duration after which they
are terminated automatically.
Enable – All Loopback and Pattern tests have a timeout. This setting is recommended
when the unit is managed remotely through an in-band data stream. If the system is
accidently commanded to execute a disruptive test on the interface providing the
management access, control can be regained after the timeout expires, terminating the
test.
Disable – Loopback and pattern tests must be manually terminated.
8-26
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Test Duration (min)
Default Setting: 10
Specifies the maximum duration of the tests.
Display Conditions – This option only appears when Test Timeout is set to Enable.
1 – 120 – Sets the Test Timeout period for up to two hours.
Primary Clock Source
Possible Settings: Net1, DSXs-p, Internal, DBM
Default Setting: Net1
Allows you to select the primary clock source for the system. The source selected
provides all of the timing within the system and the clocks for all of the external
interfaces. Failure of the clock specified by this configuration option results in automatic
fallback to the Secondary Clock Source configuration option setting.
NOTE:
For the Primary and Secondary Clock Source options, only Internal can be
selected for both options. All other selections must have different settings
(e.g., if Primary Clock Source is set to Net1, Secondary Clock Source
cannot be set to Net1).
Net1 – The primary clock is derived from the Network1 T1 interface.
DSXs-p – The primary clock is derived from the DSX-T1 interface located in Slot s,
Port p. This setting only appears if the DSX-1 interface is enabled (see Configuring the
DSX-1 Interface, page 8-32).
Internal – The primary clock is the internal clock.
DBM – The primary clock is derived from the DBM. This selection only appears if the
DBM is installed and enabled.
Secondary Clock Source
Possible Settings: Net1, DSXs-p, Internal, DBM
Default Setting: Internal
Provides a secondary clock source when the primary clock source fails. The source
selected for this configuration option provides all of the timing within the unit and the
clocks for all of the external interfaces.
The clock source will switch back to primary when the primary clock source returns and
is stable for 10 seconds. If the secondary clock source fails, the clock source will switch
to internal. The clock source will switch back to primary when the primary clock source
returns and is stable for 10 seconds.
NOTE:
For the Primary and Secondary Clock Source options, only Internal can be
selected for both options. All other selections must have different settings
(e.g., if Primary Clock Source is set to Net1, Secondary Clock Source
cannot be set to Net1).
Net1 – The secondary clock is derived from the Network1 T1 interface.
DSXs-p – The secondary clock is derived from the DSX-T1 interface located in Slot s,
Port p. This setting only appears if the DSX-1 interface is enabled (see Configuring the
DSX-1 Interface, page 8-32).
Internal – The secondary clock is the internal clock.
DBM – The secondary clock is derived from the DBM. This selection only appears if the
DBM is installed and enabled.
9191-A2-GH30-00
DRAFT — June 1999
8-27
Configuration
System Alarm Relay
Specifies whether an alarm condition for the unit will activate the system alarm relay.
The alarm relay is deactivated when the condition causing the alarm is corrected. If
more than one alarm condition is present, the alarm relay remains active until all alarm
conditions are cleared for that NextEDGE system. You can also deactivate an alarm via
the System Alarm Relay Cut-Off selection from the Control menu.
Display Conditions – This option only appears for systems in a 5-slot or 14-slot
housing.
Alarm conditions are:
H Self-Test Failure.
H Device Fail.
H Power Supply Failure. (For units in a multislot housing, this alarm may also
indicate a fan tray alarm.)
H Network Communication Link Down.
H CTS Down.
H DTR Down.
H LMI Down.
H DLCI Down.
H SLV Timeout.
H Out of Frame (OOF) at Network, DSX-1, or PRI.
H Continuous Loss of Signal (LOS) condition at the Network, DSX-1, or PRI
interface.
H Yellow Alarm Signal on the Network, DSX-1, or PRI interface.
H Alarm Indication Signal (AIS) received at the Network, DSX-1, or PRI interface.
H Excessive Error Rate (EER) detected at the Network or PRI interface.
H Primary or Secondary Clock Failure.
H ISDN Network Failure.
H DBM Download Required.
H DBM BRI Card Failed.
H Out of Frame (OOF) for a 64k CC Loop on any OCU-DP port.
Enable – Activates alarm conditions on the system alarm relay when an alarm condition
occurs.
Disable – Does not activate the system alarm relay when an alarm condition occurs.
8-28
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Setting Up Each Physical Interface
Configure physical characteristics using the following interface options:
H
T1 Network Physical Options (below)
H
DSX-1 Interface Physical Options on page 8-32.
H
Data Port Physical Options on page 8-34.
Configuring the T1 Network Interface Physical Options
Select Physical to display or change the physical configuration options for the
T1 Network interface (see Table 8-4) following this menu selection sequence:
Main Menu → Configuration → Network → Physical
Table 8-4. T1 Network Physical Options (1 of 3)
Interface Status
Specifies whether the interface selected in the Network field is available for use.
Enable – The interface is available.
Disable – The interface is not available for use. When the interface is disabled, any
existing cross-connect assignments for this interface will be cleared, no alarms or traps
for this interface will be generated, no configuration options will be displayed, and all
LEDs associated with this interface will remain off.
Line Framing Format
Possible Settings: D4, ESF
Default Setting: ESF
Specifies the framing format for transmitted and received signals on the T1 network
interface.
D4 – Uses D4 framing format.
NOTE:
This setting is not recommended by network carriers. False yellow alarms
may occur after traffic has been running and the channel returns to idle, or
when there is light traffic when other settings are selected. ESF format
does not create this problem.
ESF – Uses Extended Superframe framing format.
Line Coding Format
Possible Settings: AMI, B8ZS
Default Setting: B8ZS
Specifies the line coding format for the network interface.
AMI – Uses Alternate Mark Inversion (AMI) line coding format.
B8ZS – Uses Bipolar 8 Zero Substitution (B8ZS) line coding format.
9191-A2-GH30-00
DRAFT — June 1999
8-29
Configuration
Line Build Out (LBO)
Possible Settings: 0.0, –7.5, –15, –22.5
Default Setting: 0.0
Specifies the line build out for the signal transmitted to the network.
0.0, –7.5, –15, –22.5 – Specifies line build out in dB.
Bit Stuffing
Possible Settings: 62411, Disable
Default Setting: 62411
Determines the type of bit insertion to provide ones density requirements for data
transmitted to the network.
Display Conditions – This option does not appear when Line Coding Format is set
to B8ZS.
62411 – Inserts a one in the data after 15 consecutive zeros are received or the density
of ones falls below 12.5%. This setting complies with AT&T TR 62411, but is not
recommended for frame relay data because it inserts errors in the data traffic.
Disable – Disables bit stuffing. Ones density is not enforced on data sent to the
network.
Network Initiated LLB
Allows the initiation and termination of the line loopback (LLB) to be controlled by the
receipt of LLB-Actuate and LLB-Release commands from the network.
Enable – LLB is controlled by LLB-Actuate and LLB-Release commands. Receiving a
LLB-Actuate command causes the unit to enter a line loopback (provided an LLB can be
performed in the unit’s current state). Receiving an LLB-Release command terminates
the LLB.
Disable – The unit ignores the LLB-Actuate and LLB-Release commands.
NOTE:
When disabled, the system is not in compliance with ANSI T1.403 or
AT&T TR 62411.
Network Initiated PLB
Allows the initiation and termination of the payload loopback (PLB) to be controlled by
the receipt of PLB-Actuate and PLB-Release commands from the network.
Display Conditions – This option only appears when Line Framing Format is set
to ESF.
Enable – PLB is controlled by PLB-Actuate and PLB-Release commands. Receiving a
PLB-Actuate command causes the system to enter a payload loopback (provided a PLB
can be performed in the unit’s current state). Receiving a PLB-Release command
terminates the PLB.
Disable – The unit ignores the PLB-Actuate and PLB-Release commands.
NOTE:
8-30
When disabled, the unit is not in compliance with ANSI T1.403 or
AT&T TR 54016.
DRAFT — June 1999
9191-A2-GH30-00
Configuration
ANSI Performance Report Messages
Specifies whether ANSI T1.403 compliance performance report messages (PRMs) are
generated and sent to the network over the ESF facility data link every second.
to ESF.
Enable – Generates and sends PRMs.
Disable – Does not generate and send PRMs.
Excessive Error Rate Threshold
Possible Settings: 10E-4, 10E-5, 10E-6, 10E-7, 10E-8, 10E-9
Default Setting: 10E-4
Sets the error rate threshold that determines when an EER condition is declared. The
excessive error rate is determined by the ratio of the number of CRC6 errors to the total
number of bits received over a set period of time.
to ESF.
10E-4 – Declares an EER if more than 1,535 CRC6 errors are detected in a 10 second
period. Clears when fewer than 1,536 CRC6 errors are detected within the same time
period.
10E-5 – Declares an EER if more than 921 CRC6 errors are detected in a 60 second
period or a 10 – 4 condition occurs. Clears when fewer than 922 CRC6 errors are
detected within the same time period.
period or a 10 – 5 or 10 – 4 condition occurs. Clears when fewer than 93 CRC6 errors are
period or a 10 – 6, or 10 – 5, or 10 – 4 condition occurs. Clears when fewer than 10 CRC6
errors are detected within the same time period.
10E-8 – Declares an EER if more than 41 CRC6 errors are detected in three 15 minute
intervals or a 10 –7, 10 – 6, 10 – 5, 10 – 4 condition occurs. Clears when fewer than
42 CRC6 errors are detected within the same time period.
intervals or a 10 – 8, 10 –7, 10 – 6, 10 – 5, or 10 – 4 condition occurs. Clears when fewer
than 5 CRC6 errors are detected within the same time period.
Circuit Identifier
Possible Settings: Text Field, Clear
Default Setting: blank
Identifies the transmission vendor’s circuit information to facilitate troubleshooting.
Text Field – Edit or display circuit identifier information (maximum 255 characters).
Clear – Removes the circuit identifier information.
9191-A2-GH30-00
DRAFT — June 1999
8-31
Configuration
Configuring the DSX-1 Interface Physical Options
Select DSX-1 to display or change the physical configuration options for the
DSX-1 interface (see Table 8-5).
Main Menu → Configuration → DSX-1
Table 8-5. DSX-1 Physical Options
Interface Status
Specifies whether the DSX-1 interface selected is available for use.
Enable – The interface is available.
Disable – The interface is not available for use. If there are time slots assigned to the
DSX-1 interface when you attempt to disable it, the message This action will clear all
DSX-1 Cross Connections. Are You Sure? No appears. If you select:
No – The operation is cancelled.
Yes – The following occurs:
H All existing DSX-1 interface cross-connect assignments are cleared.
H Alarms or traps associated with the DSX-1 interface are not generated.
H LEDs associated with the DSX-1 interface are held in an “off’’ state.
Line Framing Format
Specifies the framing format for transmitted and received signals on the DSX-1
interface.
ESF – Uses Extended Superframe (ESF) framing format.
Line Coding Format
Possible Settings: AMI, B8ZS
Default Setting: B8ZS
Specifies the line coding format for the DSX-1 interface.
AMI – Uses Alternate Mark Inversion (AMI) line coding format.
B8ZS – Uses Bipolar 8 Zero Substitution (B8ZS) line coding format.
8-32
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Table 8-5. DSX-1 Physical Options
Line Equalization
Possible Settings: 0 –133, 133 – 266, 266 – 399, 399 – 533, 533 – 655
Default Setting: 0 –133
Permits a standard DSX signal to be delivered over a distance of up to 655 feet.
0 –133 – Equalization on the DSX-1 side allows up to 133 feet of cable between the unit
and the DTE.
133 – 266 – Equalization on the DSX-1 side allows up to 266 feet of cable between the
unit and the DTE.
unit and the DTE.
unit and the DTE.
unit and the DTE.
Send All Ones on DSX-1 Failure
Determines whether action is taken when a valid signal cannot be recovered for the
DSX-1 (LOS, continuous OOF, or AIS).
Enable – Sends all ones on the DS0 channels allocated to the DSX-1 interface in the
event of an LOS, AIS, or continuous OOS condition on the DSX-1 interface.
Disable – No action is taken when a signal fails on the DSX-1 interface. The data
received is passed through the network interface channels unchanged.
9191-A2-GH30-00
DRAFT — June 1999
8-33
Configuration
Configuring Data Port Physical Options
Select Physical to display or change the physical characteristics of the data port
connected to the DTE (see Table 8-6).
Main Menu → Configuration → Data Ports → Physical
The Data Port Physical Options screen appears for Port 1 of the first slot
containing a NAM. If desired, enter the slot and port number of another data port.
Table 8-6. Data Port Physical Options (1 of 4)
Port Status
Determines whether the data port is being used and can be configured.
Enable – The port is active, and can be used to transmit and receive data.
Disable – The port is not active. When the port is disabled, the following will occur:
H No alarms or traps configured for the port will be generated.
H LED for the port will be held in an Off state.
H Existing synchronous data cross-connect assignments associated with the port
are cleared.
Port Use
Possible Settings: Frame Relay, Synchronous Data
Default Setting: Frame Relay
Determines how the data port will be used.
Display Conditions – This option only appears for user data Port-Z on the NAM.
Frame Relay – The port is configured for frame relay traffic. Frame relay links, DLCis,
and PVC connections can be configured on this port.
Synchronous Data – The port is configured for standard TDM data, and can be
cross-connected to a time slot on a T1 interface.
H Existing cross-connect assignments associated with the port are cleared.
Port Type
Possible Settings: E530, V.35, RS449, X.21
Default Setting: V.35
Selects the type of port to be used for the user data port.
Display Conditions – This option only appears for flexible user data ports on
synchronous data APMs.
E530 – The port is an EIA-530A-compatible DCE. An EIA-530-compatible DTE can be
directly connected to the DB25 connector.
V.35 – The port is a V.35-compatible DCE. A V.35-compatible DTE can be connected to
the DB25 connector by using an adapter.
RS449 – The port is an RS449-compatible DCE. An RS449-compatible DTE can be
connected to the DB25 connector by using DB37-to-DB25 adapter.
X.21 – The port is a V.11/X.21-compatible DCE. A V.11/X.21-compatible DTE can be
connected to the DB25 connector by using an adapter.
8-34
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Max Port Rate (Kbps)
Possible Settings: 1536, 2048
Specifies the maximum clock rate for a user data port. The data rate for this port is
limited to the rate specified by this option so that the maximum rate supported by an
attached DTE is not exceeded.
Display Conditions – This option only appears when Port Use is set to Frame Relay,
and the selected port is Port-2 on the NAM.
Port Base Rate (Kbps)
Possible Settings: Nx64, Nx56
Default Setting: Nx64
Specifies the base rate for the data port, which is a multiple (from 1 to 24) of the base
rate specified by this option. N is a number from 1 to 24.
Display Conditions – This option only appears when Port Use is set to
Synchronous Data.
Nx64 – The base rate for the port is 64 kbps.
Nx56 – The base rate for the port is 56 kbps.
Transmit Clock Source
Possible Settings: Internal, External
Determines whether the DTE’s transmitted data is clocked into the unit by its internal
transmit clock or by the external clock provided by the DTE.
Display Conditions – This option does not appear when Port Type is set to X.21.
Internal – The unit uses the interchange circuit DB (ITU 114) – Transmit Signal Element
Timing (TXC) (DCE source) for timing the incoming data.
External – The DTE provides the clock for the transmitted data, and the unit uses
the interchange circuit DA (ITU 113) – Transmit Signal Element Timing (XTXC)
(DTE source) for timing the incoming data.
Possible Settings: Auto, Enable, Disable
Default Setting:
Auto – On NAM user data ports
Disable – On APM user data ports
Specifies whether the phase relationship between the data received by the unit from the
DTE (TXD) and the clock used to time this incoming data will be inverted in order to
minimize transmission errors.
Auto – Phase relationship is automatically adjusted to optimize data transmission from
the DTE. This option is only available on user data ports on the NAM.
Enable – Phase relationship is inverted.
Disable – Phase relationship is normal; it is not inverted.
9191-A2-GH30-00
DRAFT — June 1999
8-35
Configuration
Monitor DTR
Specifies whether the state of the DTE Ready (DTR) circuit on the user data port will be
used to determine when valid data communication is not possible with the DTE. When
this condition is detected, an alarm is generated, LMI is declared down, and no further
transfer of frame relay data can occur on this interface.
Display Conditions – This option only appears when Port Type is not set to X.21.
Enable – Interchange circuit CD (ITU 108/1/2)) – DTR is monitored to determine when
valid data communication is possible with the DTE.
Disable – DTR is not monitored. DTR is assumed to be asserted and data is being
transmitted, regardless of the state of the lead.
Monitor RTS (Control)
Specifies the conditions on the data port that determine when valid data is not being
sent from the DTE. When this condition is detected, all ones are sent to the network on
the DS0 channels allocated to the port.
Enable – When Port Type is V.35, EIA-530, or RS449, interchange circuit CA (ITU 105)
is used to monitor RTS to determine when valid data communication is possible with the
DTE. When Port Type is X.21, circuit C (ITU ???) is used.
Disable – RTS is not monitored. RTS is assumed to be asserted and data is being
transmitted, regardless of the state of the lead.
Port (DTE) Initiated Loopbacks
When Port Use is set to Frame Relay:
Possible Settings: Disable, Local
When Port Use is set to Synchronous Data:
Possible Settings: Disable, DTPLB, DCLB, Both
When Port Use is set to Frame Relay:
Allows a local external DTE Loopback to be started or stopped via DTE connected to
the port using the port’s interchange lead LL (ITU 141), specified by V.54.
Local – The local external DTE Loopback can be controlled by the DTE.
Disable – The loopback cannot be controlled by the DTE.
When Port Use is set to Synchronous Data:
Allows local Data Terminal Loopbacks (DTPLBs) and remote Data Channel Loopbacks
(DCLBs) to be controlled by the DTE connected to this port.
Disable – Local Data Terminal Loopbaclks (DTPLBs) and remote Data Channel
Loopbacks (DCLBs) cannot be controlled by the DTE.
DTPLB – DTPLBs for this port can be controlled by the DTE (circuit LL – CCITT 141)
specified by V.54. The port remains in loopback as long as the circuit statys on.
DCLB – DCLBs for this port can be controlled by the DTE (circuit RL – CCITT 140)
specified by V.54. The far-end equipment must support inband V.54 loopbacks.
Both – Local DTPLBs and remote DCLBs can be controlled by the DTE.
8-36
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Invert Transmit and Receive Data
Specifies whether transmitted and received data for the synchronous data port is
logically inverted before being transmitted or after being received from the network. Use
this configuration option for applications where data is being transported using HDLC
protocol, whereby inverting the data ensures that the ones density requirements for the
network are met.
Synchronous Data.
Enable – Inverts the transmitted and received data for the port.
Disable – Does not invert the transmitted and received data for the port.
Action on Network Yellow Alarm
Possible Settings: None, Halt
Default Setting: Halt
Specifies the action to take on the synchronous data port when a yellow alarm is
received on the network interface. (A yellow alarm indicates a problem with the signal
being transmitted to the network.)
Synchronous Data on NAM Port-2 and for user data ports on Synch Data APMs.
None – No action taken when a yellow alarm is received.
Halt – Halts the transmission of data received on the synchronous data port and all
ones are sent on circuit BB (ITU 104) – Receive Data (RD) and circuit CB (ITU 106) –
Clear-to-Send (CTS) is deasserted to the port when a yellow alarm is received.
Network Initiated Data Channel Loopback
Possible Settings: Disable, V.54, FT1, Both
Allows the initiation and termination of the Data Channel Loopback (V.54 loop 2) to be
controlled by the receipt of a DCLB-actuate and DCLB-release sequence (either V.54,
or FT1 [ANSI] compliant sequences) from the network or far end unit. When this
configuration is enabled (V.54, FT1, or Both), receiving a DCLB-actuate sequence on a
particular port causes the NAM to initiate a DCLB on that port (provided that a DCLB
can be performed based on the current state of the port and NAM). Receiving a
DCLB-release sequence terminates the DCLB.
Synchronous Data on NAM Port-2 and for user data ports on Synch Data APMs.
Disable – Ignores the DCLB-actuate and DCLB-release for the port.
V.54 – DCLB-actuate and DCLB-release sequences that comply with the V.54 standard
for “inter-DCE signaling for point-to-point circuits” are recognized and will control the
initiation and termination of a DCLB (V.54 Loop 2) for the port.
FT1 – DCLB-actuate and DCLB-release sequences that comply with either the
ANSI.403, Annex B standard for “in-band signaling for fractional T1 (FT1) channel
loopbacks” are recognized and will control the initiation and termination of a DCLB for
the port.
Both – DCLB-actuate and DCLB-release sequences that comply with either the ANSI
or V.54 standard are recognized and will control the initiation and termination of a DCLB
for the port.
9191-A2-GH30-00
DRAFT — June 1999
8-37
Configuration
Assigning Time Slots/Cross Connections
The system allows you to assign data paths between the various interfaces to
share the T1 network. Assuming that both the Network and DSX-1 interfaces are
enabled, you can make the following cross connection assignments:
H
Frame relay links to Network interface time slots
H
DSX-1 to the Network interface time slots
H
Voice or Synchronous Data Ports to Network or DSX-1 time slots (see
Chapter 11, Application Modules, for additional information)
You can also clear cross-connection assignments for the system, or for a
selected slot or interface (see page 8-44).
Movement Between Assignment Screens
Time Slot Assignment screens provide functions keys for quick and easy access
to most other time slot assignments within the system.
Select . . .
To . . .
ClearAll
Reset all time slots that are not cross-connected (Assigned) to
another port or interface to Available. Available deletes a time slot
assignment.
When Time Slot Discovery is enabled, rediscovery of time slots
assigned to frame relay will take place when the ClearAll operation
is saved.
DSXAssign
Go to the DSX-1 to Network Assignment screen.
VocAssign
Go to the Voice Port Assignments screen. This selection is only
available when an APM is installled.
FrAssign
Return to the Frame Relay Network Assignment screen.
NOTE:
Although not required, it is suggested that you progress through each screen
in order, from top to bottom.
Use the following procedures to assign cross connections.
8-38
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Assigning DSX-1 Time Slots to the Network Interface
Before assigning Network time slots for use by Frame Relay, configure the
Network physical and Frame Relay options (if needed), then allow Time Slot
Discovery to autodetect and assign the appropriate time slots to Frame Relay.
If there are multiple Frame Relay data links on the Network interface, or if
Time Slot Discovery is not currently active, you can manually assign time slots on
the Network interface for Frame Relay traffic using the Frame Relay Network
Assignments screen. This screen is read-only when Time Slot Discovery is set to
Enable for the Network interface.
Value
Meaning
Time Slot
Discovery
Specifies whether the time slots used for frame relay traffic should
be discovered from the Network interface upon detection of LMI
failure. This option allows additional time slots to be added without
manual device reconfiguration.
Nxx
This field represents time slot xx of the selected Network interface.
Assigned
The time slot is already assigned to something other than Frame
Relay, so it is unavailable. Assigned time slots cannot be modified
from this screen.
Available
The time slot is currently unassigned.
FrameRly1
Time slot ss is assigned to Frame Relay service, Link 1.
Time Slot Assignment Rule:
Valid Network time slots are either labeled as Available, or contain a Frame
Relay link 1 assignment.
" Procedure
1. Follow this menu sequence:
Main Menu → Configuration → Time Slot Assignment →
Frame Relay Network Assignments
2. The Frame Relay Network Assignments screen appears. This screen
contains a matrix of the current assignment status of all time slots on the
Network interface.
3. Enable or disable Time Slot Discovery. When enabled, the unit will examine
all time slots not cross-connected to other ports to determine which time slots
are being used by the network for frame relay traffic. These time slots are set
to FrameRly1. This is the factory default. When disabled, you must make
time slot assignments manually.
4. If Time Slot Discovery is disabled, assign Network time slots for use by
Frame Relay service link 1 by typing FrameRly1 in the selected Network field.
5. Repeat Step 4 until all desired time slots are assigned.
6. Save your assignments and return to the Time Slot Assignment menu.
9191-A2-GH30-00
DRAFT — June 1999
8-39
Configuration
DSX-1 time slots are assigned by channel allocation, where you specify individual
time slots. The DSX-1 interface must be enabled to assign DSX-1 time slots to
the Network interface (see Table 8-5, DSX-1 Physical Options).
Value
Meaning
Nxx
The upper field represents time slot xx of the selected Network
interface.
Assigned
The time slot is already assigned to something other than a DSX-1
time slot, so it is unavailable. Assigned time slots cannot be
modified from this screen.
Available
The time slot is currently unassigned.
Ds-p/yy
Time slot yy of DSX-1 interface p in slot s is assigned to the
Network time slot identified right above it (Nxx).
Time Slot Assignment Rules:
H
Valid Network time slots are either labeled as Available, or contain a DSX-1
time slot assignment
H
Valid DSX-1 time slots are those that are unassigned, and the currently
assigned time slot
H
Order of display is as follows:
— Available is the first selection
— Then, from lowest DSX-1 interface to the highest DSX-1 interface
— Then lowest available time slot number to the highest available time slot
number
For example, if the cursor is on a field with the Available value under assigned
time slot Nxx, pressing the Spacebar causes this field’s values to cycle through
all valid DSX-1 time slots, starting with Ds-p/yy, assuming it is unassigned. If
Ds-p/yy is already assigned, the next valid time slot in the order described above
is displayed.
8-40
DRAFT — June 1999
9191-A2-GH30-00
Configuration
" Procedure
Configuration → Time Slot Assignment→ DSX-to-Network Assignments
2. The DSX-1 to Network Assignments screen appears. It contains a matrix of
the current cross-connect status of all time slots on the Network interface.
3. Move the cursor to the next editable time slot (underlined). Use the spacebar
or type in a time slot to display the desired time slot assignment.
4. Repeat Step 3 until all desired time slots are assigned.
5. Save your assignments and return to the Time Slot Assignment menu.
DSX-1 Signaling Assignments and Trunk Conditioning
The second page of the DSX-1 to Network Assignments screen enables you to
define the signaling assignments and trunk conditioning for each time slot on the
DSX-1 interface. You can specify whether robbed bit signaling information is
being passed within a given DS0, and the value of the signaling bits that will be
transmitted for that DS0 to the other cross-connected T1 interface if a Carrier
Group Alarm (CGA) occurs on a T1 interface.
Only those DSX-1-to-Network assignments from page 1 are displayed on this
page, from left to right and top to bottom in ascending order, by network and
time slot.
When a CGA condition (LOS, OOF, or AIS) is declared for a T1 interface, the
signaling bits being transmitted to the other T1 interface for the DS0 are forced to
idle for two seconds (except for user-defined patterns which are transmitted
immediately). This drops any call in progress. The signaling bits are then forced
to the selected state (Busy or Idle), and remain in this state until the CGA
condition clears. At this point, the received signaling bits from the T1 interface
which formerly had the CGA condition are passed through to the other T1
interface.
NOTE:
Trunk conditioning will only occur on DS0s that are cross-connected to
another T1 interface. All other DS0s remain unaffected by trunk conditioning.
Enter one of the values shown in Table 8-7 in each of the fields on both the
Network side and the DSX-1 side. Although you can choose any value for the
DSX-1 side, the default value displayed is based on a typical setting that would
be used with the corresponding Network side value. Typical pairs of values are
shown in the table below. If you change the Network side value, the DSX side
value is changed to the corresponding default value.
9191-A2-GH30-00
DRAFT — June 1999
8-41
Configuration
Table 8-7. Signaling and Trunk Conditioning Values (1 of 2)
Network
Side Value
DSX-1 Side
Default
Value
Meaning
None
No signaling used on this DS0. Use this setting if there is
no voice signaling information being passed on this DS0
(clear channel).
None
RBS
(default)
Robbed Bit Signaling is used on this DS0, but no trunk
conditioning. Signaling bits will be passed to the T1
interface to which this DS0 is cross-connected when this
T1 interface is not in CGA, but the signaling bits will be all
ones when CGA is present.
RBS
The following values will configure the cross-connect for RBS, as well as perform
the trunk conditioning, indicated when a CGA condition occurs. Although the
ABCD signaling bits for each setting are described, only AB bits are transmitted
when the cross-connected T1 interface is using D4 framing.
8-42
E&M-idle
The signaling bits transmitted to the cross-connected T1
E&M idle
interface during a CGA represent the idle state for an E&M
interface (ABCD = 0000).
E&M-busy
interface during a CGA represent the busy state for an
E&M interface (ABCD = 1111).
E&M busy
FXOg-idle
interface during a CGA represent the idle state for an FXO
Ground-Start interface (ABCD = 1111).
FXSg-idle
FXOg-busy
FXO Ground-Start interface (ABCD = 0101).
FXSg-busy
FXOl-idle
interface during a CGA represent the idle state for an FXO
Loop-Start interface (ABCD = 0101).
FXSl-idle
FXOl-busy
FXO Loop-Start interface (ABCD = 0101).
FXSl-busy
FXSg-idle
interface during a CGA represent the idle state for an FXS
Ground-Start interface (ABCD = 0101).
FXOg-idle
FXSg-busy
FXS Ground-Start interface (ABCD = 1111).
FXOg-busy
FXSl-idle
interface during a CGA represent the idle state for an FXS
Loop-Start interface (ABCD = 0101).
FXOl-idle
FXSl-busy
FXS Loop-Start interface (ABCD = 1111).
FXOl-busy
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Table 8-7. Signaling and Trunk Conditioning Values (2 of 2)
Network
Side Value
FXOD-idle
interface during a CGA represent the idle state for an
FXODN interface (ABCD = 0000).
FXSD-idle
FXOD-busy
FXODN interface (ABCD = 1111).
FXSD-busy
FXSD-idle
interface during a CGA represent the idle state for an
FXSDN interface (ABCD = 0000).
FXOD-idle
FXSD-busy
FXSDN interface (ABCD = 1111).
FXOD-busy
PLAR3idle
interface during a CGA represent the idle state for a PLAR
D3 interface (ABCD = 0000).
PLAR3idle
PLAR3busy
PLAR D3 interface (ABCD = 1111).
PLAR3busy
PLAR4idle
interface during a CGA represent the idle state for a PLAR
D4 interface (ABCD = 1111).
PLAR4idle
PLAR4busy
PLAR D4 interface (ABCD = 0000).
PLAR4busy
DPO-idle
interface during a CGA represent the idle state for a DPO
DPT-idle
DPO-busy
DPT-busy
interface during a CGA represent the busy state for a DPO
DPT-idle
interface during a CGA represent the idle state for a DPT
DPO-idle
DPT-busy
interface during a CGA represent the busy state for a DPT
DPO-busy
USER-xxxx
interface during a CGA represent a user-defined pattern of
ABCD = xxxx.
USER-xxxx1
1 xxxx
9191-A2-GH30-00
Meaning
DSX-1 Side
Default
Value
is the same value on both the Network and the DSX-1 sides.
DRAFT — June 1999
8-43
Configuration
Clearing Assignments
Clearing assignments sets all time slots to unassigned. Follow this menu
selection sequence:
Main Menu → Configuration → Time Slot Assignment → Clear Assignments
Configuring Frame Relay LMI for an Interface
Select Frame Relay from the selected Network or Data Ports menu. Based upon
the information about the local management interface (LMI ) and assigned line
conditions supplied by the service provider, edit the Frame Relay configuration
options (see Table 8-8). To guarantee a faster response to a backup condition,
set the LMI polling parameters appropriately.
Main Menu → Configuration → [Network/Data Ports] → Frame Relay
Table 8-8. Frame Relay and LMI Options (1 of 4)
LMI Protocol
Possible Settings: Initialize_From_Net1FR1, Initialize_From_Interface,
Auto_On_LMI_Fail, Standard, Annex-A, Annex-D
Default Setting:
For data port links: Initialize_From_Interface
For network links: Auto_On_LMI_Fail
Specifies either the LMI protocol supported on the frame relay interface or the discovery
source for the LMI protocol.
Initialize_From_Net1FR1 – The LMI type supported on this frame relay link will be
configured to match the LMI protocol initially discovered on the primary Network frame
relay link (Net1FR1). LMI Protocol is set to None internally, but once a protocol has
become active or is set on the primary Network link, the protocol will be set to the same
value on this link (Standard, Annex-A or Annex-D). The protocol will not be updated
based on changes to Net1FR1 after being set initially.
Display Conditions – This option value only appears for a user data port.
Initialize_From_Interface – The LMI type supported on this frame relay link will be
configured to match the LMI protocol discovered from the attached Network line or DTE
device. Once a protocol has become active, the protocol will be set to the protocol
discovered (Standard, Annex-A or Annex-D) on the frame relay link. The protocol will not
be updated after being initially discovered. Frame relay links on user data ports discover
the LMI protocol from an attached device via LMI status polls. Frame relay links on the
Network interface discover LMI protocol by sending polls to an attached Network line
and “listening” for correct poll response messages.
8-44
DRAFT — June 1999
9191-A2-GH30-00
Configuration
LMI Protocol
Possible Settings: Initialize_From_Net1FR1, Initialize_From_Interface,
Auto_On_LMI_Fail, Standard, Annex-A, Annex-D
(Cont’d)
Auto_On_LMI_Fail – The LMI type supported on this frame relay link will be configured
to match the LMI protocol discovered from the attached Network line or the DTE device
whenever an LMI Link Down failure occurs. This option is available for frame relay links
on the Port and Network interfaces. Frame relay links on user data ports discover the
LMI protocol from LMI status polls on attached DTE devices. Frame relay links on the
Network interface discover LMI protocol by sending polls to an attached Network line
and “listening” for correct poll response messages. If Time Slot Discovery is enabled, the
current time slots for the link will be deleted and incoming data patterns will be used to
reassigns DS0 time slots for the frame relay link before attempting to discover LMI
Protocol.
Standard – Supports Standard LMI and the Stratacom enhancements to the
Standard LMI.
Annex-A – Supports LMI as specified by Q.933, Annex A.
Annex-D – Supports LMI as specified by ANSI T1.617, Annex D.
LMI Parameters
Possible Settings: System, Custom
Default Setting: System
Allows you to use the system LMI options, or to set specific LMI options for this
interface.
System – Use system LMI options (see Table 8-1, System Frame Relay and LMI
Options).
Custom – Use the following options in this table to configure LMI parameters.
LMI Error Event (N2)
Default Setting: 3
Configures the LMI-defined N2 parameter which sets the number of errors that can
occur on the LMI link before reporting an error.
Display Conditions – This option only appears when LMI Parameters is set to
Custom.
1 – 10 – Specifies the number of errors that can occur on the LMI link.
LMI Clearing Event (N3)
Default Setting: 1
Configures the LMI-defined N3 parameter which sets the number of error-free messages
that must be received before clearing an error event.
Custom.
1 – 10 – Specifies the number of error-free messages that must be received.
9191-A2-GH30-00
DRAFT — June 1999
8-45
Configuration
LMI Status Enquiry (N1)
Possible Settings: 1, 2, 3, 4, . . . 255
Default Setting: 6
Configures the LMI-defined N1 parameter which sets the number of status enquiry
polling cycles that the user side of the LMI initiates before a full status enquiry is
initiated. Applies to and configured for the user side of the UNI only.
Custom, and only on the network interface.
1 – 255 – Specifies the number of status enquiry polling cycles that can be initiated.
LMI Heartbeat (T1)
Default Setting: 10
Configures the LMI-defined T1 parameter which sets the number of seconds between
the initiation of status enquiry messages on the user side of the LMI. Applies to and
configured for the user side of the UNI only.
Custom, and only on the network interface.
5 – 30 – Specifies the number of seconds between the initiation of status enquiry
LMI Inbound Heartbeat (T2)
Default Setting: 15
Configures the LMI-defined T2 parameter which sets the number of seconds between
the receipt of status enquiry messages on the network side of the LMI. Applies to and
configured for the network side of the UNI only.
Custom, and only on a user data port.
5 – 30 – Specifies the number of seconds between the receipt of status enquiry
LMI N4 Measurement Period (T3)
Default Setting: 20
Configures the LMI-defined T3 parameter which is the time interval (in seconds) that the
network side of the LMI uses to measure the maximum number of status enquiry
messages received (N4) from the user side. Applies to and configured for the network
side of the UNI only.
Custom, and only on a user data port.
5 – 30 – Specifies the interval of time in increments of 5.
8-46
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Frame Relay DS0s Base Rate
Selects the base rate for the DS0s allocated to frame relay on the Network interface.
Display Conditions – This option only appears for the network interface.
Nx64 – The base rate is 64 kbps.
Nx56 – The base rate is 56 kbps.
Network Initiated DCLB
Possible Settings: Disable, V.54, ANSI_FT1, Both
Default Setting: Both
Allows the initiation and termination of the Data Channel Loopback (DCLB V.54 loop 2)
to be controlled by the receipt of a DCLB-actuate or DCLB-release sequence (either
V.54 or FT1-ANSI compliant) from the network. When enabled, this option causes a
NextEDGE device to initiate a DCLB on the DS0s allocated to this frame relay link when
a DCLB-actuate sequence is received.
Display Conditions – This option only appears for the network interface.
Disable – The DCLB-actuate and DCLB-release sequences are ignored for this frame
relay link.
V.54 – DCLB-actuate and DCLB-release sequences that comply with V.54 standard for
“Inter-DCE signaling for point-to-point circuits” will be recognized and will control
initiation and termination of a DCLB (V.54 Loop 2) for this frame relay link.
ANSI_FT1 – DCLB-actuate and DCLB-release sequences that comply with ANSI
T1.403, Annex B standard for “In-band signaling for fractional-T1 (FT1) channel
loopbacks” will be recognized and will control initiation and termination of a DCLB for
this frame relay link.
Both – DCLB-actuate and DCLB-release sequences that comply with either V.54 or
ANSI T1.403, Annex B standard will be recognized and will control initiation and
termination of a DCLB for this frame relay link. The actuate and release sequences do
not need to match (for example, a DCLB started with a V.54 actuate sequence can be
stopped with an FT1 release sequence).
9191-A2-GH30-00
DRAFT — June 1999
8-47
Configuration
Configuring DLCI Records for Each Interface
If Auto-Configuration is not used, it is necessary to create DLCI records manually
for each interface. If you do use Auto-Configuration, then it may only be
necessary to create a management DLCI between the system and the router
attached to the data port.
DLCI records for all interfaces are created and configured in the same manner.
Procedures for creating DLCI Records are shown in the following examples.
" Procedure
To create and configure DLCI records:
1. Select the desired DLCI records.
Main Menu→ Configuration→ [Network/Data Ports/ISDN]→ DLCI Records
For an ISDN link DLCI Record, select the desired ISDN link.
2. Select New and press Enter to create a new DLCI.
The DLCI Records Entry screen appears for the frame relay link selected.
The DLCI Number field is blank, while the rest of the fields are filled with the
default value settings.
NOTE:
If the maximum number of DLCIs have already been defined, the
message No more DLCIs allowed appears.
3. Enter the DLCI number to be created.
4. Change DLCI option settings, as required.
NOTE:
Do not multiplex a DLCI unless a NextEDGE or FrameSaver device is at
both ends of the connection.
5. Save the DLCI Record.
8-48
DRAFT — June 1999
9191-A2-GH30-00
Configuration
" Procedure
To change DLCI records:
1. Select the desired DLCI record.
Main Menu→ Configuration→ [Network/Data Ports/ISDN]→ DLCI Records
For an ISDN link DLCI Record, select the desired ISDN link.
2. Select Modify to change a DLCI record.
3. Select the DLCI record to be modified from the list of all DLCIs on the frame
relay link and interface displayed. Then, press Enter.
The DLCI record entry screen displays with the fields initialized for the
selected DLCI.
4. Make the desired changes.
If a connected network DLCI’s type is changed from Multiplexed to Standard, the
following prompt will appear when the DLCI is part of a connection: DLCI in
Connection. Update DLCI usage as follows:
Select one of the following choices:
H
Delete EDLCI Connections and Make a Mgmt Only PVC
If you choose this selection, the following actions occur. This is typically done
by frame relay service providers so there is management connectivity from
the network operation/control center (NOC or NCC):
— Removes this DLCI as the Alternate Destination on all PVC Connections
(see Table 8-10, PVC Connection Options), and Management PVC
Connections (see Table NO TAG, Management PVC Options).
— Resets any Trap Manager Destination (see Table 8-16, SNMP Traps and
Trap Dial-Out Options), or Default Network Destination (see Table 8-11,
Node IP Options) that is configured for a Management PVC with this
DLCI to the factory default setting.
— Deletes all PVC Connections (see Configuring PVC Connections on
page 8-53) and Management PVC Connections (see Configuring
Management PVCs on page 8-59) involving this DLCI as the source or
primary destination.
— Deletes all excess DLCIs (on user data ports) that were used only in
deleted connections.
— Changes DLCI Type from Multiplexed to Standard for the selected
Network DLCI.
— Configures the Network DLCI as a Management PVC (see Configuring
Management PVCs on page 8-59).
9191-A2-GH30-00
DRAFT — June 1999
8-49
Configuration
H
Delete EDLCI Connections and Make a standard PVC to frame relay link,
DLCI nnnn
If you choose this selection, the following actions occur:
— Removes this DLCI as the Alternate Destination on all PVC Connections
(see Table 8-10, PVC Connection Options), and Management PVC
Connections (see Table NO TAG, Management PVC Options).
— Resets any Trap Manager Destination (see Table 8-16, SNMP Traps and
Trap Dial-Out Options), or Default Network Destination (see Table 8-11,
Node IP Options) that is configured for a Management PVC with this
DLCI to the factory default setting.
— Deletes all PVC Connections (see Configuring PVC Connections on
page 8-53) and Management PVC Connections (see Configuring
Management PVCs on page 8-59) involving this DLCI as the source or
primary destination.
— Deletes all excess DLCIs (other than frame relay link, DLCI nnnn) that
were used only in deleted connections.
— Changes DLCI Type from Multiplexed to Standard for the selected
Network DLCI.
— Creates a standard PVC connection between this Network DLCI and
frame relay link, DLCI nnnn (see Configuring PVC Connections on
page 8-53).
H
Leave as Multiplexed DLCI
The DLCI Type remains unchanged. You must delete the DLCI connection
before you can change the DLCI Type.
" Procedure
To create additional DLCI records:
1. Press Esc to return to the previous DLCI Records screen.
Helpful Hint:
Once you create the first DLCI record, you can use the CopyFrom
function to create additional records, assigning a unique number to each
new DLCI record.
Example:
First DLCI numbered 16
Second DLCI numbered 17
2. Select New, or the CopyFrom function, and press Enter.
When the CopyFrom function is selected, the DLCI Record specified is used
to create a new DLCI record. You just have to assign a DLCI Number to the
new record.
8-50
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Table 8-9. DLCI Record Options (1 of 2)
DLCI Number
Default Setting: Initially blank; no default.
Specifies the number identifying the DLCI. The parameter determines which DLCI
record is used for transferring data on a particular frame relay interface. DLCI numbers
range from 0 to 1023. However, the numbers 0 –15 and 1008 –1023 are reserved. Entry
of an invalid number results in the error message Value Out of Range (16 –1007).
If the DLCI number is part of a connection, this field is read-only.
NOTES: – If a DLCI number is not entered, the DLCI record is not created.
– The DLCI number entered must be unique for the interface.
16 – 1007 – Specifies the DLCI number.
DLCI Type
Possible Settings: Standard, Multiplexed
Default Setting:
For DLCIs on user data ports: Standard
For DLCIs on the network and ISDN interfaces: Multiplexed .
Specifies whether the DLCI is standard or multiplexed. This field is read-only when the
selected DLCI is used in a PVC or Management link connection and the DLCI Type is
Standard.
Display Conditions – This option does not appear for a user data port.
Standard – Supports standard DLCIs as specified by the Frame Relay Standards. Use
this setting when a non-NextEDGE or non-FrameSaver unit is at the other end.
Multiplexed – Enables multiplexing of multiple connections into a single DLCI. Allows a
single PVC through the frame relay network to carry multiple DLCIs as long as these
connections are between the same two endpoints (proprietary). Do not use this setting
unless there is a NextEDGE or FrameSaver unit at each end of the connection.
CIR (bps)
Possible Settings: 0 – maximum line rate on port
Determines the data rate for the DLCI that the network commits to accept and carry
without discarding frames; the CIR in bits per second. If an invalid rate is entered, the
error message Value Out of Range (0 – x) is displayed, x being the maximum line
rate available on the port.
Committed Burst Size Bc (Bits)
Possible Settings: CIR, Other
Default Setting: CIR
Specifies the committed amount of transmitted data in bits that the network will accept
without discarding frames (Bc).
CIR – Specifies the CIR amount of data that will be accepted before frames are
discarded.
Other – Allows you to specify a rate other than the CIR in the Port Rate-Bc field. In this
case, Tc is calculated according to I.370.
9191-A2-GH30-00
DRAFT — June 1999
8-51
Configuration
Table 8-9. DLCI Record Options (2 of 2)
Bc
Default Setting: CIR rate
Allows you to display or change the committed burst size for the DLCI.
Display Conditions – This option only appears when Committed Burst Size is set
to Other.
Excess Burst Size Be (Bits)
Possible Settings: This field is blank; it explains Be.
Default Setting: There is no default setting.
Specifies the maximum amount of data in bits that the network may accept beyond the
CIR without discarding frames.
Be
Default Setting: maximum port rate minus 64000 bits.
Allows you to display or change the excess burst size for the DLCI.
DLCI Priority
Possible Settings: Low, Medium, High
Default Setting: High
Specifies the relative priority for data received on the DLCI from an attached device
(also known as quality of service). All data on Port 1 is cut-through, as long as there is
no higher-priority data queued from another user port. The DLCI priority set for an
interface applies to data coming into that interface. For example, the priority set for
DLCIs on Port 1 applies to data coming into Port 1 from the attached equipment (such
as a router).
Display Conditions – This option is not available on the Network or DBM interface.
NOTE:
Since pipelining occurs on Port-1, it is recommended that higher priority
data be connected to Port-1 .
Low – Data configured for the DLCI has low priority.
Medium – Data configured for the DLCI has medium priority.
High – Data configured for the DLCI has high priority.
Outbound Management Priority
Possible Settings: Low, Medium, High
Default Setting: Medium
Specifies the relative priority for management traffic sent on management PVCs
transmitted on this DLCI to the network.
Display Conditions – This option is not available on a user data port.
Low – Management data configured for the DLCI has low priority.
Medium – Management data configured for the DLCI has medium priority.
High – Management data configured for the DLCI has high priority.
8-52
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Configuring PVC Connections
Select PVC Connections to display or change the configuration options for the
PVC connections (see Table 8-10). DLCI records must have been configured for
the interface first. See Maximum PVCs, EDLCIs, and Management PVCs in
Chapter 1, About the NextEDGE System, for a table of the maximum number of
PVCs that you can configure.
If the system is equipped with an ISDN DBM, see Chapter 11, Dial Backup
Modules.
" Procedure
Main Menu → Configuration → PVC Connections
The PVC Connection Table screen appears.
2. Select New or M o dify from the PVC Connection Table screen to add or
change PVC connections between a source DLCI (link) and destination DLCI
(link) on a frame relay interface.
Also, to add or change an Alternate Destination DLCI for backup when the
primary link or destination DLCI is down and a backup link has been
established.
3. When New is selected, the configuration option field is blank. Tab to the first
configuration option and press the spacebar. The first valid selection appears
in the field.
NOTE:
Management links are not created using this screen. Go to the
Management PVC Entry screen:
Management PVCs
Table 8-10. PVC Connection Options (1 of 3)
Source Link
Possible Settings: Port-n, ISDN Link Name, Net1-FR1
Specifies the frame relay interface that starts a PVC connection; the from end of a
from-to link. The only valid settings for this configuration option are frame relay
interfaces that have at least one DLCI or EDLCI defined that are not part of a PVC
connection or management link. For example, if Port-1 has no DLCIs defined, Port-1
would not appear as a valid setting.
SxPort-n – Specifies the port n in slot x as the source link. Refers to frame relay links on
data ports capable of having the Port Use option set to Frame Relay (see Table 8-6,
Data Port Physical Options).
ISDN Link Name – Specifies the ISDN link of the DBM as the source link. This can be
any nonnull link name configured on an ISDN frame relay link on an installed DBM.
Net1-FR1 – Specifies the Network interface as the source link.
Clear All – Clears all Link and DLCI settings, and suppresses EDLCIs.
9191-A2-GH30-00
DRAFT — June 1999
8-53
Configuration
Source DLCI
Specifies the source DLCI for a frame relay interface. The DLCI must be defined and
cannot be part of a PVC connection or management link. For multiplexed DLCIs, at least
one EDLCI must be unconnected for the DLCI to be a valid selection.
NOTE:
Source DLCI has no value if Source Link contains no value.
Source EDLCI
Specifies the source Embedded Data Link Connection Identifier (EDLCI) for a frame
relay interface when a multiplexed DLCI record is selected as one end of a connection.
Display Conditions – This option only appears when Source DLCI contains a
multiplexed DLCI record number.
0 – 62 – Specifies the EDLCI number.
Primary Destination Link
Possible Settings: Net1-FR1, ISDN Link Name
Specifies the frame relay interface used as the primary destination link; the to end of a
interfaces that have at least one DLCI or EDLCI defined which are not part of a PVC
connection or management link. For example, if the network interface has no DLCIs
defined, Net1-FR1 would not appear as a valid setting.
Net1-FR1 – Specifies the Network interface as the destination link.
ISDN Link Name – Specifies the ISDN link of the DBM as the destination of the
connection. This can be any nonnull link name configured on an ISDN frame relay link
on an installed DBM.
Primary Destination DLCI
Specifies the primary destination DLCI for a frame relay interface. The DLCI must be
defined and cannot be part of a PVC connection or management link. For multiplexed
DLCIs, at least one EDLCI must be unconnected for the DLCI to be a valid selection.
NOTE:
Primary Destination DLCI has no value if Primary Destination Link contains
no value.
8-54
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Primary Destination EDLCI
Specifies the primary destination Embedded Data Link Connection Identifier (EDLCI) for
a frame relay interface when a multiplexed DLCI record is selected as one end of a
connection.
Display Conditions – This option only appears when the Primary Destination DLCI
contains a multiplexed DLCI record number.
Alternate Destination Link
Specifies the frame relay interface used as the alternate destination link; the to end of a
from-to link that is used for backup when the primary destination link or DLCI is out of
service. The only valid settings for this configuration option are frame relay interfaces
that have at least one DLCI or EDLCI defined which are not part of a PVC connection or
management link. For example, if ISDN Link Name has no DLCIs defined, the ISDN link
name would not appear as a valid setting.
connection. This can be any non-null link name configured on an ISDN frame relay link
on an installed DBM.
Clear Alternate – Clears the Alternate Destination Link and Alternate Destination DLCI
settings, and suppresses Alternate Destination EDLCI.
Alternate Destination DLCI
Specifies the alternate destination Data Link Connection Identifier (DLCI) for a frame
relay interface used for backup. The DLCI must be defined and cannot be part of a PVC
connection or management link. For multiplexed DLCIs, at least one EDLCI must be
unconnected for the DLCI to be a valid selection.
Display Conditions – This option does not appear when the Alternate Destination Link
contains no value.
Alternate Destination EDLCI
Specifies the alternate destination Embedded Data Link Connection Identifier (EDLCI)
for a frame relay interface when a multiplexed DLCI record is selected as one end of a
backup connection.
Display Conditions – This option only appears when the Alternate Destination DLCI
9191-A2-GH30-00
DRAFT — June 1999
8-55
Configuration
Setting Up Management and Communication Options
Select Management and Communication to display the Management and
Communications Options menu. The following Management and Communication
Options can be selected from the menu:
H
Node IP Options on page 8-11.
H
Management PVC Options on page 8-60.
H
General SNMP Management Options on page 8-13.
H
Telnet and FTP Sessions Options on page 8-14.
H
SNMP NMS Security Options on page 8-15.
H
SNMP Traps and Trap Dial-Out Options on page 8-68.
H
Communication Port Options on page 8-17.
H
Modem Port Options on page 8-77.
Configuring Node IP Information
Select Node IP to display, add, or change the information necessary to support
general IP communications for the node (see Table 8-11).
Main Menu → Configuration → Management and Communication → Node IP
In addition to the Node IP communication information (Node IP Address, Node
Subnet Mask, and Default IP Destination), the FrameSaver 9626 provides a
Troubleshooting (TS) Management Link feature to help service providers isolate
device problems within their networks (see Table 8-11).
Troubleshooting Management Link Feature
The Troubleshooting (TS) Management feature allows Telnet or FTP access to
the unit on this link. Troubleshooting over this link is essentially transparent to
customer operations. No alarms or SNMP traps are generated to create nuisance
alarms for the customer.
TS_Management_Link is initially disabled, but the link can be enabled at any
time. Any valid network Management PVC created on a standard DLCI can be
used. A troubleshooting link can be enabled any time the service provider
requests access. An assigned security level can also control access.
When a DLCI has been defined as the troubleshooting management link, the
link is identified in the status field at the bottom of the Management PVC Entry
screen with the This PVC has been designated as the TS
Management Link message.
NOTE:
The unit may come from the factory with a TS Management PVC already
set up (eg., 980).
8-56
DRAFT — June 1999
9191-A2-GH30-00
Configuration
The following configuration options are included in the unit’s Node IP information
to support this feature (see Table 8-11). See Troubleshooting Management Link
Feature in Chapter 13, Troubleshooting, for additional information. See
Configuring the Communications Protocol in the User’s Guide for descriptions of
the Node IP Address, Node Subnet Mask, and Default IP Destination options.
Table 8-11. Node IP Options (1 of 3)
Node IP Address
Possible Settings: 001.000.000.000 – 223.255.255.255, Clear
Default Setting: Clear (000.000.000.000)
Specifies the IP address needed to access the node. Since an IP address is not bound
to a particular port, it can be used for remote access via a management PVC.
001.000.000.000 – 223.255.255.255 – Shows the IP address for the node, which can be
viewed or edited.
Clear – Fills the node IP address with zeros.
Node Subnet Mask
Default Setting: 000.000.000.000
Specifies the subnet mask needed to access the node. Since the subnet mask is not
bound to a particular port, it can be used for remote access via a management PVC.
000.000.000.000 – 255.255.255.255 – Shows the subnet mask for the node, which can
be viewed or edited.
Clear – Fills the node subnet mask with zeros. When the node’s subnet mask is
all zeros, the IP protocol creates a default subnet mask based upon the class of the
IP address: Class A: 255.000.000.000, Class B: 255.255.000.000, or Class C:
255.255.255.000.
9191-A2-GH30-00
DRAFT — June 1999
8-57
Configuration
Default IP Destination
Possible Settings: None, Modem, COM, PVCname
Default Setting: None
Specifies a default IP destination so that data without a specifically defined PVC will
have a route. Examples: If the default IP network is connected to the communications
port, you would select COM. If the default IP network is connected to a far-end device
over the management PVC named Tpa (as defined by the Name configuration option
(see Table NO TAG, Management PVCs Options), you would select the PVC name Tpa.
NOTE:
If the link to the IP destination selected as the default route becomes
disabled or down, the unrouteable data will be discarded. Make sure that
the link selected is operational, and if that link goes down, change the
default destination.
CAUTION: Use care when configuring a default route to an interface that has a
subnet route configured at a remote end where the NMS, router, LAN
adapter, terminal server, etc. is connected. Communicating with an
unknown IP address on the subnet will cause temporary routing loops,
which will last 16 iterations times the retry count.
None – No default network destination is specified. Unrouteable data will be discarded.
This is the recommended setting.
COM – Specifies the COM port as the default destination. This selection only appears
when Port Use is set to Net Link (see Table 8-17, Communication Port Options).
Modem – Specifies the Modem port as the default destination. This selection only
appears when Modem Port Use is set to Net Link (see Table8-18, Modem Port Options).
PVCname – Specifies a name for the management PVC. This selection only appears
when a management PVC name is defined for the node. For example, when the
network is connected to a remote device located in Tampa, Tpa can be specified as the
PVC name, which is the link between the local NextEDGE system and the one located
in Tampa. PVCTpa would appear as one of the available selections.
TS Management Link
Available Settings: None, PVCname
Specifies a troubleshooting management link for the special needs of network service
providers.
If the option is changed from a management PVC name to None, the Delete the
Management PVC PVCname and the associated DLCI Record? prompt
appears. If you select:
H No – The link designation is removed and the option is set to None.
H Yes – The link designation is removed and the option is set to None. In addition,
the link and its DLCI will be deleted.
None – Disables or does not specify a TS Management Link.
PVCname – Specifies the name of the TS Management PVC.
Display Conditions – This selection only appears when a dedicated Management
PVC has been defined on the network frame relay link as a DLCI with DLCI Type set
to Standard.
8-58
DRAFT — June 1999
9191-A2-GH30-00
Configuration
TS Management Link Access Level
Available Settings: Level-1, Level-2, Level-3
Default Setting: Level-1
Specifies the highest access level allowed when accessing the unit via a Telnet or FTP
session when the service provider is using the TS Management Link.
Display Conditions – This option does not appear when TS Management Link is set
to None.
NOTES: Telnet and FTP sessions on this link are not affected by the access level
set by the Session Access Level, Login Required, or FTP Login Required
option settings (see the Telnet and FTP Sessions options).
Telnet and FTP sessions on this link are affected by the Telnet Session,
Inactivity Timeout, Disconnect Time and FTP Session option settings.
Level-1 – Allows Telnet or FTP access by network service providers with the capability
to view unit information, change configuration options, and run tests. This is the highest
access level allowed. Use this setting to allow downloading of software files.
Level-2 – Allows Telnet or FTP access by network service providers with the capability
to view unit information and run tests only; they cannot change configuration options.
Level-3 – Allows Telnet access by network service providers with the capability to view
unit information only; they cannot change configuration options or run tests.
Configuring Management PVCs
Select Management PVCs to define inband management links by adding or
changing Management PVCs (see Table 8-12). First, DLCI records must have
been configured for the interface where the Management PVC will reside. See
Configuring DLCI Records for Each Interface on page 8-48.
" Procedure
Management PVCs
2. Select New or M o dify to add or change DLCI and EDLCI Management
PVCs. When you select New, the configuration option field is blank. When
you select Modify, the values displayed for all fields are based on the PVC ID
that you specified.
9191-A2-GH30-00
DRAFT — June 1999
8-59
Configuration
Table 8-12. Management PVC Options (1 of 4)
Name
Possible Settings: ASCII text entry
Specifies a unique name for the management PVC as referenced on screens
(e.g., Tpa for Tampa, Florida ).
ASCII text entry – Up to 8 ASCII characters can be entered or edited. Make sure the
name you enter is unique to this management PVC.
Intf IP Address
Possible Settings: Node-IP-Address, Special (nnn.nnn.nnn.nnn)
Default Setting: Node-IP-Address
Specifies the IP address used to access the unit via this management PVC. This
provides connectivity to an external IP network through the frame relay network.
Node-IP-Address – Uses the IP address contained in the Node IP Address (see
Table 8-11, Node IP Options).
Special (001.000.000.000 – 223.255.255.255) – Allows you to display/edit an IP
address for the system’s management PVC when the IP address for this interface is
different from the node’s IP address.
Intf Subnet Mask
Possible Settings: Node-Subnet-Mask, Calculate, Special (nnn.nnn.nnn.nnn)
Default Setting: Node-Subnet-Mask
Specifies the subnet mask needed to access the unit when the management PVC is
providing connectivity to an external IP network (through frame relay) that requires a
specific subnet mask for the interface.
Node-Subnet-Mask – Uses the Interface IP Subnet contained in the Node-Subnet
Mask configuration option (see Table 8-11, Node IP Options).
Calculate – Calculates the subnet mask created by the IP protocol based on the class
of the IP address (Class A: 255.000.000.000, Class B: 255.255.000.000, or
Class C: 255.255.255.000). Cannot be displayed or edited.
Special (000.000.000.000 – 255.255.255.255) – Allows you to edit/display the subnet
mask for the management PVC when the subnet mask is different for this interface. A
text field displays where you can enter the subnet mask for this unit’s management
PVC.
Set DE
Specifies whether frames (packets) sent on a management PVC have the Discard
Eligible (DE) bit set. This bit is used by the network to prioritize which frames to discard
first during periods of network congestion. This allows management traffic to be viewed
as lower priority than user data.
Enable – Sets the DE bit to one on all frames sent on the management PVC.
Disable – Sets the DE bit to zero on all frames sent on the management PVC. This is
the recommended setting, particularly for NSPs providing a managed network service.
8-60
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Primary Link
Possible Settings: Net1-FR1, SsPort-n, ISDN Link Name, Clear
Specifies the frame relay interface to use for this management PVC. The interface
selected must have at least one DLCI (or DLCI with EDLCI) defined, which is not part of
a PVC connection or already assigned as a management PVC.
Net1-FR1 – Specifies the network interface as the source link for the connection.
SsPort-n – Specifies the frame relay link on Slot s, Port n as the destination link for the
connection.
ISDN Link Name – Specifies the ISDN link on the DBM to be used in the connection.
This can be any non-null link name configured on an ISDN frame relay link on an
installed DBM.
Clear – Clears the link and the DLCI field, and suppresses the EDLCI field if the DLCI
was multiplexed.
Primary DLCI
Specifies the DLCI number used for the management PVC after the frame relay
interface is selected.
The DLCI must be defined for the link (i.e., has a DLCI record), and it must not be part
of a PVC connection or already assigned as a management PVC. For multiplexed
DLCIs, at least one EDLCI must be unconfigured for the DLCI.
NOTES: – DLCI cannot be entered if the Link field is blank.
– Clearing Link also clears the DLCI.
Primary EDLCI
Specifies the EDLCI number used for a management PVC when a multiplexed DLCI is
selected. EDLCIs identify individual connections within multiplexed DLCIs that are
unique to those DLCIs.
Use a unique EDLCI to identify an individual connection within a multiplexed DLCI.
Use 0 to identify the primary EDLCI. Use 1 – 62 to identify secondary EDLCIs. Use the
primary EDLCI for user data, which has a higher utilization rate than management data,
with slightly less line overhead.
Display Conditions – This option does not appear when the DLCI does not reference
a multiplexed DLCI.
NOTE:
Clearing the DLCI or changing it to a standard DLCI suppresses EDLCI
field.
9191-A2-GH30-00
DRAFT — June 1999
8-61
Configuration
Primary Link RIP
Possible Settings: None, Proprietary, Standard_out
Default Setting:
Multiplexed DLCIs: Proprietary
Nonmultiplexed DLCIs: Standard_out
Specifies which Routing Information Protocol (RIP) is used to enable routing of
management between NextEDGE frame systems, FrameSaver units, and attached
equipment.
None – Does not use a routing protocol.
Proprietary – Uses a proprietary variant of RIP version 1 to communicate routing
information between NextEDGE and/or FrameSaver units. A NextEDGE or FrameSaver
unit must be on the other end of the link. This is the factory default for management
PVCs configured on multiplexed DLCIs (see Table 8-9, DLCI Records Options).
Standard_out – The device will send standard RIP messages to communicate routing
information only about other NextEDGE or FrameSaver SLV units in the network. This is
the factory default for management PVCs configured on standard DLCIs.
Alternate Link
Possible Settings: Net1-FR1, ISDN Link Name, Clear
Specifies the frame relay interface to use for this management PVC as the alternate
link. The interface selected must have at least one DLCI (or DLCI with EDLCI) defined,
which is not part of a PVC connection or already assigned as a management PVC.
Net1-FR1 – Specifies the Network interface as the frame relay link.
ISDN Link Name – Specifies the ISDN link of the DBM to be used in the connection.
installed DBM.
was multiplexed.
Alternate DLCI
Specifies the alternate DLCI number to be used for the management PVC after the
frame relay interface is selected.
Display Conditions – The DLCI cannot be entered if the Link field is blank.
NOTE:
8-62
Clearing Link also clears the DLCI.
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Alternate EDLCI
Specifies the alternate EDLCI number used for a management PVC when a multiplexed
DLCI is selected for the frame relay link. EDLCIs identify individual connections within
multiplexed DLCIs that are unique to those DLCIs.
Display Conditions – This option does not appear if the DLCI does not reference a
multiplexed DLCI.
NOTE:
Clearing the DLCI or changing it to a standard DLCI suppresses EDLCI
field.
Configuring General SNMP Management
Select General SNMP Management (see Table 8-13) to add, change, or delete
the information needed to allow the unit to be managed as an SNMP agent by the
NMS supporting the SNMP protocols.
Table 8-13. General SNMP Management Options (1 of 2)
SNMP Management
Determines whether the unit can be managed by an SNMP-compatible NMS.
Enable – Allows the system to be managed as an SNMP agent.
Disable – The system cannot be managed as an SNMP agent. The unit will not
respond to SNMP messages or send SNMP traps.
Community Name 1
Possible Settings: ASCII text entry, Clear
Default Setting: Public in ASCII text field
Specifies the first of two names that can be used to access the objects in the system’s
MIB. The community name must be supplied by an external SNMP manager when the
manager tries to access an object in the MIB.
ASCII text entry – Up to 255 ASCII characters can be entered or edited.
Clear – Clears Community Name 1.
9191-A2-GH30-00
DRAFT — June 1999
8-63
Configuration
Table 8-13. General SNMP Management Options (2 of 2)
Name 1 Access
Possible Settings: Read, Read/Write
Default Setting: Read
Specifies the type of access allowed to the objects in the MIB using Community
Name 1. This is the type of access allowed for external SNMP managers accessing MIB
objects using Community Name 1.
Read – Allows read-only access (SNMP Get command). This includes all objects
specified as either read-only or read/write in the MIB RFCs.
Read/Write – Allows read and write access (SNMP Get and Set commands).
Community Name 2
Default Setting: Clear
Specifies a second name that can be used to access the objects in the NextEDGE
unit’s MIB. The community name must be supplied by an external SNMP manager
when the manager tries to access an object in the MIB.
ASCII text entry – Up to 255 ASCII characters can be entered or edited.
Clear – Clears Community Name 2.
Name 2 Access
Specifies the type of access allowed when external SNMP managers access MIB
objects using Community Name 2.
Read – Allows read-only access (SNMP get command). This includes all objects
specified as either read-only or read/write in the MIB RFCs.
Read/Write – Allows read and write access (SNMP get and set commands).
Configuring Telnet and/or FTP Session Support
Select Telnet and FTP Session to enable or disable access via Telnet or FTP (File
Transport Protocol) sessions. Telnet or FTP configuration options control whether
a Telnet or FTP session is allowed through an interconnected IP network and the
access security applicable to the session (see Table 8-14). Two Telnet sessions
can be active at a time.
Telnet and FTP Session
When a TS Management Link has been set up and activated (see page 8-56),
the following options have no effect upon the PVC:
8-64
H
Telnet Login Required
H
Session Access Level
H
FTP Login Required
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Table 8-14. Telnet and FTP Session Options (1 of 2)
Telnet Session
Specifies whether the system will respond to a session request from a Telnet client on
an interconnected IP network.
Enable – Allows Telnet sessions between the system and Telnet client.
Disable – Does not allow Telnet sessions.
Telnet Login Required
Specifies whether a user ID and password (referred to as the login) are required to
access the menu-driven user interface via a Telnet session. If required, the login used is
the same login used for an menu-driven user interface session. This option does not
affect the TS Management Link.
Enable – Requires a login to access a Telnet session.
Disable – Does not require a login.
Session Access Level
Possible Settings: Level-1, Level-2, Level-3
Specifies the highest security level allowed when accessing the menu-driven user
interface via a Telnet session. If a login is required for the session, the effective access
level is also determined by the user’s access level. When a login is not required, the
effective access level is determined by this option. This option does not affect the TS
Management Link.
NOTE:
The effective access level is always the lowest one assigned to either the
session or the user. For example, if the assigned Session Access Level is
Level-2, but the User Access Level is Level-3, then only level-3 access is
allowed for the session.
Level-1 – Allows Telnet access by users with Login ID access levels of 1, 2, and 3, with
the capability to view system information, change configuration options, and run tests.
This is the highest access level allowed.
CAUTION: Before changing the session access level to Level-2 or 3, make sure that
the COM port’s Port Access Level is set to Level-1 and that at least one
Login ID is set to Level-1. Otherwise, access will be lost. If this occurs,
you must reset the unit to the factory defaults and begin the
configuration process again. A reset is required if the Communication
Port’s Port Use option is set to Net Link (see Table 8-3, General
Options).
the capability to view system information and run tests only; they cannot change
configuration options.
the capability to view system information only; they cannot change configuration options
or run tests.
9191-A2-GH30-00
DRAFT — June 1999
8-65
Configuration
Table 8-14. Telnet and FTP Session Options (2 of 2)
Inactivity Timeout
Determines whether a Telnet session is disconnected after a specified period of
keyboard inactivity.
NOTE:
Changing this setting does not affect the current session; it changes all
subsequent sessions.
Enable – Terminates the session after the Disconnect Time expires.
Disable – Does not terminate Telnet session during inactivity.
Disconnect Time (Minutes)
Default Setting: 10
Sets the amount of keyboard inactive time allowed before a user session is
disconnected.
Display Conditions – This option does not appear when Inactivity Timeout is disabled.
NOTE:
1 – 60 – Up to an hour can be set.
FTP Session
Determines whether the system responds as a server when an FTP (file transfer
protocol) client on an interconnected IP network requests an FTP session. This option
must be enabled when downloading files.
Enable – Allows an FTP session between the system and an FTP client.
Disable – Does not allow FTP sessions.
FTP Login Required
Specifies whether a login ID and password are required for an FTP session. If required,
the login used is the same login used for a menu-driven user interface session. This
option does not affect the TS Management Link.
Enable – User is prompted for a login ID and password.
Disable – No login is required for an FTP session.
FTP Max Receive Rate (kbps)
Sets the maximum receive rate of file transfer to the system. This option allows new
software and configuration files to be downloaded using selected bandwidth without
interfering with normal operation. Using this option, new software and configuration files
can be downloaded quickly using the default settings, or at a slower rate over an
extended period of time by selecting a slower speed. Based upon TCP flow control, the
FTP server in the system throttles bandwidth to match this setting.
1 – 1536 – Sets the download line speed from 1 kilobits per second to the full network
line speed.
8-66
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Configuring SNMP NMS Security
Select SNMP NMS Security to display, add, or change the SNMP security
configuration options for the unit see Table 8-15). A table is displayed consisting
of the network management systems identified by IP address that are allowed to
access the system by SNMP.
SNMP NMS Security
Table 8-15. SNMP NMS Security Options (1 of 2)
NMS IP Validation
Specifies whether security checks are performed on the IP address of SNMP
management systems attempting to access the node. Only allows access when the
sending manager’s IP address is listed on the SNMP NMS Security Options screen.
Enable – Performs security checks.
Disable – Does not perform security checks.
Number of Managers
Default Setting: 1
Specifies the number of SNMP management systems that are authorized to send
SNMP messages to the system. An IP address must be configured for each
management system allowed to send messages. Configure IP addresses in the NMS n
IP Address configuration option.
1 – 10 – Specifies the number of authorized SNMP managers.
NMS n IP Address
Provides the IP address of an SNMP manager that is authorized to send SNMP
messages to the system. If an SNMP message is received from an unauthorized NMS
and its IP address cannot be matched here, access is denied and an
authenticationFailure trap is generated. If a match is found, the type of access
(read-only or read/write) is determined by the corresponding Access Type..
Display Conditions – This option appears for each trap manager specified in the
Number of Trap Managers configuration option.
001.000.000.000 – 223.255.255.255 – Adds to or changes the NMS IP address.
Clear – Fills the NMS IP address with zeros.
9191-A2-GH30-00
DRAFT — June 1999
8-67
Configuration
Table 8-15. SNMP NMS Security Options (2 of 2)
Access Type
Specifies the type of access allowed for an authorized NMS when IP address validation
is performed.
Read – Allows read-only access (SNMP get command) to the MIB objects. This
includes all objects specified as either read-only or read/write in the MIB RFCs.
Read/Write – Allows read and write access (SNMP get and set commands) to the MIB
objects. However, access for all read-only objects is specified as read-only.
Configuring SNMP Traps and Trap Dial-Out
Select SNMP Traps to display, add, or change the information necessary to send
SNMP traps and select the traps that will be sent (see Table 8-16).
SNMP Traps
See Appendix C, SNMP MIBs and Traps, and RMON Alarm Defaults, for trap
format standards and special trap features, including the default settings that will
generate RMON-specific SNMP traps.
Table 8-16. SNMP Traps and Trap Dial-Out Options (1 of 5)
SNMP Traps
Determines whether the system sends trap messages to the currently configured SNMP
trap manager(s).
Enable – Sends trap messages.
Disable – Does not send trap messages.
Number of Trap Managers
Default Setting: 1
Specifies the number of SNMP management systems that will receive SNMP trap
messages from the system. An NMS IP Address must be configured in the NMS n IP
Address configuration option for each trap manager to receive trap messages.
1 – 6 – Specifies the number of trap managers.
8-68
DRAFT — June 1999
9191-A2-GH30-00
Configuration
NMS n IP Address
Specifies the IP address of the SNMP manager(s) to receive SNMP traps.
001.000.000.000 – 223.255.255.255 – Adds to or changes the IP address for the trap
manager.
Clear – Fills the NMS IP address with zeros.
Destination
Possible Settings: Default, Modem, COM, PVCname
Default Setting: Default
Specifies the interface over which SNMP traps will be sent.
Default – Uses the default network.
COM – Uses the COM port. This selection is only available when Communication Port
Use is set to Net Link (see Table 8-17, Communication Port Options).
Modem – Uses the Modem port. This selection only appears if Modem Port Use is set
to Net Link (see Table 8-18, Modem Port Options).
PVCname – Uses the defined management linkname (the name given the Management
PVC). This selection only appears when at least one Management PVC is defined for
the node.
General Traps
Possible Settings: Disable, Warm, AuthFail, Both
Determines whether SNMP trap messages for warmStart and/or authenticationFailure
events are sent to the currently configured trap manager(s).
Disable – Does not send trap messages for these events.
Warm – Sends trap messages for warmStart events only.
AuthFail – Sends trap messages for authenticationFailure events only.
Both – Sends trap messages for both warmStart and authenticationFailure events.
Enterprise Specific Traps
Determines whether trap messages for enterpriseSpecific events are sent to the
currently configured trap manager(s).
Enable – Sends trap messages for enterpriseSpecific events.
Disable – Does not send trap messages for enterpriseSpecific events.
9191-A2-GH30-00
DRAFT — June 1999
8-69
Configuration
Link Traps
Possible Settings: Disable, Up, Down, Both
Determines whether SNMP linkDown or linkUp traps are sent to the currently configured
trap manager(s). A linkDown trap indicates that the system recognizes a failure in one
of the interfaces. A linkUp trap indicates that the system recognizes that one of its
interfaces is active.
Use the Link Traps Interface and the DLCI Traps on Interface configuration options to
specify which interface will monitor linkUp and linkDown traps messages.
Disable – Does not send these trap messages.
Up – Sends trap messages for linkUp events only.
Down – Sends trap messages for linkDown events only.
Both – Sends trap messages for linkUp and linkDown events.
Link Traps Interfaces
Possible Settings: Network, DSX-1, T1s, Ports, DBM, OCU, All
Default Setting: All
Specifies which interfaces will generate linkUp, linkDown, and enterpriseSpecific trap
messages. These traps are not supported on the COM or Modem port.
Network – Generates these trap messages on the T1 Network interface only.
DSX-1 – Generates these trap messages on the DSX-1 interface only.
T1s – Generates these trap messages on the T1 Network and DSX-1 interfaces only.
Ports – Generates these trap messages on user data ports only.
DBM – Generates these trap messages on the DBM interface only.
OCU – Generates these trap messages on the OCU interface only.
All – Generates these trap messages on all frame relay interfaces.
DLCI Traps on Interfaces
Possible Settings: Network, Ports, DBM, All
Default Setting: All
Specifies which interfaces will generate linkUp and linkDown trap messages for
individual DLCIs. These traps are only supported on the frame relay interfaces.
Network – Generates these trap messages for DLCIs on the network interface only.
Ports – Generates these trap messages for DLCIs on user data ports only.
DBM – Generates these trap messages for DLCIs on the DBM only.
All – Generates these trap messages on all frame relay interfaces.
RMON Traps
Specifies whether remote monitoring traps are sent to the currently configured trap
manager(s). RMON traps are typically sent as a result of the Alarms and Events Groups
of RMON1 when a selected variable’s configured threshold is exceeded.
Enable – Sends trap messages when set thresholds are exceeded.
Disable – Does not send trap messages when set thresholds are exceeded.
8-70
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Trap Dial-Out
Controls whether alarm or SNMP trap messages automatically initiate a call. If the call
cannot be completed and the Call Retry option is set to Enable, the SNMP trap
message is held (queued) until the call completes to either the Alarm or alternate
directory.
NOTE:
For traps, when Modem port is configured as a network communication
link, up to ten SNMP trap messages are held at the modem interface (see
Port Use set to Net Link, see Table 8-18, Modem Port Options).
Enable – Automatically calls the phone number contained in the Control menu’s Modem
Call Directories, Directory Number A (Alarm).
Disable – For traps, where the modem has not completed the connection, holds the
messages.
Trap Disconnect
Determines whether the modem disconnects after an SNMP trap message has been
sent. This configuration option only applies to modem connections initiated as a result of
sending the SNMP trap message.
Enable – Disconnects the call after sending an SNMP trap message(s).
Disable – The modem connection remains active to facilitate troubleshooting. The line
remains open until it is manually disconnected from the remote modem or from the
Disconnect Modem selection on the Control menu.
Call Retry
Controls whether an incomplete call (busy, no answer, etc.) is retried when an SNMP
trap message is sent to the Modem interface.
Enable – Attempts to retry the call, up to one time per SNMP trap message, with a
delay between the retry. The delay is specified by the Dial-Out Delay Time (Min)
configuration option.
If an Alternate Dial-Out Directory is specified, the alarm directory’s telephone number is
called first. If the call cannot be completed, then the alternate directory’s telephone
number is called (see the Control menu’s Modem Call Directories).
Disable – Does not retry an incomplete call.
Dial-Out Delay TIme (Min)
Default Setting: 5
Specifies the amount of time between call retries when an SNMP trap message is sent;
the wait between call attempts (see Call Retry).
1 – 10 – Allows up to ten minutes.
9191-A2-GH30-00
DRAFT — June 1999
8-71
Configuration
Alternate Dial-Out Directory
Possible Settings: None, 1 – 5
Specifies whether an incomplete call (busy, or no answer, etc.) resulting from an attempt
to send an SNMP trap message is retried using an alternate telephone number. Up to
five alternate call directories can be set up, but can only be used one at a time.
When Call Retry is enabled, the alarm directory’s telephone number is called first. If the
call cannot be completed after one additional try, then the specified alternate directory’s
telephone number is called.
None – Does not dial-out using one of the alternate directory telephone numbers.
1 – 5 – Specifies the call directory containing the telephone number to call if a call
cannot be completed using the telephone number in the alarm directory (Directory
Number A in the Control menu’s Modem Call Directories).
Configuring the Communication Port
Select Communication Port to display or change the communication port
configuration options (see Table 8-17).
Communication Port
Table 8-17. Communication Port Options (1 of 5)
Port Use
Possible Settings: Terminal, Net Link
Default Setting: Terminal
Assigns a specific use to the COM port.
NOTE:
If the Default IP Destination is set to COM (see Table 8-11, Node IP
Options) and you change Port Use to Terminal, the Default IP Destination
is forced to None.
Terminal – The COM port is used for a direct connection to an asynchronous terminal.
Net Link – The COM port is the network communications link to the IP network or
IP device port.
Data Rate (Kbps)
Possible Settings: 9.6, 14.4, 19.2, 28.8, 38.4, 57.6, 115.2
Specifies the rate for the COM port in kilobits per second.
9.6 – 115.2 kbps
8-72
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Character Length
Default Setting: 8
Specifies the number of bits needed to represent one character.
NOTE:
Character length defaults to 8 and cannot be changed when Port Use is
set to Net Link.
7 – Sets the character length to seven bits.
8 – Sets the character length to eight bits. Use this setting when the COM port is used
as the network communication link.
Parity
Possible Settings: None, Even, Odd
Provides a method of checking the accuracy of binary numbers for the COM port. A
parity bit is added to the data to make the “1” bits of each character add up to either an
odd or even number. Each character of transmitted data is approved as error-free if the
“1” bits add up to an odd or even number.
None – Provides no parity.
Even – Makes the sum of all 1 bits and its corresponding parity bit always even.
Odd – Makes the sum of all 1 bits and its corresponding parity bit always odd.
Stop Bits
Default Setting: 1
Determines the number of stop bits used for the COM port.
1 – Provides one stop bit.
2 – Provides two stop bits.
Ignore Control Leads
Possible Settings: Disable, DTR
Specifies whether DTR is used.
Disable – Treats control leads as standard operation.
DTR – Ignores DTR. This may be necessary when connecting to some PAD devices.
9191-A2-GH30-00
DRAFT — June 1999
8-73
Configuration
Login Required
Determines whether a user login ID and password (referred to as the login) is required to
access the unit using an asynchronous terminal connected to the COM port.
Display Conditions – This option only appears when Port Use is set to Terminal.
Enable – Requires a login to access the menu-driven user interface.
Disable – Does not requires a login.
Port Access Level
Specifies level of user access privilege for an asynchronous terminal COM port
connection. If a login is required, the effective access level is determined by the user’s
access level. When a login is not required, the effective access level is determined by
this option.
NOTE:
port or the user. For example, if the Port Access Level assigned is Level-2,
but the User Access Level is Level-3, then only level-3 access will be
permitted for the port.
Level-1 – Allows full access and control of the device including monitoring, diagnostics,
and configuration. The user can add, change, and display configuration options, and
perform device testing.
CAUTION: Before changing the communication port’s access level to Level-2 or 3,
make sure that either Telnet Session Access Level or the Modem Port’s
Port Access Level is set top Level-1 and at least one login is set to
Level-1. Otherwise, access will be lost. If this occurs, you must reset the
unit to the factory defaults and begin the configuration process again.
Level-2 – Allows limited access and control of the device. The user can monitor and
perform diagnostics, and display status and configuration option information.
Level-3 – Allows limited access for monitoring puposes. The user can only display and
monitor status and configuration screens.
8-74
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Inactivity Timeout
Determines whether a user session is disconnected after a specified time of inactivity
(no keyboard activity).
NOTE:
Enable – Disconnects the user session after the specified time of inactivity.
Disable – Does not disconnect user session.
Default Setting: 10
Specifies the number of minutes of inactivity that can elapse before the session is
disconnected.
NOTE:
1 – 60 – Allows up to an hour.
IP Address
Specifies a unique IP address for accessing the system via the COM port. Only in effect
when the COM port is configured as a network communication link (Port Use option is
set to Net Link, see Table 8-17).
Display Conditions – This option only appears when Port Use is set to Net Link.
001.000.000.000 – 223.255.255.255 – Shows the IP address for the COM port, which
you can view or edit.
Clear – Clears the IP address for the COM port and fills the address with zeros. When
the IP Address is all zeros, the COM port uses the Node IP Address if one has been
configured.
9191-A2-GH30-00
DRAFT — June 1999
8-75
Configuration
Subnet Mask
Specifies the subnet mask needed to access the unit. Only in effect when the COM port
is configured as a network communication link (Port Use option is set to Net Link, see
Table 8-17, Communication Port Options).
000.000.000.000 – 255.255.255.255 – Shows the subnet mask for the COM port, which
Clear – Clears the subnet mask for the COM port and fills the address with zeros. When
the node subnet mask is all zeros, the IP protocol creates a default subnet mask based
upon the class of the IP address: Class A: 255.000.000.000, Class B: 255.255.000.000,
or Class C: 255.255.255.000.
Link Protocol
Possible Settings: PPP, SLIP
Default Setting: PPP
Specifies the link-layer protocol to be used. This option is only in effect when the COM
port is configured as a network communication link (Port Use option is set to Net Link,
see Table 8-17, Communication Port Options).
PPP – Point-to-Point Protocol.
SLIP – Serial-Line Internet Protocol.
RIP
management data between devices.
None – No routing is used.
Proprietary – A proprietary variant of RIP version 1 is used to communicate routing
information only between devices to enable routing of IP traffic.
Standard_out – The device will respond to standard RIP requests to communicate
routing information about other NextEDGE and FrameSaver units in the network.
NOTE:
8-76
The router must be configured to receive RIP on the port connected to the
COM port, configured as the management interface (e.g., Cisco: config-t,
router RIP, int serialx, IP RIP Receive version 1, ctl-z WR).
To create this management interface, make sure that Node or COM port IP
Information has been set up (see Configuring Node IP Information on
page 8-11).
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Configuring the Modem Port
If you have a FrameSaver NAM, the NAM is equipped with an internal modem.
Select Modem Port (see Table 8-18) to set up the modem for management and
SNMP trap dial-out.
Modem Port
Table 8-18. Modem Port Options (1 of 4)
Port Use
Possible Settings: Terminal, Net Link
Default Setting: Terminal
Assigns a specific use to the Modem port.
NOTE:
If the Default IP Destination is set to Modem (see Table 8-11, Node IP
Options) and you change Port Use to Terminal, the Default IP Destination is
forced to None.
Terminal – The Modem port is used for the asynchronous terminal connection.
Net Link – The Modem port is a network communications link to the IP network or
IP device port.
Dial-In Access
Controls whether external devices can dial-in to the system through the internal modem.
This allows dial-in access by a remote terminal when Port Use is set to Terminal. When
Port Use is set to Net Link, Dial-In Access must be set to Enable to allow an external
NMS to dial in to the device.
Enable – Dial-in access is allowed. Incoming calls are answered.
Disable – Dial-in access is not allowed. Incoming calls are not answered.
Login Required
Determines whether a user ID and password (referred to as the login) is required in
order to log on to the asynchronous terminal connected to the Modem port.
Enable – Requires a login to access the menu-driven user interface.
Disable – Does not require a login.
9191-A2-GH30-00
DRAFT — June 1999
8-77
Configuration
Port Access Level
Specifies the level of user access privilege for an asynchronous terminal connected to
the Modem port.
NOTE:
port or the user. For example, if the Port Access Level assigned is Level-2,
but the User Access Level is Level-3, then only level-3 access will be
permitted for the modem port.
Level-1 – Allows full access and control of the device including monitoring, diagnostics,
and configuration. The user can add, change, and display configuration options, save,
and perform device testing. If Login Required is set to Enable, the effective access level
is determined by the user’s access level. Otherwise, the access level is 1.
CAUTION: Before changing the modem port’s access level to Level-2 or 3, make
sure that either Telnet Session Access Level or the communications
port’s Port Access Level is set to Level-1 and at least one Login ID are
set to Level-1. Otherwise, access will be lost. If this occurs, you must
reset the unit to the factory defaults and begin the configuration process
again.
Level-2 – Allows limited access and control of the device. The user can monitor and
perform diagnostics, display status and configuration option information. If Login
Required is set to Enable, the effective access level is 2 for User ID access levels of 1
or 2. User Ids set to access level 3 have only level 3 access.
Level-3 – Allows limited access with monitoring control only. The user can only display
and monitor status and configuration screens. If Login Required is set to Enable, the
effective access level is 3 for all user IDs.
Inactivity Timeout
Determines whether a user session is disconnected after a specified time of inactivity
(no keyboard activity).
NOTE:
Enable – Disconnects the user session after the specified time of inactivity.
Disable – Does not disconnect the user session.
8-78
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Default Setting: 10
Determines the amount of lapsed time before disconnecting a user session in minutes.
Display Conditions – This option only appears when:
H Port Use is set to Terminal.
H Inactivity Timeout is set to Enable.
NOTE:
1 – 60 – Sets the number of minutes allowed before the modem disconnects.
IP Address
Specifies a unique IP address for accessing the system via the Modem port. This option
is only in effect when the Modem port is configured as a network communication link
(Port Use is set to Net Link, see page 8-77).
001.000.000.000 – 223.255.255.255 – Shows the IP address for the Modem port, which
Clear – Clears the IP address for the Modem port and fills the address with zeros
( i.e., 000.000.000.000 ). When the IP Address is all zeros, the Modem Port uses the
Node IP Address if one has been configured.
Subnet Mask
Specifies the subnet mask needed to access the system. This option is only in effect
when the Modem port is configured as a network communication link (Port Use is set to
Net Link, see page 8-77).
000.000.000.000 – 255.255.255.255 – Shows the subnet mask for the Modem port,
which you can view or edit.
Clear – Clears the subnet mask for the COM port and fills the address with zeros. When
the node subnet mask is all zeros, the IP protocol creates a default subnet mask based
upon the class of the IP address: Class A: 255.000.000.000, Class B: 255.255.000.000,
or Class C: 255.255.255.000.
9191-A2-GH30-00
DRAFT — June 1999
8-79
Configuration
Link Protocol
Possible Settings: PPP, SLIP
Default Setting: PPP
Specifies the link-layer protocol to be used. This option is only in effect when the Modem
port is configured as a network communication link (Port Use is set to Net Link, see
page 8-77).
PPP – Point-to-Point Protocol.
SLIP – Serial-Line Internet Protocol.
Alternate IP Address
Specifies the alternate IP address for the Modem port. If this configuration option is not
configured (i.e., it is zero), the Modem port’s primary IP address is used when the
alternate telephone directory is used for dial-out traps.
001.000.000.000 – 223.255.255.255 – Shows the modem’s alternate IP address, which
Clear – Clears the alternate IP address for the Modem port and fills the address with
zeros.
Alternate Subnet Mask
Specifies the alternate subnet mask needed to access the unit. Only in effect when the
Modem port is configured as a network communication link (Port Use option is set to Net
Link, see Table 8-18, Modem Port Options).
000.000.000.000 – 255.255.255.255 – Shows the subnet mask for the Modem port,
which you can view or edit.
Clear – Clears the subnet mask for the Modem port and fills the address with zeros.
When the node subnet mask is all zeros, the IP protocol creates a default subnet mask
based upon the class of the IP address: Class A: 255.000.000.000,
Class B: 255.255.000.000, or Class C: 255.255.255.000.
RIP
management data between devices.
None – No routing is used.
Proprietary – A proprietary variant of RIP version 1 is used to communicate routing
information between devices to enable routing of IP traffic.
Standard_out – The device will respond to standard RIP requests to communicate
routing information.
8-80
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Configuring the COM Port to Support an External Modem
If you have a T1 TDM NAM, an an external device like a modem or a PAD can be
connected to the NAM’s COM port. Select External Device (Com Port) to set up
the COM port to support an external device. These options control call
processing for the external device (see Table 8-19).
Configuration → User Interface → External Device (Com Port)
NOTE:
A standard EIA-232 crossover cable is required when connecting an external
modem to the unit’s COM Port so that the communication port’s DTR lead is
connected to the external device’s DSR lead. The communication port’s DTR
lead is monitored for loss of connection. The external device must be
configured to drop DSR when a disconnect occurs, and to ignore DTR.
Table 8-19. External Modem (on Com Port) Options (1 of 3)
External Modem Commands
Possible Settings: Disable, AT
Specifies the type of commands to be sent over the COM port.
Disable – Commands will not be sent over the COM port.
AT – Standard Attention (AT) Commands are sent over the COM port to control the
external device. All AT command strings will end with a carriage return (hex 0x0D) and a
line feed (hex 0x0A).
CAUTION: Do not use this setting if you have an async terminal connected to the
COM port.
Dial-In Access
Controls whether external devices can dial-in to the FrameSaver unit through the COM
port (based on the Port Use option setting).
Display Conditions – This option only appears when External Modem Commands is
set to AT.
Enable – Answers incoming calls and establishes connection to the remote terminal or
IP network.
Disable – Does not answer incoming calls. Refer to the Control Characters table on
page 8-84.
Connect Prefix
Specifies the connect prefix to dial the directory phone number.
disabled.
ASCII text entry – Adds to or changes the connect prefix (maximum 20 characters).
Refer to the Control Characters table on page 8-84.
Clear – Clears the connect prefix. No connect prefix is used.
9191-A2-GH30-00
DRAFT — June 1999
8-81
Configuration
Connect Indication String
Specifies the connect indication string that determines whether a connection is
established. The FrameSaver unit searches the COM port’s receive data stream for the
connect indication string. If not received within 1 minute, the connection times out.
disabled.
ASCII text entry – Adds to or changes the connect indication string (maximum
20 characters). Refer to the Control Characters table on page 8-84.
Clear – Clears Connect Indication String. The COM port’s receive data stream is not
searched and the Carrier Detect (CD) lead is used to determine that a connection has
been established.
Escape Sequence
Specifies the COM port escape sequence used to switch an external device to
command mode before the external device is commanded to disconnect.
disabled.
ASCII text entry – Adds to or changes the escape sequence (maximum 20 characters).
Clear – Clears and sets the escape sequence. No escape sequence is sent out.
Escape Sequence Delay (Sec)
Possible Settings: None, 0.2, 0.4, 0.6, 0.8, 1.0
Specifies the delay before sending the first character of the escape sequence and the
delay after the last character of the escape in seconds. During the delay, no data is sent
from the COM port.
disabled.
None – No COM port escape delay is used.
x.x – The delay ( 0.2, 0.4, 0.6, 0.8, 1.0 seconds) used during the COM port’s escape
sequence. You must configure this delay for there to be a delay greater than or equal to
the escape guard time, which is required by the external device.
Disconnect String
Specifies the command used to disconnect an external device. Refer to the Control
Characters table on page 8-84.
disabled.
ASCII text entry – Adds to or changes the disconnect string (maximum 20 characters).
Clear – Clears Disconnect String.
8-82
DRAFT — June 1999
9191-A2-GH30-00
Configuration
Alternate IP Address
Specifies the Alternate IP Address for the COM port when the alternate phone directory
is used. If this configuration option is not configured (i.e., it is zero), the COM port’s
primary IP Address is used when the alternate telephone directory is used.
This option is only in effect when the COM port is configured as a network
communication link (Port Use is set to Net Link, see Table 8-17, Communication Port
Options).
disabled.
001.000.000.000 – 223.255.255.255 – Shows the COM port’s Alternate IP Address,
which you can view or edit. The first byte (i.e., nnn.255.255.255) can be any number
from 001 through 223, excluding 127. Remaining bytes (i.e., 223.nnn.nnn.nnn) can be
any number from 000 through 255. Leading zeros are required.
Clear – Clears the Alternate IP Address for the COM port and fills the address with
zeros ( i.e., 000.000.000.000 ).
Alternate Subnet Mask
Specifies the Alternate Subnet Mask for the COM port when the alternate phone
directory is used.
This option is only in effect when the COM port is configured as a network
communication link (Port Use is set to Net Link, see Table 8-17, Communication Port
Options).
disabled.
000.000.000.000 – 255.255.255.255 – Shows the subnet mask for the COM port, which
Clear – Clears the subnet mask for the COM port and fills the address with zeros
( i.e., 000.000.000.000 ). When the node subnet mask is all zeros, the IP protocol creates
a default subnet mask based upon the class of the IP address:
Class A: 255.000.000.000, Class B: 255.255.000.000, or Class C: 255.255.255.000.
9191-A2-GH30-00
DRAFT — June 1999
8-83
Configuration
Control Characters
8-84
Sequence
ASCII
Hex
Â or â
SOH
0x01
^B or ^b
STX
0x02
^C or ^c
ETX
0x03
^D or ^d
EOT
0x04
Ê or ê
ENQ
0x05
^F or ^f
ACK
0x06
^G or ^g
BEL
0x07
^H or ^h
BS
0x08
Î or î
HT
0x09
^J or ^j
LF or NL
0x0A
^K or ^k
VT
0x0B
^L or ^l
FF or NP
0x0C
^M or ^m
CR
0x0D
^N or ^n
SO
0x0E
Ô or ô
SI
0x0F
^P or ^p
DLE
0x10
^Q or ^q
DC1
0x11
^R or ^r
DC2
0x12
^S or ^s
DC3
0x13
^T or ^t
DC4
0x14
Û or û
NAK
0x15
^V or ^v
SYN
0x16
^W or ^w
ETB
0x17
^X or ^x
CAN
0x18
^Y or ^y
EM
0x19
^Z or ^z
SUB
0x1A
^{ or ^[
ESC
0x1B
^\ or ^|
FS
0x1C
^] or ^}
GS
0x1D
^^ or ^~
RS
0x1E
^–
US
0x1F
DRAFT — June 1999
9191-A2-GH30-00
Security and Logins
9
This chapter provides information about the following:
H
Limiting Access (see below).
H
Controlling Asynchronous Terminal Access on page 9-2.
H
Controlling Telnet or FTP Access on page 9-4.
— Limiting Telnet Access on page 9-4.
— Limiting FTP Access on page 9-5.
— Limiting Telnet or FTP Access Over the TS Management Link on
page 9-6.
H
Controlling SNMP Access on page 9-7.
— Disabling SNMP Access on page 9-7.
— Assigning SNMP Community Names and Access Levels on page 9-8.
— Limiting SNMP Access Through IP Addresses on page 9-9.
9191-A2-GH30-00
H
Controlling Dial-In Access on page 9-10.
H
Controlling ISDN Access on page 9-11.
H
Creating a Login on page 9-12.
H
Modifying a Login on page 9-13.
H
Deleting a Login on page 9-13.
DRAFT — June 1999
9-1
Security and Logins
Limiting Access
The NextEDGE system provides access security through the following:
H
Asynchronous (async) terminal
H
Telnet
H
FTP
H
SNMP
Up to two direct or Telnet sessions can be active at any given time; that is, you
can have two simultaneous Telnet sessions, or one Telnet session and one active
async terminal session, or two simultaneous async terminal sessions.
Controlling Asynchronous Terminal Access
The NextEDGE system provides the following methods for limiting direct access
to the asynchronous user interface on the communication (COM) port:
H
Requiring a login.
H
Assigning an access level to the port.
See Configuring the Communication Port in Chapter 8, Configuration, for more
information about communication port configuration options.
9-2
DRAFT — June 1999
9191-A2-GH30-00
Security and Logins
" Procedure
To limit COM port or modem access to the async user interface:
1. Go to the Communication Port Options or the Modem Port Options screen.
[Communication Port /Modem Port]
2. Select and set the following configuration options, as appropriate:
To . . .
Set the configuration option . . .
Require a login
Login Required to Enable.
NOTE: User ID and password combinations
must be defined. See Creating a Login on
page 9-12.
Limit the effective access level to
Level-3 or Level-2
Port Access Level to Level-2 or Level-3.
NOTE: Regardless of a user’s login access
level, a user cannot operate at a level higher
than the access level specified for the port
(e.g., if a user has a Level-1 login and Level-2
port access has been set, the Level-1 user
can only operate as a Level-2 user).
If you are going to allow users to configure the
unit via the COM port or modem port, keep the
access at Level-1.
NOTE:
See Resetting the NextEDGE system in Chapter NO TAG, Operation and
Maintenance, should you inadvertently be locked out.
See Configuring the Communication Port in Chapter 8, Configuration, for more
information about communication port configuration options.
Controlling Telnet or FTP Access
The NextEDGE system provides several methods for limiting access via a Telnet
or FTP session. Telnet or FTP access can be on a standard management link, or
it can be on a service provider’s troubleshooting (TS) management link.
9191-A2-GH30-00
DRAFT — June 1999
9-3
Security and Logins
Limiting Telnet Access
Methods for limiting access through a Telnet session include the following:
H
Disabling Telnet access completely.
H
Requiring a user ID or password to login for Telnet Sessions not on the
TS Management Link.
H
Assigning an access level for Telnet sessions.
H
Disabling special TS Management Link access (see page 9-6).
To limit Telnet access via a service provider’s troubleshooting management link,
follow the procedure on page 9-6.
" Procedure
To limit Telnet access when the session is not on the TS Management Link:
1. Go to the Telnet and FTP Session Options screen.
Telnet and FTP Sessions
2. Set the following configuration options, as appropriate.
To . . .
Disable Telnet access
Telnet Session to Disable.
Require a login
page 9-12.
Assign an access level
Session Access Level to Level-2 or Level-3.
than the access level specified for the Telnet
session (e.g., if a user has a Level-1 login and
Level-2 telnet access has been set, the
Level-1 user can only operate as a Level-2
user).
unit, keep the access at Level-1.
See Configuring Telnet and/or FTP Session Support in Chapter 8, Configuration,
for more information about setting Telnet options.
9-4
DRAFT — June 1999
9191-A2-GH30-00
Security and Logins
Limiting FTP Access
Methods for limiting access through a FTP session include the following:
H
Disabling FTP access completely.
H
Requiring a user ID or password to login for FTP Sessions not on the
TS Management Link.
H
Bandwidth of FTP.
H
Disabling special TS Management Link access.
To limit FTP access via a service provider’s troubleshooting management link,
follow the procedure on page 9-6.
" Procedure
To limit FTP access when the session is not on the TS Management Link:
2. Select and set the following configuration options, as appropriate.
To . . .
Disable FTP
FTP Session to Disable.
Require a login
pageNO TAG.
If you want to allow users to configure the unit
or perform file transfers, including downloads,
keep the access at Level-1.
Level-1 access is required to download
software to the unit, or to upload or download
configuration files. Level-3 is sufficient for
NMS access for SLV historical information.
Limit bandwidth for FTP
FTP Max Receive Rate to a rate less than the
network line speed, typically less than or
equal to the CIR.
This method is not recommended if SLV
reports are desired since FTP is required to
generate the reports.
See Configuring Telnet and/or FTP Session Support in Chapter 8, Configuration,
for more information about setting FTP options.
9191-A2-GH30-00
DRAFT — June 1999
9-5
Security and Logins
Limiting Telnet or FTP Access Over the TS Management Link
" Procedure
To limit Telnet or FTP access when the session is on the TS Management Link:
— Set Telnet Session to Disable.
— Set FTP Session to Disable.
3. Return to the Management and Communication menu and select Node IP.
To . . .
Disable access via a
TS Management Link
TS Management Link to None.
Assign an access level to the
TS Management Link
TS Management Access Level to Level-2
or Level-3.
than the access level specified for the session
(e.g., if a user has a Level-1 login and Level-2
telnet access has been set, the Level-1 user
can only operate as a Level-2 user).
unit, keep the access at Level-1.
See Configuring Telnet and/or FTP Session Support or Configuring Node IP
Information in Chapter 8, Configuration, for more information about these
9-6
DRAFT — June 1999
9191-A2-GH30-00
Security and Logins
Controlling SNMP Access
The NextEDGE system supports SNMP Version 1, which only provides limited
security through the use of community names. There are three methods for
limiting SNMP access:
H
Disabling SNMP access.
H
Assigning SNMP community names and access type.
H
Assigning IP addresses of NMSs that can access the NextEDGE system.
Disabling SNMP Access
The General SNMP Options screen provides the configuration option to disable
SNMP access to the unit. When this configuration option is disabled, the
NextEDGE system will not respond to any SNMP messages.
" Procedure
To disable SNMP access:
1. Go to the General SNMP Options screen.
2. Set SNMP Management to Disable.
See Configuring SNMP Management in Chapter 8, Configuration, for more
information about General SNMP Management configuration options.
9191-A2-GH30-00
DRAFT — June 1999
9-7
Security and Logins
Assigning SNMP Community Names and Access Levels
The General SNMP Options screen provides the configuration options that allow
the NextEDGE system to be managed by an SNMP manager supporting the
SNMP protocol. Use this screen to:
H
Assign the SNMP community names that are allowed to access the
NextEDGE system’s Management Information Base (MIB).
H
Specify the type of access allowed for each SNMP community name.
Whenever an external SNMP manager attempts to access an object in the MIB,
the community name must be supplied.
" Procedure
To assign SNMP community names and access levels:
1. Go to the General SNMP Management Options screen.
To . . .
Assign SNMP community names
Community Name 1 and Community Name 2
to a community name text, up to 255
characters in length.
Assign the type of access allowed
for the SNMP community names
Name 1 Access and Name 2 Access to Read
or Read/Write.
information about General SNMP Management configuration options.
9-8
DRAFT — June 1999
9191-A2-GH30-00
Security and Logins
Limiting SNMP Access Through IP Addresses
The NextEDGE system provides an additional level of security by:
H
Limiting the IP addresses of the NMSs that can access the NextEDGE
system.
H
Performing validation checks on the IP address of SNMP management
systems attempting to access the NextEDGE system.
H
Specifying the access allowed for the authorized NMS when IP address
validation is performed.
The SNMP NMS Security Options screen provides the configuration options that
determine whether security checking is performed on the IP address of SNMP
management systems attempting to communicate with the unit.
Make sure that SNMP Management is set to Enable.
General SNMP Management → SNMP Management: Enable
information about SNMP management configuration options.
" Procedure
To limit SNMP access through IP addresses:
1. Go to the SNMP NMS Security Options screen.
SNMP NMS Security
To . . .
Enable IP address checking
NMS IP Validation to Enable.
Specify the number (between 1
and 10) of SNMP management
systems that are authorized to
send SNMP messages to the
NextEDGE system
Number of Managers to the desired
number.
Specify the IP address(es) that
identifies the SNMP manager(s)
authorized to send SNMP
messages to the NextEDGE unit
NMS n IP Address to the appropriate
IP address.
Specify the access allowed for an
authorized NMS when IP address
validates is performed
Access Level to Read or Read/Write.
9191-A2-GH30-00
DRAFT — June 1999
9-9
Security and Logins
See Configuring SNMP NMS Security in Chapter 8, Configuration, for more
information about SNMP NMS Security configuration options.
Controlling Dial-In Access
Access to the NextEDGE’s modem port is limited by disabling the Dial-In Access
configuration option.
" Procedure
To limit access through a dial-in connection:
1. Go to the Modem Port Options screen.
Modem Port
2. Disable the Dial-In Access configuration option.
3. Save your change.
See Configuring Dial-In Access to the Async User Interface and Configuring the
Modem Port in Chapter 8, Configuration, for additional information.
9-10
DRAFT — June 1999
9191-A2-GH30-00
Security and Logins
Controlling ISDN Access
The NextEDGE unit limits ISDN access through either of the following methods:
H
ISDN call security.
H
Disabling ISDN access.
ISDN Call Security
The NextEDGE unit equipped with an ISDN BRI or PRI DBM uses call screening
to avoid accidental or intentional disruption of network traffic. The answering
internal DBM only accepts calls from valid calling number identifiers.
When an ISDN DBM is installed and enabled, the DBM takes advantage of ISDN
services for network backup and Calling Number Identification Service (CNIS) to
provide backup security. ISDN assures the integrity of calling party identifiers, and
the DBM uses the calling party identifier as the destination DBM or backup
partner. No additional security is required.
Disabling ISDN Access
" Procedure
To disable ISDN access:
1. Go to the ISDN Physical Options screen.
Main Menu → Configuration → ISDN → Physical
2. Set Interface Status to Disable.
3. Save your change.
See Configuring the ISDN Physical Interface in Chapter 8, Configuration, for
more information about ISDN BRI and PRI DBM configuration options.
9191-A2-GH30-00
DRAFT — June 1999
9-11
Security and Logins
Creating a Login
A login is required if security is enabled.* Up to six login ID/password
combinations can be created using ASCII text, and each must have a specified
access level. Logins must be unique and they are case-sensitive.
" Procedure
To create a login:
1. Go to the Administer Logins screen.
Main Menu → Control → Administer Logins
2. Select New from the function keys area and press Enter.
3. Enter the login ID, password, and security level for each login.
In the field . . .
Enter the . . .
Login ID
ID of 1 to 10 characters.
Password
Password from 1 to 10 character.
Re-enter password
Password again to verify that you entered the
correct password into the device.
Access Level
Access level: 1, 2, or 3.
H Level-1 – User can add, change, and
display configuration options, save, and
perform device testing.
H Level-2 – User can monitor and perform
diagnostics, display status and
configuration option information.
H Level-3 – User can only monitor and
display status and configuration screens.
Note: Make sure at least one login is setup for
Level-1 access or you may be inadvertently
locked out.
NOTE:
See Resetting the NextEDGE Unit in Chapter 10, Operation and
Maintenance, should you inadvertently be locked out.
When Save is complete, the cursor is repositioned at the Login ID field, ready
for another entry.
See Configuring SNMP NMS Security in Chapter 8, Configuration, for more
information about security configuration options.
* Security is enabled by the Login Required configuration option for the communication port and modem port, as well
as the Telnet Login Required or FTP Login Required option for a Telnet or FTP Session.
9-12
DRAFT — June 1999
9191-A2-GH30-00
Security and Logins
Modifying a Login
Logins are modified by deleting the incorrect login and creating a new one.
Deleting a Login
A login record can be deleted.
" Procedure
To delete a login record:
1. Go to the Administer Logins screen.
Main Menu → Control → Administer Logins
2. Press Ctrl-a to switch to the screen function key area.
3. Select PgUp or PgDn and press Enter to page through login pages / records
until you find the one to be deleted.
4. Once the correct record is displayed, select De l ete and press Enter.
5. Save your deletion.
When the deletion is complete, the number of login pages / records reflects
one less record, and the record before the deleted record reappears.
Example:
Page 2 of 4 is changed to Page 2 of 3.
9191-A2-GH30-00
DRAFT — June 1999
9-13
Security and Logins
9-14
DRAFT — June 1999
9191-A2-GH30-00
Operation and Maintenance
10
This chapter includes the following information:
H
Displaying System Information on page 11-27.
H
Displaying LEDs and Control Leads on page 11-28.
H
Device Messages on page 10-6.
H
Status Information on page 10-11.
— Self-Test Results Messages on page 10-12.
— Health and Status Messages on page 10-13.
— Test Status Messages on page 10-19.
— Network LMI-Reported DLCIs Status on page 10-21.
— PVC Connection Status on page 10-22.
H
Time Slot Assignment Status on page 10-23.
H
Performance Statistics on page 10-26.
— Clearing Performance Statistics on page 10-27.
— Service Level Verification Performance Statistics on page 10-28.
— DLCI Performance Statistics on page 10-29.
— Frame Relay Performance Statistics on page 10-31.
— ESF Line Performance Statistics on page 10-35.
H
FTP File Transfers on page 10-39.
— Upgrading System Software on page 10-41.
— Determining Whether a Download is Completed on page 10-42.
— Changing Software on page 10-42.
— Transferring Collected Data on page 10-43.
9191-A2-GH30-00
DRAFT — June 1999
10-1
Displaying System Information
Use the Identity screen to view identification information about the system and
the NextEDGE system. This information is useful if you are purchasing additional
or replacement units and/or making firmware upgrades.
" Procedure
To view system information:
1. Access the Identity menu.
Main Menu → Status → Identity
2. Select System & NAM to view the following information:
View this field . . . To find the . . .
System Name
Domain name for this SNMP-managed node (up to 255 ASCII
characters).
System Contact
Contact person for this SNMP-managed node.
System Location
Physical location for this SNMP-managed node.
NAM
NAM Type
Type of unit installed, referred to as a network access module,
or NAM (e.g., T1 FR NAM).
Serial Number
Unit’s 7-character serial number.
Current
Software Revision
Software version currently being used by the unit.
Format nn.nn.nn consists of a 6-digit number that represents
the major and minor revision levels.
Alternate
Software Revision
Software version that has been downloaded into the unit, but
has not yet been implemented. Format is the same as for the
Current Software Revision.
H In Progress indicates that the flash memory is currently
being downloaded.
H Invalid indicates that no download has occurred or the
download was not successful
Hardware Revision
Unit’s hardware version. Format nnnn-nnx consists of a 4-digit
number, followed by two digits and one alphabetic character.
Your system may have an ISDN DBM and/or APM installed for which
additional information is provided.
— For an ISDN DBM, see Displaying DBM Information in Chapter 11, Dial
Backup Modules.
— For an APM, see Displaying APM Information in Chapter 11, Application
Modules.
10-2
DRAFT — June 1999
9191-A2-GH30-00
Viewing LEDs and Control Leads
The NextEDGE system’s frame NAM’s faceplate includes LEDs ( light-emitting
diodes) that provide status on the unit and its interfaces.
NETWORK
DSX/PRI
O
K
O
K
2-
1-
O
O
F
AL
M
SI
G
O
O
F
AL
M
SI
G
BK
P
AL
M
TM
TS
T
NextEDGE
O
K
9191
PORT
99-16339
The Display LEDs and Control Leads feature allows you to monitor a remote unit,
and is useful when troubleshooting control lead problems. This feature is selected
from the Status menu.
Main Menu → Status → Display LEDs and Control Leads
NAM with an ISDN DBM and APM Example
main/status/leds
Device Name: Node A
PARADYNE 9191
1/26/1998 23:32
DISPLAY LEDS & Control Leads
GENERAL
OK
Alarm
Test
Backup
ISDN PRI
Sig
OOF
Alm
NETWORK 1
Sig
OOF
Alm
DSX-1
Sig
OOF
Alm
Port-1
OK
TXD
RXD
DTR
CTS
Port-2
OK
TXD
RXD
DTR
CTS
VOICE PORTS
OK
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Exit
ESC for previous menu
MainMenu
Refresh
When using this feature:
H
Inverse video indicates that the LED is on.
H
Normal video indicates that it is off.
For more information about LEDs and Control Leads:
9191-A2-GH30-00
H
For an ISDN DBM, see Viewing DBM LEDs and Control Leads in Chapter 11,
Dial Backup Modules.
H
For APMs, see Viewing APM LEDs and Control Leads in Chapter 11,
Application Modules.
DRAFT — June 1999
10-3
LED Descriptions
The following tables describe what these LEDs indicate.
Table 10-1. General Status LEDs
Label
ALM
Indication
Color
What It Means
Power and
Operational
Status
Green
ON – System has power and is operational.
Operational
Alarm ( Fail )
Red
OFF – System is in a power-up self-test, or
there is a failure.
ON – System has just been reset, or an
error or fault has been detected.
Error/fault/alarm conditions:
H Out of Frame ( OOF )
H Loss of Signal (LOS)
H Alarm Indication Signal (AIS)
H Exceeded Error Rate (EER)
H Yellow Alarm Signal
H Device Fail
H Self-Test Failed
H Power Supply Failure
H LMI Down
H DLCI Down
H SLV Timeout
H Network Communication Link Down
H CTS Down
H DTR Down
H Primary or Secondary Clock Failed
OFF – No failures have been detected.
TST
Test Mode
Yellow
ON – Loopback or test pattern in progress,
initiated locally, remotely, or from the
network.
OFF – No tests are active.
10-4
DRAFT — June 1999
9191-A2-GH30-00
Table 10-2. Network, DSX, or PRI Interface LEDs
Label
Indication
Color
What It Means
SIG
Signal
Green
ON – A recoverable signal is present on the
Network/DSX/PRI interface.
OFF – The signal cannot be recovered from
the Network/DSX/PRI interface. An
LOS condition exists.
OOF
Out of Frame
Yellow
ON – At least one OOF was detected during
the sampling period.
OFF – No OOFs were detected during the
sampling period.
ALM
Alarm
Yellow
ON – An alarm condition is present on the
network/DSX/PRI interface.
Current alarm conditions:
H Loss of Signal ( LOS )
H Loss of Frame (LOF)
H Out of Frame (OOF)
H Excessive Error Rate (EER)
OFF – No alarm condition is present on the
Table 10-3. DTE Port Interface LEDs
Label
Indication
Color
What It Means
OK
Operational
Status
Green
ON – The interchange circuits for the port
are in the correct state to transmit and
receive data.
OFF – The port is idle. Occurs if the port is
disabled, or if the port is configured to
monitor DTR and/or RTS and the
lead(s) is not asserted.
9191-A2-GH30-00
DRAFT — June 1999
10-5
Device Messages
These messages appear in the messages area at the bottom of the screens.
All device messages are listed in alphabetical order.
Table 10-4. Device Messages (1 of 5)
Message
What It Indicates
What To Do
Access level is n ,
Read-only.
User’s access level is 2
or 3; user is not authorized
to change configurations.
No action needed.
Already Active
Test selected is already
running.
H Allow test to continue.
H Select another test.
H Stop the test.
New had been selected
from the Administer Logins
screen, no entry was made,
then Save was selected.
H No action needed.
Cannot delete Trap
Manager
De l ete was selected from
the Management PVCs
Options screen, but the
PVC had been defined as a
trap destination.
No action needed, or configure
another path for traps and try
again.
Command Complete
Configuration has been
saved or all tests have
been aborted.
No action needed.
Connection Refused
Wait and try again.
(Seen at an FTP
terminal.)
Two menu-driven user
interface sessions are
already in use when a
Telnet session was
attempted.
Destination Not
Unique
Destination entered is
already being used.
Enter another destination
indicator.
DLCI in connection.
Delete connection first
User tried to delete a DLCI
that was part of a
connection.
H No action needed, or
DLCI number entered is not
unique for the frame relay
link.
No action needed; previous
contents of the DLCI number
field is restored.
Blank Entries
Removed
Duplicate DLCI
Number
10-6
DRAFT — June 1999
H Reenter the Login ID,
Password, and Access Level.
H Delete the connection, then
delete the DLCI.
9191-A2-GH30-00
Message
What It Indicates
File Transfer Complete A file transfer was
performed successfully.
(Seen at an FTP
terminal.)
Switch to the newly downloaded
software.
File Transfer Failed –
Invalid file
H Try again, making sure you
(Seen at an FTP
terminal.)
A file transfer was
attempted, but it was not
successful.
type the filename correctly.
H Exit the FTP session, or
download another file.
Invalid Character (x )
A non-valid printable ASCII
character has been
entered.
Reenter information using valid
characters.
Invalid date: must be
mm/dd/yyyy
A non-valid date was
entered on the System
Information screen.
Reenter the date in the
month/day/4-digit year format.
Invalid date and/or
time
A non-valid date or time
was entered on the System
Information screen. The
date does not exist (e.g.,
February 29th).
Reenter the date in the
month/day/4-digit year format.
Invalid time: must be
hh:mm
A non-valid system time
was entered on the System
Information screen.
Reenter the time in the
hour:minutes format.
Invalid – Already
Active
A test was already in
progress when it was
selected.
No action needed.
Invalid Password
Login is required and an
incorrect password was
entered; access is denied.
H Try again.
A conflicting loopback or
pattern test was in progress
when Start was selected to
start another test, or was
active on the same or
another interface when
Start was selected.
H Wait until other test ends and
Invalid Test
Combination
9191-A2-GH30-00
What To Do
DRAFT — June 1999
H Contact your system
administrator to verify your
password.
message clears.
H Cancel all tests from the Test
screen ( Path: main/ test ).
H Stop the test from the same
screen the test was started
from.
10-7
Message
What It Indicates
What To Do
Limit of six Login IDs
reached
An attempt to enter a new
login ID was made, and the
limit of six login/password
combinations has been
reached.
H Delete another login/password
New was selected from the
PVC Connection Table and
the maximum number of
management PVCs has
already been created.
H Do not create the
PVC Connection Table and
the maximum number of
PVCs has already been
created.
H Do not create the PVC
Name Must be Unique
Name entered for a
management PVC has
been used previously.
Enter another 4-character name
for the logical/management link.
No Destination Link
DLCIs Available
PVC Connection Table, but
even though DLCIs are
available to form a
connection, no DLCIs are
available on the network or
ISDN link, which are
suitable PVC Destinations.
Configure additional DLCIs for
the network or ISDN link and try
again.
No DLCIs available for
connection
PVC Connection Table, but
all configured DLCIs have
been connected.
No action needed, or configure
more DLCIs and try again.
No DLCIs available for
connection
Management PVCs option
screen, but all Link/DLCI
pairs have been connected.
Configure more network and/or
Port-1 Links/DLCIs pairs and try
again.
Limit of Mgmt PVCs
reached
Limit of PVC
Connections reached
No DLCIs Available for New was selected from the
Mgmt PVC
Management PVCs option
screen, but all configured
DLCIs have been
connected.
10-8
DRAFT — June 1999
combination.
H Reenter the new login ID.
management PVC.
H Delete another management
PVC, and try again.
connection.
H Delete another PVC
connection, and try again.
Configure more network and/or
Port-1 DLCIs and try again.
9191-A2-GH30-00
Message
What It Indicates
What To Do
No DLCIs Defined
DLCI Records was selected Select New and create a DLCI
from an interface’s
record.
Configuration Edit/Display
menu, and no DLCI
Records have been created
for this interface.
No more DLCIs
allowed
New or CopyFrom was
selected from an interface’s
DLCI Records configuration
screen, and the maximum
number of DLCI Records
had already been reached.
Delete a DLCI, then create the
new DLCI Record.
No Primary
Destination Link
DLCIs Available
New or Modify was
selected from the PVC
Connection Table, but even
though DLCIs are available
to form a connection, no
DLCIs are available on the
network or ISDN link, which
is a suitable Primary PVC
Destination.
Configure additional DLCIs for
the network or ISDN link and try
again.
If a network or ISDN DLCI has
been entered as a Source DLCI:
1. Change the Source DLCI to a
user data port DLCI.
2. Enter the network or ISDN
DLCI as the PVC’s Primary
Destination..
No Security Records
to Delete
Delete was selected from
the Administer Login
screen, and no security
records had been defined.
H No action needed.
Password Matching
Error – Re-enter
Password
Password entered in the
Re-enter Password field of
the Administer Logins
screen does not match
what was entered in the
Password field.
H Try again.
Permission Denied
A file transfer was
attempted, but the:
(Seen at an FTP
terminal.)
H Enter a security record.
H Contact your system
administrator to verify your
password.
User did not have Level 1
security.
See your system administrator to
get your security level changed.
Wrong file was specified
when the put command
was entered.
Try again, entering the correct
file with the put command.
User attempted to upload a
program file from the unit.
Enter the put command instead
of a get command; you can only
transfer files to the unit, not from
it.
See Performing a Software
Upgrade in Chapter 12,
Operation and Maintenance.
9191-A2-GH30-00
DRAFT — June 1999
10-9
Message
What It Indicates
What To Do
Please Wait
Command takes longer
than 5 seconds.
Wait until message clears.
Resetting Device,
Please Wait ...
Yes (or y) was entered in
the Reset COM Port usage
field of the System Paused
menu.
No action needed.
Test Active
No higher priority health
and status messages exist,
and a test is running.
H Contact service provider if test
initiated by the network.
H Wait until the test ends and
message clears.
H Cancel all tests from the Test
screen ( Path: main/test ).
H Stop the test from the same
screen the test was started
from.
User Interface Already
in Use
Two Telnet sessions are
already in use when an
attempt to access the
async user interface
through the COM or
modem port is made.
H Wait and try again.
H Contact one of the IP address
user and request that they
logoff.
IP addresses and logins of
the users currently
accessing the interface are
also provided.
User Interface Idle
Value Out of Range
10-10
Previously active session is
now closed/ended, and
access via the COM port or
modem port is now
available.
Log onto the system.
Session has been ended
due to timeout.
No action needed.
CIR entered for the DLCI is
a number greater than the
maximum allowed.
Enter a valid CIR ( 0 – 1536000 ).
Excess Burst Size entered
for the DLCI is a number
greater than the maximum
allowed.
Enter a valid Excess Burst Size
( 0 – 1536000 ).
DLCI Number entered is
less than 16 or greater than
1007.
Enter a valid number
(16 – 1007 ).
DRAFT — June 1999
9191-A2-GH30-00
Status Information
Status information is useful when monitoring the FrameSaver unit. Use the Status
menu to display information concerning:
H
System and Test Status Messages – Health and Status, Self-Test Results,
Test Status (see page 10-12)
H
Network LMI Reported DLCIs Status – DLCIs, Status, and CIR (Kbps) (see
page 10-21)
H
PVC Connection Status – Source and Destination Links, DLCIs, EDLCIs, and
connection status (see page 10-22)
H
Time Slot Assignment Status (see page 10-23)
For additional status information:
H
For an ISDN DBM, see Viewing DBM Interface Status in Chapter 11,
Dial Backup Modules.
H
For APMs, see Viewing Voice APM Status in Chapter 11, Application
Modules.
NOTE:
Status messages contained in the following sections are in
alphabetical order.
These self-test result messages appear in the Self-Test Results field at the top of
the System and Test Status screen, in the Self-Test Results field.
9191-A2-GH30-00
DRAFT — June 1999
10-11
System and Test Status Messages
System and test status information is selected from the Status menu.
Main Menu → Status → System and Test Status
The following information is included on this screen:
H
Self-Test Results Messages on page 10-12.
H
Health and Status Messages on page 10-13.
H
Test Status Messages on page 10-19.
Self-Test Results Messages
These self-test result messages appear in the Self-Test Results field at the top of
the System and Test Status screen.
Table 10-5. Self-Test Results Message
Message
What It Indicates
What To Do
Failure xxxxxxxx
An internal failure occurred
(xxxxxxxx represents an
8-digit hexadecimal failure
code for use by service
personnel).
1. Record the failure code.
No problems were found
during power-up or reset.
No action needed.
Passed
10-12
DRAFT — June 1999
2. Reset the unit.
3. Contact your service
representative.
9191-A2-GH30-00
Health and Status Messages
Health and Status messages appear in the left column of the System and Test
Status screen. The highest priority Health and Status message appears at the
bottom right corner of the screen. Most messages are as a result of an alarm
condition.
Table 10-6. Health and Status Messages (1 of 6)
Message
What It Indicates
What To Do
AIS at DSX-1
An Alarm Indication Signal
(AIS) is received by the
DSX-1 interface. AIS is an
unframed, all ones signal.
Check the DTE attached to the
DSX-1 interface.
AIS at Network
network interface. AIS is an
Report problem to carrier.
The network is transmitting
an AIS.
Auto-Configuration
Active
Auto-Configuration feature
is active, which allows
automatic configuration and
cross-connection of DLCIs
as they are reported by the
network LMI.
No action needed unless you
want to disable this feature.
Back-to-Back Mode is
Active
The operating mode has
been configured for
back-to-back
( Control → Change
Operating Mode).
No action needed unless you
want to disable this feature.
The NextEDGE system can
be connected to another
NextEDGE or a
FrameSaver device without
a frame relay switch
between them via a
crossover cable.
This feature is useful for product
demonstrations or for a
point-to-point configuration using
a leased line.
See Back-to-Back
Operation in Chapter 3,
Typical Applications, for an
illustration.
9191-A2-GH30-00
DRAFT — June 1999
10-13
Message
What It Indicates
What To Do
CTS down to Port-1
Device
The Port-1 CTS control
lead on the FrameSaver
unit is off.
Check DTR and RTS from
Port-1.
Device Fail yyyyyyyy
An internal error has been
detected by the operating
software.
1. Provide the displayed 8-digit
failure code (yyyyyyyy) to your
service representative.
2. Clear the Device Fail
message.
Main Menu → Control →
Clear Device Fail
DLCI nnnn Down,
frame relay link 1, 2
The DLCI for the specified
frame relay link is down.
Verify that the network LMI is up.
If it is, contact network provider.
DTR down from Port-1
Device
The DTR control lead on
the device connected to
Slot s Port p is off.
Examine the attached DTE and
cable connected to the
FrameSaver unit’s port.
1. Check that the Port-1 cable is
securely attached at both
ends.
2. Check the status of the
attached equipment.
EER at Network n
The error rate of the
received network signal
exceeds the currently
configured threshold. This
condition only occurs if the
network interface is
configured for ESF framing.
1. Verify that the network cable is
ends.
2. Contact network provider.
This condition clears when
the error rate falls below the
threshold value, which may
take up to 15 minutes.
Internal Modem Failed
1
2
The integral modem failed
to pass the self-test.
Reset the unit. If it continued
to fail, call your service
representative.
nnnn indicates a DLCI number of 16 through 1007;
frame relay link is one of the following:
– Netn-FRx. The frame relay link specified by Frame Relay x time slot assignments
on Network n.
– Port-n. The frame relay link associated with data Port-n in single slot units.
10-14
DRAFT — June 1999
9191-A2-GH30-00
Message
What It Indicates
What To Do
Link Down
Administratively,
frame relay link 2
The selected frame relay
link has been disabled by
the unit due to LMI
Behavior conditions or a
configuration conflict.
1. Verify that the LMI Protocol
setting reflects the LMI type
being used.
2. Contact your network provider
The frame relay link can be
on the network or data port.
LMI Down, frame relay
link 2
The Local Management
Interface is down for the
specified frame relay link.
For the Network interface:
1. If LMI was never up, verify
that the proper time slots
have been configured.
2. If LMI was never up, verify
that the LMI Protocol setting
reflects the LMI type being
used.
3. Verify that Frame Relay
Performance Statistics show
LMI frames being transmitted.
If all of the above have been
verified and the physical link is
not in Alarm, contact network
provider.
For Port-n:
1. Check that the DTE cable is
ends.
2. Verify that Transmit Clock
Source and Invert Transmit
Clock options are properly
configured.
LMI frames being received. If
no frames are being received:
– Check the attached device.
– Verify that the LMI Protocol
being used.
1
2
nnnn indicates a DLCI number of 16 through 1007;
on Network n.
9191-A2-GH30-00
DRAFT — June 1999
10-15
Message
What It Indicates
What To Do
LMI Discovery in
Process,
frame relay link
LMI protocol discovery to
determine the protocol that
will be used on a selected
link is currently being
performed. It occurs when
LMI Protocol is configured
for Auto_On_LMI_Fail,
Initialize_from_Net1FR1, or
Initialize_from_Interface
and there is an LMI Down
alarm on the link configured
to provide the LMI Protocol.
1. Verify that the Frame Relay
LMI frames being received.
2. If LMI was never up, verify that
the LMI Protocol setting
reflects the LMI type being
used.
3. Contact your network provider
The frame relay link can be
on the network or data port.
MFR Link Down,
frame relay link
At least one call has been
made on a selected
multilink ISDN frame relay
link, but LMI was declared
down on all links, so all
calls were unsuccessful.
Contact your ISDN network
provider.
The frame relay link is the
ISDN Link Name, and the
unit is configured to
originate backup callsover
the DBM interface.
MFR Link Suboptimal,
frame relay link
At least one call has been
made on a selected
multilink ISDN frame relay
link, LMI was declared
down on one of the links,
and the Maximum Link
Rate configured in the
ISDN Link Profile has not
been achieved.
provider.
The frame relay link is the
ISDN Link Name, and the
unit is configured to
originate backup callsover
the DBM interface.
LOS at Network 1
10-16
A Loss of Signal (LOS)
condition is detected on the
network interface. Clears
when the ratio of ones to
zeros received is greater
than or equal to 12.5%.
1. Network cable problem.
1. Check that the network cable
is securely attached at both
ends.
2. T1 facility problem.
2. Contact your network provider.
DRAFT — June 1999
9191-A2-GH30-00
Message
2
What It Indicates
What To Do
on Network n.
LOS at DSX-1
network interface. Clears
1. DSX-1 cable problem.
1. Check that the DSX-1 cable is
ends.
2. No signal being
transmitted from the
DTE.
2. Check the DTE status.
Network Com Link
Down
The communication link for
the COM port is down, and
the COM port is configured
for Net Link.
Check the router connected to
the COM port.
OOF at DSX-1
An Out of Frame (OOF)
DSX-1 interface.
Cleared when a reframe occurs.
1. Incompatible framing
format between the DTE
and the FrameSaver
unit.
1. Check that the framing format
for the DSX-1 (DTE) interface
is correct.
2. DSX-1 cabling problem.
ends.
network interface.
format between the
network and the
FrameSaver unit.
for the network interface is
correct.
2. Network cabling
problem.
ends.
A power supply or fan tray
problem is detected on the
system for the 14-slot
access carrier.
1. Check that the power supply
or fan tray is mounted
correctly in the housing.
OOF at Network n
Power Supply Alarm
9191-A2-GH30-00
DRAFT — June 1999
representative.
10-17
Message
What It Indicates
What To Do
Primary Clock Failed
A failure of the primary
clock source configured for
the NAM is detected and
the secondary clock is
providing the timing for the
NAM.
1. Check that the cable is
securely attached at both ends
for the primary clock source
interface.
2. Contact the network provider.
the configured primary
clock is restored.
Primary & Secondary
Clock Failed
A failure of the primary and
secondary clock sources
configured for the
FrameSaver unit are
detected and the internal
clock is providing the timing
for the unit.
securely attached at both ends
for the primary and secondary
clock source interfaces.
2. Contact the network provider.
The clock source will not
automatically switch from
internal until the primary
clock source returns.
SLV Timeout,
DLCI nnnn,
frame relay link 3
An excessive number of
SLV communication
responses from the remote
FrameSaver unit have been
missed on the specified
multiplexed DLCI; the DLCI
is not suitable for user data.
Contact your network provider if
the problem persists.
A yellow alarm signal is
received on the DSX-1
interface. DTE has
detected a LOS or OOF
condition.
ends.
If a DBM is present, backup is
initiated automatically.
Timeslot Discovery in
Progress,
frame relay link
Yellow at DSX-1
Yellow at Network n
3
10-18
attached equipment.
received on the specified
network interface.
1. Network cable problem.
1. Check that your network cable
ends.
Does not apply to a TS Managment Link DLCI.
DRAFT — June 1999
9191-A2-GH30-00
For additional Health and Status messages, see the following sections:
H
Alarms in Chapter 8, Troubleshooting, for information about these messages.
H
For an ISDN DBM, see DBM Health and Status Messages in Chapter 11, Dial
Backup Modules.
H
For APMs, see APM Health and Status Messages in Chapter 11, Application
Modules.
Test Status Messages
Test Status messages appear in the right column of the System and Test Status
screen.
You have the option of allowing a test to continue, or of aborting the test.
See Tests and Starting and Stopping a Test in Chapter 13, Troubleshooting, for
more information on tests.
For additional test status messages, see the following sections:
H
For an ISDN DBM, see DBM Test Status Messages in Chapter 11, Dial
Backup Modules.
H
For APMs, see APM Test Status Messages in Chapter 11, Application
Modules.
Table 10-7. Test Status Messages (1 of 2)
9191-A2-GH30-00
Message
What It Indicates
DCLB Active, Slot-s Port-p or
frame relay link
A Data Channel Loopback (DCLB) is active on the
T1 network frame relay link, or on the data for the
specified slot and port.
DTE External LB Active,
Slot-s Port-p
An external DTE Loopback is running on the
specified port.
DTE Init. Ext LB Active,
Slot-s Port-p
DTE has initiated an external DTE Loopback on
the specified port.
Lamp Test Active
The Lamp Test is active, causing the LEDs on the
faceplate to flash on and off.
LLB Active, DSX-1, Slot-s Port-p
LLB Active, Network, Slot-s Port-p
A Line Loopback (LLB) is active on the interface
for the specified slot and port.
PLB Active, DSX-1, Slot-s Port-p
PLB Active, Network, Slot-s Port-p
A Payload Loopback (PLB) is active on the
interface for the specified slot and port.
DRAFT — June 1999
10-19
Table 10-7. Test Status Messages (2 of 2)
Message
What It Indicates
DTPLB Active, Slot-s Port-p
A Data Terminal Payload Loopback (DTPLB) is
active for the specified slot and port.
This test cannot be activated on user data ports
that have Port Use set to Frame Relay.
RLB Active, DSX-1, Slot-s Port-p
A Repeater Loopback (RLB) is active on the
interface for the specified slot and port.
Monitor Pttn Active, Network1
Send Pttn Active, DSX-1,
Send Pttn Active, Slot-s Port-p
A Monitor Pattern test (user-selected pattern) is
active on the specified interface (and in the
specified slot).
10-20
Send Pttn Active, Network1
Send Pttn Active, DSX-1,
Send Pttn Active, Slot-s Port-p
A user-selected pattern test is being sent on the
specified interface (in the specified slot).
No Test Active
No tests are currently running.
PVC Loopback Active, DLCI nnnn,
frame_relay_link
A PVC Loopback is active on the specified DLCI
and frame relay link.
DRAFT — June 1999
9191-A2-GH30-00
Network LMI-Reported DLCIs Status
Network LMI-reported DLCI statuses are selected from the Status menu.
Main Menu → Status → LMI Reported DLCIs
The LMI Reported DLCIs screen displays the status and CIR (if supported by the
switch) for each DLCI, whether the DLCI is configured or not. An asterisk
identifies each DLCI contained in the device configuration. Data and LMI status
received on DLCIs that are not configured pass transparently through the system
between the network interface and the first data port without monitoring of DLCI
traffic or demultiplexing/multiplexing management diagnostics or user data. Data
received on DLCIs that are not configured on other frame relay links is discarded.
Table 10-8. Network LMI-Reported DLCIs Status
Field
Status
What It Indicates
DLCI
16 through 1007
Identifies the Local Management
Interface-reported DLCI numbers
assigned to the selected interface – the
identifying number assigned to the path
between two frame relay systems’ ports.
DLCI statuses are listed in ascending
order ( i.e., lowest number first ).
Status
Active
Inactive
Deleted 1
New 1
LMI-reported status of the DLCI:
H Whether the DLCI is active (capable
of carrying data) in the frame relay
network,
H Whether it is inactive,
H Whether it has been deleted by the
frame relay network, or
H Whether it has been created by the
frame relay network.
CIR (bps)
Displays the committed information rate
reported by the Stratacom switch. CIR
information only appears in this column
when LMI Protocol is set to Standard.
If blank, the switch does not support this
feature.
1
9191-A2-GH30-00
Appears for 10 seconds only, before the network changes Deleted to Inactive and
New to Active.
DRAFT — June 1999
10-21
PVC Connection Status
PVC connection statuses are selected from the Status menu. Only PVC
connections with Source DLCIs configured to be Active are shown. See
page 10-23 for an example of this screen.
Main Menu → Status → PVC Connection Status
Table 10-9. PVC Connection Status
Field
Status
What It Indicates
—
No PVC Connections.
PVC connections have yet to be
defined.
Link
Netx-FRx
ISDN Link Name
Mgmt PVC Name
Identifies the cross-connection of
DLCIs configured for the system.
H Source/destination is frame relay
link x on Network n
H Virtual circuit is a management
link that terminates in the unit,
where Name is the link name
DLCI
16 to 1007
For standard DLCIs.
Identifies an individual link/
connection embedded within a
DLCI.
EDLCI
0 to 62
For multiplexed DLCIs only.
Identifies an individual link/
connection embedded within a
DLCI.
Status
1
10-22
Active 1
Inactive
Identifies whether the physical
interfaces, LMIs, and DLCIs are all
enabled and active for this PVC
connection.
For the circuit to be active, both Source and Destination Statuses must be Active.
DRAFT — June 1999
9191-A2-GH30-00
ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ
PVC Connection Status Example
main/status/connections
Device Name: Node A
PARADYNE 9191
01/26/1998 23:32
Page 1 of 2
PVC CONNECTION STATUS
Link
Source
Primary Destination
DLCI EDLCI Link
DLCI EDLCI
Status
Port-1 201
Port-1 202
Port-1 100
Port-1 204
Mgmt PVC Dunedin
Port-1 206
Port-1 207
Port-1 208
Port-1 209
Port-1 210
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
300
1001
1001
1001
1001
1001
1001
500
502
504
1
4
2
5
3
Link
Alternate Destination
DLCI EDLCI Status
Active
Active
Active
Active
Active
Active
Active
Active
Colorado
Inactive Colorado
Inactive Colorado
400
302
304
Inactive
Active
Active
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Exit
MainMenu
PgUp PgDn
Refresh
Time Slot Assignment Status
Time slot assignments are made using the Time Slot Assignment configuration
option. See Assigning Time Slots/Cross Connections in Chapter 9, Configuration
Options, for making time slot assignments. Use the Timeslot Assignment Status
screen to display time slot assignments for:
9191-A2-GH30-00
H
Network Channels
H
DSX-1 Channels
DRAFT — June 1999
10-23
Displaying Network Time Slot Assignments
Use the Network Timeslot Assignment Status screen to display DS0 assignments
for each DS0 on the network interface.
Use the following menu sequence to display network channel information.
Main Menu → Status → Timeslot Assignment Status → Network
The Network Timeslot Assignment Status screen displays 24 two-field entries in
three rows. Together, each two-field entry defines the assignment for one
Network interface time slot. The top field represents the time slot of the Network
Interface. The bottom field represents the cross connect status of the associated
(top field) network time slot.
The following information is available for viewing.
The Network Time Slot Fields (top) . . .
Indicates . . .
N01 to N24
The Network Interface time slot (01 to 24).
The Cross Connect Status Field
(bottom) . . .
Indicates . . .
Unassgn
The time slot is unassigned.
FrameRlyx
The time slot is assigned to Network
Frame Relay Link
Dss-p/yy
The DSX-1 on slot ss, port p, time slot yy
is assigned to the Network Interface time
slot (01 to 24).
Dss-p/yyr
The DSX-1 on slot ss, port p, time slot yy
is assigned to the Network Interface time
slot (01 to 24), using Robbed Bit Signaling
(r ).
NextEDGE physical slot assignment information appears below the DSX-1
interface time slot fields.
Physical Slot . . .
Identifies the assigned card type . . .
01 to 14 (based on model)
T1 NAM – T1 NAM.
Empty – The slot is empty.
10-24
DRAFT — June 1999
9191-A2-GH30-00
Displaying DSX-1 Time Slot Assignments
Use the DSX-1 Timeslot Assignments Status screen to display all of the DS0
assignments for each DS0 on the DSX-1 interface.
Use the following menu sequence to display DSX-1 channel information.
Main Menu → Status → Timeslot Assignment Status → DSX-1
Select the desired DSX-1 slot and port.
The DSX-1 Timeslot Assignment Status screen displays 24 two-field entries in
three rows. Together, each two-field entry defines the assignment for one DSX-1
interface time slot. The top field represents the time slot of the DSX-1 Interface.
The bottom field represents the cross-connect status of the associated (top field)
DSX-1 time slot.
The DSX-1 Time Slot Fields (top) . . .
Indicate . . .
D01 to D24
The DSX-1 Interface time slot (01 to 24).
(bottom) . . .
Indicates the . . .
blank
Time slot is unassigned.
Netnyy
Network Interface n (1 or 2), time slot (yy )
is assigned to DSX-1 time slot (01 to 24),
using Clear Channel.
Netnyyr
Network Interface n (1 or 2), time slot (yy )
is assigned to DSX-1 time slot (01 to 24),
using Robbed Bit Signaling (r ).
NextEDGE physical slot assignment information appears below the DSX-1
interface time slot fields.
Physical Slot . . .
T1 NAM – T1 NAM.
9191-A2-GH30-00
DRAFT — June 1999
10-25
Performance Statistics
Use the Performance Statistics menu to display statistical information for a
selected interface. Statistical information is useful when trying to determine the
severity and frequency or duration of a condition.
Main Menu → Status → Performance Statistics
The following performance statistics are collected:
H
Service Level Verification Performance Statistics on page 10-28.
H
DLCI Performance Statistics on page 10-29.
H
Frame Relay Performance Statistics on page 10-31.
H
ESF Line Performance Statistics on page 10-35.
When you want to observe and estimate the frequency or duration of a specific
condition (e.g., gathering information for reporting a problem to the network),
determine whether a statistic is incrementing.
" Procedure
To determine whether a statistic is incrementing:
1. Record the accumulated value for the statistic of interest (the beginning
value).
2. Press r for Refresh to see if it changes.
3. If the statistic is incrementing, record the ending value and the amount of
time between the beginning and ending values.
Continue to Refresh the screen until you have a sense of how serious the
problem might be.
If you have a Level-1 security access level, you can reset the performance
statistics locally using an asynchronous terminal (see Clearing Performance
Statistics on page 10-27).
10-26
DRAFT — June 1999
9191-A2-GH30-00
Clearing Performance Statistics
Performance statistics counters can also be reset to the baseline when using a
directly-connected asynchronous terminal when your security Access Level
is Level-1. This feature is useful when troubleshooting problems.
Statistic counters are not actually cleared using this feature. True statistic counts
are always maintained so SLAs can be verified, and they can be viewed from an
SNMP NMS. However, since statistics can be cleared locally, the statistics viewed
on the asynchronous terminal may be different from those viewed from the NMS.
" Procedure
To clear all statistics:
Performance Statistics → Clear All Statistics
" Procedure
To clear specific sets of statistics:
H
Use the C l rSLV&DLCIStats function key to reset the SLV and DLCI
performance statistic counters for the currently displayed DLCI from one of
the following screens:
Performance Statistics → Service Level Verification
Performance Statistics → DLCI
H
Use the C l rLinkStats function key to reset the frame relay link performance
statistics.
Performance Statistics → Frame Relay
H
Use the ClrNearStats and ClrFarStats function keys to reset ESF line
performance statistics.
Performance Statistics → ESF Line
9191-A2-GH30-00
DRAFT — June 1999
10-27
Service Level Verification Performance Statistics
These statistics appear when Service Level Verification (SLV) is selected from
the Performance Statistics menu. These statistics only appear for the network
interface and only if DLCIs are multiplexed (see DLCI Type option in Table 8-9,
DLCI Records Options).
Main Menu → Status → Performance Statistics → Service Level Verification
Table 10-10. Service Level Verification Performance Statistics
Statistic
What It Indicates
Far End DLCI
Number of the multiplexed DLCI at the other end of the
connection.
None is displayed if the system has not communicated with the
other end.
Inbound Dropped
Frames
Number of frames transmitted by the far-end unit that were
dropped in transit.
This count continues to accumulate until the maximum count
(232 –2) value has been reached, then the count is reset and
starts to accumulate dropped frames again.
Dropped SLV
Responses
The number of SLV inband sample packets sent that did not
receive a response.
Far End IP Addr
IP Address of the unit at the other end of the multiplexed DLCI
connection.
None is displayed if the system has not communicated with the
other end, or if the unit at the other end of the multiplexed
DLCI does not have an IP Address configured.
Inbound Dropped
Frames
Number of frames transmitted by the far-end unit that were
dropped in transit.
(232 –2) value has been reached, then the count is reset and
starts to accumulate dropped frames again.
Inbound Dropped
Characters
Number of bytes transmitted by the far-end unit that were
dropped in transit.
value has been reached, then the count is reset and starts to
accumulate dropped characters again.
10-28
DRAFT — June 1999
9191-A2-GH30-00
Table 10-10. Service Level Verification Performance Statistics
Statistic
What It Indicates
Avg RdTrip Latency
Average round trip latency, measured in milliseconds, between
the system and the unit at the other end of the multiplexed
DLCI connection. Average round trip latency is measured
every SLV sampling interval and the average is computed over
the previous 15 sampling intervals.
Unknown is displayed if communication with the far-end unit
over the last 15 sampling intervals has not been successful.
Max RdTrip Latency
Same as average (Avg RdTrip Latency), but storing the
maximum number of milliseconds over the sampling interval
instead.
Unknown is displayed if communication with the far-end unit
over the last 15 sampling intervals has not been successful.
DLCI Performance Statistics
These statistics appear when DLCI is selected from the Performance Statistics
menu.
Main Menu → Status → Performance Statistics → DLCI
Table 10-11. DLCI Performance Statistics (1 of 2)
Statistic
What It Indicates
DLCI Up Since 1
Date and time that the DLCI was last declared Active after a
period of inactivity. Down is displayed if the DLCI is inactive.
If the DLCI was Down, this is the time that the DLCI recovered.
If the DLCI was never Down, this is the first time the system
discovered that the DLCI was active in the network.
DLCI Up Time 1
Days, hours, minutes, and seconds since the DLCI was last
declared Active after a period of inactivity. Down is displayed if
the DLCI is inactive.
If the DLCI was Down, this is the amount of time since the
DLCI recovered.
If the DLCI was never Down, this is the amount of time since
the system discovered that the DLCI was active in the network.
Tx/ Rx Characters
9191-A2-GH30-00
Number of data octets ( 8-bit bytes) sent/received for the
selected DLCI on the interface.
DRAFT — June 1999
10-29
Table 10-11. DLCI Performance Statistics (2 of 2)
Statistic
What It Indicates
Tx / Rx Frames
Number of frames sent/received for the DLCI on the interface.
Tx / Rx Frames
Within CIR
Number of frames sent/received for the DLCI on the interface
that are within the committed information rate that had been
configured.
Tx / Rx Frames
Exceed CIR
that exceed the committed information rate that had been
configured.
Tx / Rx Frames
With DE
that have the discard eligible bit set.
Tx BECN Frames
Number of Backward Explicit Congestion Notifications
(BECNs) sent over the interface.
BECNs are sent to notify users of data traffic congestion in the
opposite direction of the frame carrying the BECN indicator.
Rx BECN Frames
received over the interface.
The network sends BECNs to notify users of data traffic
congestion in the opposite direction of the frame carrying the
BECN indicator.
Rx FECN Frames
Number of Forward Explicit Congestion Notifications (FECNs)
received for the selected DLCI on the interface.
The network sends FECNs to notify users of data traffic
congestion in the same direction of the frame carrying the
FECN indicator.
10-30
DRAFT — June 1999
9191-A2-GH30-00
Frame Relay Performance Statistics
These statistics appear when Frame Relay is selected from the Performance
Statistics menu.
Main Menu → Status → Performance Statistics → Frame Relay
Table 10-12. Frame Relay Performance Statistics (1 of 4)
Statistic
What It Indicates
Frame Relay Link
Frames Sent
Number of frames sent over the interface.
Frames Received
Number of frames received over the interface.
Characters Sent
Number of data octets ( bytes) sent over the interface.
Characters Received
Number of data octets (bytes) received over the interface.
FECNs Received
Number of Forward Explicit Congestion Notifications (FECNs)
received over the interface.
The network sends FECNs to notify users of data traffic
congestion in the same direction of the frame carrying the
FECN indicator.
BECNs Received
(BECNs) received over the interface.
The network sends BECNs to notify users of data traffic
congestion in the opposite direction of the frame carrying the
BECN indicator.
9191-A2-GH30-00
DRAFT — June 1999
10-31
Statistic
What It Indicates
Frame Relay Errors
Total Errors
Number of total frame relay errors, excluding LMI errors. Short
frames, long frames, invalid DLCIs, unknown DLCIs, and
unknown errors are included in this total.
Indicates that there may be a non-frame relay device on the
other end of the link, or the units at either the far end or both
ends of the link may be configured incorrectly.
Invalid Rx Frames
Number of invalid frames received over the Network or Port-1
interface.
There is a non-frame relay device on the other end of the link.
Short Rx Frames
Number of frames received over the Network or Port-1
interface that were less than 5-octets ( five 8-bit bytes) in
length.
There may be a non-frame relay device on the other end of
the link.
Long Rx Frames
Number of frames received over the Network or Port-1
interface that were more than 8192-octets in length.
The device on the far end of the link may be configured
incorrectly.
Invalid DLCI
Number of frames received over the interface that were
addressed to DLCIs outside the valid range; that is, a number
less than 16 or greater than 1007.
The device on the far end of the circuit may have been
configured incorrectly, or the DLCIs configured for the system
may not match the DLCIs supplied by the service provider.
Unknown DLCI
Number of frames received over the interface that were
addressed to unknown DLCIs.
The DLCI may not have been configured, or it has been
configured to be Inactive.
Indicates that the systems or devices at both or either end of
the circuit have been configured incorrectly.
Unknown Error
Number of frames received over the interface that do not fall
into one of the other statistic categories.
Indicates that the error is not one that the unit can recognize.
10-32
DRAFT — June 1999
9191-A2-GH30-00
Statistic
What It Indicates
Frame Relay LMI
LMI Protocol
LMI protocol configured for the frame relay link.
Normal condition.
Status Msg Received
Number of LMI status messages received over the interface.
Normal condition.
Total LMI Errors
Number of LMI errors. Reliability errors, protocol errors,
unknown report types, unknown information elements, and
sequence errors are included in this total.
Network problems.
Number of Inactives
Number of times the LMI has declared the frame relay link
Inactive.
Network problems.
9191-A2-GH30-00
DRAFT — June 1999
10-33
Statistic
What It Indicates
Frame Relay HDLC Errors
Rx Total Errors
Number of receiver errors on the interface. The following are
included in this count:
H Receive invalid frames (short frames, long frames, invalid
DLCIs, unknown DLCIs, and unknown errors)
H Rx Total Discards
H Receive errors (non-octet aligned frames, frames with CRC
errors, and Rx Overruns)
Rx Total Discards
Number of receiver discards on the interface. The following are
included in this count:
H Resource errors
H Rx Overruns
H Frames received when the link was down
H Inactive and disconnected DLCIs
H Inactive destination DLCIs
H Unknown EDLCIs
10-34
Rx Overruns
Number of receiver overruns (too many bits) on the interface.
Rx Non-Octet Frames
Number of non-octet frames received on the interface.
Rx CRC Errors
Number of received CRC (cycle redundancy check) errors.
Tx Total Errors
Total number of transmit errors on the interface, including
transmits discards and transmit overruns.
Tx Total Discards
Total number of transmit discards on the interface, including
underrun flushes.
Tx Underruns
Number of transmitter underruns (too few bits) on the
interface.
DRAFT — June 1999
9191-A2-GH30-00
ESF Line Performance Statistics
These statistics appear when ESF Line is selected from the Performance
Statistics menu for the network interface.
Main Menu → Status → Performance Statistics → ESF Line
Only seven intervals appear on the screen at any one time. You can choose
which intervals to display on your screen by entering:
H
Interval Number (01– 96)
– or –
H
Time (Hours and Minutes)
NOTES:
Interval 01 is the interval occurring just prior to the current one;
Interval 02 is 2 intervals prior to the current one, etc.
Selecting a specific time is useful when the approximate time at which a
specific event occurred is known.
Edit any of the interval or time fields on lines 10, 13, or 16. When Enter is
pressed, the values change to the selected range.
9191-A2-GH30-00
To select intervals . . .
You must enter an interval or time on . . .
Occurring on and before a
selected interval or time
Line 10. The display will include the selected interval plus
the 6 intervals recorded before it.
Bracketing a selected
interval or time
the 3 intervals recorded before it and the 3 intervals
recorded after it.
Occurring on and after a
selected interval or time
the 6 intervals recorded after it.
DRAFT — June 1999
10-35
ESF Line Performance Statistics Screen Example
main/status/performance/esf
PARADYNE 9128
Device Name: Node A
01/26/1998 23:32
Network 1 ESF LINE PERFORMANCE STATISTICS
Current Interval Timer
ESF Error Events
Near=123
Far = 124
Near = 15
Far = 12
Line 10
Line 13
Line 16
Line 18
Time
Current: 10:37
Int 01: 10:35
Int 02: 10:20
Int 03: 10:05
Int 04: 09:50
Int 05: 09:35
Int 06: 09:20
Int 07: 09:05
–––ES––
Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
––UAS––
Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
––SES––
Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
––BES––
Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
––CSS––
Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
–LOFC––
Near Far
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Worst Interval:
24 24
14 14
14 14
09 09
18 16
44 44
Near Tot(valid 96): 00010
00000
00000
00000
002
003
Far Tot(valid 96): 00010
00000
00000
00000
002
003
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Exit
MainMenu
ClrFarStats
ClrNearStats
Refresh PgDn PgUp
Select: 01, 02, 03, 04, 05, 06, 07, 08, 09 ...
For the ESF line performance statistics, the following metrics are kept for each
15-minute interval over the past 24-hour period. A Near set and a Far set are
kept for each metric. The Far set is based on information kept by the unit at the
other end of the local loop and is only available when ANSI performance report
messages are enabled in the unit.
Summary information that appears near the top of the screen include:
10-36
H
Near/Far Current Interval Timer – Contains the number of seconds that
have elapsed in the current 15-minute interval for the near or far information,
which can show a value up to 900 seconds.
H
Near/Far ESF Error Events – Maintains a count of ESF error events, as
specified by AT&T TR 54016, which counts CRC and OOF events. A
maximum of 65,535 error events can be counted. Once 65535 is reached,
it stays at that number until the network issues a reset command.
DRAFT — June 1999
9191-A2-GH30-00
The following metrics are collected for the Network interface:
Statistic
What It Indicates
Errored Seconds (ES)
Any second with one or more ESF Error events.
Unavailable Seconds
(UAS)
Any second in which service is unavailable. Begins
incrementing at the onset of 10 consecutive seconds of
severely errored seconds (SES), and stops incrementing after
10 consecutive seconds of no SESs.
Severely Errored
Seconds (SES)
Any second with 320 or more CRC errors or one or more
Out Of Frame (OOF) events.
Bursty Errored
Seconds (BES)
Any second with more than one, but less than 320 CRC errors.
Controlled Slip
Seconds (CSS)
Any second with one or more controlled slips (a replication or
deletion of a DS1 frame by the receiving device). This is
collected for network performance statistics only.
Loss of Frame Count
(LOFC)
The number of Loss of Frame conditions.
Worst Interval
The largest number of seconds for either ES, UAS, SES, BES,
or CSS, or the greatest Loss of Frame Count (LOFC).
If more than one interval contains the same worst value, then
the oldest interval is displayed.
9191-A2-GH30-00
DRAFT — June 1999
10-37
Maintaining Modem Call Directories
See Entering Modem Directory Phone Numbers in Chapter 11, Setup, to set up
modem call directory phone numbers.
Displaying or Changing Modem Call Directories
" Procedure
To display modem directory phone numbers:
1. Select Modem Call Directories.
Main Menu → Control → Modem Call Directories
2. Select the directory to be verified. Use either of the following methods:
— Enter the desired directory (A for Alarm, or 1 through 5 as the alternate
directory) and press Enter.
— Press the spacebar to cycle through various directories until the desired
directory is displayed and press Enter.
The phone number for that directory appears.
" Procedure
To change or add a modem directory phone number:
1. Display the modem call directory to be changed (see Steps 1 and 2 above).
2. Change the phone number. Make sure only valid characters are entered
when changing the phone number.
Valid characters include:
— ASCII text
— W (wait for dialtone)
— Space ( )
Dash ( – )
Underscore ( _ )
2-second pause ( , )
— B (blind dialing) or
P (pulse dialing) or
T (tone dialing)
NOTE:
Select Clear to remove all characters in a field to start over, enter a new
phone number, or delete a phone number.
3. Press Ctrl-a and Save your entries.
CAUTION:
Failure to save additions or changes to Modem Call Directories will
result in your changes being lost.
10-38
DRAFT — June 1999
9191-A2-GH30-00
FTP File Transfers
The system supports a standard File Transfer Protocol (FTP) server over
Transmission Control Protocol (TCP) to allow software upgrades, copying
configurations, and SLV statistics gathering. A complete binary image of the
configuration files can be copied to a host to provide a backup. To use this
feature, the unit must be configured to support Telnet and FTP Sessions.
Be aware of the following rules when doing a file transfer:
H
You must have Access Level 1 permission to use the put and get
commands. However, you can retrieve the data file for the user history
reports regardless of access level.
H
You cannot put a configuration file to the factory.cfg or current.cfg files
under the system directory. Configuration files should be put to a customer
file (cust1.cfg or cust2.cfg), then loaded into the downloaded unit’s Current
Configuration via the menu-driven user interface.
H
You can only put a NAM program file (nam.ocd) into a NextEDGE system.
You cannot upload a NAM program file from the system.
H
Before you put a download file, you must use the bin (binary) command to
place the data connection in binary transfer mode.
H
When transferring SLV user history information to the NMS, you can only get
a uhbcfull.dat file. It is recommended that you use the NMS application to get
this information (see Transferring SLV Statistics to an NMS on page 10-43).
H
A data file (uhbcfull.dat or lmitrace.syc) cannot be put into a NextEDGE node.
H
LMI packet capture data (lmitrace.syc) is not readable when the LMI Packet
Capture Utility is active.
The system provides an additional feature that allows new software to be
downloaded in the background, using the selected bandwidth and without
interfering with normal operation. Downloads can be performed quickly, using the
full line speed, or at a slower rate over an extended period of time.
You initiate an FTP session to a system node in the same way as you would
initiate an FTP to any other IP-addressable device.
NOTE:
Loading a configuration with many DLCIs from a unit’s Customer
Configuration 1 or 2 option area into its Current Configuration area may take
time. Allow a minute or more for the downloaded file to be put into the unit’s
currently active configuration.
9191-A2-GH30-00
DRAFT — June 1999
10-39
" Procedure
To initiate an FTP session:
1. Start the FTP client program on your host. For example, on a Unix host,
type ftp and the NextEDGE system’s IP address.
2. If security is being enforced, enter your login ID and password. The FTP
prompt appears.
The starting directory is the root directory ( / ). Use standard FTP commands
during the FTP session, as well as the following remote FTP commands.
10-40
Command
Definition
cd directory
Change the current directory on the system node to the
specified directory.
dir [directory]
Print a listing of the directory contents in the specified directory.
If no directory is specified, the current one is used.
get file1 [file2]
Copy a file from the remote directory of the system node to the
local directory on the host (for configuration files only).
remotehelp
[command ]
Print the meaning of the command. If no argument is given, a
list of all known commands is printed.
ls [directory]
Print an abbreviated list of the specified directory’s contents.
If no directory is specified, the current one is used.
put file1 [file2]
Copy file1 from a local directory on the host to file 2 in the
current directory of the system node. If file2 is not specified,
the file will be named file1 on the system node.
recv file1 [file 2]
Same as a get.
send file1 [file 2]
Same as a put.
pwd
Print the name of the current directory of the system node.
bin
Places the FTP session in binary-transfer mode.
DRAFT — June 1999
9191-A2-GH30-00
Upgrading System Software
If you need to upgrade the NextEDGE system’s program code, you must transfer
the upgrade of the nam.ocd file in the system memory directory using the put
command.
NOTE:
Upgrades can be performed through the network using a Management PVC,
or through the COM port if Port Use is set to Net Link (see Table 9-15,
Communication Port Options).
" Procedure
To download software:
1. Initiate an FTP session to the device that you are upgrading.
2. Type bin to enter binary transfer mode.
3. Type hash to enter hash mode if you want to monitor the progress of the
upgrade, provided this function is supported by your equipment.
4. Type cd system to change to the system directory.
5. Perform a put of Rxxxxxx.ocd (xxxxxx being the software release number) to
the nam.ocd file to start the upgrade.
If the message displayed is . . .
Then . . .
nam.ocd: File Transfer Complete
The download was successful. The file is
loaded into system memory.
nam.ocd: File Transfer Failed –
Invalid file
The file is not valid for this system.
A different Rxxxxxx.ocd file will need to be
downloaded. Repeat the step or end the
FTP session.
NOTE:
During the download, a series of hash marks (#) appear. When the hash
marks stop appearing, there is a pause of about 30 seconds before the
nam.ocd: File Transfer Complete message appears. Please be
patient. Do not exit from FTP at this time.
! WARNING:
A put to current.cfg will replace all currently-configured configuration
options, including the node’s IP Address. Always put configuration files
to a customer configuration area so it can be modified before the file is
loaded into the current configuration.
See Changing Software on page 10-42 to activate the newly downloaded
software.
9191-A2-GH30-00
DRAFT — June 1999
10-41
Determining Whether a Download Is Completed
To see whether a download has completed, check the Identity screen (selected
from the Status menu). Check Alternate Software Rev. under the NAM Identity
column.
H
If a software revision number appears, the file transfer is complete.
H
If In Progress appears, the file is still being transferred.
H
If Invalid appears, no download has occurred or the download was not
successful.
Changing Software
Once a software upgrade is downloaded, it needs to be activated. When
activated, the unit resets, then executes the downloaded software. With this
feature, you control when the upgrade software is implemented.
" Procedure
To switch to the new software:
1. Go to the Control menu, and select Select Software Release.
Main Menu → Control → Select Software Release
The Select Software Release screen shows the currently loaded software
version and the new release that was just transferred.
If the download failed, Invalid appears in the Alternate Release field
instead of the new release number. Repeat the procedure on page 10-41,
Upgrading System Software, if this occurs.
2. Select Switch&Reset. The Are you sure? prompt appears.
3. Enter Yes. The unit resets and begins installing the newly transferred
software.
4. Verify that the new software release was successfully installed as the Current
Software Revision.
NOTE:
If someone opens a Telnet session and accesses the unit’s Identity
(identification) screen while the unit is downloading software, the
In Progress... message appears in the Alternate Software
Revision field.
See Displaying System Information on page 11-27 to see what is included in
the unit’s Identity screen.
10-42
DRAFT — June 1999
9191-A2-GH30-00
Transferring Collected Data
SLV user history statistics and LMI packet capture data can be uploaded to an
NMS or a Network Associates Sniffer using FTP, which is faster than other
methods. The rate at which the data file is transferred is the rate set by the FTP
MaxReceive Rate (Kbps) option (see the FTP Max Receive Rate (Kbps)
configuration option in Table 8-14, Telnet and FTP Session Options in Chapter 8,
Configuration).
NOTE:
Use your NMS application to FTP and view statistics and packet data.
Data files are not in user-readable format.
" Procedure
To retrieve data:
1. Perform Steps 1 through 3 in Upgrading System Software on page 10-41 to
initiate and set up an FTP session.
1. Initiate an FTP session to the device from which SLV statistics will be
retrieved.
2. Type cd data to change to the data directory.
If the retrieving . . .
Then . . .
SLV statistics
Perform a get of the uhbcfull.dat file.
H File Transfer Complete – Transfer was successful.
H File Transfer Failed – Transfer was not successful.
Try again or end the session.
LMI packet capture data
1. Stop the LMI Packet Capture Utility.
Main Menu → Control → LMI Packet Capture Utility
LMI packet capture data is not available (readable)
when the LMI Packet Capture Utility is Active.
2. Perform a get of the lmitrace.syc file.
One of the following will display for the file:
– File Transfer Complete
– File Transfer Failed
– Permission Denied – The LMI Packet Capture
Utility was not readable. Stop the LMI Packet
Capture Utility and try again.
3. Close the FTP session.
SLV statistics and/or LMI Packet Capture data are now available for reporting.
9191-A2-GH30-00
DRAFT — June 1999
10-43
10-44
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
11
The NextEDGE FrameSaver SLV module supports various LMI types, provides
switching capability, and performs continuous monitoring of the frame relay
physical and logical links. When combined with an ISDN DBM for frame relay
backup instead of relying on a router, better, faster, and easier backup can be
achieved.
This feature is only supported by the FrameSaver product, not theT1 TDM
product.
This chapter provides information for the following:
H
Dial Backup Applications on page 11-2.
— Backing Up to the Primary Destination Node on page 11-4.
— Backing Up to the Nearest Neighbor Node on page 11-6.
H
Our Philosophy on Backup on page 11-7.
— About the Automatic Backup Feature on page 11-7.
— Considerations When Setting Up Dial Backup on page 11-8.
— Before Starting on page 11-8.
H
Setting Up Dial Backup on page 11-9.
— Configuring the ISDN DBM Interface on page 11-10.
— Setting Up ISDN Link Profiles on page 11-15.
— Manually Creating Alternate DLCIs on ISDN Frame Relay Links at the
Central Site on page 11-18.
— Manually Adding Alternate Destinations on page 11-18.
— Setting Up Automatic Backup Configuration on page 11-23.
— Setting the Criteria for Automatic Backup on page 11-25.
— Configuring the DBM Interface to Send SNMP Traps on page 11-26.
9191-A2-GH30-00
DRAFT — June 1999
11-1
Dial Backup Modules
H
DBM Operation and Maintenance on page 11-27.
— Displaying Information About the DBM on page 11-27.
— Viewing DBM LEDs and Control Leads on page 11-28.
— Manually Forcing Backup (Disruptive) on page 11-30.
— Manually Placing a Call (Nondisruptive) on page 11-31.
— Verifying the ISDN Lines on page 11-32.
— Verifying That Backup Can Take Place on page 11-33.
— Upgrading ISDN DBM Software on page 11-34.
H
DBM Status Information on page 11-35.
— DBM Health and Status Messages on page 11-35.
— DBM Test Status Messages on page 11-38.
— PVC Connection Status on page 11-39.
— DBM Interface Status on page 11-40 (includes Last Cause Values).
H
DBM Call Performance Statistics on page 11-48.
— Clearing DBM Call Performance Statistics on page 11-48.
H
DBM Alarms on page 11-49.
— ISDN DBM Problems on page 11-51.
H
DBM Tests on page 11-52.
— ISDN PVC Tests on page 11-53.
Dial Backup Applications
Backup provides continuing service in case of a network, LMI, or PVC failure.
Being a frame relay aware product, the system continually monitors frame relay
physical and logical links to detect these failures.
If a PRI DBM is installed, up to 23 remote sites can be backed up simultaneously,
using a single B-channel per remote site. If a BRI DBM is installed, up to two
remote sites can be backed up simultaneously. Remote sites usually back up to
the central-site unit.
Here is how backup works:
1. When a network, LMI, or PVC failure is detected, the system generates an
alarm, which triggers an SNMP Trap.
2. If the system is configured for automatic backup and an alternate destination
circuit has been configured, the originating DBM places a call and the
answering device at the other end prepares to receive the call.
11-2
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
3. Once Caller ID is verified, a connection is established between the DBMs, the
NAM switches data to the backup link, the alternate path.
All reconfiguration and redirection occurs automatically within the unit,
entirely transparent to the connected DTE.
For circuit restoration:
1. When the system detects that normal service has been restored, the unit
clears the alarm and SNMP Trap.
2. Data is switched back to its original path and the backup link is disconnected.
A backup link is disconnected when:
— One of the devices in the backup link physically disconnects from the
ISDN.
— The backup link LMI has timed out.
— All alternate DLCIs on the backup link become inactive.
If the backup link is disconnected but a failure is still detected, the device
continues to try to reestablish the connection until the failure is no longer
detected or until backup is no longer needed.
The following sections discuss two backup applications: backing up to the primary
destination node, and backing up to an intermediate/neighboring node.
When backing up to a destination node, an alternate network like ISDN can be
used, or the service provider may provide access to ISDN lines through its own
network. Either way, the ISDN DBM supports a variety of backup schemes.
Refer to:
9191-A2-GH30-00
H
Setting Up for Dial Backup on page 11-9 for assistance configuring the
backup feature.
H
Controlling ISDN Access in Chapter 9, Security and Logins, for information
about the security provided data over the alternate/backup path.
DRAFT — June 1999
11-3
Dial Backup Modules
Backing Up to the Primary Destination Node
Many times it is desirable to backup directly to the ultimate destination node using
an alternate network like ISDN. This method allows systems equipped with ISDN
DBMs to bypass network problems completely. It also gives the operator more
control.
Alternate destination links are configured for the systems on each end of an ISDN
circuit so a frame relay link is set up over the ISDN line when the frame relay
network connection fails. In this way, systems can always establish a frame relay
user-to-network interface (UNI) between them, regardless of the type of service
used for backup.
It is important to note that since DLCI numbers are assigned by the local service
provider and they may not be the same number at both ends of the circuit, DLCI
numbers might not have significance to a destination unit. For NextEDGE
systems, the DLCI number for the primary destination link can be different from
the DLCI number for the alternate (backup) destination link. Configuring an
alternate destination link and DLCI number allows a direct backup connection to
be established by cross-matching a source unit’s DLCI number to an alternate
destination unit’s DLCI number.
The example below shows an application using an ISDN DBM to back up directly
to the primary/final destination.
Cluster
Controller
Frame
Relay
IBM FEP
FR
FR
ISDN
FRAD
PRI
BRI
Frame
Relay
Router
DBM
FR X
FR
NextEDGE
System with
PRI DBM
Frame
Relay
Network
PVC
FR = Frame Relay
Frame
Relay
Router
DBM
FR
FR
NextEDGE
System with
BRI DBM
Physical Connection
99-16402
PVC Connection
Backup Connection
11-4
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
The next example shows a T1 frame relay backup application to illustrate how
remote sites can maintain connectivity with the central site when a failure occurs.
The system at the central site is equipped with an ISDN PRI DBM. This provides
simultaneous backup for up for 23 remote locations. One remote system is also
equipped with an ISDN PRI DBM, while the other sites are equipped with an
ISDN BRI DBM. The ISDN BRI DBM provides simultaneous backup for up to two
other sites.
DLCI number mapping is also provided during backup so redundant DLCI
number issues are avoided since these numbers only have local significance.
NextEDGE
System with
BRI DBM
Token
Ring
Frame
Relay
Router
Frame
Relay
Network
NextEDGE
System with
PRI DBM
Frame
Relay
IBM FEP
T1
X
T1
X
T1
X T1
DBM
PVCs
DBM
BRI
PRI
ISDN
Physical Connection
PVC Connection
PRI
Frame
Relay
Router
NextEDGE
System with
Frame
BRI DBM Relay Cluster
Controller
NextEDGE
System with
PRI DBM
BRI
FR = Frame Relay
DBM
Frame
Relay Cluster
Controller
DBM
Frame
Relay
Router
Frame
Relay Cluster
Controller
Frame
Relay
Router
99-16385
Backup Connection
9191-A2-GH30-00
DRAFT — June 1999
11-5
Dial Backup Modules
Backing Up to the Nearest Neighbor Node
Sometimes it is desirable to backup to a neighboring node like a regional node
(e.g., when the system is part of a mesh or partial-mesh network, or when only
selected systems are to place backup calls to the central site).
When the regional node receives a call from its nearest neighbor, the system
switches the remote system’s alternate destination traffic with its own primary
traffic, then sends the traffic to the frame relay network.
The application example below shows a remote unit backing up to a neighboring
unit, both equipped with an ISDN DBM, using the Auto Backup feature.
NextEDGE
System with
BRI DBM
Token
Ring
Remote
Site
DBM
Token
Ring
Frame
Relay
Router
ISDN
Central
Site
NextEDGE
System
Frame
Relay
Router
X
DBM
Frame
Relay
Network
Physical Connection
NextEDGE
System with
BRI DBM
Regional
Backup
Site
PVC Connection
Backup Connection
99-16386
Extra CIR for network DLCIs and/or additional network DLCIs may need to be
provisioned with/by the network provider to implement this application.
11-6
H
If multiplexed DLCIs are used, CIR for the network DLCIs between the
regional and central sites may need to be increased to allow for the additional
backup traffic (DLCIs plus the EDLCIs) depending upon the behavior of the
service provider’s network.
H
If standard DLCIs are used, additional network DLCIs between the regional
and central sites (the regional unit’s DLCIs plus the remote unit’s DLCIs)
must be provisioned for use during backup.
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Our Philosophy on Backup
NextEDGE/FrameSaver backup configuration is very flexible, allowing for many
different approaches to implementing a network backup topology. Since data
flows from remote sites to the central site in most network topologies, it is
recommended that this approach also be used when configuring the backup
feature. When this approach is followed, configuration of the backup feature is
greatly simplified so that remote-site units are generally plug-and-play and most
of the configuration is done at the central-site system.
The following guidelines apply when following this recommendation.
H
Central site configuration guidelines:
— Configure a Link Profile for each remote site.
— Configure the system to answer calls from the remote sites.
— Leave Automatic Backup Configuration disabled.
— Manually create alternate DLCIs on the ISDN Backup Link for each
remote-site ISDN Link Profile.
— Manually specify ISDN DLCIs as alternate DLCIs for the PVC Connection
after the primary DLCIs have been automatically discovered from the
primary network Link LMI or manually configured.
H
Remote site configuration guidelines:
— Configure a Link Profile for the central site in the first link profile,
called HQ_Site.
This ensures that a backup DLCI will be created automatically on the
backup link for each DLCI discovered on the network interface using the
central site’s link profile.
— Configure the unit to originate calls to the central site. The default
configuration for an ISDN PRI DBM is to answer calls, while the default
for an ISDN BRI DBM is to originate calls.
— Enable the Automatic Backup Configuration feature if the system is
configured to originate calls.
About the Automatic Backup Feature
The Automatic Backup Configuration feature is used to automatically create
alternate DLCI records and PVC connections on the ISDN DBM (backup)
interface. This feature should be disabled for a site configured to answer, which is
typically the central site.
Automatic backup can be changed at any time via the Auto Backup Criteria
configuration options. Specific days and times that backup will be allowed can
also be specified. See Setting Up Automatic Backup Configuration on page 11-23
for additional information.
9191-A2-GH30-00
DRAFT — June 1999
11-7
Dial Backup Modules
Considerations When Setting Up Dial Backup
We recommend that you decide how to configure the NextEDGE system before
actually configuring it.
When setting up the NextEDGE system for backup, you need to:
H
Arrange for ISDN service.
H
Determine whether you will be using the Auto-Configuration feature. Refer to
Setting Up Automatic Backup Configuration on page 11-23.
Before Starting
Obtain the following information:
H
Verification of the type of ISDN switch.
— For a BRI DBM: NI-1
— For a PRI DBM: NI-2, ATT 4ESS, or ATT 5ESS
H
Verification of the type of ISDN service.
— For a BRI DBM: Capability Package B for 1B-service or Capability
Package ( I ) for 2B Service for an ISDN BRI DBM – Supports up to two
circuit-switched B-channels, BRI-B1 and BRI-B2, each with one Service
Profile Identification (SPID) number and one local phone number.
— For a PRI DBM: 23B with one phone number and Circuit Switched Data
capability.
H
Verification of CNIS (calling number identification service) for answering unit.
H
Number of digits used for the Outbound Phone Number or Inbound Calling ID
(the ISDN Link Profile formats).
Example:
A 10-digit format with the area code included may be used for the Inbound
Calling ID (8135309999), while a 7-digit format without the area may be used
for the Outbound Phone Number (5309999).
H
Actual phone number(s) for the DBM.
H
For a BRI DBM, obtain the SPID (service profile identification) numbers.
Order BusyCall Forwarding if more than one phone number will be used so
that calls will be forwarded to the second B-channel when the primary
B-channel is busy.
11-8
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Setting Up Dial Backup
To set up dial backup at an originating site (typically the remote site), you
need to:
H
Configure the ISDN DBM interface (see page 11-10).
H
Create an ISDN Link Profile for the central site (see page 11-15).
H
Set up Automatic Backup Configuration (see page 11-23).
H
Enable Automatic Backup and specify restrictions on when backup can occur
(see page 11-25).
H
Configure the DBM interface to originate SNMP Traps (see pageNO TAG).
This section includes Last Cause Values.
H
Verify the ISDN lines (see page 11-32).
H
Verify that backup can take place (see page 11-33).
To set up dial backup at an answering site (typically the central site), you
need to:
9191-A2-GH30-00
H
Configure the ISDN DBM interface (see page 11-10).
H
Set up an ISDN Link Profile for each remote site (see page 11-15).
H
Manually create DLCI records on the ISDN frame relay links (see
page 11-18).
H
Manually change the PVC Connection being backed up to the alternate
destination (see page 11-18).
H
Enable Automatic Backup and specify restrictions on when backup can occur
(see page 11-23).
H
Configure the DBM interface to originate SNMP Traps (see pageNO TAG).
This section includes Last Cause Values.
H
Verify the ISDN lines (see page 11-32).
H
Verify that backup can take place (see page 11-33).
DRAFT — June 1999
11-9
Dial Backup Modules
Configuring the ISDN DBM Interface
When configuring systems with an ISDN BRI DBM, one unit’s DBM must be
configured to originate backup and the other unit’s DBM must be configured to
answer a backup call. The default setting for a PRI DBM (typically used at a
central site) is Answer, while the default setting for a BRI DBM is Originate.
If a PRI DBM is at both ends of the circuit, the setting for the Originate or Answer
option at the remote site needs to be changed to originate a call. If a BRI DBM is
at both ends of the circuit, the setting for the Originate or Answer option at the
cental site needs to be changed to answer a call.
" Procedure
To configure the DBM interface:
1. Select Physical from the ISDN menu.
Main Menu → Configuration → ISDN → Physical
2. Enable the DBM interface (the Interface Status option).
3. Make sure the remote site is configured to originate calls and the central site
to answer calls (the Originate or Answer option on page 11-14).
4. In addition, configure the following:
For a PRI DBM
For a BRI DBM
Enter the Local Phone Number.
Configure the B-channels:
Configure T1 physical characteristics to
match the service provider’s settings:
H Service Profile ID1 (SPID)
H Line Framing Format
– If ESF, Network Initiated PLB
– If ESF, ANSI Performance Report
Messages
– If ESF, Excessive Error Rate
Threshold
H Local Phone Number 1
H Service Profile ID2 (SPID)
H Local Phone Number 2
H Line Build Out (LBO)
H Network Initiated LLB
H Circuit Identifier
5. Save the configuration.
When configuring a PRI DBM, refer to Table 11-1 on page 11-11.
When configuring a BRI DBM, refer to Table 11-2 on page 11-14.
11-10
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Table 11-1. ISDN PRI Physical Interface Options (1 of 3)
Interface Status
Determines whether the ISDN interface is available for use.
Enable – The ISDN interface is enabled.
Disable – The ISDN interface cannot be configured, nor can it transmit or receive data.
No PVC connections or frame relay DLCIs will be deleted. Disabling the ISDN interface
results in the following:
H All currently connected ISDN calls are terminated.
H Alarms or traps associated with this interface are not generated or displayed.
H LEDs associated with this interface are held in an “off” state. Specifically, the
DSX/PRI LEDs are held off if they represent the PRI status.
Originate or Answer
Possible Settings: Originate, Answer
Default Setting: Answer
Specifies whether the access unit’s DBM will originate or answer dial backup calls. The
DBM at one end of the circuit must be configured to originate calls, while the other must
be configured to answer calls.
Originate – Places dial backup calls; the recommended setting for a remote site DBM.
Answer – Answers dial backup calls; the recommended setting for a central site DBM.
Switch Type
Possible Settings: NI-2, ATT_4ESS, ATT_5ESS
Default Setting: NI-2
Specifies type of ISDN switch provided by the server.
NI-2 – The DBM will communicate with a service provider supporting the National
ISDN-2 switching standard.
ATT_4ESS – The DBM will communicate with a service provider supporting the ATT
4ESS switching standard.
ATT_5ESS – The DBM will communicate with a service provider supporting the ATT
5ESS switching standard.
Network Initiated PLB
Allows the initiation and termination of the payload loopback (PLB) to be controlled by
the receipt of PLB-Actuate and PLB-Release commands from the ISDN.
to ESF.
Enable – PLB is controlled by PLB-Actuate and PLB-Release commands. Receiving a
PLB-Actuate command causes the system to enter a payload loopback (provided a PLB
can be performed in the system’s current state). Receiving a PLB-Release command
terminates the PLB.
Disable – The system ignores the PLB-Actuate and PLB-Release commands.
NOTE:
9191-A2-GH30-00
When disabled, the unit is not in compliance with ANSI T1.403 or
AT&T TR 54016.
DRAFT — June 1999
11-11
Dial Backup Modules
ANSI Performance Report Messages
Specifies whether ANSI T1.403 compliance performance report messages (PRMs) are
generated and sent to the ISDN over the ESF facility data link every second.
to ESF.
Enable – Generates and sends PRMs.
Disable – Does not generate and send PRMs.
Sets the error rate threshold that determines when an EER condition is declared. The
excessive error rate is determined by the ratio of the number of CRC6 errors to the total
number of bits received over a set period of time.
to ESF.
10E-4 – Declares an EER if more than 1,535 CRC6 errors are detected in a 10 second
period.
period or a 10 – 4 condition occurs. Clears when fewer than 922 CRC6 errors are
period or a 10 – 5 or 10 – 4 condition occurs. Clears when fewer than 93 CRC6 errors are
period or a 10 – 6, or 10 – 5, or 10 – 4 condition occurs. Clears when fewer than 10 CRC6
intervals or a 10 – 7, 10 – 6, 10 – 5, 10 – 4 condition occurs. Clears when fewer than
intervals or a 10 – 8, 10 – 7, 10 – 6, 10 – 5, or 10 – 4 condition occurs. Clears when fewer
than 5 CRC6 errors are detected within the same time period.
Local Phone Number
Possible Settings: 10 digits
Provides the telephone number associated with all Bearer channels. All blanks is a valid
setting.
10 digits – Where you enter the telephone number. If a nondigit/numeric is entered, an
Invalid Character (x) message appears at the bottom of the screen. If fewer
than 7 digits/numerics are entered, an Invalid – Phone number must be at
least 7 digits message appears at the bottom of the screen.
Clear – Clears the phone number field so it can be reentered.
11-12
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Line Framing Format
Specifies the framing format for transmitted and received signals on the ISDN interface.
NOTE:
This setting is not recommended by network carriers. False yellow alarms
may occur after traffic has been running and the channel returns to idle, or
when there is light traffic when other settings are selected. ESF format
does not create this problem.
ESF – Uses Extended Superframe framing format.
Line Build Out (LBO)
Possible Settings: 0.0, –7.5, –15, –22.5
Specifies the line build out for the signal transmitted to the ISDN.
0.0, –7.5, –15, –22.5 – Specifies line build out in dB.
Network Initiated LLB
Allows the initiation and termination of the line loopback (LLB) to be controlled by the
receipt of LLB-Actuate and LLB-Release commands from the ISDN.
Enable – LLB is controlled by LLB-Actuate and LLB-Release commands. Receiving a
LLB-Actuate command causes the system to enter a line loopback (provided an LLB
can be performed in the system’s current state). Receiving an LLB-Release command
terminates the LLB.
Disable – The system ignores the LLB-Actuate and LLB-Release commands.
NOTE:
When disabled, the system is not in compliance with ANSI T1.403 or
AT&T TR 62411.
Circuit Identifier
Possible Settings: Text Field, Clear
Default Setting: blank
Identifies the transmission vendor’s circuit information to facilitate troubleshooting.
Text Field – Edit or display circuit identifier information (maximum 255 characters).
Clear – Removes the circuit identifier information.
9191-A2-GH30-00
DRAFT — June 1999
11-13
Dial Backup Modules
Table 11-2. ISDN BRI DBM Physical Interface Options
Interface Status
Determines whether the ISDN interface is available for use.
Enable – The ISDN interface is enabled.
Disable – The ISDN interface cannot be configured, nor can it transmit or receive data.
No PVC connections or frame relay DLCIs will be deleted. Disabling the ISDN interface
results in the following:
H All currently connected ISDN calls are terminated.
H Alarms or traps associated with this interface are not generated or displayed.
Originate or Answer
Possible Settings: Originate, Answer
Default Setting: Originate
Specifies whether the unit’s DBM will originate or answer dial backup calls. The DBM at
one end of the circuit must be configured to originate calls, while the other must be
configured to answer calls.
Originate – Places dial backup calls; the recommended setting for a remote site DBM.
Answer – Answers dial backup calls; the recommended setting for a central site DBM.
Service Profile ID (SPID)
Possible Settings: 3 – 20 digits
Specifies the SPID number assigned by the ISDN service provider for Bearer channel 1
(B1) and Bearer channel 2 (B2). SPID numbers are used by the switch to identify which
ISDN services the DBM can access. All blanks is a valid setting.
3 – 20 digits – You can enter a SPID number, or you can leave blanks. If a nondigit/
numeric is entered, an Invalid Character (x ) message appears at the bottom of
the screen. If fewer than three digits/numerics are entered, an Invalid – SPID must
be at least 3 digits message appears at the bottom of the screen.
Clear – Clears the SPID field so it can be reentered.
Local Phone Number 1 or 2
Possible Settings: 10 digits
Provides the telephone number associated with Bearer channel 1 (B1) and 2 (B2). All
blanks is a valid setting.
10 digits – Enter the telephone number. If a nondigit/numeric is entered, an
Invalid Character (x ) message appears at the bottom of the screen. If fewer
than 7 digits/numerics are entered, an Invalid – Phone number must be at
least 7 digits message appears at the bottom of the screen.
Clear – Clears the phone number field so it can be reentered.
11-14
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Setting Up ISDN Link Profiles
When the system is equipped with an ISDN DBM, ISDN link profiles must be set
up for each device at the other end of an alternate (backup) link.
H
For the central site DBM, a link profile is set up for each remote device.
H
For a remote site DBM, a link profile is set up for the central site.
If there is a failure in the primary link or DLCI for which you are creating an
alternate link, then the DBM performs based upon the ISDN Originate or Answer
(see Table 11-1, ISDN PRI DBM Physical Interface Options, or Table 11-2, ISDN
BRI DBM Physical Interface Options) and the ISDN Link Profile Link Status
configuration option settings (see Table 11-3, ISDN Link Profile Options).
If ISDN Physical option And ISDN LInk Profile
Originate or Answer is
set to . . .
Link Status Option is
set to. . .
Originate
Auto
Dial the Outbound Phone
Number that you have specified
for this link.
Answer
Auto
Wait for a call from one of the
Inbound Calling IDs that you
have specified for this link. When
the primary link recovers, the call
will be disconnected.
Originate or Answer
Disable
Terminate any existing ISDN
call(s) associated with this link
profile and will not originate any
future calls for this link profile.
Then the DBM will . . .
In addition to backup, any time a Primary Destination or Source DLCIs for this link
profile has been configured (see Table 11-4, PVC Connection Options), the
specified link profile will become active. The DBM then performs based upon the
ISDN Originate or Answer (see Table 11-1, ISDN PRI DBM Physical Interface
Options, or Table 11-2, ISDN BRI DBM Physical Interface Options) and the ISDN
Link Profile Link Status configuration option settings (see Table 11-3, ISDN Link
Profile Options).
When no ISDN Link Profiles have been configured, No ISDN Link Profiles
displays. Otherwise, up to 10 previously configured profiles display on one screen
in the order they were defined. ISDN Link Profiles are only displayed for links with
nonnull link names.
When creating an ISDN Link Profile and the maximum number of link profiles
have been configured, Limit of ISDN Link Profiles Reached displays
at the bottom of the screen. When this occurs, another link profile must be
deleted before a new link profile can be created.
9191-A2-GH30-00
DRAFT — June 1999
11-15
Dial Backup Modules
" Procedure
To set up or change link profiles:
Main Menu → Configuration → ISDN → Link Profiles
2. Select New and the ISDN Link Profile Entry screen appears.
3. Enter a name for the destination (e.g., Tampa). Up to 8 characters can be
entered.
Use Clear to remove all characters in a field if you want to start over. Using
Clear for the Link Name field sets the Link Name to null and all outbound and
inbound numbers are also cleared.
4. Set the Link Satus for Auto (press the spacebar so that Auto appears).
5. Enter phone numbers.
Originating DBM
Answering DBM
Outbound phone number.
Valid characters can include:
Inbound Calling ID1 and ID2. These are
the phone numbers of units that calls will
be accepted from.
H Numbers (0 – 9)
H Special characters * and #
Valid characters can include:
H Spaces
H Numbers (0 – 9)
See Table 11-3, ISDN Link Profiles, on page 11-17 for additional information.
If setting up a central site unit, go to Manually Creating Alternate DLCIs on ISDN
Links at the Central Site on page 11-18. If setting up a remote site unit, go to
Setting Up Automatic Backup Configuration on page 11-23.
11-16
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Table 11-3. ISDN Link Profiles
Link Name
Possible Settings: ASCII Text
Default Setting: HQ_Site, blank
Assigns the name used for the ISDN link profile. It is generally the backup destination
for a frame relay link. Each profile must have a unique link name. If the link name field is
blank, the link profile will be deleted. Use ASCII text, 8 characters maximum.
HQ_Site – The link name configured in the remote site unit (originating a backup call)
for the central site unit (answering a backup call). One link has a default value of
HQ_Site to allow for Automatic Backup Configuration.
NOTE:
To prevent confusion, do not use the following link names: Network,
Net1-FR1, or SxPort-n. These names will be treated as nonunique.
Link Status
Possible Settings: Auto, Disable
Determines whether the ISDN Frame Relay link is in or out of service.
Auto – The link is configured to be in service when needed. Packets will be transmitted
and received on the interface, and the LMI for a PVC connection will become active
when the link is required.
Disable – The frame relay link is out of service. No data will be transmitted or received
on the interface.
Outbound Phone Number
Possible Settings: 0 – 9, *, #, <space>, ( _ ), or –
Default Setting: none
Specifies the phone number to call (the called party ID). Up to 36 digits can be entered.
Display Conditions – This option only appears when Originate or Answer is set to
Originate (see Table 11-1, ISDN PRI Physical Interface Options, or Table 11-2, ISDN
BRI Physical Interface Options).
Inbound Calling ID 1 or 2
Default Setting: none
Specifies the phone number to accept calls from (calling party IDs). Up to 18 digits can
be entered.
Display Conditions – This option only appears when Originate or Answer is set to
Answer (see Table 11-1, ISDN PRI Physical Interface Options, or Table 11-2, ISDN
BRI Physical Interface Options).
NOTE:
Inbound Calling ID 2 is only useful when multiple local phone numbers are
programmed at the originating site (e.g., a 2B+D BRI location).
CAUTION: All calling party IDs must be unique across all of the enabled DBM call
profiles. This ensures that the DBM installs the correct backup
configuration on answering, since the calling party ID is used to identify
the remote unit and to determine which PVC mappings to use.
9191-A2-GH30-00
DRAFT — June 1999
11-17
Dial Backup Modules
Manually Creating Alternate DLCIs on ISDN Links at the Central Site
This can be done automatically using the Automatic Backup Configuration feature
(see Setting Up Automatic Backup Configuration on page 11-23). However, a
central site generally needs to manually configure DLCI records on multiple ISDN
frame relay links for ISDN backup capability and multiple link profiles are not
created when using the Automatic Backup Configuration feature.
" Procedure
To manually configure DLCI Records for the link:
1. Select DLCI Records for the ISDN link:
Main Menu → Configuration → ISDN → DLCI Records
2. Select the desired ISDN Link Profile (an ISDN Link Name), then select
New or Modify.
3. Configure the ISDN link DLCI like any other DLCI record.
Manually Adding Alternate Destinations
This procedure can also be performed automatically through the
Auto-Configuration feature, Automatic Backup Configuration (see page 11-23).
Refer to Table 11-4 on page 11-19 for backup-related PVC connection options
and Table 11-5 on page 11-21 for backup-related management PVC options.
An ISDN Link Name can be specified for a dial backup connection. This can be
any non-null link name configured on an ISDN frame relay link.
" Procedure
1. Follow the appropriate menu selection sequence:
Main Menu → Configuration → PVC Connections or
Management PVCs
2. Select the Modify function key. The message Modify Connection ID
appears.
3. Select the PVC to be backed up, then add or modify the following alternate
destination (backup) information:
— Enter the name for the Alternate Destination Link (the ISDN Link Profile
Name).
— Enter the DLCI to be used as the Alternate Destination DLCI.
— If it is a multiplexed DLCI, enter the Alternate Destination EDLCI.
11-18
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Source Link
Possible Settings: SxPort-n, ISDN Link Name, Net1-FR1
Specifies the frame relay interface that starts a PVC connection; the from end of a
interfaces that have at least one DLCI or EDLCI defined that are not part of a PVC
connection or management link. For example, if Port-1 has no DLCIs defined, Port-1
would not appear as a valid setting.
SxPort-n – Specifies the port n in slot x as the source link. Refers to frame relay links on
the user data port as the frame relay link. (see Table 8-6, Data Port Physical Options).
ISDN Link Name – Specifies the ISDN link of the DBM as the source link. This can be
any nonnull link name configured on an ISDN frame relay link.
Net1-FR1 – Specifies the Network interface as the source link.
Clear All – Clears all Link and DLCI settings, and suppresses EDLCIs.
Source DLCI
Specifies the source DLCI for a frame relay interface. The DLCI must be defined and
cannot be part of a PVC connection or management link. For multiplexed DLCIs, at least
one EDLCI must be unconnected for the DLCI to be a valid selection.
NOTE:
Source DLCI has no value if Source Link contains no value.
Source EDLCI
Specifies the source Embedded Data Link Connection Identifier (EDLCI) for a frame
relay interface when a multiplexed DLCI record is selected as one end of a connection.
Display Conditions – This option only appears when Source DLCI contains a
multiplexed DLCI record number.
Primary Destination Link
Specifies the frame relay interface used as the primary destination link; the to end of a
interfaces that have at least one DLCI or EDLCI defined which are not part of a PVC
connection or management link. For example, if the network interface has no DLCIs
defined, Net1-FR1 would not appear as a valid setting.
connection. This can be any nonnull link name configured on an ISDN frame relay link.
9191-A2-GH30-00
DRAFT — June 1999
11-19
Dial Backup Modules
Primary Destination DLCI
Specifies the primary destination DLCI for a frame relay interface. The DLCI must be
defined and cannot be part of a PVC connection or management link. For multiplexed
DLCIs, at least one EDLCI must be unconnected for the DLCI to be a valid selection.
NOTE:
Primary Destination DLCI has no value if Primary Destination Link contains
no value.
Primary Destination EDLCI
Specifies the primary destination Embedded Data Link Connection Identifier (EDLCI) for
a frame relay interface when a multiplexed DLCI record is selected as one end of a
connection.
Display Conditions – This option only appears when the Primary Destination DLCI
Alternate Destination Link
Specifies the frame relay interface used as the alternate destination link; the to end of a
from-to link that is used for backup when the primary destination link or DLCI is out of
service. The only valid settings for this configuration option are frame relay interfaces
that have at least one DLCI or EDLCI defined which are not part of a PVC connection or
management link. For example, if ISDN Link Name has no DLCIs defined, the ISDN link
name would not appear as a valid setting.
Net1-FR1 – Specifies the Network interface as the alternate destination link.
ISDN Link Name – Specifies the ISDN link of the DBM interface as the alternate
destination of the connection. This can be any non-null link name configured on an
ISDN frame relay link.
Clear Alternate – Clears the Alternate Destination Link and Alternate Destination DLCI
settings, and suppresses Alternate Destination EDLCI.
Alternate Destination DLCI
Specifies the alternate destination Data Link Connection Identifier (DLCI) for a frame
relay interface used for backup. The DLCI must be defined and cannot be part of a PVC
connection or management link. For multiplexed DLCIs, at least one EDLCI must be
unconnected for the DLCI to be a valid selection.
Display Conditions – This option does not appear when the Alternate Destination Link
contains no value.
11-20
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Alternate Destination EDLCI
Specifies the alternate destination Embedded Data Link Connection Identifier (EDLCI)
for a frame relay interface when a multiplexed DLCI record is selected as one end of a
backup connection.
Display Conditions – This option only appears when the Alternate Destination DLCI
See Configuring PVC Connections in Chapter 8, Configuration, for information
about other PVC Connection configuration options.
Primary Link
Possible Settings: Net1-FR1, SsPort-n, ISDN Link Name, Clear
Specifies the frame relay interface to use for this management PVC. The interface
selected must have at least one DLCI (or DLCI with EDLCI) defined, which is not part of
a PVC connection or already assigned as a management PVC.
Net1-FR1 – Specifies the network interface as the source link for the connection.
SsPort-n – Specifies the frame relay link on Slot s, Port n as the destination link for the
connection.
ISDN Link Name – Specifies the ISDN link on the DBM to be used in the connection.
installed DBM.
was multiplexed.
Alternate Link
Possible Settings: Net1-FR1, ISDN Link Name, Clear
Specifies the frame relay interface to use for this management PVC as the alternate
link. The interface selected must have at least one DLCI (or DLCI with EDLCI) defined,
which is not part of a PVC connection or already assigned as a management PVC.
Net1-FR1 – Specifies the Network interface as the alternate frame relay link.
ISDN Link Name – Specifies the ISDN link of the DBM to be used in the connection.
This can be any non-null link name configured on an ISDN frame relay link.
was multiplexed.
9191-A2-GH30-00
DRAFT — June 1999
11-21
Dial Backup Modules
Alternate DLCI
Specifies the alternate DLCI number to be used for the management PVC after the
frame relay interface is selected.
Display Conditions – The DLCI cannot be entered if the Link field is blank.
NOTE:
Clearing Link also clears the DLCI.
Alternate EDLCI
Specifies the alternate EDLCI number used for a management PVC when a multiplexed
DLCI is selected for the frame relay link. EDLCIs identify individual connections within
multiplexed DLCIs that are unique to those DLCIs.
Display Conditions – This option does not appear if the DLCI does not reference a
multiplexed DLCI.
NOTE:
Clearing the DLCI or changing it to a standard DLCI suppresses the EDLCI
field.
These options do not apply when the Management PVC is designated as a
TS Management Link. See Configuring Node IP Options on page 8-56 for
See Configuring Management PVCs in Chapter 8, Configuration, for information
about other Management PVC configuration options.
11-22
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Setting Up Automatic Backup Configuration
When a DBM is installed and enabled, the Auto-Configuration feature allows you
to select automatic configuration for backup, as well as for DLCI record
configuration and connection within the unit.
Main Menu → Auto-Configuration
Automatic Backup Configuration only appears when an ISDN DBM is present. It
is used to automatically create alternate DLCI records and PVC connections on
the ISDN DBM (backup) interface for current or newly discovered PVC
Connections and Management PVCs.
If this feature is . . .
Then . . .
Enabled
Appropriate DLCIs are automatically configured on the
first ISDN link, and all network primary destination PVC
connections and managment PVCs are updated to include
alternate destination DLCIs with the same number as the
network DLCIs. This is the default setting for an ISDN BRI
DBM.
Disabled
No automatic configuration takes place on the DBM
interface and no alternate destinations are created for
PVCs. This is the default setting for an ISDN PRI DBM.
Since a central site DBM generally needs ISDN links for multiple remote sites and
a remote site DBM only needs one ISDN link to the central site DBM, this feature
should be disabled for a central site DBM (configured to answer backup calls) but
enabled for a remote site DBM (configured to originate a backup call).
The default settings for the DBM are based upon the assumption that the
central-site DBM is equipped with an ISDN PRI DBM, and a remote-site DBM is
equipped with an ISDN BRI DBM. However, the setting can be changed at any
time from this menu.
9191-A2-GH30-00
DRAFT — June 1999
11-23
Dial Backup Modules
When the Automatic Backup Configuraiton setting is changed, one of the
following prompts appears. No is the default for these prompts.
Prompt
Appears When . . .
Description
Delete All Alternate
Destinations from
PVC Connections?
Automatic Backup
Configuration is
disabled.
If Yes (y) is selected, all Alternate
Destination information is removed from
PVC connections and Management PVCs,
and all DLCIs used exclusively for alternate
destinations are deleted.
If No (n) is selected, no previously
configured DLCIs or PVC connections are
removed or changed, and newly
discovered DLCIs will be configured
according to the new discovery mode and
automatic backup settings.
Add Alternate
Destinations to
Current PVC
Connections?
Automatic Backup
Configuration is
enabled.
If Yes (y) is selected, DLCI records are
configured on the first ISDN link and
Alternate Destination information is added
to current PVC connections and
management PVCs.
If No (n) is selected, no previously
configured PVC connections are changed,
and newly discovered DLCIs will be
configured according to the new discovery
mode and automatic backup settings.
Changes must be saved to take effect.
NOTE:
When DLCIs, PVC connections, and management PVCs for the first ISDN
link profile have been configured manually, it is recommended that specific
discovered DLCIs, PVC connections, and management PVCs be deleted
manually via the Configuration menus. Otherwise, the manual configurations
will be deleted along with the automatically configured ones.
To specify when automatic backup is allowed or can occur, see Setting the
Criteria for Automatic Backup on page 11-25.
11-24
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Setting the Criteria for Automatic Backup
Select Auto Backup Criteria to change or display the configuration option that
determines whether and when automatic backup is allowed. The criteria for
automatic backup is set up on the originating DBM only.
Main Menu → Configuration → Auto Backup Criteria
Table 11-6. Auto Backup Criteria Options (1 of 2)
Auto Backup
Determines whether backup for the system is automatically performed when the primary
physical link or LMI, or a DLCI on a PVC connection fails.
When enabled, the system automatically enables the Alternate Destination Link and
reroutes traffic over the backup interface. (See Table 11-4, PVC Connection Options
and Table 11-5, Management PVCs Options, to configure the Alternate DLCI and
Alternate EDLCI.)
NOTE:
Auto Backup cannot be enabled unless LMI Behavior is set to Independent
(see Table 8-1, System Frame Relay and LMI Options).
Enable – Automatically reroutes traffic over the backup (alternate) interface when a
failure is detected.
Disable – Does not reroute traffic.
When Auto Backup Allowed
Possible Settings: Always, Restrict
Default Setting: Always
Determines when backup for the system is allowed to occur.
Always – No restrictions on backup. Backup can occur any day, any time.
Restrict – Backup is restricted to the day and time selected in the following
configuration options. Use this selection when the importance of the data that you are
backing up is day/time dependent.
Backup Allowed: Day From nn:nn
Possible Settings: 00:00 – 23:00, None
Default Setting: 00:00
Specifies the time that Auto Backup can begin for a selected day of the week in
increments of 1 hour. Day is Monday through Sunday.
00:00 – 23:00 – Specifies the time of day that Auto Backup will start for this
particular day. For example, if you enter 13:00, then auto backup is allowed beginning at
1 p.m. for this day.
None – Auto Backup cannot occur on this day. For example, if you enter None by
Monday, then auto backup can occur on any day but Monday.
9191-A2-GH30-00
DRAFT — June 1999
11-25
Dial Backup Modules
Table 11-6. Auto Backup Criteria Options (2 of 2)
Backup Allowed: Day To nn:nn
Possible Settings: 00:00 – 24:00
Default Setting: 24:00
Specifies the time that Auto Backup must end occurring for the selected day of the week
in increments of 1 hour.
Display Conditions – This option only appears if a start time was specified.
00:00 – 24:00 – Specifies the time of day that Auto Backup will stop for this
particular day. For example, if you enter 15:00, then auto backup is forbidden after
3 p.m. for this day.
Configuring the DBM Interface to Send SNMP Traps
The ISDN DBM interface can be specified as an interface that monitors and
generates SNMP traps:
Main Menu → Configuration → Management and Communications →
SNMP Traps
The configuration options for doing this include:
H
Link Trap Interfaces
H
DLCI Traps on Interfaces
When DBM is selected, trap messages are generated for linkUp and linkDown
events on DLCIs and frame relay links for the originating DBM interface only.
See Configuring SNMP Traps and Trap Dial-Out Option Differences on page 8-68
for more about SNMP trap configuration.
See Configuring SNMP Traps and Trap Dial-Out in Chapter 8, Configuration, for
more about SNMP trap configuration.
11-26
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
DBM Operation and Maintenance
This section includes the following:
H
Displaying Information About the DBM (see below).
H
Viewing DBM LEDs and Control LEDs on page 11-28.
H
Manually Forcing Backup (Disruptive) on page 11-30.
H
Manually Placing a Call (Nondisruptive) on page 11-31.
H
Verifying the ISDN Lines on page 11-32.
H
Verifying That Backup Can Take Place on page 11-33.
H
Upgrading ISDN BRI DBM Software on page 11-34.
Displaying Information About the DBM
Information about the ISDN DBM can be found on the Identity screen.
" Procedure
To view information about the DBM:
2. Select System & NAM to view System, NAM, and DBM information. The
following DBM information is provided:
Card Type
The type of dial backup module, ISDN-BRI or ISDN-PRI.
H Unsupport indicates that an unsupported DBM is installed.
H Failed indicates that the DBM has failed.
Software Revision
Software version currently being used by the DBM.
Format nn.nn.nn consists of a 6-digit number that represents
the major and minor revision levels.
For an ISDN-PRI DBM, None displays because the DBM does
not have loaded software; it runs from the NAM’s software.
Hardware Revision
DBM’s hardware version. Format nnnn-nnx consists of a
4-digit number, followed by two digits and one alphabetic
character.
For System and NAM information, see Displaying System Information in
Chapter 10, Operation and Maintenance.
9191-A2-GH30-00
DRAFT — June 1999
11-27
Dial Backup Modules
Viewing DBM LEDs and Control Leads
Display LEDs and Control Leads information for an ISDN DBM is with the NAM
information. No other screen is needed. This feature is selected from the Status
menu.
Main Menu → Status → Display LEDs and Control Leads
NAM with an ISDN DBM Example
main/status/leds
Device Name: Node A
PARADYNE 9191
1/26/1998 23:32
GENERAL
OK
Alarm
Test
Backup
ISDN PRI
Sig
OOF
Alm
NETWORK 1
Sig
OOF
Alm
DSX-1
Sig
OOF
Alm
Port-1
OK
TXD
RXD
DTR
CTS
Port-2
OK
TXD
RXD
DTR
CTS
VOICE PORTS
OK
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Exit
MainMenu
Refresh
For more information, see Viewing LEDs and Control Leads in Chapter 10,
11-28
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Backup LED Description
In addition to the OK. ALM (Alarm), and TST (Test) LEDs, the NextEDGE
FrameSaver system has a BKP (Backup) LED.
Table 11-7. General Status Backup LED
Label
Indication
Color
What It Means
BKP
Backup
Yellow
ON – System is in Backup mode; that is, the
backup link has been established, and
backup is in progress through the
specified Alternate Destination Link.
OFF – System is not in Backup mode.
Blinking ON and OFF – Alternate Destination
Link is being established, but no data
has been passed.
ISDN PRI DBM LED Descriptions
The following LEDs apply to an ISDN PRI DBM.
Table 11-8. PRI Interface LEDs
Label
Indication
Color
What It Means
SIG
Signal
Green
ON – A recoverable signal is present on the
OFF – The signal cannot be recovered from
the Network/DSX/PRI interface. An
LOS condition exists.
OOF
Out of Frame
Yellow
ON – At least one OOF was detected during
the sampling period.
OFF – No OOFs were detected during the
sampling period.
ALM
Alarm
Yellow
ON – An alarm condition is present on the
network/DSX/PRI interface.
Current alarm conditions:
H Loss of Signal ( LOS )
H Loss of Frame (LOF)
H Out of Frame (OOF)
H Excessive Error Rate (EER)
OFF – No alarm condition is present on the
9191-A2-GH30-00
DRAFT — June 1999
11-29
Dial Backup Modules
Manually Forcing Backup (Disruptive)
Use this procedure to force backup when network maintenance is planned, when
equipment problems are reported, or when testing the backup path – whenever
data needs to be forced from the primary destination interface to the alternate
destination, typically the T1 network to the ISDN.
" Procedure
1. Make sure the ISDN Link Profiles are set up correctly (see Setting Up ISDN
Link Profiles on page 11-15).
2. Have someone at the far end disconnect the network cable. The originating
unit should initiate backup.
To determine the answering or originating side, see the Originate or Answer
configuration option for the ISDN physical interface options (see Table 11-1
for a PRI DBM or Table 11-2 for a BRI DBM).
3. Verify that backup is taking place.
See Verifying That Backup Can Take Place on page 11-33.
NOTE:
When an alarm requiring backup is received, backup can be manually
controlled by enabling or disabling the Auto Backup option (see Step 2).
4. Have the far end network cable reconnected to return to standard operation.
11-30
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Manually Placing a Call (Nondisruptive)
Use this procedure to test the ISDN path to each remote site. This procedure will
not put the system into backup. This is accomplished by creating unique PVCs,
with the ISDN Link as the Primary Destination.
The following procedures tell you how to set up the originating unit, as well as the
answering unit for this test.
" Procedure
1. Make sure the ISDN Link Profiles are set up correctly at both the originating
and answering devices (see Setting Up ISDN Link Profiles on page 11-15).
Main Menu → Configuration → ISDN → Link Profiles
2. Create a unique test DLCI Record on the ISDN interface at each end
(e.g., Line Test).
Main Menu → Configuration → ISDN → DLCI Records
3. Create a new Management PVC at each end using the DLCI numbers
created in Step 2.
Management PVCs
The ISDN Link should be configured as the Primary Destination Link and
DLCI/EDLCI.
— For the originating device, the call is placed once the configurations
are saved.
— For the answering device, the answering unit will be receiving a call.
NOTE:
As long as no other backup is taking place, the Backup (BKP) LED
remains off during this procedure since the ISDN link is being used as the
primary destination, not the alternate (backup) destination.
4. When the test is complete, delete the test Management PVC and DLCI
Records.
9191-A2-GH30-00
DRAFT — June 1999
11-31
Dial Backup Modules
Verifying the ISDN Lines
Use either of the following methods to verify operation of the ISDN lines.
H
Check the status of the DBM interface:
Main Menu → Status → DBM Interface Status
Line Status should display Active. If an invalid ( Inv) status appears (e.g.,
Inv SPID for an ISDN BRI DBM) in the Line Status field, verify that you
entered ISDN physical options correctly.
H
Check the status of the unit:
Main Menu → Status → System and Test Status →
Health and Status column
System Operational should appear.
If ISDN Network Failed appears, check that both ends of the ISDN cable
are seated properly for a good physical connection. If that does not clear the
message, verify that you entered ISDN physical option information correctly,
then contact the network service provider.
See DBM Interface Status on pageNO TAG and DBM Health and Status
Messages on page 11-35 for additional status information.
11-32
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Verifying That Backup Can Take Place
As each remote site is installed, verify its backup operation by unplugging the
network cable so the system is forced into backup.
Verify that backup can take place by viewing the:
H
DBM Interface Status screen (see pageNO TAG) – The Last Call Value
should be Call awarded and being delivered in est chnl.
When viewing a status screen, select Refresh to see the most current status.
Use the spacebar to tab through each configured ISDN link to view the status
of each link.
H
System and Test Status screen – Under the Health and Status column
messages you should see Backup Active and ISDN Active. You should
not see LMI Down for an ISDN Link Profile (see page 11-35).
H
PVC Connection Status screen – The Alternate Destination Status should be
Active for the appropriate PVCs.
H
Frame Relay Performance Statistics – Statistics incrementing indicates
data flow.
Main Menu → Status → Performance Statistic → Frame Relay
Use the space bar to tab through each configured ISDN link to view the
statistics on each link.
Clear all statistics, then Refresh the screen a few times:
— Frames/Characters Sent and Frames/Characters Received (Frame Relay
Link) increase when data is being passed.
— Status Msg Received (Frame Relay LMI) also increases.
H
Backup (BKP) LED should be on continuously.
Reconnect the network cable to reestablish normal operation.
See DBM Health and Status Messages on page 11-35, Viewing DBM LEDs and
Control Leads on page 11-28, and DBM Call Statistics on page 11-48 for
9191-A2-GH30-00
DRAFT — June 1999
11-33
Dial Backup Modules
Upgrading ISDN BRI DBM Software
To upgrade a system’s BRI DBM program code, you must transfer the
dbmprog.ocd file in the Dial Backup Module directory using the put command.
NOTE:
An ISDN PRI DBM is not upgraded using this procedure. PRI software is
upgraded when the system software is upgraded.
" Procedure
To perform a BRI DBM upgrade:
1. Initiate an FTP session to the device that you are upgrading.
2. Type bin to enter binary transfer mode, then cd dbm to change to the Dial
Backup Module directory.
3. Type hash to enter hash mode if you want to monitor the progress of the
upgrade, provided this function is supported by your equipment.
4. Perform a put of Rxxxxxx.ocd (xxxxxx being the software release number) to
the dbmprog.ocd file to start the upgrade.
If the message displayed is . . .
Then . . .
DBM Download Failed
Errors were detected during the DBM
download.
The dbmprog.ocd file will need to be
downloaded again.
dbmprog.ocd: File Transfer Complete
The download was successful.
dbmprog.ocd: File Transfer Failed
The download was not successful.
Possible cause: A bad or invalid file, or the
wrong checksum.
A different dbmprog.ocd file will need to be
downloaded for the DBM to become
operational. Repeat the step or end the FTP
session.
5. Close the FTP session.
6. Verify that the new software release was successfully installed as the DBM
Software Revision.
See Upgrading System Software in Chapter 10, Operation and Maintenance, for
11-34
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
DBM Status Information
When an ISDN DBM is installed, DBM-specific Health and Status (see below)
and Test Status (see page 11-38) information is available.
Status information is also available for the DBM interface (see pageNO TAG).
Status → DBM Interface Status
DBM Health and Status Messages
These messages appear in the left column of the System and Test Status screen.
The highest priority Health and Status message also appears on the last line at
the bottom right corner of the screen.
Table 11-9. DBM Health and Status Messages (1 of 4)
Message
What It Indicates
What To Do
AIS at ISDN PRI
(Active/Idle)
ISDN PRI interface. AIS is
an unframed, all ones
signal.
Report problem to carrier.
(PRI only)
H Active – Backup call was
in progress.
H Idle – DBM was in Idle
mode.
The ISDN network is
transmitting an AIS.
Backup Active
Backup has been
established and data is
flowing over the alternate
DLCI.
No action needed.
DBM BRI Card Failed
One or more of the
system’s integrated circuit
chips has failed to internally
loop data through the dial
backup unit BRI circuit.
1. Reset the system and try
again.
(BRI only)
2. Call your service
representative for assistance.
3. Return the NextEDGE NAM to
the factory (see Page A at the
front of this guide).
DBM Download Failed
(BRI only)
A download attempt was
interrupted and failed to
complete.
Call your service representative.
The NAM software and
DBM software are
incompatible.
DLCI nnnn Down,
ISDN LinkName
9191-A2-GH30-00
The DLCI for the ISDN link
profile specified (ISDN Link
Name) specified is down.
DRAFT — June 1999
Verify that the ISDN network is
up. If it is, contact your ISDN
service provider.
11-35
Dial Backup Modules
Message
What It Indicates
What To Do
EER at ISDN PRI
(Active/Idle)
received ISDN network
signal exceeds the
currently configured
threshold. This condition
only occurs if the network
interface is configured for
ESF framing and a PRI dial
backup module (DBM) is
installed.
1. Verify that the network cable is
securely attached at the DBM
interface.
(PRI only)
2. Contact ISDN network
provider.
in progress.
mode.
threshold value, which may
ISDN Active
An ISDN call is active.
No action needed.
ISDN Link Profile
Invalid ISDNLinkName
An ISDN backup call could
not be made because the
ISDN link profile specified
(ISDNLinkName) is invalid.
Check that the phone number is
valid.
ISDN Network Failed
(Active/ Idle)
An ISDN network failure
was detected when:
Contact network provider if
problem persists.
in progress.
mode.
11-36
ISDN Link Profile
Disabled
ISDNLinkName
An ISDN backup call could
not be made because the
(ISDNLinkName) is
disabled.
LMI Down,
ISDN LinkName
(ISDN Link Name).
DRAFT — June 1999
Enable the ISDN link profile if
you want to make a call.
9191-A2-GH30-00
Dial Backup Modules
Message
What It Indicates
LOS at ISDN PRI
(Active/Idle)
ISDN PRI interface. Clears
(PRI only)
What To Do
in progress.
mode.
This could indicate:
OOF at ISDN PRI
(Active/Idle)
(PRI only)
1. DBM cable problem.
1. Check that the DBM cable is
ends.
ISDN PRI interface. An
OOF is declared when two
out of four frame
synchronization bits are in
error.
in p
rogress.
for the ISDN PRI DBM
interface is correct.
2. Check that the ISDN PRI DBM
cable is securely attached at
both ends.
mode.
This could indicate:
format between the
ISDN network and the
system.
2. ISDN network cabling
problem.
3. ISDN network problem.
SLV Timeout,
DLCI nnnn,
frame relay link 1
1
9191-A2-GH30-00
SLV communication
responses from the remote
FrameSaver device have
been missed on the
specified multiplexed DLCI;
the DLCI is not suitable for
user data.
If a DBM is present and Auto
Backup is enabled, backup is
initiated automatically.
Does not apply to a TS Managment Link DLCI.
DRAFT — June 1999
11-37
Dial Backup Modules
Message
What It Indicates
What To Do
Yellow at ISDN PRI
(Active/Idle)
received on the ISDN
network interface.
provider.
(PRI only)
in progress.
mode.
Indicates a possible cable
problem.
DBM Test Status Messages
These test messages appear in the right column of the System and Test Status
screen.
You have the option of allowing a test to continue, or aborting it. For additional
test status messages, see Test Status Messages in Chapter 10, Operation and
Maintenance.
Table 11-10. Test Status Messages
Message
What It Indicates
LLB Active, ISDN PRI
A Line Loopback (LLB) is active on the interface.
PLB Active, ISDN PRI
A Payload Loopback (PLB) is active on the
interface.
Monitor Pttn Active, ISDN
A Monitor Pattern test (user-selected pattern) is
active on the specified interface (and in the
specificed slot).
Send Pttn Active, ISDN
A user-selected pattern test is being sent on the
specified interface (in the specified slot).
Network Initiated ISDN BRI Test
Active
An ISDN test has been initiated by the ISDN BRI
network and is currently active.
Test Call Active
A PVC Loopback is active on the specified frame
relay link, which is the ISDN Link Name.
See Tests and Starting and Stopping a Test in Chapter 13, Troubleshooting, for
information on tests.
11-38
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
PVC Connection Status
The PVC connection status screen shows both a Primary and Alternate
Destination Link, DLCI, EDLCI, and Status. An example of this screen is shown
below.
PVC Connection Status Example
main/status/connections
Device Name: Node A
PARADYNE 9191
01/26/1998 23:32
Page 1 of 2
PVC CONNECTION STATUS
Link
Source
Primary Destination
DLCI EDLCI Link
DLCI EDLCI
Status
Port-1 201
Port-1 202
Port-1 100
Port-1 204
Mgmt PVC Mgm205
Port-1 206
Port-1 207
Port-1 208
Port-1 209
Port-1 210
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
Net1-FR1
300
1001
1001
1001
1001
1001
1001
500
502
504
0
0
2
2
2
2
2
Active
Active
Active
Active
Active
Active
Active
Active
Inactive
Inactive
Link
DLCI EDLCI Status
HQ_Site 400
HQ_Site 302
HQ_Site 304
2
2
Inactive
Active
Active
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Exit
MainMenu
PgUp PgDn
Refresh
For additional information about the Alternate Destination fields, see Manually
Adding Alternate Destinations on page 11-18.
9191-A2-GH30-00
DRAFT — June 1999
11-39
Dial Backup Modules
DBM Interface Status
ISDN DBM interface statuses appear when DBM Interface Status is selected from
the Status menu.
Table 11-11. DBM Interface Status (1 of 2)
Field
Status
What It Indicates
Line Status
Active
Disabled
Inactive
Invalid SPID
Invalid Local Number
Invalid Call ID – call ID
Status of the ISDN line.
H Active – The ISDN line is active
and no error conditions exist.
H Disabled – The ISDN interface
has been disabled.
Main Menu → Configuration →
ISDN → Physical
H Inactive – The ISDN line is
disconnected or an ISDN
network alarm condition exists.
H Invalid SPID – The switch has
rejected one of the configured
SPIDs.
H Invalid Local Number – The
phone number configured for a
B-channel is an invalid local
number.
H Invalid Call ID – The incoming
call was rejected because the
Inbound Calling ID did not match
the number in any of the enabled
ISDN Link Profiles. The rejected
Inbound Calling ID appears at
the end of the message, if
provided by the switch.
Link
11-40
ISDN Link Name
DRAFT — June 1999
ISDN link for which status will be
displayed.
9191-A2-GH30-00
Dial Backup Modules
Table 11-11. DBM Interface Status (2 of 2)
Field
Status
What It Indicates
Link Operating Mode
Disabled 1
Idle 1
Testing
Active
Status of the ISDN DBM.
H Disabled – ISDN Link Profile is
disabled.
H Idle – An ISDN link is not
currently needed, so there is
no ISDN connection.
H Testing – A network-initiated test
is running on the DBM interface.
H Active – The ISDN link is
required for frame relay traffic
and needs an active ISDN
connection.
Last Cause Value
Various ITU cause
messages
Refer to the Last Cause Messages
on pageNO TAG for additional
information.
None
Backup has never been active on
the link.
Remote device’s ID
Remote call origination – Last
Calling ID of the remote backup
device received for the B-channel. If
the remote device initiated the call,
this is the Inbound Call ID. If this
device originated the call, this is the
Outbound Phone Number.
Previous Last Cause
Value
Remote Call ID
Up to 36 characters (0 – 9).
ISDN Channel
Bn
ISDN B-channel being used for the
call on this link (1 or 2 if a BRI DBM,
1 – 23 if a PRI DBM).
Negotiated Rate
64 Kbps
56 Kbps
Negotiated rate of the connection/
link.
1
9191-A2-GH30-00
If Link Operating Mode is Disabled or Idle, the Remote Call ID, ISDN Channel and
Negotiated Rate fields will not appear.
DRAFT — June 1999
11-41
Dial Backup Modules
The following Last Cause Value Messages are presented in alphabetical order.
The Cause Number is also provided if you need to convert the message to its
corresponding ITU number for your service provider.
Table 11-12. Last Cause Value Messages (1 of 6)
Message
Cause
What It Indicates
No.
What To Do
Bearer capability
not authorized
57
User has requested a
bearer capability that the
user is not authorized to
use.
Arrange for the desired
capability.
Bearer capability
not implemented
65
Device sending this cause
does not support the bearer
capability (i.e., channel
type) requested.
capability.
Bearer capability
presently not
available
58
Bearer capability requested
is supported by the device
generating the cause, but it
is not available at this time.
capability.
Call awarded and
being delivered in
est chnl
7
An incoming call is being
connected to an already
established channel that is
used for similar calls.
No action is needed.
Call profile disabled
129
Backup was attempted, but
the ISDN link profile was
disabled.
Enable ISDN Link Profile
status.
Call profile invalid
128
A blank telephone number
was entered in the unit’s
ISDN Link Profile.
1. Enter a valid telephone
number for the ISDN
Link Profile’s
– Outbound Phone
Number if originating
backup.
– Inbound Calling ID if
answering backup
calls.
2. No other action needed.
11-42
Call rejected
21
Equipment sending the
cause does not want to
receive the call at this time.
Call terminated by
remote end
130
Remote DBM rejected or
terminated the call.
1. Retry the call.
Call with requested
call id has been
cleared
86
2. Verify that the remote
DBM’s link profile is
correct.
Network has received a call No action is needed.
resume request, but the call
had been cleared after it
was suspended.
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Message
Cause
What It Indicates
No.
What To Do
Channel type not
implemented
66
does not support the
requested channel type.
capability.
Channel
unacceptable
6
Channel identified for the
call is not acceptable to the
receiving device.
capability.
Destination out of
order
27
Destination interface
specified is not functioning
correctly so the signalling
message could not be
delivered (e.g., physical or
data-link layer failure at the
remote end, user
equipment is offline).
Verify that the remote
DBM’s link profile is
correct.
Facility rejected
29
Requested facility is not
provided by the network.
Incoming calls
barred
54
Called user is not permitted
to accept the call.
Turn off network call
screening.
Incompatible
destination
88
Request to establish a call
has been received, but
low-layer, high-layer, or
another compatibility
attribute (e.g., data rate)
cannot be provided.
capability.
Incorrect format of the
destination link.
Identified channel
does not exist
82
Channel requested for a
call is not activated on the
interface.
Make sure the network is
configured for 2B service,
if a BRI DBM. Contact your
service provider to verify
that your service is
provisioned for two
B-channels.
Info element
nonexistent or
nonimplemented
99
has received a message it
does not recognize.
1. Verify that the Inbound
Calling ID has been
defined.
This cause will not prevent
the message from being
precessed.
2. Verify that the Inbound
Calling ID is part of your
service.
Precise cause of a
message cannot be
determined because the
interworking network does
not provide causes.
Interworking,
unspecified
9191-A2-GH30-00
127
DRAFT — June 1999
11-43
Dial Backup Modules
Message
Cause
What It Indicates
No.
What To Do
Invalid call
reference value
81
Call reference used is not
currently in use on the
user-network interface.
Contact your service
representative.
Invalid info element
contents
100
has received and
representative.
implemented an information
element, but one or more
fields in the element cannot
be processed.
Invalid message,
unspecified
95
No other cause in the
invalid message class
applies for this invalid
message event.
representative.
Invalid number
format – incomplete
address
28
Call cannot be completed
because the phone number
is incorrect or incomplete.
Check your ISDN link
profile, and correct the
number.
Invalid transit
network selection
91
Incorrect format of transit
network identification.
representative.
Mandatory
information element
missing
96
Required data is missing
from a mandatory
information element.
representative.
Message not
compatible with call
state
101
has received a message
that is not permissible while
in the call state.
representative.
Msg nonexistent
98
An unexpected message
was received in a state
other than Null.
Retry the call.
Msg type
nonexistent or
unimplemented
97
has received a nonexistent
or not implemented
message type while in the
call state.
representative.
has received a status
message that indicates an
incompatible call state.
11-44
Network out of order 38
Network is not functioning
correctly, and the condition
is expected to continue.
representative.
No call suspended
A call resume has been
issued, but no calls have
been suspended.
85
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Cause
What It Indicates
No.
What To Do
No circuit/channel
available
34
No circuit/channel is
currently available to
handle the call.
Wait and try again.
No destination route
3
Network through which call
has been routed does not
serve the destination area
or device.
representative.
None
—
No causes have been
generated.
Non-selected user
clearing
26
User has not been awarded
the incoming call.
No route to specify
transit network
2
The device sending or
receiving this cause does
not recognize the transit
network that the call is
being/ has been routed
through.
1. Verify that the network
exists.
Message
2. Verify that the network
serves the device
sending the cause.
Normal call clearing
16
Call is being cleared
because either the caller or
receiver has requested that
it be cleared.
Normal, unspecified
31
Remote user has sent a
release message to the
network.
normal class applies for this
normal event.
No user responding
18
Called device does not
respond to the call with an
alert or connect indication
within the prescribed period
of time.
Contact the network
provider if the cause
continues.
Internal network timers may
be a cause.
9191-A2-GH30-00
Number changed
22
Called number is no longer
assigned.
Look in the diagnostic field
for the new number, then
change the phone number
in your ISDN link profile.
Only restricted
bearer capability
available
70
An unrestricted bearer
service has been
requested, but the device
sending the cause only
supports the restricted
version.
capability.
DRAFT — June 1999
11-45
Dial Backup Modules
Message
11-46
Cause
What It Indicates
No.
What To Do
Outgoing calls
barred
52
Network is using Call
Screening.
Contact the network
provider to turn Call
Screening off.
Pre-empted
45
Call has been pre-empted.
Contact the network
provider.
Protocol error,
unspecified
111
protocol error class applies
for this protocol error event.
representative.
Quality of service
unavailable
49
Requested Quality of
Service requested cannot
be provided (e.g.,
throughput cannot be
supported).
Recovery of timer
expired
102
Error-handling procedure
has been initiated as a
result of the expiration of a
timer.
Retry the call.
Requested channel
not available
44
Circuit or channel
requested cannot be
provided by the other side
of the interface.
Allow the DBM to
automatically call using the
alternate link if Auto
Backup is enabled, or
manually select an
alternate path for the call.
Requested facility
not implemented
69
Supplemental service
requested is not supported
by this device.
Requested facility
not subscribed
50
The supplementary service
requested cannot be
provided by the network
until user completes
arrangement with its
supporting networks.
capability.
Resource
unavailable,
unspecified
47
resource unavailable class
applies for this resource
unavailable event.
Response to
STATus ENQuiry
30
Status enquiry message
received, generating this
message.
Service/option not
implemented
79
service or option not
available class applies for
this not implemented event.
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
Cause
What It Indicates
No.
What To Do
Service/option
unavailable,
unspecified
63
service or option not
available class applies for
this not available event.
Wait and try again.
Switching
equipment
congestion
42
Switching equipment
sending the cause is
experiencing heavy traffic.
Wait and try again.
A call resume has been
attempted, but no
suspended call exists for
this phone number.
1. Verify the number in the
Inbound Calling ID #
field for the suspended
call.
Message
Suspended call
83
exists, but not call id
2. Reissue the Call
Resume command
using the correct
number.
Temporary failure
41
Network is not functioning
correctly, but the condition
is not expected to continue
for long.
Wait and try again.
Unallocated number
1
Destination requested
Assign the Inbound
cannot be reached because Calling ID.
the Inbound Calling ID
number is not assigned or
allocated.
User access
information
discarded
43
Network was unable to
deliver the access
information when trying to
establish the call.
User alerting,
no answer
19
During call establishment,
an alerting was received
but a connection was not.
1. Verify that the remote
device is operational
and configured to
answer.
2. Retry the call.
User busy
9191-A2-GH30-00
17
Called number cannot
receive the call.
DRAFT — June 1999
Wait and try again.
11-47
Dial Backup Modules
DBM Call Performance Statistics
These statistics are available for ISDN calls and call attempts.
Main Menu → Status → Performance Statistics → DBM Call
Table 11-13. DBM Call Performance Statistics
Statistic
What It Indicates
Total Call Attempts
Number of call attempts made by the DBM.
Total Calls Originated
Number of successful calls made by the DBM.
Total Calls Answered
Number of successful calls answered by the DBM.
Total Calls Rejected (Security)
Number of calls rejected by the DBM due to
security.
Total Calls Rejected (Other)
Number of calls rejected by the DBM due to
reasons other than security.
Average Call Duration (mins)
Average amount of time, in minutes, that
successful calls take.
Longest Call Duration (mins)
Amount of time spent, in minutes, during the
longest successful call.
Total Call Duration (mins)
Sum of all successful calls in minutes.
For information about other performance statistics, see Performance Statistics in
Clearing DBM Call Performance Statistics
Clearing DBM Call performance statistics will not affect performance statistics
stored in user history for the system. The statistics are only cleared locally.
" Procedure
To clear all statistics for the system, including DBM Call Statistics:
Main Menu → Status → Performance Statistics → Clear All Statistics
" Procedure
To clear DBM call performance statistics:
Main Menu → Status → Performance Statistics → DBM Call
Select the ClrDBMStats function key to reset the DBM call performance statistics.
11-48
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
DBM Alarms
The following table describes the alarm conditions that are unique to ISDN DBMs.
These alarms are in alphabetical order.
For information about other alarms, see Alarms in Chapter 13, Troubleshooting.
Table 11-14. DBM Alarm Conditions (1 of 2)
Alarm Condition
What It Indicates
What To Do
AIS
For the ISDN PRI DBM
interface, the ISDN network
is transmitting an AIS.
For the ISDN PRI DBM interface,
report the problem to your ISDN
service provider.
One or more of the unit’s
integrated circuit chips has
failed to internally loop data
through the ISDN BRI
DBM’s BRI circuit.
1. Reset the unit and try again.
DBM Download
Required
A download attempt was
interrupted and failed to
complete, or the NAM
software and DBM software
are incompatible.
Call your service representative.
EER
For an ISDN PRI DBM
interface, Active indicates
that a backup call was in
progress when the ISDN
network failure was
detected, and Idle indicates
that the call was in idle
mode when it was
detected.
For the ISDN PRI DBM interface:
An ISDN network failure
was detected when a
backup call was in progress
or tthe DBM was in Idle
mode.
(PRI only)
DBM BRI Card Failed
(BRI only)
(PRI only)
ISDN Network Failed
9191-A2-GH30-00
DRAFT — June 1999
2. Call your service
representative for assistance.
3. Return the unit to the factory
(see Page A at the front of this
guide).
1. Verify that the cable is
interface.
2. Contact your ISDN network
provider.
11-49
Dial Backup Modules
Table 11-14. DBM Alarm Conditions (2 of 2)
Alarm Condition
What It Indicates
What To Do
OOF
For an ISDN PRI DBM
network failure was
mode when it was
detected.
For an ISDN PRI DBM interface,
contact your ISDN network
provider instead of your T1
network provider.
(PRI only)
It could indicate a cabling
problem, incompatiblity
between the ISDN network
and the unit, or an ISDN
network problem.
LOS
(PRI only)
Yellow Alarm
(PRI only)
11-50
H For an ISDN PRI DBM
interface, Active
indicates that a backup
call was in progress
when the ISDN network
failure was detected, and
Idle indicates that the
call was in idle mode
when it was detected.
There could be a cable
problem, the far-end unit
may not be transmitting
a signal, or there may be
a T1 facility problem.
For an ISDN PRI DBM
network failure was
mode when it was
detected.
DRAFT — June 1999
For the network, DSX-1, or ISDN
PRI DBM interface:
ends.
2. Verify that the attached device
is operational.
For the ISDN PRI DBM interface,
report the problem to your ISDN
service provider.
9191-A2-GH30-00
Dial Backup Modules
ISDN DBM Problems
See Configuring the ISDN DBM Interface on page 11-10 and Configuring ISDN
Link Profiles on page 11-15 for more information about ISDN DBM configuration.
Table 11-15. ISDN DBM Problems
Symptom
Possible Cause
Solutions
Cannot connect to the
remote unit
Misconfiguration
H Verify that the link profiles are
correct in both units, both the
area codes and phone or ID
numbers (see Configuring
ISDN Link Profiles on
page 11-15.
H For a BRI DBM, verify that the
SPIDs and local area codes
and phone numbers are
correct (see Configuring the
ISDN DBM Interface on
page 11-10.
H Verify that the unit at one end
is configured to originate and
the unit at the other end is
configured to answer a call.
H Verify that the ISDN interface
is enabled.
H Verify that Auto Backup is
enabled and no time
restrictions apply.
DBM LMI comes up,
but no data is
transferred
Misconfiguration
Check that the DLCI numbers
are correct and are the same at
both ends.
See the Last Cause Value Messages on page 11-42 for additional information
about ISDN problems. Last Cause Value messages appear on the DBM Interface
Status screen.
9191-A2-GH30-00
DRAFT — June 1999
11-51
Dial Backup Modules
DBM Tests
The Test menu allows you to run loopbacks and test patterns on the system and
its ISDN DBM interface. It is available to users with a security Access Level of 1
or 2. Currently, there are no physical tests for a BRI DBM interface.
The following tests can be run for an ISDN DBM:
H
PVC Tests on the ISDN link
— PVC Loopback
— Send and Monitor Pattern
— Connectivity
H
PRI Physical Tests
— Local Line Loopback
— Local Payload Loopback
— Remote Send Line Loopback
— Send and Monitor user-selected Pattern
These tests are started and monitored the same as the network tests.
See DBM Test Status Messages on page 11-38 for test status information.
See PVC Tests and Physical Tests in Chapter 13, Troubleshooting, for additional
information about these tests.
11-52
DRAFT — June 1999
9191-A2-GH30-00
Dial Backup Modules
ISDN PVC Tests
PVC tests can be run on the ISDN DBM frame relay links. Only one PVC test can
be run on the same DLCI and no physical test can be run on the same interface
while a PVC test is running. An example of the PVC Tests screen is shown, with
the multiplexed DLCI 550 selected.
Example of a PVC Tests Screen
main/test/isdn_pvc
Device Name: Node A
PARADYNE 9191
5/26/1999 23:32
ISDN-FLA PVC TESTS
DLCI Number: 550
Test (Non-Disruptive)
Command
Status
PVC Loopback:
Send Pattern:
Monitor Pattern:
Start
Start
Start
Inactive
Inactive
Inactive
Connectivity:
Start
Inactive
Result
0:00:00
0:00:00
0:00:00
Sequence Errors 99999+
Data Errors
99999+
RndTrip Time (ms) 99999
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Exit
MainMenu
9191-A2-GH30-00
DRAFT — June 1999
11-53
Dial Backup Modules
11-54
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
12
This chapter provides information about the following:
H
APM Overview on page 12-4.
H
Typical Applications on page 12-5.
— High Speed Data Using Port-2 or Synchronous Data APM on
page 12-5.
— High Speed Data and E&M on page 12-6.
— High Speed Data and APL on page 12-7.
— High Speed Data, FXS, and E&M on page 12-8.
— High Speed Data and Drop & Insert on page 12-9.
— Off-Premises Extension (OPX) on page 12-9.
— Direct Dial (DID) on page 12-10.
— Video Conferencing on page 12-10.
— Consolidated T1 Access of DDS Circuits on page 12-11.
H
Displaying APM Information on page 12-12.
H
Viewing APM LEDs and Control Leads on page 12-13.
— OCU-DP APM LED Descriptions on page 12-14.
— Voice APM LED Descriptions on page 12-15.
— Synchronous Data APM LED Descriptions on page 12-15.
H
Displaying System and Test Status on page 12-16.
— APM Health and Status Messages on page 12-16.
— APM Test Status Messages on page 12-19.
H
9191-A2-GH30-00
Viewing Voice APM Status on page 12-21.
DRAFT — June 1999
12-1
Application Modules
H
Viewing Cross Connect Status on page 12-24.
— Displaying Network Channels on page 12-24.
— Displaying DSX-1 Channels on page 12-26.
— Displaying Port Assignments on page 12-28.
H
Viewing APM Performance Statistics on page 12-29.
— Statistics That Can Be Collected on page 12-29.
H
Hot Swapping APMs on page 12-30.
— APM Insertion on page 12-30.
— APM Removal on page 12-31.
H
T1 TDM ASCII Alarm Messages on page 12-31.
— Automatic Dialing Out When an Alarm Occurs on page 12-37.
H
FrameSaver APM Alarms on page 12-39.
H
Configuring APM Ports on page 12-40.
— Configuring Synchronous Data APM Ports on page 12-40.
— Configuring FXS Voice APM Ports on page 12-48.
— Configuring FXO Voice APM Ports on page 12-52.
— Configuring E&M Voice APM Ports on page 12-55.
— Configuring OCU-DP APM Ports on page 12-57.
H
Assigning Cross Connections on page 12-58.
— Assigning Voice Ports to DSX-1 or Network Interface Time Slots on
page 12-61.
— Assigning Synchronous Data Ports on page 12-61.
— Assigning OCU-DP Data Ports on page 12-62.
— Assigning DSX-1 Time Slots to the Network Interface on page 12-62.
— Clearing Port Assignments on page 12-63.
H
12-2
APM Tests on page 12-64.
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
H
Voice Port Tests on page 12-65.
— Digital Loopbacks on page 12-66.
— Analog Loopbacks on page 12-66.
— Line Loopbacks on page 12-67.
— Send Test Tones on page 12-67.
— Force and Monitor Signaling on page 12-68.
H
OCU-DP Tests on page 12-70.
— Sending a Latching Loopback on page 12-70.
— Starting/Stopping Other Loopbacks on page 12-70.
H
OCU-DP Loopback Tests on page 12-71.
— DDS CSU/DSU Latching/Nonlatching Loopbsck on page 12-72.
— Latching Loopback on page 12-72.
— OCU Loopback on page 12-73.
— DS-0 Loopback on page 12-73.
— Line Loopback on page 12-74.
— Data Loopback on page 12-74.
9191-A2-GH30-00
DRAFT — June 1999
12-3
Application Modules
APM Overview
There are six Application Module types.
H
The Synchronous Data APM supports:
— Four ports, each supporting EIA-530A, V.35, RS449, or V.11/X.21.
— Rates of Nx56 or Nx64.
— Standard RS232-like (RFC 1659) MIB.
— Enterprise MIB for testing, statistics, and some configuration functions.
See the 9109 Sync Data Application Module (APM) Installation Instructions
for more information.
H
The E&M Voice APM supports:
— E&M Type I, II, IV, or V circuits.
— mĆlaw PCM coding of analog voice line.
— Enterprise MIB for testing and some configuration functions.
See the 9109 E&M Analog Voice Application Module (APM) Installation
Instructions for more information.
H
The FXO Voice APM supports:
— FXO circuits.
See the 9109 FXO Analog Voice ApplicationModule (APM) Installation
H
The FXS Voice APM supports:
— FXS circuits.
See the 9109 FXS Analog Voice Application Module (APM) Installation
H
The OCU-DP APM supports:
— Either two or six ports.
— Speeds of 56 kbps and 64 kbps, as well as 4-wire Switched 56.
See the 9109 OCU-DP Application Module (APM) Installation Instructions for
more information.
12-4
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
To see faceplate LEDs and screens, see Viewing APM LEDs and Control
Leads on page 12-13.
Typical APM Applications
The following sections provide examples of typical APM applications.
High Speed Data Using Port-2 or a Synchronous Data APM
This application supports two ports of high speed data. Port-1 is for frame relay
traffic, while Port-2 can be configured for either frame relay traffic or synchronous
data. The following illustration depicts a frame relay router and mainframe
application.
Cluster
Controller
FEP
Terminal
Port-2
FR
Router
FR
Port-1
NextEDGE
System
Port-2
FR
Port-1
NextEDGE
System
FR
Router
FR = Frame Relay
Mainframe
99-16375
The data moving through the FEP and the cluster controller is heritage data that
is not available on the LAN. Because the NextEDGE system includes two data
ports, the router-based data can easily be added to the network without
disrupting the existing network operations.
allows the router connection to increase in speed. It also allows the FEP-based
data to reduce its data rate as the amount of data transmitted on this route
declines naturally over time.
Additional data ports can be added using a 4-port Synchronous Data APM.
9191-A2-GH30-00
DRAFT — June 1999
12-5
Application Modules
High Speed Data and E&M
Analog PBXs typically communicate on trunk lines (lines between switches) with
a type of communications protocol called E&M. The NextEDGE system fully
supports this application. Up to three 8-port E&M APMs are supported.
In the example shown below, you could assign eight time slots to the voice ports,
two time slots to the FEP-cluster controller link, and up to 14 time slots to the
router link. This provides the following:
H
Voice – Eight telephone calls
H
FEP-CC – 128 kbps
H
Frame Relay Router – 896 kbps
Downtown HQ
Cluster
Controller
FEP
Terminal
NextEDGE
System Port-2
FR
Router
NextEDGE
System Port-2
FR
Port-1
FR
Port-1
E&M
E&M
PBX
PBX
Analog
PBX
Analog
PBX
FR
Router
Mainframe
Suburban Office
FR = Frame Relay
12-6
DRAFT — June 1999
99-16376
9191-A2-GH30-00
Application Modules
High Speed Data and APL
In this example, E&M analog voice APMs are used to transport analog private
line (APL) modem traffic instead of voice traffic.
In some parts of the country digital circuits are hard to obtain, and many
applications do not require the higher speeds of digital circuits. This application
allows customers to use existing modems while reducing the cost of using them
by eliminating access lines.
The NextEDGE system supports up to three 8-port E&M APMs. A typical
application consists of:
H
Modem Lines – Eight lines
H
FEP-CC – 128 kbps
H
Frame Relay Router – 896 kbps
Downtown HQ
Cluster
Controller
Terminal
NextEDGE
Port-2
System
FR
Router
FEP
NextEDGE
System Port-2
FR
Port-1
FR
Port-1
E&M
(APL Modems)
Suburban Office
FR
Router
FR = Frame Relay
Mainframe
99-16377
E&M is used to transport the analog information, and no E&M signaling is
involved. In fact, the E&M signaling leads are disconnected in this application (the
operating mode is set to Transmit Only).
9191-A2-GH30-00
DRAFT — June 1999
12-7
Application Modules
High Speed Data, FXS, and E&M
In the example shown below, data and regular voice traffic is transported by the
NextEDGE system and the APL modem. E&M-type voice (in Transmit mode only)
is being used to transport the APL modem traffic, while FXS is being used to
transmit regular voice traffic.
Downtown HQ
Cluster
Controller
FEP
Terminal
NextEDGE
Port-2
System
FR
Router
NextEDGE
System Port-2
FR
Port-1
FR
Port-1
FR
Router
Mainframe
FXS and E&M
Voice
Warehouse
APL
Modems
FR = Frame Relay
99-16378
Another variation of this application would have the FXS lines that are connected
to the telephones terminate at a switch in the cloud, where they could be
connected to the Public Switched Telephone Network (PSTN).
Downtown HQ
Cluster
Controller
FEP
Terminal
NextEDGE
Port-2
System
FR
Router
FrameSaver
SLV 9128 Port-2
FR
Port-1
FR
Port-1
FR
Router Mainframe
FXS Voice
Warehouse
12-8
DRAFT — June 1999
FR = Frame Relay
99-16400
9191-A2-GH30-00
Application Modules
High Speed Data and Drop & Insert
Voice and data are mixed in the following example. The NextEDGE system’s
Drop and Insert feature allows voice information to be sent from a remote site to
a large site that contains a digital PBX. As a result, people at the far end can
make calls.
Multiple routers and data lines require adding a Synchronous Data APM to the
NextEDGE system because more than two data ports are needed.
Downtown HQ
Cluster
Controller
FEP
Terminal
NextEDGE
Port-2
System
FR
Router
NextEDGE
System Port-2
FR
Port-1
FR
Port-1
FR
Router
Mainframe
FXS and E&M
Voice
APL
Modems
Warehouse
FR = Frame Relay
99-16378
Off-Premises Extension (OPX)
In this example, a branch location is permitted to access the PBX line as if it were
locally connected. Likewise, the branch office phones appear as though they are
locally connected. As a result, a call between the two sites does not result in any
long distance charges.
Branch Office
Headquarters
NextEDGE
System
NextEDGE
System
FR
Router
FR
Port-1
FR
Port-1
FXO PBX
Line
FXS
X114
FR
Router
X114
PBX
Mainframe
X111
9191-A2-GH30-00
DRAFT — June 1999
X113
X112
99-16381
12-9
Application Modules
Direct Inward Dial (DID)
The configuration shown below allows an incoming call to dial to an extension
from the PBX, without going through the main switchboard.
NextEDGE
System
DID Lines
Central
Office
(CO)
T1 Facility
FXO
PBX
99-16382
Video Conferencing
The OCU-DP APM supports Switched 56 video. In the following example, an
external video codec is connected to OCU-DP ports using external Switched 56K
DSU/CSUs. Connection distance can be up to 18,000 feet. The OCU-DP APM
converts the 56K digital format from the line side into a digital DS0 format. This
DS0 format contains the 56K of data plus the necessary signaling information
required to set up the call to the far-end video equipment.
Frame
Relay
Router
Video
Codec
4-Wire
56K Facility
56K
DSU/CSU
12-10
T1FT1
NextEDGE
System
with OCU-DP
Cards(s)
DRAFT — June 1999
Switched
56K
DDS/PSTN
4-Wire
Video
Switched Codec
56K Facility
Integral 56K
DSU/CSUs
99-16383
9191-A2-GH30-00
Application Modules
Consolidated T1 Access of DDS Circuits
The following example illustrates how the OCU-DP APM can be used to reduce
facility costs associated with point-to-point 56/64K connections by consolidating
these lines into a single T1 facility. The T1 TDM NAMes shown in this application
could also be used to support both voice and high-speed data.
Typically, NextEDGE systems are placed at concentration points where a single
T1 line is less costly than multiple 56K lines (typically four or five). If DSUs are left
at both ends of the circuit, proprietary DSU Network Management Systems can
be used. Or, circuits associated with remote DSUs can be terminated directly on
a Synchronous Data APM at the Data Center to eliminate Data Center DSUs.
56 kbps
Data Center
56 kbps
T1
OCU-DP
Card
DCE
Manager
56 kbps
T1
56 kbps
56 kbps
Public
Network
T1
DSU
Carrier
Remote DSUs
99-16384
The OCU-DP APM does not support subrate DDS rates. Subrate applications can
be supported by installing a Paradyne 3610 or similar device configured for
56/64K line speed.
9191-A2-GH30-00
DRAFT — June 1999
12-11
Application Modules
Displaying APM Information
When an APM is installed, the Identity screen includes information about the
APM, along with the System and NAM information. For systems installed in a
5-slot housing, you can also view information about the APM in each slot.
" Procedure
To view APM identity information:
2. To view a single APM’s identity information, select System & NAM.
To view identity information for all APMs, select APM from the Identity menu.
The following information is provided:
EXP APM Type
The type of expansion APM that is installed: Synchronous
Data, DSX-1, E&M Voice, FXS Voice, FXOVoice, OCU (2) or
OCU (6).
H Empty indicates that no APM has been installed in the slot.
H Failed indicates that the APM has been removed from the
slot or has failed.
H Misconfig indicates that the APM in the slot is not
configured as defined in the NAM’s configuration table.
H Unsupport indicates that an unsupported APM is installed;
the NAM does not recognize the APM.
Serial Number
APM’s 7-character serial number.
Software Revision
Software version currently being used by the APM. Format
nn.nn.nn consists of a 6-digit number that represents the
major and minor revision levels. If the flash memory is
currently being downloaded, In Progress displays.
Hardware Revision
APM’s hardware version. Format nnnn-nnx consists of a
4-digit number, followed by two digits and one alphabetic
character.
For System and NAM information, see Displaying System Information in
12-12
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Viewing APM LEDs and Control Leads
The Display LEDs and Control Leads feature allows you to monitor a remote
system’s APMs, and is useful when troubleshooting control lead problems. This
feature is selected from the Status menu.
FrameSaver: Main Menu → Status → Display LEDs and Control Leads
T1 TDM: Main Menu → Status → Voice Status
Sample APM screens are shown below.
Voice Port APM Example
main/status/leds
Device Name: Node A
PARADYNE 9191
4/14/1999 23:32
DISPLAY LEDS & CONTROL LEADS
SLOT: 2 – FXS Voice APM
Voice Ports
OK
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Exit
MainMenu
Refresh
Synchronous Data Port APM Example
main/status/leds
Device Name: Node A
PARADYNE 9191
4/26/1998 23:32
SLOT: 2 – Sync Data Port APM
Port-1
OK
TXD
RXD
DTR
CTS
Port-2
OK
TXD
RXD
DTR
CTS
Port-3
OK
TXD
RXD
DTR
CTS
Port-4
OK
TXD
RXD
DTR
CTS
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Exit
MainMenu
Refresh
9191-A2-GH30-00
DRAFT — June 1999
12-13
Application Modules
OCU-DP APM Example
main/status/leds
Device Name: Node A
PARADYNE 9191
4/14/1999 23:32
DISPLAY LEDS & CONTROL LEADS
SLOT: 2 – OCU (6) APM
OCU-DP
1-TST
2-TST
3-TST
4-TST
5-TST
6-TST
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Exit
MainMenu
Refresh
For more information, see Viewing LEDs and Control Leads in Chapter 10,
OCU-DP APM LED Descriptions
The 2-port OCU-DP APM has three LED status indicators. The 6-port OCU-DP
APM has seven LEDs.
Table 12-1. OCU-DP APM General Status LED
Indication
Color
What It Means
OK
Power and
Operational
Status
Green
ON – APM has power and is operational.
9109 OCU
K
O
K
O
9109 OCU
Label
OFF – APM is in a local self-test, or there is a
failure.
TS
1-
T
T
TS
1-
TS
2-
T
T
TS
2-
PORT
Table 12-2. OCU-DP APM Port (1 to 6) LEDs
Color
What It Means
1-TST
2-TST
3-TST
4-TST
5-TST
6-TST
Operational
Status
Yellow
ON – A test is in progress.
T
T
TS
4T
TS
5ST
T
6-
12-14
Indication
TS
3-
PORT
98-15926
Label
98-15927
OFF – No test is active on the port, including
all test pattern generation, and any
loopback that may be active on the
local loop or the OCU-DP APM.
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Voice APM LED Description
The E&M, FXO, and FXS Analog Voice APMs each have one
LED status indicator.
Table 12-3. General Status Voice APM LED
Indication
Color
What It Means
OK
Power and
Operational
Status
Green
ON – APM has power and is
operational.
K
O
97-15648
9109 FXS
K
O
OFF – APM is in a local self-test,
or there is a failure.
9109 FXO
9109 E&M
K
O
496-15141
Label
496-15139
Synchronous Data APM LED Descriptions
The Synchronous Data APM has five LED status indicators.
IN
T
U
O
DSX 2
Table 12-4. General Status Synchronous Data APM LED
IN
DSX 1
T
U
O
IN
DSX 2 MON
Indication
Color
What It Means
OK
Power and
Operational
Status
Green
ON – APM has power and is operational.
T
U
O
Label
IN
DSX 1 MON
OFF – APM is in a local self-test, or there is a
failure.
T
U
O
9109 DSX
K
O
Table 12-5. Port 1, Port 2, Port 3, and Port 4 Synchronous Data APM LEDs
SI
G
F
O
O
DSX 1
Indication
Color
What It Means
1-OK
2-OK
3-OK
4-OK
Operational
Status
Green
ON – The interchange circuits for the port
are in the correct state to transmit
and receive data.
M
AL
Label
G
SI
F
O
O
DSX 2
M
AL
97-15649-01
9191-A2-GH30-00
OFF – The port is idle. Occurs if the port is
disabled, if an EDL OOF or EER
condition is present, if a DCLB is
active, or if the port is configured to
monitor DTR and/or RTS and the
lead(s) is not asserted.
DRAFT — June 1999
12-15
Application Modules
Displaying System and Test Status
Use the System and Test Status screen to display information concerning:
H
System Health and Status
H
Self-Test results
H
Status of tests currently running
See Chapter 10, Operation and Maintenance, for additional status messages.
Use the following menu selection sequence to display system and test status
information.
APM Health and Status Messages
These messages appear in the left column of the System and Test Status screen,
or the highest priority Health and Status message appears on the last line at the
bottom of the screen (right corner).
Table 12-6. APM Health and Status Messages (1 of 3)
Message
What It Indicates
What To Do
Abnormal Station
Code, Slot-s Port-p
An Abnormal Station Code
is being received from the
network DS0 for the
identified OCU-DP
interface. This indicates
that the far-end system is
disconnected or
powered-off.
1. Check that the far-end device
is operational.
The NAM detects an APM
failure for the identified slot.
1. Check if APM is removed from
the slot.
APM Card Failed,
Slot s
2. Check the cable to the far-end
device.
2. Remove, then reinstall the
APM.
representative.
12-16
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Message
What It Indicates
What To Do
DDS Net Failure,
yyyyyy Slot-s Port-p
The specified OCU-DP
interface is receiving DDS
network code yyyyyy from
the network. This is a 6-bit
code representing bits 2–7
of the DS0 code defined in
AT&T PUB 62310. The
least significant bit is to
the left.
failure code (yyyyyy) to your
DDS Network Fail
yyyyyy Slot-s Port-p
2. Reset the system by using the
Reset Device feature to clear
the condition and message.
Reset Device
3. Contact your DDS service
provider.
LOS at OCU-DP,
Slot-s Port-p
specified OCU-DP
interface. An LOS is
declared when a signal has
been absent on the local
loop for more than two
consecutive minutes.
Check the OCU-DP???
Loss of Loop Timing,
Slot-s Port-p
The OCU-DP interface in
Slot s, Port p cannot
recover timing from the
received signal on the local
loop.
Check that the system is
configured for the correct rate
(e.g., 19.2 kbps) when the
OCU-DP is configured for
56 kbps or Switched 56
operation.
condition has been
detected on the specified
OCU-DP interface. An LOS
is declared when a signal
has been absent on the
local loop for more than two
consecutive seconds.
1. Check that the system is
powered up.
Loss of Loop Timing
s-p
Loss of Signal,
Slot-s Port-p
9191-A2-GH30-00
DRAFT — June 1999
2. Check the cable.
12-17
Application Modules
Message
What It Indicates
What To Do
Module MisConfig,
Slot-s
The APM in slot xx is not
the one specified in the
NAM’s configuration table.
1. Replace the APM with the
type of APM specified by the
configuration table.
2. Change the current
configuration to reflect the
type of APM in the slot. To do
this, edit the configuration,
accept the APM, then save the
configuration.
Module Unsupported,
Slot-s
The NAM does not
recognize the APM.
1. Check that an E&M Voice
APM, FXS Voice APM, FXO
Voice APM, Dual DSX APM,
or Synchronous Data APM is
installed in Slot s.
2. For Model 926x T1 TDM NAM,
check that there is not more
than one DSX APM installed
(only one is supported).
3. Re-download the NAM
software if new APMs are
supported in later releases.
4. Replace the APM.
representative.
64KCC Loop OOF,
Slot-s Port p
12-18
A Dual DSX APM has been
installed in a T1 TDM
system.
Remove the Dual DSX APM.
A second DSX APM has
been installed.
Remove the second DSX APM.
Only one is supported.
condition has been
detected for the identified
OCU-DP interface.
1. Check the that system is
configured for the correct
speed.
DRAFT — June 1999
2. Check the cable to ensure that
the pairs are not crossed.
9191-A2-GH30-00
Application Modules
APM Test Status Messages
The right-most column of the System and Test Status screen shows the tests that
are currently active on the NAM or APM (see Table 12-7).
You have the option of allowing the test to continue or aborting the test. For more
about APM tests, see APM Tests on page 12-65. See Chapter 13,
Troubleshooting, for more information on tests, including how to start and stop
them.
Table 12-7. APM Test Status Messages (1 of 2)
9191-A2-GH30-00
Message
What It Indicates
DCLB, Slot s Port p
A Data Channel Loopback (DCLB) test is active on
Slot s, Port p.
DSXs-p LLB Test Active
A DSX-1 Line Loopback (LLB) test is active on
Slot s, Port p.
DSXs-p PLB Test Active
A DSX-1 Payload Loopback (PLB) test is active on
Slot s, Port p.
DSXs-p RLB Test Active
A DSX-1 Repeater Loopback (RLB) test is active
on Slot s, Port p.
DTLB, Slot s Port p
A Data Terminal Loopback (DTLB) test is active on
Slot s, Port p.
DTPLB, Slot s Port p
A Data Terminal Payload Loopback (DTPLB) test
is active on Slot s, Port p.
Forced Signal, Slot s Port p
A forced signaling test is active on Slot s, Port p.
Lamp Test Active
The Lamp Test is active, causing all LEDs on the
NAM and APMs to blink.
Latching CSU LB, Slot-s Port-p
A Latching CSU Loopback test is active on the
specified OCU-DP interface.
Latching DSU LB, Slot-s Port-p
A Latching DSU Loopback test is active on the
Latching OCU LB, Slot-s Port-p
A Latching OCU Loopback test is active on the
Networkn LLB Test Active
A network Line Loopback (LLB) test is active on
specified Network interface (n).
Networkn PLB Test Active
A network Payload Loopback (PLB) test is active
on specified Network interface (n).
Networkn RLB Test Active
A network Repeater Loopback (RLB) test is active
on specified network interface (n).
DRAFT — June 1999
12-19
Application Modules
Table 12-7. APM Test Status Messages (2 of 2)
Message
What It Indicates
Non-Latching CSU LB, Slot-s
Port-p
A Nonlatching CSU Loopback test is active on the
Non-Latching DSU LB, Slot-s
Port-p
A Nonlatching DSU Loopback test is active on the
Non-Latching OCU LB, Slot-s
Port-p
A Nonlatching OCU Loopback test is active on the
specified OCU-DP interface.NO TAG
No Test Active
No tests are currently running.
OCU Data LB, Slot-s Port-p
An OCU Data Loopback test is active on the
OCU DS-0 OCU LB, Slot-s Port-p
An OCU Data Loopback test is active on the
OCU Line LB, Slot-s Port-p
An OCU Line Loopback test is active on the
Pttn Active, or
Mon Pttn,
The specified pattern test is active or is being
monitored on the specified interface.
H Networkn
H On Network 1, or Network 2 if a Dual T1 TDM
NAM.
12-20
H DSXs-p
H On the DSX-1 interface in Slot s, Port p.
H Slot s Port p
H On a synchronous data port in Slot s, Port p.
Voice ALB, Slot-s Port-p
A voice Analog Loopback (ALB) test is active on
the specified OCU-DP interface.
Voice DLB, Slot-s Port-p
A voice Digital Loopback (DLB) test is active on
the specified OCU-DP interface.
Voice DRS, Slot-s Port-p
A voice Digital Reference test tone is active on the
Voice DRS, Slot-s Port-p
A voice Digital Reference (DRS) test tone is active
on the specified OCU-DP interface.
Voice Forced Signal, Slot-s Port-p
A voice forced signaling condition is active on the
Voice LLB, Slot-s Port-p
A voice Line Loopback (LLB) test is active on the
Voice Quiet, Slot-s Port-p
A voice quiet test tone is active on the specified
OCU-DP interface.
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Viewing Voice APM Status
Use the Voice Status screen to display information about analog voice cards
installed in your system.
Main Menu → Status → Voice Status
Enter the desired voice APM’s slot number. Status information varies depending
upon the type of voice APM installed.
Table 12-8. Voice APM Status (1 of 3)
View this field . . .
To find the . . .
E&M Voice APM
Port Status
Status of the port.
Assigned To
Interface the port is assigned to.
Operating Mode
Operating mode of the voice port that was configured
using the Operating Mode configuration option on the
Voice Ports screen. See the Table 10-13. E&M Voice
Options on page for configuration information.
Signaling Type
Type of signaling used by the voice port that was
configured using the switches on the E&M APM. See
the Table 10-13. E&M Voice Options on page for
configuration information.
Call Progress
Current condition of the port.
TX ABCD bits
Current value of the ABCD bits that are being
transmitted to the T1 interface.
RX ABCD bits
Current value of the ABCD bits that are being received
from the T1 interface.
E-Lead State
Current status of the E-lead (On or Off).
M-Lead State
Current status of the M-lead (On or Off).
Trunk Cond CGA
Displays the status of trunk conditioning (On for CGA,
Off for no CGA).
FXO Voice APM
9191-A2-GH30-00
Port Status
Status of the port.
Assigned To
Operating Mode
Voice Ports screen.
Signaling Type
configured using the Signaling Type configuration option
on the Voice Ports screen. See Table 10-12. FXO Voice
Call Progress
DRAFT — June 1999
12-21
Application Modules
To find the . . .
FXO Voice APM (Cont’d)
TX ABCD bits
Current value of the ABCD signaling bits that are being
RX ABCD bits
received from the T1 interface.
T-R Control
Current status of the tip and ring leads:
H Loop. Tip and Ring are connected together.
H Rgnd. Ring lead is attached to ground.
H Open. Ring lead is not connected to either the Tip
lead or the ground.
H Lpgnd. Tip and Ring are connected together, and are
connected to ground.
T-R Receive
Status of what the attached device is doing with the Tip
and Ring leads of the FXO port.
H RbTo. Attached device has battery applied to the
Ring lead and the Tip lead is opened
H RbTg. Attached device has battery applied to the
Ring lead and the Tip lead is grounded
H TbRg. Attached device has battery applied to the Tip
lead and the Ring lead is grounded
H Ring. Attached device is applying Ringing voltage
between Tip and Ring
H ToRo. Attached device has both Tip and Ring leads
open.
H TgRo. Attached device has the Tip lead grounded
and the Ring lead open.
H TgR*. Attached device has the Tip lead grounded
and the Ring lead state is unknown.
H ToR*. Attached device has the Tip lead open and the
Ring lead state is unknown.
H RoT*. Attached device has the Ring lead open and
the Tip lead state is unknown.
Trunk Cond CGA
12-22
Displays the status of trunk conditioning (On during
CGA, Off for no CGA).
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
To find the . . .
FXS Voice APM
Port Status
Status of the port.
Assigned To
Operating Mode
Voice Ports screen. See Table 10-11. FXS Voice
Signaling Type
configured using the Signaling Type configuration option
on the Voice Ports screen. See Table 10-11. FXS Voice
Call Progress
TX ABCD bits
RX ABCD bits
received from the T1 interface.
T-R Control
Current status of the tip and ring leads:
H RbTo. A – 48 Vdc battery is applied to the Ring lead
and the Tip lead is opened
H RbTg. A – 48 Vdc battery is applied to the Ring lead
and the Tip lead is grounded
H TbRg. A – 48 Vdc battery is applied to the Tip lead
and the Ring lead is grounded
H Ring. Ringing voltage is applied between Tip and
Ring
T-R Receive
Status of what the attached device is doing with the Tip
and Ring leads of the FXS port.
H Loop. Tip and Ring are connected together
H Rgnd. Ring lead is grounded by attached device
H Open. Ring lead is not connected to either the Tip
lead or the ground
Trunk Cond CGA
9191-A2-GH30-00
Displays the status of trunk conditioning (On for CGA,
Off for no CGA).
DRAFT — June 1999
12-23
Application Modules
Viewing Cross Connect Status
Slot assignments are made using the Cross Connect configuration option. See
Assigning Cross Connections in Chapter 5, Configuration, for making time slot
assignments. Use the Cross Connect Status screen to display time slot
assignments for:
H
Network Channels
H
DSX-1 Channels
H
Ports
Displaying Network Channels
Use the Network Channel Display screen to display DS0 assignments for each
DS0 on the network interface. This screen also provides information on the slot
assignment for each NAM or APM type.
FrameSaver: Main Menu → Status → Timeslot Assignment Status →
Network Timeslot Status
T1 TDM: Main Menu → Status → Cross Connect Status →
Network Channel Display
Select the desired network interface: 1 for Network 1, 2 for Network 2 (only the
Model 926x provides Network 2).
The Network Channel Display screen displays 24 two-field entries in three rows.
Together, each two-field entry defines the assignment for one Network interface
time slot. The top field represents the time slot of the Network Interface. The
bottom field represents the cross connect status of the associated (top field)
network time slot.
The Network Time Slot Fields (top) . . . Indicates . . .
12-24
N01 to N24
The Network Interface time slot (01 to 24).
(bottom) . . .
Indicates . . .
Unassgn
The time slot is unassigned.
SsPp
The voice or synchronous data Port p of
Slot s is assigned to the Network Interface
time slot (01 to 24).
Netn/yy
Network n (1 or 2) time slot yy is assigned to
the Network interface time slot (01 to 24),
using Clear Channel.
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
(bottom) . . .
Indicates . . .
Netn/yyr
Network n (1 or 2) time slot yy is assigned to
the Network Interface time slot (01 to 24),
using Robbed Bit Signaling (r ).
Ds-p/yy
The DSX-1 on Slot s, Port p, time slot yy is
assigned to the Network Interface time slot
(01 to 24).
Ds-p/yyr
The DSX-1 on Slot s, Port p, time slot yy is
assigned to the Network Interface time slot
(01 to 24), using Robbed Bit Signaling (r ).
RsvdAPM
The time slot is assigned to an APM which is
either:
H Failed,
H Removed or not installed, or
H Has been replaced by an APM type that
is not compatible with the configuration.
DDL
The time slot is reserved for a management
path using Direct Data Link (DDL).
Slot Assignment information. NAM or APM physical slot assignment
information appears below the time slot fields.
Physical Slot . . .
T1 NAM – T1 TDM NAM.
Sync Data – 4-port synchronous data APM.
DSX-1 – 2-port Dual DSX APM.
E&M Voice – 8-port E&M Voice APM.
FXO Voice – 8-port FXO Voice APM.
FXS Voice – 8-port FXS Voice APM.
OCU (2) – 2-port OCU-DP APM.
Misconfig – The slot contains a
misconfigured APM.
Unsupport – The slot contains an
unrecognized APM.
Failed – The slot contained an APM that has
been removed or is no longer operational.
9191-A2-GH30-00
DRAFT — June 1999
12-25
Application Modules
Displaying DSX-1 Channels
Use the Network Channel Display screen to display all of the DS0 assignments
for each DS0 on the DSX-1 interface. This screen also provides information on
the slot assignment for each NAM or APM type.
FrameSaver: Main Menu → Status → Timeslot Assignment Status →
DSX-1 Timeslot Status
T1 TDM: Main Menu → Status → Cross Connect Status →
DSX-1 Channel Display
Select the desired DSX-1 slot and port.
NOTE:
The DSX-1 Channel screen will not appear if the Interface Status field on the
DSX-1 Interface Option screen is set to Disable.
The DSX-1 Channel Display screen displays 24 two-field entries in three rows.
Together, each two-field entry defines the assignment for one DSX-1 interface
time slot. The top field represents the time slot of the DSX-1 Interface. The
bottom field represents the cross-connect status of the associated (top field)
DSX-1 time slot.
The DSX-1 Time Slot Fields (top) . . .
Indicate . . .
D01 to D24
The DSX-1 Interface time slot (01 to 24).
(bottom) . . .
Indicates the . . .
blank
Time slot is unassigned.
SssPp
Voice or synchronous data port (p) of slot
(ss) is assigned to DSX-1 time slot (01 to
24).
Netnyy
Network Interface n (1 or 2), time slot (yy ) is
assigned to DSX-1 time slot (01 to 24), using
Clear Channel.
Netnyyr
Network Interface n (1 or 2), time slot (yy ) is
assigned to DSX-1 time slot (01 to 24), using
Robbed Bit Signaling (r ).
RsvdAPM
Time slot is assigned to an APM which is
either:
H failed,
H removed or not installed, or
H has been replaced by an APM type that is
not compatible with the configuration.
12-26
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Slot Assignment information. NAM or APM physical slot assignment
information appears below the DSX-1 interface time slot fields.
Physical Slot . . .
Sync Data – 4-port Synchronous Data APM.
DSX-1 – 2-port Dual DSX APM.
E&M Voice – 8-port E&M Voice APM.
Misconfig – The slot contains a
misconfigured APM.
Unsupport – The slot contains an
unrecognized APM.
Failed – The slot contained an APM that has
been removed or is no longer operational.
9191-A2-GH30-00
DRAFT — June 1999
12-27
Application Modules
Displaying Port Assignments
Use the Port Assignments Display screen to view port assignment information for
each voice and data port on the NAM and APMs.
Main Menu → Status → Cross Connect Status →Port Assignment Display
To find the . . .
Slot
Slot number.
Type
Type of NAM or APM occupying the slot. Possible values are:
Sync Data – 4-port Synchronous Data APM.
E&M Voice – 8-port E&M APM.
Misconfig – The slot contains a misconfigured APM.
Unsupport – The slot contains an unrecognized APM.
Failed – The slot contained an APM that has been removed or
is no longer operational.
Assignment
Port assignment. Possible values are:
Blank – slot is empty or port does not exist on the NAM or the
APM.
Disable – The port is disabled.
Unassgn – The port is unassigned.
Netn – The port is assigned to the Network Interface 1 or 2.
DSXss-p – The port is assigned to the DSX-1 interface in Slot s
(always 01), Port p on a clear channel time slot. Ports cannot
be cross-connected to the DSX APM.
SssPp – The port-to-port assignment of the Slot s and
synchronous data Port p shown in this field.
12-28
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Viewing APM Performance Statistics
Statistics are defined in AT&T Technical Reference (TR) 54016.
H
Network Performance Statistics screen – Displays a complete view of the
performance of the network interface and a synchronous data port over the
previous 24-hour period.
H
Sync Data Performance Statistics screen – Displays a complete view of the
performance of the network interface and a synchronous data port over the
previous 8-hour period.
Statistics That Can Be Collected
You can collect the following metrics:
9191-A2-GH30-00
H
Errored Seconds (ES) – Any second with one or more ESF Error events.
H
Unavailable Seconds (UAS) – Any second in which service is unavailable.
H
Severely Errored Seconds (SES) – Any second with 320 or more CRC
errors or one or more Out Of Frame (OOF) events.
H
Bursty Errored Seconds (BES) – Any second with more than one but less
than 320 CRC errors.
H
Controlled Slip Seconds (CSS) – Any second with one or more controlled
slips (a replication or deletion of a DS1 frame by the receiving device). This is
collected for network performance statistics only.
H
Loss of Frame Count (LOFC) – The number of Loss of Frame conditions.
H
Complete – Indicates whether or not the 15 minutes worth of far-end
statistics contain 900 seconds worth of statistics. Bad T1 network conditions
or a loopback test can prevent far-end statistics from reaching the NextEDGE
system. If one or more seconds of far-end performance statistics are missing,
then this field displays No. Otherwise, Yes is displayed. This field appears on
the Sync Data Performance Statistics screen only.
DRAFT — June 1999
12-29
Application Modules
Hot Swapping APMs
The NextEDGE system allows you to insert and remove APM cards and their
matching I/O cards without powering down the system or interrupting data on the
network or on other APMs. The system automatically recognizes when an APM is
inserted or removed, and can display the configuration option settings and MIB
objects applicable to the APM that was inserted or removed.
NOTE:
You do not have access to screens and configuration options that are not
valid for the given configuration, nor can you preconfigure or predelete a
configuration for an APM prior to inserting it in the housing. To see
configuration options for an inserted APM, you must exit the configuration
screen, then reenter it.
APM Insertion
Insertion of an APM into a housing occurs under one of the following three
conditions.
If previously the slot . . . Then . . .
Was unassigned
The configuration options for this new APM will be set to
factory defaults and will be accessible from the MIB and the
asynchronous terminal.
Contained the same type
of APM
The existing configuration options will be used and will be
accessible from the MIB and the asynchronous terminal.
Contained a different type The system will generate a Module Misconfiguration alarm
of APM
and trap for the selected slot. The screens and field choices
applicable to this APM will not be displayed until you accept
the APM upon loading or saving a configuration, or via an
enterprise MIB. When you accept the new APM, the
previous APM’s configuration is deleted, the new APM’s
configuration options are set to factory defaults, and the
screens and field choices applicable to the new APM will be
displayed.
If you reject the APM, the configuration options for the
previous APM can be edited, but all other configuration
options and screens will not display fields or choices or MIB
objects applicable to either the previous or the current APM.
12-30
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
APM Removal
When you remove an APM from its slot, you can still edit the applicable
If viewing a Status or Test screen when an APM is removed:
H
The message APM Removed will display after the screen is refreshed and all
fields relating to the APM will be cleared.
H
Only the ESC (previous menu), Main Menu, and Exit virtual functions will be
available when no other valid slots are available for selection.
H
MIB objects applicable to the removed APM, and attempts to do a get or set
of those objects will display the message No Such Name.
T1 TDM ASCII Alarm Messages
The alarm messages in this section are sent to an ASCII terminal or printer
attached to a T1 TDM system’s communication port, either locally or remotely via
an external device.
H
When set, an alarm is sent at the start of an alarm condition.
H
An Alarm Cleared message is sent when the alarm condition no longer
exists.
H
If more than one alarm condition exists, only the highest priority alarm will be
sent. View Health and Status for all conditions.
CAUTION:
You should be sure to clear alarms as they occur by correcting the
condition that caused the alarm. Additional alarms will not be reported
until the previous alarm is cleared. Therefore, if you do not clear an
alarm, a serious outage could occur and you will be unaware of it
unless you are monitoring the system via the user interface or SNMP.
9191-A2-GH30-00
DRAFT — June 1999
12-31
Application Modules
Table 12-9 lists the alarm messages and corresponding clear messages in
alphabetical order. Priority order is identified. Each alarm message contains:
H
Date and time (month/day/year hours:minutes:seconds ) that the condition
occurred or was cleared.
H
The user-configured device name.
H
Alarm description.
H
An identification of the affected interface (when applicable).
Table 12-9. T1 TDM ASCII Alarm Messages (1 of 6)
12-32
Message
What It Indicates
What To Do
Priority
month/day/year
hours:minutes:seconds –
has been received at the
OCU-DP port in slot s
port p.
An Abnormal Station
1. Check that the
far-end DSU is
Code from the network
operational.
DS0 is detected on the
specified OCU-DP
2. Check the far-end
port
cable to the DSU.
17
month/day/year
Alarm condition no
longer exists.
Alarm Cleared for Abnormal
Station Code at OCU-DP
port in slot s port p.
month/day/year
Alarm Indication Signal
(AIS) received at the
Network 1/Network 2
Interface or at the DSX-1
Interface in slot s port p.
An Alarm Indication
Signal condition is
detected on the
specified Network or
DSX-1 interface.
Check the status of
the far-end system. If
necessary, contact
network provider for
Network interface.
month/day/year
Alarm Cleared for Alarm
Indication Signal (AIS) at
the Network 1/Network 2)
Alarm condition no
longer exists.
month/day/year
An APM Card Failure has
been detected for slot s.
An APM card failure is
detected for the
identified slot.
1. Check that the APM 11
card is seated
properly.
month/day/year
Alarm Cleared for an APM
Card Failure for slot s.
Alarm condition no
longer exists.
6 (Net)
7 (DSX-1)
Check the DTE
attached to the DSX-1
interface.
2. Contact your
service
representative.
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Message
What It Indicates
What To Do
Priority
month/day/year
Continuous Loss Of Signal
(LOS) condition detected at
the Network 1/Network 2
Interface or at DSX-1
LOS condition
detected.
1. Check the cable to
the Network/DSX-1
interface.
2 (Net)
3 (DSX-1)
month/day/year
Alarm Cleared for Loss Of
Signal (LOS) condition at
Alarm condition no
longer exists.
month/day/year
Continuous Out Of Frame
(OOF) detected at the
Network 1/Network 2
Interface or at DSX-1
An out-of-frame
condition is detected
at the specified
Network or DSX-1
interface.
1. Ensure that the line
framing format
configuration option
setting matches the
setting of the
equipment (DSX-1)
or network (Net).
2. Contact network
provider.
4 (Net)
5 (DSX-1)
2. Contact network
provider.
month/day/year
Alarm Cleared for Out of
Frame (OOF) condition at
Alarm condition no
longer exists.
month/day/year
Continuous Out of Frame
(OOF) condition at
synchronous data port in
slot s port p.
A continuous
out-of-frame condition
occurred on the
synchronous data port
for the identified slot
and port.
1. Ensure that EDL is
enabled on the
far-end port. Refer
to the Technical
Reference for
setting
configuration
options.
13
2. There is a network
problem with the
fractional portion of
the link carrying this
port’s data. Contact
network provider.
month/day/year
Alarm Cleared for Out Of
Frame (OOF) condition at
slot s port p.
9191-A2-GH30-00
Alarm condition no
longer exists.
DRAFT — June 1999
12-33
Application Modules
12-34
Message
What It Indicates
What To Do
Priority
month/day/year
A DDS Network Failure
code has been received at
port p.
A DDS network failure
is being detected on
the specified OCU-DP
port.
Contact the DDS
service provider.
19
month/day/year
Alarm Cleared for a DDS
Network Failure code at
port p.
Alarm condition no
longer exists.
month/day/year
An Excessive Error Rate
(EER) has been detected at
the Network 1/ Network 2
Interface.
An Excessive Error
Rate condition is
detected on the
network interface.
Contact network
provider.
month/day/year
Alarm Cleared for
Excessive Error Rate
(EER) at the Network 1/
Network 2 Interface.
Alarm condition no
longer exists.
month/day/year
hours/minutes/seconds –
An Excessive Error Rate
(EER) has been detected at
slot s port p.
An excessive error
rate occurred on the
synchronous data port
for the identified slot
and port.
There is a network
problem with the
network provider.
month/day/year
Alarm Cleared for
(EER) at synchronous data
Alarm condition no
longer exists.
month/day/year
A Loss of Loop Timing has
been detected at OCU-DP
The specified
OCU-DP port cannot
recover timing from
the received signal on
the local loop.
Check that the CPE
CSU/DSU rate
matches the OCU-DP
rate.
month/day/year
Alarm Cleared for Loss of
Loop Timing at OCU-DP
Alarm condition no
longer exists.
DRAFT — June 1999
12
14
20
9191-A2-GH30-00
Application Modules
Message
What It Indicates
What To Do
Priority
month/day/year
hours:minutes:seconds – A
Loss Of Signal (LOS) has
been detected at the
port p.
LOS condition
detected.
1. Check the cable to
the OCU-DP port.
16
month/day/year
Alarm Cleared for a Loss
Of Signal (LOS) at
port p.
Alarm condition no
longer exists.
month/day/year
A Module Misconfiguration
condition was detected for
slot s.
The identified slot
previously contained a
different type of APM.
Ensure that the APM
installed is the correct
type. If it is not, install
the correct APM type.
The card needs to be
accepted. Refer to the
Technical Reference
for additional
information, if
necessary.
month/day/year
Alarm Cleared for the
Module Misconfiguration for
slot s.
Alarm condition no
longer exists.
month/day/year
Power Supply Alarm
condition detect.
A power supply or fan
tray problem is
detected on the
system.
1. Check that the
power supply or fan
tray is mounted
correctly in the
housing.
2. Contact network
provider.
8
1
2. Contact your
service
representative.
month/day/year
Alarm Cleared for Power
Alarm condition.
9191-A2-GH30-00
Alarm condition no
longer exists.
DRAFT — June 1999
12-35
Application Modules
Message
What It Indicates
What To Do
Priority
month/day/year
Yellow alarm signal
received at the Network 1/
Network 2 Interface or at
the DSX-1 Interface in
slot s port p.
A Yellow alarm signal
is detected on the
specified Network or
DSX-1 interface.
1. Check the Network
and/or DSX-1
cable.
9 (Net)
10 (DSX-1)
month/day/year
Alarm Cleared for Yellow
alarm signal at the
Network1/Network 2
Alarm condition no
longer exists.
month/day/year
A Primary Clock Source
Failure has occurred.
The primary clock
source has failed. The
system is operating
from the secondary
clock source.
1. If the primary clock
was derived from
the network,
contact the network
provider.
2. Contact network
provider for
Network interface
problem. Check
equipment for
DSX-1 interface
problem.
22
2. Check the clock
source. Contact
your service
representative.
month/day/year
Alarm Cleared for a
Primary Source Failure.
Alarm condition no
longer exists.
month/day/year
A Secondary Clock Source
Failure has occurred.
The secondary clock
source has failed. The
system is operating
from the internal clock.
1. If the secondary
clock was derived
from the network,
contact the network
provider.
21
2. Check the clock
source. Contact
your service
representative.
month/day/year
Alarm Cleared for a
Secondary Source Failure.
12-36
Alarm condition no
longer exists.
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Message
What It Indicates
What To Do
Priority
month/day/year
A 64KCC Loop Out of
Frame has been detected
at OCU-DP port in slot s
port p.
A continuous
out-of-frame condition
occurred on the
OCU-DP port for the
identified slot and port.
There is a network
problem with the
network provider.
18
month/day/year
Alarm Cleared for a 64KCC
Loop Out Of Frame at
port p.
Alarm condition no
longer exists.
Automatic Dialing Out When an Alarm Occurs
For T1 TDM systems, you can control whether generated alarm messages will
initiate a call if a connection on the COM port external device has not already
been established.
To dial out when an alarm occurs you must:
H
Connect the modem to the COM port using the appropriate cable.
H
Select the ASCII alarms to receive for each interface.
H
Configure the phone directory to use for Dial Out Alarms.
H
Enable Alarm & Trap Dial Out.
H
Enable Call Retry, if desired.
" Procedure
To enable the desired ASCII alarms for each interface:
1. Follow this menu selection sequence to display the Load Configuration From
screen:
Main Menu → Configuration
2. Select the desired configuration area and press Return. The Configuration
Edit/Display screen appears.
9191-A2-GH30-00
DRAFT — June 1999
12-37
Application Modules
3. Select the ASCII alarms to enable for the interface.
To enable . . .
Set the configuration option(s) . . .
T1 alarms
Configuration → Network
DSX-1 alarms
Configuration → DSX-1
Synchronous Data Ports alarms
Configuration → Sync Data Ports
OCU-DP Ports alarms
Configuration → OCU-DP Ports
4. Configure the phone directory to use for dialing out alarms (see Displaying
Directory Numbers and Changing Directory Numbers in Chapter 8, Operation
and Maintenance).
5. Select Alarm from the Configuration Edit/Display menu . The Alarms Options
screen appears.
To . . .
Automatically initiate a call (dial out)
Alarm & Trap Dial-Out to Enable.
Retry the call if the call cannot be
completed
Call Retry to Enable.
Enable ASCII alarms
Configuration → Alarm
6. Save your changes. The Save Configuration To screen appears.
7. Select the configuration area where you want to save the changes to and
press Return. When Save is complete, Command Complete appears at the
bottom of the screen.
12-38
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
FrameSaver APM Alarms
The following table describes the alarm conditions that are unique to APMs.
These alarms are in alphabetical order.
For information about other alarms, see Alarms in Chapter 13, Troubleshooting.
Table 12-10. FrameSaver APM Alarm Conditions (1 of 1)
Alarm Condition
What It Indicates
What To Do
Abnormal Station
Code
is being received from the
network DS0 for the
identified OCU-DP
interface. This indicates
that the far-end system is
disconnected or
powered-off.
1. Check the APM’s slot location
and the affected port.
APM Card Failed
2. Check the cable to the far-end
device.
3. Check that the far-end device
is operational.
The NAM detects an APM
1. Check whether the APM was
removed from the slot.
card failure for the identified
slot, or the APM card was
2. Remove the APM, then
removed.
reinstall it.
representative.
DDS Network Failure
LOS
9191-A2-GH30-00
The OCU-DP specified
interface is receiving a 6-bit
DDS network code. This
code represents bits 0 –7 of
the DS0 code as defined in
AT&T PUB 62310.
failure code to your service
representative.
2. Reset the NextEDGE system
to clear the condition.
Reset Device
For an OCU-DP interface, a 1. Check that the cable is
Loss of Signal (LOS) alarm
ends.
is declared when a signal
has been absent on the
local loop for more than two 2. Verify that the DCE is powered
on.
consecutive minutes.
DRAFT — June 1999
12-39
Application Modules
Configuring APM Ports
Configure the following ports on the NAM and any APMs that are installed in your
system.
H
Synchronous Data ports on the NAM or the Synchronous Data APM
H
Voice ports on the FXS, FXO and E&M APMs
Once you have a port configured, you can copy that configuration to other ports
of the same type (see Copying Port Configurations on pageNO TAG).
The following configuration option tables are included in this chapter:
H
Table 12-12. FXS Voice Options on page 12-48.
H
Table 12-13. FXO Voice Options on page 12-52.
H
Table 12-14. E&M Voice Options on page 12-55.
H
Table 12-15. OCU-DP Physical Options on page 12-57.
Configuring Synchronous Data APM Ports
Use the Synchronous Data Port Options to configure the synchronous data
port(s) on the NAM or on any Sync Data APM associated with the NAM (see
Table 12-11).
Configuration → Sync Data Ports
NOTE:
If the selected Synchronous Data Port is disabled, Disable appears on the
screen. No other options are shown.
The Synchronous Data Port Options screen appears for Port 1 of the first slot
containing a Synchronous Data APM. If desired, enter the slot and port number of
another synchronous data port.
12-40
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Table 12-11. Synchronous Data Port APM Options (1 of 7)
Port Status
Determines whether the synchronous data port is being used and can be configured.
Display Conditions – This option does not appear when Port Status is set to Disable.
Enable – The port is active, and can be used to transmit and receive data.
Disable – The port is not active. When the port is disabled, the following will occur:
H Existing cross-connect assignments associated with the port will be cleared. The
message This action will clear any Cross Connections for the
Port. Are You Sure? No appears. If you select:
No – The operation is cancelled.
Yes – Port status is disabled.
Port Type
Possible Settings: E530, V.35, RS449, X.21
Default Setting: E530
Selects the synchronous data port type for the data port.
E530 – The port is an EIA-530A-compatible DCE. An EIA-530-compatible DTE can be
directly connected to the DB25 connector.
V.35 – The port is a V.35-compatible DCE. A V.35-compatible DTE can be connected to
the DB25 connector by using an MS34-to-DB25 adapter cable.
RS449 – The port is an RS449-compatible DCE. An RS449-compatible DTE can be
connected to the DB25 connector by using DB37-to-DB25 adapter cable.
X.21 – The port is a V.11/X.21-compatible DCE. A V.11/X.21-compatible DTE can be
connected to the DB25 connector by using a DB15-to-DB25 adapter cable.
Port Base Rate
Specifies the base rate for the synchronous data port. The data rate for the port is a
multiple (from 1 to 24) of the base rated specified by this configuration option.
Nx64 – The base rate for the port is 64 kbps. The data rate available for the port is
Nx64, where N is the number of channels to which the port is cross-connected (1–24).
Nx56 – The base rate for the port is 56 kbps. The data rate available for the port is
Nx56, where N is a number between 1 and 24.
9191-A2-GH30-00
DRAFT — June 1999
12-41
Application Modules
Transmit Clock Source
Possible Settings: Internal, External
Determines whether the transmitted data is clocked by the synchronous data port
internal clock, or by the clock supplied by the DTE connected to the synchronous data
port.
Internal – The DCE clocks transmitted data, and uses the interchange circuit DB
(CCITT 114) – Transmit Signal Element Timing (TXC) (DCE source) for timing the
incoming transmitted data.
External – The DTE externally provides the clock for the transmitted data, and the
synchronous data port uses the interchange circuit DA (CCITT 113) – Transmit Signal
Element Timing (XTXC) (DTE source) for timing the incoming transmitted data.
NOTE:
When an external clock is used, it must be synchronized to the same clock
source as the system.
Determines whether the clock supplied by the DCE on interchange circuit DB
(CCITT 114) – Transmit Signal Element Timing (DCE Source) TXC is phase inverted
with respect to interchange circuit BA (CCITT 103) – Transmitted Data (TD). Use this
configuration option when long cable lengths between the NAM and the DTE are
causing data errors.
Enable – Phase inverts the TXC clock on the DCE.
Disable – Does not phase invert the TXC clock on the DCE.
Invert Transmit and Received Data
Specifies whether the transmitted and received data for the synchronous data port is
logically inverted before being transmitted or after being received from the network. Use
this configuration option for applications where data is being transported using HDLC
protocol, whereby inverting the data ensures that the ones density requirements for the
network are met.
Enable – Inverts the transmitted and received data for the port.
Disable – Does not invert the transmitted and received data for the port.
12-42
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Send All Ones on Data Port Not Ready
Possible Settings: Disable, DTR, RTS, Both
Specifies the conditions on the synchronous data port that determine when valid data is
not being sent from the DTE. When this condition is detected, all ones are sent to the
network on the DS0 channels allocated to the port.
Disable – Interchange circuits from the DTE are not monitored. Data sent from the DTE
is always sent to the network for the port.
DTR – Monitors DTE Ready (DTR) to determine when valid data is sent from the DTE.
When DTR is off, all ones are sent to the network.
Display Conditions – This selection does not appear when Port Type is set to X.21.
RTS – Monitors Request to Send (RTS) to determine when valid data is sent from the
DTE. When RTS is off, all ones are sent to the network.
Both – Monitors both DTR and RTS to determine when valid data is sent from the DTE.
If either DTR or RTS is off, all ones are sent to the network.
Display Conditions – This selection does not appear when Port Type is set to X.21.
Action on Network Yellow Alarm
Possible Settings: None, Halt
Default Setting: Halt
Specifies the action to take on the synchronous data port when a yellow alarm is
received on the network interface. (A yellow alarm indicates a problem with the signal
being transmitted to the network.)
None – No action taken when a yellow alarm is received.
Halt – Halts the transmission of data received on the synchronous data port and all
ones are sent on circuit BB (ITU 104) – Receive Data (RD) and circuit CB (ITU 106) –
Clear-to-Send (CTS) is deasserted to the port when a yellow alarm is received.
Network Initiated Data Channel Loopback (DCLB)
Possible Settings: Disable, V.54, FT1, Both
Allows the initiation and termination of the data channel loopback (V.54 loop 2) to be
controlled by the receipt of a DCLB-actuate and DCLB-release sequence (either V.54,
or FT1 [ANSI] compliant sequences) from the network or far end system. When this
configuration is enabled (V.54, FT1, or Both), receiving a DCLB-actuate sequence on a
particular port causes the NAM to initiate a DCLB on that port (provided that a DCLB
can be performed based on the current state of the port and NAM). Receiving a
DCLB-release sequence terminates the DCLB.
Disable – Ignores the DCLB-actuate and DCLB-release for the port.
V.54 – DCLB-actuate and DCLB-release sequences that comply with the V.54 standard
for “inter-DCE signaling for point-to-point circuits” are recognized and will control the
initiation and termination of a DCLB (V.54 Loop 2) for the port.
FT1 – DCLB-actuate and DCLB-release sequences that comply with either the
ANSI.403, Annex B standard for “in-band signaling for fractional T1 (FT1) channel
loopbacks” are recognized and will control the initiation and termination of a DCLB for
the port.
Both – DCLB-actuate and DCLB-release sequences that comply with either the ANSI
or V.54 standard are recognized and will control the initiation and termination of a DCLB
for the port.
9191-A2-GH30-00
DRAFT — June 1999
12-43
Application Modules
Port (DTE) Initiated Loopbacks
Possible Settings: Disable, DTPLB, DCLB, Both
Allows the initiation and termination of a local Data Payload Loopback (DTPLB) or a
remote Data Channel Loopback (DCLB) to be controlled by the DTE for the
synchronous data port.
Disable – The DTE attached to the port does not control the Local DTPLB and remote
DCLBs.
DTPLB – The DTE attached to the port may control the DTPLB for the port. The
loopback is controlled by the interchange circuit LL (CCITT 141) – Local Loopback as
specified by V.54. The port remains in DTPLB loopback as long as interchange circuit
remains on.
DCLB – The DTE attached to the port may control the DCLB for the connected remote
port. The loopback is controlled by the interchange circuit RL (CCITT 140) – Remote
Loopback as specified by V.54.
NOTE:
The remote equipment must support inband V.54 loopback.
Both – The DTE attached to the port may control both the local DTPLB and remote
DCLBs.
Embedded Data Link
Specifies whether the Embedded Data Link (EDL) is enabled for the synchronous data
port. When the EDL is enabled, 8 kbps of the total bandwidth allocated for the port are
not available to the synchronous data port. For example, if the port rate is 256 kbps
(4 DS0 channels allocated) and the EDL is enabled, then only 248 kbps are available to
the port. The EDL provides detection of frame synchronization, CRC of the data stream
(excluding the 8 kbps EDL), and a 4 kbps inband data link between the local and remote
systems. The 4 kbps in-band data link can be used for performance report messages
(PRMs) and as a management link for IP traffic.
Display Conditions – This option does not appear when Management Link is set
to FDL.
Enable – EDL is enabled for the port.
NOTE:
EDL must be enabled for both the local port and associated remote port.
Disable – EDL is disabled for the port.
EDL Management Link
Possible Settings: Disable, Enable
Specifies whether the EDL management link is enabled for IP traffic on the synchronous
data port.
Display Conditions – This option does not appear when:
H EDL is set to Disable.
H Management Link is set to FDL.
Enable – EDL management link is enabled for IP traffic flow over the 4 kbps in-band
data link provided by the EDL.
Disable – EDL management link is disabled for IP traffic.
12-44
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
IP Address
Specifies the internet protocol address needed to access the EDL.
Display Conditions – This option does not appear when EDL Management Link is set
to Disable.
000.000.000.000 – 223.255.255.255 – Enter the IP address for the EDL. The first digit
(i.e., xxx.255.255.255) cannot be 0 or 127, or greater than 223. However,
000.000.000.000 is valid, representing a null address.
Clear – Clears the IP address and fills the address with zeros (i.e., 000.000.000.000).
Subnet Mask
Specifies the subnet mask for the EDL.
Display Conditions – This option does not appear when EDL Management Link is set
to Disable.
000.000.000.000 – 255.255.255.255 – Enter the subnet mask for the EDL. Subnet Mask
is based on the class of the IP address: Class A: 255.000.000.000,
Class B: 255.255.000.000, or Class C: 255.255.255.000.
Clear – Clears the subnet mask and fills the field with zeros (i.e., 000.000.000.000).
Routing Information Protocol
Possible Settings: None, Proprietary
Default Setting: Proprietary
Specifies which routing information protocol (RIP) is used to enable routing of
management between devices.
H EDL Management Link is set to Disable.
None – Does not use routing information protocol. Use this setting when the device at
the other end of the management link cannot accept routing information.
Proprietary – Uses a proprietary variant of RIP version 1 to communicate routing
information between devices.
9191-A2-GH30-00
DRAFT — June 1999
12-45
Application Modules
Near-End Performance Statistics
Possible Settings: Disable, Maintain, Send, Both
Specifies whether the T1 TDM system maintains near-end performance statistics and
sends Performance Report Messages (PRMs) for the synchronous data port.
H EDL Management Link is set to Disable.
NOTE:
If the local T1 TDM system is configured to send near-end performance
statistics, then the remote T1 TDM system must be configured to maintain
far-end performance statistics.
Disable – Does not maintain near-end performance statistics or send PRMs.
Maintain – Maintain near-end performance statistics for the port.
Send – Send PRMs over the port’s EDL every second. Each PRM contains the
performance statistics for the previous 4 seconds.
Both – Maintain near-end performance statistics and send PRMs over the port’s EDL.
Far-End Performance Statistics
Possible Settings: Disable, Maintain
Specifies whether the T1 TDM system maintains far-end performance statistics and
sends Performance Report Messages (PRMs) for the synchronous data port.
NOTE:
If the local T1 TDM system is configured to maintain far-end performance
statistics, then the remote T1 TDM system must be configured to send
near-end performance statistics.
Disable – Does not monitor the port’s EDL for PRMs or maintain far-end performance
statistics.
Maintain – Monitors the port’s EDL for PRMs and maintains far-end performance
statistics.
Out of Frame (OOF) Alarm
Out of Frame (OOF). Specifies whether an alarm is generated when an out-of-frame
condition is detected on the synchronous data port.
H Embedded Data Link is set to Disable.
H Management Link is set to FDL on the Network Interface Options screen.
Enable – Generates an alarm.
Disable – Does not generate an alarm.
12-46
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Excessive Error Rate (EER) Alarm
Specifies whether an alarm is generated when an excessive error rate condition is
detected on the synchronous data port.
Enable – Generates an alarm.
Disable – Does not generate an alarm.
Sets the error rate threshold that determines when an excessive error rate (EER)
condition is declared for a synchronous data port. The EER is determined by the ratio of
the number of CRC5 errors to the total number of bits received over a set period of time.
H Excessive Error Rate is set to Disable.
H Both Near-End and Far-End Performance Statistics are set to Disable.
10E-4 – Declares an EER if more than 1,535 CRC5 errors are detected in a 10-second
period.
10E-5 – Declares an EER if more than 921 CRC5 errors are detected in a 60-second
period or a 10–4 condition occurs. Clears when fewer than 922 CRC5 errors are
period or a 10–5, or 10–4 condition occurs. Clears when fewer than 93 CRC5 errors are
period or a 10–6, 10–5, or 10–4 condition occurs. Clears when fewer than 10 CRC5
10E-8 – Declares an EER if more than 41 CRC5 errors are detected in three 15-minute
intervals or a 10–7, 10–6, 10–5, or 10–4 condition occurs. Clears when fewer than
10E-9 – Declares an EER if more than 4 CRC5 errors are detected in three 15-minute
intervals or a 10–8, 10–7, 10–6, 10–5, or 10–4 condition occurs. Clears when fewer than
9191-A2-GH30-00
DRAFT — June 1999
12-47
Application Modules
Configuring FXS Voice APM Ports
Use the FXS (Table 12-12), FXO (Table 12-13), and E&M (Table 12-14) Voice
Options to configure the voice port on the voice APM in the selected slot.
Configuration → Voice Ports
The Voice Port Options screen appears for Port 1 of the first slot containing a
voice APM (either FXS, FXO or E&M). The displayed fields differ, depending on
the type of voice APM in the selected slot.
Table 12-12. FXS Voice APM Options (1 of 4)
Port Status
Specifies whether the FXS voice port is in use, and can be configured and assigned to a
time slot on the T1 interface to transmit and receive voice frequency signals.
Display Conditions – This option only appears when Port Status is set to Enable.
Enable – The port is active, and can be configured and assigned to a time slot.
Disable – The port is not active, cannot be configured, and does not take up a time slot.
No – The operation is cancelled. (Pressing either the Esc or Ctrl-a key acts as a
No.)
Yes – Port status is disabled and any cross connections are cleared.
Operating Mode
Possible Settings: FXS, FXSDN, FXSDN/WINK, PLAR, DPO
Default Setting: FXS
Selects the operating mode for the FXS voice port.
FXS – Enables the Foreign Exchange Station (FXS) mode, supporting a bidirectional
connection to a telephone device, PBX, or key system trunk. This mode uses 4-state
signaling (A&B).
FXSDN – Enables Foreign Exchange Station Software-Defined Network (FXSDN)
mode for operation on software-defined networks. This mode is used by Class 4
switches and uses 2-state signaling (A=B). A ring-back signal may need to be provided
to the calling end, which is controlled by the Ring-Back Tone option.
FXSDN/WINK – Enables the mode FXSDN with WINK which is similar to FXSDN, but in
addition provides an indication to the central office (CO) when the station equipment is
ready to receive signaling information. This consists of detecting an off-hook signal from
the CO, which initiates a configurable “wink delay” followed by a configurable off-hook
signal back to the CO.
PLAR – Private Line Automatic Ring-down (PLAR) allows “hotline” point-to-point
dedicated connection of two phones. When one phone goes off-hook, the other phone
starts ringing.
DPO – The Dial Pulse Originating (DPO) mode is similar to FXS, except for supporting
out-going, one-way trunks from a PBX (direct outward dialing) or key system, or station
instrument. No ringing is provided in this mode.
12-48
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Signaling Type
Possible Settings: Loop-Start, Loop-Start/Fwd Disc, Ground-Start,
Ground-Start-Immediate, Ground-Start-Automatic, d3, d4
Default Setting: Loop-Start
Determines the type of signaling for the FXS voice port.
H Port Status is set to Enable.
H Operating Mode is not set to DPO.
NOTE:
If you change the value of the Operating Mode option so that the Signaling
Type option contains an invalid value, then the invalid value will be forced
to the first valid setting for this option.
Loop-Start – Enables the signaling used for basic telephone service stations, simple
PBX trunks, or key systems. Loop Start only appears if Operating Mode is set to FXS,
FXSDN, or FXSDN/WINK.
Loop-Start/Fwd Disc – Enables the signaling used for automated answering
equipment. This selection only appears if Operating Mode is set to FXS, FXSDN, or
FXSDN/WINK.
Ground-Start – Enables the signaling used for two-way PBX trunks. Helps to prevent
“glaring”, i.e., call collision. This selection only appears if Operating Mode is set to FXS,
FXSDN, or FXSDN/WINK.
Ground-Start-Immediate – Enables the signaling used for fast response time to the
PBX or station. This selection only appears if Operating Mode is set to FXS.
Ground-Start-Automatic – Enables the signaling used for fast response time to the
central office. This selection only appears if Operating Mode is set to FXS.
d3 – The APM meets the pre-1988 specifications for PLAR circuits. This selection only
appears if Operating Mode is set to PLAR.
d4 – The APM meets the post-1988 specifications for PLAR circuits. This selection only
appears if Operating Mode is set to PLAR.
Terminating Impedance (ohms)
Determines the terminating impedance (in ohms) for the port.
600 – The terminating impedance is 600 ohms.
9191-A2-GH30-00
DRAFT — June 1999
12-49
Application Modules
Wink Delay (10 ms)
Default Setting: 15
Determines the amount of delay before the wink signal is generated towards the
network, and when an off-hook signal from the CO is detected in increments of
10 milliseconds.
H Operating Mode is set to FXODN/WINK.
10 to 990 – The valid range is from 10 to 990 ms, in 10 ms increments. The settings are
numbers between 1 and 99, representing such increments. The default is 20, for a wink
delay of 150 ms.
Wink Duration (10 ms)
Default Setting: 20
Determines the duration of the wink signal generated towards the network when an
off-hook signal for the CO is detected and after the wink delay has elapsed in
increments of 10 milliseconds.
H Operating Mode is set to FXODN/WINK.
10 to 990 ms – The valid range is from 10 to 990 ms, in 10 ms increments. The settings
are numbers between 1 and 99, representing such increments. The default is 20, for a
wink duration of 200 ms.
Rx Gain (dB)
Possible Settings: –10.00, – 9.5, – 9.0, – 8.5, ..., 0.0, +0.5, +1.0, +1.5, +2.0
Determines the receive path analog signal amplification, or gain, on the FXS voice port
in decibels. This is the gain (increased signal level) or attenuation (decreased signal
level) applied to the signal.
–10.00 to +2.0 – Increases or decreases the signal level. The more positive the
number, the greater the signal level.
12-50
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Tx Attenuation (dB)
Possible Settings: –10.00, – 9.5, – 9.0, – 8.5, ..., 0.0, ..., +4.0, +4.5, +5.0
Determines the amount of attenuation, in dB, that the FXS voice port applies to the
analog signal presented by the user’s analog equipment. Positive TX Attenuation
settings reduce the level of the encoded analog signals sent towards the telephone
network and negative settings introduce gain. When connecting permissive mode
modems and fax machines, a setting of +3 dB should result in a compliant, encoded
analog of less than –12 dBm. The proper setting of this strap is crucial to ensuring
compliance with Part 68, FCC Rules and Industry Canada’s CS-03 Specification.
–10.00 to +5.0 – Increases or decreases the signal level. The more negative the
number, the greater the signal level (opposite of Rx Gain settings).
Ring-Back Tone
Allows generation of an audible tone toward the network in response to an incoming call
request, normally referred to as a ring-back. This feature is invoked only when the
central office (CO) does not provide it, as with a Class 4 ESS switch. This tone indicates
to the calling party that the called line has been reached and ringing has started. Use
the ring-back tone when you have a PLAR application.
Enable – Generates a ring-back tone toward the network in response to an incoming
call request.
Disable – Does not generate a ring-back tone toward the network in response to an
incoming call request.
Trunk Cond in CGA
Possible Settings: Busy, Idle
Default Setting: Busy
Determines the trunk condition or state that the port is forced into as a result of the
Carrier Group Alarm (CGA).
Busy – Forces the port to Busy during the Carrier Group Alarm.
Idle – Forces the port to Idle during the Carrier Group Alarm.
9191-A2-GH30-00
DRAFT — June 1999
12-51
Application Modules
Configuring FXO Voice APM Ports
Table 12-13. FXO Voice APM Options (1 of 3)
Port Status
Specifies whether the FXO voice port is in use, and can be configured and assigned to
a time slot on the T1 or DSX interface in order to transmit and receive voice frequency
signals.
No.)
Operating Mode
Possible Settings: FXO, FXODN, FXODN/WINK, DPT
Default Setting: FXO
Selects the operating mode for the FXO voice port.
FXO – Enables the Foreign Exchange Office (FXO) mode, supporting a bidirectional
connection to a PBX phone line. This mode uses 4-state signaling (A&B).
FXODN – Enables Foreign Exchange Office Software-Defined Network (FXODN) mode
for operation on software-defined networks. This mode is used by Class 4 switches and
uses 2-state signaling (A=B).
FXODN/WINK – Enables the mode FXODN with WINK which is similar to FXODN, but
in addition provides an indication toward the network interface when the attached
analog equipment is ready to receive signaling information. This consists of detecting an
off-hook signal from the network interface, which initiates a configurable “wink delay”
followed by a configurable off-hook signal back to the network interface.
DPT – The Dial Pulse Terminating (DPT) mode is similar to FXO, except for supporting
in-coming, one-way trunks to a PBX (direct inward dialing) or key system.
12-52
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Signaling Type
Possible Settings: Loop-Start, Loop-Start/Fwd Disc, Ground-Start
Default Setting: Loop-Start
Determines the type of signaling for the FXO voice port.
H Operating Mode is not set to DPT.
Loop-Start – Enables the signaling used for basic telephone service stations, simple
PBX trunks, or key systems.
Loop-Start/Fwd Disc – Enables the signaling used for automated answering
equipment.
Ground-Start – Enables the signaling used for two-way PBX trunks. Helps to prevent
“glaring”, i.e., call collision.
Determines the terminating impedance (in ohms) for the port.
Wink Delay (10 ms)
Default Setting: 15
Determines the amount of delay before the wink signal is generated towards the
network, and when an off-hook signal from the CO is detected in increments of
10 milliseconds.
H Operating Mode is set to FXODN/WINK or DPT.
10 to 990 – The valid range is from 10 to 990 ms, in 10 ms increments. The settings are
numbers between 1 and 99, representing such increments. The default is 15, for a wink
delay of 150 ms.
Wink Duration (10 ms)
Default Setting: 20
Determines the duration of the wink signal generated towards the network when an
off-hook signal for the CO is detected and after the wink delay has elapsed in
increments of 10 milliseconds.
H Operating Mode is set to FXODN/WINK or DPT.
10 to 990 ms – The valid range is from 10 to 990 ms, in 10 ms increments. The settings
are numbers between 1 and 99, representing such increments. The default is 20, for a
wink duration of 200 ms.
9191-A2-GH30-00
DRAFT — June 1999
12-53
Application Modules
Rx Gain (dB)
Possible Settings: –10.00, – 9.5, – 9.0, – 8.5, ..., 0.0, +0.5, +1.0, +1.5, +2.0
Determines the receive path analog signal amplification, or gain, on the FXO voice port
in decibels. This is the gain (increased signal level) or attenuation (decreased signal
level) applied to the signal.
Tx Attenuation (dB)
Possible Settings: –10.00, –9.5, –9.0, –8.5, ..., 0.0, ..., +4.0, +4.5, +5.0
Determines the amount of attenuation, in dB, that the FXO voice port applies to the
analog signal presented by the user’s analog equipment. Positive TX Attenuation
settings reduce the level of the encoded analog signals sent towards the telephone
network and negative settings introduce gain. When connecting permissive mode
modems and fax machines, a setting of +3 dB should result in a compliant, encoded
analog of less than –12 dBm. The proper setting of this strap is crucial to ensuring
compliance with Part 68, FCC Rules and Industry Canada’s CS-03 Specification.
–10.00 to +5.0 – Increases or decreases the signal level. The more negative the
number, the greater the signal level (opposite of Rx Gain settings).
Trunk Cond in CGA
Busy – Forces the port to Busy during the Carrier Group Alarm.
Idle – Forces the port to Idle during the Carrier Group Alarm.
12-54
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Configuring E&M Voice APM Ports
Table 12-14. E&M Voice APM Options (1 of 2)
Port Status
Specifies whether the E&M voice port is in use, and can be configured and assigned to
a time slot on the T1 or DSX-1 interface in order to transmit and receive voice frequency
signals.
No.)
Operating Mode
Possible Settings: E&M, Transmit Only
Default Setting: E&M
Selects the operating mode for the E&M voice port.
E&M – Enables normal earth and magnetic (E&M) mode.
Transmit Only – Enables the mode used to support 4-wire private-line modems that do
not require E&M signaling.
Rx Gain (dB)
Possible Settings: –17.0, –16.5, –16.0, –15.5, –15.0 ..., 0.0, ..., +15.0, +15.5, +16.0
Determines the receive path analog signal amplification on the E&M voice port in
decibels. This is the gain (increased signal level) or attenuation (decreased signal level)
applied to the signal before it is presented to the user’s analog equipment.
9191-A2-GH30-00
DRAFT — June 1999
12-55
Application Modules
Table 12-14. E&M Voice APM Options (2 of 2)
Tx Attenuation (dB)
Possible Settings: –17.0, –16.5, –16.0, –15.5, –15.0 ..., 0.0, ..., +15.0, +15.5, +16.0
Determines the amount of attenuation, in dB, that the E&M voice receive port applies to
the analog signal presented by the user’s analog equipment transmit port. Positive TX
Attenuation settings reduce the level of the encoded analog signals sent towards the
telephone network, and negative settings will introduce gain. The proper setting of this
strap is crucial to ensuring compliance with Part 68, FCC Rules and Industry Canada’s
CS-03 Specification.
Trunk Cond in CGA
Busy – Forces the port to Busy during a CGA.
Idle – Forces the port to Idle during a CGA.
12-56
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Configuring OCU-DP APM Ports
Use the OCU-DP Physical Options (Table 12-15) to configure the ports (either
two or six) on the OCU-DP APM in the selected slot.
Configuration → OCU-DP Ports
The OCU-DP Options screen appears for Port 1 of the first slot containing an
OCU-DP APM.
Table 12-15. OCU-DP APM Port Options (1 of 1)
Port Status
Specifies whether the OCU-DP port is in use, and can be configured and used to
transmit and receive data.
Enable – The port is active, and can be configured used to
Disable – The port is not active, cannot be configured, and cannot transmit/receive
data.
No.)
Port Rate
Possible Settings: 56K, 64KCC, Switched_56
Default Setting: 56K
Selects the rate for the port.
56K – The setting for 56 kbps.
64KCC – The setting for 64 kbps Clear Channel.
Switched_56 – The rate for 4-wire Switched 56.
Loopback Detection
Determines whether the the NextEDGE system will detect loopback activation codes
coming from the network.
Enable – Loopback code detection is enabled.
Disable – Loopback code detection is disabled.
9191-A2-GH30-00
DRAFT — June 1999
12-57
Application Modules
Assigning Cross Connections
The system allows you to assign data paths between the various interfaces to
share the T1 network. Assuming that both the Network and DSX-1 interfaces are
enabled and that at least one voice port APM is installed, you can make the
following cross connection assignments:
H
Assign DSX-1 time slots to the Network interface
H
Assign Network 2 interface time slots to the Network 1 interface
H
Assign voice ports to DSX-1 or Network interface time slots
H
Assign Synchronous Data ports to DSX-1 or Network interface time slots, or
to another Synchronous Data port
H
Assign OCU-DP data ports to DSX-1 or Network interface time slots
You can also clear cross-connection assignments.
NOTE:
Although it is not required, it is suggested that you progress through each
screen in order, from top to bottom.
12-58
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
The following figures illustrate various cross-connection assignments.
T1
Access Mux
Sync Data
Port
Network T1 Interface
DSX-1
98-15983
Assigning Synchronous Data Ports to Network Interface Time Slots
T1
Access Mux
Sync Data
Port
DSX-1
98-15984
Assigning Synchronous Data Ports to DSX-1 or Network Interface Time Slots
T1
Access Mux
Sync Data
Port
Sync Data
Port
DSX-1
24 DS0s with 9161 Single T1 NAM
16 DS0s with 9261 Dual TI NAM
98-15985
Assigning Synchronous Data Ports to DSX-1 Time Slots or to Another Synchronous
Data Port
Page 12-60 shows an example of data channel allocation.
9191-A2-GH30-00
DRAFT — June 1999
12-59
Application Modules
Channel Allocation Example
12-60
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Assigning Voice Ports to DSX-1 or Network Interface Time Slots
Use the Voice Port Assignments screen to view the status of all DS0 assignments
on the Network or DSX-1 interface. You can also use this screen to assign voice
ports to selected time slots.
NOTE:
You can assign voice ports to the DSX-1 interface on the T1 TDM NAM.
Voice port assignments on the Dual DSX APM are not supported.
" Procedure
Configuration →Time Slot Assignment/ Cross Connect →
Voice Port Assignment
2. The Cross Connect menu appears. Select Voice Port Assignment and press
Return. The Voice Port Assignments screen appears.
3. Enter Net1, Net2, or DSX01-1 into the Assign To field to assign voice ports to
the Network 1, Network 2, or DSX-1 interface, respectively.
or type in the desired slot and port. Repeat this step until all desired time
slots are assigned.
5. Save your assignments and return to the Time Slot Assignment/Cross
Connect menu.
Assigning Synchronous Data Ports
Synchronous Data ports are considered to be any data port with Port Use set to
Synchronous Data (see Table 8-6, Data Ports Physical Options). Use the Sync
Data Port Assignments screen to view the status of:
H
All DS0 assignments on the Network interface.
H
All DS0 assignments on the DSX-1 interface.
You can also use this screen to assign synchronous data ports to:
H
Network interface time slots.
H
DSX-1 interface time slots.
NOTES:
Synchronous Data Port-to-Synchronous Data Port assignments are not
supported.
You can assign synchronous data ports to the DSX-1 interface on the Single
T1 NAM. Sync Data port assignments on the Dual DSX APM are not
supported.
9191-A2-GH30-00
DRAFT — June 1999
12-61
Application Modules
Assigning OCU-DP Data Ports
Use the OCU-DP Port Assignments screen to view the status of:
H
All DS0 assignments on the Network interface.
H
All DS0 assignments on the DSX-1 interface.
You can also use this screen to assign OCU-DP data ports to:
H
Network interface time slots.
H
DSX-1 interface time slots.
NOTES:
You can assign OCU-DP ports to the DSX-1 interface on the Single T1
TDM NAM. OCU-DP port assignments on the Dual DSX APM are not
supported.
" Procedure
Configuration → Time Slot Assignment/Cross Connect →
OCU-DP Port Assignment
2. The OCU-DP Port Assignments screen appears. Enter one of the following
into the Assign To field:
If you want to assign to . . .
Then enter . . .
Network interface time slots
Net1 or Net2
DSX-1 interface time slots on the Single
T1 TDM NAM
DSX01-1
or type in the desired slot and port. Repeat this step until all desired time
slots are assigned.
4. Save your assignments and return to the Time Slot Assignment/Cross
Connect menu.
DSX-1 time slots are assigned by channel allocation, where you specify individual
time slots. The DSX-1 interface must be enabled to assign DSX-1 time slots to
the Network interface.
When assigning time slots to a Dual T1 TDM NAM, you must select which
network interface to use. Enter 1 or 2 in the NETWORK field.
See Assigning Time Slots/Cross Connections and DSX-1 Signaling Assignments
and Trunk Conditioning in Chapter 8, Configuration, for additional information.
12-62
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Clearing Port Assignments
Clearing port assignments sets the selected time slots to unassigned.
Configuration → Cross Connect → Clear Assignments
You can clear all port assignments for:
9191-A2-GH30-00
H
This device.
H
A specified slot.
H
A specified interface.
To clear . . .
Select . . .
All assignments for the DSX-1 time slots,
Network time slots, voice ports, and
Synchronous Data ports
Clear All
All assignments for the Network 1 Interface
time slots
Clear Network 1 Interface Time Slots
All assignments for the DSX01-1 time slots
on a Single T1 TDM NAM
Clear DSX01-1 Time Slots
Assignments for the synchronous data
ports on the NAM in slot s
Clear Slot s – NAM Synchronous Data
Ports
All assignments for the DSX-1
interface 1 time slots in slot s
Clear DSXs-1 Interface Time Slots
All assignments for the DSX-1
interface 2 time slots in slot s
Clear DSXs-2 Interface Time Slots
Assignments for time slots or ports on the
APM in slot s
Clear Slot s – xxxxx, where xxxxx = name
or type of APM
DRAFT — June 1999
12-63
Application Modules
APM Tests
The Test menu allows you to run loopbacks and test patterns on the NextEDGE
system, and to test the front panel LEDs. It is available to users with a security
access level of 1 or 2. Use the test menu to access the following tests.
12-64
To access the . . .
Select . . .
Network (1 or 2) Interface tests:
Line Loopback
Payload Loopback
Repeater Loopback
Remote Line Loopback
Pattern Tests
QRSS
All-zeroes
All-ones
1-in-8
3-in-24
63
511
2047
215-1
220-1
user-defined
Network Tests
DSX-1 Interface tests:
Line Loopback
Payload Loopback
Repeater Loopback
Pattern tests
QRSS
All-zeroes
All-ones
1-in-8
3-in-24
63
511
2047
215-1
220-1
user-defined
DSX-1 Tests
Synchronous Data Port tests
DTE Loopback
DTE Payload Loopback
Data Channel Loopback
Remote Loopbacks
V.54
FT1
Pattern tests
QRSS
All-zeroes
All-ones
63
511
2047
215-1
220-1
user-defined
Sync Data Port Tests
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
To access the . . .
Select . . .
Voice Port tests
Digital Loopback
Analog Loopback
Line Loopback
Test tones
DRS
Quiet
Force Signaling
Monitor Signaling
Voice Port Tests
OCU-DP tests
Local Loopback
Latching Loopback
Nonlatching Loopback
OCU Loopback
DS-0 Payload Loopback
Line Loopback
Data Loopback
Remote Loopback
Latching LB
Nonlatching LB
Pattern tests
All-zeroes
All-ones
63
511
2047
OCU-DP Tests
Lamp test
Device Tests
Voice Port Tests
Voice port tests are available to run on voice ports for any installed and enabled
APM.
" Procedure
To start and stop a voice port loopback:
Main Menu → Test → Voice Port Tests
2. Enter the desired slot and port number.
3. Highlight Start under Command in the row to send a test. Then, press Return
to start the test.
4. View the length of time that the test has been running in the Results column.
5. Highlight Stop under Command to stop the test.
9191-A2-GH30-00
DRAFT — June 1999
12-65
Application Modules
Digital Loopbacks
A Digital Loopback loops the digital voice signal received from the T1 interface
back to the same interface, just before reaching the D-to-A converter on the voice
port.
CODEC
Digital Loopback
D to A
Converter
to: T1 Interface
496-15200
The following tests cannot be running when a digital loopback test is initiated:
Analog Loopback, DRS or Quiet Test Tone on the same port.
Analog Loopbacks
An Analog Loopback loops the analog voice signal received from the T1 interface
back to the same interface, after passing through the Digital-to-Analog converter
and Analog-to-Digital converter on the voice port.
CODEC
D to A
Converter
Analog Loopback
to: T1 Interface
496-15201
The following tests cannot be running when an Analog Loopback test is initiated:
DRS or Quiet Test Tone, or Digital or Line Loopback on the same port.
12-66
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
Line Loopbacks
This test is only available for a voice port belonging to an E&M APM. A Line
Loopback loops the analog voice signal received from the analog line/device
connected to the port back to the same line/device, before passing through the A
to D converter on the voice port.
CODEC
D to A
Converter
Line Loopback
to: Analog Device
496-15202
The following tests cannot be running when a Line Loopback is initiated: DRS or
Quiet Test Tone, or Analog Loopback on the same port.
Send Test Tones
The following test tones are available to send to interface or to the user:
H
DRS – Digital Reference Signal, a 1004 Hz, 0.0 dBm tone.
H
Quiet – No signal is sent.
" Procedure
To start and stop a Test Tone:
3. Highlight either Send ___ to T1 Interface or Send ___ to User and select
either Quiet or DRS for each field.
to start the test.
The following tests cannot be running when a Test Tone is initiated:
9191-A2-GH30-00
H
Any loopbacks on the same port
H
Another type of test tone (other than the one currently running) on the same
interface
DRAFT — June 1999
12-67
Application Modules
Force and Monitor Signaling
Force and Monitor signaling enables you to send and receive the following
to/from the T1 interface to which the selected port is assigned:
You can force these fields . . .
To these settings . . .
ABCD bits (Tx and Rx) for ESF framing or
AB bits (Tx and Rx) for D4 framing
User-specified values
Set Tip and Ring Leads To
(FXO)
Loop – Tip and Ring are connected
together
Rgnd – Ring lead is attached to ground
Open – Ring lead is not connected to
either the Tip lead or the ground
Lpgnd – Tip and Ring are connected
together, and Tip is connected to ground
Set Tip and Ring Leads To
(FXS)
RbTo – A – 48 Vdc battery is applied to the
Ring lead and the Tip lead is open
RbTg – A – 48 Vdc battery is applied to the
Ring lead and the Tip lead is grounded
TbRg – A – 48 Vdc battery is applied to the
Tip lead and the Ring lead is grounded
Ring – Ringing voltage applied between
Tip and Ring
Set E-lead to (E&M APM only)
On
Off
ABCD bits (Tx and Rx) for ESF framing or
AB bits (Tx and Rx) for D4 framing
Whatever value is currently set
Tip and Ring Leads State
(FXO)
ToRo – Attached device has both Tip and
Ring leads open
TgRo – Attached device has Tip lead
grounded and Ring lead open
TgR* – Attached device has Tip lead
grounded and Ring lead state is unknown
ToR* – Attached device has Tip lead open
and Ring lead state is unknown
RoT* – Attached device has Ring lead
open and Tip lead state is unknown
RbTo – A battery is applied to the Ring
lead and the Tip lead is open
RbTg – A battery is applied to the Ring
lead and the Tip lead is grounded
TbRg – A battery is applied to the Tip lead
and the Ring lead is grounded
Tip and Ring
12-68
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
You can force these fields . . .
To these settings . . .
Tip and Ring Leads State
(FXS)
RbTo – Ring Lead connected to nominal
– 48Vdc battery and Tip lead open
RbTg – Ring Lead connected to nominal
– 48Vdc battery and Tip lead grounded
TbRg – Tip Lead connected to nominal
– 48Vdc battery and Ring lead grounded
Tip and Ring
Tip and Ring Leads Control State
(FXO only)
Loop – Tip and Ring are connected
together
Rgnd – Ring lead is attached to ground
Open – Ring lead is not connected to
either the Tip lead or the ground
Lpgnd – Tip and Ring are connected
together, and Tip is connected to ground
E-lead state (E&M APM only)
On
Off
M-lead state (E&M APM only)
On
Off
" Procedure
To force signaling:
3. Press PgDn to go to page 2.
4. Enter the desired setting for each field.
to start the test.
" Procedure
To monitor signaling:
3. Press PgDn to go to page 2.
4. Look at the values displayed under the Monitor Signaling portion of the
screen.
9191-A2-GH30-00
DRAFT — June 1999
12-69
Application Modules
OCU-DP Tests
The OCU-DP tests run on the OCU-DP APM’s ports. The procedure to send a
Latching loopback differs from the procedure to start/stop other loopbacks. Both
procedures are described below.
Sending a Latching Loopback
" Procedure
To send a Latching Loopback:
Main Menu → Test → OCU-DP Tests
2. Enter the loopback type:
— For Local: CSU or DSU
— For Remote: CSU, DSU, or OCU
3. Select the code Up or Down.
4. Highlight Send in the Command row. Then, press Return to start the test. The
code will be sent for up to 10 seconds, or until an acknowledgement is
received.
6. Send the Down code to stop the loopback.
Starting/Stopping Other Loopbacks
" Procedure
To start and stop loopback tests:
1. Follow this menu selection sequence to display the Tests screen:
Main Menu → Test → OCU-DP Tests
2. For Nonlatching loopbacks, select the desired loopback type (CSU or DSU).
3. Highlight Start under Command in the selected test’s row. Then, press Return
to start the test. This field now displays the word Stop.
4. View the length of time that the test has been running in the Result column.
5. Highlight Stop under Command in the selected test’s row. Then, press Return
to stop the test. This field now displays the word Start.
12-70
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
OCU-DP Loopback Tests
The following local loopback tests are available for the OCU-DP APM:
H
Latching Loopback – applicable only to the 64 Clear Channel DDS (64KCC)
rate
H
Nonlatching Loopback – applicable only to the DDS rate of 56K
H
OCU Loopback
H
DS-0 Loopback
H
Line Loopback
H
Data Loopback
The following remote loopback tests are available for the OCU-DP APM:
9191-A2-GH30-00
H
Latching Loopback – applicable only to the 64 Clear Channel DDS (64KCC)
rate.
H
Nonlatching Loopback – applicable only to the DDS rates of 56K and
Switched 56.
DRAFT — June 1999
12-71
Application Modules
DDS CSU/DSU Latching/Nonlatching Loopback
The Latching/Nonlatching Loopback sends the selected loopback sequence to
the CPE attached to the port.
Allows testing of a local loop between
the selected port and the CPE
This loopback running at . . .
Loopback
types
Latching
64K Clear Channel
CSU or DSU up or down
Nonlatching
56K
CSU or DSU
DSU Latching
and Nonlatching
Loopback
DDS
CSU
DSU
OCU
APM
Direction
–
T1
NAM
Network
Interface
OCU
Port
CSU Latching
and Nonlatching
Loopback
98-15958
The following tests are the only tests allowed to run at the same time as a
Latching/Nonlatching Loopback. No other tests can be running when a
Latching/Nonlatching Loopback test is started: Send Pattern/Monitor Pattern Test
on any data port assigned to this interface.
Latching Loopback
A latching loopback is a network-initiated DSU Loopback. Once a DSU Loopback
is started, the FrameSaver system remains in loopback until it receives the
loopback-release sequence from the network.
The latching loopback code is a control sequence (as opposed to a bipolar
violation sequence); therefore, user data may cause the FrameSaver system to
activate the loopback.
Disable the DSU Latching Loopback configuration option to stop the latching
loopback when the network did not command the test.
Main Menu → Configuration → Network → Physical
12-72
DRAFT — June 1999
9191-A2-GH30-00
Application Modules
OCU Loopback
The OCU Loopback loops the data received from the T1 interface for the selected
port back to the T1 interface.
OCU
APM
OCU
Port
T1
NAM
OCU
Loopback
Network
Interface
All
1s
98-15959
The following test is the only test allowed to run at the same time as an OCU
Loopback. No other tests can be running when an OCU Loopback test is started:
Line Loopback.
DS-0 Loopback
The DS-0 Loopback loops the data received from the T1 interface for the
selected port back to the T1 interface.
OCU
APM
OCU
Port
All
1s
T1
NAM
Network
Interface
DS-0
Loopback
98-15960
The following test is the only test allowed to run at the same time as an DS-0
Loopback. No other tests can be running when a DS-0 Loopback test is started:
Line Loopback
9191-A2-GH30-00
DRAFT — June 1999
12-73
Application Modules
Line Loopback
The Line Loopback tests the local loop between the OCU port and the attached
CPE. The loopback occurs on the APM near the local loop interface, toward the
local loop.
Line
Loopback
OCU
APM
T1
NAM
Network
Interface
OCU
Port
All 1s
98-15961
The following tests are the only tests allowed to run at the same time as a Line
Loopback. No other tests can be running when a Line Loopback test is initiated:
H
OCU Loopback.
H
DS-0 Loopback.
H
Line Loopback on the cross-connected T1 interface.
H
Payload Loopback on the cross-connected T1 interface.
Data Loopback
The Data Loopback tests the APM circuitry and the local loop connecting the port
to the CPE. The loopback occurs on the APM near the backplane connection,
toward the local loop.
Data
Loopback
OCU
Port
OCU
APM
T1
NAM
Network
Interface
All 1s
98-15962
The following tests are the only tests allowed to run at the same time as a Data
Loopback. No other tests can be running when a Data Loopback test is started:
12-74
H
Line Loopback on the cross-connected T1 interface.
H
Payload Loopback on the cross-connected T1 interface.
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
13
This chapter includes the following:
9191-A2-GH30-00
H
Problem Indicators on page 13-2.
H
Resetting the Unit on page 13-3.
H
Alarms on page 13-5.
H
Troubleshooting Tables on page 13-9.
H
Tests on page 13-13.
H
Test Timeout feature on page 13-14.
H
Starting and Stopping a Test on page 13-16.
H
Aborting All Tests on page 13-18.
H
Determining Test Status and Results on page 13-18.
H
PVC Tests on page 13-18.
H
Physical Tests on page 13-22.
H
IP Ping Test on page 13-33.
H
Lamp Test on page 13-35.
H
LMI Packet Utility on page 13-36.
DRAFT — June 1999
13-1
Troubleshooting
Problem Indicators
The system provides a number of indicators to alert you to possible problems:
Indicators . . .
See . . .
LEDs
Displaying LEDs and Control Leads and LED Descriptions
in Chapter 10, Operation and Maintenance, for faceplate
LEDs, their description, as well as the user interface
screen.
Main Menu → Status →
Display LEDs and Control LEDs
Health and Status
Alarms on page 13-5, and Health and Status Messages
in Chapter 10, Operation and Maintenance.
Messages also appear at the bottom of any menu-driven
user interface screen.
Performance statistics
Performance Statistics in Chapter 10, Operation and
Maintenance, to help you determine how long a problem
has existed.
Alarm conditions that will
generate an SNMP trap
Alarms on page 13-5.
SNMP traps
Appendix C, SNMP MIBs and Traps, and RMON Alarm
Defaults.
Alarm system relay for units Setting General System Optionss in Chapter 8,
installed in a 5-slot housing Configuration, to enable this feature.
Main Menu → Configuration → System → General
13-2
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
Resetting the Unit
You can reset the access unit in one of four ways:
H
Reset it from the Control menu.
H
Cycle the power.
H
Reset the configuration options for the COM port, or reload the factory default
settings.
H
Set the appropriate MIB object from NMS (see your NMS documentation).
The access unit performs a self-test when it is reset.
Resetting the Unit from the Control Menu
Use this procedure to initiate a power-on self-test of the access unit, recycling
power.
" Procedure
To reset the access unit from the Control menu:
1. From the Main Menu screen, select Control.
2. Select Reset Device and press Enter. The Are You Sure? prompt
appears.
3. Type y ( Yes) and press Enter. The unit reinitializes itself, performing a
self-test.
Resetting the Unit By Cycling the Power
Disconnecting, then reconnecting the power cord resets the access unit.
9191-A2-GH30-00
DRAFT — June 1999
13-3
Troubleshooting
Restoring Communication with a Misconfigured Unit
Misconfiguring the access unit could render the menu-driven user interface
inaccessible. If this occurs, connectivity to the unit can be restored via a directly
connected asynchronous terminal.
" Procedure
To reset COM port settings:
1. Configure the asynchronous terminal to operate at 19.2 kbps, using character
length of 8 bits, with one stop-bit, and no parity. In addition, set Flow Control
to None.
2. Reset the access unit, then hold the Enter key down until the System Paused
screen appears. (See Resetting the Unit on page 13-3 for other methods of
resetting the unit.)
3. Tab to the desired prompt, and type y ( Yes) at one of the prompts.
If selecting . . .
The following occurs . . .
Reset COM Port usage
H Port Use is set to Terminal so the
asynchronous terminal can be used.
H Data Rate (Kbps), Character Length, Stop Bits,
and Parity are reset to the factory defaults.
H Access unit resets itself.
Reload Factory Defaults
H All configuration and control settings are reset
to the Default Factory Configuration,
overwriting the current configuration.
H Access unit resets itself.
CAUTION: This causes the current configuration
to be destroyed and a Self-Test to be
performed.
If no selection is made within 30 seconds, or if No (n) is entered, the access
unit resets itself and no configuration changes are made.
Once the access unit resets itself, connectivity is restored and the Main Menu
screen appears.
13-4
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
Alarms
The following table describes the alarm conditions that will generate an SNMP
trap for a physical interface, and the frame relay LMIs and DLCIs. These alarm
conditions also generate Health and Status messages seen on the System and
Test Status screen.
Additional alarm information is provided in the following sections:
H
ISDN DBM – See DBM Alarms in Chapter 11,.Dial Backup Modules.
H
APM – See APM Alarms in Chapter 11, Application Modules.
Table 13-1. Alarm Conditions (1 of 5)
9191-A2-GH30-00
Alarm Condition
What It Indicates
What To Do
AIS at Network 1
(AIS) is being received by
the interface. AIS is an
For the network interface, report
the problem to your T1 service
provider.
AIS at DSX-1,
Slot-s Port-p
For the DSX-1 interface,
the attached DTE is
transmitting an AIS.
For the DSX-1 interface, check
the DTE attached to the
interface.
CTS down to
Slot-s Port-p Device
The CTS control lead on
the device’s interface is off.
Check DTR and RTS from
Port-1.
DLCI nnnn Down,
frame_relay_link
The DLCI for the specified
frame relay link is down.
If it is, contact your network
service provider.
DRAFT — June 1999
13-5
Troubleshooting
Alarm Condition
What It Indicates
What To Do
Device Fail yyyyyyyy
An internal error has been
detected by the operating
software.
1. Provide the 8-digit failure code
(yyyyyyyy) that follows the
alarm to your service
representative.
2. Clear the Device Fail
message.
Clear Device Fail
DTR Down from
Slot-s Port-p Device
The DTR control lead on
the device connected to the
specified port is off. This
message applies to data
ports that act as DCEs.
Examine the attached DTE and
cable connected to the system’s
port.
1. Check that the port cable is
ends.
attached equipment.
EER at Network 1
For the network interface:
received network signal has
exceeded the currently
securely attached at the
configured threshold. An
Network interface.
(EER) condition only occurs 2. Contact your network provider.
when the network interface
is configured for ESF
framing.
For the ISDN PRI DBM interface:
threshold value, which may 1. Verify that the cable is
interface.
2. Contact your ISDN network
provider.
13-6
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
Alarm Condition
What It Indicates
What To Do
LMI Down,
frame_relay_link
specified frame relay link.
For the Network interface:
1. If LMI was never up:
– Verify that the proper time
slots have been configured.
being used.
LMI frames being transmitted.
If all of the above have been
verified and the physical link is
not in Alarm, contact your
network provider.
For User Data Port:
1. Check that the DTE cable is
ends.
2. Verify that Transmit Clock
Source and Invert Transmit
Clock options are properly
configured.
LMI frames being received. If
no frames are being received:
– Check the attached device.
being used.
interface. For the network,
DSX, or ISDN PRI DBM
interface, an LOS condition
is declared when 175
consecutive zeros are
received.
For the network, DSX-1, or ISDN
PRI DBM interface:
LOS at DSX-1,
Slot-s Port-p
For the DSX-1 interface,
there may be a cable
problem or the DTE may
not be transmitting a signal.
Network Com Link
Down
The communication link for
the COM port is down and
the COM port is configured
for Net Link.
Check the router connected to
the COM port.
LOS at Network 1
9191-A2-GH30-00
DRAFT — June 1999
ends.
2. Verify that the attached device
is operational.
13-7
Troubleshooting
Alarm Condition
What It Indicates
What To Do
OOF at Network 1
condition has been
detected on the interface.
An OOF condition is
declared when two out of
four frame-synchronization
bits are in error.
For the network or DSX-1
interface:
OOF at DSX-1,
Slot-s Port-p
a reframe occurs.
Power Supply Alarm
ends.
for the interface is correct.
Output voltage for the 5-slot 1. Check that the power cord is
housing has dropped below
ends.
the system’s tolerance
level.
2. Check that the power outlet
has power by plugging in
equipment that that you know
is operational, then check the
circuit breaker.
3. Replace the power supply.
Primary Clock Failed
A failure of the configured
primary clock source for the
unit was detected and the
secondary clock is
unit.
ends.
clock is restored.
Primary & Secondary
Clocks Failed
A failure of both clock
sources configured for the
unit was detected
This condition only applies
to T1 network and DSX-1
interfaces. It clears when
clock is restored.
Secondary Clock
Failed
A failure of the configured
secondary clock source for
the unit was detected and
the internal clock is
unit.
The clock source will not
automatically switch from
internal until the primary
clock source returns.
Self-Test Failure
13-8
The unit did not pass its
basic verification tests
when it was powered up or
reset.
DRAFT — June 1999
1. Reset the unit.
representative.
9191-A2-GH30-00
Troubleshooting
Alarm Condition
What It Indicates
What To Do
SLV Timeout,
DLCI nnnn,
frame_relay_link
SLV communication
If it is, contact your network
responses from the remote service provider.
system have been missed
on the specified multiplexed
DLCI and link.
If the frame relay link is
Net1-FR1, the timeout is on
the network FrameRly1
timeshot assignment.
Yellow Alarm at
Network 1
being received on the
specified interface. The
DTE has detected an
LOS or OOF condition.
For the network interface:
securely attached at the
Network interface.
Yellow Alarm at
DSX-1, Slot-s Port-p
For the DSX-1 interface:
ends.
attached equipment.
Troubleshooting Tables
The system is designed to provide you with many years of trouble-free service. If
a problem occurs, however, refer to the appropriate table in the following sections
for possible solutions.
9191-A2-GH30-00
DRAFT — June 1999
13-9
Troubleshooting
Device Problems
Table 13-2. Device Problems (1 of 2)
Symptom
Possible Cause
Solutions
No power, or the LEDs
are not lit.
The power cord is not
securely plugged into the
wall receptacle to rear
panel connection.
Check that the power cord is
securely attached at both ends.
The wall receptacle has no
power.
H Check the wall receptacle
power by plugging in some
equipment that is known to be
working.
H Check the circuit breaker.
H Verify that your site is not on
an energy management
program.
13-10
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
Table 13-2. Device Problems (2 of 2)
Symptom
Possible Cause
Solutions
Power-Up Self-Test
fails. Only Alarm LED
is on after power-up.
The access unit has
detected an internal
hardware failure.
H Reset the unit and try again.
H Contact your service
representative.
H Return the unit to the factory
(refer to Warranty, Sales,
Service, and Training
Information on page A of this
document).
Cannot access the
unit or the
menu-driven user
interface.
Login or password is
incorrect, COM port is
misconfigured, or the unit is
otherwise configured so it
prevents access.
H Reset the unit (see
Restoring Communication
with a Misconfigured Unit on
page 13-4).
representative.
Device Fail appears
on the System and
Test Status screen
under Self-Test
results.
The unit detects an internal
hardware failure.
H Record the 8-digit code from
the System and Test Status
screen.
H Reset the unit and try again.
representative.
An LED appears
dysfunctional.
LED is burned out.
Run the Lamp Test. If the LED in
question does not flash with the
other LEDs, then contact your
Not receiving data.
Network cable loose or
broken.
H Reconnect or repair the cable.
T1 network is down.
Receiving data errors
FR Discovery is being used
on a multiplexed DLCI, for automatic DLCI and
but frame relay is
PVC configuration
okay.
H Call the network service
provider.
Change the DLCI Type for each
network DLCI from Multiplexed to
Standard, turning off
multiplexing.
The equipment at the other end
is not frame relay RFC 1490compliant or the unit at one end
of the PVC does not support the
Data Delivery Ratio feature.
9191-A2-GH30-00
DRAFT — June 1999
13-11
Troubleshooting
Frame Relay PVC Problems
Table 13-3. Frame Relay PVC Problems
Symptom
Possible Cause
Solutions
No receipt or
transmission of data.
Cross Connection of the
DLCIs are configured
incorrectly.
Verify the PVC connections,
DLCIs, and CIRs agree with
those of the service provider by
checking the network-discovered
DLCIs.
DLCI is inactive on the
frame relay network.
H Verify that the DLCI(s) is
active on the PVC Connection
Status screen. If the DLCI(s)
is not active, contact the
service provider.
H Verify the LMI Reported DLCI
field on the Interface Status
screen.
DTE is configured
incorrectly.
Check the DTE’s configuration.
LMI is not configured
properly for the DTE,
network, or ISDN link.
Configure LMI characteristics to
match those of the DTE or
network.
LMI link is inactive.
Verify that the LMI link is active
on the network; the Status Msg
Received counter on the Network
Frame Relay Performance
Statistics screen increments.
Losing Data.
Frame relay network is
experiencing problems.
Run PVC Loopback and Pattern
tests to isolate the problem, then
contact the service provider.
Out of Sync.
If Monitor Pattern was
selected, it means the test
pattern generator and
receiver have not yet
synchronized.
H Verify that the unit at the
If the message persists, it
means that 5 packets out of
25 are missing or are out of
sequence.
13-12
DRAFT — June 1999
other end is configured to
Send Pattern.
Correct unit configurations.
H Check the line’s error rate –
the physical line quality.
Contact the service provider.
9191-A2-GH30-00
Troubleshooting
Tests Available
The Test menu allows you to run loopbacks and test patterns on the access unit,
and to test the front panel LEDs. It is available to users with a security access
level of 1 or 2.
Select . . .
To run the following tests . . .
See . . .
H PVC Loopback
page 13-19
H Send Pattern
page 13-26
H Monitor Pattern
page 13-26
H Connectivity
page 13-22
H Line Loopback
page 13-22
H Payload Loopback
page 13-23
H Repeater Loopback
page 13-24
H Send Line Loopback
page 13-25
H Send Pattern Tests
page 13-26
H Monitor Pattern Tests
page 13-26
H DTE Loopback
page 13-28
H DTE Payload Loopback
page 13-29
H Data Channel Loopback
page 13-30
H Send V.54 Loopback
page 13-31
H Send FT1 Loopback
page 13-32
H Send Pattern
page 13-26
H Monitor Pattern
page 13-26
H Line Loopback
page 13-22
H Payload Loopback
page 13-23
H Repeater Loopback
page 13-24
H Send Pattern
page 13-26
H Monitor Pattern
page 13-26
IP Ping
IP PING
page 13-33
Lamp Test
LEDs test
page 13-35
PVC Tests 1
Network PVC Tests
Data Port PVC Tests
Physical Tests
Network Physical Tests
Data Port Physical Tests
DSX-1 Physical Tests
Other Tests
1
9191-A2-GH30-00
Menu selections for PVC Tests are suppressed when no PVCs have been defined for
the interface.
DRAFT — June 1999
13-13
Troubleshooting
For additional test information:
H
For an ISDN DBM, see ISDN Tests in Chapter 11, Dial Backup Modules.
H
For APMs, see APM Tests in Chapter 11, Application Modules.
Test Timeout
A Test Timeout feature is available to automatically terminate a test (as opposed
to manually terminating a test) after it has been running a specified period of
time.
It is recommended that this feature be used when the system is remotely
managed through an inband data stream (PVC). If a test is accidently
commanded to execute on the interface providing management access, control is
regained when the specified time period expires, automatically terminating the
test.
To use this feature, enable the Test Timeout configuration option, and set a
duration for the test to run in the Test Duration (min) configuration option (see
Configuring General System Options in Chapter 8, Configuration Options).
NOTE:
These configuration options do not pertain to tests commanded by the DTE,
like a DTE-initiated External Loopback.
13-14
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
Changing the Test Timeout from OpenLane Diagnostic Wizard
The system default for tests is the system’s Test Timeout setting, but it can be
overridden from Diagnostic Wizard. You can override the test duration for all tests
or for a single test.
Prior to running tests from Diagnostic Wizard, the test duration can be set from
the Customize drop-down menu.
" Procedure
To override the timeout duration for all tests, change the Test Timeout Value prior
to running any tests.
Navigation Wizard → Tests button → Customize drop-down menu →
Test Timeout Value
Values range from one minute to 15 hours; the default setting is 10-minutes.
" Procedure
To override the timeout duration for one test:
1. Select a DLCI from Navigation Wizard, and the Tests button.
2. Position the cursor over the Connectivity button in the test path, and click the
right mouse button. A pop-up menu appears.
3. Select Test Timeout Value, then set the test duration.
4. Run the test.
When the test is concluded, the Test Timeout Value reverts to the system
default.
9191-A2-GH30-00
DRAFT — June 1999
13-15
Troubleshooting
Starting and Stopping a Test
Use this procedure to start, monitor, or abort specific tests. To abort all active
tests on all interfaces, see Aborting All Tests on page 13-18.
When the status of a test is . . .
The only command available is . . .
Inactive
Start
Active
Stop
Start or stop an individual test using the same procedure.
" Procedure
To start and stop a loopback or a set-pattern test:
Main Menu → Test
2. Select an interface to be tested (Network, Data Port, or ISDN PVC Tests, or
Network, Data Port, DSX-1, or PRI Physical Tests) and press Return.
The selected test screen appears. Start appears in the Command column.
Inactive appears in the Status column.
3. Select the Port number and press Return.
4. Select the DLCI number and press Enter if a PVC test has been selected.
The cursor is positioned at Start in the Command column of the first available
test. Start is highlighted.
5. Highlight the Start command for the test you want to start and press Enter.
Stop now appears and is highlighted, and the status of the test changes to
Active.
6. Press Enter to stop the test.
Start reappears and the status of the test changes back to Inactive.
13-16
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
Starting and Stopping a Test from an OpenLane Application
Tests can be run from OpenLane DCE Manager aas well as from OpenLane
Diagnostic Wizard.
H
DCE Manager for Unix – To run tests you need to
— Make sure the Writer Community Name matches the Community Name
for the system to be tested.
—
—
—
H
DCE Manager for Windows
H
Performance Wizard’s Diagnostic Wizard
The following table identifies the tests that can be run
9191-A2-GH30-00
DRAFT — June 1999
13-17
Troubleshooting
Aborting All Tests
Use the Abort All Tests selection from the Test menu to abort all tests running on
all interfaces, with exception to DTE-initiated loopbacks. To abort individual tests
that are active, see Starting and Stopping a Test on page 13-16.
" Procedure
To abort all tests on all interfaces:
Main Menu → Test
2. Select Abort All Tests.
Command Complete appears when all tests on all interfaces have been
stopped.
NOTE:
Abort All Tests does not interrupt DTE-initiated loopbacks.
Determining Test Status and Results
Current test status and results are available on the:
H
Test screen from which you execute the test (Results column)
H
System and Test Status screen
H
NMS
H
Test LED
PVC Tests
PVC tests can be run on a requested DLCI for a selected interface.
H
When PVC tests are on a multiplexed DLCI between NextEDGE systems and
NextEDGE system and FrameSaver units, they are nondisruptive to data, so
user data can continue to be sent during a test.
H
If the device at one end of the circuit is not a NextEDGE or FrameSaver unit,
PVC tests are on a standard DLCI and are disruptive to data.
Loopback, and send/monitor pattern tests are available for each interface on the
selected DLCI. Access units should be at each end of the circuit. If a
PVC Loopback is started at one end of the circuit, the other end can send and
monitor pattern tests.
13-18
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
NOTE:
Errors encountered during these tests may be caused by mismatched CIRs
in the two access units. If errors are detected, verify the CIR configuration
and retest.
PVC Loopback
The Network/Port/ISDN PVC Loopback loops frames back to the selected
interface on a per-PVC basis. This test logically (not physically) loops back
frames from one access unit node through the frame relay PVC to the
same access unit node.
Main Menu → Test → [Network PVC Tests/Data Port PVC Tests/
ISDN PVC Tests] → PVC Loopback
If the selected DLCI is . . .
Then the PVC Loopback is . . .
Standard
Disruptive to data.
Proprietary, multiplexed
Nondisruptive to data.
Network PVC Loopback
DTE
PVC #x
Network
PVC #x
98-16186
Port PVC Loopback
DTE
PVC #x
Network
PVC #x
98-16187
9191-A2-GH30-00
DRAFT — June 1999
13-19
Troubleshooting
Send Pattern
This test sends frames filled with a hexadecimal 55 test pattern and sequence
number over the selected interface on a per-DLCI basis.
ISDN PVC Tests] → Send Pattern → Rate (Kbps)
If the selected
DLCI is configured as . . . Then . . .
And the default
Rate (Kbps) setting is . . .
Standard
(Disruptive) appears
after Test
100% of CIR
Multiplexed
(Non-Disruptive) appears
after Test
10% of CIR
If the CIR is zero, the pattern will be sent at a rate of 1000 bps.
Monitor Pattern
This test monitors packets for the 55 test pattern and checks sequence numbers
using a proprietary method.
ISDN PVC Tests → Monitor Pattern
The current number of sequence and data errors are shown under the Result
column when the access unit is in sync. An Out of Sync message appears
when 5 frames out of 25 are missing or out of sequence.
These error counts are updated every second. If the maximum count is reached,
99999+ appears in these fields.
13-20
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
Connectivity
The Connectivity test is is used to determine round-trip latency and is only
available for multiplexed DLCIs.
Connectivity is a proprietary method that determines whether the access unit
node at the other end of the frame relay PVC is active. This test stops
automatically and can only be executed for multiplexed PVCs.
ISDN PVC Tests] → Connectivity
Selecting Connectivity sends a frame to the access unit at the other end of the
PVC. A RndTrip Time(ms) message appears in the Result column when a
response is received within 5 seconds, indicating that the access unit at the
remote end is alive (operational and connected), and the round trip (RT) time is
shown in milliseconds (ms), with a resolution of 1 ms. If a response is not
received within 5 seconds, No Response appears in the Result column.
" Procedure
To perform a Connectivity test from DCE Manager:
1. Open a Device Display for the access unit.
2. Position the cursor over an active interface and click the right mouse button
to display the pop-up menu.
3. Select PVC Tests to open the PVC Tests dialog.
4. Select a DLCI to be tested from the list, then select Start Connectivity Test.
The results of the test appear in the Results screen area.
5. To stop the test, select Abort Connectivity Test.
" Procedure
To perform a Connectivity test from Performance Wizard:
1. From Navigation Wizard, click on the Tests button.
2. Position the cursor over the remote access unit to be tested and click the
right mouse button to display the pop-up menu.
3. In the test selection area, click on both Connectivity buttons in the test path
so the test will be performed by both the local and remote unit.
4. Click on the Start button to start the test.
5. To stop the test, Click on the Abort button.
9191-A2-GH30-00
DRAFT — June 1999
13-21
Troubleshooting
Physical Tests
Physical tests require the participation of your network service provider.
Line Loopback
The Line Loopback (LLB) loops the information received on the selected interface
back to the source of the loopback. When used with a pattern test at the remote
node, LLB determines whether the problem is with the sending device or the T1
facility.
Framer
Other
T1
Interface
LLB
All
1s
The T1
Interface
97-15336
To access a Line Loopback, follow this menu selection sequence:
Main Menu → Test → [Network Physical Tests/DSX-1 Physical Tests/
PRI Physical Tests] → Line Loopback
If Network Physical Tests was selected, a network interface must be selected.
CAUTION:
A Line Loopback may affect the operation of frame relay PVCs
assigned to the selected interface. While in loopback, the frame relay
link will be down, so any IP data being sent while this test is active will
be disrupted.
An LLB cannot be started when one of the following tests is active:
13-22
H
Payload Loopback, Send Remote Line Loopback, or an active Monitor
Pattern on this network interface.
H
Repeater Loopback on any other T1 interface with DS0s assigned to this
network interface.
H
Send Pattern Test on this network interface or any synchronous data port
(Port Use set to Synchronous) assigned to this interface.
H
Send V.54 or FT1 Loopback, or Data Channel Loopback on any synchronous
data port (Port Use set to Synchronous) and assigned to this network
interface.
H
Data Channel Loopback on the frame relay link on this network interface.
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
H
Send Remote Line Loopback on the Network or DSX-1 interface
H
Send V.54 or Send FT1 Loopback on any port assigned to this Network or
DSX-1 interface
H
Data Channel Loopback on any data port assigned to this Network or DSX-1
interface
Payload Loopback
The Payload Loopback (PLB) loops the information received on the selected
interface back to the network after it has passed through the receive and transmit
framing section of the device. Use the PLB to determine whether the problem is
with the T1 facility or in the circuitry of the remote device.
Other
T1
Interface
Framer
All
1s
PLB
The T1
Interface
97-15337
Main Menu → Test → [Network Physical Tests/DSX-1 Physical Tests/
PRI Physical Tests] → Payload Loopback
CAUTION:
A Payload Loopback may affect the operation of frame relay PVCs
assigned to the selected port. While in loopback, the frame relay link
will be down so any IP data being sent while this test is active will be
disrupted.
A PLB cannot be started when one of the following tests is active:
9191-A2-GH30-00
H
Line Loopback, Repeater Loopback, Send Remote Line Loopback, or an
active Monitor Pattern on this network interface.
H
Payload or Repeater Loopback on any other T1 interface with DS0s assigned
to this network interface.
H
H
interface.
H
H
Line Loopback or Repeater Loopback on the same Network or DSX-1
interface
DRAFT — June 1999
13-23
Troubleshooting
H
Send Pattern Test on the same Network or DSX-1 interface or any data port
assigned to this interface
H
Send Remote Line Loopback on the same Network interface
H
Send V.54 or Send FT1 Loopback on any data port assigned to this Network
or DSX-1 interface
H
Data Channel Loopback on any data port assigned to the same Network or
DSX-1 interface
Repeater Loopback
The Repeater Loopback (RLB) loops data received from the data ports and the
DSX-1 interface after the signal has passed through the framing circuitry. Use
RLB to ensure that all of the data is correct up to the point where it is sent over
the interface. This helps to indicate that the access unit is operational.
An attached device or test equipment should generate and monitor data to be
looped back.
Other
T1
Interface
Framer
RLB
AIS
The T1
Interface
97-15338
The T1 NAM will not respond to any messages from the network during this test.
To access Repeater Loopback, follow this menu selection sequence:
Main Menu → Test → [Network Physical Tests/DSX-1 Physical Tests] →
Repeater Loopback
CAUTION:
A Repeater Loopback may affect the operation of frame relay PVCs
disrupted.
A RLB cannot be started when one of the following tests is active:
13-24
H
Payload Loopback, Send Remote Line Loopback, or an active Monitor
Pattern on this network interface.
H
All loopbacks on any other T1 interface with DS0s assigned to this network
interface.
H
H
Send Pattern Test on the Network interface or any data port assigned to this
interface
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
H
H
Send V.54 or Send FT1 Loopback on any data port assigned to this Network
or DSX-1 interface
H
interface
Send Line Loopback
The remote Line Loopback (LLB) up and down codes are in-band codes that
allow control of a remote device. The LLB Up code invokes a line loopback in the
remote unit while the LLB Down code terminates the remote line loopback.
Network loopbacks are defined in AT&T TR 62411.
Main Menu → Test →Network Physical Tests → Send Line Loopback
A remote LLB cannot be started when one of the following tests is active:
9191-A2-GH30-00
H
Any Loopback on the same interface.
H
Line Loopback, Payload Loopback, Repeater Loopback, or an active Monitor
Pattern on this network interface
H
H
interface.
H
H
All loopbacks on this Network interface
H
Send Pattern Test on the Network interface or any data port assigned to this
interface
H
interface
H
Send V.54 or Send FT1 Loopback on any data port assigned to this interface
H
Data Channel Loopback on any data port assigned to this interface
DRAFT — June 1999
13-25
Troubleshooting
" Procedure
To start and stop a remote Send Line Loopback:
Main Menu → Test → [Network Physical Tests/PRI Physical Tests] →
Send Line Loopback
2. Select the desired Network interface (shown in the screen title).
3. Select the code Up or Down in the Send Line Loopback field.
— Up – Puts a remote device in loopback.
— Down – Takes the remote device out of loopback.
4. Highlight Send and press Return to start the test. The code is sent for
10 seconds.
Sending and Monitoring Pattern Tests
The pattern tests enable a access unit to either send or monitor a known bit
pattern. These tests generate industry-standard bit patterns that can be used to
determine whether information is being correctly transmitted across a circuit.
The following test patterns are available:
— QRSS
— 511
— All-zeros
— 2047
— All-ones
— 2E15-1 (215-1)
— 1-in-8
— 2E20-1 (220-1)
— 3-in-24
— User-defined 2-byte test pattern (a0a0)
— 63
A Send Pattern test cannot be started when the following tests are running:
13-26
H
Send Pattern Test on the same interface or any data port assigned to that
interface
H
Send V.54 or Send FT1 Loopback on any data port assigned to this interface
H
Data Channel Loopback on any data port assigned to the same interface
H
Any Loopback on the same interface
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
H
Line Loopback, Payload Loopback, Repeater Loopback, or Send Remote
Line Loopback on this network interface
H
Send Pattern Test on any port assigned to this network interface
H
interface.
H
Data Channel Loopback on the frame relay link on this network interface
" Procedure
To send and monitor a Pattern Test:
Main Menu → Test →[Network Physical Tests/DSX-1 Physical Tests/
Data Port Physical Tests] → Send user-defined Pattern
2. Select the desired pattern in the Send or Monitor field. If sending/monitoring
a user-defined pattern, enter the the desired 2-byte hexadecimal value in the
field next to Send or Monitor.
When sending a pattern, the I njectErr function key appears. Use I njectErr if
you want to inject a bit error in the transmitted bit pattern.
3. Highlight the Send command to send a pattern, or the Start command to
monitor a pattern, and press Return to start the test or start monitoring it.
An error count is also displayed. When monitoring a pattern, the ResetMon
virtual function key appears. ResetMon resets the error count to zero.
5. Highlight Stop and press Return to stop the test.
9191-A2-GH30-00
DRAFT — June 1999
13-27
Troubleshooting
DTE Loopback
The DTE external Loopback (DTLB) test loops the received signal on a DTE
interface back to the DTE without affecting the operation of the remaining ports.
Use this test for isolating problems on the DTE interface.
An attached device or test equipment must generate and monitor data to be
looped back.
To access DTE Loopback, follow this menu selection sequence:
Main Menu → Test → Data Port Physical Tests → DTE Loopback
DSX
Interface
Network
Interface
All 1s
DTLB
DTE
Port 2
DTLB
DTE
Port 1
98-16190
CAUTION:
A DTE Loopback may affect the operation of frame relay PVCs assigned
to the selected port. Any IP data being sent while this test is active will
be disrupted.
13-28
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
DTE Payload Loopback
The DTE Payload Loopback (DTPLB) loops the information received on the
Network or DSX-1 interface back to the network after it has passed through the
port circuitry. Use DTPLB for isolating problems on the DTE line. An attached
device or test equipment must generate and monitor data to be looped back.
All 1s
DSX
Port
DTLB
DTLB
DCE
Port 2
DCE
Port1
Network
Interface
496-15211
To access DTE Payload Loopback, follow this menu selection sequence:
Main Menu → Test → Data Port Physical Tests → DTE Payload Loopback
CAUTION:
The Abort All Tests selection from the Test screen, or the test timeout
feature, will not interrupt a DTE Loopback initiated by an attached
device since the Local Loopback lead will still be asserted.
The following tests cannot be running on the same port when a DTE Payload
Loopback is initiated:
9191-A2-GH30-00
H
DTE Loopback
H
H
Send Pattern Test
DRAFT — June 1999
13-29
Troubleshooting
The Data Channel Loopback (DCLB) loops the data for a particular synchronous
data port back to the interface after the information has passed all the way
through the device (i.e., just before it is sent to the Customer Premises
Equipment). Use DCLB to verify the end-to-end integrity of a circuit for a
particular port.
To access Data Channel Loopback, follow this menu selection sequence:
Main Menu → Test → Data Port Physical Tests → Data Channel Loopback
Network
Interface
DSX
Port
DCLB
DCLB
All 1s
All 1s
DCE
Port 2
DCE
Port 1
496-15212
The following tests cannot be running when a DCLB test is initiated:
13-30
H
A Line Loopback, Payload Repeater Loopback or Send Pattern Test on the
same interface
H
Send Pattern Test or DTE Payload Loopback on the same port
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
Send V. 54 Loopback
The remote V.54 Loopback commands a device to go into the data channel
loopback on the associated port.
" Procedure
To send a remote V.54 Loopback:
Main Menu → Test → Data Port Physical Tests → Send V.54 Loopback
3. Select the code Up or Down in the Send V.54 Loopback field.
4. Highlight Send under Command in the Send V.54 Loopback row. Then, press
Return to start the test. The code will be sent for up to 10 seconds, or until an
acknowledgement is received from the remote end.
6. Send the Down code to stop the remote loopback.
CAUTION:
A V.54 Loopback may affect the operation of frame relay PVCs assigned
to the selected port. While in loopback, the frame relay link will be down
so any IP data being sent while this test is active will be disrupted.
The following tests cannot be running when a V.54 test is initiated:
9191-A2-GH30-00
H
A Send Pattern Test, Send Remote Line Loopback, Payload Loopback, or
Repeater Loopback on the interface to which the port is assigned
H
DTE Payload Loopback, Send Pattern Test, or Send FT1 Loopback on the
same port
DRAFT — June 1999
13-31
Troubleshooting
Send FT1 Loopback
The remote FT1 Loopback commands a remote device to go into Data Channel
Loopback on the associated port.
" Procedure
To send a remote FT1 Loopback:
Main Menu → Test → Data Port Physical Tests → Send FT1 Loopback
3. Select the code Up or Down in the Send FT1 Loopback field.
4. Highlight Send under Command in the Send Ft1 Loopback row. Then, press
Return to start the test. The code will be sent for up to 10 seconds, or until an
acknowledgement is received from the remote end.
An FT1 Loopback may affect the operation of frame relay PVCs
disrupted.
The following tests cannot be running when a V.54 test is initiated:
13-32
H
A Send Pattern Test, Send Remote Line Loopback, Payload Loopback, or
Repeater Loopback on the interface to which the port is assigned
H
DTE Payload Loopback, Send Pattern Test, or Send V.54 Loopback on the
same port
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
IP Ping Test
An IP Ping test can be run to test connectivity between the system and any
NextEDGE or FrameSaver device, router, or NMS to which it has a route.
Times when you might want to run an IP Ping test are:
H
To test connectivity between the system and any NextEDGE or FrameSaver
unit in the network to verify that the path is operational. Select Procedure 1 to
Ping any far-end access unit.
H
To verify the entire path between a newly-installed remote-site NextEDGE or
FrameSaver unit and the central-site NMS. During a remote-site installation,
an IP Ping test is typically run from the remote-site to Ping the NMS at the
central site. The remote access unit must have SNMP trap managers
configured, and one of those trap managers must be the central-site NMS.
Select Procedure 2 on page 13-34 to Ping the NMS at the central site.
H
To test the path to the NMS trap managers during installation of the
central-site system. The remote access unit must have configured the SNMP
trap managers to be sent the Ping. Select Procedure 2 on page 13-34 to Ping
the SNMP trap managers.
" Procedure 1
To Ping any far-end NextEDGE or FrameSaver device:
1. Select the IP Ping test.
Main Menu → Test → IP Ping
2. From the PC, enter the IP Address of the device the Ping is being sent to,
then select Start.
NOTE:
If the access unit has just initialized, or the far-end unit has just initialized,
it may take about a minute for the units to learn the routes via the
proprietary RIP.
3. Verify the results of the IP Ping test.
— While the test is running, In Progress... is displayed in the Status
field.
— When the test is finished, Alive. Latency = nn ms should appear as
the Status (nn being the amount of time the test took in milliseconds).
If any other message is displayed, additional testing will be required.
9191-A2-GH30-00
DRAFT — June 1999
13-33
Troubleshooting
" Procedure 2
To Ping the NMS at the central site:
1. Verify that the central-site NMS has the access unit’s IP address in its routing
table so it can communicate with the unit.
2. Verify that the central-site NMS’s router has the access unit’s IP address in its
routing table so it can communicate with the unit.
3. Verify that the central-site NMS has been configured as an SNMP Trap
Manager if the router is to route data, so a route has been configured within
the access unit.
SNMP Traps
Or, for a local DLCI between the central-site system and its router, verify that
a Default IP Destination route has been configured.
Node IP → Default IP Destination
Configure both SNMP Traps and a Default IP Destination when PVC
Multiplexing is used, as when using the Auto-Configuration feature.
4. Select the IP Ping test.
Main Menu → Test → IP Ping
5. Enter the IP Address of the central-site NMS, then select Start.
6. Verify the results of the IP Ping test.
— While the test is running, In Progress . . . is displayed in the
Status field.
— When the test is finished, Alive. Latency = nn ms should appear as
the Status (nn being the amount of time the test took in milliseconds).
If any other message is displayed, additional testing will be required.
13-34
DRAFT — June 1999
9191-A2-GH30-00
Troubleshooting
Lamp Test
The system supports a Lamp Test to verify that all LEDs are lighting and
functioning properly. All LEDs flash or blink on and off at the same time every
1/2 second during execution of the test. When the test is stopped, the LEDs are
restored to their normal condition.
If the Test Timeout configuration option is enabled and a Test Duration is set, the
Lamp Test stops when the test duration expires.
See Configuring General System Options in Chapter 8, Configuration Options, to
configure the unit to stop the test automatically.
" Procedure
To perform a Lamp Test from DCE Manager, take the folllowing path:
DCE Manager → Device Display → Diagnosis menu → Lamp Test Start
The LEDs on the access unit start blinking. Once the device is located and the
LEDs verified, select Lamp Test Stop. The access unit LEDs return to normal
operation.
" Procedure
To perform a Lamp Test from Performance Wizard:
1. Click on the Tests button from Navigation Wizard.
2. Highlight the device to be tested.
3. Click on the Device Tests menu and select Start Lamp Test.
4. To stop the test, select Stop Lamp Test from the Device Tests menu.
9191-A2-GH30-00
DRAFT — June 1999
13-35
Troubleshooting
LMI Packet Utility
A packet capture utility is provided to aid with problem isolation when LMI errors
are detected. Using this utility, any enabled frame relay link that is having
problems can be selected. The utility captures any LMI packets sent or received
and writes them to a data file called lmitrace.syc in the system’s data directory
so the data can be uploaded and transferred to a Network Associates Sniffert
for analysis.
" Procedure
To use the utility:
1. Select an enabled frame relay link.
2. Start packet capture.
While capturing data, the status is Active. Packets in Buffer indicates the
number of packets that have been captured. Up to 8000 packets can be held.
If the utility is left to overrun the buffer, only the most current 8000 packets
are retained.
3. To stop the utility, press Return. The field toggles back to Start.
4. Upload the data file holding the collected packets to a diskette so the
information can be transferred to a Network General Sniffer for
debugging/decoding.
See FTP File Transfers in Chapter 10, Operation and Maintenance, to learn
how to transfer a data file.
13-36
DRAFT — June 1999
9191-A2-GH30-00
Menu Hierarchy
A
Menus
The following is a graphical representation of the NextEDGE System menu
organizations.
9191-A2-GH30-00
H
For the FrameSaver NAM’s menu, see the menu on page A-2.
H
For the T1 TDM NAM’s menu, see the menu on page A-4.
DRAFT — June 1999
A-1
Menu Hierarchy
Menu Hierarchy
MAIN MENU
Status
Status
System and Test Status
NNI LMI Reported DLCIs
Local LMI Reported DLCIs
Management Connection Status
Display LEDs
Identity
System and
Test Status
• Health and
Status
• Self-Test Results
• Test Status
NNI LMI
Reported
DLCIs
Management
Connection
Status
• DLCI
• Status
• CIR (bps)
• Source Link
• Destination Link
and DLCI Status
Identity
• System Name,
Contact and
Location
• Serial and
Model Numbers
• Current and
Alternate
Software
Revisions
• Hardware
Revision
Test
Configuration
Control
Performance
Statistics
• NNI DLCIs
• NNI SLV
• Local DLCIs
• Local SLV
• NNI Frame Relay
• Local Frame Relay
• NNI Line
• NNI Physical
• Local Physical
• Clear All Statistics
MAIN MENU
Status
PVC Tests
NNI DLCI
(DLCI Number, Test,
Command, Status,
and Results)
• Interior PVC Loopback
• Interior Send Pattern
• Interior Monitor Pattern
• Interior Connectivity
• Exterior Monitor Pattern
A-2
Test
Test
NNI PVC Tests
Local PVC Tests
NNI Port Physical Tests
Local Port Physical Tests
IP Ping
Device Tests
Abort All Tests
Configuration
Control
IP Ping
Device Test
Physical Tests
• IP Address
• Start
• Status
(Status)
• Lamp Test
(Test, Command, Status, and Result)
Network:
• Line Loopback
• Payload Loopback
• Send Pattern
• Monitor Pattern
DRAFT — June 1999
99-16441a
9191-A2-GH30-00
Menu Hierarchy
Configuration
Edit/Display
MAIN MENU
Status
Test
Load
Configuration
from:
Configuration
Control
NNI
Local
LMI
Time Slot Assignment
General
User Interface
Alarm
Management and
Communication
for Interface
General Options
User Interface Options
• Physical
• DLCI Records
• Test Timeout
• Test Duration
• Primary and Secondary
Clock Source
• SLV Link and Sampling
• SLV Sample Interval
• Communication Port
• External Device (COM Port)
• Telnet and FTP Sessions
Management and
Communication Options
• Communication Protocol
• Management PVCs
• General SNMP
• SNMP NMS Security
• SNMP Traps
New, Modify, or Delete
Management
PVC Entry
MAIN MENU
Status
Test
Configuration
Control
COM Port Call Setup
COM Port Call Directories
Device Name
Date & Time
Administer Logins
Change Operating Mode
Select Software Release
Clear Device Fail
Reset Device
Device Name
Administer Logins
Select Software Release
• Device Name
• System Name,
Location, Contact
• Login ID
• Password
• Access Level
• Current Release
• Select New Release
• Switch & Reset
Control
New or Delete
Login Entry
9191-A2-GH30-00
DRAFT — June 1999
99-16441b
A-3
Menu Hierarchy
Menu Hierarchy
MAIN MENU
System and
Test Status
Cross Connect
Status
• Health and
Status
• Self-Test
Results
• Test Status
• Network Channel
Display
• DSX-1
Channel Display
• Port Assignment
Display
Voice Status
• Port Status
• Assigned To
• Operating Mode
• Signaling Type
• Call Progress
• Tx/Rx ABCD Bits
• E-Lead State
• M-Lead State
• T-R Control/Receive
• Trunk Conditioning
CGA
Status
Status
System and Test Status
Cross Connect Status
Voice Status
Identity
Test
Configuration
Control
Performance
Statistics
• Service Level
Verification
• Network
• Sync Data Ports
• Clear Statistics
• Clear All
Statistics
Identity
• System
• NAM
• APM
MAIN MENU
Status
Test
Test
Network Tests
DSX-1 Tests
Sync Data Port Tests
Voice Port Tests
OCU-DP Tests
Device Tests
Abort Tests
Configuration
Control
99-16440a
A-4
DRAFT — June 1999
9191-A2-GH30-00
Menu Hierarchy
Configuration
Edit/Display
Load
Configuration
from:
Network
DSX-1
Sync Data Ports
Voice Ports
OCU-DP
Copy Ports
Cross Connect
System Options
User Interface
Alarm
Management and
Communication
Cross Connect
User Interface
• DSX-1 to Network
Assignments
• Network to Network
Assignments
• Voice Port
Assignments
• Sync Data Port
Assignments
• OCU-DP Port
Assignments
• Clear
Assignments
• Communication Port
• External Device
(Com Port)
• Telnet/FTP Sessions
MAIN MENU
Status
Test
Configuration
Control
Management and
Communication Options
• Node IP
• Communication Protocol
• General SNMP
Management
• SNMP NMS Security
• SNMP Traps
MAIN MENU
Status
Test
Configuration
Control
Control
COM Port Call Setup
COM Port Call Directories
Device Name
Date & Time
Administer Logins
System Alarm Relay Cut-Off
Clear Device Fall
Reset Device
Administer Logins
• Login ID
• Password
• Access Level
New
Login Entry
9191-A2-GH30-00
DRAFT — June 1999
99-16440b
A-5
Menu Hierarchy
A-6
DRAFT — June 1999
9191-A2-GH30-00
IP Addressing
B
This appendix includes the following information:
H
Selecting an IP Addressing Scheme on page B-2.
— If You Have a FrameSaver NAM on page B-2.
— If You Have a T1 TDM NAM on page B-3.
H
NextEDGE FrameSaver System IP Addressing on page B-3.
— Customer Management on page B-4.
— Service Provider Management on page B-5.
— Joint Customer and Service Provider Management on page B-7.
— Frame Relay IP Addressing Scheme Examples on page B-8.
— Direct PVCs to Remote Frame Relay Devices on page B-8.
— Routing to Remote Frame Relay Devices on the Same Subnet on
page B-9.
— Routing to Remote Frame Relay Devices Using Different Subnets on
page B-10.
— Routing to Remote Frame Relay Devices Using Routers on page B-11.
— Assigning Frame Relay IP Addresses and Subnet Masks on page B-13.
H
NextEDGE T1 TDM System IP Addressing on page B-14.
— Direct Management Links to Remote T1 TDM Systems on page B-14.
— Routing to Remote T1 TDM Systems on the Same Subnet on page B-15.
— Routing to Remote T1 TDM Systems Using Different Subnets on
page B-16.
— Routing to Remote T1 TDM Systems Using Routers on page B-17.
— Assigning T1 TDM System IP Addresses and Subnet Masks on
page B-18.
9191-A2-GH30-00
DRAFT — June 1999
B-1
IP Addressing
Selecting an IP Addressing Scheme
You can select from many IP addressing schemes to provide SNMP NMS, Telnet,
or FTP connectivity. When selecting a scheme, keep the following in mind:
H
Assign IP addresses on a per-interface or NextEDGE system basis.
H
Although routing information is automatically passed between interconnected
NextEDGE systems from the network side, make sure to set a route to the
subnet(s) in the NMS’s or local router’s routing table.
H
Be aware that each NextEDGE system’s routing table supports a maximum
of 300 routes.
H
Have a default route set only for devices directly connected to the NMS’s
COM port.
H
Allow any legal host address for a given subnet; the address choice within
the subnet is not important to the system, but should be selected in
conjunction with all IP addressing for the subnet.
NOTE:
When dealing with IP addressing, your Information Systems (IS) department
needs to be involved since they typically dictate the IP addressing scheme
used in an organization.
If You Have a FrameSaver NAM
When the NextEDGE system has a FrameSaver NAM, the following should also
be kept in mind:
H
Connection to remote devices using a FrameSaver NAM is through PVCs, so
if desired, you can assign IP addresses and subnet masks to each PVC
individually.
H
Although routing information is automatically passed between interconnected
systems from the network side, make sure to set a route to the subnet(s) in
the NMS’s or local router’s routing table.
The gateway to subnet(s) is through the system connected to one of the
following:
— A router’s, terminal server’s, or NMS’s direct PPP ( point-to-point
protocol) or SLIP’s ( link-layer protocol for IP traffic) serial connection.
— The router’s DTE port using a local PVC.
— The LAN (using a LAN adapter).
— A dedicated PVC through the frame relay network to the service
provider’s network operation center (NOC).
When your system is equipped with a NextEDGE FrameSaver NAM, see
NextEDGE FrameSaver System IP Addressing on page B-3 for IP addressing
examples.
B-2
DRAFT — June 1999
9191-A2-GH30-00
IP Addressing
If You Have a T1 TDM NAM
When the NextEDGE system has a T1 TDM NAM, the following should also be
kept in mind:
H
Connection to remote devices using a T1 TDM NAM is through different
interfaces (for EDL), so it may be necessary to assign IP addresses and
subnet masks to each EDL individually.
H
Avoid multiple EDL connections between the same two devices to prevent
routing loops.
H
For a point-to-point ESF T1 link, use the FDL to connect to the remote site.
H
For a fractional T1 network, use EDL(s) to connect to each remote site (when
at least one data port is configured at that site).
H
For a fractional T1 network, when a data port is not configured (in the case of
voice only), a single DDL can be used to connect to a remote site.
H
The gateway to subnet(s) is through the T1 TDM NAM connected to one of
the following:
— The LAN (using a LAN adapter).
— A router’s, terminal server’s, or NMS’s direct PPP ( point-to-point
protocol) or SLIP ( link-layer protocol for IP traffic) serial connection.
When your system is equipped with a NextEDGE T1 TDM NAM, see NextEDGE
T1 TDM System IP Addressing on page B-14 for IP addressing examples.
NextEDGE FrameSaver System IP Addressing
The following sections include an example of:
H
Customer Management on page B-4.
— Using Multiplexed PVCs on page B-6.
H
Service Provider Management on page B-5.
H
Joint Customer and Service Provider Management on page B-7.
H
Frame Relay IP Addressing Scheme Examples on page B-8.
— Direct PVCs to Remote Frame Relay Devices on page B-8.
— Routing to Remote Frame Relay Devices on the Same Subnet on
page B-9.
— Routing to Remote Frame Relay Devices Using Different Subnets on
page B-10.
— Routing to Remote Frame Relay Devices Using Routers on page B-11.
— Assigning Frame Relay IP Addresses and Subnet Masks on page B-13.
9191-A2-GH30-00
DRAFT — June 1999
B-3
IP Addressing
Customer Management
When customers are connected to the internet, IP addresses are limited to the
number of IP addresses they own. Using NextEDGE FrameSaver systems, or a
NextEDGE FrameSaver system at the central site and a mix of NextEDGE and
FrameSaver devices at remote sites, private addressing can be used for the
network without taking away from the customer’s pool of IP addresses.
The illustration below shows this scheme of public and private IP addressing,
which is like having two networks in one. DLCI 900 is a static route to the system.
Central
Site
DLCI 200
Customer
NMS
DLCI 200/EDLCI 2
DLCI 200
DLCI 210
10.10.10.2
DLCI 210/EDLCI 2
Frame DLCI 900
Relay
10.10.10.1
Router
135.18.2.1
Physical Connection
PVC Connection
Frame
Relay
Router
135.18.2.2
DLCI 210
Frame Relay
Network
10.10.10.3
Frame
Relay
Router
135.18.2.3
99-16390
Both public and private addressing scheme networks share the near-to-far end
customer-ordered DLCIs (200 and 210) so that user data is multiplexed with
management data using EDLCIs (multiplexed DLCIs, e.g., DLCI 200/EDLCI 2).
Management of the far-end devices is performed via the EDLCIs, creating a
communication path within a communication path.
Using the FrameSaver RIP feature, far end FrameSaver devices can be identified
automatically and reported to the management station via local DLCI 900, which
is configured between the central-site FrameSaver system and its router. This
DLCI is dedicated to management and is not propagated to the network by the
FrameSaver system. The DLCI terminates in the system and is only used for
management.
B-4
DRAFT — June 1999
9191-A2-GH30-00
IP Addressing
Service Provider Management
Total management can be performed by service providers using both private and
public IP addressing. A standard CSU/DSU can be used by the NOC NMS.
Central
Site
Customer
NMS
DLCI 200
Frame Relay
Network
DLCI 200/EDLCI 2
DLCI 200
DLCI 210
Frame
Relay
Router
DLCI 210/EDLCI 2
DLCI 909
DLCI 909
Integrated
Services
Center
9
0
I 91
Physical Connection
PVC Connection
I 90
DLC
135.18.2.1
DLCI 210
DLCI 910
DLC
Frame
Relay
Router
135.18.2.2
135.18.2.3
10.10.10.1 NMS
Frame
Relay
Router
99-16391
In this illustration, two dedicated PVCs are required.
H
DLCI 909 is used to manage the router if it is a managed router service.
H
DLCI 910 is used to manage the central site system.
Notice that DLCI 910 terminates in the central site NextEDGE FrameSaver
system. It is dedicated to managing the central site system. Each remote device
can be reached through the multiplexed DLCIs between the central site system
and the remote NextEDGE or FrameSaver devices.
9191-A2-GH30-00
DRAFT — June 1999
B-5
IP Addressing
Using Multiplexed PVCs
When deploying a managed router service, instead of having one PVC for the
router (DLCI 909) and another for the NextEDGE or FrameSaver device, the
network can be managed using only the router PVC when the NOC uses a
FrameSaver device, which has its own IP address, as seen in the illustration
below.
Central
Site
DLCI 200
Customer
NMS
Frame Relay
0
20
Network
Frame
CI
L
Relay
D
DLCI 200
10.10.10.3
Router
DLCI 210
135.18.2.3
DLCI 909
DLCI 210
DLCI 200
DLCI 210
DLCI 909
10.10.10.2
9/
90
CI I 2
DL DCL
E
DLCI 908
Frame
Relay
Router
135.18.2.2
Physical Connection
PVC Connection
Network
Operation
Center
10.10.10.4
Frame
Relay
Router
135.18.2.4
10.10.10.1 NMS
99-16392
Simply create a dedicated multiplexed PVC between the NOC and the central site
router, then let the system automatically discover the DLCI and configure an
EDLCI for management using its Auto-Configuration feature (DLCI 909/EDLCI 2)
to manage the central site system.
In this case, one PVC is used for both system and router management.
H
DLCI 909 is used to manage the router.
H
DLCI 909/EDLCI 2 is used to manage the system.
H
DLCI 908 is a static route between the central site system and its router for
back door managment of the system.
Management through a back door can be accomplished via a dial line to the
router. Should the network fail, communication with both the router and the
NextEDGE or FrameSaver device would be maintained.
When management through a back door is desired, a local management PVC
must be created between each NextEDGE or FrameSaver device and its router.
The device will not pass the DLCI to the network, so the PVC is reserved for
management only.
B-6
DRAFT — June 1999
9191-A2-GH30-00
IP Addressing
Joint Customer and Service Provider Management
FrameSaver systems can be configured so they can be managed by the
customer’s central site, as well as by the NOC. Separate IP addressing schemes
for each, the central site and the NOC, are used, as shown in the illustration.
Remote
Sites
Network
Operation
Center
Central
Site
Customer
NMS
DLCI 900
Frame
Relay
Router
9
Service
90 Provider NMS
CI
L
D
DLCI 200/EDLCI 2/EDLCI 3
DLCI 200
Frame
Relay
Router
EDLCI 2 135.18.2.3 Frame
EDLCI 3 180.20.2.6 Relay
Router
DLCI 210
135.18.2.2
180.20.2.5
EDLCI 2 135.18.2.4
EDLCI 3 180.20.2.7
DLCI 220
Frame
Relay
Router
EDLCI 2 135.18.2.5
EDLCI 3 180.20.2.8
99-16471
In this example, a single DLCI between the customer’s central and remote sites
is used to carry the customer’s management data and the NOC’s management
data. Separate management EDLCIs are configured for each, and each uses its
own IP addressing scheme.
In this case, one dedicated PVC is required, but two EDLCIs are configured.
H
DLCI 909 is used to manage the central site system.
H
EDLCI 2 is used for customer management data.
H
EDLCI 3 is used for service provider management data.
Different IP addresses and subnet masks are configured for each EDLCI, and
the service provider manually configures EDLCI 3 for its management traffic on
the PVC.
9191-A2-GH30-00
DRAFT — June 1999
B-7
IP Addressing
Frame Relay IP Addressing Scheme Examples
The following sections include examples that describe some typical network
scenarios. They are not the only scenarios that can be used. The subnet mask
shown for each NextEDGE FrameSaver system or FrameSaver unit is
255.255.255.0.
Direct PVCs to Remote Frame Relay Devices
In this example, NextEDGE FrameSaver System A is connected to:
H
The NMS at the central site through the router.
H
Each remote NextEDGE FrameSaver system or FrameSaver unit through a
management PVC.
The illustration below shows three separate PVCs, one for each remote
NextEDGE/FrameSaver device. The management data for each site is
transported via an EDLCI in each PVC.
SNMP NMS
Ethernet
135.18.2.17
135.18.40.1
DLCI 50
B
135.18.2.18
DLCI 60
C
Frame
Relay
Network
135.18.2.26
D
DLCI 20
DLCI 21
DLCI 70
Subnet 135.18.2.0
Physical Connection
B-8
Frame
Relay
Router
DRAFT — June 1999
DLCI 22
DLCI 201
IP Address: 135.18.40.3
A
135.18.2.1
Subnet 135.18.40.0
PVC Connection
99-16419
9191-A2-GH30-00
IP Addressing
Routing to Remote Frame Relay Devices on the Same Subnet
H
H
Remote NextEDGE/FrameSaver devices through management PVCs.
The illustration below shows two management PVCs at the central site, and
one management PVC between the remote-site devices B and C. There is no
management PVC between the central site NextEDGE system and FrameSaver
device C. Management is through device B to device C using the FrameSaver
proprietary RIP feature.
135.18.2.17
Ethernet
SNMP NMS
B
135.18.40.1
135.18.2.18
C
Frame
Relay
Network
135.18.2.26
Frame
Relay
Router
IP Address: 135.18.40.3
A
D
135.18.2.1
Subnet 135.18.2.0
Physical Connection
9191-A2-GH30-00
DRAFT — June 1999
Subnet 135.18.40.0
PVC Connection
99-16422
B-9
IP Addressing
Routing to Remote Frame Relay Devices Using Different Subnets
H
H
Two remote NextEDGE/FrameSaver devices through management PVCs.
The illustration below shows two management PVCs, with NextEDGE/
FrameSaver devices B and C connected through one management PVC. By
configuring a different IP address and subnet for each management PVC:
H
Devices B and C share a subnet: 135.18.3.0.
H
NextEDGE FrameSaver Systems A and B share a different subnet:
135.18.2.0.
H
NextEDGE Systems A and D share yet another subnet: 135.18.4.0.
Subnet 135.18.40.0
*
Subnet 135.18.2.0
135.18.2.2
B
SNMP NMS
Ethernet
135.18.40.1
Frame
Relay
Router
135.18.3.2
C
COM Port
IP Address: 135.18.40.3
Frame
Relay
Network
135.18.3.3
135.18.2.1
Subnet 135.18.3.0
A
135.18.4.26
135.18.4.1
D
Subnet 135.18.4.0
Physical Connection
*
B-10
PVC Connection
This subnet connection can be to any of the following:
• Frame relay RFC 1490 IP router via the DTE Port
• Frame relay non-RFC router via AUX port-to-COM port
• SNMP NMS via the COM Port
• Terminal server via the COM Port
• LAN adapter via the COM Port
DRAFT — June 1999
99-16423
9191-A2-GH30-00
IP Addressing
Routing to Remote Frame Relay Devices Using Routers
In the following examples, the NextEDGE FrameSaver system at the central site
is connected to:
H
A router ( instead of a LAN connection).
H
The router is connected to the NMS.
The router’s additional serial or AUX port connection is not used for management
and no additional network PVCs are required.
In the following examples, data is not routed by the NextEDGE/FrameSaver
devices, and management PVCs are not configured between them. Instead,
management data for the remote devices is routed through the routers, with
management PVCs configured between the routers and their NextEDGE/
FrameSaver devices. Connection is via the existing DTE cable, between the
router’s DTE interface and the device.
The illustration below shows all NextEDGE FrameSaver systems and
FrameSaver devices on the same subnet, and all routers on the same subnet.
Subnet 135.18.1.0
135.18.3.2
SNMP NMS
135.18.1.2
B
FR Router:
135.18.2.2
FR Router:
135.18.1.1
FR Router:
135.18.2.1
Frame
Relay
Network
135.18.3.3
C
A
Subnet 135.18.3.0
FR Router:
135.18.2.3
135.18.3.1
Subnet 135.18.2.0
FR = Frame Relay
Physical Connection
99-16424
PVC Connection
9191-A2-GH30-00
DRAFT — June 1999
B-11
IP Addressing
The following illustration is a more complex example in which each NextEDGE/
FrameSaver device is on its own subnet, having a subnet mask of 255.255.255.0.
This subnet is independent of the subnet on the LAN supported by the local
router.
Subnet
135.18.2.0
Subnet 135.18.1.0
Subnet 135.18.5.0
135.18.5.2
FR Router:
135.18.2.1
Subnet
135.18.3.0
SNMP NMS
135.18.1.2
COM
B
Port
FR Router:
135.18.5.1
FR Router:
135.18.1.1
Subnet 135.18.6.0
135.18.6.2
Frame
Relay
Network
FR Router:
135.18.4.1
COM
Port
A
C
FR Router:
135.18.3.1
COM
Port
FR Router:
135.18.6.1
Physical Connection
FR = Frame Relay
B-12
135.18.4.2
Subnet 135.18.4.0
PVC Connection
DRAFT — June 1999
99-16425
9191-A2-GH30-00
IP Addressing
Assigning Frame Relay IP Addresses and Subnet Masks
Once you select an IP scheme, assign an address (or addresses) to the
NextEDGE/FrameSaver devices.
H
If one IP address is wanted for the NextEDGE/FrameSaver device, set the
node IP address and subnet mask.
H
If an IP address is wanted for each interface, assign a separate IP address
and subnet mask to each interface.
If using . . .
Then . . .
COM port as a
management interface
Assign the node IP address and subnet mask or the
COM port IP address and subnet mask.
Main Menu→ Configuration→ Management and
Communication→ Node IP
Integral modem as a
Configure an IP address and subnet mask to the COM
and modem ports, or to the node IP address if only one
IP address per device is desired.
Communication→ Modem Port
Or, configure the node IP address and subnet mask.
Communication→ Node IP
Management PVC as a
9191-A2-GH30-00
Assign IP addresses and subnet masks to each PVC, or
to the node IP address if only one IP address per device is
desired.
Communication→ Management PVCs
DRAFT — June 1999
B-13
IP Addressing
NextEDGE T1 TDM IP Addressing
The following sections include examples that describe some typical network
scenarios. They are not the only scenarios that can be used. The subnet mask
shown for each NextEDGE system’s T1 TDM NAM is 255.255.255.0.
The following sections are included:
H
Direct Management Links to Remote T1 TDM Systems on page B-14.
H
Routing to Remote T1 TDM Systems on the Same Subnet on page B-15.
H
Routing to Remote T1 TDM Systems Using Different Subnets on page B-16.
H
Routing to Remote T1 TDM Systems Using Routers on page B-17.
H
Assigning T1 TDM System IP Addresses and Subnet Masks on page B-18.
Direct Management Links to Remote T1 TDM Systems
In this example, NextEDGE T1 TDM System A is connected to:
H
H
Each remote T1 TDM system through a management link (multiple EDLs).
B
SNMP NMS
Ethernet
135.18.2.17
135.18.40.1
C
135.18.2.18
T1
Network
A
D
135.18.2.26
Subnet 135.18.2.0
Physical Connection
B-14
COM Port
IP Address: 135.18.40.3
DRAFT — June 1999
135.18.2.1
Subnet 135.18.40.0
EDL Management Link
99-16427
9191-A2-GH30-00
IP Addressing
Routing to Remote T1 TDM Systems on the Same Subnet
In this example, NextEDGE T1 TDM System A is connected to:
H
H
Remote T1 TDM systems through EDL management links.
The illustration shows two EDL management links at the central site, with T1
TDM Systems B and C connected through one EDL management link.
B
Ethernet
135.18.2.17
SNMP NMS
135.18.40.1
C
135.18.2.18
T1
Network
A
D
135.18.2.26
Subnet 135.18.2.0
Physical Connection
9191-A2-GH30-00
COM Port
IP Address: 135.18.40.3
DRAFT — June 1999
135.18.2.1
Subnet 135.18.40.0
EDL Management Link
99-16428
B-15
IP Addressing
Routing to Remote T1 TDM Systems Using Different Subnets
In this example, the NextEDGE T1 TDM System A is connected to:
H
H
Two remote T1 TDM systems through EDL management links.
The illustration shows two EDL management links, with T1 TDM Systems B and
C connected through one EDL management link. By configuring a different IP
address and subnet for each management link:
H
T1 TDM Systems B and C share a subnet: 135.18.3.0.
H
T1 TDM Systems A and B share a different subnet: 135.18.2.0.
H
T1 TDM Systems A and D share yet another subnet: 135.18.4.0.
Subnet 135.18.2.0
135.18.2.2
B
Subnet 135.18.40.0
*
SNMP NMS
Ethernet
135.18.40.1
135.18.3.2
C
COM Port
IP Address: 135.18.40.3
T1
Network
135.18.2.1
A
135.18.3.3
Subnet 135.18.3.0
D
135.18.4.1
135.18.4.26
Physical Connection
*
Subnet 135.18.4.0
EDL Management Link
This subnet connection can be to any of the following:
• SNMP NMS via the COM Port
• LAN adapter via the COM Port
• Terminal server via the COM Port
99-16429
B-16
DRAFT — June 1999
9191-A2-GH30-00
IP Addressing
Routing to Remote T1 TDM Systems Using Routers
In the following example, each NextEDGE T1 TDM system receives its
management traffic through a connection from the COM port to the serial port of a
router. In this case, the T1 TDM systems do not route data among themselves,
but rely on the IP routers to route management traffic for the remote systems
using data streams configured between the routers.
Each T1 TDM system is configured to be on its own subnet, having a subnet
mask of 255.255.255.0. This subnet is independent of the subnet on the LAN
supported by the local router.
Subnet 135.18.1.0
Subnet 135.18.5.0
135.18.5.2
SNMP NMS
135.18.1.2
COM
Router:
135.18.5.1
Serial
Port
Router:
135.18.1.1
Router:
135.18.2..
Serial
Port
Subnet 135.18.2.0
T1
Network
Router:
135.18.4.1
COM
Subnet 135.18.6.0
135.18.6.2
135.18.4.2
Subnet 135.18.4.0
Router:
135.18.6.1
COM
Serial
Port
Router:
135.18.3..
Subnet 135.18.3.0
9191-A2-GH30-00
DRAFT — June 1999
497-15196-01
B-17
IP Addressing
Assigning T1 TDM System IP Addresses and Subnet Masks
Once you select an IP scheme, assign an address (or addresses) to the
NextEDGE system(s).
B-18
If using . . .
Then . . .
COM port as a
Assign the COM port address and net mask.
Main Menu→ Configuration→ Management &
Communication→ Communication Protocol
COM port connected to an
external modem
Configure using an alternate IP address.
Main Menu→ Configuration→ Management &
Communication→ Communication Protocol
FDL, DDL, or EDL
management links
Assign IP addresses and net masks to each management
link.
Main Menu→ Configuration→ Network (for FDL and
DDL)
Main Menu→ Configuration→ Sync Data Ports (for EDL)
DRAFT — June 1999
9191-A2-GH30-00
SNMP MIBs and Traps, and
RMON Alarm Defaults
C
This appendix includes the following sections:
H
MIB Support on page C-2.
H
Downloading MIBs and SNMP Traps on page C-2.
H
Standards Compliance for SNMP Traps on page C-3.
— Trap: warmStart on page C-3.
— Trap: authenticationFailure on page C-4.
— Traps: linkUp and linkDown on page C-4.
— Traps: enterprise-Specific on page C-8.
— Traps: RMON-Specific on page C-14.
H
RMON Alarm Defaults on page C-15.
— Static Frame Relay Interface Alarm Defaults on page C-17.
— Dynamic Frame Relay Interface Alarm Defaults on page C-19.
— DLCI Alarm Defaults – Paradyne Area on page C-20.
— Static DLCI Alarm Defaults – NetScout Area on page C-21.
— Dynamic DLCI Alarm Defaults – NetScout Area on page C-22.
H
9191-A2-GH30-00
Object ID Cross-Reference (Numeric Order) on page C-23.
DRAFT — June 1999
C-1
MIB Support
The NextEDGE system supports the SNMP Version 1, and has the capability of
being managed by any industry-standard SNMP manager and accessed by
external SNMP managers using SNMP protocol.
The following MIBs are supported:
H
MIB II (RFC 1213 and RFC 1573)
H
Frame Relay DTEs MIB (RFC 2115)
H
DS1/E1 MIB (RFC 1406)
H
RS-232-Like MIB (RFC 1659)
H
Frame Relay Service MIB (RFC 1604)
H
Enterprise MIB
H
RMON Version 1 MIB (RFC 1757)
H
RMON Version 2 MIB (RFC 2021)
Downloading MIBs and SNMP Traps
Paradyne standard and enterprise MIBs are available from the Paradyne World
Wide Web site.
" Procedure
To access Paradyne MIBs:
1. Access the Paradyne World Wide Web site at www.paradyne.com.
2. Select Service & Support.
3. Select Management Information Base (MIBs).
The download procedure may vary depending upon your browser or NMS
application software. Refer to your browser or NMS manual for additional
download information.
C-2
DRAFT — June 1999
9191-A2-GH30-00
Standards Compliance for SNMP Traps
NextEDGE systems, with their special operational trap features, comply with
SNMP format standards.
All traps have an associated string to help you decipher the meaning of the trap.
Strings associated with an interface with a substring containing $ifString have the
following format:
‘DLCI $dlciNumber of $ifName frame relay link “$linkName”.’
— $dlciNumber is the DLCI number. DLCI $dlciNumber only appears when
a DLCI is associated with the trap.
— $linkName is the name given to the link. Frame relay $linkName only
appears when a frame relay link is associated with the trap.
— $ifName is the string returned for the SNMP ifName variable.
Example:
‘DLCI 100 of Sync Data Port S01P1 frame relay’
In this example, a DLCI and a frame relay link are associated with the trap.
The NextEDGE system supports the following traps:
H
warmStart on page C-3.
H
authenticationFailure on page C-4.
H
linkUp and linkDown on page C-4.
H
enterprise-Specific on page C-8.
H
RMON-Specific on page C-14.
These traps are listed in alphabetical order within each table.
Trap: warmStart
This trap indicates that the NextEDGE system has been reset as a result of a
reset command or a power disruption.
Table C-1. warmStart Trap
Trap
What It Indicates
Possible Cause
warmStart
NextEDGE system has just
reinitialized and stabilized
itself.
H Reset command sent.
Variable-Bindings
H Power disruption.
String:
‘Unit reset.’
devLastTrapString
(devHealthAndStatus. mib)
9191-A2-GH30-00
DRAFT — June 1999
C-3
Trap: authenticationFailure
Table C-2. authenticationFailure Trap
Trap
What It Indicates
Possible Cause
authenticationFailure
Access to the NextEDGE
system was attempted and
failed.
H SNMP protocol message not
properly authenticated.
H Three unsuccessful attempts
were made to enter a correct
login user ID/password
combination.
H IP Address security is enabled
and a message was received
from the SNMP Manager
whose address was not on the
lost of approved managers.
String:
‘Unauthorized access attempted.’
Variable-Bindings
devLastTrapString
(devHealthAndStatus. mib)
Traps: linkUp and linkDown
These traps are supported on the following interfaces:
H
Network, PRI or BRI, DSX-1, and synchronous data ports – Physical sublayer
interfaces
H
Frame relay logical link layer interfaces
Table C-3. linkUp and linkDown Traps
C-4
Trap
What It Indicates
Possible Cause
linkDown
A failure in one of the
communication interfaces
has occurred.
A failure in one of the
communication interfaces has
occurred.
linkUp
One of the failed
One of the failed communication
communication interfaces is interfaces is up and operational.
up and operational.
DRAFT — June 1999
9191-A2-GH30-00
The following variable-bindings support the linkUp and linkDown traps.
Table C-4. linkUp and linkDown Variable-Bindings (1 of 3)
Interface
Variable-Bindings
Possible Cause
Physical Sublayer – Represented by the entry in the MIB II Interfaces Table.
T1 Network,
DSX-1,
PRI
(Supported by the
media-specific DS1
MIB.)
H ifIndex (RFC 1573)
H ifAdminStatus
(RFC 1573)
H ifOperStatus (RFC 1573)
H devLastTrapString
(devHealthAndStatus.mib)
H linkDown – One or more alarm
conditions are active on the
interface.
Alarm conditions include:
– Loss of Signal (LOS) or
far-end loss of signal
– Out of Frame (OOF)
– Alarm Indication Signal
(AIS)
– Excessive Error Rate (EER)
– Yellow Alarm
– Loopback
Strings:
‘$ifString down.’ No alarms
exist. (E.g., ‘Network T1 down
due to loopback.’ )
‘$ifString administratively
shutdown.’ (Due to an
intentional shutdown.)
H linkUp – No alarms on the
interface.
String:
‘$ifString up.’
Synchronous
Data Port
H ifAdminStatus
(RFC 1573)
(Supported by the
media-specific
RS232-like MIB.)
H devLastTrapString
port.
– DTR 1
– RTS 2
– ‘ ’ – Not DTR or RTS, but
link is down.
String:
‘$ifString $alarmString down.’
(E.g., ‘Sync Data Port S01P1
DTR and RTS down.’ )
port.
String:
‘$ifString up.’
1
The DTR alarm condition will only generate a linkUp/ linkDown trap if the DTE
supports the DTR lead state.
2 The RTS alarm condition will only generate a linkUp/ linkDown trap if the DTE
supports the RTS lead state.
9191-A2-GH30-00
DRAFT — June 1999
C-5
Interface
Variable-Bindings
Possible Cause
Physical Sublayer (Cont’d)
BRI
H ifAdminStatus
(Supported through
ifIndex – RFC 1573.)
(RFC 1573)
H devLastTrapString
interface.
Strings:
exist on the link.
interface.
String:
‘$ifString up.’
OCU
H ifAdminStatus
(Supported by the
media-specific
RS232-like MIB.)
(RFC 1573)
H ifType (RFC 1573)
interface.
– Loss of Signal
– Abnormal Station Code
– 64 KCC Loop OOF
– DDS Net Failure xxxxxx
(xxxxxx is the failure code)
– Loss of Loop Timing
interface.
C-6
DRAFT — June 1999
9191-A2-GH30-00
Interface
Variable-Bindings
Possible Cause
Logical Link Sublayer – Represented by the entry in the MIB II Interfaces Table.
T1 Network,
BRI,
PRI,
Synchronous
Data Port
H ifAdminStatus
(RFC 1573)
H devLastTrapString
Service Side of the
Frame Relay UNI
(Supported by the
media-specific Frame
Relay Services MIB.)
H linkDown – LMI is down for the
LMI Protocol configured, 3 or
Frame Relay link is disabled.
Strings:
exist on the link due to LMI.
‘$ifString LMI down.’ No
alarms exist on the link.
(E.g., ‘Frame Relay link
“Chicago” on T1 Network
LMI down.’ )
H linkUp – LMI is up or Frame
Relay link is enabled.
String:
‘$ifString up.’
T1 Network,
BRI,
PRI,
Synchronous
Data Port
H ifAdminStatus
(RFC 1573)
H devLastTrapString
DTE Side of the
Frame Relay UNI
(Supported by the
media-specific Frame
Relay DTE’s MIB.)
3
9191-A2-GH30-00
H linkDown – LMI is down for the
LMI Protocol configured, 3 or
Frame Relay link is disabled.
Strings:
‘$ifString LMI down.’
H linkUp – LMI is up or Frame
Relay link is enabled.
String:
‘$ifString up.’
If the LMI Protocol is not configured, a linkUp/ linkDown trap is based solely upon
whether the interface is enabled or disabled.
DRAFT — June 1999
C-7
Traps: enterprise-Specific
These traps indicate that an enterprise-specific event has occurred. Supported
enterprise-specific traps include the following, listed in alphabetical order:
Table C-5. enterprise-Specific Traps (1 of 2)
Trap
What It Indicates
Possible Cause
enterpriseAPMFailed(9)
Operating software cannot
communicate with an APM.
The system detected the failure
of an APM, or the APM was
removed from its configured slot.
String:
‘APM failure on module in slot x.’
(Slot x is the slot number.)
enterpriseAPMFailedClear(109)
Operating software is
communicating with the
APM again.
The system detected the failure
of an APM, or the APM was
removed from its configured slot.
String:
‘APM failure cleared on module
in slot x.’ (Slot x is the slot
number.)
enterpriseCIRChange(115)
CIR has changed due to
the LMI report.
LMI Protocol is set to Standard
and the network’s CIR changed.
enterpriseConfigChange(6)
Configuration has been
changed via the async user
interface or an SNMP
Manager after 60 seconds
has elapsed without
another change.
Configuration has been changed
via the async user interface or an
SNMP Manager from
devLastTrapString
(devHealthAndStatus.mib).
enterpriseDeviceFail(3)
An internal device failure.
Operating software has detected
an internal device failure.
enterpriseDLCIDown(11)
The DLCI for an interface
supporting one side of the
UNI is down.
DLCI is down.
enterpriseDLCIUp(12)
The DLCI for an interface
supporting one side of the
UNI is up.
DLCI is up again.
enterpriseModuleMisConfig(8)
The system detected a
module misconfiguration
error.
An APM is installed in a slot
currently configured for another
type of APM.
The variable binding for this
trap is devHealthandStatus.
String:
‘Misconfiguration occurred on
module in slot x.’ (Slot x is the
slot number.)
C-8
DRAFT — June 1999
9191-A2-GH30-00
Table C-5. enterprise-Specific Traps (2 of 2)
Trap
What It Indicates
Possible Cause
enterpriseModuleMisConfigClear(108)
The misconfiguration error
has cleared.
The APM was returned to its
configured slot.
String:
‘Misconfiguration cleared on
module in slot x.’ (Slot x is the
slot number.)
9191-A2-GH30-00
enterprisePrimaryClockFail(1)
A failure of the device’s
primary clock source.
that the primary clock source has
failed.
enterprisePrimaryClockFailClear(101)
The failure of the device’s
primary clock source has
cleared.
that the primary clock source is
now operational again.
enterpriseRMONResetToDefault(13)
All RMON-related option
changes have been reset to settings have been reloaded,
their default values.
returning RMON-related options
to their original settings.
enterpriseSecondaryClockFail(4)
A failure of the device’s
secondary clock source.
enterpriseSecondaryClockFailClear(104)
The failure of the device’s
that the secondary clock source
secondary clock source has is operational again.
cleared.
enterpriseSelfTestFail(2)
A hardware failure.
System has completed
(re)initialization and a hardware
failure was detected.
enterpriseTestStart(5)
A test is running.
At least one test has been
started on an interface or virtual
circuit.
enterpriseTestStop(105)
All tests have been halted.
All tests have been halted on an
interface or virtual circuit.
DRAFT — June 1999
has failed.
C-9
The following variable-bindings support the enterprise-Specific traps and
conditions for each interface.
Table C-6. enterprise-Specific Variable-Bindings (1 of 4)
Trap
Variable-Bindings
Possible Cause
enterpriseAPMFailed(9)
H devCfgCardSlot
H System detected the failure of
an APM.
H APM was removed from its
configured slot.
H APM recovered or was
enterpriseAPMFailedClear(109)
replaced.
H APM was returned to its
configured slot.
H devFrExtDlciIfIndex
enterpriseCIRChange(115)
(devFrExt.mib)
H devFrExtDlciDlci
(devFrExt.mib)
H devFrExtDlciCIR
LMI Protocol is set to Standard
and the network’s CIR changed.
String:
‘CIR on $ifString changed to
$CIR bps.’
(devFrExt.mib)
H devLastTrapString
H devLastTrapString
enterpriseConfigChange(6)
Configuration has been changed
via the async user interface or an
SNMP Manager from
devLastTrapString
(devHealthAndStatus.mib).
String:
‘Device configuration change.’
H devLastTrapString
enterpriseDeviceFail(3)
(devHealthAndStatus.mib is the internal failure
number.)
enterpriseModuleMisConfig(8)
H devCfgCardSlot
enterpriseModuleMisConfigClear(108)
C-10
DRAFT — June 1999
An internal device failure was
detected.
String:
‘Device fail with error code
xxxxxxxx.’
H An APM is installed in a slot
that is configured for another
type of APM.
H Correct type of APM is
installed in the slot.
9191-A2-GH30-00
Trap
Variable-Bindings
Possible Cause
enterpriseDLCIDown(11)
DLCI Status is set to Inactive; the
DLCI is down.
(devFrExt.mib)
H devFrExtDlciDlci
(devFrExt.mib)
H devLastTrapString
(devHealthAndStatus.mib.)
enterpriseDLCIUp(12)
Strings:
‘$ifString down.’ (Due to LMI or
physical failure.)
shutdown.’ (Due to an intentional
shutdown.)
DLCI Status is set to Active;
DLCI is up again.
String:
‘$ifString up.’
H devLastTrapString
enterprisePrimaryClockFail(1)
that the primary clock source has
failed.
String:
‘Primary clock failed.’
enterprisePrimaryClockFailClear(101)
that the primary clock source is
now operational again.
String:
‘Primary clock restored.’
H devLastTrapString
enterpriseRMONResetToDefault(13)
settings have been reloaded,
returning RMON-related options
to their original settings.
String:
‘RMON database reset to
defaults.’
enterpriseSecondaryClockFail(4)
H devLastTrapString
has failed.
String:
‘Secondary clock failed.’
enterpriseSecondaryClockFailClear(104)
is operational again.
String:
‘Secondary clock restored.’
enterpriseSelfTestFail(2)
H devLastTrapString
System has completed
(re)initialization and a hardware
failure was detected.
String:
‘Selftest failed: $s.’ ($s is the
contents of devSelfTestResult.)
9191-A2-GH30-00
DRAFT — June 1999
C-11
Trap
Variable-Bindings
Possible Cause
enterpriseTestStart(5)
For physical interfaces and
frame relay links:
At least one test has been
started on an interface or virtual
circuit.
H .0.0 (placeholder)
H devLastTrapString
(devHealthAndStatus.mib
String:
‘$testString test started
on$ifString.’ (E.g., ‘DTE External
Loopback test started on Sync
Data Port S01P1.’)
For virtual circuits (DLCIs):
enterpriseTestStop(105)
(devFrExt.mib)
H devFrExtDlciDlci
(devFrExt.mib)
H devLastTrapString
(devHealthAndStatus.mib
OCU
H ifAdminStatus
(RFC 1573)
H ifType (RFC 1573)
H devOcuTestType
(devOcu.mib)
All tests have been halted on an
interface or virtual circuit.
String:
‘$testString test started
on$ifString.’ (E.g., ‘DTE External
Loopback test stopped on Sync
Data Port S01P1.’)
H enterpriseTest Start – The
following test is active on the
interface:
– Latching and Nonlatching
CSU Loopbacks
– Latching and Nonlatching
DSU Loopbacks
– OCU Loopback
– DS0 Loopback
– Line Loopback
– Data Loopback
– Remote Latching CSU,
DSU, and OCU Loopbacks
– Remote Nonlatching CSU,
DSU, and OCU Loopbacks
– Send Pattern
– Monitor Pattern
H enterpriseTest Stop – Test is
no longer running on the
interface.
C-12
DRAFT — June 1999
9191-A2-GH30-00
Trap
Variable-Bindings
Possible Cause
E&M,
FXS,
FXO
H ifAdminStatus
(RFC 1573)
H ifType (RFC 1573)
H devVoiceTestType
(devVoice.mib)
interface:
– Digital Loopback
– Analog Loopback
– Line Loopback
– Send DRS Tone to T1
interface and user
– Send Quiet Tone to T1
interface and user
H enterpriseTest Stop – Test is
no longer running on the
interface.
Voice Port
H ifAdminStatus
(RFC 1573)
H ifType (RFC 1573)
H ifTestType (RFC 1573)
port:
– Analog Loopback
– Digital Loopback
– Line Loopback
– Send DRS Tone
– Send Quiet Tone
H enterpriseTest Stop – No
longer any tests running on
the port.
9191-A2-GH30-00
DRAFT — June 1999
C-13
Traps: RMON-Specific
Two traps are defined to support the Alarm and Events Groups of RMON, which
are shown below with their variable-bindings.
See RMON Alarm Defaults on page C-15 for the default values that will generate
RMON-specific traps.
Table C-7. risingAlarm and fallingAlarm Variable-Bindings
Trap
Variable-Bindings
Possible Cause
risingAlarm
H alarmIndex (RFC 1757)
Object being monitored has risen
above the set threshold.
H alarmVariable
(RFC 1757)
H alarmSampleType
(RFC 1757)
H alarmValue (RFC 1757)
H alarmRisingThreshold
(RFC 1757)
H devLastTrapString
String:
‘Change in $variableName
$typeString threshold of
$alarmRisingThreshold by
$(alarmValue –
AlarmRisingThreshold.’
(E.g., Octets received on
Network T1 frame relay rose
to threshold of 1.’)
fallingAlarm
H alarmIndex (RFC 1757)
H alarmVariable
(RFC 1757)
H alarmSampleType
(RFC 1757)
H alarmValue (RFC 1757)
H alarmFallingThreshold
(RFC 1757)
H devLastTrapString
Object being monitored has
fallen below the set threshold.
String:
‘Change in $variableName
$typeString threshold of
$alarmFallingThreshold by
$(alarmValue –
AlarmFallingThreshold.’
(E.g., Octets received on
Network T1 frame relay fell
to threshold of 1.’)
C-14
DRAFT — June 1999
9191-A2-GH30-00
RMON Alarm and Event Defaults
The NextEDGE FrameSaver system supports automatic generation of RMON
alarm and event information. Each alarm sets an SNMP variable to monitor.
When the threshold set for the monitored variable is exceeded, an SNMP trap or
a log event is sent.
Event Defaults
Since all events sent are under the control of the FrameSaver system, there is no
need to define multiple events for each alarm type, so only the following two
events need to be generated:
eventIndex
eventDescription
eventType
eventCommunity
1
Default SLV Rising Event
snmp-trap(3)
0
2
Default SLV Falling Event snmp-trap(3)
0
The alarm default tables starting on the next page show how each RMON default
alarm is set by the FrameSaver system, shows the alarm and event types, the
interval used when generating alarms, and thresholds.
H
Physical Interface Alarm Defaults on page C-16.
H
Static Frame Relay Interface Alarm Defaults on page C-17.
H
Dynamic Frame Relay Interface Alarm Defaults on page C-19.
H
DLCI Alarm Defaults – Paradyne Area on page C-20.
H
Static DLCI Alarm Defaults – NetScout Area on page C-21.
H
Dynamic DLCI Alarm Defaults – NetScout Area on page C-22.
See Standards Compliance for SNMP Traps on page C-3 for information about
how traps work, and Traps: RMON-Specific on page C-14 for traps specific to
remote monitoring.
9191-A2-GH30-00
DRAFT — June 1999
C-15
Rising Event Operation
If a rising threshold is crossed during the interval shown in a table (e.g., frames
dropped by the network), the event is armed and an alarm is generated at the
end of the interval. Only one alarm per event per interval is generated. The alarm
condition persists until the event has been disarmed (reset).
The event is disarmed when a falling threshold has been crossed and the rising
threshold has not been crossed during an interval, allowing the event to return to
its original disarmed state.
Physical Interface Alarm Defaults
These alarms only apply to the FrameSaver system’s network interface. They are
created during RMON initialization and put into the Paradyne-defined alarm area.
Item
Sample
Type 1 MIB/Tag/OID 2
Errored Seconds
D
MIB: DS1/E1 MIB (RFC 1406)
Tag: dsx1TotalESs
Event
Type
Rising
Falling
Threshold Threshold
Default
Default
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
1
1
Interval
OID: .1.3.6.1.2.1.10.18.9.1.2.I
Unavailable
Seconds
D
Tag: dsx1TotalUASs
OID: .1.3.6.1.2.1.10.18.9.1.5.I
1
D = Delta. Indicates that the calculated difference between the current value and the previous value is contained
in the MIB.
2 I in the OID = Interface ID of the frame relay link.
C-16
DRAFT — June 1999
9191-A2-GH30-00
Static Frame Relay Interface Alarm Defaults
These alarms apply to the FrameSaver system’s frame relay interfaces. They are
created during RMON initialization.
Table D-2. Static Frame Relay Interface Alarm Defaults (1 of 2)
Item
Sample
Invalid Frames
D
MIB: devfrext.mib (E)
Tag: devFrExtLinkRxIlFrames
Event
Type
Rising
Falling
Threshold Threshold
Default
Default
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
1
1
Interval
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.18.I
Short Frames
D
Tag: devFrExtLinkRxShort
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.6.I
Long Frames
D
Tag: devFrExtLinkRxLong
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.7.I
Rx Discards
D
Tag: devFrExtLinkRxDiscards
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.15.I
Tx Discards
D
Tag: devFrExtLinkTxDiscards
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.14.I
Rx Total Errors
D
Tag: devFrExtLinkTotRxErrs
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.20.I
Tx Total Errors
D
Tag: devFrExtLinkTotTxErrs
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.19.I
1
in the MIB.
9191-A2-GH30-00
DRAFT — June 1999
C-17
Table D-2. Static Frame Relay Interface Alarm Defaults (2 of 2)
Item
Sample
Rx Overruns
D
Tag: devFrExtLinkRxOverruns
Event
Type
Rising
Falling
Threshold Threshold
Default
Default
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
1
1
Interval
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.28.I
Tx Underruns
D
Tag: devFrExtLinkTxUnderruns
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.29.I
Rx Nonoctet Aligns
D
Tag: devFrExtLinkRxNonOctet
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.16.I
Rx CRC Errors
D
Tag: devFrExtLinkRxCrcErrs
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.17.I
Total LMI Errors
D
Tag: devFrExtLinkTotalLMIErrs
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.7.1.32.I
1
in the MIB.
C-18
DRAFT — June 1999
9191-A2-GH30-00
Dynamic Frame Relay Interface Alarm Defaults
These alarms apply to the FrameSaver system’s frame relay interfaces. They are
created during RMON initialization, and will change if the interface’s line speed
changes.
Table D-3. Dynamic Frame Relay Interface Alarm Defaults
Item
Sample
Rx Utilization
D
MIB: MIB II (RFC 1573)
Tag: ifInOctets
Interval
Event
Type
Rising
Falling
Threshold Threshold
Default
Default
60 secs
(1 min)
Rising
70% of link 65% of link
capability
capability
60 secs
(1 min)
Rising
capability
capability
OID: .1.3.6.1.2.1.2.2.1.10.I
Tx Utilization
D
Tag: ifOutOctets
OID: .1.3.6.1.2.1.2.2.1.16.I
1
in the MIB.
9191-A2-GH30-00
DRAFT — June 1999
C-19
DLCI Alarm Defaults – Paradyne Area
These alarms apply to DLCIs on the network interface. They are created either
during RMON initialization or when a DLCI is created, and put into the
Paradyne-defined alarm area.
Table D-4. DLCI Alarm Defaults – Paradyne Area
Item
DLCI Inactive
Seconds
Sample
D
Tag: devFrExtDlciStsInactiveSecs
Event
Type
Rising
Falling
Threshold Threshold
Default
Default
900 secs
(15 mins)
Rising
1
1
900 secs
(15 mins)
Rising
5
5
Rising
1
1
Rising
1
1
60 secs
(1 min)
Rising
5
5
900 secs
(15 mins)
Rising
1
1
Interval
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.2.1.2.I.D
Missing Latency
Responses
D
Tag: devFrExtDlciMissedSLVs
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.1.1.23.I.D
Rx FECNs
D
MIB: FT DTE MIB (RFC 2115) 60 secs
(1 min)
Tag: frCircuitReceivedFECNs
OID: .1.3.6.1.2.1.10.32.2.1.
5.I.D
Rx BECNs
D
(1 min)
Tag: frCircuitReceivedBECNs
OID: .1.3.6.1.2.1.10.32.2.1.
4.I.D
Congested Seconds D
Tag: devFrExtDlciStsCongestedSecs
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.2.1.6.I.D
Frames Dropped by
Network
D
Tag: frFrExtDlciNetDropFr
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.1.1.20.I.D
1
in the MIB.
A = Absolute. Indicates that the exact value for the item is contained in the MIB.
2
I in the OID = Interface ID of the frame relay link.
D = DLCI number.
C-20
DRAFT — June 1999
9191-A2-GH30-00
Static DLCI Alarm Defaults – NetScout Area
NetScout-defined alarm area.
The thresholds for these alarms can be edited using NetScout Manager Plus so
they match the values in the SLA between the customer and service provider.
See Editing Alarms in Chapter 6, Using NetScout Manager Plus.
???????
Table D-5. Static DLCI Alarm Defaults – NetScout Area
Item
Sample
Current Latency
A
Interval
Event
Type
Rising
Falling
Threshold Threshold
Default
Default
60 secs
(1 min)
Rising
Must be
0
configured.
900 secs
(15 mins)
Rising
Must be
0
configured.
Rising
Must be
0
configured.
Rising
Must be
0
configured.
60 secs
(1 min)
Rising
Must be
0
configured.
(1 min)
Tag: frCircuitSentOctets
Rising
Must be
0
configured.
Tag: devFrExtLatencyLatest
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.3.1.7.I.D
Average Latency
A
Tag: devFrExtLatencyAvg
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.3.1.5.I.D
Frames Received
D
(1 min)
Tag: frCircuitReceivedFrames
OID: .1.3.6.1.2.1.10.32.2.1.
8.I.D
Frames Sent
D
(1 min)
Tag: frCircuitSentFrames
OID: .1.3.6.1.2.1.10.32.2.1.
6.I.D
Tx Frames
Exceeding CIR
D
Tag: devFrExtDlciTxFrOutCIR
OID: .1.3.6.1.4.1.1795.2.24.2.
6.9. 4.1.1.17.I.D
Tx CIR Utilization
D
OID: .1.3.6.1.2.1.10.32.2.1.
7.I.D
1
in the MIB.
2
D = DLCI number.
9191-A2-GH30-00
DRAFT — June 1999
C-21
Dynamic DLCI Alarm Defaults – NetScout Area
NetScout-defined alarm area. They will be reconfigured if the interface’s line
speed changes.
Table D-6. Dynamic DLCI Alarm Defaults – NetScout Area
Item
Rx DLCI Link
Utilization
Sample
D
Interval
MIB: FT DTE MIB (RFC 2115) 60 secs.
(1 min)
Tag: frCircuitReceivedOctets
Event
Type
Rising
Falling
Threshold Threshold
Default
Default
Rising
capability
capability
Rising
capability
capability
OID: .1.3.6.1.2.1.10.32.2.1.
9.I.D
Tx DLCI Link
Utilization
D
MIB: FT DTE MIB (RFC 2115) 60 secs.
(1 min)
OID: .1.3.6.1.2.1.10.32.2.1.
7.I.D
1
in the MIB.
2
D = DLCI number.
C-22
DRAFT — June 1999
9191-A2-GH30-00
Object ID Cross-Reference (Numeric Order)
The FrameSaver system supports automatic generation of RMON alarm and
event information. Each alarm sets an SNMP variable to monitor. When the
threshold set for the monitored variable is exceeded, an SNMP trap or a log
event is sent.
This table is helpful in identifying alarm conditions being tracked when viewing
the NetScout Custom History screen, which provides the OID instead of the alarm
condition.
Table C-9. OID Cross-Reference (1 of 3)
Object ID (OID)
Item
MIB/Tag
Rx Utilization
.1.3.6.1.2.1.2.2.1. . .
.1.3.6.1.2.1.2.2.1.10.I
Tag: ifInOctets
.1.3.6.1.2.1.2.2.1.16. I
Tx Utilization
Tag: ifOutOctets
.1.3.6.1.2.1.10.18.9.1. . .
.1.3.6.1.2.1.10.18.9.1.5.I
Unavailable Seconds
Tag: dsx1TotalUASs
9191-A2-GH30-00
DRAFT — June 1999
C-23
Object ID (OID)
Item
MIB/Tag
Errored Seconds
.1.3.6.1.2.1.10.18.9.1. . .
.1.3.6.1.2.1.10.18.9.1.2.I
Tag: dsx1TotalESs
.1.3.6.1.2.1.10.18.9.1.5.I
Unavailable Seconds
Tag: dsx1TotalUASs
.1.3.6.1.2.1.10.32.2.1. . .
.1.3.6.1.2.1.10.32.2.1.4.I .D
Rx BECNs
MIB: FT DTE MIB (RFC 2115)
Tag: frCircuitReceivedBECNs
.1.3.6.1.2.1.10.32.2.1.5.I .D
Rx FECNs
Tag: frCircuitReceivedFECNs
.1.3.6.1.2.1.10.32.2.1.6.I .D
Frames Sent
Tag: frCircuitSentFrames
.1.3.6.1.2.1.10.32.2.1.7.I .D
Tx CIR Utilization
.1.3.6.1.2.1.10.32.2.1.7.I .D
Tx DLCI Link Utilization
.1.3.6.1.2.1.10.32.2.1.8.I .D
Frames Received
Tag: frCircuitReceivedFrames
.1.3.6.1.2.1.10.32.2.1.9.I .D
Rx DLCI Link Utilization
Tag: frCircuitReceivedOctets
.1.3.6.1.4.1.1795.2.24.2.6.9.4. . .
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.1.1.17.I.D
Tx Frames Exceeding CIR
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.1.1.20.I .D
Frames Dropped by Network MIB: devfrext.mib (E)
Tag: frFrExtDlciNetDropFr
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.1.1.23.I .D
Missing Latency Responses
Tag: devFrExtDlciMissedSLVs
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.2.1.6.I .D
Congested Seconds
Tag: devFrExtDlciStsCongestedSecs
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.2.1.2.I .D
DLCI Inactive Seconds
Tag: devFrExtDlciStsInactiveSecs
C-24
DRAFT — June 1999
9191-A2-GH30-00
Object ID (OID)
Item
MIB/Tag
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.3.1.5.I .D
Average Latency
Tag: devFrExtLatencyAvg
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.3.1.7.I .D
Current Latency
Tag: devFrExtLatencyLatest
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.6.I
Short Frames
Tag: devFrExtLinkRxShort
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.7.I
Long Frames
Tag: devFrExtLinkRxLong
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.14.I
Tx Discards
Tag: devFrExtLinkTxDiscards
.1.3.6.1.4.1.1795.2.24.2.6.9.4. . .
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.15.I
Rx Discards
Tag: devFrExtLinkRxDiscards
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.16.I
Rx Nonoctet Aligns
Tag: devFrExtLinkRxNonOctet
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.17.I
Rx CRC Errors
Tag: devFrExtLinkRxCrcErrs
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.1.1.17.I .D
Tx Frames Exceeding CIR
.1.3.6.1.4.1.1795.2.24.2.6.9.4. . .
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.18.I
Invalid Frames
Tag: devFrExtLinkRxIlFrames
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.19.I
Tx Total Errors
Tag: devFrExtLinkTotTxErrs
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.20.I
Rx Total Errors
Tag: devFrExtLinkTotRxErrs
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.28.I
Rx Overruns
Tag: devFrExtLinkRxOverruns
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.29.I
Tx Underruns
Tag: devFrExtLinkTxUnderruns
.1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.32.I
Total LMI Errors
Tag: devFrExtLinkTotalLMIErrs
9191-A2-GH30-00
DRAFT — June 1999
C-25
Cables, Connectors, and
Pin Assignments
D
This appendix shows the NextEDGE system’s rear panel and pin assignments for
the connectors/interfaces and cables. The following information is included:
H
Rear Panels on page D-4.
— FrameSaver NAM Rear Panel on page D-3.
— T1 TDM NAM Rear Panels on page D-3.
H
COM Port Connectors on page D-4.
— FrameSaver NAM’s Communication Port on page D-4.
— T1 TDM NAM’s Communication Port on page D-4.
— LAN Converter and Adapter Cable on page D-5.
— COM Port-to-PC Cable (3100-F2-550) on page D-6.
— COM Port-to-Terminal Cable (3100-F2-540) on page D-6.
— COM Port-to-Modem Cable on page D-7.
— Gender Adapter/Changer on page D-7.
H
DTE Port Connectors on page D-8.
— FrameSaver NAM’s DTE Port Connector on page D-8.
— T1 TDM NAM’s DTE Port Connector on page D-9.
— EIA-530A-to-V.35 DTE Cable Adapter on page D-10.
— EIA-530A-to-RS-449 DTE Cable Adapter on page D-12.
— EIA-530A-to-X.21 DTE Cable Adapter on page D-13.
— Standard V.35 Straight-through Cable on page D-14.
— Standard V.35 Crossover Cable on page D-14.
9191-A2-GH30-00
DRAFT — June 1999
D-1
H
T1 TDM NAM’s DSX-1 Connector on pageNO TAG.
H
FrameSaver NAM’s DSX-1 Connector on pageNO TAG.
— T1 Line Interface Cable on page D-16.
H
T1 Network Cable (3100-F1-500) on page D-17.
— Canadian T1 Line Interface Cable (3100-F1-510) on page D-17.
— T1 Mass Termination Cable on page D-18.
H
FrameSaver NAM’s Modem Connector on page D-19.
H
FrameSaver NAM’s ISDN DBM Connector on page D-19.
H
Synchronous Data APM on page D-20.
H
Voice APM Cables on page D-21.
— FXO/FXS Voice APM Connector on page D-21.
— E&M Voice APM Connector on page D-22.
— APM Extension Cables on page D-24.
H
OCU Ports on page D-34.
— OCU Port Connectors on page D-34.
NOTE:
In the pin assignment tables of this appendix, if the pin number is not shown,
it is not being used.
D-2
DRAFT — June 1999
9191-A2-GH30-00
Rear Panels
The rear panels for the FrameSaver and T1 TDM NAMs are shown below.
FrameSaver NAM’s Rear Panel
The following illustration shows the single T1 FrameSaver NAM’s rear panel. The
NAM is installed in a 2-slot or 5-slot housing.
T1 TDM NAM Rear Panels
The following illustration shows the single and dual T1 TDM NAM rear panels.
The NAM is installed in a 2-slot, 5-slot housing, or 14-slot access carrier.
SINGLE
T1 NAM
SINGLE
T1 NAM
DUAL
T1 NAM
NET
NET
DBM
DBM
N
E
T
D
B
M
M
D
M
D
S
X
NET 2
DSX
P
O
R
T
1
PORT 1
PORT 1
PORT 2
PORT 2
COM
COM
P
O
R
T
2
C
O
M
99-16469
99-16161-01
FrameSaver NAM
9191-A2-GH30-00
Single T1 TDM NAM
DRAFT — June 1999
99-16470
Dual T1 TDM NAM
D-3
COM Port Connectors
FrameSaver and T1 TDM NAMs have different communications ports. The
following sections provide the pin assignments for each.
FrameSaver NAM’s Communication Port
The following table shows the signals and pin assignments for the
FrameSaver NAM’s 8-position communication port.
The following table shows the signals and pin assignments for the FrameSaver
9128 carrier-mounted unit’s 8-position communication port interface/connector.
Signal
Direction
Pin #
DCE Received Data ( RXD )
From DCE ( Out )
2
Signal Ground ( SG )
To/From DCE
3
DCE Transmit Data ( TXD )
To DCE ( In )
4
DCE Data Terminal Ready ( DTR )
To DCE ( In )
5
DCE Carrier Detect ( CD )
From DCE ( Out )
6
DCE Request to Send ( RTS )
To DCE ( In )
7
T1 TDM NAM’s Communication Port
The following table shows the signals and pin assignments for the
T1 TDM NAM’s 8-position communication port.
D-4
Signal
Direction
Pin #
DCE Transmit Clock ( TXC )
Out
1
DCE Received Data ( RXD )
Out
2
Signal Ground ( SG )
—
3
DCE Transmit Data ( TXD )
In
4
DCE Data Terminal Ready ( DTR )
In
5
DCE Carrier Detect ( CD )
Out
6
DCE Request to Send ( RTS )
In
7
DCE Received Clock ( RXC )
Out
8
DRAFT — June 1999
9191-A2-GH30-00
LAN Converter and Adapter Cable
A LAN adapter may be required when connecting a T1 TDM NAM to a LAN. The
following shows the pin assignments for the:
H
DB25 plug-to-modular jack converter between the COM port and the
8-conductor LAN Adapter cable and
H
Custom 8-conductor cable (with modular plugs on both ends) between the
converter and the LAN Adapter (3100-F2-910).
Plug-to-Modular
Jack Converter
Com Port
(DB25 Plug)
Cable
8-Position
Modular Jack
Plug to
Modular Jack
Plug to
LAN Adapter
Tx Clock 15
1
1
1 Unused
Rx Data
3
2
2
2 DTR
Signal Ground
7
3
3
3 Tx Data
Tx Data
2
4
4
4 Signal Ground
DTR 20
5
5
5 Rx Data
CD
8
6
6
6 CTS
RTS
4
7
7
7 Frame Ground
Rx Clock 17
8
8
8 Unused
98-16214
9191-A2-GH30-00
DRAFT — June 1999
D-5
COM Port-to-PC Cable (3100-F2-550)
This cable comes with the NextEDGE system.The following shows the
pin assignments from the COM port to the PC interface.
COM Port
Non-Keyed
8-Position
Modular Plug
DTE
DB9 Socket
Tx Clock
1
Rx Data
2
2
Rx Data
Ground
3
5
Ground
Tx Data
4
3
Tx Data
DTR
5
4
DTR
CD
6
1
CD
RTS
7
8
CTS
Rx Clock
8
6
DSR
7
RTS
No Connection
No Connection
496-14909
COM Port-to-Terminal Cable (3100-F2-540)
Order this cable when connecting the COM port to a terminal, or printer if a T1
TDM NAM, rather than to a PC; it does not come with the NextEDGE system.
The following shows the pin assignments from the COM port to the terminal or
printer interface.
COM Port
Non-Keyed
8-Position
Modular Plug
DTE
DB25 Plug
Tx Clock
1
15
Rx Data
2
3
Rx Data
Ground
3
7
Ground
Tx Data
4
2
Tx Data
DTR
5
20
DTR
CD
6
8
CD
RTS
7
5
CTS
Rx Clock
8
6
DSR
4
RTS
17
496-14910
D-6
DRAFT — June 1999
9191-A2-GH30-00
COM Port-to-Modem Cable
Order this cable when connecting a T1 TDM NAM’s COM port to a modem or
other external device. The following shows the pin assignments from the COM
port to the external device.
COM Port
Non-Keyed
8-Position
Modular Plug
No
Tx Clock 1
Connection
Rx Data 2
Modem
DB25 Plug
2
Tx Data
Signal Ground
3
7
Signal Ground
Tx Data
4
3
Rx Data
DTR
5
6
DSR
CD
6
4
RTS
RTS
7
Rx Clock
8
20 DTR
No
Connection
5
CTS
97-15669
Gender Adapter/Changer
When connecting the COM port to a router or Frame Relay Assembler/
Disassembler ( FRAD), a gender adapter is required to convert the
COM Port-to-Terminal cable’s plug-type interface to a socket-type interface
for the AUX port.
9191-A2-GH30-00
DRAFT — June 1999
D-7
DTE Port Connectors
FrameSaver NAM’s DTE Port Connectors
The following table provides the pin assignments for the FrameSaver NAM’s
34-position V.35 connector to the DTE.
Table O-1. V.35 DTE Port Connectors
D-8
Signal
ITU CT#
Direction
34-Pin
Socket
Shield
101
—
A
Signal Ground/Common
102
—
B
Request to Send ( RTS )
105
To DSU (In)
C
Clear to Send ( CTS )
106
From DSU (Out)
D
Data Set Ready ( DSR )
107
From DSU (Out)
E
Receive Line Signal Detector
( RLSD or LSD )
109
From DSU (Out)
F
Data Terminal Ready ( DTR )
108/1, /2
To DSU (In)
H
Local Loopback ( LL )
141
To DSU (In)
L
Transmit Data ( TXD )
103
To DSU (In)
P (A)
S (B)
Receive Data ( RXD )
104
From DSU (Out)
R (A)
T (B)
Transmit Signal Element Timing –
DTE Source ( XTXC or TT )
113
To DSU (In)
U (A)
W (B)
Receive Signal Element Timing –
DCE Source ( RXC )
115
From DSU (Out)
V (A)
X (B)
Transmit Signal Element Timing –
DCE Source ( TXC )
114
From DSU (Out)
Y (A)
AA ( B )
Test Mode Indicator ( TM )
142
From DSU (Out)
NN
DRAFT — June 1999
9191-A2-GH30-00
T1 TDM NAM’s DTE Port Connectors
The following table shows the EIA-530A circuit and pin assignments for the T1
TDM NAM’s data port connectors.
Table O-2. EIA-530A Port Connectors
9191-A2-GH30-00
Signal
Circuit
Mnemonic
ITU/
CCITT #
Direction
25-Pin
Pin #
Shield
—
—
—
1
Transmitted Data ( TXD )
BA
103
To DCE
2 (A)
14 (B)
Received Data ( RXD )
BB
104
From DCE
3 (A)
16 (B)
CA
105
To DCE
4 (A)
19 (B)
CB
106
From DCE
5 (A)
13 (B)
Data Set (or DCE ) Ready
( DSR )
CC
107
From DCE
6
Signal Ground/Common ( SG )
AB
102A
—
7
Received Line Signal Detector CF
( RLSD or LSD )
109
From DCE
8 (A)
10 (B)
Transmit Signal Element
Timing (TXC – DTE Source)
DA
113
To DCE
11 (B)
24 (A)
Transmitter Signal Element
Timing ( TXC – DCE Source)
DB
114
From DCE
12 (B)
15 (A)
Receiver Signal Element
Timing ( RXC – DCE Source )
DD
115
From DCE
17 (A)
9 (B)
LL
141
To DCE
18
Data Terminal (or DTE )
Ready ( DTR )
CD
108/1, /2
To DCE
20
Remote Loopback ( RL )
RL
140
To DCE
21
Signal Common
AC
102B
—
22, 23
TM
142
From DCE
25
DRAFT — June 1999
D-9
EIA-530A-to-V.35 DTE Adapter
This adapter is used as an interface between a 25-position EIA-530A
synchronous data port and a DTE’s V.35 connector.
99-16294
D-10
DRAFT — June 1999
9191-A2-GH30-00
The following table provides the pin assignments for the EIA-530A-to-V.35 DTE
adapter.
Table O-3. EIA-530A-to-V.35 DTE Adapter
9191-A2-GH30-00
Signal
ITU/
CCITT #
25-Pin
Plug
Pin #
Direction
34-Pin
Socket
Pin #
Shield
—
1
—
A
Transmit Data ( TXD )
103
2 (A)
14 ( B )
To DCE
P (A)
S (B)
104
3 (A)
16 ( B )
From DCE
R (A)
T (B)
105
4
To DCE
C
106
5
From DCE
D
Data Set (or DCE ) Ready ( DSR )
107
6
From DCE
E
102
7, 23
—
B
Data Channel Received Line
Signal Detector ( RLSD or LSD )
109
8
From DCE
F
Transmitter Signal Element/
Terminal Timing ( TT ) —
DTE Source
113
24 ( A )
11 ( B)
To DCE
U (A)
W (B)
Transmitter Signal Element Timing
( TXC ) — DCE Source
114
15 ( A )
12 ( B )
From DCE
Y (A)
AA ( B )
Receiver Signal Element Timing
( RXC ) — DCE Source
115
17 ( A )
9 (B)
From DCE
V (A)
X (B)
141
18
To DCE
L
Data Terminal (or DTE ) Ready
( DTR )
108/1, /2
20
To DCE
H
Loopback/Maintenance ( RL )
140
21
To DCE
N
142
25
From DCE
NN
DRAFT — June 1999
D-11
EIA-530A-to-RS-449 DTE Adapter Cable
This cable is used as an interface between a 25-position EIA-530A synchronous
data port and a DTE’s RS-449 connector.
The following table provides the pin assignments for the EIA-530A-to-RS-449
DTE adapter cable.
Table O-4. EIA-530A-to-RS-449 DTE Adapter Cable
D-12
Signal
25-Pin
Plug
ITU/
CCITT # Pin #
Direction
37-Pin
Socket
Pin #
Shield
—
1
—
1
Transmit Data ( TXD/ TD )
103
2 ( A ),
14 ( B )
To DCE
4 (A),
22 (B)
Receive Data ( RXD/ RD )
104
3 ( A ),
16 ( B )
From DCE
6 (A),
24 (B)
105
4 ( A ),
19 ( B )
To DCE
7 (A),
25 (B)
106
5 ( A ),
13 ( B )
From DCE
9 (A),
27 (B)
Data Set Ready/ Data Mode
( DSR/ DM )
107
6
From DCE
11 (A)
Signal Ground (SG)
102A
7
—
19
Signal Detect / Receiver Ready
( RLSD/ RR )
109
8 ( A ),
10 ( B )
From DCE
13 (A),
31 (B)
Timing/Transmit Timing ( TXC ) —
DCE Source
114
15 ( A ),
12 ( B )
From DCE
5 (A),
23 (B)
Receiver Signal Element Timing/
Receive Timing ( RXC ) —
DCE Source
115
17 ( A ),
9 (B)
From DCE
8 (A),
26 (B)
141
18
To DCE
10
Data Terminal (or DTE ) Ready
( DTR/ TR )
108/1, /2
20
To DCE
12 (A)
140
21
To DCE
14
Receive Common ( RC )
102B
23
—
20, 29
Transmitter Signal Element/
DTE Source
113
24 ( A ),
11 ( B )
To DCE
17 (A),
35 (B)
Test Mode ( TM )
142
25
From DCE
18
no connection
—
—
—
30, 37
DRAFT — June 1999
9191-A2-GH30-00
EIA-530A-to-X.21 DTE Adapter Cable
This cable is used as an interface between the 25-position EIA-530A
synchronous data port and a DTE’s X.21 connector.
The following table provides the pin assignments for the EIA-530A-to-X.21 DTE
adapter cable.
Table O-5. EIA-530A-to-X.21 DTE Adapter Cable
9191-A2-GH30-00
25-Pin
Plug
Pin #
15-Pin
Socket
Pin #
Signal
ITU/
CCITT #
Transmit Data ( TXD/ TD )
103
2 (A)
14 ( B )
To DCE
2 (A),
9 (B)
Received Data ( RXD/ RD )
104
3 (A)
16 ( B )
From DCE
4 (A),
11 (B)
105
4 (A)
19 ( B )
To DCE
3 (A),
10 (B)
Signal Ground/Common
102
7
—
8
Signal Detector/ Receiver Ready
( RLSD/ RR )
109
8 (A)
10 ( B )
From DCE
5 (A),
12 (B)
Receiver Signal Element Timing
( RXC ) — DCE Source
115
17 ( A )
9 (B)
From DCE
6 (A),
13 (B)
Transmitter Signal Element Timing/
DTE Source
113
24 ( A )
11 ( B )
To DCE
7 (A),
14 (B)
DRAFT — June 1999
Direction
D-13
Standard V.35 Straight-through Cable
A standard V.35 straight-through cable can be used to connect a DTE port to a
DTE, where a 34-pin plug-type connector is needed for the data port and a
34-position socket-type connector is needed for the DTE. No special-order cables
are required.
Standard V.35 Crossover Cable
A standard V.35 crossover cable with a 34-pin plug-type connector on each end
of the cable can be used to connect the NextEDGE system’s DTE port to another
DCE.
The following illustration provides the pin assignments for the V.35 crossover
cable.
A
C
A
B
C
D
LL
B
D
LL
KK
KK
MM
NN
MM
P1
Pin
TXD A P
TXD B S
RXD A R
RXD B
T
TXC A Y
TXC B AA
Z
RXC A V
RXC B X
ETXC A U
ETXC B W
FRM GND A
SIG GND B
RTS C
CD
F
DTR H
DSR E
LL
L
NN
P2
Pin
T
R
S
P
Z
AA
Y
W
U
X
V
A
B
F
C
E
H
L
98-16165a
D-14
DRAFT — June 1999
9191-A2-GH30-00
FrameSaver NAM’s DSX-1 Connector
The following table shows the signals and pin assignments for the 8-position
modular DSX-1 interface on the FrameSaver NAM. The DSX-1 Adapter is
required for this interface (see page D-15).
Function
Circuit
Direction
Pin Number
Receive Ring
R1
From DTE
1
Receive Tip
T1
From DTE
2
Shield
—
—
3
Transmit Ring
R
To DTE
4
Transmit Tip
T
To DTE
5
Shield
—
—
6
DSX-1 Adapter (9008-F1-560)
For FrameSaver NAMs, network access is via a 20-foot cable with an RJ48C
unkeyed plug-type connector on each end. The following table shows pin
assignments and the purpose of each.
The DSX-1 adapter cable is used as an interface between the FrameSaver
NAM’s DSX-1 connector and the DTE’s DB15 interface. The following shows
pin assignments and the purpose of each.
8-Position
Modular Plug
Unkeyed
Blue
Receive Ring 1
Receive Tip
2
Shield
3
Transmit Ring
4
Transmit Tip
5
Shield
6
White/Blue
Orange
White/Orange
DB15
Socket
Blue
White/Blue
Orange
White/Orange
9
Receive Ring
1
Receive Tip
4
Shield
11 Transmit Ring
3
Transmit Tip
2
Shield
99-16216a
9191-A2-GH30-00
DRAFT — June 1999
D-15
T1 TDM Nam’sDSX-1 Connector
The following table shows the signals and pin assignments for the DB15 DSX-1
interface.
Function
Circuit
Direction
Pin Number
Receive Tip
T1
From DTE
1
Transmit Tip
T
To DTE
3
Shield
—
—
2,4
Receive Ring
R1
From DTE
9
Transmit Ring
R
To DTE
11
Network Connector
T1 Line Interface Cable
RJ48C
Plug
Unkeyed
Blue
Receive Ring 1
Receive TIP
2
White/Blue
DA15P
Plug
Blue
White/Blue
11 Receive Ring
3
Receive TIP
9
Transmit Ring
1
Transmit TIP
3
Transmit Ring
4
Transmit TIP
5
Orange
White/Orange
Orange
White/Orange
6
7
493-14342-01
D-16
DRAFT — June 1999
9191-A2-GH30-00
T1 Network Cable (3100-F1-500)
Network access to both the FrameSaver and T1 TDM NAMs is via a 20-foot cable
with an RJ48C unkeyed plug-type connector on each end. The following table
shows pin assignments and the purpose of each.
Function
Circuit
Direction
Pin Number
Receive Ring
R1
From Network
1
Receive Tip
T1
From Network
2
Transmit Ring
R
To Network
4
Transmit Tip
T
To Network
5
Canadian T1 Line Interface Cable (3100-F1-510)
The T1 line interface cable is used in Canada as an interface between the
FrameSaver NAM’s network connector and the T1 network interface. The
following diagram shows pin assignments and the purpose of each.
RJ48C
Plug
Unkeyed
Blue
Receive Ring 1
Receive Tip
2
White/Blue
DA15P
Plug
Blue
White/Blue
11 Receive Ring
3
Receive Tip
9
Transmit Ring
1
Transmit Tip
3
Transmit Ring
4
Transmit Tip
5
Orange
White/Orange
Orange
White/Orange
6
7
98-16215
9191-A2-GH30-00
DRAFT — June 1999
D-17
T1 Mass Termination Cable (907-F1-500)
A T1 mass termination cable is available to connect up to seven T1 TDM NAMs
mounted in a 9000 Series Access Carrier to an M66 block. The T1 mass
termination cable is a 5-foot RJ48H cable consisting of a 50-pin plug at one end
and seven RJ48C plugs at the other end.
Function
Circuit Line # Pin #
Function
Circuit Line # Pin #
Receive ring
from the
network
R1
Transmit ring to
the network
R
Receive tip
from the
network
D-18
T1
1
1
1
14
2
2
2
15
3
3
3
16
4
4
4
17
5
5
5
18
6
6
6
19
7
7
7
20
1
26
1
39
2
27
2
40
3
28
3
41
4
29
4
42
5
30
5
43
6
31
6
44
7
32
7
45
DRAFT — June 1999
Transmit tip to
the network
T
9191-A2-GH30-00
FrameSaver NAM’s Modem Connector
The dial modem interface/connector that is integrated into the FrameSaver NAM
is an RJ11 6-position, 4-contact unkeyed modular jack. The following table shows
pin assignments and the purpose of each.
Function
Circuit
Direction
Pin Number
Ring
R
To Local Loop
2
Tip
T
To Local Loop
3
FrameSaver NAM’s ISDN DBM Connector
The backup connection is through the DBM interface/connector, which is an
8-position keyed modular jack. The following tables show pin assignments for the
ISDN PRI and BRI DBMs, and the purpose of each.
ISDN PRI DBM pin assignments:
Function
Circuit
Direction
Pin Number
PRI Receive Ring
DBM1
From Local Loop
1
PRI Receive Tip
DBM2
From Local Loop
2
PRI Transmit Ring
DBM4
To Local Loop
4
PRI Transmit Tip
DBM5
To Local Loop
5
Function
Circuit
Direction
Pin Number
BRI Transmit/Receive Ring
DBM4
To/From
Local Loop
4
BRI Transmit/Receive Tip
DBM5
To/From
Local Loop
5
ISDN BRI/U DBM pin assignments:
9191-A2-GH30-00
DRAFT — June 1999
D-19
Synchronous Data APM Connectors
The following table shows the EIA-530A circuit and pin assignments for the
synchronous data APM.
Table O-6. EIA-530A Synchronous Data Port Connectors
D-20
Signal
Circuit
Mnemonic
ITU/
CCITT #
Direction
25-Pin
Pin #
Shield
—
—
—
1
Transmitted Data ( TXD )
BA
103
To DCE
2 (A)
14 (B)
BB
104
From DCE
3 (A)
16 (B)
CA
105
To DCE
4 (A)
19 (B)
CB
106
From DCE
5 (A)
13 (B)
Data Set (or DCE ) Ready
( DSR )
CC
107
From DCE
6
AB
102A
—
7
Received Line Signal Detector CF
( RLSD or LSD )
109
From DCE
8 (A)
10 (B)
Transmit Signal Element
Timing (TXC – DTE Source)
DA
113
To DCE
11 (B)
24 (A)
Timing ( TXC – DCE Source)
DB
114
From DCE
12 (B)
15 (A)
Receiver Signal Element
Timing ( RXC – DCE Source )
DD
115
From DCE
17 (A)
9 (B)
LL
141
To DCE
18
Data Terminal (or DTE )
Ready ( DTR )
CD
108/1, /2
To DCE
20
RL
140
To DCE
21
Signal Common
AC
102B
—
22, 23
TM
142
From DCE
25
DRAFT — June 1999
9191-A2-GH30-00
Voice APM Connectors
This section provides the pin assignments for the FXO, FXS and E&M voice APM
50-pin Amphenol connectors (RJ27X socket), followed by the pin assignments for
the extension cables that can be used with these APMs.
FXO/FXS Voice APM Connector
The FXO/FXS Analog Voice APM uses a single 50-pin connector to provide eight
2-wire interfaces for connecting to analog voice equipment.
FXO/FXS 50-Pin Amphenol Connector
Port
Pin
Signal
1
26
T
1
R
29
T
4
R
32
T
7
R
35
T
10
R
38
T
13
R
41
T
16
R
44
T
19
R
47
T
22
R
2
3
4
5
6
7
8
1
9191-A2-GH30-00
All other pins are unconnected.
DRAFT — June 1999
D-21
E&M Voice APM Connector
The E&M Analog Voice APM uses a single 50-pin connector (RJ27X socket) to
provide eight 2-wire interfaces for connecting to analog voice equipment.
E&M 50-Pin Amphenol Connector (1 of 2)
Port
Pin
Function
Signal
1
26
Transmit tip
T
1
Transmit ring
R
27
Receive tip
T1
2
Receive ring
R1
28
E Lead
E
3
M Lead
M
29
Transmit tip
T
4
Transmit ring
R
30
Receive tip
T1
5
Receive ring
R1
31
E Lead
E
6
M Lead
M
32
Transmit tip
T
7
Transmit ring
R
33
Receive tip
T1
8
Receive ring
R1
34
E Lead
E
9
M Lead
M
35
Transmit tip
T
10
Transmit ring
R
36
Receive tip
T1
11
Receive ring
R1
37
E Lead
E
12
M Lead
M
2
3
4
D-22
DRAFT — June 1999
9191-A2-GH30-00
E&M 50-Pin Amphenol Connector (2 of 2)
Port
Pin
Function
Signal
5
38
Transmit tip
T
13
Transmit ring
R
39
Receive tip
T1
14
Receive ring
R1
40
E Lead
E
15
M Lead
M
41
Transmit tip
T
16
Transmit ring
R
42
Receive tip
T1
17
Receive ring
R1
43
E Lead
E
18
M Lead
M
44
Transmit tip
T
19
Transmit ring
R
45
Receive tip
T1
20
Receive ring
R1
46
E Lead
E
21
M Lead
M
47
Transmit tip
T
22
Transmit ring
R
48
Receive tip
T1
23
Receive ring
R1
49
E Lead
E
24
M Lead
M
25
Signal Ground
SG
50
Signal Battery
SB
6
7
8
All
9191-A2-GH30-00
DRAFT — June 1999
D-23
APM Extension Cables
Extension cables can be ordered for use with the 50-pin FXO, FXS and E&M
Voice APM connectors. They are all straight-through cables (i.e., Pin 1 on the
voice APM side is Pin 1 on the M66 block side of the cable), and they coincide
with the pins on the 50-pin APM connector.
The following table identifies these cables, indicates the voice APM it is used
with, and describes when you might use each:
Extension Cables
Extension Cable
Length Voice APM When Used
1 Amphenol plug-to1 Amphenol plug
cable
3′
E&M
FXO
FXS
(Twisted pair/25-pair:
1-26, 2-27, 3-28 . . .
25-50)
When the M66 block is further than five
feet from the APM connector, used as an
extension to the 5-foot cable normally
used.
See FXO/FXS Voice APM Connector on
Page D-21 or E&M Voice APM
Connector on Page D-22 for pin
assignments.
(9008-F1-531)
1 Amphenol socketto-1 Amphenol plug
cable
25′
E&M
FXO
FXS
(Twisted pair/25-pair:
1-26, 2-27, 2-28 . . .
25-50)
3 Amphenol plugs-to- 6′
1 Amphenol plug
connector assembly
When the M66 block is further than five
feet from the APM’s connector, used as
an extension to the 5-foot 1 Amphenol
plug-to-1 Amphenol plug cable.
See FXO/FXS Voice APM Connector on
Page D-21 or E&M Voice APM
Connector on Page D-22 for pin
assignments.
(9008-F1-532)
FXO
FXS
To condense three voice APMs onto the
single M66 block connector.
Extend the cable using the 25-foot
1 Amphenol socket-to-1 Amphenol
plug 25-pair cable.
(Twisted pair: T1-R1
. . .T24-R24, S1-S2)
(9008-F1-534)
See 3 Amphenol Plugs-to-1 Amphenol
Plug Cable on Page D-26 for pin
assignments.
3 Amphenol plugs-to- 6′
4 Amphenol plugs
connector assembly
E&M
(Twisted pair: T1-R1
. . .T24-R24,
TR1-RR1 . . .
TR24-RR24,
M1-E1 . . . M24-E24,
SG1-SG1 . . .
SG3-SG3)
(9008-F1-533)
D-24
To connect the voice APM’s 50-pin
Amphenol connector to the M66 block.
To consolidate signals from three voice
APMs and segregate four applications
onto four M66 blocks (e.g., all transmit
signals on one block, all receive signals
on a second block, all E&M signals on a
third, and all battery and signal ground
signals on the fourth).
Extend the cable using the 25-foot
1 Amphenol socket-to-1 Amphenol
plug 25-pair cable.
See 3 Amphenol Plugs-to-4 Amphenol
Plugs Cable starting on Page E-19 for
pin assignments.
DRAFT — June 1999
9191-A2-GH30-00
3 Amphenol Plugs-to-1 Amphenol Plug Cable
M66 Block
Voice APMs
P3
P2
P1
P4
97-15171-02
9191-A2-GH30-00
DRAFT — June 1999
D-25
3 Amphenol Plugs-to-1 Amphenol Plug Cable
M66
Plug Pin
Connects
to APM
Pin
Plug
Signal
M66
Plug Pin
Connects
to APM
Pin
Plug
Signal
P4
P1
1
R Port 1
P4
P1
26
T Port 1
2
4
R Port 2
27
29
T Port 2
3
7
R Port 3
28
32
T Port 3
4
10
R Port 4
29
35
T Port 4
5
13
R Port 5
30
38
T Port 5
6
16
R Port 6
31
41
T Port 6
7
19
R Port 7
32
44
T Port 7
22
R Port 8
33
47
T Port 8
1
8
9
P2
1
R Port 1
34
26
T Port 1
10
4
R Port 2
35
29
T Port 2
11
7
R Port 3
36
32
T Port 3
12
10
R Port 4
37
35
T Port 4
13
13
R Port 5
38
38
T Port 5
14
16
R Port 6
39
41
T Port 6
15
19
R Port 7
40
44
T Port 7
16
22
R Port 8
41
47
T Port 8
1
R Port 1
42
26
T Port 1
18
4
R Port 2
43
29
T Port 2
19
7
R Port 3
44
32
T Port 3
20
10
R Port 4
45
35
T Port 4
21
13
R Port 5
46
38
T Port 5
22
16
R Port 6
47
41
T Port 6
23
19
R Port 7
48
44
T Port 7
24
22
R Port 8
49
47
T Port 8
–
–
50
–
–
17
25
D-26
P2
26
P3
–
DRAFT — June 1999
P3
–
9191-A2-GH30-00
3 Amphenol Plugs-to-4 Amphenol Plugs Cable
M66 Blocks
TX
RX
E&M
Signal Ground
and Battery
Voice APMs
P3
P2
P1
P4
P5
P6
P7
97-15172-02
9191-A2-GH30-00
DRAFT — June 1999
D-27
3 Amphenol Plugs-to-4 Amphenol Plugs Cable for P1 (1 of 2)
D-28
P1 Pin #
Designation
Connects To Pin #
Designation
Function
1
R (Port 1)
P4
1
R (Port 1)
Transmit Ring
2
R1 (Port 1)
P5
1
R1 (Port1)
Receive Ring
3
M (Port 1)
P6
1
M (Port 1)
M Lead
4
R (Port 2)
P4
2
R (Port 2)
Transmit Ring
5
R1 (Port 2)
P5
2
R1 (Port 2)
Receive Ring
6
M1 (Port 2)
P6
2
M (Port 2)
M Lead
7
R (Port 3)
P4
3
R (Port 3)
Transmit Ring
8
R1 (Port 3)
P5
3
R1 (Port 3)
Receive Ring
9
M (Port 3)
P6
3
M (Port 3)
M Lead
10
R (Port 4)
P4
4
R (Port 4)
Transmit Ring
11
R1 (Port 4)
P5
4
R1 (Port 4)
Receive Ring
12
M (Port 4)
P6
4
M (Port 4)
M Lead
13
R (Port 5)
P4
5
R (Port 5)
Transmit Ring
14
R1 (Port 5)
P5
5
R1 (Port 5)
Receive Ring
15
M (Port 5)
P6
5
M (Port 5)
M Lead
16
R (Port 6)
P4
6
R (Port 6)
Transmit Ring
17
R1 (Port 6)
P5
6
R1 (Port 6)
Receive Ring
18
M (Port 6)
P6
6
M (Port 6)
M Lead
19
R (Port 7)
P4
7
R (Port 7)
Transmit Ring
20
R1 (Port 7)
P5
7
R1 (Port 7)
Receive Ring
21
M (Port 7)
P6
7
M (Port 7)
M Lead
22
R (Port 8)
P4
8
R (Port 8)
Transmit Ring
23
R1 (Port 8)
P5
8
R1 (Port 8)
Receive Ring
24
M (Port 8)
P6
8
M (Port 8)
M Lead
25
SG
(Ports 1–8)
P7
1–8
SG
(Ports 1–8)
Signal Ground
DRAFT — June 1999
9191-A2-GH30-00
9191-A2-GH30-00
P1 Pin #
Designation
Connects To Pin #
Designation
Function
26
T (Port 1)
P4
26
T (Port 1)
Transmit Tip
27
T1 (Port 1)
P5
26
T1 (Port 1)
Receive Tip
28
E (Port 1)
P6
26
E (Port 1)
E Lead
29
T (Port 2)
P4
27
T (Port 2)
Transmit Tip
30
T1 (Port 2)
P5
27
T1 (Port 2)
Receive Tip
31
E (Port 2)
P6
27
E (Port 2)
E Lead
32
T (Port 3)
P4
28
T (Port 3)
Transmit Tip
33
T1 (Port 3)
P5
28
T1 (Port 3)
Receive Tip
34
E (Port 3)
P6
28
E (Port 3)
E Lead
35
T (Port 4)
P4
29
T (Port 4)
Transmit Tip
36
T1 (Port 4)
P5
29
T1 (Port 4)
Receive Tip
37
E (Port 4)
P6
29
E (Port 4)
E Lead
38
T (Port 5)
P4
30
T (Port 5)
Transmit Tip
39
T1 (Port 5)
P5
30
T1 (Port 5)
Receive Tip
40
E (Port 5)
P6
30
E (Port 5)
E Lead
41
T (Port 6)
P4
31
T (Port 6)
Transmit Tip
42
T1 (Port 6)
P5
31
T1 (Port 6)
Receive Tip
43
E (Port 6)
P6
31
E (Port 6)
E Lead
44
T (Port 7)
P4
32
T (Port 7)
Transmit Tip
45
T1 (Port 7)
P5
32
T1 (Port 7)
Receive Tip
46
E (Port 7)
P6
32
E (Port 7)
E Lead
47
T (Port 8)
P4
33
T (Port 8)
Transmit Tip
48
T1 (Port 8)
P5
33
T1 (Port 8)
Receive Tip
49
E (Port 8)
P6
33
E (Port 8)
E Lead
50
SB
(Ports 1–8)
P7
26–33
SB
(Ports 1–8)
Signal Battery
DRAFT — June 1999
D-29
D-30
P2 Pin #
Designation
Connects To Pin #
Designation
Function
1
R (Port 1)
P4
9
R (Port 9)
Transmit Ring
2
R1 (Port 1)
P5
9
R1 (Port 9)
Receive Ring
3
M (Port 1)
P6
9
M (Port 9)
M Lead
4
R (Port 2)
P4
10
R (Port 10)
Transmit Ring
5
R1 (Port 2)
P5
10
R1 (Port 10)
Receive Ring
6
M (Port 2)
P6
10
M (Port 10)
M Lead
7
R (Port 3)
P4
11
R (Port 11)
Transmit Ring
8
R1 (Port 3)
P5
11
R1 (Port 11)
Receive Ring
9
M (Port 3)
P6
11
M (Port 11)
M Lead
10
R (Port 4)
P4
12
R (Port 12)
Transmit Ring
11
R1 (Port 4)
P5
12
R1 (Port 12)
Receive Ring
12
M (Port 4)
P6
12
M (Port 12)
M Lead
13
R (Port 5)
P4
13
R (Port 13)
Transmit Ring
14
R1 (Port 5)
P5
13
R1 (Port 13)
Receive Ring
15
M (Port 5)
P6
13
M (Port 13)
M Lead
16
R (Port 6)
P4
14
R (Port 14)
Transmit Ring
17
R1 (Port 6)
P5
14
R1 (Port 14)
Receive Ring
18
M (Port 6)
P6
14
M (Port 14)
M Lead
19
R (Port 7)
P4
15
R (Port 15)
Transmit Ring
20
R1 (Port 7)
P5
15
R1 (Port 15)
Receive Ring
21
M (Port 7)
P6
15
M (Port 15)
M Lead
22
R (Port 8)
P4
16
R (Port 16)
Transmit Ring
23
R1 (Port 8)
P5
16
R1 (Port 16)
Receive Ring
24
M (Port 8)
P6
16
M (Port 16)
M Lead
25
SG
(Ports 1–8)
P7
9–16
SG
(Ports 9–16)
Signal Ground
DRAFT — June 1999
9191-A2-GH30-00
9191-A2-GH30-00
P2 Pin #
Designation
Connects To Pin #
Designation
Function
26
T (Port 1)
P4
34
T (Port 9)
Transmit Tip
27
T1 (Port 1)
P5
34
T1 (Port 9)
Receive Tip
28
E (Port 1)
P6
34
E (Port 9)
E Lead
29
T (Port 1)
P4
35
T (Port 10)
Transmit Tip
30
T1 (Port 1)
P5
35
T1 (Port 10)
Receive Tip
31
E (Port 1)
P6
35
E (Port 10)
E Lead
32
T (Port 1)
P4
36
T (Port 11)
Transmit Tip
33
T1 (Port 1)
P5
36
T1 (Port 11)
Receive Tip
34
E (Port 1)
P6
36
E (Port 11)
E Lead
35
T (Port 1)
P4
37
T (Port 12)
Transmit Tip
36
T1 (Port 1)
P5
37
T1 (Port 12)
Receive Tip
37
E (Port 1)
P6
37
E (Port 12)
E Lead
38
T (Port 1)
P4
38
T (Port 13)
Transmit Tip
39
T1 (Port 1)
P5
38
T1 (Port 13)
Receive Tip
40
E (Port 1)
P6
38
E (Port 13)
E Lead
41
T (Port 1)
P4
39
T (Port 14)
Transmit Tip
42
T1 (Port 1)
P5
39
T1 (Port 14)
Receive Tip
43
E (Port 1)
P6
39
E (Port 14)
E Lead
44
T (Port 1)
P4
40
T (Port 15)
Transmit Tip
45
T1 (Port 1)
P5
40
T1 (Port 15)
Receive Tip
46
E (Port 1)
P6
40
E (Port 15)
E Lead
47
T (Port 1)
P4
41
T (Port 16)
Transmit Tip
48
T1 (Port 1)
P5
41
T1 (Port 16)
Receive Tip
49
E (Port 1)
P6
41
E (Port 16)
E Lead
50
SB
(Ports 1–8)
P7
34–41
SB
(Ports 9–16)
Signal Battery
DRAFT — June 1999
D-31
D-32
P3 Pin #
Designation
Connects To Pin #
Designation
Function
1
R (Port 1)
P4
17
R (Port 17)
Transmit Ring
2
R1 (Port 1)
P5
17
R1 (Port 17)
Receive Ring
3
M (Port 1)
P6
17
M (Port 17)
M Lead
4
R (Port 2)
P4
18
R (Port 18)
Transmit Ring
5
R1 (Port 2)
P5
18
R1 (Port 18)
Receive Ring
6
M (Port 2)
P6
18
M (Port 18)
M Lead
7
R (Port 3)
P4
19
R (Port 19)
Transmit Ring
8
R1 (Port 3)
P5
19
R1 (Port 19)
Receive Ring
9
M (Port 3)
P6
19
M (Port 19)
M Lead
10
R (Port 4)
P4
20
R (Port 20)
Transmit Ring
11
R1 (Port 4)
P5
20
R1 (Port 20)
Receive Ring
12
M (Port 4)
P6
20
M (Port 20)
M Lead
13
R (Port 5)
P4
21
R (Port 21)
Transmit Ring
14
R1 (Port 5)
P5
21
R1 (Port 21)
Receive Ring
15
M (Port 5)
P6
21
M (Port 21)
M Lead
16
R (Port 6)
P4
22
T (Port 22)
Transmit Ring
17
R1 (Port 6)
P5
22
R1 (Port 22)
Receive Ring
18
M (Port 6)
P6
22
M (Port 22)
M Lead
19
R (Port 7)
P4
23
R (Port 23)
Transmit Ring
20
R1 (Port 7)
P5
23
R1 (Port 23)
Receive Ring
21
M (Port 7)
P6
23
M (Port 23)
M Lead
22
R (Port 8)
P4
24
R (Port 24)
Transmit Ring
23
R1 (Port 8)
P5
24
R1 (Port 24)
Receive Ring
24
M (Port 8)
P6
25
M (Port 24)
M Lead
25
SG
(Ports 1–8)
P7
17–24
SG
(Port 17–24)
Signal Ground
DRAFT — June 1999
9191-A2-GH30-00
9191-A2-GH30-00
P3 Pin #
Designation
Connects To Pin #
Designation
Function
26
T (Port 1)
P4
42
T (Port 17)
Transmit Tip
27
T1 (Port 1)
P5
42
T1 (Port 17)
Receive Tip
28
E (Port 1)
P6
42
E (Port 17)
E Lead
29
T (Port 2)
P4
43
T (Port 18)
Transmit Tip
30
T1 (Port 2)
P5
43
T1 (Port 18)
Receive Tip
31
E (Port 2)
P6
43
E (Port 18)
E Lead
32
T (Port 3)
P4
44
T (Port 19)
Transmit Tip
33
T1 (Port 3)
P5
44
T1 (Port 19)
Receive Tip
34
E (Port 3)
P6
44
E (Port 19)
E Lead
35
T (Port 4)
P4
45
T (Port 20)
Transmit Tip
36
T1 (Port 4)
P5
45
T1 (Port 20)
Receive Tip
37
E (Port 4)
P6
45
E (Port 20)
E Lead
38
T (Port 5)
P4
46
T (Port 21)
Transmit Tip
39
T1 (Port 5)
P5
46
T1 (Port 21)
Receive Tip
40
E (Port 5)
P6
46
E (Port 21)
E Lead
41
T (Port 6)
P4
47
T (Port 22)
Transmit Tip
42
T1 (Port 6)
P5
47
T1 (Port 22)
Receive Tip
43
E (Port 6)
P6
47
E (Port 22)
E Lead
44
T (Port 7)
P4
48
T (Port 23)
Transmit Tip
45
T1 (Port 7)
P5
48
T1 (Port 23)
Receive Tip
46
E (Port 7)
P6
48
E (Port 23)
E Lead
47
T (Port 8)
P4
49
T (Port 24)
Transmit Tip
48
T1 (Port 8)
P5
49
T1 (Port 24)
Receive Tip
49
E (Port 8)
P6
49
E (Port 24)
E Lead
50
SB
(Ports 1– 8)
P7
42–49
SB
(Ports 17– 24)
Signal Battery
DRAFT — June 1999
D-33
OCU Ports
The OCU-DP APM can have either two or six ports, each port having an RJ48S
connector. Connect the OCU port to the DDS network using one of the following
cables:
H
14-foot DDS cable (3600-F3-501)
H
25-foot DDS cable (3600-F3-502)
OCU Port Connectors
The OCU-DP port is a USOC RJ48S connector. The following table shows pin
assignments and the purpose of each.
D-34
Function
Circuit
Pin #
Transmit ring
R
1
Transmit tip
T
2
Receive tip
T1
7
Receive ring
R1
8
DRAFT — June 1999
9191-A2-GH30-00
9191-A2-GH30-00
DRAFT — June 1999
D-35
E
The following technical specifications are included:
H
2-Slot Housing Technical Specifications on page E-2.
H
5-Slot Housing Technical Specifications on page E-3.
H
NextEDGE System Technical Specifications on page E-4.
— For the System and All Optional Features on page E-4.
— FrameSaver SLV NAM and I/O Card on page E-5.
— T1 TDM NAM and I/O Card on page E-6.
H
APM Technical Specifications on page E-7.
— Synchronous Data APM on page E-7.
— Dual DSX APM on page E-7.
— Voice APMs on page E-8.
— OCU-DP APM on page E-9.
H
ISDN DBM Technical Specifications on page E-10.
— ISDN BRI DBM on page E-10.
— ISDN PRI DBM on page E-11.
9191-A2-GH30-00
DRAFT — June 1999
E-1
2-Slot Housing Technical Specifications (1 of 1)
Criteria
Specification
Physical Dimensions
Height
11.0 inches (27.95 cm)
Width
4.3 inches (10.80 cm)
Depth
14.8 inches (37.48 cm)
Weight
Empty housing (includes
power supply)
11 lbs. 2 oz. (5.05 kg)
Heat Dissipation (Max.) at
115 Vac
Fully loaded housing
145 Btu per hour
Power Requirements
115 volts
E-2
90 to 132 Vac, 60 Hz 3, 0.5 amps
DRAFT — June 1999
9191-A2-GH30-00
5-Slot Housing Technical Specifications (1 of 1)
Criteria
Specification
Physical Dimensions
Height
Desktop
Rack-mount
11.9 inches (30.23 cm)
10.5 inches (26.67 cm)
Width
Desktop
Rack-mount
8.8 inches (22.35 cm)
8.2 inches (20.83 cm)
Depth
Desktop
Rack-mount
15.6 inches (39.63 cm)
14.3 inches (36.32 cm)
Weight
Empty housing
(without power supply)
11 lbs. 6 oz. (5.15 kg)
Heat Dissipation (Max.) at
115 Vac
Fully loaded housing
360 Btu per hour maximum
Power Requirements
AC
90 to 132 Vac, 60 Hz3, 1.5 amps maximum
DC
+24 Vdc
– 48 Vdc
Operating Voltage
For negative input voltages:
Power supply disabled: Voltage < |38.5 1 Vdc|
Power supply enabled: Voltage > |43 0.5 Vdc|
4.85 amps
2.35 amps
116 watts
113 watts
For positive input voltages:
Power supply disabled: Voltage <16.5 Vdc nominal
Power supply enabled: Voltage +20 Vdc to +30 Vdc
Approximately 2 volts hysteresis between turn-on
and turn-off voltage.
9191-A2-GH30-00
DRAFT — June 1999
E-3
NextEDGE System Technical Specifications (1 of 3)
Criteria
Specification
For the System and All Optional Features
Approvals
FCC Part 15
Class A digital device
FCC Part 68
Refer to the equipment’s label for the
Registration Number.
Industry Canada
Refer to the equipment’s label for the
Certification Number.
Safety
Refer to the equipment’s label for safety information.
Physical Environment
Operating temperature
32° F to 122° F ( 0° C to 50° C )
Storage temperature
– 4° F to 158° F (– 20° C to 70° C )
Relative humidity
5% to 85% ( noncondensing )
Shock and vibration
Withstands normal shipping and handling
Physical Dimensions
NAM or APM Card
Height
8 inches (20.32 cm)
Depth
11.58 inches (29.41 cm)
I/O Card
Height
10.15 inches (25.78 cm)
Depth
2.9 inches (7.37 cm)
Weight
NAM
1 lb. 2 oz. ( .51 kg )
I/O Card
6 oz. (.17 kg)
FrameSaver SLV NAM and I/O Card
E-4
Power Consumption and
Dissipation
9.5 watts, 0.080 A at 120 Vac
Result: 32 Btu per hour
T1 Network Interface
8-position modular unkeyed USOC RJ48C jack
Data rates
Up to 1.536 Mbps
Services supported
Fractional T1 service, frame relay service
Physical interface (USA)
RJ48C
Physical interface (Canada)
CA81A using adapter cable
Framing format
D4, ESF
Coding format
AMI, B8ZS
Line Build-Out (LBO)
0.0 dB, –7.5 dB, –15 dB, –22.5 dB
ANSI PRM
Selectable
Bit stuffing
AT&T TR 62411
DRAFT — June 1999
9191-A2-GH30-00
Specification
Criteria
FrameSaver NAM and I/O Card (cont’d)
DSX-1 Interface
8-position modular unkeyed jack
Physical interface
D4, ESF
Framing format
AMI, B8ZS
Coding format
DTE line equalization
5 selectable ranges from 0 to 655 feet
(0 to196.5 meters)
Selectable
Send AIS
COM Port –
Communications/Management
8-position modular jack unkeyed
Standard
EIA-232/ ITU, V.24 (ISO 2110)
Data rates
9.6, 14.4, 19.2, 28.8, 38.4, 57.6, and 115.2 kbps
DTE Ports
34-position V.35 connector
Standard
V.35/ ITU (ISO 2593)
Data rates
Variations for T1 rates;
automatically set to the network rate.
ISDN BRI DBM Interface
One 8-position modular keyed USOC RJ49C jack
Physical interface
RJ49C
Service supported
BRI, NI-1
Data rates
56 kbps and 64 kbps
ISDN PRI DBM Interface
One 8-position modular unkeyed USOC RJ48C jack
Physical interface
RJ48C
Service supported
PRI, NI-1 or NI-2
Data rates
1.536 Kbps
Framing format
D4, ESF
Coding format
B8ZS
0.0 dB, –7.5 dB, –15 dB, –22.5 dB
ANSI PRM
Selectable
Modem (MDM) Interface
Data rates
Up to 14.4 Kbps
Link Protocol
PPP, SLIP
Loopbacks
Standard
Network Line Loopback, Network Payload Loopback,
V.54 Loop 2 (DCLB) and V.54 Loop 3 (DTPLB)
Additional
Network Repeater Loopback, DTE Loopback
DSX-1 Line Loopback, DSX-1 Payload Loopback, and
DSX-1 Repeater Loopback
9191-A2-GH30-00
DRAFT — June 1999
E-5
Specification
Criteria
T1 TDM NAM and I/O Card
Power Consumption
9.4 watts, 0.78 amps input current at 12 volts
Result: 32.07 Btu per hour
T1 Network 1/2 Interface
Data rates
Up to 1.536 Mbps
Services supported
Fractional T1 service, frame relay service
Physical interface (USA)
RJ48C
Physical interface (Canada)
CA81A using adapter cable
Framing format
D4, ESF
Coding format
AMI, B8ZS
0.0 dB, –7.5 dB, –15 dB, –22.5 dB
ANSI PRM
Selectable
Bit stuffing
AT&T TR 62411
Yellow Alarm Generation
Selectable
DSX-1 Interface (9161 only)
Physical Interface
DB15 socket
Framing Format
D4, ESF
Coding Format
AMI, B8ZS
DTE Line Equalization
(0 to 196.5 meters)
Send AIS
Selectable
DTE Ports
Standards
EIA-530A, V.35, RS-449, V.11, X.21
Rates
Nx64 – 64K to 1.536 Mb
Nx56 – 56K to 1.344 Mb
COM Port
Data Rates
9.6, 14.4, 19.2, 28.8, 38.4 , 57.6, and 115.2 kbps.
57.6 and 115.2 kbps are recommended for FTP
download only.
Clocking Sources
T1 network interface (1 or 2), any port, internal clock,
DSX-1 T1 interface (9161 only), or external clock
Loopbacks
E-6
Standard
Network Line Loopback, Network Payload Loopback,
Additional
Network Repeater Loopback, DTE Loopback
For 9161 Only
DSX-1 Line Loopback, DSX-1 Payload Loopback, and
DSX-1 Repeater Loopback
DRAFT — June 1999
9191-A2-GH30-00
APM Technical Specifications (1 of 3)
Specification
Criteria
Synchronous Data APM
Weight
Sync Data APM
15 oz. (.425 kg)
Sync Data I/O card
6 oz. (.170 kg)
Size
Sync Data APM
11.58 inches x 8.00 inches (29.41 cm x 20.32 cm)
Sync Data I/O card
Power Consumption
DTE Ports
Standards
EIA-530A, V.35, RS-449, V.11, X.21
Rates
Nx64 – 64K to 1.536 Mb
Nx56 – 56K to 1.344 Mb
Loopbacks
Standard
Additional
DTE Loopback
Dual DSX APM
Weight
DSX APM
15 oz. (.425 kg)
DSX I/O card
6 oz. (.170 kg)
Size
9191-A2-GH30-00
DSX APM
11.58″ x 8.00″ (29.41 cm x 20.32 cm)
DSX I/O card
2.90″ x 10.15″ (7.37 cm x 25.78 cm)
Power Consumption
DSX-1 Interfaces
15-position (DB15) subminiature connector
Physical Interface
DB15 socket
Framing Format
D4, ESF
Coding Format
AMI, B8ZS
DTE Line Equalization
(0 to 196.5 meters)
Send AIS
Selectable
DRAFT — June 1999
E-7
Specification
Criteria
Voice APMs
Weight
E&M APM
14 oz. (.397 kg)
FXO APM
1 lb. (.454 kg)
FXS APM
1 lb. (.454 kg)
Voice I/O card
6 oz. (.170 kg)
Size
E&M/FXO/FXS APM
Voice I/O card
Cable Length (Max.)
18,000 feet using 26 AWG
Power Consumption
E&M APM
FXO APM
FXS APM (8 lines talking)
FXS APM (8 lines ringing)
Interface Connector
50-pin amphenol connector (RJ27X)
Operating Modes
E-8
E&M
E&M
Transmit Only
FXO
DPT
FXO
FXO DN
FXO DN Wink
FXS
DPO
FXS
FXS DN
FXS DN Wink
PLAR
DRAFT — June 1999
9191-A2-GH30-00
Specification
Criteria
Voice APMs (cont’d)
Signaling Types
E&M
Type I
Type II
Type IV
Type V
FXO
Loop Start
Loop Start/Forward Disconnect
Ground Start
FXS
Loop Start
Loop Start/Forward Disconnect
Ground Start
Ground Start Immediate
Ground Start Automatic
PLAR D3
PLAR D4
OCU-DP APM
Weight
2-port OCU-DP APM
0.800 lbs. (.362 kg)
6-port OCU-DP APM
1.052 lbs. (.477 kg)
OCU-DP I/O card
0.286 lbs. (.130 kg)
Size
OCU-DP APM
OCU-DP I/O card
Power Consumption (max)
2-Port OCU
6-Port OCU
DDS Ports
9191-A2-GH30-00
Standards
AT&T PUB 62310, Bellcore TA-TSY-00077, ANSI
T1.410, AT&T PUB 61330, AT&T TR41458
Rates
56 kbps, 64 kbps Clear Channel, 4-wire Switched 56
Loopbacks
DS-0, OCU Line, OCU Data, OCU, Local and Remote
Latching and Non-Latching DSU/CSU
DRAFT — June 1999
E-9
ISDN DBM Technical Specifications (1 of 2)
Criteria
Specification
ISDN BRI DBM
ISDN BRI DBM Interface
ISDN BRI U-interface:
One 8-position modular keyed USOC RJ49C jack
Physical interface
RJ49C
Service supported
Capability Package B for 1B-channel service, or
Capability Package I for 2B-channel support,
NI-1 (supporting up to two B-channels)
Data rates
56 kbps and 64 kbps
Standards Compliance
ANSI T1.601 – 1992 (physical layer)
Bellcore SR-NWT-001937, Issue 1 – February 1991
ITU Q.921 – 1992 (link layer)
ITU Q.931 – 1993 (network layer)
TR-TSY-00860, ISDN Calling Number Identification
Services – February 1989, and
Supplement – June 1990
Power Consumption
60 mA at 15 Vdc
Average power .9 watt (3.07 Btu per hour)
Weight
0.27 lbs. 4.3 oz. ( 0.12 kg 122 grams)
Switch Compatibility
National ISDN-1 (NI-1)
Service Supported
Capability Package B for 1B-channel service, or
Capability Package I for 2B-channel support
(supporting up to two B-channels)
Switched Network Interface
One USOC RJ45 8-pole keyed modular plug and jack,
specified in ISO/ IEC 8877
Transmit Interface
Signal Level
13.5 dBm nominal over frequency band,
0 Hz – 80 kHz
Impedance
135 Ω
Receive Interface
Dynamic Range
Operates on 2-wire loops,
defined in ANSI T1.601-1992
Impedance
135 Ω
Modulation and Frequency
2B1Q line coding with
4-level amplitude modulation (PAM) at 80 kbps baud
Channel Equalization
Receiver
E-10
Automatic adaptive equalizer with echo cancellation
DRAFT — June 1999
9191-A2-GH30-00
ISDN DBM Technical Specifications (2 of 2)
Criteria
Specification
ISDN PRI DBM
ISDN PRI DBM Interface
IOne 8-position modular unkeyed USOC RJ48C jack
Physical interface
RJ48C
Service supported
PRI, NI-2, ATT 4ESS, or ATT 5ESS custom
(supporting up to 23 B-channels), with
Circuit-Switched Data capabillity
Data rates
1.536 Kbps
Framing format
D4, ESF
Coding format
B8ZS
0.0 dB, –7.5 dB, –15 dB, –22.5 dB
ANSI PRM
Selectable
Standards Compliance
ANSI T1.403 – 1989 (physical layer) and AT&T 62411
Bellcore SR-NWT-002120, Issue 1 – May 1992
ITU Q.921 – 1992 (link layer)
ITU Q.931 – 1993 (network layer)
TR-TSY-00860, ISDN Calling Number Identification
Services – February 1989, and
Supplement – June 1990
9191-A2-GH30-00
Power Consumption
8 mA at 120 Vac
Average power 1 watt (3.41 Btu per hour)
Weight
0.15 lbs. 2.4 oz. ( 0.07 kg 68 grams)
Switch Compatibility
National ISDN-2 (NI-2),
ATT 4ESS, or
ATT 5ESS
Service Supported
PRI, NI-2, ATT 4ESS custom, or ATT 5ESS custom
(supporting up to 23 B-channels), with
Circuit-Switched Data capability.
Framing Format
D4, ESF
Coding Format
B8ZS
0.0 dB, –7.5 dB, –15 dB, –22.5 dB
ANSI PRM
Selectable
DRAFT — June 1999
E-11
E-12
DRAFT — June 1999
9191-A2-GH30-00
Equipment List
F
Equipment
See page F-6 for cables you can order.
Model/ Feature
Number
Description
NextEDGE Multiservices Access System (MSA)
1xT1 Mux 9161 NAM with 5-slot housing, 120 Vac power supply
9165-A1-201
with power cord, and NAM I/O card. Includes network cable, COM
port-to-PC cable, and 5-Slot Housing with AC Power Supply
Installation Instructions.
1xT1 Mux 9161 NAM with 5-slot housing, rack-mount bracket,
120 Vac power supply with power cord, and NAM I/O card.
Includes network cable, COM port-to-PC cable, and 5-Slot
Housing with AC Power Supply Installation Instructions.
9165-A1-209
1xT1 Mux 9161 NAM with 5-slot housing, – 48 and +24 Vdc
power supply with power cord, and NAM I/O card. Includes
network cable, COM port-to-PC cable, and 5-Slot Housing with
DC Power Supply Installation Instructions.
9165-A1-501
2xT1 Mux 9261 NAM with 5-slot housing (without bezel and
chassis skins), rack-mount bracket, 120 Vac power supply with
power cord, and NAM I/O card. Includes network cable, COM
9165-A1-509
9162-A1-201
port-to-PC cable, and 2-Slot Housing Installation Instructions.
1xT1 Frame 9191 NAM with 2-slot housing and integral modem,
Includes network cable, COM Port-to-PC cable Installation
Instructions, and Quick Reference.
9191-A2-GH30-00
DRAFT — June 1999
9192-A1-201
F-1
Equipment List
Model/ Feature
Number
Description
F-2
1xT1 Frame 9191 NAM with 2-slot housing, an integral modem,
an ISDN BRI DBM, 120 Vac power supply with power cord, and
NAM I/O card. Includes network cable, COM Port-to-PC cable
Installation Instructions, and Quick Reference.
9192-A1-202
an ISDN PRI DBM, 120 Vac power supply with power cord, and
9192-A1-222
1xT1 Frame 9191 NAM with 5-slot housing an integral modem,
9195-A1-201
an ISDN BRI DBM, 120 Vac power supply with power cord, and
9195-A1-202
an ISDN PRI DBM, 120 Vac power supply with power cord, and
9195-A1-222
1xT1 Frame 9191 NAM with 5-slot housing (without bezel and
chassis skin), rack-mount bracket, an integral modem, 120 Vac
power supply with power cord, and NAM I/O card. Includes
network cable, COM Port-to-PC cable Installation Instructions,
and Quick Reference.
9195-A1-209
– 48 and +24 Vdc power supply with power cord, and NAM I/O
card. Includes network cable, COM Port-to-PC cable Installation
9195-A1-501
an ISDN BRI DBM, – 48 and +24 Vdc power supply with power
cord, and NAM I/O card. Includes network cable, COM Port-to-PC
cable Installation Instructions, and Quick Reference.
9195-A1-502
an ISDN PRI DBM, – 48 and +24 Vdc power supply with power
cord, and NAM I/O card. Includes network cable, COM Port-to-PC
cable Installation Instructions, and Quick Reference.
9195-A1-522
1xT1 Frame 9191 NAM with 5-slot housing (without bezel and
chassis skin), rack-mount bracket, an integral modem, – 48 and
+24 Vdc power supply with power cord, and NAM I/O card.
9195-A1-509
DRAFT — June 1999
9191-A2-GH30-00
Equipment List
Model/ Feature
Number
Description
9262-A1-201
port-to-PC cable, and 2-Slot Housing Installation Instructions.
9265-A1-201
2xT1 Mux 9261 NAM with 5-slot housing (without bezel and
chassis skins), rack-mount bracket, 120 Vac power supply with
power cord, and NAM I/O card. Includes network cable, COM
9265-A1-209
2xT1 Mux 9261 NAM with 5-slot housing, – 48 and +24 Vdc power 9265-A1-501
supply with power cord, and NAM I/O card. Includes network
cable, COM port-to-PC cable, and 5-Slot Housing with DC Power
Supply Installation Instructions.
2xT1 Mux 9261 NAM with 5-slot housing, rack-mount bracket,
– 48 and +24 Vdc power supply with power cord, and NAM I/O
card. Includes network cable, COM port-to-PC cable, and 5-Slot
Housing with DC Power Supply Installation Instructions.
9265-A1-509
Optional Features
9191-A2-GH30-00
Mounting Brackets for 5-Slot Housing
9001-F1-890
Universal 2/5-Slot Wall Mount Kit
9008-F1-893
ISDN BRI DBM
9098-F1-870
ISDN PRI DBM
9098-F1-875
High-Speed Synchronous Data APM
9109-F1-604
FXS Analog Voice APM – 2-Wire
9109-F1-648
FXO Analog Voice APM – 2-Wire
9109-F1-658
OCU-DP 2-Port APM
9109-F1-622
OCU-DP 6-Port APM
9109-F1-626
Dual DSX APM
9109-F1-692
E&M Analog Voice APM – 4-Wire
9109-F2-668
DRAFT — June 1999
F-3
Equipment List
Model/ Feature
Number
Description
Network Access Modules (NAMs)
1xT1 Mux 9161 NAM and a NAM I/O card. Includes network cable 9161-B2-902
and T1 Mux NAM Installation Instructions.
1xT1 Carrier NAM and a NAM I/O card. Includes network cable
9167-B1-902
1xT1 Frame 9191 NAM with integral modem and a NAM I/O card.
Includes network cable and NextEDGE NAM Installation
Instructions.
9191-B1-212
2xT1 Mux 9261 NAM and a NAM I/O card. Includes network cable 9261-B2-902
2xT1 Mux 9261 Carrier NAM with I/O card. Includes network
cable and T1 Mux NAM Installation Instructions.
9267-B1-902
T1 TDM NAM Upgrade Kits
Software to upgrade 9161 T1 TDM NAM for FXO capability,
software instructions, current FXO feature (9109-F1-658).
9161-F1-658
Software to upgrade the 9161 Single T1 TDM NAM, new NAM
I/O, and manuals.
9161-F1-620
Software to upgrade the Single T1 TDM 9261 NAM, new NAM
I/O, and manuals.
9261-F1-620
Hardware and software upgrade, 9261 overlay, E8 jumper, 2xT1
I/O, software, cables, manuals.
9261-F1-902
Power Supplies
120 Vac Power Supply (for 2-slot housing)
9002-F1-020
120 Vac Power Supply (for 5-slot housing)
9005-F1-020
DC Power Supply (for 5-slot housing)
9005-F1-050
Universal Power Supply (for access carrier)
9007-F1-040
NMS Products
OpenLane Enterprise
7805-D1-001
OpenLane Workgroup
7805-D1-003
For Unix or Windows NT
9180
NetScout Server
For Unix or Windows NT
9190
NetScout WebCast
F-4
For Unix
9145
For Windows NT
9150
DRAFT — June 1999
9191-A2-GH30-00
Equipment List
Model/ Feature
Number
Description
2-Slot Housing
2-Slot housing and 120 Vac power supply with power cord.
Includes COM Port-to-PC cable and 2-Slot Housing Installation
Instructions.
9002-B1-200
5-Slot Housing
5-Slot housing and – 48 and +24 Vdc power supply with power
cord and alarm relay connector, and filler panels. Includes
COM Port-to-PC cable and 5-Slot Housing with DC Power Supply
9005-B1-500
5-Slot housing (without bezel and chassis skins) and – 48 and
+24 Vdc power supply with power cord, rack-mount bracket,
alarm relay connector, and filler panels. Includes COM Port-to-PC
cable and 5-Slot Housing with DC Power Supply Installation
Instructions.
9005-B1-509
5-Slot housing and 120 Vac power supply, alarm relay connector,
and filler panels. Includes COM Port-to-PC cable and 5-Slot
Housing with AC Power Supply Installation Instructions.
9005-B1-200
5-Slot housing (without bezel and chassis skins) and 120 Vac
power supply with power cord, rack-mount bracket, alarm relay
connector, and filler panels. Includes COM Port-to-PC cable and
5-Slot Housing with AC Power Supply Installation Instructions.
9005-B1-209
Access Carrier
14-Slot Access Carrier, Fan Tray, Baffle, Universal AC Power
Supply, Cables, Manuals
9007-B1-409
Access Carrier Baffle Assembly
9007-S1-897
Universal Power Supply Fan Tray
9007-S1-898
Access Carrier Auxiliary Fan Tray
9007-S1-899
Printed Manual
NextEDGE Multiservices Access System Technical Reference
9191-A2-GH30-00
DRAFT — June 1999
9190-M1-001
F-5
Equipment List
Cables
This table lists cables you can order.
Description
Part Number
Feature Number
RJ48C T1 and DSX-1 Network Cables,
RJ48C-to-RJ48C/RJ49C –
20 feet/ 6.1 meters
035-0209-2031
3100-F1-500
RJ49C Cable for an ISDN BRI DBM
ISDN-U – 20 feet/6.1 meters
035-0209-2031
3100-F1-500
RJ48C Cable for an ISDN PRI DBM –
20 feet/6.1 meters
035-0209-2031
3100-F1-500
T1 Line Interface Cable,
RJ48C-to-CA81A – 20 feet/ 6.1 meters
For use in Canada.
035-0221-2031
3100-F1-510
COM Port-to-Terminal Cable,
8-pin modular-to-DB25P –
14 feet/4.3 meters
035-0314-1431
3100-F2-540
COM Port-to-PC Cable,
Standard EIA-232 Straight-Through Cable
(D-Sub9-to-DB25 for PC serial port) –
14 feet/4.3 meters
035-0313-1431
3100-F2-550
V.35 DTE Adapter
(connects Port to the DTE’s V.35 interface),
EIA 530A-to-V.35 – 1 foot/.3 meter
002-0095-0031
3100-F1-570
V.11/X.21 Interconnect Cable –
1 fo/.31 meter
035-0302-0131
3100-F1-571
RS449 Interconnect Cable –
1 ft./.31 meter
035-0245-0031
3100-F1-580
COM Port-to-LAN Adapter Cable
(custom unkeyed 8-pin plug-to-8-pin plug
modular cable) – 14 feet/4.3 meters
Used as a LANA.
035-0315-1431
3100-F2-910
035-0267-1431
035-0267-2531
3600-F3-501
3600-F3-502
RJ11C Modem Cable for Frame NAM’s
internal modem: 6-position non-keyed
modular plug-to-6-position non-keyed
modular plug – 14 feet/4.3 meters
035-0266-1431
—
T1 Mass Termination Cable (50-pin
plug-to-seven RJ48S plug) – 5 feet/1.524
meters
035-0363-0531
9007-F1-500
EIA-530 straight-through cable
(10 feet – 3 meters)
035-0385-1031
9008-F1-523
RJ48S DDS Network Cable
14 feet/4.3 meters
25 feet/7.6 meters
F-6
DRAFT — June 1999
9191-A2-GH30-00
Equipment List
Description
Part Number
Feature Number
Amphenol plug-to-Amphenol plug –
6 feet/1.9 meters
035-0320-0531
9008-F1-531
3 Amphenol plug-to-1 Amphenol plug –
25 feet/7.6 meters
035-0321-2531
9008-F1-532
035-0321-2531
9008-F1-532
6 feet/1.9 meters
035-0318-0631
9008-F1-533
6 feet/1.9 meters
035-0319-0631
9008-F1-534
M66 Block (with
2-socket 50-pin connectors)
—
9008-F1-535
Modem Cable for an external modem:
6-pin RJ45 modular plug-to-DB25 plug –
14 feet/4.3 meters
035-0336-1431
9008-F1-550
DSX-1 Adapter Cable,
RJ48C-to-DB15 – 1 foot/0.3048 meters
035-0386-0031
9008-F1-560
Voice Cable – Plug-to-Plug
(Amphenol plug-to-Amphenol plug,
25 pairs),
Voice Cable – Socket-to-Plug
(Amphenol socket-to-Amphenol plug,
25 pairs) – 25 feet/7.6 meters
Voice Adaptor – Plug-to-Plug
9191-A2-GH30-00
DRAFT — June 1999
F-7
Equipment List
F-8
DRAFT — June 1999
9191-A2-GH30-00
Index
Numbers
3 Amphenol plug–1 Amphenol plug, F-7
3 Amphenol plug–4 Amphenol plug, F-7
64KCC Loop OOF, 12-18
A
Abnormal Station Code, 12-39
aborting tests, 13-18
Access
Dial-In, 9-10
Dial-In, 8-81
Name, 8-64
Type, 8-68
Access Level, 9-9, 9-12
assigning, 9-8
Port, 8-74, 8-78
security, 4-1
Session, 8-65
accessing NetScout Manager Plus, 5-6
acronyms and terms, glossary, xv
Action on Network Yellow Alarm, 8-37, 12-43
adapter, EIA-530A, to-V.35, D-10
adapters, D-7
adding
DLCI records, 8-50
SLV units to network, 5-4, 7-3
aggregated summary, 5-11
aggregation, application, 3-11
AIS
alarm condition, 11-49, 13-5
at DSX-1, 10-13
at ISDN PRI, 11-35
at Network, 10-13
LED, 10-4, 10-5, 11-29
linkDown trap, C-5
Alarm, 1-8, 13-5
(Fail), 10-4
& Trap Dial-Out, 12-38
adding manually, 6-14
ASCII messages, 12-31
conditions, 13-5
APM, 12-39
DBM, 11-49
editing, 6-11
LED is lit, 13-11
RMON defaults, C-15
using template, 6-10
alarms, dialing out, 12-37
ALM, LED, 10-4, 10-5, 11-29
Alternate
destinations, 11-18
Dial-Out Directory, 8-72
IP Address, 8-80, 8-83
software revision, 10-2
Subnet Mask, 8-80, 8-83
DLCI, 8-55, 11-20
EDLCI, 8-55, 11-21
Link, 8-55, 11-20
Amphenol plug–Amphenol plug, 25 pairs, F-7
Amphenol socket–Amphenol plug, 25 pairs, F-7
Analog Loopback, 12-66, C-13
Annex A and D, LMI Protocol, 8-45
ANSI Performance Report Messages, 8-31, 11-12
APL, 1-3
application, 12-7
APM
alarms, 12-39
application, 12-5
Card Failed, 12-16
card failure, 12-39
configuring
E&M voice ports, 12-55
FXO voice ports, 12-52
FXS voice ports, 12-48
OCU-DP ports, 12-57
synchronous data ports, 12-40
displaying information, 12-12
E&M Voice, 12-4
FXO Voice, 12-4
FXS Voice, 12-4
Health and Status messages, 12-16
hot swapping, 1-4, 8-6, 12-30
insertion, 12-30
LEDs and control leads, 12-13
OCU-DP, 12-4
overview, 12-4
performance statistics, 12-29
removal, 12-31
status, 12-21
Synchronous Data, 12-4
tests, 12-64
voice cable, D-21
DRAFT — June 1999
IN-1
Index
application, using the unit in your network, 3-1
application modules (APMs), 12-1
applications
APMs, 12-5
dial backup, 11-2
direct inward dial, 12-10
off-premises extension, 12-9
T1 TDM with high speed data, 3-15
ARP, inverse, 1-6
ASCII Alarm Messages, 12-31
assign
cross connections, 12-58
DSX-1 time slots, 8-39, 8-40, 12-62
IP addresses and subnet masks, B-18
OCU-DP ports, 12-62
time slots and cross connections, 8-38
voice ports, 12-61
assigning
community names and access levels, 9-8
IP addresses and subnet masks, B-13
asynchronous terminal interface, direct management
control, 2-14
AT commands, 8-81
At-a-Glance report, 7-8, 7-18
authentificationFailure trap, C-4
Auto Backup, Criteria, 11-25
Auto-Configuration, 1-6, 3-12, 4-5
Active, 10-13
setting up, 8-11, 11-23
automatic, setting up backup, 8-16
B
back door access when locked out, 13-4
back-to-back
Mode Active, 10-13
operation, 3-14, 8-21
backing up to a node, 11-4
Backspace, 4-7
Backup
Active, 11-35
applications, 11-2
auto, 11-25
automatic, 11-23
changing automatic configuration, 11-24
ISDN, 1-5
LED, 11-29
modules (DBMs), 11-1
philosophy, 11-7
PVCs, 11-18
verifying setup, 11-33
IN-2
Bc, 8-52
Be, 8-52
Bearer channel, 11-14
BECN, 5-17
Bit Stuffing, 8-30
BKP LED, 11-29
blank, field value, 4-10
branches/menus, 4-5
BRI, technical specifications, E-10
burst
analysis, 5-21
ranges, 5-8
C
cable
1 Amph. plug-to-1 Amph. plug, D-24
1 Amph. socket-to-1 Amph. plug, D-24
3 Amph. plugs-to-1 Amph. plug, D-24, D-25
3 Amph. plugs-to-4 Amph. plugs, D-24, D-27
COM port-to-modem, D-7
COM port-to-PC or terminal/printer, D-6
EIA-530A
to-V.35 DTE adapter cable–to–RS449 DTE
adapter, D-12
to-X.21 DTE adapter, D-13
extension, D-24
T1 Line Interface, D-16
voice APM, D-21
call directories, modem, 10-38
Call Retry, 8-71, 12-38
calling number identification service (CNIS), 11-8
capacity, 5-11, 5-19
CGA, 8-41
changing
auto-configuration, 11-24
automatic backup configuration, 11-24
configuration options, 8-9
domains and groups, 6-8
modem call directory numbers, 10-38
operating mode, 8-21
software release, 10-42
channel allocation, example, 12-60
Channel Loopback, 13-30
channels
DSX-1, 12-26
network, 12-24
DRAFT — June 1999
Index
Character
Length, 8-73
matching, 4-10
CIR (bps), 8-51
Circuit Identifier, 8-31, 11-13
Clearing
cross connection assignments, 8-38
Event, LMI, 8-24, 8-45
existing information, 8-5
statistics, 11-48
clearing
cross connection assignments, 12-58
statistics, 10-27
Clock
Invert Transmit, 8-35
Source, 8-27
Transmit, 8-35
CNIS, 9-11, 11-8
COM port, 1-8, 8-58, 8-69, 8-81
configuring an external device, 2-15
connector, D-4
creating a separate management link, 2-7
to-PC or terminal/printer cable, D-6
Committed Burst Size Bc (Bits), 8-51
Committed Information Rate (CIR), 8-51
Communication Port, user interface, 8-72
Community Name, 8-63
assigning, 9-8
Concord Network Health, compatibility, 7-1
Configuration
APM ports, 12-40
Auto, Active, 10-13
customer storage areas, 1-4
displaying and changing options, 8-9
E&M voice ports, 12-55
end-to-end management control, 2-16
external device, 2-15
FXO voice ports, 12-52
FXS voice ports, 12-48
local management control, 2-13
menu/branch, 4-5
OCU-DP ports, 12-57
option areas, 8-7
saving options, 8-10
setting up automatic backup, 11-23
tables, 8-7
upload/download, 1-4
configuring
added SLV units/elements, 7-4
DBM, 11-10
interface to send traps, 11-26
dial-in access, 8-15
dial-out for traps, 8-16
end-to-end management control, 2-9
local management, 2-5
management DLCI, 2-6
NetScout Manager Plus, 6-4
the system, 8-22
congestion, 5-19
DLCI, 5-18
Connect
Indication String, 8-82
Prefix, 8-81
connectivity, 13-21
IP, 1-4
connector
E&M voice APM, D-22
FXO/FXS voice APM, D-21
consolidated T1 access of DDS circuits, 12-11
Control
characters, 8-84
keys, 4-7
Leads, Ignore, 8-73
menu/branch, 4-5
viewing leads, 10-3, 11-28, 12-13
controlling
async terminal access, 9-2
FTP access, 9-3
ISDN access, 9-11
SNMP access, 9-7
Telnet access, 9-3
conversation elements, 7-3
copy feature, 8-50
copyrights, A
CRC, 10-34
creating
a login, 9-12
a management link, 2-14
a management link via modem, 2-8
a separate management link, 2-7
additional DLCI records, 8-50
new PVC connections/management links, 8-9
PVC connections, 5-7
user history files, 6-16
DRAFT — June 1999
IN-3
Index
criteria for automatic backup, setting, 11-25
Cross Connect Status, 12-24
cross connections, 8-38, 12-58
CTS down, 13-5
to Port Device, 10-14
current software revision, 10-2
customer management, 2-2
customer management
and service provider, IP addressing, B-7
IP addressing, B-4
customer service level report, 7-16
customer-specified storage areas, 1-4
D
Data
Channel Loopback, 13-30
Delivery Ratio (DDR), 1-6
Link Control Identifier (DLCI), 8-61, 8-62, 11-22
Loopback, 12-74, C-12
Port, physical options, 8-34
port connector pin assignments, D-8
Rate (Kbps), 8-72
selection criteria, 4-1
uploading SLV and packet capture, 10-43
Date & Time setting, 8-5
DBM
alarm conditions, 11-49
BRI Card Failed, 11-35, 11-49
call performance statistics, 11-48
changing BRI software, 11-34
configuring interface, 11-10
configuring to send traps, 11-26
connector, D-19
dial backup modules, 11-1
Download Required, 11-35, 11-49
forcing backup and placing a call, 11-27
interface status, 11-40
ISDN problems, 11-51
LEDs and control leads, 11-28
PVC Connection Status, 11-39
setting up, 11-8
test status messages, 11-38
tests, 11-52
verifying setup, 11-33
DCE Manager
installation and setup, 5-2
NMS support, 1-11
starting and stopping a test, 13-17
IN-4
DCLB, 13-30
DDL, 1-8, 2-16
DDR, 1-6
DDS
consolidated T1 access, 12-11
Network Fail, 12-17, 12-39
DE, Set, 8-60
Default IP Destination, 8-57, 8-58
Delete key, 4-7
deleting
a login, 9-13
modem call directory phone number, 10-38
delivery
PVC analysis, 5-20
success, 5-22
Destination, 8-69
Default IP, 8-57, 8-58
DLCI, 8-54, 8-55, 11-20
EDLCI, 8-55, 11-20, 11-21
Link, 8-54, 8-55, 11-19, 11-20
destinations, adding alternate, 11-18
determining, test status/results, 13-18
Device
Fail, 10-4, 10-14, 13-6
messages, 10-6
troubleshooting problems, 13-10
Diagnostic Wizard
setting test timeout, 13-15
starting and stopping a test, 13-17
dial backup, 11-8, 11-9
applications, 11-2
modules (DBMs), 11-1
Dial-In Access, 8-15, 8-77, 8-81
Dial-Out, 8-68
Delay Time (Min), 8-71
Directory, 8-72
SNMP traps, 8-16
Trap, 8-71
dialing out
alarms, 12-37
automatic, 12-37
DID, application, 12-10
Digital Loopback, C-13
Digital Loopbacks, 12-66
Direct Data Link (DDL), 1-8
Directory
Alternate Dial-Out, 8-72
displaying and changing numbers, 10-38
entering phone numbers, 8-14
maintaining modem, 10-38
DRAFT — June 1999
Index
disabling, SNMP access, 9-7
disaster recovery, 11-8, 11-9
applications, 11-2
Discard Eligible (DE), 8-60
Disconnect
String, 8-82
Time (Minutes), 8-66, 8-75, 8-79
discovering elements/DLCIs, 7-3
Discovery, frame relay (FR), 8-11
displaying
APM identity information, 12-12
configuration options, 8-9
DBM identity information, 11-27
identity information, 10-2
LEDs, 10-3, 11-28, 12-13
modem call directory numbers, 10-38
DLCI, 8-61, 8-62, 11-22
Alternate, 8-62, 11-22
congestion, 5-18
Destination, 8-54, 8-55, 11-20
Down, 10-14, 13-5
Down on SLV Timeout, 8-26
elements summary report, 7-12
entering records, 11-18
interface status, 10-21
monitoring user history, 6-19
Number, 8-51
Primary, 8-61
Priority, 8-52
Records, 8-48
Source, 8-54, 11-19
statistics, 10-29
status, 10-21
Traps on Interfaces, 8-70
Type, 8-51
domains and groups
correcting, 6-8
verifying, 6-7
download, 10-41
capability, 1-4
downloading
determining when completed, 10-42
MIBs and SNMP traps, C-2
SLV alarms, 6-10
software, 10-39
user history file, 6-16
Drop & Insert, 1-8
application, 12-9
DS-0 Loopback, 12-73
DS0, Loopback, C-12
DSX-1
adapter pin assignments, D-15
assigning time slots, 8-39, 8-40, 12-62
connector, D-16
connector pin assignments, D-15, D-16
interface LEDs, 10-5
setting up, 8-32
signaling assignments, 8-41
timeslot assignments, 10-25
trunk conditioning, 8-41
DSX-1 channels, 12-26
DTE
configuring port using a management DLCI, 2-6
Loopback, 13-28
Payload Loopback, 13-29
Port 1 LEDs, 10-5
port connector pin assignments, D-8
port-initiated loopbacks, 8-36
DTLB, 13-28
DTPLB, 13-29
DTR
down, 13-6
down from Port-1 Device, 10-14
Ignore Control Leads, 8-73
E
E&M
50-Pin Amphenol connector, D-22
application, 12-6
configuring voice ports, 12-55
Voice APM, 12-4
voice port options, 12-55
EDL, 1-8, 2-16, 2-17
management control, 2-17
EDL Management Link, 12-44
EDLCI, 3-12, 8-61, 8-63, 11-22
Destination, 8-55, 11-20, 11-21
management using PVC multiplexing, 2-10
Primary, 8-61
Source, 8-54, 11-19
EER, 12-47
at ISDN PRI, 11-36
at Network, 10-14
LED, 10-4, 10-5, 11-29
linkDown trap, C-5
DRAFT — June 1999
IN-5
Index
EIA-530A, port, connector, D-9
elements/DLCIs, 7-3
summary report, 7-12
Embedded Data Link (EDL), 1-8, 12-44
Embedded Data Link Connection Identifier (EDLCI),
8-54, 8-55, 8-61, 8-63, 11-19, 11-20, 11-21, 11-22
end-to-end data delivery success, 5-22
ending a session, 4-4
Enter (Return) key, 4-7
entering
DLCI records, 11-18
ISDN call profiles, 11-15
phone numbers, 8-14
system information, 8-5
Enterprise Specific Traps, 8-69, C-8
equipment list, F-1
Error
Event, LMI, 8-24, 8-45
messages, 5-9
errored
frames, 5-14
seconds, 5-16
Errors
frame relay statistics, 10-32
LMI signaling, 5-14
transmission, 5-16
Esc key, 4-7
Escape Sequence, 8-82
Delay, 8-82
ESF, 1-8
ESF Line, statistics, 10-35
even parity, 8-73
exception points, 7-9
exceptions report, 7-9
Excess Burst Size (Bits), 8-52
Excessive
Error Rate linkDown trap, C-5
Error Rate Threshold, 8-31, 11-12
Alarm, 12-47
Threshold, 12-47
executive service level report, 7-14
External
Device, configuring, 2-15
Modem
(on Com Port), 8-81
Commands, 8-81
Transmit Clock, 8-35
IN-6
F
faceplates, 9126, 10-3
Facility Data Link (FDL), 1-8
fault condition indication, 1-8
FDL, 1-8, 2-16
FDR, 1-6
feature numbers
access carrier, F-5
five–slot housing, F-5
9161 Software Upgrade Kit, F-4
power supplies, F-4
two–slot housing, F-5
features
common, 1-3
frame NAM, 1-5
T1 TDM NAM, 1-8
FECN, 5-17
field is blank/empty, 4-10
file transfer, 10-39
Force and Monitor Signaling, 12-68
Frame
Delivery Ratio (FDR), 1-6
size distribution, 5-23
Frame Relay
Discovery, 8-11
DS0s Base Rate, 8-47
monitoring, 3-5
multinational application, 3-6
options, 8-44
statistics, 10-31
troubleshooting PVC problems, 13-12
frames, 8-60
setting the range, 5-8
FTP, 1-4, 8-66, 10-39
file transfers, 10-39
initiating a session, 10-39
limiting access, 9-3, 9-5
Login Required, 8-66
Max Receive Rate (kbps), 8-66
Session, 8-66, 9-5
function keys, 4-6, 4-8
FXO
configure voice ports, 12-52
Voice APM, 12-4
FXO/FXS, 50-Pin Amphenol connector, D-21
FXS, 12-8
configuring voice ports, 12-48
Voice APM, 12-4
DRAFT — June 1999
Index
G
gender adapter/changer, D-7
General
LEDs, 10-4, 11-29
options, 8-26
SNMP management, options, 8-63
Traps, 8-69
generating reports, 7-6
glossary, xv
graphs, Performance Wizard, 5-10
grouping elements for reports, 7-5
H
hardware requirements, 6-2
hardware revision
APM, 12-12
DBM, 11-27
NAM, 10-2
HDLC errors, frame relay statistics, 10-34
Health and Status, messages, 10-13, 11-35, 12-16
heaviest users – output, 5-12
high speed data, 3-2, 3-15
high speed data and
APL application, 12-7
drop & insert application, 12-9
E&M application, 12-6
FXS and E&M application, 12-8
Port-2 or Sync Data APM, 12-5
history
adding files, 6-16
installing files, 6-17
monitoring DLCI, 6-19
hot swapping, 1-4, 8-6
APMs, 12-30
I
Identity, displaying, 10-2, 11-27, 12-12
Ignore Control Leads, 8-73
Inactivity Timeout, 8-66, 8-75, 8-78
Inbound Calling ID, 11-17
installation and setup
DCE Manager, 5-2
Network Health, 7-2
Performance Wizard, 5-2
SLM Reports, 5-25
installing
NetScout Manager Plus and graphs, 6-4
Network Health, 7-2
user history files, 6-17
interface
DBM status, 11-40
menu-driven, 1-4
status, 9-11
user, 4-1
Interface Status, Network, 8-29, 8-32
Internal
Modem Failed, 10-14
international, application, 3-6
Inv SPID, Local Number, Call ID, 11-40
Inverse ARP, 1-6, 2-6, 2-10, 2-11
Invert Transmit
and Received Data, 12-42
Clock, 12-42
Invert Transmit and Received Data, 8-37
Invert Transmit Clock, 8-35
IP
Address, 8-60, 8-75, 8-79, 8-80, 8-83
NMS manager number, 8-69
NMS number, 8-67
connectivity, 1-4
default destination, 8-57
node information, 8-56
Ping test, 13-33
Validation, NMS, 8-67
IP Address, 12-45
assigning addresses and subnet masks, B-18
Node, 8-57
T1 Mux examples, B-14
IP addressing
assigning addresses and subnet masks, B-13
direct PVCs to remote systems, B-8
frame relay, B-3
frame relay examples, B-8
limiting SNMP access, 9-9
selecting a scheme, B-2
DRAFT — June 1999
IN-7
Index
ISDN
Active, 11-36
backup, 1-5
BRI DBM, troubleshooting problems, 11-51
controlling access, 9-11
DBM connector, D-19
DBM operation, 11-27
entering DLCIs on link, 11-18
Link Profile Invalid, 11-36
Network Failed, 11-36, 11-49
physical options, 11-10
PVC Loopback, 13-19
setting up DBM, 11-8
setting up link profiles, 11-15
verifying line, 11-32
IT manager service level report, 7-15
K
keys
keyboard, 4-7
screen function, 4-6, 4-8
L
Lamp Test, 1-9, 10-19, 12-19, 13-35
LAN, adapter and cable, D-5
Last Cause Value messages, 11-42
Latching Loopback, 12-72
latency, 5-22
round trip, 5-22
launching graphs, 5-12
leaders, summary report, 7-11
LEDs, 13-10
descriptions, 10-4, 11-29
network and DSX interface, 10-5
PRI interface, 11-29
viewing, 10-3, 11-28
APM, 12-13
limiting
asynchronous terminal access, 9-2
FTP access, 9-5
SNMP access, 9-7
through IP addresses, 9-9
Telnet access, 9-4
IN-8
Line
Build Out (LBO), 8-30, 11-13
Coding Format, 8-29, 8-32
Equalization, 8-33
Framing Format, 8-29, 8-32, 11-13
Loopback, 12-67, 12-74, 13-22, C-12, C-13
Line Status, 11-40
Link
Destination, 8-54, 8-55, 11-19, 11-20
Name, 11-17
Operating Mode, 11-41
Primary, 8-61, 11-21
Profile Disabled, 11-36
Protocol, 8-76, 8-80
Source, 8-53, 11-19
Status, 11-17
Traps, 8-70
Traps Interfaces, 8-70
TS Management, 2-4, 8-58
linkUp and linkDown
events, 8-70
traps, C-4
LLB, 13-22, 13-25
LMI
Behavior, 8-23, 8-24
Clearing Event (N3), 8-24, 8-45
Down, 10-15, 13-7
Error Event (N2), 8-24, 8-45
Heartbeat (T1), 8-24, 8-46
Inbound Heartbeat (T2), 8-25, 8-46
N4 Measurement Period (T3), 8-25, 8-46
packet utility, 13-36
Parameters, 8-45
pass-through, 8-23
Protocol, 8-44, 8-45
signaling errors, 5-14
Status Enquiry (N1), 8-24, 8-46
uploading packet capture data, 10-43
local, External DTE Loopback, 8-36
locked out, 9-3, 9-12, 13-4
LOF, LED, 10-5, 11-29
logging in, 4-2
logging out, 4-4
DRAFT — June 1999
Index
Login
creating, 9-12
ID, 9-12
modifying and deleting, 9-13
Required, 8-65, 8-74, 8-77, 9-3, 9-4, 9-5
logins, 9-1
Loopback
Analog, C-13
available tests, 1-9
Data, C-12
Detection, OCU-DP, 12-57
Digital, C-13
DTE, 13-28
Payload, 13-29, 13-30
Latching, 12-72
Latching and Nonlatching, C-12
Line, 13-22, C-12, C-13
OCU, C-12
Payload, 13-23
Port (DTE) Initiated, 8-36
PVC, 13-19
Remote, 13-25, C-12
Repeater, 13-24
send V.54, 13-31
LOS, 11-50, 12-39, 13-7
at DSX-1, 10-17
at ISDN PRI, 11-37
at Network, 10-16
at OCU-DP, 12-17
LED, 10-4, 10-5, 11-29
linkDown trap, C-5
Loss of Loop Timing, 12-17
Loss of Signal, linkDown trap, C-5
M
Main Menu, screen/branch, 4-5
maintaining, modem directories, 10-38
making input selections, 4-10
Management
and Communication, options, 8-56
configuring end-to-end control, 2-9
control and IP addressing, 2-1
creating a link, 2-14
creating a separate link, 2-7
customer, 2-2
Direct link to remote T1 units, B-14
General SNMP, 8-63
IP connectivity, 1-4
OpenLane 5.0, 1-10
paths, 1-8
PVCs, 8-59, 11-21
selecting interface, 8-4
service provider, 2-3
SNMP, 1-4, 8-63
through modem connection, 2-8
troubleshooting link, 8-56
TS Link, 8-58
using a dedicated DLCI, 2-11
using PVC multiplexing (EDLCI), 2-10
using RFC 1490 routers, 2-12
Management
customer, IP addressing, B-4
joint customer and service provider, IP addressing,
B-7
service provider, IP addressing, B-5
using multiplexed PVCs, B-6
mass termination cable, D-18
Max Port Rate, 8-35
MDM connector, D-19
Menu, structure, A-1
menu
branches, 4-5
path, 4-6
selecting from, 4-9
menu-driven user interface, 1-4
messages
ASCII Alarm, 12-31
Device, 10-6
Health and Status, 10-13, 11-35, 12-16
Last Cause Values, 11-42
Self-Test Results, 10-12
system, 4-6
System and Test Status, 10-12
Test Status, 10-19, 12-19
DBM, 11-38
MIB
downloading, C-2
support, C-2
minimal remote configuration, 8-5
Mode
changing Operating, demos, 8-21
Operating, 11-41
Test, 10-4
model number, 4-6
Modem, Failed message, 10-14
DRAFT — June 1999
IN-9
Index
modem
connector, D-19
entering directory phone numbers, 8-14
management link, 2-8
setting up, 8-13
modem port, 8-58, 8-69, 8-77
modifying
a login, 9-13
PVC connection backup, 11-18
Module, MisConfig, 12-18
modules
application (APMs), 12-1
dial backup (DBMs), 11-1
Monitor
DTR, 8-36
test pattern, 13-20
Monitor Pattern, C-12
Monitor RTS, 8-36
monitoring, 1-4, 1-9
DLCI history data, 6-19
FrameSaver unit, 10-11
LEDs, 10-3, 11-28, 12-13
using NetScout Manager Plus, 6-22
MSA, overview, 1-1
multinational, application, 3-6
Multiplexed
DLCI, 8-54, 8-55, 8-61, 8-62, 8-63, 11-19,
11-20, 11-21, 11-22
DLCI Type, 8-51
PVCs, 13-21, B-6
multiplexing, applications, 3-9, 3-11
N
N1, LMI Status Enquiry, 8-24, 8-46
N2, LMI Error Event, 8-24, 8-45
N3, LMI Clearing Event, 8-24, 8-45
Name
1 or 2 Access, 9-8
Access, 8-64
Community, 8-63, 8-64
management PVC, 8-60
navigating the screens, 4-7
NCC (network control center), 2-3, 8-49
Net Link, Port Use, 8-72, 8-77
NetOnly, 8-12
IN-10
NetScout
Manager Plus
from Performance Wizard, 5-6
NMS support, 1-12
NMS solution, 6-1
Network
cable pin assignments, D-17
channels, 12-24
Com Link Down, 10-17, 13-7
DLCI records, options, 8-48
Health (Concord) compatibility, 7-1
Initiated Data Channel Loopback, 8-37, 12-43
Initiated DCLB, 8-47
Initiated LLB, 8-30, 11-13
Initiated PLB, 8-30, 11-11
initiated tests, 13-13
interface LEDS, 10-5
interface options, 8-29
management, 1-4
PVC Loopback, 13-19
timeslot assignments, 10-24
Network Health, installation and setup, 7-2
NMS
IP Address, 8-67, 8-69, 9-9
IP Validation, 8-67, 9-9
OpenLane management solution, 1-10
SNMP security, 8-67
NOC (network operation center), 2-3, 3-4, 8-49
Node
IP, 8-56
IP Address, 8-57
Subnet Mask, 8-57
Nonlatching Loopback, 12-72
Number of
Managers, 8-67, 9-9
Trap Managers, 8-68
O
OCU, Loopback, C-12
OCU Loopback, 12-73
OCU-DP
APM, 12-4
assigning ports, 12-62
configuring ports, 12-57
options, 12-57
send Latching Loopback, 12-70
starting/stopping loopback tests, 12-70
tests, 12-70
DRAFT — June 1999
Index
odd parity, 8-73
OID
(object identification), user history file, 6-16
cross-reference (numeric order), C-23
OK, LED, 10-5
OOF
at DSX-1, 10-17
at ISDN PRI, 11-37
at Network, 10-17
LED, 10-4, 10-5, 11-29
linkDown trap, C-5
OpenLane
5.0, 1-10
DCE Manager, 1-11
graphs, 5-10
NMS solutions, 5-1
NMS support, 1-10
operating, changing mode for demos, 8-21
Operating Mode
E&M, 12-55
FXO, 12-52
FXS, 12-48
operation, 4-1
OPX, application, 12-9
organization of this document, xiii
Out of Frame, 10-4
linkDown trap, C-5
Out of Frame (OOF), 12-46
Out of Sync, message, 13-12, 13-20
Outbound Management Priority, 8-52
Outbound Phone Number, 11-17
P
packet capture, uploading data, 10-43
packets, 8-60
Parity, 8-73
Password, 9-12
patents, A
Pattern, tests, 1-9
pattern
send/monitor, 13-20
tests, 13-26, C-12
DTE, 13-29
Performance Statistics, 10-26
Far-End, 12-46
Near-End, 12-46
performance statistics, clearing, 11-48
Performance Wizard
copying directory, 6-5
graphs, 5-10
Phone Number, 11-12, 11-14
physical
data port options, 8-34
DSX-1, 8-32
ISDN options, 11-10
tests, 13-22
pin assignments
3 Amph. plugs-to-1 Amph. plug cable, D-26
3 Amph. plugs-to-4 Amph. plugs cable, D-28
COM port, to-LAN cable, D-5
COM port-to-modem cable, D-7
COM port-to-PC or terminal/printer cable, D-6
DSX-1 connector, D-16
E&M voice APM connector, D-22
EIA-530A
Port 1 or 2, D-9
to-RS449 DTE adapter cable, D-12
to-V.35 DTE adapter cable, D-11
to-X.21 DTE adapter cable, D-13
EIA-232E port, connector/interface, D-9, D-20
FXO/FXS voice APM connector, D-21
FXS voice APM connector, D-21
ISDN DBM connector, D-19
modem connector, D-19
OCU port, D-34
Port-1 V.35 connector, D-8
RJ48S DDS network, D-34
T1 cable, D-17
T1 line interface cable, D-17
T1 network cable, D-15
V.35 crossover cable, D-14
Ping test, 13-33
PLB, 13-23
DRAFT — June 1999
IN-11
Index
Port
(DTE) Initiated Loopbacks, 8-36, 12-44
Access Level, 8-74, 8-78, 9-3
aggregation, 3-11
assignment, clearing, 8-44
Base Rate, 8-35, 12-41
clearing assignments, 12-63
communication, 8-72
configure
E&M voice, 12-55
FXO voice, 12-52
FXS voice, 12-48
OCU-DP ports, 12-57
synchronous data, 12-40
configuring, APM ports, 12-40
displaying assignments, 12-28
modem, 8-77
PVC Loopback, 13-19
Rate, OCU-DP, 12-57
Status
E&M, 12-55
FXO, 12-52
FXS, 12-48, 12-57
Synchronous Data Ports, 12-41
Type, 8-34, 12-41
Use, 8-34, 8-72, 8-77
Port Status, Sync Data Ports, 8-34
Power Supply Alarm, 10-17
PPP, 8-76, 8-80
PRI
interface LEDs, 11-29
technical specifications, E-11
Primary Clock
Failed, 10-18, 13-8
Source, 8-27
Primary Destination
DLCI, 8-54, 11-20
EDLCI, 8-55, 11-20
Link, 8-54, 11-19
Primary Frame Relay Link, 8-61, 8-62, 11-21
Primary Link RIP, 8-62
printed reports, 7-8
product-related documents, xvi
Profile ID (SPID), 11-14
profiles, entering, 11-15
Proprietary, RIP, 8-62, 8-76, 8-80
IN-12
Protocol
address resolution, 1-6
Link, 8-76, 8-80
LMI, 8-44, 8-45
Point-to-Point (PPP), 8-76, 8-80
Routing Information (RIP), 8-62, 8-76, 8-80
Serial Line, IP (SLIP), 8-76, 8-80
support, 1-4, 1-6
PVC
backup, 11-18
Connection, 11-19
connection status, 10-22, 11-39
connections, 8-53
creating, 5-7
data delivery analysis, 5-20
Management, 8-59, 11-21
multiplexing, 2-10, 3-9, 3-11
name, 8-58, 8-69
Network Loopback, 13-19
tests, 1-7, 11-53, 13-18
throughput, 5-16
troubleshooting problems, 13-12
using multiplexed, B-6
Q
QoS, 1-6, 8-52
quality of service, 1-6, 8-52
Quick Reference, 8-7
R
ranges, setting frame and burst, 5-8
ratios, FDR and DDR, 1-6
rear panel, D-3
remote
Loopback, C-12
loopbacks, 13-25
systems
on same subnet, B-9
using direct PVCs, B-8
using routers, B-11
T1 TDM systems, B-14
routing using routers, B-17
units
minimal configuration, 8-5
using different subnets, B-10
DRAFT — June 1999
Index
Remote FT1 Data Channel Loopback, 13-32
Repeater Loopback, 13-24
reports
Network Health, 7-7
SLV, 3-4
resetting
statistics, 10-27, 11-48
the unit, 13-3
unit default configuration options, 13-4
restoring connectivity, 13-4
retrieving statistics, 10-43
Return (Enter) key, 4-7
revision, software and hardware, 10-2, 11-27, 12-12
RFC 1213 and 1573, C-2
RFC 1315, C-2
RFC 1406, C-2
RFC 1490, routers, for transparent management, 2-12
RFC 1604, C-2
RFC 1659, C-2
RFC 1757, C-2
RFC 2021, C-2
right arrow key, 4-7
Ring-Back Tone, FXS, 12-51
RIP, 1-6, 8-19, 8-62, 8-76, 8-80
Primary Link, 8-62
RJ11 modem connector, D-19
RJ27X socket, D-22
RJ48C, COM Port connector, D-15
RJ48C network cable, D-17
RLB, 13-24
RMON
alarm and event defaults, C-15
Specific Traps, C-14
Traps, 8-70
user history collection, 1-6
round trip network latency, 5-22
router-independence, 1-5, 8-23
routers, routing to remote access units, B-17
Routing
Information Protocol (RIP), 8-76, 8-80
on same subnet, B-9, B-15
using different subnets, B-10, B-16
using routers, B-11, B-17
Routing Information Protocol (RIP), 12-45
running reports, 7-6
Rx Gain (dB)
E&M, 12-55
FXO, 12-54
FXS, 12-50
S
Sampling, SLV Inband and Interval, 8-25
saving configuration options, 8-10
screen
area, 4-6
function keys area, 4-6
how to navigate, 4-7
scrolling through valid selections, 4-10
Secondary Clock
Failed, 10-18, 13-8
Source, 8-27
security, 1-4, 4-1, 4-2, 8-8, 9-1
SNMP NMS, 8-67
selecting
a field, 4-10
an IP addressing scheme, B-2
from a menu, 4-9
management interface, 8-4
Self-Test Results messages, 10-12
Send
All Ones on Data Port Not Ready, 12-43
All Ones on DSX-1 Failure, 8-33
and monitor test pattern, 13-26
DRS Tone, C-13
pattern, C-12
Quiet Tone, C-13
test pattern, 13-20
serial number
APM, 12-12
NAM, 10-2
Service, A
Profile ID (SPID), 11-14
service level
agreement, 1-6
customer report, 7-16
executive report, 7-14
IT manager report, 7-15
reports, 7-8
verification, statistics, 10-28
service profile identification (SPID), 11-8
service provider
and customer management, IP addressing, B-7
management, IP addressing, B-5
Session
Access Level, 8-65, 9-4, 9-6
ending, 4-4
starting, 4-2
DRAFT — June 1999
IN-13
Index
Set DE, 8-60
setting
criteria for automatic backup, 11-25
date and time, 8-5
frame and burst ranges, 5-8
setting up
auto-configuration, 8-11, 11-23
considerations when, 8-4
DBM, 11-9
dial backup, 11-8
historical data collection, 5-5
ISDN link profiles, 11-15
management configuration, 8-4
modem, 8-13
SIG, LED, 10-5, 11-29
Signaling, force and monitor, 12-68
Signaling Type
FXO, 12-53
FXS, 12-49
SLA, 1-6, 1-10, 5-20
SLIP, 8-76, 8-80
SLM Reports
creating, 5-24
Slot Assignment information, 10-24, 10-25, 12-27
SLV, 1-2
Delivery Ratio, 8-25
DLCI Down on Timeout, 8-26
frame relay
access, 3-3
monitoring, 3-5
options, 8-25
performance statistics, 10-28
reports, 3-4
Sample Interval (secs), 8-25
Timeout, Error Event Threshold, 8-26
SNMP
assigning community names/access levels, 9-8
dialing out traps, 8-16
Management, 8-63, 9-7, C-2
management, 1-4
MIB object test commands, 1-9
NMS security, 8-67
Number of Managers, 8-67
Traps, 8-68
downloading, C-2
setting up DBM to send, 11-26
standards compliance, C-3
IN-14
software
changing, 10-42
BRI DBM, 11-34
download, 1-4
downloading, 10-39
requirements, 6-3
revision
DBM, 11-27
NAM, 10-2
software revision, APM, 12-12
Source
DLCI, 8-54, 11-19
EDLCI, 8-54, 11-19
Link, 8-53, 11-19
Spacebar, 4-7
specifications, technical, E-1
SPID, 11-8, 11-14
Standard_out RIP, 1-6
standards compliance, SNMP traps, C-3
starting
a session, 4-2
a test, 13-16
graphs, 5-12
Statistics, 12-29
statistics, 1-4, 1-6, 1-9, 10-26
clearing, 11-48
elements, 7-3
selecting performance intervals for display, 10-35
uploading to an NMS, 10-43
Status
cross connect, 12-24
DLCI, 10-21
Enquiry, LMI, 8-24, 8-46
information, 10-11
LED, 10-4
Line, 11-40
menu/branch, 4-5
PVC connection, 10-22, 11-39
System and Test, 12-16
timeslot assignment, 10-23
voice APM, 12-21
Stop Bits, 8-73
stopping a test, 13-16
Subnet
assigning IP addresses and masks, B-13, B-18
Mask, 8-60, 8-76, 8-79, 8-80, 8-83, 12-45
Node, 8-57
routing using different, B-10, B-16
routing using same, B-9, B-15
DRAFT — June 1999
Index
suggestions, user documentation, A
summary
aggregated, 5-11
element/DLCI report, 7-12
leaders report, 7-11
network report, 7-10
supplemental report, 7-13
Switch Type, 11-11
switching
between screen areas, 4-9
to new software, 10-42
Synchronous Data
APM, 12-4
application, 12-5
Port, 12-41
Ports, 12-40
assigning, 12-61
System
Alarm Relay, 8-28
and test status messages, 10-12
configuring options, 8-22
entering information, date, and time, 8-5
Frame Relay and LMI, options, 8-23
messages, 4-6
Name, Contact, and Location, 10-2
T
T1
Canadian line interface cable, D-17
Line Interface Cable, D-16
LMI Heartbeat, 8-24, 8-46
mass termination cable, D-18
network cable, D-17
network interface options, 8-29
TDM NAM’s DSX-1 connector, D-16
T2, LMI Inbound Heartbeat, 8-25, 8-46
T3, LMI N4 Measurement Period, 8-25, 8-46
Tab key, 4-7
TCP, 10-39
TDM, 1-2
technical specifications, E-1
Telnet
Session, 8-64, 9-4
Terminal, Port Use, 8-72, 8-77
FXO, 12-53
FXS, 12-49
Test
jacks, 1-9
menu/branch, 4-5
Mode, 10-4, 11-41
Status messages, 10-19, 12-19
DBM, 11-38
Tones, 12-67
Tests, 1-4, 1-7, 1-9
aborting, 13-18
Analog Loopback, 12-66
APM, 12-64
available, 13-13
Data Channel Loopback, 13-30
Data Loopback, 12-74
DBM, 11-52
determining status and results, 13-18
Digital Loopback, 12-66
DS-0 Loopback, 12-73
DTE Loopback, 13-28
DTE Payload Loopback, 13-29
Duration, 8-27
IP Ping, 13-33
Lamp, 13-35
Latching Loopback, 12-72
Line Loopback, 12-74, 13-22
Nonlatching Loopback, 12-72
OCU Loopback, 12-73
OCU-DP, 12-70, 12-71
pattern, 13-26
physical, 13-22
PVC, 13-18
PVC Loopback, 11-53, 13-19
Remote FT1 Data Channel Loopback, 13-32
Remote Line Loopback, 13-25
Repeater Loopback, 13-24
starting or stopping, 13-16
test pattern, 13-20
Timeout, 8-26, 13-14
Tones, 12-67
V.54 remote loopback, 13-31
voice port, 12-65
DRAFT — June 1999
IN-15
Index
tests, Line Loopback, 12-67
throughput, 5-11, 5-14, 5-16, 5-19
time, setting, 8-5
time slots, 8-38
Timeout
Inactivity, 8-66, 8-75, 8-78
Test, 13-14
timeslot assignment, status, 10-23
timeslot assignments
DSX-1, 10-25
network, 10-24
trademarks, A
training, A
transferring data, 10-43
transmission errors, 5-16
transmit
bit burst analysis, 5-21
frame size distribution, 5-23
Invert, 8-35
Source, 8-35
transparent remote management control, 2-12
Trap
Dial-Out, 8-71
Disconnect, 8-71
Number of Managers, 8-68
Traps
authentificationFailure, C-4
dialing out SNMP, 8-16
DLCI, 8-70
Enterprise Specific, 8-69, C-8
General, 8-69
Link, 8-70
Link Interfaces, 8-70
linkUp and linkDown, C-4
RMON, 8-70
RMON Specific, C-14
SNMP and dial-out, 8-68
standards compliance, C-3
warmStart, C-3
Trend, report, 7-8, 7-20
troubleshooting, 13-1
creating a management link, 8-56
device problems, 13-10
frame relay PVC problems, 13-12
ISDN BRI DBM problems, 11-51
test jacks, 1-9
TS management link, 2-4
IN-16
TruePut, 1-6
Trunk Cond in CGA
E&M, 12-56
FXO, 12-54
FXS, 12-51
trunk lines, 12-6
TS Management Link, 8-56, 8-58
Access Level, 8-59
access level, 9-6
limiting Telnet access, 9-4, 9-5, 9-6
management overview, 2-4
TST, LED, 10-4
Tx Attenuation (dB)
E&M, 12-56
FXO, 12-54
Tx Gain (dB), FXS, 12-51
Type, Access, 8-68
typical applications, 3-1
U
UNI, 8-24, 8-25, 11-4
unknown protocol frames, 5-15
upgradability, 1-3
upgrade, BRI DBM, 11-34
upgrading, system software, 10-41
upload/download capability, 1-4
uploading data, 10-43
user history
adding files, 6-16
installing files, 6-17
monitoring DLCI, 6-19
statistics gathering, 1-6
user interface, 1-4, 1-9, 4-1
cannot be accessed, 13-11
communication port, 8-72
external modem (on Com port), 8-81
resetting/restoring access, 13-4
Telnet session, 8-64
user-defined history, 6-16
user-to-network interface (UNI), 11-4
DRAFT — June 1999
Index
V
W
V. 54 Remote Loopback, 13-31
V.35
connector, D-8
crossover cable, D-14
straight-through cable, D-14
valid, modem directory characters, 10-38
Value Out of Range message, 8-51
variable-bindings, C-5, C-10, C-14
verifying
DBM setup, 11-33
ISDN lines, 11-32
video conferencing, 12-10
viewing
Network Health charts and tables, 7-7
Performance Wizard graphs, 5-10
Voice APM, D-21
status, 12-21
voice ports
assigning, 12-61
tests, 12-65
VT100-compatible terminal, direct management control,
2-14
warmStart
events, General Traps, 8-69
trap, C-3
warranty, A
web browsers, 5-24
Web-site
access to documentation, xvii
glossary, xv
Wink
Delay, FXS, 12-50
Delay (10ms), FXO, 12-53
Duration, FXS, 12-50
Duration (10ms), FXO, 12-53
Y
Yellow
Alarm, C-5
Alarm Signal, 10-4, 10-5, 11-29
at DSX-1, 10-18
at ISDN PRI, 11-38
at Network, 10-18
DRAFT — June 1999
IN-17
Index
IN-18
DRAFT — June 1999

NextEDGE Multiservices Access System Technical Reference

Transcription

Similar documents

Napoleon Container Terminal

Subcutaneous Port Catheter (Port, porta

January 17, 2011 - Village of Port Clements

PDF 1mb - Marina Adelaide

the perfect condo in port aransas!

JAY A. FERNANDO Vice-President Strategic Planning

#104 300 Klahanie Drive • Port Moody

The project incorporates two types of new architecture

PA NEWS - Port Authority Retirees Association, Inc.

Dog Meet and Greet! Saturday June 6th